- From: Dan Bolser <dan@geromics.co.uk>
- Date: Thu, 18 Jun 2020 11:20:51 +0100
- To: dzagidulin@gmail.com
- Cc: W3C DID Working Group <public-did-wg@w3.org>
- Message-ID: <CANQ+bf4k4q9YEJaZBq4wP_HC2ptFAgE-gtUSWs6s4GPBd0i7Tg@mail.gmail.com>
Sorry, this is the correct URL: https://cryptpad.fr/pad/#/2/pad/edit/FIfjWl77ZgmGiO8Jd-rlu+Is/ On Thu, 18 Jun 2020 at 11:15, Dan Bolser <dan@geromics.co.uk> wrote: > To keep momentum, I've put some 'rough notes' here: > https://cryptpad.fr/pad/#/3/pad/edit/7bb4c36d5a9729a66d6e66fa56e76d9b/ > > Please feel free to add comments / suggestions / feedback there. > > > Cheers, > > > On Thu, 21 May 2020 at 16:48, Dan Bolser <dan@geromics.co.uk> wrote: > >> Thanks both, >> >> Yes, I don't want to duplicate work! >> >> I'll have to read the above in a bit more detail, after which I can build >> a prototype for feedback pretty easily. >> >> Unfortunately, 'seqwiki' (the paper I linked) has been down for a while. >> I'm planning to resurrect it, but user accounts are a lingering issue... >> However, you can look at how it (nearly) works here: >> http://116.203.158.69/wiki/Software >> >> e.g. >> http://116.203.158.69/wiki/Special:BrowseData >> >> >> >> >> >> On Thu, 21 May 2020 at 15:37, Dmitri Zagidulin <dzagidulin@gmail.com> >> wrote: >> >>> Hi Dan, >>> >>> I was thinking of doing the same thing! (Except was still at the phase >>> of pondering which tool stack to use.) MediaWiki is a great idea! >>> As Manu mentions, there IS already the DID Methods Registry. However, it >>> is a static markdown table, and it would be very interesting and useful to >>> actually use a database as a backend. (And to expand the fields used for >>> tracking and classifying the methods.) >>> >>> Here are the fields I would like to see, to start with: >>> >>> (Fields from the DID Registry) >>> * Method name >>> * Link to method spec >>> * Authors >>> * (Spec) Status (provisional/deprecated etc) >>> * Persistence mechanism (DLT or Network column) >>> >>> Other fields: >>> * Broad persistence category. (Ledger [public permissionless, public >>> permissioned, private, etc] vs DHT vs Local/Peer vs Other). >>> * Number of implementations >>> * DID Core features supported (proof purposes, service endpoints, etc) >>> * Other / custom features supported >>> * Key algorithms supported (ed25519, rsa, etc) >>> * Cost of DID Document creation/registering >>> * Cost of DID Document update (key rotation etc) >>> >>> In addition, I think it would be interesting to go through the >>> (forthcoming) DID Method Rubrics >>> <https://docs.google.com/document/d/1rYdWiwawWmLOWtHRvT0GzYcdewW_OS9M2mAkENLFdtY/edit> >>> document, to see which fields from there it would make sense to add to the >>> db. >>> >>> On Thu, May 21, 2020 at 10:04 AM Dan Bolser <dan@geromics.co.uk> wrote: >>> >>>> Hi, >>>> >>>> I've been thinking of building a registries database using Semantic >>>> MediaWiki. It's kind of my favorite hammer / toy [1]. >>>> >>>> What fields would people expect to see for a did-method? >>>> >>>> Many thanks, Dan >>>> >>>> [1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3245082/ >>>> >>>
Received on Thursday, 18 June 2020 10:21:17 UTC