From e4a9644916d87c32a903e24773ae83c23f0d3036 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Mon, 19 Jun 2023 03:22:47 -0400
Subject: [PATCH 1/4] Make referenced vocabulary values normative.

---
 index.html | 89 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 88 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 95c67d665..0a1cd18ba 100644
--- a/index.html
+++ b/index.html
@@ -5052,7 +5052,7 @@ <h3>Fitness for Purpose</h3>
     </section>
 
     <section class="appendix informative">
-      <h2>Contexts, Types, and Credential Schemas</h2>
+      <h2>Contexts, Vocabularies, Types, and Credential Schemas</h2>
 
       <section class="normative">
         <h3>Base Context</h3>
@@ -5116,6 +5116,93 @@ <h3>Base Context</h3>
         </p>
       </section>
 
+      <section class="normative">
+        <h3>Vocabularies</h3>
+
+        <p>
+Implementations MUST ensure that the following vocabulary URLs used in the base
+context ultimately resolve to the following files, which are normative:
+        </p>
+
+        <table class="simple">
+          <thead>
+            <tr>
+              <th>URL</th>
+              <th>Media Type</th>
+              <th>Content</th>
+            </tr>
+          </thead>
+          <tbody>
+            <tr>
+              <td>
+https://www.w3.org/2018/credentials#
+              </td>
+              <td>
+text/html
+              </td>
+              <td>
+https://www.w3.org/2018/credentials/index.html
+              </td>
+            </tr>
+            <tr>
+              <td>
+https://www.w3.org/2018/credentials#
+              </td>
+              <td>
+application/ld+json
+              </td>
+              <td>
+https://www.w3.org/2018/credentials/index.jsonld
+              </td>
+            </tr>
+            <tr>
+              <td>
+https://schema.org/
+              </td>
+              <td>
+text/html
+              </td>
+              <td>
+https://schema.org/
+              </td>
+            </tr>
+            <tr>
+              <td>
+https://schema.org/
+              </td>
+              <td>
+application/ld+json
+              </td>
+              <td>
+https://schema.org/version/latest/schemaorg-current-https.jsonld
+              </td>
+            </tr>
+            <tr>
+              <td>
+https://w3id.org/security#
+              </td>
+              <td>
+text/html
+              </td>
+              <td>
+https://w3c.github.io/vc-data-integrity/vocab/security/vocabulary.html
+              </td>
+            </tr>
+            <tr>
+              <td>
+https://w3id.org/security#
+              </td>
+              <td>
+application/ld+json
+              </td>
+              <td>
+https://w3c.github.io/vc-data-integrity/vocab/security/vocabulary.jsonld
+              </td>
+            </tr>
+          </tbody>
+        </table>
+
+      </section>
       <section class="informative">
         <h3>Differences between Contexts, Types, and CredentialSchemas</h3>
 

From 73d775d8a4380d57cdac85b4d4360311bf742f8c Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Fri, 30 Jun 2023 06:10:59 -0400
Subject: [PATCH 2/4] Add issue marker noting Vocabulary URLs might change.

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

diff --git a/index.html b/index.html
index 0a1cd18ba..b5774edd2 100644
--- a/index.html
+++ b/index.html
@@ -5119,6 +5119,14 @@ <h3>Base Context</h3>
       <section class="normative">
         <h3>Vocabularies</h3>
 
+        <p class="issue" title="(AT RISK) URL values might change during Candidate Recommendation">
+This section lists URL values that might change during the Candidate
+Recommendation phase based on migration of documents to the W3C Technical
+Reports namespace and implementer feedback that requires the referenced URLs to
+be modified. Specifically, it is expected that the github.io links listed
+below will eventually point to W3C TR space.
+        </p>
+
         <p>
 Implementations MUST ensure that the following vocabulary URLs used in the base
 context ultimately resolve to the following files, which are normative:

From b2142479549e961fd88f7a10822f620c63cf4f91 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Fri, 30 Jun 2023 06:20:29 -0400
Subject: [PATCH 3/4] Add issue marker noting impending change away from
 w3c.github.io.

---
 index.html | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index b5774edd2..648fe3774 100644
--- a/index.html
+++ b/index.html
@@ -5123,8 +5123,7 @@ <h3>Vocabularies</h3>
 This section lists URL values that might change during the Candidate
 Recommendation phase based on migration of documents to the W3C Technical
 Reports namespace and implementer feedback that requires the referenced URLs to
-be modified. Specifically, it is expected that the github.io links listed
-below will eventually point to W3C TR space.
+be modified.
         </p>
 
         <p>
@@ -5210,6 +5209,13 @@ <h3>Vocabularies</h3>
           </tbody>
         </table>
 
+        <p class="issue" title="w3c.github.io links expected to change">
+The URLs listed above that start with
+`https://w3c.github.io/vc-data-integrity/vocab/security/` are expected to change
+to `https://www.w3.org/ns/security/` or an equally normative and archived
+location under W3C control.
+        </p>
+
       </section>
       <section class="informative">
         <h3>Differences between Contexts, Types, and CredentialSchemas</h3>

From f3d32dd31b038cdde4d7a2deb8d182b2cf3d0851 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Fri, 30 Jun 2023 06:36:42 -0400
Subject: [PATCH 4/4] Add issue marker for normative references for vocabulary
 files.

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

diff --git a/index.html b/index.html
index 648fe3774..9813f63d1 100644
--- a/index.html
+++ b/index.html
@@ -5216,6 +5216,14 @@ <h3>Vocabularies</h3>
 location under W3C control.
         </p>
 
+        <p class="issue" title="How to normatively refer to vocabulary files">
+The Working Group is currently discussing how it might want to normatively
+refer to the vocabulary files that are under the control of the Working Group.
+Current options are: inclusion of the files directly into the specification or
+publishing the files in W3C TR space and referring to them by using a
+cryptographic hash.
+        </p>
+
       </section>
       <section class="informative">
         <h3>Differences between Contexts, Types, and CredentialSchemas</h3>