From 0b9268149623efd08c1b9c4c04e2b2bbaa1705d5 Mon Sep 17 00:00:00 2001
From: David Chadwick <d.w.chadwick@kent.ac.uk>
Date: Mon, 30 Aug 2021 11:23:46 +0100
Subject: [PATCH 1/5] Credentials and Verifiable Credentials

This PR is text for issue #798
---
 index.html | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index eb967034d..7c069fc5c 100644
--- a/index.html
+++ b/index.html
@@ -436,13 +436,19 @@ <h3>Use Cases and Requirements</h3>
 <!-- requirement list start -->
         <ul>
           <li>
+          <li>
+<a>Credentials</a> represent statements made by an issuer.
+          </li>
 <a>Verifiable credentials</a> represent statements made by an <a>issuer</a> in
 a tamper-evident and privacy-respecting manner.
           </li>
           <li>
 <a>Holders</a> assemble collections of <a>verifiable credentials</a> from
 different <a>issuers</a> into a single artifact, a
-<a>verifiable presentation</a>.
+<a>presentation</a>.
+          </li>
+          <li>
+Holders convert <a>presentations</a> into <a>verifiable presentations</a>, yielding them tamper-evident. 
           </li>
           <li>
 <a>Issuers</a> can issue <a>verifiable credentials</a> about any <a>subject</a>.
@@ -514,6 +520,9 @@ <h3>Use Cases and Requirements</h3>
 <a>Issuers</a> can issue revocable <a>verifiable credentials</a>.
           </li>
           <li>
+The process of cryptographically protecting <a>credentials</a> and <a>presentations</a>, and verifying <a>verifiable credentials</a> and <a>verifiable presentations</a>, has to be deterministic, bi-directional, and lossless. Any verification of a <a>verifiable credential</a> or <a>verifiable presentation</a> needs to be transformable to the generic data model defined in this document in a deterministic process such that the resulting <a>credential</a> or <a>presentation</a> is semantically and syntactically equivalent to the original construct so that it can be processed in an interoperable fashion.
+          </li>
+          <li>
 <a>Verifiable credentials</a> and <a>verifiable presentations</a> have to be
 serializable in one or more machine-readable data formats. The process of
 serialization and/or de-serialization has to be deterministic, bi-directional,

From 69ff5f06599de21713557d0f8e8a87192c906924 Mon Sep 17 00:00:00 2001
From: Brent Zundel <brent.zundel@gmail.com>
Date: Tue, 7 Sep 2021 16:24:40 -0600
Subject: [PATCH 2/5] Apply suggestions from code review

apply suggestions approved by @David-Chadwick

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

diff --git a/index.html b/index.html
index 7c069fc5c..285b8b670 100644
--- a/index.html
+++ b/index.html
@@ -448,7 +448,8 @@ <h3>Use Cases and Requirements</h3>
 <a>presentation</a>.
           </li>
           <li>
-Holders convert <a>presentations</a> into <a>verifiable presentations</a>, yielding them tamper-evident. 
+Holders convert <a>presentations</a> into <a>verifiable presentations</a>,
+rendering them tamper-evident. 
           </li>
           <li>
 <a>Issuers</a> can issue <a>verifiable credentials</a> about any <a>subject</a>.
@@ -520,7 +521,15 @@ <h3>Use Cases and Requirements</h3>
 <a>Issuers</a> can issue revocable <a>verifiable credentials</a>.
           </li>
           <li>
-The process of cryptographically protecting <a>credentials</a> and <a>presentations</a>, and verifying <a>verifiable credentials</a> and <a>verifiable presentations</a>, has to be deterministic, bi-directional, and lossless. Any verification of a <a>verifiable credential</a> or <a>verifiable presentation</a> needs to be transformable to the generic data model defined in this document in a deterministic process such that the resulting <a>credential</a> or <a>presentation</a> is semantically and syntactically equivalent to the original construct so that it can be processed in an interoperable fashion.
+The processes of cryptographically protecting <a>credentials</a> and
+<a>presentations</a>, and verifying <a>verifiable credentials</a> and
+<a>verifiable presentations</a>, have to be deterministic, bi-directional, and
+lossless. Any verification of a <a>verifiable credential</a> or
+<a>verifiable presentation</a> has to be transformable to the generic data model
+defined in this document in a deterministic process, such that the resulting
+<a>credential</a> or <a>presentation</a> is semantically and syntactically
+equivalent to the original construct, so that it can be processed in an
+interoperable fashion.
           </li>
           <li>
 <a>Verifiable credentials</a> and <a>verifiable presentations</a> have to be

From c8741b8c674a60d4a93693b366f2443b9c9e119f Mon Sep 17 00:00:00 2001
From: Brent Zundel <brent.zundel@gmail.com>
Date: Tue, 14 Sep 2021 15:55:49 -0600
Subject: [PATCH 3/5] Update index.html

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 285b8b670..ec70e97ff 100644
--- a/index.html
+++ b/index.html
@@ -437,7 +437,7 @@ <h3>Use Cases and Requirements</h3>
         <ul>
           <li>
           <li>
-<a>Credentials</a> represent statements made by an issuer.
+<a>Credentials</a> represent statements made by an <a>issuer</a>.
           </li>
 <a>Verifiable credentials</a> represent statements made by an <a>issuer</a> in
 a tamper-evident and privacy-respecting manner.

From 4b50b3bfbe4c8975d754ba4d51ac15c08b36d728 Mon Sep 17 00:00:00 2001
From: Brent Zundel <brent.zundel@gmail.com>
Date: Tue, 14 Sep 2021 15:57:29 -0600
Subject: [PATCH 4/5] Apply suggestions from code review

commit suggestion from @dlongley per @David-Chadwick's approval

Co-authored-by: Dave Longley <dlongley@digitalbazaar.com>
---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index ec70e97ff..7b18d8074 100644
--- a/index.html
+++ b/index.html
@@ -448,8 +448,8 @@ <h3>Use Cases and Requirements</h3>
 <a>presentation</a>.
           </li>
           <li>
-Holders convert <a>presentations</a> into <a>verifiable presentations</a>,
-rendering them tamper-evident. 
+Holders transform <a>presentations</a> into <a>verifiable presentations</a>
+to render them tamper-evident. 
           </li>
           <li>
 <a>Issuers</a> can issue <a>verifiable credentials</a> about any <a>subject</a>.

From cc7befb64cfe7c2ab0e15a46a2d97e9e2ac69bed Mon Sep 17 00:00:00 2001
From: Brent Zundel <brent.zundel@gmail.com>
Date: Tue, 14 Sep 2021 15:59:31 -0600
Subject: [PATCH 5/5] Commit @TallTed's suggestion per @David-Chadwick's
 approval

Signed-off-by: Brent Zundel <brent.zundel@gmail.com>
---
 index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index 285b8b670..dcce68ab5 100644
--- a/index.html
+++ b/index.html
@@ -443,9 +443,9 @@ <h3>Use Cases and Requirements</h3>
 a tamper-evident and privacy-respecting manner.
           </li>
           <li>
-<a>Holders</a> assemble collections of <a>verifiable credentials</a> from
-different <a>issuers</a> into a single artifact, a
-<a>presentation</a>.
+<a>Holders</a> assemble collections of <a>credentials</a> and/or
+<a>verifiable credentials</a> from different <a>issuers</a> into a single
+artifact, a <a>presentation</a>.
           </li>
           <li>
 Holders convert <a>presentations</a> into <a>verifiable presentations</a>,