- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Wed, 24 Oct 2012 14:55:29 -0400
- To: Henry Story <henry.story@bblfish.net>
- CC: Melvin Carvalho <melvincarvalho@gmail.com>, Robin Wilton <wilton@isoc.org>, Ben Laurie <benl@google.com>, public-identity@w3.org, public-webid@w3.org
- Message-ID: <508839A1.50609@openlinksw.com>
On 10/24/12 2:16 PM, Henry Story wrote: > > On 24 Oct 2012, at 19:51, Kingsley Idehen <kidehen@openlinksw.com > <mailto:kidehen@openlinksw.com>> wrote: > >> On 10/24/12 11:20 AM, Henry Story wrote: >>> >>> On 24 Oct 2012, at 17:09, Melvin Carvalho <melvincarvalho@gmail.com >>> <mailto:melvincarvalho@gmail.com>> wrote: >>> >>>> >>>> - webfinger does indeed give a method to dereference a mailto: >>>> uri, which could be used for a WebID protocol. >>>> >>>> >>>> the current draft of webfinger allows dereferencing a mailto: URI >>>> ... in fact it is anyURI >>> >>> WebFinger is a dereferencing protocol, but not an authentication >>> protocol, and as such it could possibly be used with WebID over TLS. >>> >>> Henry >>> >>> Social Web Architect >>> http://bblfish.net/ >>> >> Henry, >> >> We already use it with acct: or mailto: scheme URIs that serve as >> WebIDs in our implementation of the WebID Authentication Protocol >> (WAP). Basically, these URIs resolve to entity-attribute-value graphs >> expressed in XRD or JRD format which we then transform into RDF >> graphs. The aforementioned transformation adds the requisite entity >> relationship semantics required for WAP conformance. >> >> This simply requires implementers to take responsibility for the >> following: >> >> 1. Webfinger protocol incorporation for URI resolution >> 2. RDF graph generation from XRD or JRD resources . > > yes, that is something we can work on adding to the spec. But that is > work by itself, and we need > more people to implement it. Yes, but all we need to do is acknowledge the pathway that exists for those who are conversant with Webfinger and JRD or XRD descriptor resources. > We are just about getting to the point where people are implementing > the current spec correctly, and the spec itself still needs work. This isn't about the folks working on the spec right now, it's about enabling others to understand we are open to a variety of contributor and collaborator profiles etc.. > > I think this is somehting we can discuss a road map for at TPAC. Being officially open and engaging should be intrinsic to this endeavor :-) Kingsley > >> >> -- >> >> Regards, >> >> Kingsley Idehen >> Founder & CEO >> OpenLink Software >> Company Web:http://www.openlinksw.com >> Personal Weblog:http://www.openlinksw.com/blog/~kidehen >> Twitter/Identi.ca <http://Identi.ca> handle: @kidehen >> Google+ Profile:https://plus.google.com/112399767740508618350/about >> LinkedIn Profile:http://www.linkedin.com/in/kidehen >> >> >> >> > > Social Web Architect > http://bblfish.net/ > -- 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
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Wednesday, 24 October 2012 18:55:54 UTC