DIDDocument
https://w3c.github.io/did-core/#did-document-properties
https://github.com/w3c/?q=did&type=all&language=&sort=
- authentication -> challenge-response protocol
- assertionMethod -> Issuer key (for purposes of issuing a Verifiable Credential)
- keyAgreement -> tablishing a secure communication channel with the recipient
- capabilityInvocation -> Master key (for authorization to update the DID Document.)
- capabilityDelegation -> ...
Attributes
- Companion
- object
- Graph
-
- Supertypes
- Known subtypes
-
class DIDDocumentClass
Members list
Value members
Abstract methods
The assertionMethod verification relationship is used to specify how the DID subject is expected to express claims, such as for the purposes of issuing a Verifiable Credential [VC-DATA-MODEL].
The assertionMethod verification relationship is used to specify how the DID subject is expected to express claims, such as for the purposes of issuing a Verifiable Credential [VC-DATA-MODEL].
Attributes
- See also
Keys declared in this section are used to signed JWM.
Keys declared in this section are used to signed JWM.
The authentication verification relationship is used to specify how the DID subject is expected to be authenticated, for purposes such as logging into a website or engaging in any sort of challenge-response protocol.
Attributes
- See also
The capabilityDelegation verification relationship is used to specify a mechanism that might be used by the DID subject to delegate a cryptographic capability to another party, such as delegating the authority to access a specific HTTP API to a subordinate.
The capabilityDelegation verification relationship is used to specify a mechanism that might be used by the DID subject to delegate a cryptographic capability to another party, such as delegating the authority to access a specific HTTP API to a subordinate.
Attributes
- See also
The capabilityInvocation verification relationship is used to specify a verification method that might be used by the DID subject to invoke a cryptographic capability, such as the authorization to update the DID Document.
The capabilityInvocation verification relationship is used to specify a verification method that might be used by the DID subject to invoke a cryptographic capability, such as the authorization to update the DID Document.
Attributes
- See also
Keys declared in this section are used as target keys when encrypting a message.
Keys declared in this section are used as target keys when encrypting a message.
The keyAgreement verification relationship is used to specify how an entity can generate encryption material in order to transmit confidential information intended for the DID subject, such as for the purposes of establishing a secure communication channel with the recipient.
Attributes
- See also
Attributes
- See also
-
https://www.w3.org/TR/did-core/#verification-methods The VerificationMethod MUST be embedded (can be a reference to another VerificationMethod)
Concrete methods
Keys for Encrypting Messages
Keys for Encrypting Messages
Attributes
Keys for Signing Messages
Keys for Signing Messages
Attributes
Inherited methods
Attributes
- Inherited from:
- DID