Conformance Report

5.1.1 DID Subject - The value of id MUST be a string that conforms to the rules in § 3.1 DID Syntax and MUST exist in the root map of the data model for the DID document.

5.1.2 DID Controller - The controller property is OPTIONAL. If present, the value MUST be a string or an ordered set of strings that conform to the rules in § 3.1 DID Syntax.

5.2 Verification Methods - The verificationMethod property is OPTIONAL. If present, the value MUST be an ordered set of verification methods, where each verification method is expressed using a map.

5.2 Verification Methods - The verification method map MUST include the id, type, controller, and specific verification material properties that are determined by the value of type and are defined in § 5.2.1 Verification Material.

5.2 Verification Methods - The value of the id property for a verification method MUST be a string that conforms to the rules in Section § 3.2 DID URL Syntax.

5.2 Verification Methods - The value of the type property MUST be a string that references exactly one verification method type.

5.2 Verification Methods - The value of the controller property MUST be a string that conforms to the rules in § 3.1 DID Syntax.

5.2 Verification Methods - The publicKeyMultibase property is OPTIONAL. This feature is non-normative. If present, the value MUST be astring representation of a [MULTIBASE] encoded public key.

5.2 Verification Methods - The publicKeyJwk property is OPTIONAL. If present, the value MUST be a map representing a JSON Web Key that conforms to [RFC7517].

5.2 Verification Methods - The map MUST NOT contain "d", or any other members of the private information class as described in Registration Template.

5.2.1 Verification Material - A verification method MUST NOT contain multiple verification material properties for the same material. For example, expressing key material in a verification method using both publicKeyJwk and publicKeyMultibase at the same time is prohibited.

5.3.1 Authentication - The authentication property is OPTIONAL. If present, the associated value MUST be an ordered set of one or more verification methods.

5.3.2 Assertion - The assertionMethod property is OPTIONAL. If present, the associated value MUST be an ordered set of one or more verification methods.

5.3.3 Key Agreement - The keyAgreement property is OPTIONAL. If present, the associated value MUST be an ordered set of one or more verification methods.

5.3.4 Capability Invocation - The capabilityInvocation property is OPTIONAL. If present, the associated value MUST be an ordered set of one or more verification methods.

5.3.5 Capability Delegation - The capabilityDelegation property is OPTIONAL. If present, the associated value MUST be an ordered set of one or more verification methods.

5.4 Services - The service property is OPTIONAL. If present, the associated value MUST be an ordered set of services, where each service is described by a map.

5.4 Services - Each service map MUST contain id, type, and serviceEndpoint properties.

5.4 Services - The value of the id property MUST be a URI conforming to [RFC3986].

5.4 Services - A conforming producer MUST NOT produce multiple service entries with the same id.

5.4 Services - A conforming consumer MUST produce an error if it detects multiple service entries with the same id.

5.4 Services - The value of the type property MUST be a string or an ordered set of strings.

5.4 Services - The value of the serviceEndpoint property MUST be a string, a map, or an ordered set composed of one or more strings and/or maps.

5.4 Services - All [serviceEndpoint] string values MUST be valid URIs conforming to [RFC3986] and normalized according to the Normalization and Comparison rules in RFC3986 and to any normalization rules in its applicable URI scheme specification.

7.3 Metadata Structure - The structure used to communicate this metadata MUST be a map of properties.

7.3 Metadata Structure - Each property name MUST be a string.

7.3 Metadata Structure - Each property value MUST be a string, map, list, ordered set, boolean, or null.

7.3 Metadata Structure - The values within any complex data structures such as maps and lists MUST be one of these data types as well.

7.3 Metadata Structure - The entire metadata structure MUST be serializable according to the JSON serialization rules in the [INFRA] specification.

7.3 Metadata Structure - All metadata property definitions registered in the DID Specification Registries [DID-SPEC-REGISTRIES] MUST define the value type, including any additional formats or restrictions to that value (for example, a string formatted as a date or as a decimal integer).

3.1 DID Syntax - All DIDs MUST conform to the DID Syntax ABNF Rules.

3.2.1 DID Parameters - hl - If present, the associated value MUST be an ASCII string.

3.2.1 DID Parameters - service - If present, the associated value MUST be an ASCII string.

3.2.1 DID Parameters - relativeRef - If present, the associated value MUST be an ASCII string and MUST use percent-encoding for certain characters as specified in RFC3986 Section 2.1.

3.2.1 DID Parameters - versionId - If present, the associated value MUST be an ASCII string.

3.2.1 DID Parameters - versionTime - If present, the associated value MUST be an ASCII string which is a valid XML datetime value, as defined in section 3.3.7 of W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes [XMLSCHEMA11-2]. This datetime value MUST be normalized to UTC 00:00:00 and without sub-second decimal precision. For example: 2020-12-20T19:17:47Z.

6.1 Production and Consumption - A conforming producer MUST take a DID document data model and a representation-specific entries map as input into the production process. The conforming producer MAY accept additional options as input into the production process.

6.1 Production and Consumption - A conforming producer MUST serialize all entries in the DID document data model, and the representation-specific entries map, that do not have explicit processing rules for the representation being produced using only the representation's data type processing rules and return the serialization after the production process completes.

6.1 Production and Consumption - A conforming producer MUST return the Media Type string associated with the representation after the production process completes.

6.1 Production and Consumption - A conforming producer MUST NOT produce non-conforming DIDs or DID documents.

6.2.1 JSON Production - string: A JSON String.

6.2.1 JSON Production - list: A JSON Array, where each element of the list is serialized, in order, as a value of the array according to its type, as defined in this table.

6.2.1 JSON Production - set: A JSON Array, where each element of the set is added, in order, as a value of the array according to its type, as defined in this table.

6.2.1 JSON Production - map: A JSON Object, where each entry is serialized as a member of the JSON Object with the entry key as a JSON String member name and the entry value according to its type, as defined in this table.

6.2.1 JSON Production - datetime: A JSON String serialized as an XML Datetime normalized to UTC 00:00:00 and without sub-second decimal precision.

6.2.1 JSON Production - integer: A JSON Number without a decimal or fractional component.

6.2.1 JSON Production - double: A JSON Number with a decimal and fractional component.

6.2.1 JSON Production - boolean: A JSON Boolean.

6.2.1 JSON Production - null: A JSON null literal.

6.2.1 JSON Production - All entries of a DID document MUST be included in the root JSON Object.

6.2.1 JSON Production - When serializing a DID document, a conforming producer MUST specify a media type of application/did+json to downstream applications such as described in § 7.1.2 DID Resolution Metadata.

6.3.1 JSON-LD Production - The DID document and any DID document data structures expressed by the data model MUST be serialized to the JSON-LD representation according to the JSON representation production rules as defined in § 6.2 JSON.

6.3.1 JSON-LD Production - In addition to using the JSON representation production rules, JSON-LD production MUST include the representation-specific @context entry.

6.3.1 JSON-LD Production - The serialized value of @context MUST be the JSON String https://www.w3.org/ns/did/v1, or a JSON Array where the first item is the JSON String https://www.w3.org/ns/did/v1 and the subsequent items are serialized according to the JSON representation production rules.

6.3.1 JSON-LD Production - When serializing a JSON-LD representation of a DID document, a conforming producer MUST specify a media type of application/did+ld+json to downstream applications such as described in § 7.1.2 DID Resolution Metadata.