From d3718acdbfba19ba566da38d4cc746a286adf419 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 22 May 2024 08:03:36 +0200 Subject: [PATCH 1/5] remove js from errata --- errata.html | 11 ----------- errata11.html | 13 +------------ 2 files changed, 1 insertion(+), 23 deletions(-) diff --git a/errata.html b/errata.html index 0da7a897..17187775 100644 --- a/errata.html +++ b/errata.html @@ -8,17 +8,6 @@ Open Errata for the Web of Things (WoT) Architecture Specification - - - - - - -
diff --git a/errata11.html b/errata11.html index 0904717d..ff6e0369 100644 --- a/errata11.html +++ b/errata11.html @@ -7,18 +7,7 @@ Open Errata for the Web of Things (WoT) Architecture 1.1 Specification - - - - - - - - +
From 0442a570f5a67bd96edfef85b1123968aac731e8 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 22 May 2024 08:06:32 +0200 Subject: [PATCH 2/5] remove gh info from head element --- errata.html | 2 +- errata11.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/errata.html b/errata.html index 17187775..1936e086 100644 --- a/errata.html +++ b/errata.html @@ -4,7 +4,7 @@ The data-githubrepo attribute provides the owner/repo name on github. For W3C repositories most of those are of the form 'w3c/XXX', although there are groups that have their own owner for their repository. --> - + Open Errata for the Web of Things (WoT) Architecture Specification diff --git a/errata11.html b/errata11.html index ff6e0369..be7de977 100644 --- a/errata11.html +++ b/errata11.html @@ -4,7 +4,7 @@ The data-githubrepo attribute provides the owner/repo name on github. For W3C repositories most of those are of the form 'w3c/XXX', although there are groups that have their own owner for their repository. --> - + Open Errata for the Web of Things (WoT) Architecture 1.1 Specification From 1f9eb69d8038799451cbc6e4bd37b5ec8459d4b3 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 22 May 2024 10:05:33 +0200 Subject: [PATCH 3/5] align footer and dates --- errata.html | 13 ++++++++++--- errata11.html | 14 ++++++++++---- 2 files changed, 20 insertions(+), 7 deletions(-) diff --git a/errata.html b/errata.html index 1936e086..e210a573 100644 --- a/errata.html +++ b/errata.html @@ -13,7 +13,7 @@

-

Open Errata for the Web of Things (WoT) Thing Description Specification

+

Open Errata for the Web of Things (WoT) Architecture Specification

Latest errata update:
@@ -50,7 +50,7 @@

Open Errata on the "WoT Architecture" Recommendation

Latest Published Version:
https://www.w3.org/TR/wot-architecture/
-
Editor’s draft:
+
Editor's draft:
https://w3c.github.io/wot-architecture/
Latest Publication Date:
2 April 2020
@@ -66,7 +66,14 @@

Editorial Issues

diff --git a/errata11.html b/errata11.html index be7de977..8c42f630 100644 --- a/errata11.html +++ b/errata11.html @@ -50,11 +50,10 @@

Open Errata on the "WoT Architecture 1.1" Recommendation

Latest Published Version:
https://www.w3.org/TR/wot-architecture/
-
Editor’s draft:
+
Editor's draft:
https://w3c.github.io/wot-architecture/
Latest Publication Date:
-
2 April 2020
- +
05 December 2023

Substantive Issues

@@ -67,7 +66,14 @@

Editorial Issues

From 75ab03254f3fba8719632478014c862d633d1f69 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 22 May 2024 18:24:41 +0200 Subject: [PATCH 4/5] align to td --- errata.html | 65 ++++++++++++++++++++++++------------------ errata11.html | 79 ++++++++++++++++++++++++++++++++------------------- 2 files changed, 88 insertions(+), 56 deletions(-) diff --git a/errata.html b/errata.html index e210a573..8e2b1763 100644 --- a/errata.html +++ b/errata.html @@ -1,9 +1,5 @@ - Open Errata for the Web of Things (WoT) Architecture Specification @@ -16,36 +12,51 @@

Open Errata for the Web of Things (WoT) Architecture Specification

Latest errata update:
-
+
24 March 2020
Number of recorded errata:
-
-
Link to all errata:
-
+
0
-
-

How to Submit an Erratum?

-

Errata are introduced and stored in the issue list for the WoT Architecture 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.
    • +
    +

    How to Submit an Erratum?

    +

    Errata are introduced and stored in the issue list for the WoT Thing Description 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), 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, 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.

    -

    If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Web of Things Working Group, Kaz Ashimura.

    -
    +

    If you have problems following this process, but you want nevertheless to report an error, you can also contact + the staff contact of the Web of Things Working Group, Kaz Ashimura.

    +
+ +
+

How to maintain this Document

+

+ When an errata is accepted, it should be added to this document. When doing so, the maintainers of this document should follow the steps below: +

+
    +
  1. Add the errata to the bottom of the list at the end of the document that corresponds to the nature of the errata.
    2. +
  2. Increment the number of recorded errata at the top of the document.
    3. +
  3. Update the value of latest errata update at the top of the document
    4. +
+
-
-
- -
+

Open Errata on the "WoT Architecture" Recommendation

Latest Published Version:
@@ -55,10 +66,10 @@

Open Errata on the "WoT Architecture" Recommendation

Latest Publication Date:
2 April 2020
-
+

Substantive Issues

-
+

Editorial Issues

diff --git a/errata11.html b/errata11.html index 8c42f630..0b032d24 100644 --- a/errata11.html +++ b/errata11.html @@ -1,9 +1,5 @@ - Open Errata for the Web of Things (WoT) Architecture 1.1 Specification @@ -16,36 +12,61 @@

Open Errata for the Web of Things (WoT) Architecture 1.1 Specification

Latest errata update:
-
+
3 October 2023
Number of recorded errata:
-
-
Link to all errata:
-
+
0
-
-

How to Submit an Erratum?

-

Errata are introduced and stored in the issue list for the WoT Architecture 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.
    • +
    +

    How to Submit an Erratum?

    +

    Errata are introduced and stored in the issue list for + the WoT Thing Description 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), 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.

    - -

    If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Web of Things Working Group, Kaz Ashimura.

    -
    + +

    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.

    + +

    If you have problems following this process, but you want nevertheless to report an error, you can also contact + the staff contact of the Web of Things Working Group, Kaz Ashimura.

    +
+ +
+

How to maintain this Document

+

+ When an errata is accepted, it should be added to this document. When doing so, the maintainers of this document + should follow the steps below: +

+
    +
  1. Add the errata to the bottom of the list at the end of the document that corresponds to the nature of the + errata.
    2. +
  2. Increment the number of recorded errata at the top of the document.
    3. +
  3. Update the value of latest errata update at the top of the document
    4. +
+
+
-
-
- -
+

Open Errata on the "WoT Architecture 1.1" Recommendation

Latest Published Version:
@@ -55,10 +76,10 @@

Open Errata on the "WoT Architecture 1.1" Recommendation

Latest Publication Date:
05 December 2023
-
+

Substantive Issues

-
+

Editorial Issues

From eb51a97f3512a9ae8e4a29760388658232ddb124 Mon Sep 17 00:00:00 2001 From: Ege Korkan Date: Wed, 22 May 2024 18:25:31 +0200 Subject: [PATCH 5/5] format document --- errata.html | 123 ++++++++++++++++++++++++++++---------------------- errata11.html | 121 ++++++++++++++++++++++++++----------------------- 2 files changed, 133 insertions(+), 111 deletions(-) diff --git a/errata.html b/errata.html index 8e2b1763..8c721523 100644 --- a/errata.html +++ b/errata.html @@ -1,30 +1,37 @@ - - - Open Errata for the Web of Things (WoT) Architecture Specification - - - -
- -
-

Open Errata for the Web of Things (WoT) Architecture Specification

-
-
Latest errata update:
-
24 March 2020
-
Number of recorded errata:
-
0
-
+ + + + Open Errata for the Web of Things (WoT) Architecture Specification + + + + +
+ +
+

Open Errata for the Web of Things (WoT) Architecture Specification

+
+
Latest errata update:
+
24 March 2020
+
Number of recorded errata:
+
0
+

How to Submit an Erratum?

-

Errata are introduced and stored in the issue list for the WoT Thing Description GitHub repository. +

Errata are introduced and stored in the issue list + for the WoT Thing Description 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.
    • + 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 @@ -32,59 +39,65 @@

    How to Submit an Erratum?

  • 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), 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.
    • +
  • 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.

+ sections below. Each section collects the issues for a specific document, with a separate section for the issues + not assigned to any.

If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Web of Things Working Group, Kaz Ashimura.

- +

How to maintain this Document

- When an errata is accepted, it should be added to this document. When doing so, the maintainers of this document should follow the steps below: + When an errata is accepted, it should be added to this document. When doing so, the maintainers of this document + should follow the steps below:

    -
  1. Add the errata to the bottom of the list at the end of the document that corresponds to the nature of the errata.
    2. +
  2. Add the errata to the bottom of the list at the end of the document that corresponds to the nature of the + errata.
  3. Increment the number of recorded errata at the top of the document.
  4. Update the value of latest errata update at the top of the document
-
+
-
-
-

Open Errata on the "WoT Architecture" Recommendation

-
-
Latest Published Version:
-
https://www.w3.org/TR/wot-architecture/
-
Editor's draft:
-
https://w3c.github.io/wot-architecture/
-
Latest Publication Date:
-
2 April 2020
+
+
+

Open Errata on the "WoT Architecture" Recommendation

+
+
Latest Published Version:
+
https://www.w3.org/TR/wot-architecture/
+
Editor's draft:
+
https://w3c.github.io/wot-architecture/
+
Latest Publication Date:
+
2 April 2020
-
-

Substantive Issues

-
-
-

Editorial Issues

-
+
+

Substantive Issues

+
+
+

Editorial Issues

-
+
+
+ + + - - - + \ No newline at end of file diff --git a/errata11.html b/errata11.html index 0b032d24..458c5514 100644 --- a/errata11.html +++ b/errata11.html @@ -1,33 +1,39 @@ - - - Open Errata for the Web of Things (WoT) Architecture 1.1 Specification - - - -
- -
-

Open Errata for the Web of Things (WoT) Architecture 1.1 Specification

-
-
Latest errata update:
-
3 October 2023
-
Number of recorded errata:
-
0
-
+ + + + Open Errata for the Web of Things (WoT) Architecture 1.1 Specification + + + + +
+ +
+

Open Errata for the Web of Things (WoT) Architecture 1.1 Specification

+
+
Latest errata update:
+
3 October 2023
+
Number of recorded errata:
+
0
+

How to Submit an Erratum?

-

Errata are introduced and stored in the issue list for +

Errata are introduced and stored in the issue list + for the WoT Thing Description 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., + 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 +
  • 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 @@ -36,19 +42,21 @@

    How to Submit an Erratum?

  • 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), either in the form of new tests or +
  • 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 + sections below. Each section collects the issues for a specific document, with a separate section for the issues + not assigned to any.

- +

If you have problems following this process, but you want nevertheless to report an error, you can also contact the staff contact of the Web of Things Working Group, Kaz Ashimura.

- +

How to maintain this Document

@@ -62,39 +70,40 @@

How to maintain this Document

  • Update the value of latest errata update at the top of the document
    • - -
    -
    -
    -

    Open Errata on the "WoT Architecture 1.1" Recommendation

    -
    -
    Latest Published Version:
    -
    https://www.w3.org/TR/wot-architecture/
    -
    Editor's draft:
    -
    https://w3c.github.io/wot-architecture/
    -
    Latest Publication Date:
    -
    05 December 2023
    +
    + +
    +
    +

    Open Errata on the "WoT Architecture 1.1" Recommendation

    +
    +
    Latest Published Version:
    +
    https://www.w3.org/TR/wot-architecture/
    +
    Editor's draft:
    +
    https://w3c.github.io/wot-architecture/
    +
    Latest Publication Date:
    +
    05 December 2023
    -
    -

    Substantive Issues

    -
    -
    -

    Editorial Issues

    -
    +
    +

    Substantive Issues

    -
    +
    +

    Editorial Issues

    +
    +
    +
    + + + - - - + \ No newline at end of file