W3C home > Mailing lists > Public > public-lod@w3.org > June 2011

Re: Using Facebook Data Objects to illuminate Linked Data add-on re. structured data

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Mon, 20 Jun 2011 17:14:19 +0100
Message-ID: <4DFF71DB.4020006@openlinksw.com>
To: Joe Presbrey <presbrey@csail.mit.edu>
CC: public-lod@w3.org
On 6/20/11 4:54 PM, Joe Presbrey wrote:
> Thanks for clarifying however eating Facebook's lunch and minting URIs
> that append #this is still not the best recommendation.
http://graph.facebook.com/kidehen#this  in my data space means that you 
can SPARQL, build exploit and FYN using that name or my local name. It 
also resolves to FB's specific Object Representation with any Name vs 
Address ambiguity. That's a win right there.

What makes that a win? The fact that it less of a burden for them to see 
the prowess of turning the literals in their graph into HTTP URI Names. 
Even if they never did it, that pattern is great tutorial material for 
anyone seeking to understand what Linked Data is about, and why Name and 
Address disambiguation is vital. Just as vital as its always been 
elsewhere in computing where "data access by reference" has been put to 
good use etc..



Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
Received on Monday, 20 June 2011 16:14:54 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:29:54 UTC