You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h1class="title">Open Errata for the Web of Things (WoT) Architecture Specification</h1>
16
+
<dl>
17
+
<dt>Latest errata update:</dt>
18
+
<dd><spanid="date"></span>24 March 2020</dd>
19
+
<dt>Number of recorded errata:</dt>
20
+
<dd><spanid="number"></span>0</dd>
21
+
</dl>
19
22
20
23
<section>
21
24
<h2>How to Submit an Erratum?</h2>
22
-
<p>Errata are introduced and stored in the <ahref="https://github.com/w3c/wot-architecture/issues/">issue list for the WoT Thing Description GitHub repository</a>.
25
+
<p>Errata are introduced and stored in the <ahref="https://github.com/w3c/wot-architecture/issues/">issue list
26
+
for the WoT Thing Description GitHub repository</a>.
23
27
The workflow to add a new erratum is as follows:</p>
24
28
<ul>
25
29
<li>An issue is raised for a possible erratum. The label of the issue SHOULD be set to
26
-
<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>
27
-
<li>Issues labeled as <code>Editorial</code> are displayed separately, to make it easier to differentiate editorial errata from substantive ones.</li>
30
+
<code>ErratumRaised</code>. It is o.k. for an erratum to have several labels. In some, exceptional, cases,
31
+
i.e., when the erratum is very general, it is also acceptable not to have a reference to a document.
32
+
</li>
33
+
<li>Issues labeled as <code>Editorial</code> are displayed separately, to make it easier to differentiate
34
+
editorial errata from substantive ones.</li>
28
35
<li>The community discusses the issue. If it is accepted as a genuine erratum, the label <code>Errata</code>
29
36
is added to the entry and the <code>ErratumRaised</code> label should be removed. Additionally, a new
30
37
comment on the issue MAY be added, beginning with the word "Summary:" (if such a summary is useful based on
31
38
the discussion).</li>
32
39
<li>If the community rejects the issue as an erratum, the issue should be closed.</li>
33
40
<li>Each errata may be labelled as <code>Editorial</code>; editorial errata are listed separately from the
34
41
substantive ones.</li>
35
-
<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>
42
+
<li>ALL substantive errata are generally expected to have corresponding test(s), either in the form of new tests
43
+
or modifications to existing tests, or must include the rationale for why test updates are not required for
44
+
the erratum.</li>
36
45
</ul>
37
46
38
47
<p>This report contains a reference to all open issues with the label <code>Errata</code>, displayed in the
39
-
sections below. Each section collects the issues for a specific document, with a separate section for the issues not assigned to any.</p>
48
+
sections below. Each section collects the issues for a specific document, with a separate section for the issues
49
+
not assigned to any.</p>
40
50
41
51
<p>If you have problems following this process, but you want nevertheless to report an error, you can also contact
42
52
the staff contact of the Web of Things Working Group, <ahref="mailto:[email protected]">Kaz Ashimura</a>.</p>
43
53
</section>
44
-
54
+
45
55
<section>
46
56
<h2>How to maintain this Document</h2>
47
57
<p>
48
-
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:
58
+
When an errata is accepted, it should be added to this document. When doing so, the maintainers of this document
59
+
should follow the steps below:
49
60
</p>
50
61
<ol>
51
-
<li>Add the errata to the bottom of the list at the end of the document that corresponds to the nature of the errata.</li>
62
+
<li>Add the errata to the bottom of the list at the end of the document that corresponds to the nature of the
63
+
errata.</li>
52
64
<li>Increment the number of recorded errata at the top of the document.</li>
53
65
<li>Update the value of latest errata update at the top of the document</li>
54
66
</ol>
55
67
</section>
56
-
</header>
68
+
</header>
57
69
58
-
<main>
59
-
<section>
60
-
<h1>Open Errata on the "WoT Architecture" Recommendation</h1>
0 commit comments