From b4c52a3076a0c3930563bae56ed99a9c256b6c54 Mon Sep 17 00:00:00 2001 From: Ivan Herman Date: Fri, 25 Apr 2025 08:39:33 +0200 Subject: [PATCH 1/3] Added errata file --- errata.html | 37 ++++++++++++++++++++++--------------- index.html | 1 + 2 files changed, 23 insertions(+), 15 deletions(-) diff --git a/errata.html b/errata.html index 945cdc09e..7987d48f3 100644 --- a/errata.html +++ b/errata.html @@ -6,7 +6,7 @@ --> - Open Errata for the Verifiable Credentials Working Group + Open Errata for the Verifiable Credentials Data Model v2.0 @@ -24,7 +24,7 @@

-

Open Errata for the Verifiable Credentials Working Group

+

Open Errata for the Verifiable Credentials Data Model v2.0

Latest errata update:
@@ -38,15 +38,15 @@

Open Errata for the Verifiable Credentials Working Group

How to Submit an Erratum?

Errata are introduced and stored in the issue list of the group‘s GitHub repository. The workflow to add a new erratum is as follows:

    -
  • An issue is raised for a possible erratum. The label of the issue SHOULD be set to “ErratumRaised”. 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.
    • -
  • Issues labeled as “Editorial” are displayed separately, to make it easier to differentiate editorial errata from substantive ones.
    • -
  • The community discusses the issue. If it is accepted as a genuine erratum, the label “Errata” is added to the entry and the “ErratumRaised” 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).
    • -
  • If the community rejects the issue as an erratum, the issue should be closed.
    • -
  • Each errata may be labelled as “Editorial”; editorial errata are listed separately from the substantive ones.
    • -
  • ALL substantive errata are generally expected to have corresponding test(s) (such as a pull request in web-platform-tests), 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.
    • -
+
  • An issue is raised for a possible erratum. The label of the issue SHOULD be set to “PossibleErratum”. One erratum might have several labels.
    • +
  • The community discusses the issue. If it is accepted as a genuine erratum, the label “Errata” is added to the entry and the “PossibleErratum” 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).
    • +
  • Issues labeled as “Errata” are displayed below.
    • +
  • 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).
    • +
  • Each errata may also be labelled as “Editorial”; editorial errata are listed separately from the substantive ones.
    • +
  • 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.
    • + -

    This report contains a reference to all open issues with the label Errata, 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.

    +

    This report contains a reference to all open issues with the label Errata.

    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, ivan.

    @@ -57,15 +57,15 @@

    How to Submit an Erratum?

    -

    Open Errata on the “Verifiable Credentials Data Model 1.0” Recommendation

    +

    Open Errata on the “Verifiable Credentials Data Model v2.0

    Latest Published Version:
    -
    https://www.w3.org/TR/vc-data-model/
    +
    https://www.w3.org/TR/vc-data-model-2.0/
    Editor’s draft:
    https://w3c.github.io/vc-data-model/
    Latest Publication Date:
    -
    19 November 2019
    -
    +
    15 May 2025
    +

    Substantive Issues

    @@ -77,7 +77,14 @@

    Editorial Issues

    diff --git a/index.html b/index.html index e76dd2149..bfe902c8a 100644 --- a/index.html +++ b/index.html @@ -172,6 +172,7 @@ xref: ["URL", "I18N-GLOSSARY", "INFRA", "CID"], lint: { "informative-dfn": false }, maxTocLevel: 3, + errata: "https://w3c.github.io/vc-data-model/errata.html", inlineCSS: true }; From d1ab8ca53d0d9abbc9262847f19732aac0f90e0f Mon Sep 17 00:00:00 2001 From: Ivan Herman Date: Fri, 25 Apr 2025 08:48:38 +0200 Subject: [PATCH 2/3] missing quote --- errata.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/errata.html b/errata.html index 7987d48f3..fbf7c225d 100644 --- a/errata.html +++ b/errata.html @@ -57,7 +57,7 @@

    How to Submit an Erratum?

    -

    Open Errata on the “Verifiable Credentials Data Model v2.0

    +

    Open Errata on the “Verifiable Credentials Data Model v2.0”

    Latest Published Version:
    https://www.w3.org/TR/vc-data-model-2.0/
    From 852561b344f909ae0572a4affe167749f31ab5ce Mon Sep 17 00:00:00 2001 From: Ivan Herman Date: Fri, 25 Apr 2025 09:00:43 +0200 Subject: [PATCH 3/3] moved the errata statement to a better place --- index.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/index.html b/index.html index bfe902c8a..9b8948955 100644 --- a/index.html +++ b/index.html @@ -31,7 +31,7 @@ crEnd: "2025-01-19", prEnd: "2025-4-17", implementationReportURI: "https://w3c.github.io/vc-data-model-2.0-test-suite/", - //errata: "https://w3c.github.io/vc-data-model/errata.html", + errata: "https://w3c.github.io/vc-data-model/errata.html", previousMaturity: "REC", previousPublishDate: "2022-03-03", @@ -172,7 +172,6 @@ xref: ["URL", "I18N-GLOSSARY", "INFRA", "CID"], lint: { "informative-dfn": false }, maxTocLevel: 3, - errata: "https://w3c.github.io/vc-data-model/errata.html", inlineCSS: true };