Simple fixes - link, copyright...
--- a/tr.html Tue Jul 09 16:12:18 2013 +0400
+++ b/tr.html Tue Jul 09 16:15:21 2013 +0400
@@ -1,5 +1,5 @@
<!DOCTYPE html>
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="content-type">
<title>A Rec-track Process Draft Proposal</title>
<link href="http://www.w3.org/StyleSheets/TR/base.css" type="text/css" rel="stylesheet">
<style type="text/css">
/*<![CDATA[*/
.new {color:red} .changed {color:gold}
.from {background-color: gold;color: black }
.about { margin-left: 3em; margin-right: 3em; font-size: .83em}
table { margin-left: auto; margin-right: auto }
.diagram { text-align: center; margin: 2.5em 0 }
.issue { line-height: 125% ; border: dashed red 2px; background-color: yellow }
.issue::before {content: "Issue: "}
.issue::after {content: "@@"}
.rfc2119 {font-variant:small-caps}
/*]]>*/</style>
<link href="prism.css" rel="stylesheet">
<link href="https://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet">
<!--[if lt IE 9]><script src='undefined://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
</head>
<body>
<p> </p>
<div class="head">
<p> <a href="http://www.w3.org/"><img alt="W3C" src="http://www.w3.org/Icons/w3c_home"
height="48"
width="72"></a>
</p>
<h1 class="title" id="title">Recommendation Track Process, draft proposal</h1>
<h2 id="w3c-working-draft-20-september-2012"><abbr title="World Wide Web Consortium"></abbr>Editors'
- Draft 9 July 2013</h2>
<dl>
<!--dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/HTML-longdesc">http://www.w3.org/TR/HTML-longdesc</a></dd-->
<dt>Latest editor's draft:</dt>
<dd> <a href="http://dvcs.w3.org/hg/AB/tr.html">http://dvcs.w3.org/hg/AB/tr.html</a></dd>
<dt>Editor:</dt>
<dd><a href="mailto:chaals@yandex-team.ru">Charles (McCathie) Nevile</a>,
<a href="http://www.yandex.ru">Яндекс</a>—<a href="http://yandex.com">Yandex</a></dd>
</dl>
<p class="copyright"> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2012-2013 <a href="http://www.w3.org/"><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.eu/"><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>),
+ Draft 9 July 2013</h2>
<dl>
<!--dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/HTML-longdesc">http://www.w3.org/TR/HTML-longdesc</a></dd-->
<dt>Latest editor's draft:</dt>
<dd> <a href="https://dvcs.w3.org/hg/AB/raw-file/default/tr.html">https://dvcs.w3.org/hg/AB/raw-file/default/tr.html</a></dd>
<dt>Editor:</dt>
<dd><a href="mailto:chaals@yandex-team.ru">Charles (McCathie) Nevile</a>,
<a href="http://www.yandex.ru">Яндекс</a>—<a href="http://yandex.com">Yandex</a></dd>
</dl>
<p class="copyright"> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2013 <a href="http://www.w3.org/"><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.eu/"><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. <abbr title="World Wide Web Consortium">W3C</abbr>
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
<a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-software">software
licensing</a> rules apply. </p>
<hr> </div>
<div class="noprint">
<div class="navbar">
<p>This is a revised draft proposal to replace the <a href="http://www.w3.org/2005/10/Process-20051014/tr.html">current
@@ -56,7 +56,7 @@
since notes are excluded from the requirements to move to a new maturity
level)</span></p>
<ul>
<li><em class="rfc2119">must</em> record the group's decision to request
advancement.</li>
<li><em class="rfc2119">should</em> public documentation of significant
changes to the technical report since the previous publication.</li>
</ul>
<p>Possible next steps:</p>
<ul>
<li>End state: A technical report <em class="rfc2119">may</em> remain a
Working Group Note indefinitely</li>
<li>A Working Group <em class="rfc2119">may</em> resume work on the
technical report at any time, <span class="new">at the maturity level
the specification had before publication as a Note</span></li>
</ul>
<p>A document published as a Working Group Note does not imply any licensing
requirements, unless work is resumed and it is subsequently published as a
W3C Recommendation. See also the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</p>
<h3>7.6 <a name="rec-modify" id="rec-modify">Modifying a W3C Recommendation</a></h3>
<p>The following sections discuss the management of errors and the process
for making normative changes to a Recommendation.</p>
<h4>7.6.1 Errata Management</h4>
<p>Working Groups <em class="rfc2119">must</em> track errata on an "errata
page." An errata page is a list of enumerated errors, possibly accompanied
by corrections. Each Recommendation links to an errata page; see the
Team's <a href="http://www.w3.org/Guide/pubrules">Publication Rules</a>.
The Working Group <em class="rfc2119">must</em> identify which
corrections are normative. [Editor's note: What happens when the working
group closes? Are normative changes really normative? Doesn't, or
shouldn't it depend on the type of change?]</p>
<p>Some changes are allowed for a W3C Recommendation, but most changes will
only be allowed to be made by publishing an Edited Recommendation or a new
Recommendation.</p>
<dl>
<dt>No changes to text content</dt>
<dd>These changes include fixing broken links or invalid markup. W3C <em
class="rfc2119">may</em>
do this without announcement. <span class="from">(was not clear who
could do this)</span></dd>
<dt><a href="#editorial-change">Editorial changes</a> or <a class="changed"
href="#substantive-correction">Substantive
corrections</a></dt>
<dd> A Working Group or W3C <em class="rfc2119 changed">must</em>
request a PER for this. <span class="from">(No review was required, and
this could be done in errata)</span></dd>
<dt><a href="#substantive-correction">Substantive corrections</a> that add
no new features</dt>
<dd>A Working Group <em class="rfc2119">must</em> create a Proposed
Edited Recommendation or a new Recommendation to make such changes. <span
class="from">(Was:
- W3C requires community review and timely publication, although it
appears that it could be done via errata)</span> </dd>
<dt><a href="#substantive-change">Substantive changes</a> that add New
features</dt>
<dd>A Working Group <em class="rfc2119">must</em>
<meta charset="utf-8">
follow the full process of advancing a technical report to
Recommendation to make such changes.</dd>
</dl>
<h3>7.7 <a name="rec-rescind" id="rec-rescind">Rescinding a W3C
Recommendation</a></h3>
<p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example
if the Recommendation contains many errors that conflict with a later
version or if W3C discovers burdensome patent claims that affect
implementers and cannot be resolved; see the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ W3C requires community review and timely publication, although it
appears that it could be done via errata)</span> </dd>
<dt><a href="#substantive-change">Substantive changes</a> that add New
features</dt>
<dd>A Working Group <em class="rfc2119">must</em> follow the full process
of advancing a technical report to Recommendation to make such changes.</dd>
</dl>
<h3>7.7 <a name="rec-rescind" id="rec-rescind">Rescinding a W3C
Recommendation</a></h3>
<p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example
if the Recommendation contains many errors that conflict with a later
version or if W3C discovers burdensome patent claims that affect
implementers and cannot be resolved; see the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
and in particular <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section
5</a> (bullet 10) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section
7.5</a>. <span class="changed">A Working Group </span><span class="changed"><em
class="rfc2119">may</em>
request the director to rescind a Recommendation which was a
deliverable, or the Director </span><span class="changed"><em class="rfc2119">may</em>
directly propose to rescind a Recommendation. </span><span class="from">(was