From d63377433d03dcc0c5f8cf059aa228e387e155a8 Mon Sep 17 00:00:00 2001
From: Orie Steele <orie@transmute.industries>
Date: Tue, 31 Oct 2023 11:49:06 -0500
Subject: [PATCH 1/4] Add section on media types

---
 index.html | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/index.html b/index.html
index 3796f7a..f6c0857 100644
--- a/index.html
+++ b/index.html
@@ -798,6 +798,33 @@ <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/vc+ld+json+sd-jwt</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 if they do not support the requested media type.
+    </p>
+  </section>
+
   <section class="informative">
     <h2>Privacy Considerations</h2>
 

From 6e707de0fb36971994856d43fbef581c7a069327 Mon Sep 17 00:00:00 2001
From: Orie Steele <orie@transmute.industries>
Date: Tue, 31 Oct 2023 11:51:33 -0500
Subject: [PATCH 2/4] Add less specific media types

---
 index.html | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.html b/index.html
index f6c0857..c78e971 100644
--- a/index.html
+++ b/index.html
@@ -812,6 +812,10 @@ <h2>Media Types</h2>
       whereas a verifiable credential secured with 
       SD-JWT might have content-type <code>application/vc+ld+json+sd-jwt</code>.
     </p>
+    <p>
+      Some implementations might choose to support less specific media types, for example:
+      <code>application/ld+json</code>, <code>application/json</code> or <code>application/sd-jwt</code>.
+    </p>
     <p>
       When dereferencing over HTTP, 
       the use of the <a data-cite="rfc7231#section-5.3.2">accept</a> 

From 6608346b55bcd5a8412267dae89ecfbe7ab542c0 Mon Sep 17 00:00:00 2001
From: Orie Steele <orie@transmute.industries>
Date: Tue, 31 Oct 2023 11:57:38 -0500
Subject: [PATCH 3/4] Add sentence on consming indexes

---
 index.html | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.html b/index.html
index c78e971..1e3231e 100644
--- a/index.html
+++ b/index.html
@@ -947,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 / assign indexes randomly. 
+      </p>
     </section>
 
   </section>

From 57026fb9bb41f8d171282a3c603f418652b6bf13 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Wed, 27 Dec 2023 16:02:34 -0500
Subject: [PATCH 4/4] Minor fixes to media types language.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/index.html b/index.html
index 1e3231e..3c30f62 100644
--- a/index.html
+++ b/index.html
@@ -810,11 +810,11 @@ <h2>Media Types</h2>
       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/vc+ld+json+sd-jwt</code>.
+      SD-JWT might have content-type <code>application/sd-jwt</code>.
     </p>
     <p>
-      Some implementations might choose to support less specific media types, for example:
-      <code>application/ld+json</code>, <code>application/json</code> or <code>application/sd-jwt</code>.
+      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, 
@@ -825,7 +825,7 @@ <h2>Media Types</h2>
     </p>
     <p>
       Some implementations might use the <a data-cite="rfc7231#section-6.5.13">415 Unsupported Media Type</a>
-      status code to signal if they do not support the requested media type.
+      status code to signal that they do not support the requested media type.
     </p>
   </section>
 
@@ -948,7 +948,7 @@ <h3>Bitstring Encoding</h3>
 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 / assign indexes randomly. 
+Implementations SHOULD consume and/or assign indexes randomly. 
       </p>
     </section>