Simpler requirements on dependencies in charter, link to horizontal groups
authorcharles
Thu, 23 Apr 2015 16:54:56 -0700
changeset 153 026871e07a84
parent 152 3d43e23c5d09
child 154 c7f0dddfc5eb
Simpler requirements on dependencies in charter, link to horizontal groups
Editorial simplifications, removing activities hangovers, …
cover.html
--- a/cover.html	Thu Apr 23 16:43:32 2015 -0700
+++ b/cover.html	Thu Apr 23 16:54:56 2015 -0700
@@ -298,10 +298,10 @@
             Submissions</a>, and the <a href="#Team">Team</a> monitors work inside and outside of W3C for signs of interest. Also, W3C is
           likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to discuss topics that interest the W3C community.</li>
         <li>When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an <a href="#ACCommunication">Advisory
-            Committee mailing list</a>), the Director announces the <a href="#ActivityDevelopment">development of a proposal for one or
-            more new</a> or Interest Group or <a href="#WGCharterDevelopment">Working Group charter</a>, depending on the breadth of the
-          topic of interest. W3C Members <a href="#ActivityCreation">review</a> the proposed charters. When there is support within W3C for
-          investing resources in the topic of interest, the Director approves the group(s) and they begin their work.</li>
+            Committee mailing list</a>), the Director announces the development of a proposal for one or more new <a href="#WGCharterDevelopment">Interest
+            Group or Working Group charters</a>, depending on the breadth of the topic of interest. W3C Members <a href="#ActivityCreation">review</a>
+          the proposed charters. When there is support within W3C for investing resources in the topic of interest, the Director approves
+          the group(s) and they begin their work.</li>
         <li>There are three types of Working Group participants: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited
             Experts</a>, and <a href="#Team">Team representatives</a>. Team representatives both contribute to the technical work and help
           ensure the group's proper integration with the rest of W3C. The <a href="#WGCharter">Working Group charter</a> sets expectations
@@ -456,9 +456,9 @@
         their roles described in this document.</p>
       <p>The <dfn id="def-Director">Director</dfn> is the lead technical architect at W3C. His responsibilities are identified throughout
         this document in relevant places Some key ones include: assessing <a href="#def-Consensus" id="DirectorDecision">consensus</a>
-        within W3C for architectural choices, publication of <a href="#Reports">technical reports</a>, and new activities; appointing group
-        <a href="#GeneralChairs">Chairs</a>; "tie-breaker" for <a href="#WGAppeals">appeal of a Working Group decision</a> and deciding on
-        the outcome of formal objections; the Director is generally Chair of the <a href="#TAG">TAG</a>.</p>
+        within W3C for architectural choices, publication of <a href="#Reports">technical reports</a>, and chartering new Groups;
+        appointing group <a href="#GeneralChairs">Chairs</a>; "tie-breaker" for <a href="#WGAppeals">appeal of a Working Group decision</a>
+        and deciding on the outcome of formal objections; the Director is generally Chair of the <a href="#TAG">TAG</a>.</p>
       <p>Team administrative information such as Team salaries, detailed budgeting, and other business decisions are <a href="#Team-only">Team-only</a>,
         subject to oversight by the Host institutions.</p>
       <p><strong>Note:</strong> W3C is not currently incorporated. For legal contracts, W3C is represented by four <dfn id="hosts">"Host"
@@ -579,8 +579,8 @@
         individual <em class="rfc2119">must</em> provide the (same) <a href="#inv-expert-info">information required for an Invited Expert
           in a Working Group</a> and the nominating Advisory Committee representative <em class="rfc2119">must</em> include that
         information in the nomination. In order for an individual to be nominated as a Team representative, the nominating Advisory
-        Committee representative <em class="rfc2119">must</em> first secure approval from Team management. A nominee is <span class="rfc2119">NOT
-          REQUIRED</span> to be an employee of a Member organization, and <em class="rfc2119">may</em> be a <a href="#fellows">W3C Fellow</a>.
+        Committee representative <em class="rfc2119">must</em> first secure approval from Team management. A nominee is <em class="rfc2119">not
+          required</em> to be an employee of a Member organization, and <em class="rfc2119">may</em> be a <a href="#fellows">W3C Fellow</a>.
         Each nomination <em class="rfc2119">should</em> include a few informative paragraphs about the nominee.</p>
       <p>If, after the deadline for nominations, the number of nominees is:</p>
       <ul>
@@ -972,7 +972,7 @@
           existence. See also relevant requirements in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-join">section 4.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>On an exceptional basis, a Working or Interest Group participant <em class="rfc2119">may</em> designate a <dfn id="mtg-substitute">substitute</dfn>
-          to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the Chair. The substitute <span class="rfc2119">MAY</span>
+          to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the Chair. The substitute <em class="rfc2119">may</em>
           act on behalf of the participant, including for <a href="#Votes">votes</a>. For the substitute to vote, the participant <em class="rfc2119">must</em>
           inform the Chair in writing in advance. As a courtesy to the group, if the substitute is not well-versed in the group's
           discussions, the regular participant <em class="rfc2119">should</em> authorize another participant to act as <a href="#proxy">proxy</a>
@@ -1122,12 +1122,8 @@
             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. For example, one group's charter might specify that
-            another group is expected to review a technical report before it can become a Recommendation. For any dependencies, the charter
-            <em class="rfc2119">must</em> specify when required deliverables are expected from the other groups. The charter <em class="rfc2119">should</em>
-            set expectations about how coordination with those groups will take place; see the section on <a href="#Liaisons">liaisons with
-              other organizations</a>. Finally, the charter <em class="rfc2119">should</em> specify expected conformance to the
-            deliverables of the other groups;</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