Reverted most of the changes to the 2nd and 3rd kinds of change listed in 7.6.2 Task Force decision today on ISSUE-47
authorcharles
Mon, 21 Oct 2013 22:45:14 +0100
changeset 46 ea903587f98e
parent 45 77898864d262
child 47 b29f6b51a034
Reverted most of the changes to the 2nd and 3rd kinds of change listed in 7.6.2 Task Force decision today on ISSUE-47
tr.html
--- a/tr.html	Fri Oct 18 03:00:41 2013 +0200
+++ b/tr.html	Mon Oct 21 22:45:14 2013 +0100
@@ -55,11 +55,12 @@
           Board 14 October 2013. This document is an editor's draft for the
           Advisory Board but does not yet fully reflect consensus. The Advisory
           Board proposed, at its 14 October meeting, recommending the content of
-          this draft (although the last version they saw was the 9 October draft)
-          as a "Last Call" draft proposed for adoption by the Advisory Committee
-          as a replacement for the existing Chapter 7. Review will take place
-          over several weeks, including the week of W3C's TPAC meeting (10-15
-          November), before a formal decision on adoption is made.</p>
+          this draft (although the last version they saw was the 9 October
+          draft) as a "Last Call" draft proposed for adoption by the Advisory
+          Committee as a replacement for the existing Chapter 7. Review will
+          take place over several weeks, including the week of W3C's TPAC
+          meeting (10-15 November), before a formal decision on adoption is
+          made.</p>
         <p>An initial version was first proposed to the W3C Advisory Board on 13
           May 2013 as a possible replacement for the <a href="http://www.w3.org/2005/10/Process-20051014/tr.html">current
             chapter 7 of the W3C process document</a>, and a <a href="http://yadi.sk/d/Zikwkr385JG8f">subsequent
@@ -502,9 +503,7 @@
     <p class="new">If 6 months elapse without significant changes to a
       specification a Working Group <em class="rfc2119">should</em> publish a
       revised Working Draft, whose status section <em class="rfc2119">should</em>
-      indicate reasons for the lack of change.
-      <meta charset="utf-8">
-    </p>
+      indicate reasons for the lack of change. </p>
     <p class="new"> </p>
     <p>To publish a revised Working draft, a Working Group <span class="from">(copied
         since this is not a new maturity level)</span> </p>
@@ -750,20 +749,28 @@
       Recommendation.</p>
     <dl>
       <dt>1. No changes to text content</dt>
-      <dd>These changes include fixing broken style sheets or invalid markup.</dd>
-      <dt>2. Corrections to references</dt>
-      <dd>Updates to references, e.g. because the original reference is outdated
-        or no longer available, that do not affect conformance to the
-        specification.</dd>
+      <dd>These changes include fixing broken links, style sheets or invalid
+        markup.</dd>
+      <dt>2. Corrections that do not affect conformance</dt>
+      <dd>Editorial changes or clarifications that do not change the technical
+        content of the specification.</dd>
       <dt>3. Corrections that do not add new features</dt>
-      <dd>These changes <span class="rfc2119">may</span> be <a href="#substantive-change">substantive
-          changes</a>, but <span class="rfc2119">must not</span> introduce new
-        features to the specification.</dd>
+      <dd>These changes <span class="rfc2119">may</span> affect conformance to
+        the Recommendation. 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>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>
+        </ul>
+      </dd>
       <dt>4. New features</dt>
     </dl>
     <p>The first two classes of change require no technical review of the
       proposed changes. A Working Group <span class="rfc2119">may</span>
-      request republication of a Recommenation for these classes of change, or
+      request republication of a Recommendation for these classes of change, or
       W3C <span class="rfc2119">may</span> republish a Recommendation with this
       class of change. The modified Recommendation is published according to the
       Team's requirements, including <a href="http://www.w3.org/Guide/pubrules">Publication