Skip to content

Use HTTP Semantics for accept option #267

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

Merged
msporny merged 5 commits into from
Jan 22, 2026
Merged

Use HTTP Semantics for accept option #267

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
31f78b5
Remove trailing spaces.
msporny Dec 18, 2025
f4e3be7
Remove unnecessary normative text from DID Resolution Algorithm.
msporny Dec 18, 2025
9aa9a02
Align `accept` value with RFC9110.
msporny Jan 8, 2026
82169ff
Merge branch 'main' into msporny-accept-semantics
msporny Jan 11, 2026
7d7f604
Merge branch 'main' into msporny-accept-semantics
msporny Jan 22, 2026
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
32 changes: 15 additions & 17 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -576,14 +576,14 @@ <h3>DID Resolution Options</h3>
accept
</dt>
<dd>
The Media Type of the caller's preferred <a>representation</a> of the <a>DID
document</a>. The Media Type MUST be expressed as an <a data-lt="ascii
string">ASCII string</a>. The <a>DID resolver</a> implementation SHOULD use this
value to determine the <a>representation</a> of the returned
<code>didDocument</code> if such a <a>representation</a> is supported and
available. Any <a>representation</a> MUST be able to be translated into
the representation defined by the <code>application/did</code> mediaType.
This property is OPTIONAL.
The media type of the caller's preferred <a>representation</a> of the
<a>DID document</a>. The value MUST be expressed according to the
`Accept` header value as defined in [[[RFC9110]]], <a
data-cite="RFC9110#section-12.5.1">Section 12.5.1</a>. The <a>DID
resolver</a> implementation SHOULD use this value to determine the
<a>representation</a> of the returned
<code>didDocument</code> if such a <a>representation</a> is supported
and available. This property is OPTIONAL.
</dd>
</dl>

Expand Down Expand Up @@ -1188,11 +1188,13 @@ <h3>DID URL Dereferencing Options</h3>
accept
</dt>
<dd>
The Media Type that the caller prefers for <code>contentStream</code>. The Media
Type MUST be expressed as an <a data-lt="ascii string">ASCII string</a>. The
<a>DID URL dereferencer</a> implementation SHOULD use this value to determine
the <code>contentType</code> of the <a>representation</a> contained in the
returned value if such a <a>representation</a> is supported and available.
The media type that the caller prefers for <code>contentStream</code>.
The value MUST be expressed according to the `Accept` header value as
defined in [[[RFC9110]]], <a data-cite="RFC9110#section-12.5.1">Section
12.5.1</a>. The <a>DID URL dereferencer</a> implementation SHOULD use
this value to determine the <code>contentType</code> of the
<a>representation</a> contained in the returned value if such a
<a>representation</a> is supported and available.
</dd>
</dl>
<dl>
Expand Down Expand Up @@ -1622,11 +1624,7 @@ <h2>Metadata Structure</h2>
<a data-cite="INFRA#sets">set</a>,
<a data-cite="INFRA#boolean">boolean</a>, or
<a data-cite="INFRA#nulls">null</a>. The values within any complex data
<<<<<<< HEAD
structure such as a map or list MUST be one of these data types as well.
=======
structure such as a map or list MUST also be one of these data types.
>>>>>>> 526ac87 (Apply suggestions from code review)
The entire metadata structure MUST be serializable according to the <a
data-cite="INFRA#serialize-an-infra-value-to-json-bytes">JSON
serialization rules</a> in the [[INFRA]] specification. Implementations MAY
Expand Down