From a355040b24ecdf20c24d8128707a88524a12c1ce Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Mon, 20 Nov 2023 11:01:06 -0500
Subject: [PATCH] Update revision history.

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

diff --git a/index.html b/index.html
index 4113931e7..c98a999a2 100644
--- a/index.html
+++ b/index.html
@@ -6649,6 +6649,139 @@ <h2>Revision History</h2>
       </p>
       <ul>
         <li>
+Many editorial updates and fixes to modernize the specification and make
+it easier to understand particular concepts.
+        </li>
+        <li>
+Add mechanism to embed enveloped VCs in VPs.
+        </li>
+        <li>
+Add verification algorithm.
+        </li>
+        <li>
+Fine tune allowable values for `issuer` property.
+        </li>
+        <li>
+Provide more concrete guidance on how to express language information as well as
+default language and direction.
+        </li>
+        <li>
+Add new conformance classes for issuer and verifier implementations.
+        </li>
+        <li>
+Add new Security Considerations regarding key management.
+        </li>
+        <li>
+Add new Privacy Considerations for trust boundaries, metadata-based correlation,
+data theft, and use of Oblivious HTTP.
+        </li>
+        <li>
+Formally define base classes and properties for vocabulary.
+        </li>
+        <li>
+Provide warnings around not using advanced JSON-LD features in order to
+maximize interoperability.
+        </li>
+        <li>
+Provide more explicit guidance around sets and arrays.
+        </li>
+        <li>
+Add support for `name` and `description` fields for issuers and credentials.
+        </li>
+        <li>
+Add security considerations around interception, replay, and spoofing attacks.
+        </li>
+        <li>
+Add JWT and SD-JWT claims to base JSON-LD Context.
+        </li>
+        <li>
+Clarify the difference between a "credential" and a "verifiable credential".
+        </li>
+        <li>
+Add section on how to ensure ecosystem compatibility.
+        </li>
+        <li>
+Add section on credential-type-specific processing.
+        </li>
+        <li>
+Add section on validation and relevance to holders.
+        </li>
+        <li>
+Add section on media type precision and interpretation.
+        </li>
+        <li>
+Ensure that `dateTimeStamp` is used for time values. Provide further guidance
+on proper usage of time values and timezones.
+        </li>
+        <li>
+Make `validFrom` optional.
+        </li>
+        <li>
+Add `relatedResource` feature.
+        </li>
+        <li>
+Make base context, vocabularies, and other items used for securing normative.
+        </li>
+        <li>
+Add `renderMethod` and `confidenceMethod` to list of reserved properties.
+        </li>
+        <li>
+Modernize examples in the specification.
+        </li>
+        <li>
+Add "Getting Started" section.
+        </li>
+        <li>
+Add table of reserved properties for properties that are not yet standardized
+or are at risk for removal.
+        </li>
+        <li>
+Restrict data model expression to JSON-LD in compact document form.
+        </li>
+        <li>
+Update ZKP section to remove older content.
+        </li>
+        <li>
+Add `termsOfUse` to presentations in v2 context.
+        </li>
+        <li>
+Add default vocabulary for undefined terms to v2 context.
+        </li>
+        <li>
+Add media types for `application/vc+ld+json` and `application/vp+ld+json`.
+        </li>
+        <li>
+Provide guidance on converting to and from conforming documents from other
+digital credential formats.
+        </li>
+        <li>
+Change reference to URI/IRI to use WHATWG URL specification.
+        </li>
+        <li>
+Add normative dependency on Data Integrity and JOSE COSE securing mechanisms.
+        </li>
+        <li>
+Rename issuanceDate/expirationDate to validFrom/validUntil.
+        </li>
+        <li>
+Add JSON Schema support and update examples to use new format.
+        </li>
+        <li>
+Clarify that `credentialSubject` values cannot be strings.
+        </li>
+        <li>
+Create more formal vocabulary document that refers to this specification.
+        </li>
+        <li>
+Define v2.0 JSON-LD Context.
+        </li>
+        <li>
+Migrate VC-JWT section to separate securing specification.
+        </li>
+        <li>
+Move Subject-Holder relationships to Verifiable Credential implementation guide.
+        </li>
+        <li>
 Increment version number to v2.0 and remove prior REC-track comments.
         </li>
         <li>