- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Sun, 13 Apr 2014 16:34:16 -0400
- To: public-vocabs@w3.org
- Message-ID: <534AF4C8.30207@openlinksw.com>
On 4/12/14 4:37 PM, Wes Turner wrote: > That would be outstanding. This does seem a bit of an OT rider > (sorry!), but schema:(Person|Organization).webid -> schema:webid -> > schema:webkey ... > > Use case: > > A (package or commit of a release of a) SoftwareApplication (release, > package) is signed with a Person or Organization's webkey; which is > hosted by a network. > > Further discussion (in re: SoftwareApplication) may be more > appropriate at: > http://lists.w3.org/Archives/Public/public-vocabs/2014Apr/0177.html In addition to a schema:webkey based relation that has a public key (in typed literal form) as its object. You can also have a schema:webkeyURL based relation which has a public key document URL as its object. Why is this useful? It enables an agent de-reference a public key in a variety of public key formats, thus just by knowing your schema:webid an agent can ultimately de-reference your public key. Typical use case? Setting up ssh access for someone or some software agent [1]. Links: [1] http://bit.ly/P0HVdI -- post that showcases (via example) the virtues of denoting a public key with an HTTP URI. Kingsley > > On 4/12/14, Kingsley Idehen<kidehen@openlinksw.com> wrote: >> >On 4/12/14 1:43 PM, Wes Turner wrote: >>> >>re: schema:webid : >>> >> >>>>> >>> >Effect: >>>>> >>> > >>>>> >>> >It just works! Entity disambiguation is in place, data consumers >>>>> >>> >(subject to their mindset: structured data, linked data, semantic web) >>>>> >>> >can all work with this without any disruption or "world view" warfare >>>>> >>> >triggers. >>>>> >>> > >>>>> >>> >Why does it just work? >>>>> >>> > >>>>> >>> >1. A webid or WebID is an HTTP URI that denotes an Agent (note: this has >>>>> >>> >nothing to do with the WebID+TLS authentication protocol, this is >>>>> >>> >simply about entity denotation, where the entity in question is an >>>>> >>> >Agent i.e., person, organization, or bot) >>>>> >>> > >>>>> >>> >2. Using the fragment identifier implies no entity URI disambiguation >>>>> >>> >heuristics. >>>>> >>> > >>>>> >>> >Conclusion: >>>>> >>> > >>>>> >>> ><http://schema.org/webid> is a non disruptive relationship property for >>>>> >>> >this kind of relation i.e., one that associates an entity with its >>>>> >>> >description document (descriptor), implicitly . >>> >>I would say +1 for 'schema:webid', but then how can I link to my >>> >>Keybase.io? >>> >> >> > >> >schema:webkey "{your-public-key}" . >> > >> >Basically, schema:webkey would be a relation for association with public >> >keys . -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Sunday, 13 April 2014 20:34:38 UTC