Re: Implementation required for DID Method registration?

+1 to Manu's idea of having some barrier of entry to distinguish between
the different DID methods and +1 to Markus' additions to this definition
around a method remaining provisional until it's made compliant with the
DID test suite.

On Sat, May 8, 2021 at 3:57 AM Markus Sabadello <markus@danubetech.com>
wrote:

> I like the idea of PROVISIONAL and IMPLEMENTED.
>
> PROVISIONAL: You have a specification, but you either have no
> implementation, or an implementation that is not (yet) compliant with
> DID Core 1.0.
>
> IMPLEMENTED: You have a specification and implementation that is
> compliant with DID Core 1.0, and you have submitted an implementation
> report to the DID test suite.
>
> Markus
>
> On 07.05.21 14:18, Manu Sporny wrote:
> > Should we require DID Method implementations to have an implementation
> in the
> > DID test suite to register the DID Method?
> >
> > Should we mark DID Method implementations as "IMPLEMENTED", instead of
> > "PROVISIONAL" if they have a test in the test suite?
> >
> > I'm trying to figure out how we incentivize people to demonstrate that
> they
> > did more than just throwing some ideas down in a markdown file for their
> DID
> > Method... as in, they actually implemented something...
> >
> > So, the states would be at least: "PROVISIONAL" and "IMPLEMENTED". Both
> have
> > objective tests. "PROVISIONAL" is "you have a spec that meets all the DID
> > Method requirements", and "IMPLEMENTED" is "you submitted an
> implementation to
> > the did-test-suite that demonstrates conformance to the DID Core
> specification".
> >
> > Thoughts?
> >
> > -- manu
> >
>
>
>

-- 
This communication, including any attachments, is confidential. If you are 
not the intended recipient, you should not read it - please contact me 
immediately, destroy it, and do not copy or use any part of this 
communication or disclose anything about it. Thank you. Please note that 
this communication does not designate an information system for the 
purposes of the Electronic Transactions Act 2002.