Re: Software maturity?

I think the registry would benefit from some kind of evaluation... and from
a test suite score.

regarding prototyping:

I would recommend did:web for prototyping... why?

1. Easy to update the DID Document with experimental features
2. Works with existing infrastructure
3. Readable names not random strings (not good for privacy but good for
testing).
4. Very simple implementation, no blockchain or decentralized storage needed

Here are some resources for did:web

Open source resolver (uses HTTP 302, no fancy document processing):
https://did-web.web.app/
Example hosting multiple did documents in a single github repo:
https://did.actor/

Next step I would recommend did:key... why?

1. Simple deterministic transformation of key material to did document data
model
2. Works offline
3. looks / feels like a ledger based did method
4. does not support update / deactivate (depending on your use case, this
might disqualify did:key)

Next step consider a ledger based did method... why?

1. use block explorers to show that your DID lives on a "real decentralized
system"
2. blockchains are slow and expensive


OS

On Tue, Apr 28, 2020 at 3:37 AM Dan Bolser <dan@geromics.co.uk> wrote:

> Just in case it helps, this is what I meant:
> https://en.wikipedia.org/wiki/Technology_readiness_level
>
> I realise this rapidly gets political, however, it should be approximately
> objective...
>
> Would there be space in the registry for a TRL column? I'd be happy to
> help evaluate (although most projects should evaluate themselves).
>
>
> Many thanks,
> Dan.
>
> On Mon, 27 Apr 2020 at 15:33, Dan Bolser <dan@geromics.co.uk> wrote:
>
>> Hi,
>>
>> I found 'the DID registry', but I'm struggling to decide which
>> implementation to prototype with. Has anyone applied the software readiness
>> levels (or similar concepts) to those projects?
>>
>> Any suggestions very welcome!
>>
>>
>> Dan.
>>
>

-- 
*ORIE STEELE*
Chief Technical Officer
www.transmute.industries

<https://www.transmute.industries>