- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 24 Feb 2014 08:25:50 -0500
- To: public-fedsocweb@w3.org, Web Payments CG <public-webpayments@w3.org>
- Message-ID: <530B485E.6040405@openlinksw.com>
On 2/24/14 7:23 AM, Manu Sporny wrote: > On 02/24/2014 04:27 AM, Andreas Kuckartz wrote: >> >The Web Identity specification which is being developed by the W3C >> >Web Payments CG seems to be interesting for the Social Web >> >communities as well: >> > >> >Web Identity 1.0 Draft Community Group Specification 21 February 2014 >> >https://web-payments.org/specs/source/web-identity > Keep in mind that the spec name is a pretty terrible one, we're trying > to come up with a better one like "Identity Assertions" (bad) "Entity > Assertions" (bad) or "Web Assertions" (meh). > > The spec focuses on asserting statements about a particular entity like: > > This is my name. > > This is my government issued identification information. > > This is an assertion by my local government of my home address. > > It's also aligned with the Activity Streams 2.0 work (one of your input > documents for the Social Web WG) since they're using JSON-LD as well. > > The identity assertions spec adds simple digital signatures to the > information above as well as a read/write capability to identity URLs. > Manu, The attributes you've outlined above constitute Identification, based on verifiable Identity. Thus, you are referring to a Web Identification spec whereby a collection of Identity Claims (as you've listed above) are used as the basis for verifiable Identification of an entity denoted by an Identifier. [1] http://id.myopenlink.net/public_home/KingsleyUyiIdehen/Public/YouID/IDcard_Google_140220_175342/140220_175342_profile.ttl#identity -- HTTP URI that denotes by G+ Persona [2] http://id.myopenlink.net/public_home/KingsleyUyiIdehen/Public/YouID/IDcard_Google_140220_175342/index.html -- HTML based Identity Card for G+ Persona (note: this also exists in Turtle, JSON-LD, RDFa, and Microformats formats, and exposure is via a plethora of discovery patterns that includes use of <link/> relations in <head/>) [3] http://t.co/om6TdD9pRr -- Linked Data principles adherence verification of the personal URI (that denotes my G+ persona) used in my Identity Card (JSON-LD document) claims [4] http://t.co/hCGmKSho1j -- Ditto, but using a Turtle based Identity Card [5] http://bit.ly/1piuOsl -- Identity Claims verification using WebID+TLS protocol (of course, this could be another protocol since personal URIs and authentication protocols MUST be loosely coupled) . Note, the following are loosely coupled: 1. Web Identity spec -- this is just about entity denotation e.g., a WebID (which is just an HTTP URI used to denote entities of type: foaf:Agent) 2. Web Identification -- this covers identity claims associated with a WebID (for instance) or other Identifiers (e.g., those supported by OAuth) 3. Web Identification Verification -- this would be about protocols for verifying identity claims. Links: [1] http://bit.ly/1elKLcn -- WebID [2] http://bit.ly/1bD2eZs -- Identifier . -- 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 Monday, 24 February 2014 13:26:15 UTC