W3C home > Mailing lists > Public > public-webid@w3.org > October 2012

Re: [saag] Liking Linkability

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Wed, 24 Oct 2012 13:51:07 -0400
Message-ID: <50882A8B.3040609@openlinksw.com>
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
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/

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 .



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

Received on Wednesday, 24 October 2012 17:51:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:05:44 UTC