Re: Facebook Linked Data

Dear Norman, Sorry for replying late, I was a bit busy with other things ... Am 28.09.2011 um 19:13 schrieb Norman Gray: > > Sebastian, hello. > > On 27 Sep 2011, at 13:43, Sebastian Schaffert wrote: > >>> I think you're disappointed because your expectations may be wrong. >> >> My expectat

Re: Facebook Linked Data

Sebastian, hello. On 27 Sep 2011, at 13:43, Sebastian Schaffert wrote: >> I think you're disappointed because your expectations may be wrong. > > My expectations are my expectations. But I accept that the world maybe does > not satisfy them ;-) I often have the same feeling -- *sigh* -- I've

Re: Facebook Linked Data

Question: would be be reasonable to include more than one of those choices? On Wed, Sep 28, 2011 at 5:51 AM, Toby Inkster wrote: > On Tue, 27 Sep 2011 15:04:13 -0400 > Tim rdf wrote: > >> Thanks for pointing out that it might be a foaf:Account and not >> foaf:Person. >> >> I need to dig into th

Re: Facebook Linked Data

On Tue, 27 Sep 2011 15:04:13 -0400 Tim rdf wrote: > Thanks for pointing out that it might be a foaf:Account and not > foaf:Person. > > I need to dig into their semantics before I run around misusing them! You could even do: a fo

Re: Facebook Linked Data

On 9/27/11 3:04 PM, Tim rdf wrote: Toby, Thanks for pointing out that it might be a foaf:Account and not foaf:Person. I need to dig into their semantics before I run around misusing them! But you can make a linked data graph based on your own world view and its associated semantics, as per m

Re: Facebook Linked Data

On 9/27/11 2:53 PM, Toby Inkster wrote: On Fri, 23 Sep 2011 10:11:29 -0400 Tim rdf wrote: a foaf:Person; owl:sameAs Personally, I'd say: a foaf

Re: Facebook Linked Data

Toby, Thanks for pointing out that it might be a foaf:Account and not foaf:Person. I need to dig into their semantics before I run around misusing them! Regards, Tim Lebo On Tue, Sep 27, 2011 at 2:53 PM, Toby Inkster wrote: > On Fri, 23 Sep 2011 10:11:29 -0400 > Tim rdf wrote: > >>

Re: Facebook Linked Data

On Fri, 23 Sep 2011 10:11:29 -0400 Tim rdf wrote: > >a foaf:Person; >owl:sameAs > Personally, I'd say: a foaf:Person ; foaf:account

Re: Facebook Linked Data

On Tue, Sep 27, 2011 at 12:01 AM, Sebastian Schaffert wrote: > > Ok, let me be a bit more precise: I can stick with REST, JSON, and > human readable service descriptions for each service that define for > me how to call the REST webservice and how the JSON (or whatever) > data that comes back will

Re: Facebook Linked Data

On 9/27/11 7:43 AM, Sebastian Schaffert wrote: Am 27.09.2011 um 09:44 schrieb Norman Gray: I am disappointed because I asked for data about http://graph.facebook.com/561666514 and got back data about http://graph.facebook.com/561666514# - this is my main concern. Maybe I should ask for http://

Re: Facebook Linked Data

Am 27.09.2011 um 09:44 schrieb Norman Gray: >> >> I am disappointed because I asked for data about >> http://graph.facebook.com/561666514 and got back data about >> http://graph.facebook.com/561666514# - this is my main concern. Maybe I >> should ask for http://graph.facebook.com/561666514# in

Re: Facebook Linked Data

On 27 Sep 2011, at 08:44, Norman Gray wrote: >> Because the browser (according to the standard) removes the trailing "#". >> But if you send a GET request manually (telnet etc) and including the # you >> will get a 404. > > Well, what did you expect? As you say, the client is supposed to remo

Re: Facebook Linked Data

According to the changelog, this issue has been fixed in 7.20.0. http://curl.haxx.se/changes.html#7_20_0 - fragment part of URLs are no longer sent to the server Fumi On Tue, Sep 27, 2011 at 4:36 PM, Fumihiro Kato wrote: > Hi, > > My curl command works fine with the hash URI. It may be a versio

Re: Facebook Linked Data

Sebastien, hello. [trimming CCs] On 27 Sep 2011, at 08:01, Sebastian Schaffert wrote: >>> - I ask for http://graph.facebook.com/sebastian.schaffert and I get >>> http://graph.facebook.com/561666514# >>> - I ask for http://graph.facebook.com/561666514 and I get >>> http://graph.facebook.com/56

Re: Facebook Linked Data

Hi, My curl command works fine with the hash URI. It may be a version issue. % curl -V curl 7.21.6 (x86_64-apple-darwin10.7.0) libcurl/7.21.6 OpenSSL/1.0.0d zlib/1.2.5 libidn/1.22 Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smtp smtps telnet tftp Features: IDN IPv6

Re: Facebook Linked Data

On 27 Sep 2011, at 09:01, Sebastian Schaffert wrote: >> >> >>> - I ask for http://graph.facebook.com/sebastian.schaffert and I get >>> http://graph.facebook.com/561666514# >>> - I ask for http://graph.facebook.com/561666514 and I get >>> http://graph.facebook.com/561666514# >>> - I ask for ht

Re: Facebook Linked Data

Dear Patrick and all, Am 27.09.2011 um 00:47 schrieb Patrick Logan: > >> The distinction is impractical, especially if you compare it >> with the simplicity of the alternative JSON-based Open Graph >> representation. > > That may be a matter of one's experience and what one wishes to > do with

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

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

Re: Facebook Linked Data

Try adding ?metadata=1. For example: curl -H 'Accept: text/turtle' 'http://graph.facebook.com/jesserweaver?metadata=1' Jesse Weaver Ph.D. Student, Patroon Fellow Tetherless World Constellation Rensselaer Polytechnic Institute http://www.cs.rpi.edu/~weavej3/ ==Original message text===

Re: Facebook Linked Data

See http://developers.facebook.com/docs/authentication/ . Jesse Weaver Ph.D. Student, Patroon Fellow Tetherless World Constellation Rensselaer Polytechnic Institute http://www.cs.rpi.edu/~weavej3/ ==Original message text=== On Fri, 23 Sep 2011 16:50:47 EDT Carlo Borsoi Moura

Re: Facebook Linked Data

On 9/23/11 3:51 PM, Kingsley Idehen wrote: On 9/23/11 2:48 PM, Kingsley Idehen wrote: On 9/23/11 11:00 AM, Tim rdf wrote: Thanks, Kingsley. But I'm still at a loss for having my facebook URI being part of Linked Data... I am writing a long post for G+ that explains how Facebook as just added

Re: Facebook Linked Data

On 9/23/11 11:00 AM, Tim rdf wrote: Thanks, Kingsley. But I'm still at a loss for having my facebook URI being part of Linked Data... I am writing a long post for G+ that explains how Facebook as just added a major salvo to Linked Data bootstrap, at InterWeb scale. Give me <= 30 mins :-) --

Re: Facebook Linked Data

Hi all, Generally, a huge +1 for implementing this issue @ Facebook! On 9/23/2011 5:14 PM, Søren Roug wrote: If you pull the schema http://graph.facebook.com/schema/user then you'll see they are thinking about making a lot more properties available than what's sent out now. See also http:

Re: Facebook Linked Data

Actually, those properties already exist. You just don't see them, for example, in my data because I have not elected to share more data. If you have a Facebook account, check out http://developers.facebook.com/docs/reference/api/ for more information on the Graph API and what's available.

RE: Facebook Linked Data

If you pull the schema http://graph.facebook.com/schema/user then you'll see they are thinking about making a lot more properties available than what's sent out now. || -Original Message- || From: public-lod-requ...@w3.org [mailto:public-lod-requ...@w3.org] On || Behalf Of Jesse Weaver

Re: Facebook Linked Data

Thanks Richard! On Fri, Sep 23, 2011 at 10:55 AM, Richard Cyganiak wrote: > On 23 Sep 2011, at 15:11, Tim rdf wrote: >> Why does not resolve to anything, >> >> bash-3.2$ curl -H 'Accept: text/turtle' http://graph.facebook.com/24407945# > > Hash URIs are resol

Re: Facebook Linked Data

Thanks, Kingsley. But I'm still at a loss for having my facebook URI being part of Linked Data... (see within) On Fri, Sep 23, 2011 at 10:40 AM, Kingsley Idehen wrote: > On 9/23/11 10:11 AM, Tim rdf wrote: >> Which URI should I put in my foaf file [1][2]? >> >>

Re: Facebook Linked Data

On 23 Sep 2011, at 15:11, Tim rdf wrote: > Why does not resolve to anything, > > bash-3.2$ curl -H 'Accept: text/turtle' http://graph.facebook.com/24407945# Hash URIs are resolved by stripping the hash off the URI first. The hash and anything behind it is ne

Re: Facebook Linked Data

On 9/23/11 10:11 AM, Tim rdf wrote: Jesse, Which URI should I put in my foaf file [1][2]? a foaf:Person; owl:sameAs , #<- Facebook's URI for me!

Re: Facebook Linked Data

Jesse, Which URI should I put in my foaf file [1][2]? a foaf:Person; owl:sameAs , # <- Facebook's URI for me! ; # <- Or should I omit th

Re: Facebook Linked Data

On 9/23/11 8:09 AM, Jesse Weaver wrote: APOLOGIES FOR CROSS-POSTING I would like to bring to subscribers' attention that Facebook now supports RDF with Linked Data URIs from its Graph API. The RDF is in Turtle syntax, and all of the HTTP(S) URIs in the RDF are dereferenceable in accordance with

Re: Facebook Linked Data

On 23 September 2011 14:09, Jesse Weaver wrote: > APOLOGIES FOR CROSS-POSTING > > I would like to bring to subscribers' attention that Facebook now > supports RDF with Linked Data URIs from its Graph API.  The RDF is in > Turtle syntax, and all of the HTTP(S) URIs in the RDF are dereferenceable >