diff --git a/index.html b/index.html
index eb967034d..e87ace79a 100644
--- a/index.html
+++ b/index.html
@@ -436,13 +436,20 @@
Use Cases and Requirements
-
+
-
+Credentials represent statements made by an issuer.
+
Verifiable credentials represent statements made by an issuer in
a tamper-evident and privacy-respecting manner.
-
-Holders assemble collections of verifiable credentials from
-different issuers into a single artifact, a
-verifiable presentation.
+Holders assemble collections of credentials and/or
+verifiable credentials from different issuers into a single
+artifact, a presentation.
+
+ -
+Holders transform presentations into verifiable presentations
+to render them tamper-evident.
-
Issuers can issue verifiable credentials about any subject.
@@ -514,6 +521,17 @@
Use Cases and Requirements
Issuers can issue revocable verifiable credentials.
-
+The processes of cryptographically protecting credentials and
+presentations, and verifying verifiable credentials and
+verifiable presentations, have to be deterministic, bi-directional, and
+lossless. Any verification of a verifiable credential or
+verifiable presentation has to be transformable to the generic data model
+defined in this document in a deterministic process, such that the resulting
+credential or presentation is semantically and syntactically
+equivalent to the original construct, so that it can be processed in an
+interoperable fashion.
+
+ -
Verifiable credentials and verifiable presentations 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,