From cf7bb515120e0d4e2de4a8300c51338915b3f84a Mon Sep 17 00:00:00 2001 From: Will Abramson Date: Tue, 2 Dec 2025 11:03:53 +0900 Subject: [PATCH 1/6] remove DID method normative statement about proofs --- index.html | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/index.html b/index.html index 6439910..b0bff5f 100644 --- a/index.html +++ b/index.html @@ -1831,9 +1831,7 @@

Method Architectures

To enable verifiable reads, many DID methods use digital signatures, state proofs, proofs of - inclusion in Merkle trees, cryptographic event logs, or other types of proofs. If a DID method - uses such proofs, it MUST specify in its DID method specification how they are used for - verification of the correctness of the result of a "Read" operation. + inclusion in Merkle trees, cryptographic event logs, or other types of proofs.

From 180796f65e96023388c737aaa81ccc7d9f304f7a Mon Sep 17 00:00:00 2001 From: Will Abramson Date: Tue, 2 Dec 2025 11:09:22 +0900 Subject: [PATCH 2/6] remove requirement on did extensions registry for did resolution metadata --- index.html | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index b0bff5f..ab7037e 100644 --- a/index.html +++ b/index.html @@ -1592,13 +1592,8 @@

Metadata Structure

set, boolean, or null. The values within any complex data - structure such as a map or list MUST be one of these data types as well. - All metadata property definitions registered in the DID Resolution Extensions - [[?DID-EXTENSIONS-RESOLUTION]] MUST define the value type, including any - additional formats or restrictions to that value (for example, a string - formatted as a date). It is RECOMMENDED that property - definitions use strings for values. The entire metadata structure MUST be - serializable according to the JSON serialization rules in the [[INFRA]] specification. Implementations MAY serialize the metadata structure to other data formats. From 5f4bb49343f2bc79c3207ef5b79abb2281da097d Mon Sep 17 00:00:00 2001 From: Will Abramson Date: Tue, 2 Dec 2025 11:13:10 +0900 Subject: [PATCH 3/6] remove duplicate normative statements about implementing the resolution/derferencing algs --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index ab7037e..288295a 100644 --- a/index.html +++ b/index.html @@ -879,7 +879,7 @@

DID Document Metadata

DID Resolution Algorithm

-

The following DID resolution algorithm MUST be implemented by a conformant DID resolver.

+

A DID resolver implements the following DID resolution algorithm.

  1. Validate that the input DID conforms to the `did` rule of the DID Syntax. @@ -1248,7 +1248,7 @@

    DID URL Content Metadata

    DID URL Dereferencing Algorithm

    -

    The following DID URL dereferencing algorithm MUST be implemented by a conformant DID resolver. +

    A DID URL dereferencer implements the following DID URL dereferencing algorithm. In accordance with [[RFC3986]], it consists of the following three steps: resolving the DID; dereferencing the resource; and dereferencing the fragment (only if the input DID URL contains a DID fragment):

    From 322598e12bd1122771b051e5d416816f7873e333 Mon Sep 17 00:00:00 2001 From: Will Abramson Date: Tue, 2 Dec 2025 11:18:49 +0900 Subject: [PATCH 4/6] remove duplicate normative statement about supporting resolution for at least one DID method --- index.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/index.html b/index.html index 288295a..8c53aba 100644 --- a/index.html +++ b/index.html @@ -476,7 +476,7 @@

    DID Resolution

    All conformant DID resolvers MUST implement the DID resolution function for at least one DID method and MUST be able to return a - DID document in at least one conformant representation. + DID document.

    @@ -1933,8 +1933,7 @@

    Resolver Architectures

    Multiple Methods

    -

    A DID resolver MUST support the DID resolution algorithm for at least one DID method and - MAY support it for multiple DID methods:

    +

    A DID resolver might support the DID resolution algorithm for multiple DID methods:

    Diagram showing a DID resolver that supports multiple DID methods. From c5b9b7dc645adf91ebddba39276356025d47c3fb Mon Sep 17 00:00:00 2001 From: Will Abramson Date: Tue, 2 Dec 2025 11:20:29 +0900 Subject: [PATCH 5/6] remove normative statement around passing resolution options to Read --- index.html | 4 ---- 1 file changed, 4 deletions(-) diff --git a/index.html b/index.html index 8c53aba..abb9b46 100644 --- a/index.html +++ b/index.html @@ -902,10 +902,6 @@

    DID Resolution Algorithm

    Read operation against the input DID's verifiable data registry, as defined by the input DID method:
      -
    1. Besides the input DID, all additional resolution options of - this algorithm MUST be passed to the - Read operation of the - input DID method.
    2. If the input DID does not exist, return the following result:
      1. didResolutionMetadata: error object with type set to NOT_FOUND
        2. From 1aaded8e3a379ef845022ecca5af11cd8eb4a40c Mon Sep 17 00:00:00 2001 From: Will Abramson Date: Tue, 2 Dec 2025 11:22:50 +0900 Subject: [PATCH 6/6] remove duplicate normative statement about errors --- index.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/index.html b/index.html index abb9b46..20446b6 100644 --- a/index.html +++ b/index.html @@ -649,8 +649,7 @@

        DID Resolution Metadata

        error
        - An error data structure defined in [[RFC9457]]. This property is REQUIRED when there is an error - in the resolution process. The errors defined by this specification and can be found in + An error data structure defined in [[RFC9457]]. The errors defined by this specification and can be found in Section . Additional errors SHOULD be registered in the DID Resolution Extensions [[?DID-EXTENSIONS-RESOLUTION]].