diff --git a/index.html b/index.html
index 95c67d665..9813f63d1 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,115 @@ <h3>Base Context</h3>
         </p>
       </section>
 
+      <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.
+        </p>
+
+        <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>
+
+        <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>
+
+        <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>