Update to SoTD section for PR.

index.html

@@ -168,76 +168,35 @@
       </p>
 
       <p>
-The Working Group seeks implementation feedback, having set the requirement of
-at least two implementations of each feature as the exit criteria for the
-Candidate Recommendation phase. The group aims to obtain reports from two
-producers and two consumers for each feature if possible. For details, see the
-<a href="https://github.com/w3c/vc-test-suite/">test suite</a> and sample
+The Working Group has received implementation feedback such that there are
+at least two implementations for each normative feature in the specification.
+The group has obtained reports from nine (9) implementations. For details, see
+the <a href="https://github.com/w3c/vc-test-suite/">test suite</a> and
 <a href="https://w3c.github.io/vc-test-suite/implementations/">implementation report</a>.
       </p>
 
-      <p>
-The following features are considered at risk of removal due to potentially
-insufficient implementation experience (reports): <code>credentialSchema</code>
-property, <code>refreshService</code> property, <code>evidence</code> property,
-zero-knowledge proof support, <code>disputedClaim</code> property, JWT support,
-and <code>nonTransferable</code> property.
-      </p>
-
       <p>
 Changes since the last publication of this document include:
       </p>
 
       <ul>
         <li>
-Editorial modifications to group similar information together and make the
-document flow easier to navigate.
-        </li>
-        <li>
-Added a Concrete Lifecycle Example section.
-        </li>
-        <li>
-Modified conformance statements to ensure that all conformance statements are
-testable.
-        </li>
-        <li>
-Renamed the <code>subject</code> property to <code>credentialSubject</code>.
-        </li>
-        <li>
-Clarified that <a>verifiable credentials</a> and <a>verifiable presentations</a>
-MUST include the <code>@context</code> <a>property</a> and that for a
-<a>verifiable credential</a> or <a>verifiable presentation</a> to be
-<a>verifiable</a> at least one proof mechanism MUST be expressed: external or
-embedded.
-        </li>
-        <li>
-Clarified that a <a>verifiable credential</a> MUST contain the
-<code>issuer</code> and <code>issuanceDate</code> properties.
-        </li>
-        <li>
-Added significant clarifying text for Zero-Knowledge Proof and JSON Web Token
-use.
-        </li>
-        <li>
-Added a Proof Formats section.
-        </li>
-        <li>
-Clarified JSON-LD Context URLs and their ability to be cached.
+Editorial clarifications related to the support of various proof mechanisms
+by this specification.
         </li>
         <li>
-Refactored the Verification section to a be a non-normative Validation section.
+Editorial clarifications related to JSON-LD processing not being necessary for
+conforming implementations.
         </li>
         <li>
-Marked a number of features as features at risk and documenting implementation
-details that might change based on feedback from implementers.
+Editorial clarifications related to JWT processing.
         </li>
         <li>
-Promoted the Privacy Considerations, Security Considerations,
-Accessibility Considerations, and Internationalization Considerations (new)
-sections to the top level.
+Editorial clarifications related to the level of interoperability (data model
+and syntax) that this specification is designed to achieve.
         </li>
         <li>
-Moved some content out to an Implementation Guidance document.
+Editorial updates throughout the specification to ease readability.
         </li>
       </ul>