On 12/14/12 10:54 AM, Melvin Carvalho wrote:
On 14 December 2012 15:39, Kingsley Idehen <[email protected] <mailto:[email protected]>> wrote:On 12/14/12 8:08 AM, Melvin Carvalho wrote:On 13 December 2012 21:19, Kingsley Idehen <[email protected] <mailto:[email protected]>> wrote: All, Experiment t Steps: 1. Attempt to lookup the following resource URL: http://web.ods.openlinksw.com/~kidehen/bing-snapshot-picasso.png <http://web.ods.openlinksw.com/%7Ekidehen/bing-snapshot-picasso.png> 2. Send me you preferred identifier (a URI displayed in the profile UI under "Connected Accounts") 3. **Optionally** open up an account via <http://web.ods.openlinksw.com> <http://web.ods.openlinksw.com> -- using whatever identification and authentication service works best for you (note: the profile UI has a "connected accounts" tab which will expose URIs to you re. next step) 4. I'll then add the URI to the ACL protecting the resource -- again, you don't really need to sign up for a new account to complete this step, I just need an identifier aligned with an authentication service 5. I'll reply indicating you have access 6. Done. Note, these steps can (and will be) streamlined using notifications services such that you end up with a variant of Juergen's example which I posted about at: https://plus.google.com/u/0/112399767740508618350/posts/MVEcEkY6ZCz . Without Web- and Internet-scale Linked Data this simply would be achievable, without opening up yet another artificial silo. Works for me with twitter and personaGreat! Anyone else? All: Basically, all you really have to do is just let me (the resource owner) know how you want to be identified. Examples would include: 1. Twitter -- http://twitter.com/<userid> e.g., http://twitter.com/kidehen 2. LinkedIn -- http://www.linkedin.com/in/<userid> e.g., http://www.linkedin.com/in/kidehen 3. Facebook -- http://www.facebook.com/<userid> e.g., https://www.facebook.com/kidehen 4. etc.. Basically, each of these social networking/media service providers mints a verifiable URI for its members. In many cases, these days, you can verify these URIs by testing for control over said URIs using protocols such as OpenID, OAuth etc.. Naturally, you can also leverage WebID and its WebID+TLS authentication protocol in the same manner, just by sharing your WebID with the resource owner (me). Remember, this is a "deceptively simple" example of the power of Linked Data applied to the following problems: 1. verifiable identity 2. resource access authorization . Also note, we are going to be releasing this Javascript control as part of our ODS social web framework project on Github.Awesome! I would definitely like to use something like this in my apps for login.For anyone that hasnt tried it yet, I'd encourage you to give it a go. You just need an account with any of:WebID Persona OpenID Facebook Twitter LinkedIn Google Windows Live Wordpress Yahoo Tumblr Disqus Instragram Bitly Foursquare DropboxThen click: http://web.ods.openlinksw.com/~kidehen/bing-snapshot-picasso.png <http://web.ods.openlinksw.com/%7Ekidehen/bing-snapshot-picasso.png>Do let us know if it works! :)
Also note, we can add any OAuth supporting service that's missing from the list above. Naturally, when the framework is released, you will be able to extend the list yourself.
-- Regards, Kingsley Idehen Founder & 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
smime.p7s
Description: S/MIME Cryptographic Signature
