Re: Webkeys, OpenID, WebID, OAuth etc..

On 5/6/13 1:53 PM, Manu Sporny wrote:
> On 04/22/2013 09:42 AM, Kingsley Idehen wrote:
>> On 4/21/13 10:30 PM, Manu Sporny wrote:
>>>>> Keys *can* have URLs as per the cert ontology.  They can be blank
>>>>> nodes too, which I think is currently more common.  I use a URL.
>>> It's Linked Data, you *can* do anything. The question here is MUST. In
>>> Web Keys, keys MUST have a URL. That requirement makes it so that you
>>> can depend on that URL when verifying digital signatures.
>> Do you have an example of a 5-star Linked Data URI that denotes a public
>> key?
> curl "https://dev.payswarm.com/i/manu/keys/4"
>
> -- manu
>
>

See:

1. 
http://linkeddata.uriburner.com:8000/vapour?uri=https%3A%2F%2Fdev.payswarm.com%2Fi%2Fmanu%2Fkeys%2F4&defaultResponse=dontmind&userAgent=vapour.sourceforge.net 
-- yours

2. 
http://linkeddata.uriburner.com:8000/vapour?uri=http%3A%2F%2Fid.myopenlink.net%2Fcertgen%2Fkey%2F497&validateRDF=1&defaultResponse=dontmind&userAgent=vapour.sourceforge.net 
-- one of mine

Both URIs are supposed to denote public keys.

Links:

1. http://bit.ly/P0HVdI -- post about benefits of denoting Public Keys 
using Linked Data URIs.



-- 

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