- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Tue, 25 Jul 2017 21:04:31 -0400
- To: Melvin Carvalho <melvincarvalho@gmail.com>, public-webid <public-webid@w3.org>, public-rww <public-rww@w3.org>
- Message-ID: <e4eeddad-e1f7-c270-46fb-7562c651debd@openlinksw.com>
On 7/25/17 7:12 PM, Melvin Carvalho wrote:
> FYI: Decentralized Identifiers Specification ...
>
> ---------- Forwarded message ----------
> From: *Christopher Allen* <ChristopherA@blockstream.com
> <mailto:ChristopherA@blockstream.com>>
> Date: 26 July 2017 at 00:20
> Subject: Acceptance of DID DRAFT Specification as a W3C Credentials CG
> Work Item
> To: "W3C Credentials CG (Public List)" <public-credentials@w3.org
> <mailto:public-credentials@w3.org>>
>
>
> At today’s W3C Credentials CG meeting there was unanimous support for
> accepting the DID DRAFT Specification as one of our new work items.
> There were +9 votes for, none against.
>
> The DRAFT spec currently is at:
>
> https://opencreds.github.io/did-spec/
> <https://opencreds.github.io/did-spec/>
>
> The Github repository for this specification is here:
>
> https://github.com/opencreds/did-spec
> <https://github.com/opencreds/did-spec>
>
> The issue tracker is here:
>
> https://github.com/opencreds/did-spec/issues
> <https://github.com/opencreds/did-spec/issues>
>
> These will move if these items are accepted.
>
> If there are no substantive objections to this mailing list before our
> next call on Tuesday August 1st at 12pm ET the chairs will declare
> this draft as officially accepted for additional work by our Community
> Group.
>
> — Christopher Allen
Hi Melvin,
My only concern is that did: scheme URIs depend soley on the
"/.well-known/" pattern [1] for resolver implementation. Net effect,
user's still have to control a domain as part of the quest for
self-management of identity.
An HTTP URI as Agent Identifier (as is already delivered via WebID)
doesn't have this problem, and resolution is implicit (if you leverage #
e.g., #this). In addition, it wouldn't break what they are trying to
achieve (i.e., identity explicitly controlled by individuals rather than
organizations).
My concern is that this is like WebFinger, but using a different URI
scheme i.e., did: as opposed to mailto: .
Links:
[1] https://tools.ietf.org/html/rfc5785
[2] https://opencreds.github.io/did-spec/#did-resolvers -- which says
nothing about "/.well-known/" pattern even though that's the requirement.
--
Regards,
Kingsley Idehen
Founder & CEO
OpenLink Software (Home Page: http://www.openlinksw.com)
Weblogs (Blogs):
Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
Blogspot Blog: http://kidehen.blogspot.com
Medium Blog: https://medium.com/@kidehen
Profile Pages:
Pinterest: https://www.pinterest.com/kidehen/
Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter: https://twitter.com/kidehen
Google+: https://plus.google.com/+KingsleyIdehen/about
LinkedIn: http://www.linkedin.com/in/kidehen
Web Identities (WebID):
Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
: http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Wednesday, 26 July 2017 01:05:29 UTC