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

Jump to bottom

Add protocol statements related to pub/sub of status lists. #107

Merged
merged 2 commits into from
Jan 13, 2024
Merged

Add protocol statements related to pub/sub of status lists. #107

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6d4adf8
Add protocol statements related to pub/sub of status lists.
msporny Dec 28, 2023
3293cce
Fix grammar in protocol statements.
msporny Dec 30, 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
7 changes: 7 additions & 0 deletions common.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,13 @@ var ccg = {
status: 'CG-DRAFT',
publisher: 'Credentials Community Group'
},
'OHTTP': {
title: 'Oblivious HTTP ',
href: 'https://datatracker.ietf.org/doc/html/draft-ietf-ohai-ohttp',
authors: ['Martin Thomson', 'Christopher A. Wood'],
status: 'Working Group Draft',
publisher: 'IETF Oblivious HTTP Application Intermediation'
},
'IPFS': {
title: 'InterPlanetary File System (IPFS)',
href: 'https://en.wikipedia.org/wiki/InterPlanetary_File_System',
Expand Down
23 changes: 16 additions & 7 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -815,17 +815,26 @@ <h3>Bitstring Expansion Algorithm</h3>

</section>

<section class="informative">
<section class="normative">
<h2>Media Types</h2>

<p>
<a>Issuers</a> SHOULD publish status list information
using HTTPS URLs and in ways that minimize possible correlation of usage
patterns related to the list. <a>Verifiers</a>
SHOULD retrieve status list information using protocols that guard against access
pattern correlation, such as Oblivious HTTP [[?OHTTP]].
</p>

<p>
When dereferencing `statusListCredential`, the content type of the
`statusListCredential` might be any media type registered for the purpose of
expressing a verifiable credential with one or more proofs.
When dereferencing `statusListCredential`, the content of the returned
`statusListCredential` 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 `application/vc+ld+json`, whereas a verifiable credential
secured with SD-JWT might have content-type `application/sd-jwt`.
For example, a verifiable credential secured with Data Integrity Proofs might
have media type `application/vc+ld+json`, while a verifiable credential
secured with SD-JWT might have media type `application/sd-jwt`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
secured with SD-JWT might have media type `application/sd-jwt`.
secured with SD-JWT might have media type `application/vc+ld+json+sd-jwt`.

Copy link
Member Author

@msporny msporny Jan 2, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

There doesn't seem to be consensus on this media type in the latest JOSE COSE spec.

</p>
<p>
Some implementations might choose to support less specific media types such as
Expand Down