Cleaning the Proposed Recommendation phase, review timing, etc, as per ISSUE-86
authorcharles
Fri, 14 Feb 2014 22:13:54 +0100
changeset 80 be50d35fb50f
parent 79 e9795e62d47d
child 81 da213d049976
Cleaning the Proposed Recommendation phase, review timing, etc, as per ISSUE-86
tr.html
--- a/tr.html	Fri Feb 14 22:06:41 2014 +0100
+++ b/tr.html	Fri Feb 14 22:13:54 2014 +0100
@@ -683,12 +683,13 @@
     <p>In addition to meeting the <a href="#transition-reqs">general
         requirements for advancement</a>,</p>
     <ul>
-      <li>The Director <em class="rfc2119">must</em> announce the Request for
-        publication of a Proposed Recommendation to the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
-          Committee</a>, and</li>
-      <li>The deadline for Advisory Committee review of the technical report <em
-          class="rfc2119">must</em> be <strong>at least</strong> 28 days after
-        the publication of the Proposed Recommendation.</li>
+      <li>The status information <span class="rfc2119">must</span> specify the
+        deadline for Advisory Committee review, which <em class="rfc2119">must</em>
+        be <strong>at least</strong> 28 days after the publication of the
+        Proposed Recommendation and <span class="rfc2119">should</span> be at
+        least 10 days after the end of the last Exclusion Opportunity per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
+          4</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>].</li>
     </ul>
     <p>a Working Group</p>
     <ul>
@@ -712,19 +713,13 @@
       <li><em class="rfc2119">must</em> announce the Request for publication of
         a Proposed Recommendation to the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
           Committee</a>, and</li>
-      <li>The deadline for Advisory Committee review of the technical report <em
-          class="rfc2119">must</em> be <strong>at least</strong> 28 days after
-        the publication of the Proposed Recommendation.</li>
-      <li> <span><em class="rfc2119">should not</em>&nbsp; approve a Request
-          for publication of a Proposed Recommendation less than 35 days after
-          the publication of the Candidate Recommendation on which is it based
-          [editor's note - this is to allow for the patent policy exclusion
-          period to expire], and </span></li>
-      <li><span><em class="rfc2119">may</em>&nbsp; approve a Proposed
-          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>
+      <li><span><em class="rfc2119">may</em> approve a Proposed 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. </span></li>
     </ul>
+    <ul>
+    </ul>
     <p>Possible Next Steps</p>
     <ul>
       <li>Return to <a href="#hb-wd">Working Draft</a></li>