Update specification to v2.0 and prep for FPWD.

msporny · msporny · commit 76589eccda67 · 2022-07-29T11:08:49.000-04:00
diff --git a/index.html b/index.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html>
   <head>
-    <title>Verifiable Credentials Data Model v1.1</title>
+    <title>Verifiable Credentials Data Model v2.0</title>
     <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
     <!--
       === NOTA BENE ===
@@ -18,7 +18,7 @@
         group: "vc",
 
         // specification status (e.g., WD, LCWD, NOTE, etc.). If in doubt use ED.
-        specStatus: "REC",
+        specStatus: "FPWD",
 
         // the specification's short name, as in http://www.w3.org/TR/short-name/
         shortName: "vc-data-model",
@@ -27,13 +27,13 @@
         //subtitle: "Expressing information with verifiable provenance",
 
         // if you wish the publication date to be other than today, set this
-        publishDate: "2022-03-03",
+        publishDate: "2022-08-04",
         //crEnd: "2019-08-21",
         //prEnd: "2019-10-01",
-        implementationReportURI: "https://w3c.github.io/vc-test-suite/implementations/",
-        errata: "https://w3c.github.io/vc-data-model/errata.html",
+        //implementationReportURI: "https://w3c.github.io/vc-test-suite/implementations/",
+        //errata: "https://w3c.github.io/vc-data-model/errata.html",
         previousMaturity: "REC",
-        previousPublishDate: "2019-11-19",
+        previousPublishDate: "2022-03-03",
 
         // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
         // and its maturity status
@@ -146,10 +146,7 @@
 
     <section id='sotd'>
       <p>
-Comments regarding this specification are welcome at any time, but readers
-should be aware that the comment period regarding this specific version of the
-document have ended and the Working Group will not be making
-substantive modifications to this version of the specification at this stage.
+Comments regarding this specification are welcome at any time.
 Please file issues directly on
 <a href="https://github.com/w3c/vc-data-model/issues/">GitHub</a>,
 or send them to
@@ -158,15 +155,6 @@
 <a href="https://lists.w3.org/Archives/Public/public-vc-comments/">archives</a>).
       </p>
 
-      <p>
-The Working Group has received implementation feedback showing that there are at
-least two implementations for each normative feature in the specification. The
-group has obtained reports from fourteen (14) 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>
-
     </section>
 
     <section class="informative">
@@ -6102,16 +6090,26 @@ <h2>IANA Considerations</h2>
       <h2>Revision History</h2>
 
       <p>
-This section contains the substantive changes that have been made since the
-publication of v1.0 of this specification as a W3C Recommendation.
+This section contains the substantive changes that have been made to this
+specification over time.
       </p>
 
       <p>
-Changes since the <a
-href="https://www.w3.org/TR/2019/REC-vc-data-model-20191119/"> Recommendation
-</a>:
+Changes since the
+<a href="https://www.w3.org/TR/2022/REC-vc-data-model-20220303/">
+v1.1 Recommendation</a>:
       </p>
+      <ul>
+        <li>
+Increment version number to v2.0 and remove prior REC-track comments.
+        </li>
+      </ul>
 
+      <p>
+Changes since the
+<a href="https://www.w3.org/TR/2019/REC-vc-data-model-20191119/">
+v1.0 Recommendation</a>:
+      </p>
       <ul>
         <li>
 Add this revision history section.
diff --git a/terms.html b/terms.html
@@ -32,7 +32,7 @@
   </dd>
   <dt><dfn data-lt="decentralized identifier documents|DID document|DID documents">decentralized identifier document</dfn></dt>
   <dd>
-Also referred to as a <strong><em>DID document</em></strong>, this is a document 
+Also referred to as a <strong><em>DID document</em></strong>, this is a document
 that is accessible using a <a>verifiable data registry</a> and contains
 information related to a specific <a>decentralized identifier</a>, such as the
 associated <a>repository</a> and public key information.
@@ -49,7 +49,7 @@
 minimum height requirement, without actually disclosing the specific height
 value. For example, the <a>subject</a> is taller than 150 centimeters.
   </dd>
-  <dt><dfn>digital signature</dfn></dt>
+  <dt><dfn class="lint-ignore">digital signature</dfn></dt>
   <dd>
 A mathematical scheme for demonstrating the authenticity of a digital message.
   </dd>
@@ -71,7 +71,8 @@
 credentials</a> they are holding. Holders store their <a>credentials</a> in
 <a>credential repositories</a>.
   </dd>
-  <dt><dfn data-lt="identities|identity's">identity</dfn></dt>
+  <dt><dfn class="lint-ignore"
+           data-lt="identities|identity's">identity</dfn></dt>
   <dd>
 The means for keeping track of <a>entities</a> across contexts. Digital
 identities enable tracking and customization of <a>entity</a> interactions
@@ -120,14 +121,14 @@
   </dd>
   <dt><dfn>selective disclosure</dfn></dt>
   <dd>
-The ability of a <a>holder</a> to make fine-grained decisions about what 
+The ability of a <a>holder</a> to make fine-grained decisions about what
 information to share.
   </dd>
   <dt><dfn data-lt="subjects|subject's">subject</dfn></dt>
   <dd>
 A thing about which <a>claims</a> are made.
   </dd>
-  <dt><dfn>user agent</dfn></dt>
+  <dt><dfn class="lint-ignore">user agent</dfn></dt>
   <dd>
 A program, such as a browser or other Web client, that mediates the
 communication between <a>holders</a>, <a>issuers</a>, and <a>verifiers</a>.
@@ -153,8 +154,8 @@
   </dd>
   <dt><dfn data-lt="verify|verified|verifying|verifiable|verifiability">verification</dfn></dt>
   <dd>
-The evaluation of whether a <a>verifiable credential</a> or <a>verifiable presentation</a> 
-is an authentic and timely statement of the issuer or presenter, respectively.  
+The evaluation of whether a <a>verifiable credential</a> or <a>verifiable presentation</a>
+is an authentic and timely statement of the issuer or presenter, respectively.
     This includes checking that: the credential (or presentation) conforms to the specification; the proof method is
 satisfied; and, if present, the status check succeeds.
 Verification of a credential does not imply evaluation of the truth
