-
Notifications
You must be signed in to change notification settings - Fork 63
/
errata.html
151 lines (135 loc) · 5.87 KB
/
errata.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
<!DOCTYPE html>
<html>
<!--
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.
-->
<head>
<meta charset="UTF-8">
<title>Open Errata for the Web of Things (WoT) Thing Description Specification</title>
<link rel="stylesheet" type="text/css" href="https://w3c.github.io/display_errata/assets/errata.css" />
</head>
<body>
<p class="banner"><a accesskey="W" href="/"><img width="72" height="48" alt="W3C"
src="https://www.w3.org/Icons/w3c_home" /></a> </p>
<br />
<h1 class="title">Open Errata for the Web of Things (WoT) Thing Description Specification</h1>
<dl>
<dt>Latest errata update:</dt>
<dd><span id="date"></span>24 March 2020</dd>
<dt>Number of recorded errata:</dt>
<dd><span id="number"></span>0</dd>
</dl>
<section>
<h2>How to Submit an Erratum?</h2>
<p>
Errata are introduced and stored in the <a href="https://github.com/w3c/wot-thing-description/issues/">issue list
for the WoT Thing Description GitHub repository</a>.
The workflow to add a new erratum is as follows:
</p>
<ol>
<li>
A possible mistake is submitted as issues on GitHub, whose title MUST start
with <code>[POSSIBLE ERRATA]</code>, e.g. <code>[POSSIBLE ERRATA] This sentence is wrong</code>. Anyone can
submit the issue. The specification version MAY be indicated in the issue description.
</li>
<li>
The issue MUST be evaluated before it becomes an official errata, which is reserved for mistakes, errors and
bugs in the REC document.
</li>
<li>
Evaluation of the label MUST happen by the Thing Description Task Force of the Web of Things Working Group.
<ol>
<li>
If this Task Force is not active anymore, the Web of Things Working Group MUST evaluate it.
</li>
<li>
If the Web of Things Working Group does not exist anymore, the W3C Team or their delegated entity MUST
evaluate the submission.
</li>
</ol>
</li>
<li>
Evaluation result MUST be adding a GitHub label with text being either
<code>Official Substantive Errata TD1.0 Confirmed</code> or
<code>Official Editorial Errata TD1.0 Confirmed</code>. Note that whether the errata is substantive or editorial
depends on the errata. If there is implementation impact, it is generally
a substantive errata.
</li>
<li>
If a GitHub issue is submitted without thinking that it can be Errata, thus not contain
<code>[POSSIBLE ERRATA]</code> but turns out to be one, it CAN also obtain the label above after an evaluation
by the Thing Description Task Force of the Web of Things Working Group. Note that the delegation of the Task
Force is NOT REQUIRED to evaluate every new
issue.
</li>
<li>
The Thing Description Task Force of the Web of Things Working Group or their delegation edits the REC document
to address the errata with a GitHub Pull Request also containing
the label <code>Official Errata Fix</code>. In the same Pull Request, the Task Force or the delegation edits the
corresponding errata.html document manually based on the issue, following the instructions below in this
document.
</li>
<li>
Resolution to merge the Pull Request MUST be a Web of Things Working Group resolution or a mechanism chosen by
the delegation.
</li>
</ol>
<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 Web of Things Working Group, <a href="mailto:[email protected]">Kaz Ashimura</a>.
</p>
</section>
<section>
<h2>List of Errata on the "WoT Thing Description" Recommendation</h2>
<dl>
<dt>Latest Published Version:</dt>
<dd><a href="https://www.w3.org/TR/wot-thing-description/">https://www.w3.org/TR/wot-thing-description/</a></dd>
<dt>Editor's draft:</dt>
<dd><a href="https://w3c.github.io/wot-thing-description/">https://w3c.github.io/wot-thing-description/</a></dd>
<dt>Latest Publication Date:</dt>
<dd>2 April 2020</dd>
</dl>
<section>
<h3>Substantive Issues</h3>
<p>None</p>
</section>
<section>
<h3>Editorial Issues</h3>
<p>None</p>
</section>
</section>
<section>
<h2>How to maintain this Document</h2>
<p>
When an errata is addressed in the REC document, it should be added to this document. When doing so, the
maintainers
of this document should follow the steps below:
</p>
<ol>
<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>
<li>
Increment the number of recorded errata at the top of the document.
</li>
<li>
Update the value of latest errata update date at the top of the document.
</li>
</ol>
</section>
<footer class="page-footer font-small">
<address><a href="mailto:[email protected]">Web of Things Working Group, Thing Description Task Force</a>,
<[email protected]></address>
<div class="footer-copyright text-center py-3">
Copyright © 2024 <a href="https://www.w3.org/">World Wide Web Consortium</a>.<br /> <abbr
title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a
href="https://www.w3.org/policies/#disclaimers">liability</a>, <a
href="https://www.w3.org/policies/#trademarks">trademark</a> and <a rel="license"
href="https://www.w3.org/copyright/document-license/" title="W3C Document License">permissive license</a> rules
apply.
</div>
</footer>
</body>
</html>