From 0aa7c41b76f61a8aeef2990b7870c3e2575d0f84 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 3 Jan 2021 14:25:56 -0500
Subject: [PATCH 1/5] Remove ineffective/already tested/untestable MUST
 statements.

---
 index.html | 60 +++++++++++++++++++++++++++---------------------------
 1 file changed, 30 insertions(+), 30 deletions(-)

diff --git a/index.html b/index.html
index 039ad5de..92e8dd17 100644
--- a/index.html
+++ b/index.html
@@ -1108,7 +1108,7 @@ <h2>Relative DID URLs</h2>
 
         <p>
 When resolving a relative DID URL reference, the algorithm specified in <a
-data-cite="RFC3986#section-5">RFC3986 Section 5: Reference Resolution</a>  MUST
+data-cite="RFC3986#section-5">RFC3986 Section 5: Reference Resolution</a> MUST
 be used. The <strong>base URI</strong> value is the <a>DID</a> that is
 associated with the <a>DID subject</a>, see Section <a href="#did-subject"></a>.
 The <strong>scheme</strong> is <code>did</code>. The <strong>authority</strong>
@@ -1809,7 +1809,7 @@ <h3>Verification method types</h3>
 
 
         <p>
-The <a>DID document</a> MUST NOT express revoked keys using a <a>verification
+The <a>DID document</a> does not express revoked keys using a <a>verification
 relationship</a>.
         </p>
         <p>
@@ -1847,9 +1847,9 @@ <h2>Verification Relationships</h2>
       </p>
       <p>
 The <a>verification relationship</a> between the <a>DID subject</a> and the
-<a>verification method</a> MUST be explicit in the <a>DID document</a>.
+<a>verification method</a> is explicit in the <a>DID document</a>.
 <a>Verification methods</a> that are not associated with a particular
-<a>verification relationship</a> MUST NOT be used for that <a>verification
+<a>verification relationship</a> cannot be used for that <a>verification
 relationship</a>. For example, a <a>verification method</a> in the value of
 the <code><a>authentication</a></code> property cannot be used to engage in
 key agreement protocols with the <a>DID subject</a>&mdash;the value of the
@@ -3226,7 +3226,7 @@ <h4>DagCBOR</h4>
 To produce a deterministic canonical CBOR representation of a DID document and
 faciliate maximal lossless compatiblity with other core representations via the
 <a href="#data-model">data model</a> the following constraints of a CBOR
-representation of a DID Document MUST be followed:
+representation are as follows:
           </p>
 
           <ul>
@@ -3265,12 +3265,12 @@ <h4>DagCBOR</h4>
 
           <p>
 When producing and consuming DID Documents representing in DagCBOR the following
-rules MUST be followed:
+rules are followed:
           </p>
 
           <ul>
             <li>
-Use no CBOR tags other than the CID tag (42)
+CBOR tags other than the CID tag (42) MUST NOT be utilized.
             </li>
           </ul>
 
@@ -3608,7 +3608,7 @@ <h1>
     <p>
 All conformant <a>DID resolvers</a> MUST implement the <a>DID resolution</a>
 functions for at least one <a>DID method</a> and MUST be able to return a <a>DID
-document</a> in  at least one conformant representation.
+document</a> in at least one conformant representation.
     </p>
 
     <section>
@@ -3620,7 +3620,7 @@ <h2>
 document</a> by using the "Read" operation of the applicable <a>DID method</a>.
 (See <a href="#read-verify"></a>.) The details of how this process is
 accomplished are outside the scope of this specification, but all conformant
-implementations MUST implement two functions which have the following abstract
+implementations implement two functions which have the following abstract
 forms:
         </p>
 
@@ -3725,8 +3725,8 @@ <h2>
         </dl>
 
         <p>
-<a>DID resolver</a> implementations MUST NOT alter the signature of these
-functions in any way. <a>DID resolver</a> implementations MAY map the
+Conforming <a>DID resolver</a> implementations do not alter the signature of
+these functions in any way. <a>DID resolver</a> implementations MAY map the
 <code>resolve</code> and <code>resolveRepresentation</code> functions to a
 method-specific internal function to perform the actual <a>DID resolution</a>
 process. <a>DID resolver</a> implementations MAY implement  and expose
@@ -3942,7 +3942,7 @@ <h4>equivalentId</h4>
 <code>id</code> property value.
                   </dd>
                   <dd>
-A resolving party MUST retain the values from the <code>id</code> and
+A resolving party is expected to retain the values from the <code>id</code> and
 <code><a>equivalentId</a></code> properties to ensure any subsequent
 interactions with any of the values they contain are correctly handled as
 logically equivalent (e.g. retain all variants in a database so an interaction
@@ -3999,13 +3999,13 @@ <h4>canonicalId</h4>
 <code>id</code> property value.
                   </dd>
                   <dd>
-A resolving party MUST use the <code><a>canonicalId</a></code> value as its
-primary ID value for the DID subject and treat all other equivalent values as
-secondary aliases. (e.g. update corresponding primary references in their
-systems to reflect the new canonical ID directive). <span class="issue">The
-testability of resolving parties is currently under debate and normative
-statements related to resolving parties may be downgraded in the future from a
-MUST to a SHOULD/MAY or similar language.</span>
+A resolving party is expected to use the <code><a>canonicalId</a></code> value
+as its primary ID value for the DID subject and treat all other equivalent
+values as secondary aliases. (e.g. update corresponding primary references in
+their systems to reflect the new canonical ID directive). <span
+class="issue">The testability of resolving parties is currently under debate and
+normative statements related to resolving parties may be downgraded in the
+future from a MUST to a SHOULD/MAY or similar language.</span>
                   </dd>
                 </dl>
 
@@ -4035,7 +4035,7 @@ <h2>
 and fragment. This process depends on <a>DID resolution</a> of the <a>DID</a>
 contained in the <a>DID URL</a>.
 The details of how this process is accomplished are outside the scope of this
-specification, but all conformant implementations MUST implement a function
+specification, but all conformant implementations implement a function
 which has the following abstract form:
       </p>
 
@@ -4045,7 +4045,7 @@ <h2>
       </code></p>
 
       <p>
-The input variables of this function MUST be as follows:
+The input variables of this function are as follows:
       </p>
 
       <dl>
@@ -4070,7 +4070,7 @@ <h2>
       </dl>
 
       <p>
-The output variables of this function MUST be as follows:
+The output variables of this function are as follows:
       </p>
 
       <dl>
@@ -4116,13 +4116,13 @@ <h2>
     </dl>
 
     <p>
-<a>DID URL Dereferencing</a> implementations MUST NOT alter the signature of
-these functions in any way. <a>DID URL Dereferencing</a> implementations MAY
-map the <code>dereference</code> function to a method-specific internal
-function to perform the actual <a>DID URL Dereferencing</a> process. <a>DID
-URL Dereferencing</a> implementations MAY implement and expose additional
-functions with different signatures in addition to the <code>dereference</code>
-function specified here.
+Conforming <a>DID URL Dereferencing</a> implementations do not alter the
+signature of these functions in any way. <a>DID URL Dereferencing</a>
+implementations MAY map the <code>dereference</code> function to a
+method-specific internal function to perform the actual <a>DID URL
+Dereferencing</a> process. <a>DID URL Dereferencing</a> implementations MAY
+implement and expose additional functions with different signatures in addition
+to the <code>dereference</code> function specified here.
     </p>
 
       <section>
@@ -4227,7 +4227,7 @@ <h2>
 
         <p>
 All implementations of functions that use metadata structures as either input
-or output MUST be able to fully represent all data types described here in a
+or output are able to fully represent all data types described here in a
 deterministic fashion. As inputs and outputs using metadata structures are
 defined in terms of data types and not their serialization, the method for
 representation is internal to the implementation of the function and is out of

From 27abae70ef88963c58f387cc45d4cd57608d0f9c Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 3 Jan 2021 14:31:45 -0500
Subject: [PATCH 2/5] Remove ineffective/already tested/untestable SHOULD
 statements.

---
 index.html | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/index.html b/index.html
index 92e8dd17..20b38e84 100644
--- a/index.html
+++ b/index.html
@@ -1290,12 +1290,12 @@ <h2>Extensibility</h2>
 together.
         </li>
       <li>
-Representations MAY define other extensibility mechanisms, including ones that do
-not require the use of the DID Specification Registries. Such extension mechanisms SHOULD
-support lossless conversion into any other conformant representation. Extension
-mechanisms for a representation SHOULD define a mapping of all properties and
-representation syntax into the <a href="#data-model">data model</a> and its type
-system.
+Representations MAY define other extensibility mechanisms, including ones that
+do not require the use of the DID Specification Registries. Such extension
+mechanisms SHOULD support lossless conversion into any other conformant
+representation. Extension mechanisms for a representation SHOULD define a
+mapping of all properties and representation syntax into the <a
+href="#data-model">data model</a> and its type system.
       </li>
       </ol>
       <p class="note">
@@ -2189,7 +2189,7 @@ <h2>Service Endpoints</h2>
         <dd>
           <p>
 If a <a>DID document</a> includes a <code>service</code> property, the value
-of the property SHOULD be an <a data-cite="INFRA#ordered-set">ordered set</a>
+of the property MUST be an <a data-cite="INFRA#ordered-set">ordered set</a>
 of <a>service endpoints</a>, where each service endpoint is described by a set
 of properties. Each <a>service endpoint</a> MUST have <code><a>id</a></code>,
 <code>type</code>, and <code><a>serviceEndpoint</a></code> properties, and MAY

From 3a9af61ed7c05fbc02960936c6d0ad15c8b23489 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 3 Jan 2021 14:46:48 -0500
Subject: [PATCH 3/5] Remove ineffective/already tested/untestable MAY
 statements.

---
 index.html | 66 ++++++++++++++++++++++--------------------------------
 1 file changed, 27 insertions(+), 39 deletions(-)

diff --git a/index.html b/index.html
index 20b38e84..bb4bc333 100644
--- a/index.html
+++ b/index.html
@@ -943,7 +943,7 @@ <h2>DID Parameters</h2>
         </table>
 
         <p>
-Implementers as well as <a>DID method</a> specification authors MAY use
+Implementers as well as <a>DID method</a> specification authors might use
 additional DID parameters that are not listed here. For maximum
 interoperability, it is RECOMMENDED that DID parameters use the official W3C
 DID Specification Registries mechanism [[?DID-SPEC-REGISTRIES]], to avoid
@@ -951,7 +951,7 @@ <h2>DID Parameters</h2>
         </p>
 
         <p>
-DID parameters MAY be used if there is a clear use case where the parameter
+DID parameters might be used if there is a clear use case where the parameter
 needs to be part of a URI that can be used as a link, or as a <a>resource</a>
 in RDF / JSON-LD documents.
         </p>
@@ -1600,7 +1600,7 @@ <h2>Verification Methods</h2>
 
           <p>
 In the case where a verification method is a public key, the value of the
-<code><a>id</a></code> property MAY be structured as a
+<code><a>id</a></code> property might be structured as a
 <a href="https://en.wikipedia.org/wiki/Compound_key">compound key</a>. This is
 especially useful for integrating with existing key management systems and key
 formats such as JWK [[RFC7517]]. It is RECOMMENDED that JWK <code>kid</code>
@@ -2982,12 +2982,6 @@ <h3>Production</h3>
           </li>
         </ul>
 
-      <p>
-The property name `@context` MAY be present in the CBOR representation of a DID
-Document and if present SHOULD be ignored as this property is reserved for
-JSON-LD processing.
-      </p>
-
       <p>
 All properties of the DID document represented in CBOR MUST be included in the
 root map (major type 5). Properties MAY define additional data sub structures
@@ -3406,7 +3400,7 @@ <h2>Method Operations</h2>
       </p>
       <p>
 Determining the authority of a party to carry out the operations is
-method-specific. For example, a <a>DID method</a> MAY:
+method-specific. For example, a <a>DID method</a> might:
       </p>
       <ul>
         <li>
@@ -3701,7 +3695,7 @@ <h2>
 If the resolution is successful, and if the <code>resolveRepresentation</code>
 function was called, this MUST be a byte stream of the resolved <a>DID
 document</a> in one of the conformant
-<a href="#representations">representations</a>. The byte stream MAY then be
+<a href="#representations">representations</a>. The byte stream might then be
 parsed by the caller of the <code>resolveRepresentation</code> function into a
 <a href="#data-model">data model</a>, which can in turn be validated and
 processed. If the resolution is unsuccessful, this value MUST be an empty
@@ -3726,10 +3720,10 @@ <h2>
 
         <p>
 Conforming <a>DID resolver</a> implementations do not alter the signature of
-these functions in any way. <a>DID resolver</a> implementations MAY map the
+these functions in any way. <a>DID resolver</a> implementations might map the
 <code>resolve</code> and <code>resolveRepresentation</code> functions to a
 method-specific internal function to perform the actual <a>DID resolution</a>
-process. <a>DID resolver</a> implementations MAY implement  and expose
+process. <a>DID resolver</a> implementations might implement and expose
 additional functions with different signatures in addition to the
 <code>resolve</code> function specified here.
         </p>
@@ -3845,13 +3839,11 @@ <h3>DID Document Metadata Properties</h3>
           <section>
             <h4>created</h4>
             <p>
-DID document metadata SHOULD include a <code>created</code> property
-to indicate the timestamp of the <a href="#create">Create operation</a>.
-This property MAY not be supported by a given <a>DID method</a>.
-The value of the property MUST be a <a data-cite="INFRA#string">string</a>
-formatted as an
-<a data-cite="XMLSCHEMA11-2#dateTime">XML Datetime</a> normalized to
-UTC 00:00:00 and without sub-second decimal precision. For example:
+DID document metadata SHOULD include a <code>created</code> property to indicate
+the timestamp of the <a href="#create">Create operation</a>. The value of the
+property MUST be a <a data-cite="INFRA#string">string</a> formatted as an <a
+data-cite="XMLSCHEMA11-2#dateTime">XML Datetime</a> normalized to UTC 00:00:00
+and without sub-second decimal precision. For example:
 <code>2020-12-20T19:17:47Z</code>.
             </p>
           </section>
@@ -3859,11 +3851,10 @@ <h4>created</h4>
           <section>
             <h4>updated</h4>
             <p>
-DID document metadata SHOULD include an <code>updated</code> property
-to indicate the timestamp of the last <a href="#update">Update operation</a>
-for the document version which was resolved. This property MAY not be
-supported by a given <a>DID method</a>. The value of the property MUST
-follow the same formatting rules as the <code>created</code> property.
+DID document metadata SHOULD include an <code>updated</code> property to
+indicate the timestamp of the last <a href="#update">Update operation</a> for
+the document version which was resolved. The value of the property MUST follow
+the same formatting rules as the <code>created</code> property.
                 </p>
               </section>
 
@@ -3875,7 +3866,6 @@ <h4>
 DID document metadata SHOULD include a <code>next-update</code> property if
 the resolved document version is not the latest version of the document. It
 indicates the timestamp of the next <a href="#update">Update operation</a>.
-This property MAY not be supported by a given <a>DID method</a>.
 The value of the property MUST follow the same formatting rules as the
 <code>created</code> property.
             </p>
@@ -3886,11 +3876,10 @@ <h4>
                 version-id
               </h4>
               <p>
-DID document metadata SHOULD include a <code>version-id</code> property
-to indicate the version of the last <a href="#update">Update operation</a>
-for the document version which was resolved. This property MAY not be
-supported by a given <a>DID method</a>. The value of the property MUST be
-an <a data-lt="ascii string">ASCII string</a>.
+DID document metadata SHOULD include a <code>version-id</code> property to
+indicate the version of the last <a href="#update">Update operation</a> for the
+document version which was resolved. The value of the property MUST be an <a
+data-lt="ascii string">ASCII string</a>.
               </p>
             </section>
 
@@ -3899,11 +3888,10 @@ <h4>
                 next-version-id
               </h4>
               <p>
-DID document metadata SHOULD include a <code>next-version-id</code> property
-if the resolved document version is not the latest version of the document.
-It indicates the version of the next <a href="#update">Update operation</a>.
-This property MAY not be supported by a given <a>DID method</a>.
-The value of the property MUST be an <a data-lt="ascii string">ASCII string</a>.
+DID document metadata SHOULD include a <code>next-version-id</code> property if
+the resolved document version is not the latest version of the document. It
+indicates the version of the next <a href="#update">Update operation</a>. The
+value of the property MUST be an <a data-lt="ascii string">ASCII string</a>.
               </p>
             </section>
 
@@ -4093,7 +4081,7 @@ <h2>
         <dd>
 If the <code>dereferencing</code> function was called and successful, this MUST
 contain a resource corresponding to the <a>DID URL</a>.
-The <code>content-stream</code> MAY be a <a>DID document</a> in one of the
+The <code>content-stream</code> SHOULD be a <a>DID document</a> in one of the
 conformant <a href="#representations">representations</a> obtained through
 the resolution process.
 
@@ -4118,9 +4106,9 @@ <h2>
     <p>
 Conforming <a>DID URL Dereferencing</a> implementations do not alter the
 signature of these functions in any way. <a>DID URL Dereferencing</a>
-implementations MAY map the <code>dereference</code> function to a
+implementations might map the <code>dereference</code> function to a
 method-specific internal function to perform the actual <a>DID URL
-Dereferencing</a> process. <a>DID URL Dereferencing</a> implementations MAY
+Dereferencing</a> process. <a>DID URL Dereferencing</a> implementations might
 implement and expose additional functions with different signatures in addition
 to the <code>dereference</code> function specified here.
     </p>

From 1cec62761b2462815233a392ecc364a698f61ffb Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 3 Jan 2021 14:58:30 -0500
Subject: [PATCH 4/5] Remove ineffective/already tested/untestable OPTIONAL
 statements.

---
 index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index bb4bc333..37faf91e 100644
--- a/index.html
+++ b/index.html
@@ -4130,7 +4130,7 @@ <h3>DID URL Dereferencing Input Metadata Properties</h3>
 The MIME type the caller prefers for <code>content-stream</code>. The <a>DID
 URL Dereferencing</a> implementation SHOULD use this value to determine the
 representation contained in the returned value if such a representation is
-supported and available. This property is OPTIONAL.
+supported and available.
                 </dd>
             </dl>
         </section>
@@ -4151,8 +4151,8 @@ <h3>
 content-type
                 </dt>
                 <dd>
-The MIME type of the returned <code>content-stream</code>.
-This property is OPTIONAL if dereferencing is successful.
+The MIME type of the returned <code>content-stream</code> SHOULD be expressed
+using this property if dereferencing is successful.
                 </dd>
                 <dt>
 error

From ce0f0e35bc659a2105244fa1c1f42ee72a6a4e63 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 3 Jan 2021 16:20:31 -0500
Subject: [PATCH 5/5] Fix grammar on CID tag 42 rule.

Co-authored-by: Amy Guy <amy@rhiaro.co.uk>
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 37faf91e..1a5b3f6f 100644
--- a/index.html
+++ b/index.html
@@ -3264,7 +3264,7 @@ <h4>DagCBOR</h4>
 
           <ul>
             <li>
-CBOR tags other than the CID tag (42) MUST NOT be utilized.
+CBOR tags other than the CID tag (42) MUST NOT be used.
             </li>
           </ul>