Re: Fwd: Acceptance of DID DRAFT Specification as a W3C Credentials CG Work Item

On 7/28/17 3:45 PM, Melvin Carvalho wrote:
>
>
> On 26 July 2017 at 03:04, Kingsley Idehen <kidehen@openlinksw.com
> <mailto:kidehen@openlinksw.com>> wrote:
>
>     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.
>
> It's a good point, but how else to resolve a URI without a natural,
> well deployed dereferencing system?

You mean: How else could you deploy a urn: (what they classify as a
persistent identifier) as the canonical identifier for an identity
system that isn't yet another silo? You can't, because defeats the
entire point of identity controlled by "us" rather than "them"
(providers of infrastructure such as: domains, hosted sites, and the like).

This solution that doesn't let me control my identity (denotation
[WebID] + connotation [WebID-Profile Doc] ) without an intermediary
being forced upon me, so it shouldn't really be pitching itself as such
(IMHO). Using a Blockchain-based ledger doesn't negate this fundamental
fact.

>
> WebID has a big advantage in this sense, in that it can be used with
> "follow your nose"

Yes, but I would describe that as simply being native to the abstraction
that is the Web (i.e., the HTTP URI abstraction that subsumes DNS).

>
> However, what about the idea of many services having a well-known area
> to look up such identifiers, it may become populated enough to offer a
> decent, relatively domain independent lookup service, over time?

That doesn't negate the fundamental contradiction regarding any protocol
that depends solely on ".well-known" for resolver implementation.

For the DID folks:

[1] https://www.w3.org/2005/Talks/1110-iswc-tbl/#(7) -- A single slide
that reminds everyone why HTTP URIs are identifiers are so powerful
[2]
http://kidehen.blogspot.com/2014/03/linked-data-deployment-tutorial.html
-- simple Linked Data deployment Tutorial


Kingsley
>
>     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
>     <https://tools.ietf.org/html/rfc5785>
>
>     [2] https://opencreds.github.io/did-spec/#did-resolvers
>     <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/
>     <http://www.openlinksw.com/blog/%7Ekidehen/>
>     Blogspot Blog: http://kidehen.blogspot.com
>     Medium Blog: https://medium.com/@kidehen
>
>     Profile Pages:
>     Pinterest: https://www.pinterest.com/kidehen/
>     <https://www.pinterest.com/kidehen/>
>     Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
>     <https://www.quora.com/profile/Kingsley-Uyi-Idehen>
>     Twitter: https://twitter.com/kidehen
>     Google+: https://plus.google.com/+KingsleyIdehen/about
>     <https://plus.google.com/+KingsleyIdehen/about>
>     LinkedIn: http://www.linkedin.com/in/kidehen
>     <http://www.linkedin.com/in/kidehen>
>
>     Web Identities (WebID):
>     Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
>     <http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i>
>             : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
>     <http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this>
>
>

-- 
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