Skip to content

Commit

Permalink
Merge pull request #946 from w3c/ege-errata-fixes
Browse files Browse the repository at this point in the history 
Fixes to Errata Documents
  • Loading branch information
@sebastiankb
sebastiankb authored Jun 5, 2024
2 parents 270d6d2 + eb51a97 commit 0205e37
Show file tree
Hide file tree
Showing 2 changed files with 188 additions and 143 deletions.
162 changes: 91 additions & 71 deletions errata.html
View file
Original file line number Diff line number Diff line change
@@ -1,83 +1,103 @@
<!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 data-githubrepo="w3c/wot-architecture">
<meta charset="UTF-8">
<title>Open Errata for the Web of Things (WoT) Architecture Specification</title>
<link rel="stylesheet" type="text/css" href="https://w3c.github.io/display_errata/assets/errata.css"/>
<script src="https://www.w3.org/scripts/jquery/1.11/jquery.min.js"></script>
<script src="https://w3c.github.io/display_errata/assets/moment.min.js" type="text/javascript"></script>
<script src="https://w3c.github.io/display_errata/assets/errata.js" type="text/javascript"></script>
<script src="https://www.w3.org/scripts/underscore/1.8/underscore-min.js" type="text/javascript"></script>
<script src="https://w3c.github.io/display_errata/assets/toc.js" type="text/javascript"></script>

<style type="text/css">
.todo {
background-color: yellow
}
</style>
</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) Thing Description Specification</h1>
<dl>
<dt>Latest errata update:</dt>
<dd><span id="date"></span></dd>
<dt>Number of recorded errata:</dt>
<dd><span id="number"></span></dd>
<dt>Link to all errata:</dt>
<dd><span id="errata_link"></span></dd>
</dl>
<head>
<meta charset="UTF-8">
<title>Open Errata for the Web of Things (WoT) Architecture Specification</title>
<link rel="stylesheet" type="text/css" href="https://w3c.github.io/display_errata/assets/errata.css" />
</head>

<section data-notoc>
<h1>How to Submit an Erratum?</h1>
<p>Errata are introduced and stored in the <a href="https://github.com/w3c/wot-architecture/issues/">issue list for the WoT Architecture 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) (such as a pull request in <a href='https://github.com/web-platform-tests/wpt'>web-platform-tests</a>), 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>
<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 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-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>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:[email protected]">Kaz Ashimura</a>.</p>
</section>
</header>
<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>

<div class="toc" id="toc"></div>
<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>
<!-- The data-erratalabel should include one label that filters the errata -->
<section data-nolabel>
<h1>Open Errata on the "WoT Architecture" Recommendation</h1>
<dl>
<dt>Latest Published Version:</dt>
<dd><a href="https://www.w3.org/TR/wot-architecture/">https://www.w3.org/TR/wot-architecture/</a></dd>
<dt>Editor’s draft:</dt>
<dd><a href="https://w3c.github.io/wot-architecture/">https://w3c.github.io/wot-architecture/</a></dd>
<dt>Latest Publication Date:</dt>
<dd>2 April 2020</dd>
<main>
<section>
<h1>Open Errata on the "WoT Architecture" Recommendation</h1>
<dl>
<dt>Latest Published Version:</dt>
<dd><a href="https://www.w3.org/TR/wot-architecture/">https://www.w3.org/TR/wot-architecture/</a></dd>
<dt>Editor's draft:</dt>
<dd><a href="https://w3c.github.io/wot-architecture/">https://w3c.github.io/wot-architecture/</a></dd>
<dt>Latest Publication Date:</dt>
<dd>2 April 2020</dd>
</dl>
<section id="first">
<h2>Substantive Issues</h2>
</section>
<section id="last">
<h2>Editorial Issues</h2>
</section>
<section>
<h2>Substantive Issues</h2>
</section>
<section>
<h2>Editorial Issues</h2>
</section>
</main>
</section>
</main>

<footer>
<address><a href="mailto:[email protected]" class=''>Kaz Ashimura</a>, &lt;[email protected]&gt;, (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>

<footer>
<address><a href="mailto:[email protected]" class=''>Kaz Ashimura</a>, &lt;[email protected]&gt;, (W3C)</address>
<p class="copyright"><a href="/Consortium/Legal/ipr-notice#Copyright" rel="Copyright">Copyright</a> © 2020 <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a> <sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.org/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved.</p>
</footer>
</body>
</html>
</html>
Loading

0 comments on commit 0205e37

Please sign in to comment.