Editorial changes in response to Liam Quin's review, as per thread beginning http://lists.w3.org/Archives/Public/public-w3process/2014Mar/0020.html
authorcharles
Wed, 23 Apr 2014 18:24:23 +0200
changeset 104 41f97f342b7d
parent 103 5508dec95a6a
child 105 ca06fb9c4330
Editorial changes in response to Liam Quin's review, as per thread beginning http://lists.w3.org/Archives/Public/public-w3process/2014Mar/0020.html
tr.html
--- a/tr.html	Wed Mar 19 15:47:32 2014 +0100
+++ b/tr.html	Wed Apr 23 18:24:23 2014 +0200
@@ -97,8 +97,11 @@
       <li><a href="#further-reading">Further reading</a></li>
     </ul>
     <h3 id="rec-advance">7.1 W3C Technical Reports</h3>
+    <p>Please note that <dfn>publishing</dfn> as used in this document refers
+      to producing a version which is listed as a W3C Technical Report on its <a
+        href="http://www.w3.org/TR">Technical Reports page http://www.w3.org/TR</a>.</p>
     <p>This chapter describes the formal requirements for publishing and
-      maintaining a W3C Recommendation or Note. </p>
+      maintaining a W3C Recommendation or Note.</p>
     <p>Typically a series of Working Drafts are published, each of which refines
       a document under development to complete the scope of work envisioned by a
       Working Group's charter. For a technical specification, once review
@@ -256,6 +259,9 @@
       Interest Group, nor are their contents endorsed in any way by W3C.</p>
     <h3 id="requirements-and-definitions">7.2 General requirements and
       definitions</h3>
+    <p>Please note that <dfn>publishing</dfn> as used in this document refers
+      to producing a version which is listed as a W3C Technical Report on its <a
+        href="http://www.w3.org/TR">Technical Reports page http://www.w3.org/TR</a>.</p>
     <h4 id="general-requirements">7.2.1 General requirements for Technical
       Reports</h4>
     <p>Every document published as part of the technical report development
@@ -325,8 +331,8 @@
       <li><em class="rfc2119">should</em> document known implementation.</li>
     </ul>
     <p>For a First Public Working Draft there is no "previous maturity level",
-      so many requirements do not apply and approval is normally fairly
-      automatic.. For later stages, especially transition to Candidate or
+      so many requirements do not apply, and approval is normally fairly
+      automatic. For later stages, especially transition to Candidate or
       Proposed Recommendation, there is generally a formal review meeting to
       ensure the requirements have been met before Director's approval is given.</p>
     <h4 id="doc-reviews">7.2.3 Reviews and Review Responsibilities</h4>
@@ -407,12 +413,14 @@
       <dd>These changes <span class="rfc2119">may</span> affect conformance to
         the specification. A change that affects conformance is one that:
         <ul>
-          <li>turns conforming data, processors, or other conforming agents into
-            non-conforming agents, or</li>
-          <li>turns non-conforming agents into conforming ones, or</li>
+          <li>makes conforming data, processors, or other conforming agents
+            become non-conforming according to the new version, or</li>
+          <li>makes non-conforming data, processors, or other agents become
+            conforming, or</li>
           <li>clears up an ambiguity or under-specified part of the
-            specification in such a way that an agent whose conformance was once
-            unclear becomes clearly conforming or non-conforming.</li>
+            specification in such a way that data, a processor, or an agent
+            whose conformance was once unclear becomes clearly either conforming
+            or non-conforming.</li>
         </ul>
       </dd>
       <dt>4. New features</dt>
@@ -539,7 +547,8 @@
         4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
         Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>]. Note
       that approval is <em>expected</em> to be fairly simple compared to
-      getting approval for a transition to Candidate Recommendation.</p>
+      getting approval for a transition from Working Draft to Candidate
+      Recommendation.</p>
     <p>In addition the Working Group:</p>
     <ul>
       <li><em class="rfc2119">must</em> show that the revised specification
@@ -751,12 +760,12 @@
         Recommendation.</li>
       <li><em class="rfc2119">should</em> document known implementation.</li>
     </ul>
-    <p>In addition a Working Group requesting to rescind</p>
+    <p>In addition a Working Group requesting to rescind a Recommendation</p>
     <ul>
       <li><em class="rfc2119">must</em> show that the request to rescind has
         received <a href="#wide-review">wide review</a></li>
     </ul>
-    <p>In addition the Director, if proposing to rescind</p>
+    <p>In addition the Director, if proposing to rescind a Recommendation</p>
     <ul>
       <li><em class="rfc2119">must</em> show that the request to rescind is
         based on public comment</li>