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

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

diff --git a/index.html b/index.html
index f78700c..249a730 100644
--- a/index.html
+++ b/index.html
@@ -420,13 +420,23 @@ <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>