W3C home > Mailing lists > Public > public-rww@w3.org > October 2011

Re: Using Twitter as an IdP space for WebID

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Sat, 29 Oct 2011 12:33:11 -0400
Message-ID: <4EAC2AC7.4070902@openlinksw.com>
To: public-rww@w3.org
On 10/29/11 12:04 PM, Kingsley Idehen wrote:
>> What is the connection to linked data ?
>
> The aforementioned URI is de-referencable. It resolves to a structured 
> representation it the URI referents description.
For sake of clarity, typo fixed paragraph.

The aforementioned URI is de-referencable. It resolves to a structured 
representation of the description of its referent. Of course, the 
representation is a graph pictorial, but actual serialization format is 
negotiable.

What we do in this case is transform a JSON object from Twitter into a 
Linked Data Object in our data space, which is associated with the 
relying agent that speaks the WebID protocol. Inside our particular 
relying agent's data space.

Some links that should make this a little clearer:

1. 
http://search.twitter.com/search.json?q=%40Fingerprint:EB:A1:74:5E:5E:74:98:71:2A:19:2D:4B:26:43:65:19 
-- JSON object from Twitter data space .

2. http://goo.gl/8yGwq -- effects transformation of JSON object using 
one of my URIs.

3. http://goo.gl/zGSes -- ditto using one of Melvin's URIs.

-- 

Regards,

Kingsley Idehen	
President&  CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen








Received on Saturday, 29 October 2011 16:33:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 12:56:01 GMT