From 6bb453eae4e57c7f382360f2bad9b80a570d45c3 Mon Sep 17 00:00:00 2001
From: Andres Uribe <auribe@squareup.com>
Date: Sun, 20 Aug 2023 15:21:10 -0400
Subject: [PATCH] Update links from VC-JWT to VC-JOSE-COSE.

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

diff --git a/index.html b/index.html
index 1dd7f3df0..ecab100db 100644
--- a/index.html
+++ b/index.html
@@ -588,7 +588,7 @@ <h3>Use Cases and Requirements</h3>
 
         <ul>
           <li>
-Securing Verifiable Credentials using JSON Web Tokens [[VC-JWT]].
+Securing Verifiable Credentials using JOSE and COSE [[VC-JOSE-COSE]].
           </li>
           <li>
 Securing Verifiable Credentials using Data Integrity Proofs [[VC-DATA-INTEGRITY]].
@@ -1822,10 +1822,10 @@ <h3>Securing Verifiable Credentials</h3>
 external proofs and those that use embedded proofs. An
 <dfn class="lint-ignore">external proof</dfn> is one that wraps an expression of
 this data model, such as via a JSON Web Token, which is elaborated on in the
-<em>Securing Verifiable Credentials using JOSE and COSE</em> [[VC-JOSE-COSE]]
-specification. An <dfn>embedded proof</dfn> is a mechanism where the proof is
-included in the data model, such as a Data Integrity Proof, which is elaborated
-on in <em>Verifiable Credential Data Integrity</em> [[VC-DATA-INTEGRITY]].
+<em>Securing Verifiable Credentials using JOSE and COSE</em> [[VC-JOSE-COSE]] specification.
+An <dfn>embedded proof</dfn> is a mechanism where the proof is included in the
+data model, such as a Data Integrity Proof, which is elaborated on in <em>Verifiable
+Credential Data Integrity</em> [[VC-DATA-INTEGRITY]].
         </p>
         <p>
 It should be noted that these two classes of securing mechanisms are not
@@ -2065,8 +2065,8 @@ <h3>Presentations</h3>
 contents of the <code>proof</code> <a>property</a> are proofs, as described by
 the Data Integrity [[VC-DATA-INTEGRITY]] specification. An example of a
 <a>verifiable presentation</a> using the JWT proof mechanism is
-provided in the Securing Verifiable Credentials using JSON Web Tokens
-[[?VC-JWT]] specification.
+provided in the Securing Verifiable Credentials using JOSE and COSE
+[[?VC-JOSE-COSE]] specification.
         </p>
 
         <section>
@@ -2587,7 +2587,7 @@ <h3>Extensibility</h3>
           </li>
           <li>
 Support multiple types of cryptographic proof formats through the use of
-JSON Web Tokens [[VC-JWT]] and Data Integrity Proofs [[VC-DATA-INTEGRITY]] and a variety of cryptographic
+JOSE or COSE [[VC-JOSE-COSE]], Data Integrity Proofs [[VC-DATA-INTEGRITY]], and a variety of cryptographic
 suites listed in the Verifiable Credential Specifications Directory
 [[?VC-SPECS]].
           </li>
@@ -4063,7 +4063,7 @@ <h3>Proof Formats</h3>
 
         <ul>
           <li>
-Verifiable Credentials using JSON Web Tokens [[VC-JWT]], and
+Verifiable Credentials using JOSE and COSE [[VC-JOSE-COSE]], and
           </li>
           <li>
 Verifiable Credential Data Integrity [[VC-DATA-INTEGRITY]].
@@ -5482,7 +5482,7 @@ <h3>Base Context</h3>
           <li>
 The contents of the credential itself, which is secured in
 <a>verifiable credentials</a> and <a>verifiable presentations</a> by using
-mechanisms such as [[VC-JWT]] and [[VC-DATA-INTEGRITY]].
+mechanisms such as [[VC-JOSE-COSE]] and [[VC-DATA-INTEGRITY]].
           </li>
           <li>
 The content in a credential whose meaning depends on a link to an external URL,