Re: [foaf-dev] Facebook FOAF Generator - Redux

Kingsley Idehen <kidehen-HpHEqLDO2a7UEDaH6ef/[email protected]> Wed, 13 Jul 2011 14:37:39 +0100
Newsgroups gmane.comp.web.rdfweb
Message-ID <[email protected]>
On 7/13/11 11:10 AM, Matthew Rowe wrote:
> On 12 Jul 2011, at 20:58, Kingsley Idehen wrote:
>
>> On 7/12/11 8:48 PM, Matthew Rowe wrote:
>>>>> I wonder if instead of :
>>>>>
>>>>> rdf:about="#100002283130920"
>>>>>
>>>>> You can use the graph URI?
>>>>>
>>>>> http://graph.facebook.com/100002283130920
>>> I was considering doing something along those lines but was wondering if it would be correct as when the URI is dereferenced it would not return the instance in the FOAF file but would instead retrieve the description located at the above URL.
>>>
>>> Would one solution could be to include an rdfs:seeAlso predicate to associate each foaf:Person instance within the exported file with the above URL?
>>>
>> You transform the Facebook graph into a Linked Data graph [1].
>>
>> Links:
>>
>> 1.
>> http://linkeddata.uriburner.com/about/html/http://linkeddata.uriburner.com/about/id/entity/http/graph.facebook.com/100002283130920
>> -- Description Document URL
>> 2.
>> http://linkeddata.uriburner.com/about/id/entity/http/graph.facebook.com/100002283130920
>> -- Subject Proxy/Wrapper style of de-referencable URI
> I don't think this solves the above issue though.

Of course it does. Have you looked into the graph details?

> It is just a means to consume Linked Data in the browser. What I was considering was the difference between what Melvin suggested previously:
>
> <foaf:Person rdf:about="http://graph.facebook.com/100002283130920">
> 	<foaf:name>...</foaf:name>
> </foaf:Person>
<http://graph.facebook.com/100002283130920> isA URL (a Document Address).
<http://graph.facebook.com/100002283130920#this> isA a generic HTTP URI 
used as a Data Object Name.

> and
>
> <foaf:Person rdf:about="#100002283130920">
> 	<foaf:name>...</foaf:name>
> 	<rdfs:seeAlso rdf:resource="http://graph.facebook.com/100002283130920"/>
> </foaf:Person>

A little better. But, seeAlso points to an Address that resolves to a 
facebook JSON graph rather than a Linked Data graph so FYN is broken 
amongst other things.

The graph we make via Sponger addresses all of these matters. Even note 
the use of owl:sameAs for local data space reasoning amongst other 
goodies :-)


Kingsley
> Not sure which would be best to use. With the former the resource being discussed is contained within the FOAF document, such that when the URI is dereferenced an alternative resource description is returned. In the latter case the resource description is associated with additional information located elsewhere - accessible via FYN.
>
>
>> -- 
>>
>> Regards,
>>
>> Kingsley Idehen	
>> President&   CEO
>> OpenLink Software
>> Web: http://www.openlinksw.com
>> Weblog: http://www.openlinksw.com/blog/~kidehen
>> Twitter/Identi.ca: kidehen
>>
>>
>>
>>
>>
>> _______________________________________________
>> foaf-dev mailing list
>> foaf-dev-RyYwo1q5J+qsOXdr9/[email protected]
>> http://lists.foaf-project.org/mailman/listinfo/foaf-dev
> --
> Dr Matthew Rowe
> Research Associate
> Knowledge Media Institute
> The Open University, Walton Hall, Milton Keynes, MK7 6AA
> http://people.kmi.open.ac.uk/rowe/
>
>


-- 

Regards,

Kingsley Idehen	
President&  CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen