OF FB LINKED DATA
These are just some of the features of the Facebook Graph API Linked Data.
I have been told that Facebook Linked Data is considered experimental and
that continued support depends on the degree of use by developers.
I hope this was helpful, and I am happy to attempt
...@gmail.comith regards
To: Gannon Dick gannon_d...@yahoo.com
Cc: Juan Sequeda juanfeder...@gmail.com; semantic-...@w3.org Web
semantic-...@w3.org; public-lod@w3.org public-lod@w3.org
Sent: Wednesday, October 26, 2011 7:41 AM
Subject: Re: More about Facebook Linked Data
The only question is what part
Weaver weav...@rpi.edu
Cc: semantic-...@w3.org Web semantic-...@w3.org; public-lod@w3.org
Sent: Tuesday, October 11, 2011 5:24 PM
Subject: Re: More about Facebook Linked Data
Really cool Jesse!
Now imagine linking this data to the ISWC 2011 metadata for the Linked
Data-a-thon :)
http://iswc2011
On 10/11/11 5:35 PM, Jesse Weaver wrote:
STATUS OF FB LINKED DATA
These are just some of the features of the Facebook Graph API Linked
Data. I have been told that Facebook Linked Data is considered
experimental and that continued support depends on the degree of use
by developers.
I
understand that the Graph API and the Open Graph are NOT
the same thing.
STATUS OF FB LINKED DATA
These are just some of the features of the Facebook Graph API Linked
Data. I have been told that Facebook Linked Data is considered
experimental and that continued support depends
are NOT the same
thing.
STATUS OF FB LINKED DATA
These are just some of the features of the Facebook Graph API Linked Data.
I have been told that Facebook Linked Data is considered experimental and
that continued support depends on the degree of use by developers.
I hope this was helpful, and I
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 expectations are my
On Tue, 27 Sep 2011 15:04:13 -0400
Tim rdf tim...@gmail.com 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:
http://purl.org/twc/id/person/TimLebo
Question: would be be reasonable to include more than one of those choices?
On Wed, Sep 28, 2011 at 5:51 AM, Toby Inkster t...@g5n.co.uk wrote:
On Tue, 27 Sep 2011 15:04:13 -0400
Tim rdf tim...@gmail.com wrote:
Thanks for pointing out that it might be a foaf:Account and not
foaf:Person.
I
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 come
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 the
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
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
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 f...@fumi.me wrote:
Hi,
My curl command works fine with the hash URI. It may
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 remove the
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 the
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
On Tue, Sep 27, 2011 at 12:01 AM, Sebastian Schaffert
sebastian.schaff...@salzburgresearch.at 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
On Fri, 23 Sep 2011 10:11:29 -0400
Tim rdf tim...@gmail.com wrote:
http://purl.org/twc/id/person/TimLebo
a foaf:Person;
owl:sameAs
http://graph.facebook.com/24407945#
Personally, I'd say:
http://purl.org/twc/id/person/TimLebo
a foaf:Person ;
foaf:account
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 t...@g5n.co.uk wrote:
On Fri, 23 Sep 2011 10:11:29 -0400
Tim rdf
On 9/27/11 2:53 PM, Toby Inkster wrote:
On Fri, 23 Sep 2011 10:11:29 -0400
Tim rdftim...@gmail.com wrote:
http://purl.org/twc/id/person/TimLebo
a foaf:Person;
owl:sameAs
http://graph.facebook.com/24407945#
Personally, I'd say:
http://purl.org/twc/id/person/TimLebo
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
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: http://www.w3.org/1999/02/22-df-syntax-ns# .
@prefix rdfs: http://www.w3.org/2000/01/rdf-schema# .
@prefix
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
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
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
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
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
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
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
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
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
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
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
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
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
On Mon, Sep 26, 2011 at 1:53 PM, Sebastian Schaffert
sebastian.schaff...@salzburgresearch.at 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
Am 26.09.2011 um 23:37 schrieb Patrick Logan:
On Mon, Sep 26, 2011 at 1:53 PM, Sebastian Schaffert
sebastian.schaff...@salzburgresearch.at wrote:
the point here is that this philosophical discussion...
I did not see anything philosophical in the discussion. I am confused
by that
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 httpRange-14. Please take some time to
On 23 September 2011 14:09, Jesse Weaver weav...@rpi.edu 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
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
Jesse,
Which URI should I put in my foaf file [1][2]?
http://purl.org/twc/id/person/TimLebo
a foaf:Person;
owl:sameAs
http://graph.facebook.com/24407945#, # -
Facebook's URI for me!
http://graph.facebook.com/24407945; # - Or
should I omit the hash?
On 9/23/11 10:11 AM, Tim rdf wrote:
Jesse,
Which URI should I put in my foaf file [1][2]?
http://purl.org/twc/id/person/TimLebo
a foaf:Person;
owl:sameAs
http://graph.facebook.com/24407945#, #-
Facebook's URI for me!
On 23 Sep 2011, at 15:11, Tim rdf wrote:
Why does http://graph.facebook.com/24407945# 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 never
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
kide...@openlinksw.com wrote:
On 9/23/11 10:11 AM, Tim rdf wrote:
Which URI should I put in my foaf file [1][2]?
Thanks Richard!
On Fri, Sep 23, 2011 at 10:55 AM, Richard Cyganiak rich...@cyganiak.de wrote:
On 23 Sep 2011, at 15:11, Tim rdf wrote:
Why does http://graph.facebook.com/24407945# not resolve to anything,
bash-3.2$ curl -H 'Accept: text/turtle' http://graph.facebook.com/24407945#
Hash URIs
Weaver
|| Sent: 23 September 2011 14:10
|| To: semantic-...@w3.org; public-lod@w3.org
|| Subject: Facebook Linked Data
||
|| 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
] On
|| Behalf Of Jesse Weaver
|| Sent: 23 September 2011 14:10
|| To: semantic-...@w3.org; public-lod@w3.org
|| Subject: Facebook Linked Data
||
|| APOLOGIES FOR CROSS-POSTING
||
|| I would like to bring to subscribers' attention that Facebook now
|| supports RDF with Linked Data URIs from its
-requ...@w3.org] On
|| Behalf Of Jesse Weaver
|| Sent: 23 September 2011 14:10
|| To: semantic-...@w3.org; public-lod@w3.org
|| Subject: Facebook Linked Data
||
|| APOLOGIES FOR CROSS-POSTING
||
|| I would like to bring to subscribers' attention that Facebook now
|| supports RDF with Linked Data URIs
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 :-)
--
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 a major salvo to Linked Data bootstrap, at
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
|| To: semantic-...@w3.org; public-lod@w3.org
|| Subject: Facebook Linked Data
||
|| 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
|| To: semantic-...@w3.org; public-lod@w3.org
|| Subject: Facebook Linked Data
||
|| 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
54 matches
Mail list logo
