--- a/tr.html Mon Jul 22 16:41:44 2013 +0200
+++ b/tr.html Mon Jul 22 18:07:03 2013 +0200
@@ -9,7 +9,7 @@
process for such changes</a>.</p>
<p>I am grateful to the W3C Advisory Board, the W3C Process Community
Group, Art Barstow, Robin Berjon, Wayne Carr, Marcos Cáceres, Tantek
Çelik, Ian Hickson, Ian Jacobs, Ralph Swick, Anne van Kesteren, and
many people I have forgotten to acknowledge for suggestions, comments
and discussions the helped me sort out my thinking, and to Ora Lassila
for the image that illustrates the normal process of a W3C
Recommendation-track document. </p>
<p>Please send comments on this document to, or participate in, the <a
href="http://www.w3.org/community/w3process/">W3C
Process Community Group</a>. Issues related to this proposal are
tracked in that group's issue tracker using the product "<a href="https://www.w3.org/community/w3process/track/products/1">Document
Lifecycle (chapter 7)</a>"</p>
Major changes:
<ul>
<li>Last Call and Candidate Recommendation have been collapsed
together. Some of the requirements are therefore enforced earlier in
the process.</li>
<li>Proposed Recommendation is no longer a separate step. Advisory
Committee review now begins at the same time as Last Call Candidate
recommendation, and ends 4 weeks after the Working group has
provisional approval for a Request to publish as a W3C
Recommendation.</li>
<li>The director is required to address AC review comments <strong>publicly</strong>,
2 weeks <em>before</em> publication of a Recommendation.</li>
<li>The chapter is about half the size it was. </li>
<li>And it is in HTML5</li>
</ul>
<p>Editorially, I have tried to rationalize requirements, and clarify
who is responsible for meeting them. I have also actively removed
advice and general statements to keep this version short.</p>
</div>
</div>
<h2>7 <a name="Reports" id="Reports">W3C Technical Report Development
Process</a></h2>
<p>The W3C technical report development process is the set of steps and
requirements followed by W3C <a href="http://www.w3.org/2005/10/Process-20051014/groups#GroupsWG">Working
- Groups</a> to standardize Web technology. The W3C technical report
development process is designed to </p>
<ul>
<li>support multiple specification development methodologies</li>
<li>maximize <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-consensus"
rel="glossary"
title="Definition of Consensus"><span
class="dfn-instance">consensus</span></a>
about the content of stable technical reports</li>
<li>ensure high technical and editorial quality</li>
<li>promote consistency among specifications</li>
<li>facilitate royalty-free, interoperable implementations of them, and</li>
<li>earn endorsement by W3C and the broader community. </li>
</ul>
<p>See also the licensing goals for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
+ Groups</a> to standardize Web technology. The W3C technical report
development process is designed to </p>
<ul>
<li>support multiple specification development methodologies</li>
<li>maximize <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-consensus"
rel="glossary"
title="Definition of Consensus"><span
class="dfn-instance">consensus</span></a>
about the content of stable technical reports</li>
<li>ensure high technical and editorial quality</li>
<li>promote consistency among specifications</li>
<li>facilitate royalty-free, interoperable implementations of , and</li>
<li>earn endorsement by W3C and the broader community. </li>
</ul>
<p>See also the licensing goals for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
2</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>].
</p>
<p>
<svg xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"
viewBox="0.00 0.00 400.00 62.00"
height="5em"
width="36em">
<g transform="scale(1 1) rotate(0) translate(4 58)" class="graph" id="graph0">
<polygon points="-4,5 -4,-58 397,-58 397,5 -4,5" stroke="white" fill="white"></polygon>
<g class="node" id="node1">
<ellipse ry="18" rx="35.9954" cy="-18" cx="36" stroke="black" fill="none"></ellipse>
<text font-size="14.00" font-family="Times,serif" y="-14.3" x="36" text-anchor="middle">FPWD</text>
</g>
<g class="node" id="node2">
<ellipse ry="18" rx="38.1938" cy="-18" cx="147" stroke="black" fill="none"></ellipse>
<text font-size="14.00" font-family="Times,serif" y="-14.3" x="147"
text-anchor="middle">HBWD</text>
</g>
<g class="edge" id="edge1">
<path d="M71.788,-18C80.2068,-18 89.3509,-18 98.251,-18" stroke="black"
fill="none"></path>
<polygon points="98.5289,-21.5001 108.529,-18 98.5289,-14.5001 98.5289,-21.5001"
stroke="black"
fill="black"></polygon>
</g>
<g class="edge" id="edge2">
<path d="M128.006,-33.916C123.052,-44.1504 129.383,-54 147,-54 158.561,-54 165.262,-49.7581 167.102,-43.9494"
stroke="black"
fill="none"></path>
<polygon points="170.571,-43.471 165.994,-33.916 163.613,-44.24 170.571,-43.471"
stroke="black"
fill="black"></polygon>
</g>
<g class="node" id="node3">
<ellipse ry="18" rx="37.8943" cy="-18" cx="260" stroke="black" fill="none"></ellipse>
<text font-size="14.00" font-family="Times,serif" y="-14.3" x="260"
text-anchor="middle">LCCR</text>
</g>
<g class="edge" id="edge3">
<path d="M183.121,-11.6719C193.029,-11.2434 203.944,-11.1413 214.332,-11.3656"
stroke="black"
fill="none"></path>
<polygon points="214.378,-14.8689 224.487,-11.6987 214.607,-7.87265 214.378,-14.8689"
stroke="black"
fill="black"></polygon>
</g>
<g class="edge" id="edge4">
<path d="M242.388,-33.916C237.793,-44.1504 243.664,-54 260,-54 270.72,-54 276.934,-49.7581 278.64,-43.9494"
stroke="black"
fill="none"></path>
<polygon points="282.114,-43.5071 277.612,-33.916 275.15,-44.2208 282.114,-43.5071"
stroke="black"
fill="black"></polygon>
</g>
<g class="edge" id="edge5">
<path d="M224.487,-24.3013C214.621,-24.7432 203.717,-24.8587 193.308,-24.6478"
stroke="black"
fill="none"></path>
<polygon points="193.226,-21.1436 183.121,-24.3281 193.006,-28.1402 193.226,-21.1436"
stroke="black"
fill="black"></polygon>
</g>
<g class="node" id="node4">
<ellipse ry="18" rx="28.6953" cy="-18" cx="363" stroke="black" fill="none"></ellipse>
<text font-size="14.00" font-family="Times,serif" y="-14.3" x="363"
text-anchor="middle">REC</text>
</g>
<g class="edge" id="edge6">
<path d="M297.749,-18C306.33,-18 315.485,-18 324.114,-18" stroke="black"
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> <br>
</p>
<h3>Table of Contents</h3>
<ul id="mozToc">
<!--mozToc h3 1 h4 2 h5 3 h6 4-->
<li><a href="#mozTocId357269">General requirements for Technical Reports</a></li>
<li><a href="#mozTocId185794">7.1 Maturity Levels</a></li>
<li><a href="#mozTocId310665">7.2 General Requirements for Advancement on
the Recommendation Track</a>
<ul>
<li><a href="#mozTocId303350">7.2.1 (from 7.6.2) Changes to a
Specification</a></li>
<li><a href="#mozTocId828599">7.2.2 Wide Review</a></li>
</ul>
</li>
<li><a href="#mozTocId89649">7.3 Reviews and Review Responsibilities</a></li>
<li><a href="#mozTocId510412">7.4 Advancing a Technical Report to
Recommendation</a>
<ul>
<li><a href="#mozTocId403357">7.4.1.a First Public Working Draft</a></li>
<li><a href="#mozTocId918390">7.4.1.b "Heartbeat" Working Draft</a></li>
<li><a href="#mozTocId200837">7.4.2 Last Call Candidate Recommendation</a></li>
<li><a href="#mozTocId840424">7.4.5 Publication of a W3C
Recommendation</a>
<ul>
<li><a href="#mozTocId978114">Publishing a Last Call Candidate
Recommendation as a W3C Recommendation</a></li>
<li><a href="#mozTocId128164">Publishing an Edited Recommendation
(See also Modifying a Recommendation below)</a></li>
<li><a href="#mozTocId889945">For all W3C Recommendations</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="#mozTocId763911">7.5 Publishing a Working Group or Interest
Group Note</a></li>
<li><a href="#mozTocId924165">7.6 Modifying a W3C Recommendation</a>
<ul>
<li><a href="#mozTocId436763">7.6.1 Errata Management</a></li>
</ul>
</li>
<li><a href="#mozTocId203654">7.7 Rescinding a W3C Recommendation</a></li>
<li><a href="#mozTocId957988">Good practices</a></li>
</ul>
<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>]
is available at the W3C Web site. W3C will make every effort to make
archival documents indefinitely available at their original address in
their original form.</p>
<p>Every document published as part of the technical report development
process <em class="rfc2119 old">must</em> <span class="from">(was in
7.8)</span> clearly indicate its <a href="#maturity-levels">maturity
level</a>, and <em id="DocumentStatus" class="rfc2119">must</em> <span
class="from">(was