-
Notifications
You must be signed in to change notification settings - Fork 43
/
errata11.html
109 lines (99 loc) · 4.86 KB
/
errata11.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
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Open Errata for the Web of Things (WoT) Architecture 1.1 Specification</title>
<link rel="stylesheet" type="text/css" href="https://w3c.github.io/display_errata/assets/errata.css" />
</head>
<body>
<header>
<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) Architecture 1.1 Specification</h1>
<dl>
<dt>Latest errata update:</dt>
<dd><span id="date"></span>3 October 2023</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-architecture/issues/">issue list
for
the WoT Thing Description GitHub repository</a>.
The workflow to add a new erratum is as follows:</p>
<ul>
<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>
<li>Issues labeled as <code>Editorial</code> are displayed separately, to make it easier to differentiate
editorial
errata from substantive ones.</li>
<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>
<li>If the community rejects the issue as an erratum, the issue should be closed.</li>
<li>Each errata may be labelled as <code>Editorial</code>; editorial errata are listed separately from the
substantive ones.</li>
<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>
</ul>
<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>
<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:ashimura@w3.org">Kaz Ashimura</a>.</p>
</section>
<section>
<h2>How to maintain this Document</h2>
<p>
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:
</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 at the top of the document</li>
</ol>
</section>
</header>
<main>
<section>
<h1>Open Errata on the "WoT Architecture 1.1" Recommendation</h1>
<dl>
<dt>Latest Published Version:</dt>
<dd><a href="https://www.w3.org/TR/wot-thing-description/">https://www.w3.org/TR/wot-architecture/</a></dd>
<dt>Editor's draft:</dt>
<dd><a href="https://w3c.github.io/wot-thing-description/">https://w3c.github.io/wot-architecture/</a></dd>
<dt>Latest Publication Date:</dt>
<dd>05 December 2023</dd>
</dl>
<section>
<h2>Substantive Issues</h2>
</section>
<section>
<h2>Editorial Issues</h2>
</section>
</section>
</main>
<footer>
<address><a href="mailto:ashimura@w3.org" class=''>Kaz Ashimura</a>, <ashimura@w3.org>, (W3C)</address>
<div class="footer-copyright text-center ">
Copyright © {{ 'now' | date: "%Y" }} <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>