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: Joe Presbrey <presbrey@csail.mit.edu>
Date: Wed, 15 Jun 2011 23:41:39 -0400
Message-ID: <BANLkTimUNbmMcqFpMC3PTQUqM2GWmvvhwA@mail.gmail.com>
To: Kingsley Idehen <kidehen@openlinksw.com>
Cc: public-lod@w3.org
...reviewing my Facebook acl:agent in my personal WACL:
http://presbrey.data.fm/.meta#me

http://uriburner.com/describe/?uri=http%3A%2F%2Fpresbrey.data.fm%2F.meta%23me
seems to beg Facebook Graph sponger ;)

Adding hash keys do not exist (and/or aren't supported) at upstream
sources, changing/masking hosts, or otherwise *mangling* the URIs to
the data breaks the link of Linked Data.

URIs must be dereferencable to the actual data to work efficiently and durably.

Its high time to handle application/json (even Facebook!), link our
data, and share our libraries!

--
Joe Presbrey

On Wed, Jun 15, 2011 at 6:47 PM, Kingsley Idehen <kidehen@openlinksw.com> wrote:
> On 6/15/11 2:14 PM, Melvin Carvalho wrote:
>>
>> Chatted with Joe and Nathan about this some time back.
>>
>> I think there as an argument that said you can get away with not using
>> the #this ... ill try and dig up the notes if you would like a pointer
>
> Not in my data space re. Facebook URLs :-)
>
> http://graph.facebook.com/605980750#this -- a Person Entity Name via HTTP
> URI in my data space
> http://graph.facebook.com/605980750 -- JSON based structured data from FB
> associated with the URI above.
>
>
>
> --
>
> Regards,
>
> Kingsley Idehen
> President&  CEO
> OpenLink Software
> Web: http://www.openlinksw.com
> Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter/Identi.ca: kidehen
>
>
>
>
>
>
>
Received on Thursday, 16 June 2011 03:42:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:21:13 UTC