- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Fri, 23 Sep 2011 10:40:40 -0400
- To: public-lod@w3.org, "semantic-web@w3.org" <semantic-web@w3.org>
- Message-ID: <4E7C9A68.6030308@openlinksw.com>
On 9/23/11 10:11 AM, Tim rdf wrote: > Jesse, > > Which URI should I put in my foaf file [1][2]? > > <http://purl.org/twc/id/person/TimLebo> > a foaf:Person; > owl:sameAs > <http://graph.facebook.com/24407945#>, #<----- > Facebook's URI for me! > <http://graph.facebook.com/24407945>; #<----- Or > should I omit the hash? > > [1] https://github.com/timrdf/csv2rdf4lod-automation/blob/master/doc/instances/person/lebot.ttl > [2] my vanity is timothy.lebo Use: http://graph.facebook.com/24407945#this . It's your data space, so you can use identifiers as you see fit, in line with the world view to which said data space subscribes :-) Example of pattern put to use: 1. https://plus.google.com/112399767740508618350/posts/91458DKChnr -- controlling a holistic digital representation of my profile via owl:sameAs applied across Facebook, G+ and other data spaces 2. https://plus.google.com/112399767740508618350/posts/54JNqCkqBFY -- same as above, but using http://vizualize.me/kidehen data space as focal point . Kingsley > > > Why does<http://graph.facebook.com/24407945#> not resolve to anything, > > bash-3.2$ curl -H 'Accept: text/turtle' http://graph.facebook.com/24407945# > _:error > :error [ > :message "(#803) Some of the aliases you requested do not exist: 24407945#" ; > :type "OAuthException" ] . > > while<http://graph.facebook.com/24407945> resolves to something that > doesn't describe<http://graph.facebook.com/24407945>? > > bash-3.2$ curl -H 'Accept: text/turtle' http://graph.facebook.com/24407945 > @prefix user:<http://graph.facebook.com/schema/user#> . > </24407945#> > user:id "24407945" ; > user:name "Timothy Lebo" ; > > Thanks, > Tim Lebo > > > > Some background: > > bash-3.2$ rapper -g -o ntriples http://graph.facebook.com/timothy.lebo > rapper: Parsing URI http://graph.facebook.com/timothy.lebo > <http://graph.facebook.com/24407945#> > <http://graph.facebook.com/schema/user#id> "24407945" . > <http://graph.facebook.com/24407945#> > <http://graph.facebook.com/schema/user#name> "Timothy Lebo" . > <http://graph.facebook.com/24407945#> > <http://graph.facebook.com/schema/user#first_name> "Timothy" . > <http://graph.facebook.com/24407945#> > <http://graph.facebook.com/schema/user#last_name> "Lebo" . > <http://graph.facebook.com/24407945#> > <http://graph.facebook.com/schema/user#username> "timothy.lebo" . > <http://graph.facebook.com/24407945#> > <http://graph.facebook.com/schema/user#gender> "male" . > <http://graph.facebook.com/24407945#> > <http://graph.facebook.com/schema/user#locale> "en_US" . > rapper: Parsing returned 7 triples > > > On Fri, Sep 23, 2011 at 8:09 AM, Jesse Weaver<weavej3@rpi.edu> wrote: >> APOLOGIES FOR CROSS-POSTING >> >> I would like to bring to subscribers' attention that Facebook now >> supports RDF with Linked Data URIs from its Graph API. The RDF is in >> Turtle syntax, and all of the HTTP(S) URIs in the RDF are dereferenceable >> in accordance with httpRange-14. Please take some time to check it out. >> >> If you have a vanity URL (mine is jesserweaver), you can get RDF about you: >> >> curl -H 'Accept: text/turtle' http://graph.facebook.com/<vanity-url> >> curl -H 'Accept: text/turtle' http://graph.facebook.com/jesserweaver >> If you don't have a vanity URL but know your Facebook ID, you can use >> that instead (which is actually the fundamental method). >> >> curl -H 'Accept: text/turtle' http://graph.facebook.com/<facebook-id> >> curl -H 'Accept: text/turtle' http://graph.facebook.com/1340421292 >> > From there, try dereferencing URIs in the Turtle. Have fun! >> >> Jesse Weaver >> Ph.D. Student, Patroon Fellow >> Tetherless World Constellation >> Rensselaer Polytechnic Institute >> http://www.cs.rpi.edu/~weavej3/ >> >> >> >> >> >> > -- Regards, Kingsley Idehen President& CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Friday, 23 September 2011 14:41:02 UTC