--- a/tr.html Tue Jul 23 00:11:46 2013 +0200
+++ b/tr.html Tue Sep 17 12:31:51 2013 -0400
@@ -16,7 +16,7 @@
in 7.8.1)</span> include a section about the status of the document. The
status section</p>
<ul>
<li><em class="rfc2119 changed">must</em> <span class="from">(was should
in 7.8.1)</span> state who developed the specification, </li>
<li><em class="rfc2119 changed">must</em> <span class="from">(was should
in 7.8.1)</span> state how to send comments or file bugs, and where
these are recorded, </li>
<li> <em class="rfc2119">should</em> explain how the technology relates
to existing international standards and related work inside or outside
W3C,</li>
<li><em class="rfc2119">should</em> <span class="from">(was in 7.8.1)</span>
include expectations about next steps, and</li>
<li><em class="rfc2119">should</em> <span class="from">(was in 7.8.1)</span>
explain or link to an explanation of significant changes from the
previous version.</li>
</ul>
<p>Every technical report published as part of the technical report
development process is edited by one or more editors appointed by a Group
Chair. It is the responsibility of these editors to ensure that the
decisions of the group are correctly reflected in subsequent drafts of the
technical report. An editor <em class="rfc2119">must</em> <span class="from">(was
in 7.8)</span> be a participant, as a Member representative, Team
representative, or Invited Expert in the group responsible for the
document(s) they are editing. </p>
<p>The Team is <em class="rfc2119">NOT REQUIRED</em> <span class="from">(was
in 7.8)</span> to publish a technical report that does not conform to
the Team's <a href="http://www.w3.org/Guide/pubrules">Publication Rules</a>
(e.g., for <a name="DocumentName" id="DocumentName">naming</a>, style,
and <a name="document-copyright" id="document-copyright">copyright
requirements</a>). These rules are subject to change by the Team from
time to time. The Team <em class="rfc2119">must</em> inform group Chairs
and the Advisory Board of any changes.</p>
<p>The primary language for W3C technical reports is English. W3C encourages
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>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
community, including W3C Members, the public, and other technical
organizations. Some, but not all, Working Drafts are meant to advance to
Recommendation; see the <a href="#DocumentStatus">document status
section</a> of a Working Draft for the group's expectations. Any
Working Draft not, or no longer, intended to advance to Recommendation <em
class="rfc2119">should</em>
<span class="from">(was in 7.5)</span> be published as a Working Group
Note. Working Drafts do not necessarily represent a consensus of the
Working Group, and do not imply any endorsement by W3C or its members
beyond agreement to work on a general area of technology.</dd>
<dt><a name="RecsCR" id="RecsCR">Last Call Candidate Recommendation
(LC/CR)</a></dt>
<dd class="changed">A Last Call Candidate Recommendation is a document
that Satisfies the Working Group's technical requirements, and has
already received wide review. W3C publishes a Last Call Candidate
Recommendation to
<ul>
<li>signal to the wider community that a final review should be done</li>
<li>formalize implementation experience</li>
<li>begin formal review by the Advisory Committee, who <em class="rfc2119">may</em>
recommend that the document be published as a W3C Recommendation,
returned to the Working Group for further work, or abandoned. <span
class="from">(was
+ 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>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
community, including W3C Members, the public, and other technical
organizations. Some, but not all, Working Drafts are meant to advance to
Recommendation; see the <a href="#DocumentStatus">document status
section</a> of a Working Draft for the group's expectations. Any
Working Draft not, or no longer, intended to advance to Recommendation <em
class="rfc2119">should</em>
<span class="from">(was in 7.5)</span> be published as a Working Group
Note. Working Drafts do not necessarily represent a consensus of the
Working Group, and do not imply any endorsement by W3C or its members
beyond agreement to work on a general area of technology.</dd>
<dt><a name="RecsCR" id="RecsCR">Last Call Candidate Recommendation
(LC/CR)</a></dt>
<dd class="changed">A Last Call Candidate Recommendation is a document
that Satisfies the Working Group's technical requirements, and has
already received wide review. W3C publishes a Last Call Candidate
Recommendation to
<ul>
<li>signal to the wider community that a final review should be done</li>
<li>gather implementation experience</li>
<li>begin formal review by the Advisory Committee, who <em class="rfc2119">may</em>
recommend that the document be published as a W3C Recommendation,
returned to the Working Group for further work, or abandoned. <span
class="from">(was
two steps)</span> </li>
</ul>
</dd>
<dd class="new"><strong>Note:</strong> Last Call Candidate Recommendation
is the state referred to in 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>]
as "Last Call Working Draft"</dd>
<dd class="new"><strong>Note:</strong> Last Call Candidate Recommendations
will normally be accepted as Recommendations. Announcement of a
different next step <em class="rfc2119">should</em> include the reasons
why the change in expectations comes at so late a stage.</dd>
<dt><a name="RecsW3C" id="RecsW3C">W3C Recommendation (REC)</a></dt>
<dd>A W3C Recommendation is a specification or set of normative guidelines
that, after extensive consensus-building, has received the endorsement
of W3C Members and the Director. W3C recommends the wide deployment of
its Recommendations as standards for the Web.</dd>
<dt><a name="WGNote" id="WGNote">Working Group Note, Interest Group Note
(NOTE) </a></dt>
<dd>A Working Group Note or Interest Group Note is published by a
chartered Working Group or Interest Group to <span class="new">provide
a stable reference for some document that is not intended to be a
normative specification, but is nevertheless useful. For example,
supporting documents such as Use case and Requirements documents, or
Design Principles, that explain what the Working Group was trying to
achieve with a specification, or non-normative 'Good Practices"
documents.</span> A Working Group <em class="rfc2119">may</em> also
publish a specification as a Note if they stop work without producing a
Recommendation. <span class="changed">A Working Group or Interest Group</span>
<em class="rfc2119">may</em> <span class="from">(was "W3C" in 7.1.4)</span>
publish a Note with or without its prior publication as a Working Draft.</dd>
<dt><a name="RescindedRec" id="RescindedRec">Rescinded Recommendation</a></dt>
<dd>A Rescinded Recommendation is an entire Recommendation that W3C no
longer endorses. See also clause 10 of the licensing requirements for
W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section
5</a> of 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>].</dd>
</dl>
<p class="new">Working Groups and Interest Groups <em class="rfc2119">may</em>
publish "Editor's drafts". Editor's drafts have no official standing
whatsoever, and do not imply consensus of a Working Group or Interest
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>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>
<li><em class="rfc2119">must</em> <span class="from">(was in 7.2)</span>
record the group's decision to request advancement.</li>
<li><em class="rfc2119">must </em><span class="from">(was repeated in
maturity levels)</span> obtain Director approval.</li>
<li><em class="rfc2119 ">must</em> <span class="from">(was in 7.2)</span>
provide public documentation of all <a href="#substantive-change">substantive
@@ -38,7 +38,7 @@
of the W3C Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
for information about the policy implications of the Candidate
Recommendation. </p>
<p>Possible next steps:</p>
<ul>
<li>Return to <a href="#hb-wd">Heartbeat Working Draft</a></li>
<li>Return to <a href="#last-call">Last Call Candidate Recommendation</a></li>
<li><a href="#rec-publication">Request Recommendation status</a> (The
expected next step)</li>
<li><a href="#tr-end">Working Group Note</a></li>
</ul>
<p class="new">If there are any <a href="#substantive-change">substantive
changes</a> or <a href="#substantive-correction">substantive
corrections</a> made to a Last Call Candidate Recommendation other than
to remove features explicitly identified as "at risk", the Working Group <em
class="rfc2119">must</em>
repeat the full process of publication as a Last Call Candidate
Recommendation before the Working Group can request Recommendation status.</p>
<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>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>
<li class="new"><em class="rfc2119">must</em> republish the document,
identifying it as the basis of a Request for Recommendation.</li>
<li><span class="changed"><em class="rfc2119">must</em> show that
independent implementations of the specification are extremely likely
to be highly interoperable. </span><span class="from">(said
preferably should be two interoperable implementations...)</span> <span
class="issue">This
requirement is liable to change. It is tracked in <a href="https://www.w3.org/community/w3process/track/issues/26">ISSUE-26</a>
and <a href="https://www.w3.org/community/w3process/track/issues/27">ISSUE-27</a></span></li>
<li><em class="rfc2119">must</em> show that the document has been <a href="#wide-review">widely
- reviewed</a></li>
<li><em class="rfc2119">must</em> show that all issues raised during Last
Call Candidate Recommendation have been formally addressed.</li>
<li><em class="rfc2119">must </em>identify any substantive issues raised
since the close of the review period by parties other than Advisory
Committee representatives <span class="from">(was in 7.3)</span></li>
<li class="new"><em class="rfc2119">must</em> document how the testing and
implementation requirements identified as part of the transition to Last
Call Candidate Recommendation have been met.</li>
<li class="new"><em class="rfc2119">must</em> identify where errata are
tracked.</li>
<li class="new"><em class="rfc2119">should</em> document known
implementation.</li>
<li><em class="rfc2119">may</em> remove features identified in the Last
Call Candidate Recommendation document as "at risk" without repeating
the transition to Last Call Candidate Recommendation. <span class="from">(was
+ reviewed</a></li>
<li><em class="rfc2119">must</em> show that all issues raised during the
Last Call Candidate Recommendation review period have been formally
addressed.</li>
<li><em class="rfc2119">must </em>identify any substantive issues raised
since the close of the review period by parties other than Advisory
Committee representatives <span class="from">(was in 7.3)</span></li>
<li class="new"><em class="rfc2119">must</em> document how the testing and
implementation requirements identified as part of the transition to Last
Call Candidate Recommendation have been met.</li>
<li class="new"><em class="rfc2119">must</em> identify where errata are
tracked.</li>
<li class="new"><em class="rfc2119">should</em> document known
implementation.</li>
<li><em class="rfc2119">may</em> remove features identified in the Last
Call Candidate Recommendation document as "at risk" without repeating
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">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">
<li><em class="rfc2119">must</em> republish the document, identifying it
as the basis of a Request for Recommendation.</li>
<li><em class="rfc2119">must</em> show that the document has been
available for effective public review.</li>
<li><em class="rfc2119">should</em> document known implementation.</li>
<li><em class="rfc2119">should</em> address all errata.</li>
</ul>
<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