--- a/tr.html Mon Sep 23 21:48:34 2013 +0200
+++ b/tr.html Mon Sep 23 22:25:20 2013 +0200
@@ -170,7 +170,7 @@
fill="none"></path>
<polygon points="324.306,-21.5001 334.306,-18 324.306,-14.5001 324.306,-21.5001"
stroke="black" fill="black"></polygon> </g> </g> </svg> </p>
- <h3><a class="mozTocH3" id="mozTocId316776"></a>Table of Contents</h3>
+ <h3>Table of Contents</h3>
<ul id="mozToc">
<!--mozToc h3 1 h4 2 h5 3 h6 4-->
<li><a href="#mozTocId316776">Table of Contents</a></li>
@@ -213,8 +213,7 @@
<li><a href="#mozTocId990936">7.7 Rescinding a W3C Recommendation</a></li>
<li><a href="#mozTocId589973">Good practices</a></li>
</ul>
- <h3><a class="mozTocH3" id="mozTocId405414"></a>General requirements for
- Technical Reports</h3>
+ <h3>General requirements for Technical Reports</h3>
<p>Every document published as part of the technical report development
process <em class="rfc2119 old">must</em> be a public document. The <a href="http://www.w3.org/TR/">index
of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-doc-list">PUB11</a>]
@@ -262,8 +261,7 @@
the translation of its technical reports. <a href="http://www.w3.org/Consortium/Translation/">Information
about translations of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-translations">PUB18</a>]
is available at the W3C Web site.<span class="from">(was in 7.8)</span></p>
- <h3><a class="mozTocH3" id="mozTocId1729"></a>7.1 <a name="maturity-levels"
- id="maturity-levels">Maturity Levels</a></h3>
+ <h3>7.1 <a name="maturity-levels" id="maturity-levels">Maturity Levels</a></h3>
<dl>
<dt><a name="RecsWD" id="RecsWD">Working Draft (WD)</a></dt>
<dd>A Working Draft is a document that W3C has published for review by the
@@ -333,9 +331,8 @@
Group, nor are their contents endorsed in any way by W3C or its members,
except to the extent that such contents happen to be consistent with some
other document which carries a higher level of endorsement.</p>
- <h3><a class="mozTocH3" id="mozTocId318562"></a>7.2 <a name="transition-reqs"
- id="transition-reqs">General Requirements for Advancement on the
- Recommendation Track</a></h3>
+ <h3>7.2 <a name="transition-reqs" id="transition-reqs">General Requirements
+ for Advancement on the Recommendation Track</a></h3>
<p>For <em>all</em> requests to advance a specification to a new maturity
level other than Note the Working Group:</p>
<ul>
@@ -367,8 +364,7 @@
<li class="new"><em class="rfc2119">should</em> document known
implementation.</li>
</ul>
- <h4><a class="mozTocH4" id="mozTocId348163"></a>7.2.2 <a id="wide-review">Wide
- Review</a></h4>
+ <h4>7.2.2 <a id="wide-review">Wide Review</a></h4>
<p>The requirements for wide review are not precisely defined by the
process. The objective is to ensure that the entire set of stakeholders of
the Web community, including the general public, have had adequate notice
@@ -396,8 +392,7 @@
receiving many detailed reviews is not necessarily the same as wide
review, since they may only represent comment from a small segment of the
relevant stakeholder community.</p>
- <h4 id="implementation-experience"><a class="mozTocH4" id="mozTocId133300"></a>7.2.3
- Implementation Experience</h4>
+ <h4 id="implementation-experience">7.2.3 Implementation Experience</h4>
<p>Implementation experience is required to show that a specification is
sufficiently clear, complete, and relevant to market needs that
independent interoperable implementations of each feature of the
@@ -414,8 +409,8 @@
<li>is there implementation experience at all levels of the
specification's ecosystem (creation, consuming, publishing…)?</li>
</ul>
- <h3><a class="mozTocH3" id="mozTocId29135"></a>7.3 <a name="doc-reviews" id="doc-reviews">Reviews
- and Review Responsibilities</a></h3>
+ <h3>7.3 <a name="doc-reviews" id="doc-reviews">Reviews and Review
+ Responsibilities</a></h3>
<p>A document is available for review from the moment it is first published.
Working Groups <em class="rfc2119">should</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
address</a> <em>any</em> substantive review comment about a technical
@@ -427,8 +422,8 @@
would cause significant compatibility problems due to existing
implementation</span>. Worthy ideas <em class="rfc2119">should</em> be
recorded even when not incorporated into a mature document.
- <h3><a class="mozTocH3" id="mozTocId412309"></a>7.4 <a name="rec-advance" id="rec-advance">Advancing
- a Technical Report to Recommendation</a></h3>
+ <h3>7.4 <a name="rec-advance" id="rec-advance">Advancing a Technical Report
+ to Recommendation</a></h3>
<p>W3C follows these steps when advancing a technical report to
Recommendation.</p>
<ol>
@@ -506,8 +501,8 @@
<li><a href="#last-call">Last Call Candidate recommendation</a>.</li>
<li><a href="#tr-end">Working Group Note</a></li>
</ul>
- <h4><a class="mozTocH4" id="mozTocId87620"></a>7.4.2 <a name="last-call" id="last-call">Last
- Call Candidate Recommendation </a></h4>
+ <h4>7.4.2 <a name="last-call" id="last-call">Last Call Candidate
+ Recommendation </a></h4>
<p>To publish a Last Call Candidate recommendation, in addition to meeting
the <a href="#transition-reqs">general requirements for advancement</a> a
Working Group</p>
@@ -561,11 +556,10 @@
<p> <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
Committee</a> representatives <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
the decision to advance the technical report.</p>
- <h4><a class="mozTocH4" id="mozTocId707682"></a>7.4.5 <a name="rec-publication"
- id="rec-publication">Publication of a W3C Recommendation</a></h4>
- <h5><a class="mozTocH5" id="mozTocId848355"></a><a name="lcrec-publication"
- id="lcrec-publication">Publishing a Last Call Candidate Recommendation
- as a W3C Recommendation</a></h5>
+ <h4>7.4.5 <a name="rec-publication" id="rec-publication">Publication of a
+ W3C Recommendation</a></h4>
+ <h5><a name="lcrec-publication" id="lcrec-publication">Publishing a Last
+ Call Candidate Recommendation as a W3C Recommendation</a></h5>
<p>To publish a Last Call Candidate Recommendation as a W3C Recommendation,
a Working Group</p>
<ul>
@@ -595,16 +589,24 @@
the transition to Last Call Candidate Recommendation. <span class="from">(was
in 7.4.3)</span> </li>
</ul>
- <p>The Director <em class="rfc2119">must</em> announce the provisional
- approval of a Request for publication of a W3C Recommendation to the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
- Committee</a>. <span class="new">The Director<em class="rfc2119">should
- not</em> provisionally approve a Request for publication of a W3C
- Recommendation less than 35 days after the publication of the Last Call
- Candidate Recommendation on which is it based. [editor's note - this is
- to allow for the patent policy exclusion period to expire]</span></p>
- <h5 id="rec-edited"><a class="mozTocH5" id="mozTocId961203"></a>Publishing
- an Edited Recommendation (See also <a href="#rec-modify">Modifying a
- Recommendation</a> below)</h5>
+ <p>The Director</p>
+ <ul>
+ <li> <em class="rfc2119">must</em> announce the provisional approval of a
+ Request for publication of a W3C Recommendation to the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+ Committee</a>. <span class="new"></span></li>
+ <li><span class="new"><em class="rfc2119">should not</em> provisionally
+ approve a Request for publication of a W3C Recommendation less than 35
+ days after the publication of the Last Call Candidate Recommendation
+ on which is it based [editor's note - this is to allow for the patent
+ policy exclusion period to expire].</span></li>
+ <li><span class="new"><em class="rfc2119">may</em> provisionally approve a
+ Recommendation with minimal implementation experience where there is a
+ compelling reason to do so. In such a case, the Director <em class="rfc2119">should</em>
+ explain the reasons for that decision. <br>
+ </span></li>
+ </ul>
+ <h5 id="rec-edited">Publishing an Edited Recommendation (See also <a href="#rec-modify">Modifying
+ a Recommendation</a> below)</h5>
<p>To publish an Edited Recommendation as a W3C Recommendation, a Working
Group</p>
<ul class="new">
@@ -615,7 +617,7 @@
<li><em class="rfc2119">should</em> document known implementation.</li>
<li><em class="rfc2119">should</em> address all errata.</li>
</ul>
- <h5><a class="mozTocH5" id="mozTocId138350"></a>For all W3C Recommendations</h5>
+ <h5>For all W3C Recommendations</h5>
<p>The Director <em class="rfc2119">must</em> announce the provisional
approval of a Request for publication of a W3C Recommendation to the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
Committee</a>.</p>
@@ -626,9 +628,8 @@
<p>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
in Advisory Committee reviews, the director <span class="new"><em class="rfc2119">must</em>
- publish the substantive content of the dissent to W3C <strong>and the
- general public</strong></span> and <em class="rfc2119">must</em> <a
- href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+ publish the substantive content of the dissent to W3C and the general
+ public</span> and <em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
address</a> the comment <span class="new">at least 14 days before
publication as a W3C Recommendation</span>. In this case the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
Committee</a> <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
@@ -642,8 +643,8 @@
an Edited Recommendation</a>, or</li>
<li><em class="rfc2119">may</em> be <a href="#rec-rescind">rescinded</a>.</li>
</ul>
- <h3><a class="mozTocH3" id="mozTocId151871"></a>7.5 <a name="tr-end" id="tr-end">Publishing
- a Working Group <span class="new">or Interest Group</span> Note</a></h3>
+ <h3>7.5 <a name="tr-end" id="tr-end">Publishing a Working Group <span class="new">or
+ Interest Group</span> Note</a></h3>
<p class="new">Working Groups and Interest Groups publish material that is
not a formal specification as Notes. This may include supporting
documentation for a specification, such as requirements, use cases,
@@ -681,12 +682,10 @@
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><a class="mozTocH3" id="mozTocId986536"></a>7.6 <a name="rec-modify" id="rec-modify">Modifying
- a W3C Recommendation</a></h3>
+ <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><a class="mozTocH4" id="mozTocId565826"></a>7.6.1 <a name="errata" id="errata">Errata
- Management</a></h4>
+ <h4>7.6.1 <a name="errata" id="errata">Errata Management</a></h4>
<p>Tracking errors is an important part of a Working Group's ongoing care of
a Recommendation; for this reason, the scope of a Working Group charter
generally allows time for work after publication of a Recommendation. In
@@ -717,8 +716,8 @@
become normative, according to the Team's requirements. For instance, the
Team might set up a mailing list per Recommendation where a Working Group
reports changes to an errata page.</p>
- <h4><a class="mozTocH4" id="mozTocId347486"></a>7.6.2 <a name="correction-classes"
- id="correction-classes">Classes of Changes to a Recommendation</a></h4>
+ <h4>7.6.2 <a name="correction-classes" id="correction-classes">Classes of
+ Changes to a Recommendation</a></h4>
<p>This document distinguishes the following classes of changes to a
Recommendation.</p>
<dl>
@@ -774,8 +773,8 @@
<p>For the fourth class of change (new features), W3C <span class="rfc2119">MUST</span>
follow the full process of <a href="#rec-advance">advancing a technical
report to Recommendation</a>.</p>
- <h3><a class="mozTocH3" id="mozTocId990936"></a>7.7 <a name="rec-rescind" id="rec-rescind">Rescinding
- a W3C Recommendation</a></h3>
+ <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
@@ -835,7 +834,7 @@
publication</span> as a Rescinded Recommendation. In this case the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
Committee</a> <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a>
the decision.</p>
- <h3><a class="mozTocH3" id="mozTocId589973"></a>Good practices</h3>
+ <h3>Good practices</h3>
<p>Refer to <a href="http://www.w3.org/2003/05/Transitions">"How to
Organize a Recommendation Track Transition"</a> in the <a href="http://www.w3.org/Guide/">Member
guide</a> for practical information about preparing for the reviews and