Skip to content

Define network based conformance classes for resolver and dereferencer #243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: gh-pages
Choose a base branch
from
Open

Define network based conformance classes for resolver and dereferencer #243

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6dc21c0
attempt at defining network based conformance classes and JSON serial…
wip-abramson Oct 30, 2025
5080917
Move to conforming HTTPS-based instead of network-based
wip-abramson Nov 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 25 additions & 4 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,12 +227,24 @@ <h2>Implementer Overview</h2>
statements in <a href="#resolving"></a>.
</p>

<p>
A <dfn class="lint-ignore">conforming network-based DID resolver</dfn> is a
[=conforming DID resolver=] that additionally complies with the normative statements
in [[[#bindings-https]]].
</p>

<p>
A <dfn class="lint-ignore">conforming DID URL dereferencer</dfn> is any
algorithm realized as software and/or hardware that complies with the relevant
normative statements in <a href="#dereferencing"></a>.
</p>

<p>
A <dfn class="lint-ignore">conforming network-based DID URL dereferencer</dfn> is a
[=conforming DID URL dereferencer=] that additionally complies with the normative
statements in [[[#bindings-https]]].
</p>

</section>

<section class="informative">
Expand Down Expand Up @@ -464,7 +476,7 @@ <h1>DID Resolution</h1>
document</a> by using the "Read" operation of the applicable <a>DID method</a>
as described in <a data-cite="did-core#method-operations">Method Operations</a>.
</p>
<p> All conforming <a>DID resolvers</a> implement the function below, which has the
<p> All [=conforming DID resolvers=] implement the function below, which has the
following abstract form:
</p>

Expand All @@ -474,9 +486,12 @@ <h1>DID Resolution</h1>
</pre>

<p>
All conformant <a>DID resolvers</a> MUST implement the <a>DID resolution</a>
All [=conforming DID resolvers=] MUST implement the <a>DID resolution</a>
function for at least one <a>DID method</a> and MUST be able to return a
<a>DID document</a> in at least one conformant <a>representation</a>.
<a>DID document</a> in at least one conformant <a>representation</a>. All
inputs and outputs of the <code>resolve</code> function are MUST be serializable
to JSON.

Comment on lines +491 to +494
Copy link
Contributor Author

@wip-abramson wip-abramson Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After reviewing the existing normative statements as part of the test suite work, I think this is not necessary.

We currently have the following:

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

See https://w3c.github.io/did-resolution/#:~:text=The%20entire%20metadata%20structure%20MUST%20be%20serializable%20according%20to%20the%20JSON%20serialization%20rules%20in%20the%20%5BINFRA%5D%20specification.

This applies to all metadata structures throughout the spec. So I think this addition is really duplicate statement and can be removed.

</p>

<p>
Expand Down Expand Up @@ -1042,7 +1057,7 @@ <h1>DID URL Dereferencing</h1>
</div>

<p>
All conforming <a>DID URL dereferencers</a> implement the
All [=conforming DID URL dereferencers=] implement the
function below, which has the following abstract form:
</p>

Expand All @@ -1051,6 +1066,12 @@ <h1>DID URL Dereferencing</h1>
« dereferencingMetadata, contentStream, contentMetadata »
</pre>

<p>
All [=conforming DID URL dereferencers=] MUST implement the [=DID URL dereferencing=]
function for at least one [=DID method=]. All inputs and outputs of the <code>dereference</code>
function apart from [=contentStream=] MUST be serializable to JSON.
</p>

<p>
The input variables of the <code>dereference</code> function are as follows:
</p>
Expand Down