From 9291ef4194e3198b1118a447d7e4ac8f515224da Mon Sep 17 00:00:00 2001
From: gabe <gcohen@squareup.com>
Date: Tue, 1 Aug 2023 13:34:15 -0700
Subject: [PATCH 1/4] add guidance on when to use each type

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

diff --git a/index.html b/index.html
index 05a0e36..ff9f185 100644
--- a/index.html
+++ b/index.html
@@ -151,6 +151,19 @@ <h2>Data Model</h2>
             property, and <code>JsonSchemaCredential2023</code> for usage of a [[JSON-Schema]] represented as a
             <a>verifiable credential</a>.
          </p>
+         <p>
+            Implementers MAY choose to use <code>JsonSchemaCredential2023</code> when they wish to
+            leverage features of the [[VC-DATA-MODEL-2]]. Providing a JSON Schema as a verifiable credential is
+            useful when it is valuable to leverage the data model's features, answering questions such as:
+            <ul>
+               <li>Who is the author of this schema? (provided by the <code>issuer</code> property)</li>
+               <li>Why should the author be trusted for providing this schema? (provided by the <code>evidence</code> property)</li>
+               <li>Is it schema still in use? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li>
+            </ul>
+
+            When these features are not necessary for a given use case it is RECOMMENDED that implementers
+            use the <code>JsonSchema2023</code> type.
+         </p>
          <section>
             <h3>JsonSchema2023</h3>
             <p>

From 3745b705d7ed826ca5dc160b6a4bbf40dabad4ac Mon Sep 17 00:00:00 2001
From: gabe <gcohen@squareup.com>
Date: Tue, 1 Aug 2023 14:06:00 -0700
Subject: [PATCH 2/4] update language

---
 index.html | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/index.html b/index.html
index ff9f185..dd01fe3 100644
--- a/index.html
+++ b/index.html
@@ -152,17 +152,14 @@ <h2>Data Model</h2>
             <a>verifiable credential</a>.
          </p>
          <p>
-            Implementers MAY choose to use <code>JsonSchemaCredential2023</code> when they wish to
-            leverage features of the [[VC-DATA-MODEL-2]]. Providing a JSON Schema as a verifiable credential is
-            useful when it is valuable to leverage the data model's features, answering questions such as:
+            Implementers may find use in packaging a JSON Schema as a verifiable credential when they wish to
+            leverage features of the [[VC-DATA-MODEL-2]], answering questions such as:
             <ul>
                <li>Who is the author of this schema? (provided by the <code>issuer</code> property)</li>
                <li>Why should the author be trusted for providing this schema? (provided by the <code>evidence</code> property)</li>
                <li>Is it schema still in use? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li>
+               <li>Has the schema been tampered with? (provided by [[VC-DATA-INTEGRITY]] or [[VC-JWT]])</li>
             </ul>
-
-            When these features are not necessary for a given use case it is RECOMMENDED that implementers
-            use the <code>JsonSchema2023</code> type.
          </p>
          <section>
             <h3>JsonSchema2023</h3>

From b64d8bfd884c241f790fe18c73d1f46283625446 Mon Sep 17 00:00:00 2001
From: gabe <gcohen@squareup.com>
Date: Tue, 1 Aug 2023 15:53:15 -0700
Subject: [PATCH 3/4] pr comment

---
 index.html | 1 -
 1 file changed, 1 deletion(-)

diff --git a/index.html b/index.html
index dd01fe3..5a0ee40 100644
--- a/index.html
+++ b/index.html
@@ -156,7 +156,6 @@ <h2>Data Model</h2>
             leverage features of the [[VC-DATA-MODEL-2]], answering questions such as:
             <ul>
                <li>Who is the author of this schema? (provided by the <code>issuer</code> property)</li>
-               <li>Why should the author be trusted for providing this schema? (provided by the <code>evidence</code> property)</li>
                <li>Is it schema still in use? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li>
                <li>Has the schema been tampered with? (provided by [[VC-DATA-INTEGRITY]] or [[VC-JWT]])</li>
             </ul>

From 820075908809d73ae1449c6e755ac75146b81aea Mon Sep 17 00:00:00 2001
From: gabe <gcohen@squareup.com>
Date: Tue, 1 Aug 2023 15:53:47 -0700
Subject: [PATCH 4/4] one more

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 5a0ee40..83eed8f 100644
--- a/index.html
+++ b/index.html
@@ -156,7 +156,7 @@ <h2>Data Model</h2>
             leverage features of the [[VC-DATA-MODEL-2]], answering questions such as:
             <ul>
                <li>Who is the author of this schema? (provided by the <code>issuer</code> property)</li>
-               <li>Is it schema still in use? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li>
+               <li>Is it schema still valid? (provided by the <code>validFrom</code>, <code>validUntil</code>, and <code>credentialStatus</code> properties)</li>
                <li>Has the schema been tampered with? (provided by [[VC-DATA-INTEGRITY]] or [[VC-JWT]])</li>
             </ul>
          </p>