On Thu, Jun 16, 2011 at 6:28 AM, Kingsley Idehen kide...@openlinksw.com wrote:
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.
Its high time to handle
On 6/20/11 4:16 PM, Joe Presbrey wrote:
On Thu, Jun 16, 2011 at 6:28 AM, Kingsley Idehenkide...@openlinksw.com wrote:
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
On 6/20/11 4:54 PM, Joe Presbrey wrote:
On Mon, Jun 20, 2011 at 11:29 AM, Kingsley Idehen
kide...@openlinksw.com wrote:
Facebook have released structured data in graph form. They've done so in the
Information Space dimension and its absolutely a great contribution.
owl:shameAs is really about
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
On 6/16/11 4:41 AM, Joe Presbrey wrote:
...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 ;)
Yes, but that's a URL (Address) for an HTML
On 6/15/11 11:35 AM, Richard Cyganiak wrote:
Hi Kingsley,
I have a few questions. See below.
On 14 Jun 2011, at 22:24, Kingsley Idehen wrote:
On 6/13/11 9:29 AM, Kingsley Idehen wrote:
Then you go on to say that it would be much better if it said:
id:
On 15 Jun 2011, at 12:01, Kingsley Idehen wrote:
https://graph.facebook.com/kidehen#this
Would you agree that Facebook are the owners of this URI?
I would say they own the URI: https://graph.facebook.com/kidehen
I use that URI as the basis for a disambiguated URI in my data space, for
On 12 June 2011 23:05, Kingsley Idehen kide...@openlinksw.com wrote:
All,
Facebook offers a data space (of the silo variety). Every Object has an
Address (URL) from which you can access its actual Representation in JSON
format.
Example using the URL: http://graph.facebook.com/kidehen:
{
On 13 June 2011 10:29, Kingsley Idehen kide...@openlinksw.com wrote:
On 6/13/11 8:46 AM, Richard Cyganiak wrote:
On 12 Jun 2011, at 22:05, Kingsley Idehen wrote:
Example using the URL: http://graph.facebook.com/kidehen:
{
id: 605980750,
name: Kingsley Uyi Idehen,
first_name:
On 6/15/11 2:11 PM, Melvin Carvalho wrote:
If you think that's good, try this!
http://graph.facebook.com/kidehen?metadata=1
Yes, we did a while back when making the Facebook sponger cartridge :-)
BTW - Visit uriburner.com and then click on the FB button.
I don't use FB as avidly as Aldo, so
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 :-)
...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,
{
id: 605980750,
name: Kingsley Uyi Idehen,
first_name: Kingsley,
middle_name: Uyi,
last_name: Idehen,
link: https://www.facebook.com/kidehen;,
username: kidehen,
gender: male,
locale: en_US
}
Some observations:
id attribute has value 605980750, this value means
13 matches
Mail list logo
