Skip to content

Commit bbd2d3e

Browse files
ihermanmsporny
authored andcommitted
Added errata file
1 parent b461eb7 commit bbd2d3e

File tree

2 files changed

+23
-15
lines changed

2 files changed

+23
-15
lines changed

errata.html

Lines changed: 22 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
-->
77
<head data-githubrepo="w3c/vc-data-model">
88
<meta charset="UTF-8">
9-
<title>Open Errata for the Verifiable Credentials Working Group</title>
9+
<title>Open Errata for the Verifiable Credentials Data Model v2.0</title>
1010
<link rel="stylesheet" type="text/css" href="https://w3c.github.io/display_errata/assets/errata.css"/>
1111
<script src="https://www.w3.org/scripts/jquery/1.11/jquery.min.js"></script>
1212
<script src="https://w3c.github.io/display_errata/assets/moment.min.js" type="text/javascript"></script>
@@ -24,7 +24,7 @@
2424
<header>
2525
<p class="banner"><a accesskey="W" href="/"><img width="72" height="48" alt="W3C" src="https://www.w3.org/Icons/w3c_home" /></a> </p>
2626
<br />
27-
<h1 class="title">Open Errata for the Verifiable Credentials Working Group</h1>
27+
<h1 class="title">Open Errata for the Verifiable Credentials Data Model v2.0</h1>
2828
<dl>
2929
<dt>Latest errata update:</dt>
3030
<dd><span id="date"></span></dd>
@@ -38,15 +38,15 @@ <h1 class="title">Open Errata for the Verifiable Credentials Working Group</h1>
3838
<h1>How to Submit an Erratum?</h1>
3939
<p>Errata are introduced and stored in the <a href="https://github.com/w3c/vc-data-model/issues/">issue list of the group‘s GitHub repository</a>. The workflow to add a new erratum is as follows:</p>
4040
<ul>
41-
<li>An issue is raised for a possible erratum. The label of the issue SHOULD be set to “<code>ErratumRaised</code>”. It is o.k. for an erratum to have several labels. In some, exceptional, cases, i.e., when the erratum is very general, it is also acceptable not to have a reference to a document.</li>
42-
<li>Issues labeled as “<code>Editorial</code>are displayed separately, to make it easier to differentiate editorial errata from substantive ones.</li>
43-
<li>The community discusses the issue. If it is accepted as a genuine erratum, the label <code>Errata</code>is added to the entry and the “<code>ErratumRaised</code>” label should be removed. Additionally, a new comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on the discussion).</li>
44-
<li>If the community rejects the issue as an erratum, the issue should be closed.</li>
45-
<li>Each errata may be labelled as “<code>Editorial</code>”; editorial errata are listed separately from the substantive ones.</li>
46-
<li>ALL substantive errata are generally expected to have corresponding test(s) (such as a pull request in <a href='https://github.com/web-platform-tests/wpt'>web-platform-tests</a>), either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the erratum.</li>
47-
</ul>
41+
<li>An issue is raised for a possible erratum. The label of the issue SHOULD be set to “<code>PossibleErratum</code>”. One erratum might have several labels.</li>
42+
<li>The community discusses the issue. If it is accepted as a genuine erratum, the label <code>Errata</code>is added to the entry and the “<code>PossibleErratum</code>” label should be removed. Additionally, a new comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on the discussion).</li>
43+
<li>Issues labeled as “<code>Errata</code>are displayed below.</li>
44+
<li>If the community rejects the issue as an erratum, the issue should be closed (but they will not be removed from the listing below, to ensure a historical record).</li>
45+
<li>Each errata may also be labelled as “<code>Editorial</code>”; editorial errata are listed separately from the substantive ones.</li>
46+
<li>ALL substantive errata are generally expected to have corresponding test(s), either in the form of new tests or modifications to existing tests, or must include the rationale for why test updates are not required for the erratum.</li>
47+
</ul>
4848

49-
<p>This report contains a reference to all open issues with the label <code>Errata</code>, displayed in the sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.</p>
49+
<p>This report contains a reference to all open issues with the label <code>Errata</code>.</p>
5050

5151
<p>If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Working Group, <a href="mailto:ivan@w3.org">ivan</a>.</p>
5252
</section>
@@ -57,15 +57,15 @@ <h1>How to Submit an Erratum?</h1>
5757
<main>
5858
<!-- The data-erratalabel should include one label that filters the errata -->
5959
<section data-nolabel>
60-
<h1>Open Errata on the “Verifiable Credentials Data Model 1.0” Recommendation</h1>
60+
<h1>Open Errata on the “Verifiable Credentials Data Model v2.0</h1>
6161
<dl>
6262
<dt>Latest Published Version:</dt>
63-
<dd><a href="https://www.w3.org/TR/vc-data-model/">https://www.w3.org/TR/vc-data-model/</a></dd>
63+
<dd><a href="https://www.w3.org/TR/vc-data-model-2.0/">https://www.w3.org/TR/vc-data-model-2.0/</a></dd>
6464
<dt>Editor’s draft:</dt>
6565
<dd><a href="https://w3c.github.io/vc-data-model/">https://w3c.github.io/vc-data-model/</a></dd>
6666
<dt>Latest Publication Date:</dt>
67-
<dd>19 November 2019</dd>
68-
</dl>
67+
<dd>15 May 2025</dd>
68+
</dl>
6969
<section id="first">
7070
<h2>Substantive Issues</h2>
7171
</section>
@@ -77,7 +77,14 @@ <h2>Editorial Issues</h2>
7777

7878
<footer>
7979
<address><a href="mailto:ivan@w3.org" class=''>ivan</a>, &lt;ivan@w3.org&gt;, (W3C)</address>
80-
<p class="copyright"><a href="/Consortium/Legal/ipr-notice#Copyright" rel="Copyright">Copyright</a> © 2019 <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a> <sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.org/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.</p>
80+
<p class="copyright">
81+
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © <span class="todo">2025</span>
82+
World Wide Web Consortium.
83+
W3C® <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
84+
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, and
85+
<a href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document">permissive document license</a>
86+
rules apply.
87+
</p>
8188
</footer>
8289
</body>
8390
</html>

index.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,6 +172,7 @@
172172
xref: ["URL", "I18N-GLOSSARY", "INFRA", "CID"],
173173
lint: { "informative-dfn": false },
174174
maxTocLevel: 3,
175+
errata: "https://w3c.github.io/vc-data-model/errata.html",
175176
inlineCSS: true
176177
};
177178
</script>

0 commit comments

Comments
 (0)