Clarified the process for charters that take deliverables which have already had an Exclusion Opportunity in another group.
authorcharles
Sun, 10 Jul 2016 23:52:22 +0200
changeset 171 ae15ee9082dc
parent 170 598b32e0ce8e
child 172 9ba14baa7b8a
Clarified the process for charters that take deliverables which have already had an Exclusion Opportunity in another group.
See https://lists.w3.org/Archives/Public/public-w3process/2016Jul/0010.html for the proposal the change is based on. There are many threads on this topic.
cover.html
--- a/cover.html	Sun Jul 10 22:55:48 2016 +0200
+++ b/cover.html	Sun Jul 10 23:52:22 2016 +0200
@@ -998,8 +998,8 @@
           following occurs:</p>
         <ul>
           <li>the group closes, or</li>
-          <li>the Member <a href="#resignation">resigns</a> from the Working Group; this is done through the Member's Advisory Committee
-            representative.</li>
+          <li>the Member <a href="#resignation">resigns</a> from the Working Group; this is done through the Member's Advisory
+            Committee representative.</li>
         </ul>
         <h5>5.2.1.2 <dfn id="member-rep-ig">Member Representative</dfn> in an Interest Group</h5>
         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>, an individual
@@ -1053,94 +1053,157 @@
           <li>the Chair or Director withdraws the invitation to participate, or</li>
           <li>the individual <a href="#resignation">resigns</a>.</li>
         </ul>
+
         <h5>5.2.1.4 <dfn id="invited-expert-ig">Invited Expert in an Interest Group</dfn></h5>
+
         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>, the
-          participation requirements for an Invited Expert in an Interest Group are the same as those for an <a href="#invited-expert-wg">Invited
-            Expert in a Working Group</a>.</p>
+          participation requirements for an Invited Expert in an Interest Group are the same as those for an
+          <a href="#invited-expert-wg">Invited Expert in a Working Group</a>.</p>
+
         <h5>5.2.1.5 <dfn id="team-rep-wg">Team Representative in a Working Group</dfn></h5>
         <p>An individual is a Team representative in a Working Group when so designated by W3C management.</p>
         <p>A Team representative participates in a Working Group from the moment the individual joins the group until any of the following
           occurs:</p>
+
         <ul>
           <li>the group closes, or</li>
           <li>W3C management changes Team representation by sending email to the Chair, cc'ing the group mailing list.</li>
         </ul>
-        <p>The Team participates in a Working Group from the moment the Director announces the creation of the group until the group closes.</p>
+
+        <p>The Team participates in a Working Group from the moment the Director announces the creation of the group until
+          the group closes.</p>
+
         <h5>5.2.1.6 <dfn id="team-rep-ig">Team Representative in an Interest Group</dfn></h5>
-        <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>, an individual
-          is a Team representative in an Interest Group when so designated by W3C management.</p>
+
+        <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+          an individual is a Team representative in an Interest Group when so designated by W3C management.</p>
+
         <h4>5.2.2 <dfn id="WGCharterDevelopment">Working Group and Interest Group Charter Development</dfn></h4>
-        <p>W3C creates a charter based on interest from the Members and Team. The Team <em class="rfc2119">must</em> notify the Advisory
-          Committee when a charter for a new Working Group or Interest Group is in development. This is intended to raise awareness, even if
-          no formal proposal is yet available. Advisory Committee representatives <em class="rfc2119">may</em> provide feedback on the <a
-            href="#ACCommunication">Advisory Committee discussion list</a>.</p>
+
+        <p>W3C creates a charter based on interest from the Members and Team. The Team <em class="rfc2119">must</em> notify
+          the Advisory Committee when a charter for a new Working Group or Interest Group is in development. This is intended
+          to raise awareness, even if no formal proposal is yet available. Advisory Committee representatives
+          <em class="rfc2119">may</em> provide feedback on the <a href="#ACCommunication">Advisory Committee discussion list</a>.
+          </p>
+
         <p>W3C <em class="rfc2119">may</em> begin work on a Working Group or Interest Group charter at any time.</p>
+
         <h4>5.2.3 <dfn id="CharterReview">Advisory Committee Review of a Working Group or Interest Group Charter</dfn></h4>
+
         <p>The Director <em class="rfc2119">must</em> solicit <a href="#ReviewAppeal">Advisory Committee review</a> of every new or
-          substantively modified Working Group or Interest Group charter. The Director is <em class="rfc2119">not required</em> to solicit
-          Advisory Committee review prior to a charter extension or for minor changes. The review period <em class="rfc2119">must</em> be
-          at least four weeks.</p>
-        <p>The Director's Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight important changes
-          (e.g., regarding deliverables or resource allocation) and include rationale for the changes.</p>
+          substantively modified Working Group or Interest Group charter. The Director is <em class="rfc2119">not required</em>
+          to solicit Advisory Committee review prior to a charter extension or for minor changes. The review period
+          <em class="rfc2119">must</em> be at least four weeks.</p>
+
+        <p>The Director's Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight
+          important changes (e.g., regarding deliverables or resource allocation) and include rationale for the changes.</p>
+
+        <p>Transition Requests to First Public Working Draft or Candidate Recommendation will not normally be approved while a
+          Working Group's charter is undergoing or awaiting a Director's Decision on an Advisory Committee Review.</p>
+
         <h4>5.2.4 <dfn id="cfp">Call for Participation in a Working Group or Interest Group</dfn></h4>
-        <p>After Advisory Committee review of a Working Group or Interest Group charter, the Director <em class="rfc2119">may</em> issue a
-          Call for Participation to the Advisory Committee. Charters <em class="rfc2119">may</em> be amended based on review comments
-          before the Director issues a Call for Participation. </p>
-        <p>For a new group, this announcement officially creates the group. The announcement <em class="rfc2119">must</em> include a
-          reference to the <a href="#WGCharter">charter</a>, the name(s) of the group's <a href="#GeneralChairs">Chair(s)</a>, and the
-          name of the <a href="#TeamContact">Team Contact</a>.</p>
-        <p>After a Call for Participation, any <a href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited
-            Experts</a> <em class="rfc2119">must</em> be designated (or re-designated).</p>
+
+        <p>After Advisory Committee review of a Working Group or Interest Group charter, the Director <em class="rfc2119">may</em>
+          issue a Call for Participation to the Advisory Committee. Charters <em class="rfc2119">may</em> be amended based on
+          review comments before the Director issues a Call for Participation. </p>
+
+        <p>If a charter includes deliverables that continue work on documents which have previously had an
+          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="#ref-patentpolicy">PUB33</a>],
+          the Director <em class="rfc2119">must not</em> issue a call for participation less
+          than 60 days after the beginning of Advisory Committee Review of the charter.</p>
+
+        <p>For a new group, this announcement officially creates the group. The announcement <em class="rfc2119">must</em>
+          include a reference to the <a href="#WGCharter">charter</a>, the name(s) of the group's
+          <a href="#GeneralChairs">Chair(s)</a>, and the name of the <a href="#TeamContact">Team Contact</a>.</p>
+
+        <p>After a Call for Participation, any <a href="#member-rep">Member representatives</a> and
+          <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">must</em> be designated (or re-designated).</p>
+
         <p>Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> creation or substantive
           modification of a Working Group or Interest Group charter.</p>
+
         <h4>5.2.5 <dfn id="charter-extension">Working Group and Interest Group Charter Extension</dfn></h4>
-        <p>To extend a Working Group or Interest Group charter with no other substantive modifications, the Director announces the extension
-          to the Advisory Committee. The announcement <em class="rfc2119">must</em> indicate the new duration. The announcement <em class="rfc2119">must</em>
-          also include rationale for the extension, a reference to the <a href="#WGCharter">charter</a>, the name(s) of the group's <a href="#GeneralChairs">Chair(s)</a>,
+
+        <p>To extend a Working Group or Interest Group charter with no other substantive modifications, the Director announces the
+          extension to the Advisory Committee. The announcement <em class="rfc2119">must</em> indicate the new duration.
+          The announcement <em class="rfc2119">must</em> also include rationale for the extension, a reference to the
+          <a href="#WGCharter">charter</a>, the name(s) of the group's <a href="#GeneralChairs">Chair(s)</a>,
           the name of the <a href="#TeamContact">Team Contact</a>, and instructions for joining the group.</p>
-        <p>After a charter extension, Advisory Committee representatives and the Chair are <em class="rfc2119">not required</em> to
-          re-designate <a href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited Experts</a>.</p>
-        <p>Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> the extension of a Working Group
-          or Interest Group charter.</p>
+
+        <p>After a charter extension, Advisory Committee representatives and the Chair are <em class="rfc2119">not required</em>
+          to re-designate <a href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited Experts</a>.</p>
+        <p>Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> the extension of a
+          Working Group or Interest Group charter.</p>
+
         <h4>5.2.6 <dfn id="WGCharter">Working Group and Interest Group Charters</dfn></h4>
+
         <p>A Working Group or Interest Group charter <em class="rfc2119">must</em> include all of the following information.</p>
+
         <ul>
           <li>The group's mission (e.g., develop a technology or process, review the work of other groups);</li>
           <li>The scope of the group's work and criteria for success;</li>
           <li>The duration of the group (typically from six months to two years);</li>
-          <li>The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software), expected
-            milestones, and the process for the group participants to approve the release of these deliverables (including public
-            intermediate results). A charter is <em class="rfc2119">not required</em> to include the schedule for a review of another
-            group's deliverables;</li>
-          <li>Any dependencies by groups within or outside of W3C on the deliverables of this group. For any dependencies, the charter <em
-              class="rfc2119">must</em> specify the mechanisms for communication about the deliverables;</li>
-          <li>Any dependencies of this group on other groups within or outside of W3C. Such dependencies include interactions with <a href="http://www.w3.org/Guide/Charter.html#horizontal-review">W3C
-              Horizontal Groups</a>;</li>
+          <li>The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software);</li>
+          <li>Expected milestone dates where available. <strong>Note</strong>: A charter is <em class="rfc2119">not required</em>
+            to include schedules for review of other group's deliverables;</li>
+          <li>The process for the group participants to approve the release of deliverables (including intermediate results);</li>
+          <li>Any dependencies by groups within or outside of W3C on the deliverables of this group. For any dependencies,
+            the charter <em class="rfc2119">must</em> specify the mechanisms for communication about the deliverables;</li>
+          <li>Any dependencies of this group on other groups within or outside of W3C. Such dependencies include interactions
+            with <a href="http://www.w3.org/Guide/Charter.html#horizontal-review">W3C Horizontal Groups</a>;</li>
           <li>The <a href="#confidentiality-levels">level of confidentiality</a> of the group's proceedings and deliverables;</li>
           <li>Meeting mechanisms and expected frequency;</li>
-          <li>If known, the date of the first <a href="#ftf-meeting">face-to-face meeting</a>. The date of the first face-to-face meeting
-            of a proposed group <em class="rfc2119">must not</em> be sooner than <span class="time-interval">eight weeks</span> after the
-            date of the proposal.</li>
-          <li>Communication mechanisms to be employed within the group, between the group and the rest of W3C, and with the general public;</li>
+          <li>If known, the date of the first <a href="#ftf-meeting">face-to-face meeting</a>. The date of the first
+            face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than
+            <span class="time-interval">eight weeks</span> after the date of the proposal.</li>
+          <li>Communication mechanisms to be employed within the group, between the group and the rest of W3C, and with the
+            general public;</li>
           <li>An estimate of the expected time commitment from participants;</li>
-          <li>The expected time commitment and level of involvement by the Team (e.g., to track developments, write and edit technical
-            reports, develop code, or organize pilot experiments).</li>
-          <li>Intellectual property information. What are the intellectual property (including patents and copyright) considerations
-            affecting the success of the Group? In particular, is there any reason to believe that it will be difficult to meet the
-            Royalty-Free licensing goals of section 2 of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a
-              href="#ref-patentpolicy">PUB33</a>]?</li>
+          <li>The expected time commitment and level of involvement by the Team (e.g., to track developments, write and edit
+            technical reports, develop code, or organize pilot experiments).</li>
+          <li>Intellectual property information. What are the intellectual property (including patents and copyright)
+            considerations affecting the success of the Group? In particular, is there any reason to believe that it will be
+            difficult to meet the Royalty-Free licensing goals of section 2 of the
+            <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
+            [<a href="#ref-patentpolicy">PUB33</a>]?</li>
         </ul>
-        <p>See also the charter requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section 2</a> and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
-            3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
-        <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
-          including specifying that the <dfn id="ig-mail-only">only requirement for participation (by anyone) in the Interest Group is
-            subscription to the Interest Group mailing list</dfn>. This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig">public
-            participants</a>.</p>
-        <p>A charter <em class="rfc2119">may</em> include additional voting procedures, but those procedures <em class="rfc2119">must not</em>
-          conflict with the <a href="#Votes">voting requirements</a> of the Process Document.</p>
-        <p>A charter <em class="rfc2119">may</em> include provisions other than those required by this document. The charter <em class="rfc2119">should</em>
-          highlight whether additional provisions impose constraints beyond those of the W3C Process Document (e.g., limits on the number of
-          individuals in a Working Group who represent the same Member organization or group of <a href="#MemberRelated">related Members</a>).</p>
+
+        <p>See also the charter requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section 2</a>
+         and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section 3</a> of the
+         <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+
+        <p>For every Recommendation Track deliverable that continues work on a Working Draft (WD) published under any other Charter
+          (including a predecessor group of the same name), for which an 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="#ref-patentpolicy">PUB33</a>]
+          has occurred, the description of that deliverable in the proposed charter of the adopting Working Group
+          <em class="rfc2119">must</em> provide the following information:</p>
+
+        <ul>
+          <li>The title, stable URL, and publication date of the Working Draft which will serve as the basis for work on the
+            deliverable</li>
+          <li>The title, stable URL, and publication date of the most recent Working Draft which triggered an Exclusion Opportunity per the Patent Process</li>
+          <li>The stable URL of the Working Group charter under which the most recent Working Draft which triggered an Exclusion Opportunity was published.</li>
+        </ul>
+
+        <p>The Director <em class="rfc2119">must not</em> issue a call for participation less than 60 days after the beginning of
+          an Advisory Committee Review for a charter that continues work on a Working Draft for which an Exclusion Opportunity
+          has occurred.</p>
+
+        <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding
+          participation, including specifying that the <dfn id="ig-mail-only">only requirement for participation (by anyone) in
+          the Interest Group is subscription to the Interest Group mailing list</dfn>. This type of Interest Group 
+          <em class="rfc2119">may</em> have <a href="#public-participant-ig">public participants</a>.</p>
+
+        <p>A charter <em class="rfc2119">may</em> include additional voting procedures, but those procedures
+          <em class="rfc2119">must not</em> conflict with the <a href="#Votes">voting requirements</a> of the Process Document.</p>
+
+        <p>A charter <em class="rfc2119">may</em> include provisions other than those required by this document. The charter
+          <em class="rfc2119">should</em> highlight whether additional provisions impose constraints beyond those of the W3C
+          Process Document (e.g., limits on the number of individuals in a Working Group who represent the same Member organization
+          or group of <a href="#MemberRelated">related Members</a>).</p>
+
         <h4>5.2.8 <dfn id="GeneralTermination">Working Group and Interest Group Closure</dfn></h4>
         <p>A Working Group or Interest Group charter specifies a duration for the group. The Director, subject to <a href="#ACAppeal">appeal</a>
           by Advisory Committee representatives, <em class="rfc2119">may</em> close a group prior to the date specified in the charter in
@@ -1317,8 +1380,11 @@
         <em class="rfc2119">must</em> inform group Chairs and the Advisory Committee of any changes to these rules.</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="#ref-translations">PUB18</a>] is available at the W3C Web site.</p>
+
       <h4 id="transition-reqs">6.2.2 Advancement on the Recommendation Track</h4>
+
       <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> record the group's decision to request advancement.</li>
         <li><em class="rfc2119">must </em> obtain Director approval.</li>
@@ -1333,9 +1399,14 @@
         <li><em class="rfc2119">should</em> report any changes in dependencies with other groups.</li>
         <li><em class="rfc2119">should</em> provide information about implementations known to the Working Group.</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 Proposed Recommendation, there is generally a formal
-        review meeting to ensure the requirements have been met before Director's approval is given.</p>
+
+      <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 Proposed Recommendation,
+        there is usually a formal review meeting to ensure the requirements have been met before Director's approval is given.</p>
+
+      <p>Transition Requests to First Public Working Draft or Candidate Recommendation will not normally be approved while a
+        Working Group's charter is undergoing or awaiting a Director's Decision on an Advisory Committee Review.</p>
+
       <h4 id="doc-reviews">6.2.3 Reviews and Review Responsibilities</h4>
       <p>A document is available for review from the moment it is first published. Working Groups <em class="rfc2119">should</em> <a href="#formal-address">formally
           address</a> <em>any</em> substantive review comment about a technical report in a timely manner. </p>
@@ -1484,13 +1555,17 @@
       <p>If there was any <a href="#def-Dissent" rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
         to the Working Group decision to request advancement <a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em>
         <a href="#ACAppeal">appeal</a> the decision to advance the technical report.</p>
+
       <h4 id="revised-cr">6.4.1 Revising a Candidate Recommendation</h4>
-      <p>If there are any <a href="#substantive-change">substantive changes</a> made to a Candidate Recommendation other than to remove
-        features explicitly identified as "at risk", the Working Group <em class="rfc2119">must</em> obtain the Director's approval to
-        publish a revision of a Candidate Recommendation. This is because substantive changes will generally require a new 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="#ref-patentpolicy">PUB33</a>]. Note that approval is <em>expected</em> to be fairly simple compared
-        to getting approval for a transition from Working Draft to Candidate Recommendation.</p>
+
+      <p>If there are any <a href="#substantive-change">substantive changes</a> made to a Candidate Recommendation other than to
+        remove features explicitly identified as "at risk", the Working Group <em class="rfc2119">must</em> obtain the Director's
+        approval to publish a revision of a Candidate Recommendation. This is because substantive changes will generally require a
+        new 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="#ref-patentpolicy">PUB33</a>].
+        Note that approval is <em>expected</em> to be fairly simple compared to 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 meets all Working Group requirements, or explain why the
@@ -2148,8 +2223,11 @@
       <p>The notable changes include:</p>
       <h3>Current draft</h3>
       <ul>
-        <li>Added a process to make a Recommendation Obsolete.</li>
-        <li>Clarified the process to rescind a Recommendation, aligning with with obsoleting a Recommendation.</li>
+        <li>Added a process to make a Recommendation Obsolete - 6.9</a></li>
+        <li>Clarified the process to rescind a Recommendation, aligning with with obsoleting a Recommendation - 6.9</a></li>
+        <li>Clarified the process for continuing work on a specification initially developed under another charter - 
+          <a href="#CharterReview">5.2.3</a>, <a href="#cfp">5.2.4</a>, <a href="#WGCharter">5.2.6</a>,
+          <a href="#transition-reqs">6.2.2</a>.</li>
       </ul>
     </main>
   </body>