From d7d4a47572f02a4d6fa445dae8f6486a9aa02d1d Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Fri, 29 Dec 2023 19:05:27 -0500 Subject: [PATCH] Fix grammar in protocol statements. Co-authored-by: Ted Thibodeau Jr --- index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index 3e04381..48ddccf 100644 --- a/index.html +++ b/index.html @@ -878,22 +878,22 @@

Bitstring Expansion Algorithm

Media Types

-When publishing status list information, issuers SHOULD publish the status list -using an HTTPS URL and in a way that makes it not possible to correlate usage -patterns related to the list. When retrieving status list information, verifiers -SHOULD retrieve the status list over protocols that guard against access +Issuers SHOULD publish status list information +using HTTPS URLs and in ways that minimize possible correlation of usage +patterns related to the list. Verifiers +SHOULD retrieve status list information using protocols that guard against access pattern correlation, such as Oblivious HTTP [[?OHTTP]].

-When dereferencing `statusListCredential`, the content type of the +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.

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`. +have media type `application/vc+ld+json`, while a verifiable credential +secured with SD-JWT might have media type `application/sd-jwt`.

Some implementations might choose to support less specific media types such as