Prepare for proposed recommendation by removing CR2 markers.

Author: msporny

index.html

@@ -18,7 +18,7 @@
         group: "vc",
 
         // specification status (for example, WD, LCWD, NOTE, etc.). If in doubt use ED.
-        specStatus: "CR",
+        specStatus: "PR",
 
         // the specification's short name, as in http://www.w3.org/TR/short-name/
         shortName: "vc-data-model-2.0",
@@ -27,9 +27,9 @@
         //subtitle: "Expressing information with verifiable provenance",
 
         // if you wish the publication date to be other than today, set this
-        publishDate: "2024-12-19",
+        publishDate: "2024-3-06",
         crEnd: "2024-01-19",
-        //prEnd: "2019-10-01",
+        prEnd: "2024-4-03",
         implementationReportURI: "https://w3c.github.io/vc-data-model-2.0-test-suite/",
         //errata: "https://w3c.github.io/vc-data-model/errata.html",
         previousMaturity: "REC",
@@ -275,23 +275,6 @@
     </section>
 
     <section id='sotd'>
-      <p>
-The Working Group is actively seeking implementation feedback for this
-specification. In order to exit the Candidate Recommendation phase, the
-Working Group has set the requirement of at least two independent
-implementations for each mandatory feature in the specification. Please see
-the <a href="https://w3c.github.io/vc-data-model-2.0-test-suite/">
-implementation report</a> for more details.
-      </p>
-
-      <p class="atrisk issue"
-        title="Features with less than two independent implementations">
-Any feature with less than two independent implementations in the
-<a href="https://w3c.github.io/vc-data-model-2.0-test-suite/">
-implementation report</a> is an "at risk" feature and might be
-removed before the transition to W3C Proposed Recommendation.
-      </p>
-
       <p>
 Comments regarding this specification are welcome at any time.
 Please file issues directly on
@@ -6770,22 +6753,6 @@ <h2>Contexts, Vocabularies, Types, and Credential Schemas</h2>
       <section class="normative">
         <h3>Base Context</h3>
 
-        <p class="issue atrisk" data-number="1437" title="Hash values might change during Candidate Recommendation">
-This section lists cryptographic hash values that might change during the
-Candidate Recommendation phase based on implementer feedback that requires
-the referenced files to be modified.
-<br><br>
-The Working Group is expecting all of the terms and URLs supplied in the
-JSON-LD Context to be either stabilized, or removed, before the publication of
-this specification as a Proposed Recommendation. While that means that this
-specification could be delayed if dependencies such as [[?VC-DATA-INTEGRITY]],
-[[?VC-JOSE-COSE]], SD-JWT, [[?VC-JSON-SCHEMA]], or status list
-do not enter the Proposed Recommendation phase around the same time frame, the
-Working Group is prepared to remove the dependencies if an undue burden is
-placed on transitioning to the Recommendation phase. This is a calculated
-risk that the Working Group is taking and has a mitigation strategy in place
-to ensure the timely transition of this specification to a Recommendation.
-        </p>
         <p>
 Implementations MUST treat the base context value, located at
 `https://www.w3.org/ns/credentials/v2`, as already retrieved;
@@ -6860,13 +6827,6 @@ <h3>Base Context</h3>
       <section class="normative">
         <h3>Vocabularies</h3>
 
-        <p class="issue atrisk" title="URL values might change during Candidate Recommendation">
-This section lists URL values that might change during the Candidate
-Recommendation phase based on migration of documents to time-stamped locations,
-migration of documents to the W3C Technical Reports namespace, and/or
-implementer feedback that requires the referenced URLs to be modified.
-        </p>
-
         <p>
 Implementations that depend on RDF vocabulary processing MUST ensure that the
 following vocabulary URLs used in the base context ultimately resolve to the