21 messages in com.googlegroups.social-graph-apiRe: Live data?
FromSent OnAttachments
Julian Bond02 Feb 2008 00:54 
Danny Ayers02 Feb 2008 02:10 
Arne Roomann-Kurrik (Google)02 Feb 2008 17:36 
Julian Bond03 Feb 2008 02:05 
Danny Ayers03 Feb 2008 02:27 
Markus Peter03 Feb 2008 02:55 
Julian Bond03 Feb 2008 03:27 
Martin Atkins03 Feb 2008 04:04 
Danny Ayers03 Feb 2008 04:14 
Artemy Tregoubenko03 Feb 2008 04:16 
Julian Bond03 Feb 2008 04:20 
Brad Fitzpatrick03 Feb 2008 10:23 
Brad Fitzpatrick03 Feb 2008 10:26 
Brad Fitzpatrick03 Feb 2008 10:37 
Dale Newfield03 Feb 2008 14:02 
Brad Fitzpatrick03 Feb 2008 14:10 
Martin Atkins03 Feb 2008 15:55 
Arne Roomann-Kurrik (Google)03 Feb 2008 18:07 
Brad Fitzpatrick03 Feb 2008 20:19 
victorc04 Feb 2008 08:55 
BerlinBrown07 Feb 2008 15:03 
Subject:Re: Live data?
From:Martin Atkins (m.@degeneration.co.uk)
Date:02/03/2008 03:55:42 PM
List:com.googlegroups.social-graph-api

Brad Fitzpatrick wrote:

Mart, I want to dispel any idea that LiveJournal's special cased.

Here's what's happening the LJ case:

-- the parsers see the livejournal profile pages, which have XFN link. the parser then generates edges like:

http://mart.livejournal.com/profile ----friend----> http://brad.livejournal.com/profile

Then, the edge is run through google-sgnodemapper for canonicalization, which turns it into:

sgn://livejournal.com/?ident=mart ----friend----> sgn://livejournal.com/?ident=brad

Hmm.

It could be argued that the livejournal.js file in sgnodemapper *is* a special case for LiveJournal, along with special cases for Amazon, AOL, Blogspot, Facebook, ....

To be honest, I'm not entirely convinced about the sgnodemapper project. I can't help but think that a central catalogue of the URL normalization rules for every service in existance just won't scale, and that this needs to be a decentralized process. The simplest solution that springs to mind is this:

<link rel="canonical" href="sgn://livejournal.com/?ident=mart" />

Now of course processors of this would be required to ignore assersions that are in the "wrong" domain, and you might have to adjust the sgn syntax a bit to allow for this, but I think something like this would scale better in the long run. In the short term, the special cases in the library are a good bootstrapping solution for the sites which haven't adopted this yet. (all of them!)

I'm also not convinced that using URLencoded query string arguments is a good idea, but that's a discussion for another day. Is there a separate mailing list for sgnodemapper?