To use a DID with a particular distributed ledger or network requires defining a DID method in a separate DID method specification. A DID method specifies the set of rules for how a DID is registered, resolved, updated, and revoked on that specific ledger or network.
DID method and DID method specification are used before they are defined. I believe these are important terms and by not defining them before first use, it creates an unacceptable cognitive load on the first time reader. #confuding
RE: "how a DID is registered, resolved, ..." I believe this statement is neither accurate or precise. After all, a DID is just a character string whose role is to act as an identifier. Isn't more correct to say the DID Document (or DID Entity) "is registered, resolved, updated, and revoked on that specific ledger or network? ...I think so.
Needs to be reworded/clarified. Need to formalize the concept of DID Entity I believe. For example,
In https://w3c-ccg.github.io/did-spec/#overview, it states
DID method and DID method specification are used before they are defined. I believe these are important terms and by not defining them before first use, it creates an unacceptable cognitive load on the first time reader. #confuding
RE: "how a DID is registered, resolved, ..." I believe this statement is neither accurate or precise. After all, a DID is just a character string whose role is to act as an identifier. Isn't more correct to say the DID Document (or DID Entity) "is registered, resolved, updated, and revoked on that specific ledger or network? ...I think so.
Needs to be reworded/clarified. Need to formalize the concept of DID Entity I believe. For example,
Hyperledger Indy/Sovrin Comprehensive Architecture Reference Model (INDY ARM) - latest version - bullets (12) thru (16) in both the diagram, Narration, and principles.