Skip to content
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

Add section on media types #92

Merged
merged 4 commits into from
Dec 27, 2023
Merged

Add section on media types #92

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d633774
Add section on media types
OR13 Oct 31, 2023
6e707de
Add less specific media types
OR13 Oct 31, 2023
6608346
Add sentence on consming indexes
OR13 Oct 31, 2023
57026fb
Minor fixes to media types language.
msporny Dec 27, 2023
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
34 changes: 34 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -798,6 +798,37 @@ <h3>Bitstring Expansion Algorithm</h3>

</section>

<section class="informative">
<h2>Media Types</h2>
<p>
When dereferencing <code>statusListCredential</code>,
the content type of the <code>statusListCredential</code> might
be any media type registered for the purpose of expressing a
verifiable credential with one or more proofs.
</p>
<p>
For example, a verifiable credential secured with
Data Integrity Proofs might have content type <code>application/vc+ld+json</code>,
whereas a verifiable credential secured with
SD-JWT might have content-type <code>application/sd-jwt</code>.
</p>
<p>
Some implementations might choose to support less specific media types such as
<code>application/ld+json</code> or <code>application/json</code>.
</p>
<p>
When dereferencing over HTTP,
the use of the <a data-cite="rfc7231#section-5.3.2">accept</a>
and <a data-cite="rfc7231#section-3.1.1.5">content-type</a> headers,
might allow some implementations to negotiate for the proof format
used to secure the <code>statusListCredential</code>.
</p>
<p>
Some implementations might use the <a data-cite="rfc7231#section-6.5.13">415 Unsupported Media Type</a>
status code to signal that they do not support the requested media type.
</p>
</section>

<section class="informative">
<h2>Privacy Considerations</h2>

Expand Down Expand Up @@ -916,6 +947,9 @@ <h3>Bitstring Encoding</h3>
<p>
For example, if a bitstring is 131,072 bits in size (16KB), the first index will be 0, and the last index will be 131,071.
</p>
<p>
Implementations SHOULD consume and/or assign indexes randomly.
</p>
</section>

</section>
Expand Down