From 76040bfff5e7bcfd5594bfabd615e2c0c86394b6 Mon Sep 17 00:00:00 2001
From: gabe <gcohen@squareup.com>
Date: Mon, 29 Jan 2024 14:16:16 -0800
Subject: [PATCH 1/2] clarify sematnics b/w jwt and vc properties

---
 index.html | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index a3c9561..3446cfa 100644
--- a/index.html
+++ b/index.html
@@ -413,13 +413,22 @@ <h2>JOSE Header Parameters and JWT Claims</h2>
         defined in <a data-cite="VC-DATA-MODEL-2.0#validity-period">Validity Period</a>,
         which represent the validity of the data that is being secured.
       </p>
+      <p>
+        The claims and security provided by this specification are independent of the data 
+        secured and semantics provided by the [[VC-DATA-MODEL-2.0]]. This means that while the security
+        features of this specification ensure data integrity and authenticity, they do
+        not dictate the interpretation of claim data.
+        
+        Implementers are RECOMMENDED to avoid conflicting values, especially with claims such as
+        `issuer` with `iss`, `id` with `jti`, and `credentialSubject.id` with `sub`.
+      </p>
       <p>
         The JWT Claim Names <code>vc</code> and <code>vp</code>
         MUST NOT be present.
       </p>
       <p>
         Additional members may be present as header parameters and claims.
-  If they are not understood, they MUST be ignored.
+        If they are not understood, they MUST be ignored.
       </p>
     </section>
   </section>

From 85b9bf10df7f79b8ea137b2d063a6d9825fabd5c Mon Sep 17 00:00:00 2001
From: Gabe <7622243+decentralgabe@users.noreply.github.com>
Date: Thu, 1 Feb 2024 14:57:45 -0600
Subject: [PATCH 2/2] Update index.html

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

diff --git a/index.html b/index.html
index 3446cfa..ef53c99 100644
--- a/index.html
+++ b/index.html
@@ -418,9 +418,11 @@ <h2>JOSE Header Parameters and JWT Claims</h2>
         secured and semantics provided by the [[VC-DATA-MODEL-2.0]]. This means that while the security
         features of this specification ensure data integrity and authenticity, they do
         not dictate the interpretation of claim data.
-        
-        Implementers are RECOMMENDED to avoid conflicting values, especially with claims such as
-        `issuer` with `iss`, `id` with `jti`, and `credentialSubject.id` with `sub`.
+      </p>
+      <p>
+        Implementers SHOULD avoid setting JWT claims to values that conflict with
+        verifiable credential properties, especially with pairs such as
+        `iss` and `issuer`, `jti` and `id`, and `sub` and `credentialSubject.id`.
       </p>
       <p>
         The JWT Claim Names <code>vc</code> and <code>vp</code>