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

Melvin of course technically you can do it no problem but as Kingsley
mentioned it is currently not good practice.

It's an obvious and constantly reoccurring issue and I am not
satisfied with the current design pattern myself.

I am wondering if we should consider a new protocol layer such as
sparql:// for sparql endpoints



On Wed, Jul 13, 2011 at 1:36 PM, Melvin Carvalho
<[email protected]> wrote:
> On 13 July 2011 18:43, Matthew Rowe <[email protected]> wrote:
>>
>> On 13 Jul 2011, at 14:37, Kingsley Idehen wrote:
>>
>>> 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?
>>
>> I looked at the link that Melvin sent previously. I thought that it might be best to link to the Facebook graph URI and then put the onus on the client to parse the response - e.g. using URI Burner if they should wish or a similar tool for consuming the response.
>>
>> In the above, are you suggesting that the Facebook graph URL should be replaced with a URI Burner URL containing the Facebook Graph URL? e.g. <person> rdfs:seeAlso <http://linkeddata.uriburner.com/about/html/http://linkeddata.uriburner.com/about/id/entity/http/graph.facebook.com/100002283130920>
>>
>>>
>>>> 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).
>
> The data.fm implementation of fecebook integration links to this kind
> of FB graph URI, as if it were a foaf : Person.
>
> I had a chat with Joe about this, some time back, and he seemed to
> think it was OK.
>
>>> <http://graph.facebook.com/100002283130920#this> isA a generic HTTP URI
>>> used as a Data Object Name.
>>
>> There is no notion of the "this" resource in the Facebook Graph URL, would using this hash uri work?
>>
>>>
>>>> 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.
>>
>> See my comment above, not sure it is valid.
>>
>>>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> Dr Matthew Rowe
>> Research Associate
>> Knowledge Media Institute
>> The Open University, Walton Hall, Milton Keynes, MK7 6AA
>> http://people.kmi.open.ac.uk/rowe/
>>
>>
>> --
>> The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).
>>
>> _______________________________________________
>> foaf-dev mailing list
>> foaf-dev-RyYwo1q5J+qsOXdr9/[email protected]
>> http://lists.foaf-project.org/mailman/listinfo/foaf-dev
>>
> _______________________________________________
> foaf-dev mailing list
> foaf-dev-RyYwo1q5J+qsOXdr9/[email protected]
> http://lists.foaf-project.org/mailman/listinfo/foaf-dev
>



-- 
Marco Neumann
KONA

---
Join us at the Semantic Web Media Summit in New York City for an
exciting event on 14 September 2011
http://www.lotico.com/evt/swmsNYC2011/