The discussion almost entirely appears to be Identity-focused in the context of people and organizations. These Identity classes are in fact infinitesimally small compared to all of the other types of Identity classes: e.g. business documents, NFTs, etc. More of the latter are exchanged in a single day than the size of the entire Earthly population.
This misfocus greatly skews the expectations of of DID Methods like did: object and what is expected to appear in the Privacy Considerations section of the Method specification.
A Method specification is nothing more than the definition of a namespace for organizing a family of Decentralized Identifiers and defining an abstract interface for managing the lifecycle of DID Identifiers and their associated DID Documents (the associated CRUD operations). Anything more is overkill and unnecessary IMO.
Reference: https://www.w3.org/TR/did-imp-guide/
The discussion almost entirely appears to be Identity-focused in the context of people and organizations. These Identity classes are in fact infinitesimally small compared to all of the other types of Identity classes: e.g. business documents, NFTs, etc. More of the latter are exchanged in a single day than the size of the entire Earthly population.
This misfocus greatly skews the expectations of of DID Methods like
did: objectand what is expected to appear in the Privacy Considerations section of the Method specification.A Method specification is nothing more than the definition of a namespace for organizing a family of Decentralized Identifiers and defining an abstract interface for managing the lifecycle of DID Identifiers and their associated DID Documents (the associated CRUD operations). Anything more is overkill and unnecessary IMO.