- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Fri, 12 Jun 2020 09:08:30 -0400
- To: public-credentials@w3.org
On 6/12/20 8:28 AM, Dan Bolser wrote: > Just reading this: > https://w3c-ccg.github.io/did-method-key/ > > Which looks nice, but I don't understand how resolution from DID to DID > doc happens. > > The creation of a DID Document is also performed by taking the > public key value and expanding it into DID Document Hi Dan, I'm one of the Editors for that specification. I'm going to attempt to answer your questions below: > Ah... is the DID doc just a version of the key in a different format? Yes, more or less. The DID Document is deterministically generated from the DID. The goal of did:key is to be THE simplest and easiest to implement DID Method. > e.g. no other fields except those directly derived from the key are allowed? Yes. > Sorry if that's obvious (sorry if this is a dumb question). No dumb questions... and this is a very good question and gets to the heart of what did:key is about. > In this sense it's essentially a 'mock' or 'placeholder' DID document? I wouldn't say it's a 'mock' or 'placeholder' DID document. It is a bonafide DID Document that can be used in production systems that don't require key rotation. For example, very useful in test environments and systems that use short lived DIDs (throw-away pairwise relationships, etc.). -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. blog: Veres One Decentralized Identifier Blockchain Launches https://tinyurl.com/veres-one-launches
Received on Friday, 12 June 2020 13:08:45 UTC