- From: Reed, Drummond <drummond.reed@avast.com>
- Date: Fri, 4 Mar 2022 13:36:03 -0800
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: public-did-wg@w3.org
- Message-ID: <CAD-FoVSi1LM0gFDTx-Pehn0d64W-VBzQ7MoTrt9gFCC-fFVgdA@mail.gmail.com>
And I want to +1 Manu's +1. After reading this thread, it appears you are seeking exactly the same solution the Indy community came up with for Indy-compatible ledger: *did:indy:[network]:[subnet]:[method-specific-id]* Just replace "indy" with the name of your DID method that the community as a whole can agree upon. =Drummond On Fri, Feb 18, 2022 at 6:06 AM Manu Sporny <msporny@digitalbazaar.com> wrote: > On 2/18/22 3:45 AM, Markus Sabadello wrote: > > if the difference between "zones" is mostly governance, and the > underlying > > technology is essentially the same, then again I don't think there should > > be separate DID methods. > > I just wanted to +1 the advice that Markus and Daniel are providing. It > really > does sound like the protocol is the exact same between all these different > networks, which indicates that you are dealing with one DID Method, not > hundreds of them. > > I'll also note that if you were to start attempting to register tens to > hundreds of DID Methods that we would most likely change the registration > rules for the registry so that such unsustainable use of the registry would > come to an end. > > Unless you can show us how these "zones" differ in significant ways from a > protocol perspective, you are almost certainly talking about a single DID > Method (that is capable of addressing multiple networks running the same > protocol). > > -- manu > > -- > Manu Sporny - https://www.linkedin.com/in/manusporny/ > Founder/CEO - Digital Bazaar, Inc. > News: Digital Bazaar Announces New Case Studies (2021) > https://www.digitalbazaar.com/ > > >
Received on Saturday, 5 March 2022 13:18:03 UTC