Optional@contextOptionalassertionThe 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.
OptionalauthenticationThe 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.
OptionalcapabilityThe 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.
OptionalcapabilityThe 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 DID Subject to which this DID Document pertains.
The id property is REQUIRED and must be a valid DID.
Services are used in DID documents to express ways of communicating with the DID subject or associated entities. A service can be any type of service the DID subject wants to advertise, including decentralized identity management services for further discovery, authentication, authorization, or interaction.
A DID document can express verification methods, such as cryptographic public keys, which can be used to authenticate or authorize interactions with the DID subject or associated parties.
A JSON-LD context link, which provides a JSON-LD processor with the information necessary to interpret the DID document JSON. The default context URL is 'https://www.w3.org/ns/did/v1'.