DID Document
A set of data that describes a DID, including mechanisms, such as public keys and pseudonymous biometrics, that an entity can use to authenticate itself as the DID.
This is not correct. A DID Document is a set of data that describes a DID Entity. (There may be a better word than "describes".)
More precisely, a DID Document is a JSON-LD serialization of a DID Entity, including mechanisms, such as public keys and pseudonymous biometrics, that an entity can use to authenticate itself as a specific DID Entity.
A DID is simply a character string valued identifier.
In https://w3c-ccg.github.io/did-spec/#terminology, it states...
This is not correct. A DID Document is a set of data that describes a DID Entity. (There may be a better word than "describes".)
More precisely, a DID Document is a JSON-LD serialization of a DID Entity, including mechanisms, such as public keys and pseudonymous biometrics, that an entity can use to authenticate itself as a specific DID Entity.
A DID is simply a character string valued identifier.
Reference: Hyperledger Indy/Sovrin Comprehensive Architecture Reference Model (INDY ARM) - latest version - bullets (12) thru (16) in both the diagram, Narration, and principles.