Re: LinkedIn, Twitter, Facebook etc.. as WebID IdPs

Ok do you are enabling the oauth consumer Site to obtain the client api credentials accessing  the users store in facebookland, and then said "plugin" to Facebook adds some value. This is accomplished by minting a cert with the uri of the Facebook users data space as webid. Finally, using its write privilege on the remote store, the cert is written to the Facebook-graph by the plugin trusted by the user for such function, assuming one trust Facebook.

Webid-like validation agent interact with Facebook idp subsequently, enabling a user to induce said site to get read privs on the users graph, via the api. Using the API, said sites determines if the client cert from https is present in the users Facebook graph, identified by webid in the https client cert.

It's a webid. It's not webid protocol. It's what I'd expect webid research models for ideal protocols to evolve into, during Productization. It's a variation of what I proposed once - just see if the cert blob is present at the uri. It's a nicer variant as the oAuth process enables consent. And audience controls.

Presumably, the data store can store blobs too, iincluding rdf/XML blobs.

It reminds md of the original xri vision, and it's data service (storing 4tuple graphs, with arcs bring xri structured names). Much simpler (and real, of course).

Works with actual web.

Sent from my iPhone

On Nov 18, 2011, at 1:30 PM, "Kingsley Idehen" <kidehen@openlinksw.com> wrote:

> All,
> 
> A quick FYI. We now have proxy/wrapper Linked Data URIs in SANs re. x.509 certificates produced by our HTML based certificate generator [1]. Thus, if you follow the directions from my earlier post [2], you now have an option (via the Wizard UI) for using proxy/wrapper URIs as WebID watermarks in x.509 certificates.
> 
> The proxy/wrapper URIs we generate basically work with existing WebID clients (from others) without modification. We've used proxy/wrapper URIs as a layer of abstraction that shields others from the complexity of implementing data access drivers for Web 2.0 APIs.
> 
> Links:
> 
> 1. http://id.myopenlink.net/certgen -- first cut (beautification to come) HTML based certificate generator which as has native Windows and iOS5 counterparts nearing completion
> 
> 2. http://goo.gl/AcYWQ -- original post about leveraging Facebook as a WebID compliant IdP (follow the steps here, but choose *proxy URI* option )
> 
> 3. http://id.myopenlink.net/ods/webid_demo.html -- simple WebID verification service
> 
> 4. http://id.myopenlink.net/about/id/entity/http/www.linkedin.com/in/kidehen#this -- proxy/wrapper Linked Data URI example (note the footer section re. supported formats which you can negotiate via HTTP or discover via "Link:" response headers or <link/> entries in <head/> in HTML)
> 
> 5. http://goo.gl/krOAV -- alternative HTML view (useful for deeper follow-your-nose navigation)
> 
> 6. http://id.myopenlink.net/describe/?url=http%3A%2F%2Fwww.openlinksw.com%2Fschemas%2Fcert%23Certificate -- shows how we've extended the WOT ontology in our own data space (follow-your-nose to see unobtrusive nature of this approach) .
> 
> -- 
> 
> 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 Friday, 18 November 2011 22:53:12 UTC