Re: DID methods as W3C standards - a happy compromise?

thanks Christopher

will add did:onion to our list of experiments.

Luckily I'm thick-skinned enough to cope with Manu's assertions that I
don't know what I'm talking about.. but I'll persevere because I'm
pretty sure I'm not alone in knowing "enough to be dangerous" and being
keen to improve that knowledge so that I can make better informed
recommendations.  I did get quite a few private responses that went along
the lines of "I'm confused by all these did methods too and your post
really helped". That's nice but does risk a case of the "blind leading the
blind".  So now I feel an increased obligation to expose myself to further
flaying until a reasonably confident consensus emerges...

Also I respect Manu's huge contributions to this space and will always take
his advice seriously...

On Sat, 5 Mar 2022 at 11:36, Christopher Allen <
ChristopherA@lifewithalacrity.com> wrote:

> On Fri, Mar 4, 2022 at 8:27 AM Manu Sporny <msporny@digitalbazaar.com>
> wrote:
>
>> This goes for /every/ DLT-based DID Method out there -- even the one we're
>> working on. I am highly sceptical of anyone that says that /any/ DID
>> Method is
>> ready for production usage at present.
>
>
> Agreed — as one of the proponents of DLTs (in particular permissionless
> public ones) none are mature enough yet for production.
>
> Putting anything other than keys in a DID Document requires careful
>> consideration and thought that I'm not seeing many of these DID Method
>> implementers doing.
>
>
> i absolutely agree with Manu on this. I’m even skeptical of anything
> public in VC or endpoints that might make them even in the slighted
> publicly correlatable.
>
> I think the fundamental flaw in your thinking at present, Steve, is
>> trusting
>> DLT-based DID Methods too early. They are important, and they'll have
>> their
>> day, but not this year... until then, did:key and did:web can carry a lot
>> of
>> water.
>
>
> I’d really to see did:onion added to this list somehow this year.
> Basically functions a lot like did:web but without DNS or certs hierarchy,
> but is permissionless like did:key.
>
> — Christopher Allen
>
>
>

-- 
Steve Capell