Re: Facebook Linked Data

Hello All, Been away from emails for the last few days, and got beaten to it by a better man. Melvin++. > > WOW! > > One small step for a facebook. One giant leap for the (semantic) Web! > >> >> Jesse Weaver >> Ph.D. Student, Patroon Fellow >> Tetherless World Constellation >> Rensselaer

Re: Facebook Linked Data

On Mon, Sep 26, 2011 at 3:08 PM, Sebastian Schaffert wrote: > > The philosophical part is the distinction of > > http://graph.facebook.com/561666514 representing the document > vs. > http://graph.facebook.com/561666514# representing the person. Whether or not that is "philosophical" the pragmatic

Re: Facebook Linked Data

Am 26.09.2011 um 23:37 schrieb Patrick Logan: > On Mon, Sep 26, 2011 at 1:53 PM, Sebastian Schaffert > wrote: >> >> the point here is that this "philosophical" discussion... > > I did not see anything philosophical in the discussion. I am confused > by that statement. The philosophical part i

Re: Facebook Linked Data

On Mon, Sep 26, 2011 at 1:53 PM, Sebastian Schaffert wrote: > > the point here is that this "philosophical" discussion... I did not see anything philosophical in the discussion. I am confused by that statement. > When I request a Linked Data resource, I expect what comes back to describe > what

Re: Facebook Linked Data

Dear Jesse, I know how they are handled. I just claim that this way of returning data is a bit impractical ;-) Greetings, Sebastian Am 26.09.2011 um 20:02 schrieb Jesse Weaver: > Hi Sebastian. > > See http://www.w3.org/TR/swbp-vocab-pub/#recipe1 for how hash URIs are > handled. > > Jesse

Re: Facebook Linked Data

Dear all, the point here is that this "philosophical" discussion is exactly the reason why Semantic Web/Linked Data is not really popular amongst developers. I am involved in the Semantic Web Community since 2001 and even I find it complex and impractical when it comes to really realising appli

dbSNP SPARQL Endpoint

Dear colleagues, Is anyone aware of an existing SPARQL endpoint for dbSNP ( http://www.ncbi.nlm.nih.gov/projects/SNP)? Unless I am mistaken, I could not find one at Bio2RDF. Thoughts? Best regards, - Jyoti -- Jyotishman Pathak, PhD Assistant Professor of Biomedical Informatics Division of Bio

Re: Facebook Linked Data

Hi Sebastian. See http://www.w3.org/TR/swbp-vocab-pub/#recipe1 for how hash URIs are handled. Jesse Weaver Ph.D. Student, Patroon Fellow Tetherless World Constellation Rensselaer Polytechnic Institute http://www.cs.rpi.edu/~weavej3/index.xhtml On Sep 26, 2011, at 8:16 AM, Sebastian Schaffert

Re: Facebook Linked Data

Hi Sebastian. Please see in-line comments below. On Sep 26, 2011, at 7:46 AM, Sebastian Schaffert wrote: Dear Jesse, Thanks for the effort! I am just experimenting with this. If I request my own Vanity URL http://graph.facebook.com/sebastian.schaffert The data I get back is: @prefix rdf

Re: Facebook Linked Data

On 9/26/11 11:37 AM, Alvaro Graves wrote: We don't have to bring httpRange-14 and its timeless imbroglio into every conversation re. Linked Data :-) True :) the only important thing is to make clear that facebook URIs for documents are different from URIs for people. I prefer to s

Re: Facebook Linked Data

> > We don't have to bring httpRange-14 and its timeless imbroglio into every > conversation re. Linked Data :-) True :) the only important thing is to make clear that facebook URIs for documents are different from URIs for people. Alvaro Graves On Mon, Sep 26, 2011 at 8:34 AM, Kingsley Id

Re: Facebook Linked Data

On 9/26/11 11:24 AM, Alvaro Graves wrote: No, because you are requesting a document Alvaro Graves No, because you are requesting a _document_ (in my case http://graph.facebook.com/672247057) which describes a person (http://graph.facebook.com/672247057#). When I request a document (and i

Re: Facebook Linked Data

On 9/26/11 11:16 AM, Sebastian Schaffert wrote: But then I would say the server should at least reply with a 30x redirect ;-) Not necessarily, they choosen to implement indirection internally, rather than via HTTP response headers. Naturally, doing via HTTP is more flexible and thereby desira

Re: Facebook Linked Data

On 9/26/11 11:05 AM, Alvaro Graves wrote: Hi Sebastian, AFAIK it's not a bug, but a feature :). This is done to comply with the httpRange-14 issue (i.e., you can't retrieve a person through HTTP but you can retrieve a document _about_ a person through HTTP). Since a person and a document abou

Re: Facebook Linked Data

No, because you are requesting a document Alvaro Graves No, because you are requesting a _document_ (in my case http://graph.facebook.com/672247057) which describes a person ( http://graph.facebook.com/672247057#). When I request a document (and it exists) the expected HTTP code should be 200

Re: Facebook Linked Data

Great if an HTTP request for /561666514# 303ed to this document, but /561666514# is not a URI Barry On 26.09.2011 16:05, Alvaro Graves wrote: Hi Sebastian, AFAIK it's not a bug, but a feature :). This is done to comply with the httpRange-14 issue (i.e., you can't retrieve a person through

Re: Facebook Linked Data

But then I would say the server should at least reply with a 30x redirect ;-) Greetings, Sebastian Am 26.09.2011 um 17:05 schrieb Alvaro Graves: > Hi Sebastian, > > AFAIK it's not a bug, but a feature :). This is done to comply with the > httpRange-14 issue (i.e., you can't retrieve a person

Re: Facebook Linked Data

Hi Sebastian, AFAIK it's not a bug, but a feature :). This is done to comply with the httpRange-14 issue (i.e., you can't retrieve a person through HTTP but you can retrieve a document _about_ a person through HTTP). Since a person and a document about a person are different entities, they should

Re: Facebook Linked Data

Dear Jesse, Thanks for the effort! I am just experimenting with this. If I request my own Vanity URL http://graph.facebook.com/sebastian.schaffert The data I get back is: @prefix rdf: . @prefix rdfs: . @prefi