From 70f1a954b6f3e645456460d458c0fb1289d89f36 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Thu, 18 Feb 2021 21:22:26 -0500 Subject: [PATCH] Implement Data Model / Resolution serialization mechanisms. --- index.html | 46 ++++++++++++++++++++++------------------------ 1 file changed, 22 insertions(+), 24 deletions(-) diff --git a/index.html b/index.html index af7216fd..fd88965f 100644 --- a/index.html +++ b/index.html @@ -988,7 +988,7 @@

DID Parameters

A relative URI reference according to RFC3986 Section 4.2 that identifies a resource at a service endpoint, which is selected from a DID -document by using the service parameter. +document by using the service parameter. If present, the associated value MUST be an ASCII string and MUST use percent-encoding for certain characters as specified in RFC3986 @@ -1028,7 +1028,7 @@

DID Parameters

A resource hash of the DID document to add integrity protection, as -specified in [[?HASHLINK]]. This parameter is non-normative. +specified in [[?HASHLINK]]. This parameter is non-normative. If present, the associated value MUST be an ASCII string. @@ -1134,10 +1134,10 @@

Relative DID URLs

Data Model

This specification defines a data model that can be used to express DID -documents and other data structures that can then be serialized into -multiple concrete representations. This section provides a high-level -description of the data model, how different types of properties are expressed -in the data model, and instructions for extending the data model. +documents and DID document data structures, which can then be serialized +into multiple concrete representations. This section provides a +high-level description of the data model, how different types of properties are +expressed in the data model, and instructions for extending the data model.

A DID document consists of a map of Data Model -

-Other data structures that are not DID documents can also use the data -model and representations to express information. An example of this -is elaborated upon in . -

-

As a result of the data model being defined using terminology from [[INFRA]], property values which can contain more than one @@ -2618,10 +2612,10 @@

Production

All implementers creating conforming producers that produce JSON representations are advised to ensure that their algorithms are aligned -with the JSON serialization rules in the [[INFRA]] -specification and the -precision advisements regarding Numbers -in the JSON [[RFC7159]] specification. +with the JSON +serialization rules in the [[INFRA]] specification and the precision advisements regarding Numbers in the +JSON [[RFC7159]] specification.

@@ -2767,7 +2761,7 @@

Consumption

All implementers creating conforming consumers that produce JSON representations are advised to ensure that their algorithms are aligned with the JSON +data-cite="INFRA#parse-json-bytes-to-an-infra-value">JSON conversion rules in the [[INFRA]] specification and the precision advisements regarding Numbers in the JSON [[RFC7159]] specification. @@ -2944,9 +2938,9 @@

CBOR

Production

-All DID document data structures expressed by the data model -MUST be serialized to the CBOR representation according to the -following production rules: +The DID document and any DID document data structures expressed by the data model MUST be serialized to the CBOR +representation according to the following production rules:

@@ -3132,9 +3126,10 @@

Production

Consumption

-All data structures expressed by a CBOR representation MUST be -deserialized into the data model according to the -following consumption rules: +The DID document and any DID document data structures expressed by the data model MUST be deserialized into the data model according to the following consumption +rules:

@@ -4166,7 +4161,10 @@

Metadata Structure

additional formats or restrictions to that value (for example, a string formatted as a date or as a decimal integer). It is RECOMMENDED that property definitions use strings for values. The entire metadata structure MUST be -serializable in a conforming representation. +serializable according to the JSON +serialization rules in the [[INFRA]] specification. Implementations MAY +serialize the metadata structure to other data formats.