W3C home > Mailing lists > Public > public-lod@w3.org > September 2011

Re: Facebook Linked Data

From: Jesse Weaver <weavej3@rpi.edu>
Date: Fri, 23 Sep 2011 17:53:08 -0400
Message-Id: <201109232152.p8NLqNtR021749@smtp5.server.rpi.edu>
Cc: Soren.Roug@eea.europa.eu, semantic-web@w3.org, public-lod@w3.org
To: carlo.borsoi@gmail.com
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 wrote:

Hi,

 When I access the data by Graph (eg.
http://graph.facebook.com/100001514767572)  I can see the basics data.
 But, when I use the same ID (e.g
http://www.facebook.com/profile.php?id=100001514767572) I can see moreinformation in the web page.

 How could we get those additional information from graph?

 Carlo

2011/9/23 Jesse Weaver <weavej3@rpi.edu>

> 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/<http://developers.facebook.com/docs/reference/api/>for more information on the Graph API and what's available.  It says:>
> "To get additional information about a user, you must first get their
> permission. At a high level, you need to get an access token for the
> Facebook user. After you obtain the access token for the user, you can
> perform authorized requests on behalf of that user by including the access
> token in your Graph API requests: ...."
>
> I'm glad to hear everyone seems to be enjoying it.  I had fun working on
> it.
>
>
> Jesse Weaver
> Ph.D. Student, Patroon Fellow
> Tetherless World Constellation
> Rensselaer Polytechnic Institute
> http://www.cs.rpi.edu/~**weavej3/index.xhtml<http://www.cs.rpi.edu/~weavej3/index.xhtml>>
>
> On Sep 23, 2011, at 8:14 AM, S�ren Roug wrote:
>
>  If you pull the schema http://graph.facebook.com/**schema/user<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-request@w3.org
[mailto:public-lod-request@w3.**org<public-lod-request@w3.org>]
>> On
>> || Behalf Of Jesse Weaver
>> || Sent: 23 September 2011 14:10
>> || To: semantic-web@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) URIs in the RDF are
>> dereferenceable
>> || in accordance with httpRange-14.  Please take some time to check it
>> out.
>> ||
>> || If you have a vanity URL (mine is jesserweaver), you can get RDF about
>> you:
>> ||
>> || curl -H 'Accept: text/turtle' http://graph.facebook.com/<**vanity-url>>> || curl -H 'Accept: text/turtle' http://graph.facebook.com/**jesserweaver<http://graph.facebook.com/jesserweaver>>> || If you don't have a vanity URL but know your Facebook ID, you can use
>> || that instead (which is actually the fundamental method).
>> ||
>> || curl -H 'Accept: text/turtle' http://graph.facebook.com/<**>> facebook-id>
>> || curl -H 'Accept: text/turtle' http://graph.facebook.com/**1340421292<http://graph.facebook.com/1340421292>>> || >From there, try dereferencing URIs in the Turtle.  Have fun!
>> ||
>> || Jesse Weaver
>> || Ph.D. Student, Patroon Fellow
>> || Tetherless World Constellation
>> || Rensselaer Polytechnic Institute
>> || http://www.cs.rpi.edu/~**weavej3/ <http://www.cs.rpi.edu/~weavej3/>>> ||
>> ||
>> ||
>> ||
>>
>>
>>
>
>
===========End of original message text===========



Received on Friday, 23 September 2011 21:53:16 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:35 UTC