--- a/cover.html Thu Aug 14 12:33:02 2014 +0200
+++ b/cover.html Thu Aug 14 13:30:38 2014 +0200
@@ -115,8 +115,8 @@
Policies for W3C Groups</a></li>
<li class="tocline2"><a href="#dissemination" class="tocxref">4
Dissemination Policies</a></li>
- <li class="tocline2"><a href="#Activities" class="tocxref">5
- Activities</a></li>
+ <li class="tocline2"><s><a href="#chapterActivities" class="tocxref">5
+ Activities</a></s></li>
<li class="tocline2"><a href="#GAGeneral" class="tocxref">6 Working
Groups, Interest Groups, and Coordination Groups</a></li>
<li class="tocline2"><a href="#Reports" class="tocxref">7 W3C
@@ -232,21 +232,6 @@
</li>
</ul>
</li>
- <li class="tocline2"><a href="#Activities">5 Activities</a>
- <ul class="toc">
- <li class="tocline3"><a href="#ActivityDevelopment">5.1 Activity
- Proposal Development</a></li>
- <li class="tocline3"><a href="#ActivityCreation">5.2 Advisory
- Committee Review of an Activity Proposal</a></li>
- <li class="tocline3"><a href="#ActivityModification">5.3
- Modification of an Activity</a></li>
- <li class="tocline3"><a href="#ActivityExtension">5.4 Extension of
- an Activity</a></li>
- <li class="tocline3"><a href="#ActivityTermination">5.5 Activity
- Closure</a></li>
- <li class="tocline3"><a href="#BPCreation">5.6 Activity Proposals</a></li>
- </ul>
- </li>
<li class="tocline2"><a href="#GAGeneral">6 Working Groups, Interest
Groups, and Coordination Groups</a>
<ul class="toc">
@@ -1305,827 +1290,780 @@
Patent
Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] for information
about obligations remaining after resignation from certain groups.</p>
- <h2>4 <a id="dissemination">Dissemination Policies</a></h2>
- <p>The Team is responsible for managing communication within W3C and with
- the general public (e.g., news services, press releases, managing the
- Web site and access privileges, and managing calendars). Members <span
- class="rfc2119">SHOULD</span> solicit review by the Team prior to
- issuing press releases about their work within W3C.</p>
- <p>The Team makes every effort to ensure the persistence and availability
- of the following public information:</p>
- <ul>
- <li><a href="#Reports">W3C technical reports</a> whose publication has
- been approved by the Director. Per the Membership Agreement, W3C
- technical reports (and software) are available free of charge to the
- general public; (refer to the <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
- Document License</a> [<a href="#ref-doc-license">PUB18</a>]).</li>
- <li>A <a href="http://www.w3.org/Consortium/mission">mission statement</a>
- [<a href="#ref-mission">PUB15</a>] that explains the purpose and
- mission of W3C, the key benefits for Members, and the organizational
- structure of W3C.</li>
- <li>Legal documents, including the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
- Agreement</a> [<a href="#ref-member-agreement">PUB6</a>]) and
- documentation of any legal commitments W3C has with other entities.</li>
- <li>The Process Document.</li>
- <li>Public results of W3C Activities and <a href="#GAEvents">Workshops</a>.</li>
- </ul>
- <p>To keep the Members abreast of W3C meetings, Workshops, and review
- deadlines, the Team provides them with a regular (e.g., weekly) news
- service and maintains a <a href="http://www.w3.org/Member/Eventscal">calendar</a>
- [<a href="#ref-calendar">MEM3</a>] of official W3C events. Members are
- encouraged to send schedule and event information to the Team for
- inclusion on this calendar.</p>
- <h3>4.1 <a id="confidentiality-levels">Confidentiality Levels</a></h3>
- <p>There are three principal levels of access to W3C information (on the
- W3C Web site, in W3C meetings, etc.): public, Member-only, and
- Team-only.</p>
- <p>While much information made available by W3C is public, <a id="Member-only">"Member-only"
- information</a> is available to authorized parties only, including
- representatives of Member organizations, <a href="#invited-expert-wg">Invited
- Experts</a>, the Advisory Board, the TAG, and the Team. For example,
- the <a href="#WGCharter">charter</a> of some Working Groups may specify
- a Member-only confidentiality level for group proceedings.</p>
- <p><a id="Team-only">"Team-only" information</a> is available to the Team
- and other authorized parties.</p>
- <p>Those authorized to access Member-only and Team-only information:</p>
- <ul>
- <li><span class="rfc2119">MUST</span> treat the information as
- confidential within W3C,</li>
- <li><span class="rfc2119">MUST</span> use reasonable efforts to maintain
- the proper level confidentiality, and</li>
- <li><span class="rfc2119">MUST NOT</span> release this information to
- the general public or press.</li>
- </ul>
- <p>The Team <span class="rfc2119">MUST</span> provide mechanisms to
- protect the confidentiality of Member-only information and ensure that
- authorized parties have proper access to this information. Documents <span
- class="rfc2119">SHOULD</span> clearly indicate whether they require
- Member-only confidentiality. Individuals uncertain of the
- confidentiality level of a piece of information <span class="rfc2119">SHOULD</span>
- contact the Team.</p>
- <p>Advisory Committee representatives <span class="rfc2119">MAY</span>
- authorize Member-only access to <a href="#member-rep">Member
- representatives</a> and other individuals employed by the Member who
- are considered appropriate recipients. For instance, it is the
- responsibility of the Advisory Committee representative and other
- employees and official representatives of the organization to ensure
- that Member-only news announcements are distributed for internal use
- only within their organization. Information about Member mailing lists
- is available in the <a href="http://www.w3.org/Member/Intro">New Member
- Orientation</a>.</p>
- <h4>4.1.1 <a id="confidentiality-change">Changing Confidentiality Level</a></h4>
- <p>As a benefit of membership, W3C provides some Team-only and Member-only
- channels for certain types of communication. For example, Advisory
- Committee representatives can send <a href="#ACReview">reviews</a> to a
- Team-only channel. However, for W3C processes with a significant public
- component, such as the technical report development process, it is also
- important for information that affects decision-making to be publicly
- available. The Team <span class="rfc2119">MAY</span> need to
- communicate Team-only information to a Working Group or the public.
- Similarly, a Working Group whose proceedings are Member-only <span class="rfc2119">MUST</span>
- make public information pertinent to the technical report development
- process.</p>
- <p>This document clearly indicates which information <span class="rfc2119">MUST</span>
- be available to Members or the public, even though that information was
- initially communicated on Team-only or Member-only channels. Only the
- Team and parties authorized by the Team change the level of
- confidentiality of this information. When doing so:</p>
- <ol>
- <li>The Team <span class="rfc2119">MUST</span> use a version of the
- information that was expressly provided by the author for the new
- confidentiality level. In Calls for Review and other similar messages,
- the Team <span class="rfc2119">SHOULD</span> remind recipients to
- provide such alternatives.</li>
- <li>The Team <span class="rfc2119">MUST NOT</span> attribute the
- version for the new confidentiality level to the author without the
- author's consent.</li>
- <li>If the author has not conveyed to the Team a version that is
- suitable for another confidentiality level, the Team <span class="rfc2119">MAY</span>
- make available a version that reasonably communicates what is
- required, while respecting the original level of confidentiality, and
- without attribution to the original author.</li>
- </ol>
- <h2>5 <a id="Activities">Activities</a></h2>
- <p>This section describes the mechanisms for establishing consensus within
- the areas of Web development the Consortium chooses to pursue. An <a id="def-Activity">Activity</a>
- organizes the work necessary for the development or evolution of a Web
- technology.</p>
- <p>W3C starts an Activity based on interest from the Members and Team. W3C
- Members build interest around new work through discussions among
- Advisory Committee representatives, Chairs, and Team, and through the <a
- href="#Submission">Submission process</a>. The Team tracks Web
- developments inside and outside W3C, manages <a href="#Liaisons">liaisons</a>,
- and organizes <a href="#EventsW">Workshops</a>.</p>
- <p>Based on input from the Team and Members about the structure and scope
- of an Activity, the Team sends an <a href="#ActivityProposal">Activity
- Proposal</a> to the Advisory Committee. This is a proposal to dedicate
- Team and Member resources to a particular area of Web technology or
- policy, and when there is consensus about the motivation, scope, and
- structure of the proposed work, W3C starts a new Activity.</p>
- <p>Each Activity has its own structure that generally includes Working
- Groups, Interest Groups, and Coordination Groups. Within the framework
- of an Activity, these groups produce technical reports, review the work
- of other groups, and develop sample code or test suites.</p>
- <p>The progress of each Activity is documented in an <a id="ActivityStatement">Activity
- Statement</a>. Activity Statements describe the goals of the Activity,
- completed and unfinished deliverables, changing perspectives based on
- experience, and future plans. At least before each <a href="#ACMeetings">Advisory
- Committee meeting</a>, the Team <span class="rfc2119">SHOULD</span>
- revise the Activity Statement for each Activity that has not been
- closed.</p>
- <p>Refer to the <a href="http://www.w3.org/Consortium/activities">list of
- W3C Activities</a> [<a href="#ref-activity-list">PUB9</a>]. <strong>Note:</strong>
- This list <span class="rfc2119">MAY</span> include some Activities that
- began prior to the formalization in 1997 of the Activity creation
- process.</p>
- <h3>5.1 <a id="ActivityDevelopment">Activity Proposal Development</a></h3>
- <p>The Team <span class="rfc2119">MUST</span> notify the Advisory
- Committee when a proposal for a new or modified Activity is in
- development. This is intended to raise awareness, even if no formal
- proposal is yet available. Advisory Committee representatives <span class="rfc2119">MAY</span>
- express their general support on the <a href="#ACCommunication">Advisory
- Committee discussion list</a>. The Team <span class="rfc2119">MAY</span>
- incorporate discussion points into an Activity Proposal. Refer to
- additional <a href="http://www.w3.org/2002/05/rec-tips">tips on getting
- to Recommendation faster</a> [<a href="#ref-rec-tips">PUB27</a>].</p>
- <h3>5.2 <a id="ActivityCreation">Advisory Committee Review</a> of an
- Activity Proposal</h3>
- <p>The Director <span class="rfc2119">MUST</span> solicit <a href="#ReviewAppeal">Advisory
- Committee review</a> of every proposal to create, substantively
- modify, or extend an Activity.</p>
- <p>After a Call for Review from the Director, the Advisory Committee <a href="#ACReview">reviews</a>
- and comments on the proposal. The review period <span class="rfc2119">MUST</span>
- be at least <span class="time-interval">four weeks</span>.</p>
- <p>The Director announces to the Advisory Committee whether there is
- consensus within W3C to create or modify the Activity (possibly with
- changes suggested during the review). For a new Activity, this
- announcement officially creates the Activity. This announcement <span class="rfc2119">MAY</span>
- include a <a href="#cfp">Call for Participation</a> in any groups
- created as part of the Activity.</p>
- <p>If there was <a href="#def-Dissent">dissent</a>, Advisory Committee
- representatives <span class="rfc2119">MAY</span> <a href="#ACAppeal">appeal</a>
- a decision to create, modify, or extend the Activity. <strong>Note:</strong>
- There is no appeal of a decision <em>not</em> to create an Activity; in
- general, drafting a new Activity Proposal will be simpler than following
- the appeal process.</p>
- <h3>5.3 <a id="ActivityModification">Modification of an Activity</a></h3>
- <p>Activities are intended to be flexible. W3C expects participants to be
- able to adapt in the face of new ideas (e.g., Member Submission
- requests) and increased understanding of goals and context, while
- remaining true to the intent of the original Activity Proposal. If it
- becomes necessary to make substantive changes to an Activity (e.g.,
- because significant additional resources are necessary or because the
- Activity's scope has clearly changed from the original proposal), then
- the Director <span class="rfc2119">MUST</span> solicit <a href="#ActivityCreation">Advisory
- Committee review</a> of a complete <a href="#BPCreation">Activity
- Proposal</a>, including rationale for the changes.</p>
- <h3>5.4 <a id="ActivityExtension">Extension of an Activity</a></h3>
- <p>When the Director solicits <a href="#ActivityCreation">Advisory
- Committee review</a> of a proposal to extend the duration of an
- Activity with no other substantive modifications to the composition of
- the Activity, the proposal <span class="rfc2119">MUST</span> indicate
- the new duration and include rationale for the extension. The Director
- is <span class="rfc2119">NOT REQUIRED</span> to submit a complete <a href="#BPCreation">Activity
- Proposal</a>.</p>
- <h3>5.5 <a id="ActivityTermination">Activity Closure</a></h3>
- <p>An Activity Proposal specifies a duration for the Activity. The
- Director, subject to <a href="#ACAppeal">appeal</a> by Advisory
- Committee representatives, <span class="rfc2119">MAY</span> close an
- Activity prior to the date specified in the proposal in any of the
- following circumstances:</p>
- <ul>
- <li>Groups in the Activity fail to produce chartered deliverables.</li>
- <li>Groups in the Activity produce chartered deliverables ahead of
- schedule.</li>
- <li>There are insufficient resources to maintain the Activity, according
- to priorities established within W3C.</li>
- </ul>
- <p>The Director closes an Activity by announcement to the Advisory
- Committee.</p>
- <h3>5.6 <a id="ActivityProposal">Activity Proposals</a></h3>
- <p>An Activity Proposal defines the initial scope and structure of an
- Activity. The proposal <span class="rfc2119">MUST</span> include or
- reference the following information:</p>
- <ul>
- <li>An Activity summary. What is the nature of the Activity (e.g., to
- track developments, create technical reports, develop code, organize
- pilot experiments, or for education)? Who or what group wants this
- (providers or users)?</li>
- <li>Context information. Why is this Activity being proposed now? What
- is the situation in the world (e.g., with respect to the Web
- community, market, research, or society)? within the scope of the
- proposal? Who or what currently exists that is pertinent to this
- Activity? Is the community mature/growing/developing a niche? What
- competing technologies exist? What competing organizations exist?</li>
- <li>A description of the Activity's scope. How might a potential
- Recommendation interact and overlap with existing international
- standards and Recommendations? What organizations are likely to be
- affected by potential overlap (see the section on <a href="#Liaisons">liaisons
- with other organizations</a>)? What should be changed if the
- Activity is approved?</li>
- <li>A description of the Activity's initial deployment, including:
- <ul>
- <li>The duration of the Activity.</li>
- <li>What <a href="#GAGroups">groups</a> will be created as part of
- this Activity and how those groups will be coordinated. For each
- group, the proposal <span class="rfc2119">MUST</span> include a
- provisional charter. Groups <span class="rfc2119">MAY</span> be
- scheduled to run concurrently or sequentially (either because of a
- dependency or an expected overlap in membership and the
- desirability of working on one subject at a time). These charters
- <span class="rfc2119">MAY</span> be amended based on review
- comments before the Director issues a <a href="#cfp">Call for
- Participation</a>.</li>
- <li>The expected timeline of the Activity, including proposed
- deliverable dates and scheduled <a href="#GAEvents">Workshops and
- Symposia</a>.</li>
- <li>If known, the date of the first <a href="#ftf-meeting">face-to-face
- meeting</a> of each proposed group. The date of the first
- face-to-face meeting of a proposed group <span class="rfc2119">MUST
- NOT</span> be sooner than <span class="time-interval">eight
- weeks</span> after the date of the <a href="#ActivityProposal">Activity
- Proposal</a>.</li>
- </ul>
- </li>
- <li>A summary of resources (Member, Team, administrative, technical, and
- financial) expected to be dedicated to the Activity. The proposal <span
- class="rfc2119">MAY</span> specify the threshold level of effort
- that Members are expected to pledge in order for the Activity to be
- accepted.</li>
- <li>Information about known dependencies within W3C or outside of W3C.</li>
- <li>Intellectual property information. What are the intellectual
- property (including patents and copyright) considerations affecting
- the success of the Activity? 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>A list of supporters and references. What community is expected to
- benefit from this Activity? Are members of this community part of W3C
- now? Are they expected to join the effort?</li>
- </ul>
- <h2>6 <a id="GAGeneral">Working Groups, Interest Groups, and Coordination
- Groups</a></h2>
- <p><a id="GAGroups">This document defines three types of groups:</a></p>
- <ol>
- <li><a href="#GroupsWG">Working Groups.</a> Working Groups typically
- produce deliverables (e.g., <a href="#rec-advance">Recommendation
- Track technical reports</a>, software, test suites, and reviews of
- the deliverables of other groups). There are <a href="#good-standing">Good
- Standing</a> requirements for Working Group participation as well as
- additional participation requirements described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
- Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
- <li><a href="#GroupsIG">Interest Groups.</a> The primary goal of an
- Interest Group is to bring together people who wish to evaluate
- potential Web technologies and policies. An Interest Group is a forum
- for the exchange of ideas.</li>
- <li><a href="#GroupsCG">Coordination Groups.</a> A Coordination Group
- manages dependencies and facilitates communication with other groups,
- within or outside of W3C.</li>
- </ol>
- <p>Neither Interest Groups nor Coordination Groups publish <a href="#RecsW3C">Recommendation
- Track technical reports</a>; see information about <a href="#WGNote">maturity
- levels for Interest Groups and Coordination Groups</a>.</p>
- <h3>6.1 <a id="ReqsAllGroups">Requirements for All Working, Interest, and
- Coordination Groups</a></h3>
- <p>Each group <span class="rfc2119">MUST</span> have a charter.
- Requirements for the charter depend on the group type. All group
- charters <span class="rfc2119">MUST</span> be public (even if other
- proceedings of the group are <a href="#Member-only">Member-only</a>).
- Existing charters that are not yet public <span class="rfc2119">MUST</span>
- be made public when next revised or extended (with attention to <a href="#confidentiality-change">changing
- confidentiality level</a>).</p>
- <p>Each group <span class="rfc2119">MUST</span> have a <a id="GeneralChairs">Chair</a>
- (or co-Chairs) to coordinate the group's tasks. The Director appoints
- (and re-appoints) Chairs for all groups. The Chair is a <a href="#member-rep">Member
- representative</a>, a <a href="#Team">Team representative</a>, or an
- <a href="#invited-expert-wg">Invited Expert</a> (invited by the
- Director). The requirements of this document that apply to those types
- of participants apply to Chairs as well. The <a href="/Guide/chair-roles">role
- of the Chair [MEM14]</a> is described in the <a href="http://www.w3.org/Guide/">Member
- guide</a> [<a href="#ref-guide">MEM9</a>].</p>
- <p>Each group <span class="rfc2119">MUST</span> have a <a id="TeamContact">Team
- Contact</a>, who acts as the interface between the Chair, group
- participants, and the rest of the Team. The <a href="/Guide/staff-contact">role
- of the Team Contact</a> is described in the Member guide. The Chair
- and the Team Contact of a group <span class="rfc2119">SHOULD NOT</span>
- be the same individual.</p>
- <p>Each group <span class="rfc2119">MUST</span> have an archived mailing
- list for formal group communication (e.g., for meeting announcements and
- minutes, documentation of decisions, and <a href="#FormalObjection">Formal
- Objections</a> to decisions). It is the responsibility of the Chair
- and Team Contact to ensure that new participants are subscribed to all
- relevant mailing lists. Refer to the list of <a href="http://www.w3.org/Member/Mail/">group
+ <section id="chapterDissemination">
+ <h2>4 <a id="dissemination">Dissemination Policies</a></h2>
+ <p>The Team is responsible for managing communication within W3C and
+ with the general public (e.g., news services, press releases, managing
+ the Web site and access privileges, and managing calendars). Members <span
+ class="rfc2119">SHOULD</span> solicit review by the Team prior to
+ issuing press releases about their work within W3C.</p>
+ <p>The Team makes every effort to ensure the persistence and
+ availability of the following public information:</p>
+ <ul>
+ <li><a href="#Reports">W3C technical reports</a> whose publication has
+ been approved by the Director. Per the Membership Agreement, W3C
+ technical reports (and software) are available free of charge to the
+ general public; (refer to the <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
+ Document License</a> [<a href="#ref-doc-license">PUB18</a>]).</li>
+ <li>A <a href="http://www.w3.org/Consortium/mission">mission
+ statement</a> [<a href="#ref-mission">PUB15</a>] that explains the
+ purpose and mission of W3C, the key benefits for Members, and the
+ organizational structure of W3C.</li>
+ <li>Legal documents, including the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+ Agreement</a> [<a href="#ref-member-agreement">PUB6</a>]) and
+ documentation of any legal commitments W3C has with other entities.</li>
+ <li>The Process Document.</li>
+ <li>Public results of W3C Activities and <a href="#GAEvents">Workshops</a>.</li>
+ </ul>
+ <p>To keep the Members abreast of W3C meetings, Workshops, and review
+ deadlines, the Team provides them with a regular (e.g., weekly) news
+ service and maintains a <a href="http://www.w3.org/Member/Eventscal">calendar</a>
+ [<a href="#ref-calendar">MEM3</a>] of official W3C events. Members are
+ encouraged to send schedule and event information to the Team for
+ inclusion on this calendar.</p>
+ <h3>4.1 <a id="confidentiality-levels">Confidentiality Levels</a></h3>
+ <p>There are three principal levels of access to W3C information (on the
+ W3C Web site, in W3C meetings, etc.): public, Member-only, and
+ Team-only.</p>
+ <p>While much information made available by W3C is public, <a id="Member-only">"Member-only"
+ information</a> is available to authorized parties only, including
+ representatives of Member organizations, <a href="#invited-expert-wg">Invited
+ Experts</a>, the Advisory Board, the TAG, and the Team. For example,
+ the <a href="#WGCharter">charter</a> of some Working Groups may
+ specify a Member-only confidentiality level for group proceedings.</p>
+ <p><a id="Team-only">"Team-only" information</a> is available to the
+ Team and other authorized parties.</p>
+ <p>Those authorized to access Member-only and Team-only information:</p>
+ <ul>
+ <li><span class="rfc2119">MUST</span> treat the information as
+ confidential within W3C,</li>
+ <li><span class="rfc2119">MUST</span> use reasonable efforts to
+ maintain the proper level confidentiality, and</li>
+ <li><span class="rfc2119">MUST NOT</span> release this information to
+ the general public or press.</li>
+ </ul>
+ <p>The Team <span class="rfc2119">MUST</span> provide mechanisms to
+ protect the confidentiality of Member-only information and ensure that
+ authorized parties have proper access to this information. Documents <span
+ class="rfc2119">SHOULD</span> clearly indicate whether they require
+ Member-only confidentiality. Individuals uncertain of the
+ confidentiality level of a piece of information <span class="rfc2119">SHOULD</span>
+ contact the Team.</p>
+ <p>Advisory Committee representatives <span class="rfc2119">MAY</span>
+ authorize Member-only access to <a href="#member-rep">Member
+ representatives</a> and other individuals employed by the Member who
+ are considered appropriate recipients. For instance, it is the
+ responsibility of the Advisory Committee representative and other
+ employees and official representatives of the organization to ensure
+ that Member-only news announcements are distributed for internal use
+ only within their organization. Information about Member mailing lists
+ is available in the <a href="http://www.w3.org/Member/Intro">New
+ Member Orientation</a>.</p>
+ <h4>4.1.1 <a id="confidentiality-change">Changing Confidentiality Level</a></h4>
+ <p>As a benefit of membership, W3C provides some Team-only and
+ Member-only channels for certain types of communication. For example,
+ Advisory Committee representatives can send <a href="#ACReview">reviews</a>
+ to a Team-only channel. However, for W3C processes with a significant
+ public component, such as the technical report development process, it
+ is also important for information that affects decision-making to be
+ publicly available. The Team <span class="rfc2119">MAY</span> need to
+ communicate Team-only information to a Working Group or the public.
+ Similarly, a Working Group whose proceedings are Member-only <span class="rfc2119">MUST</span>
+ make public information pertinent to the technical report development
+ process.</p>
+ <p>This document clearly indicates which information <span class="rfc2119">MUST</span>
+ be available to Members or the public, even though that information
+ was initially communicated on Team-only or Member-only channels. Only
+ the Team and parties authorized by the Team change the level of
+ confidentiality of this information. When doing so:</p>
+ <ol>
+ <li>The Team <span class="rfc2119">MUST</span> use a version of the
+ information that was expressly provided by the author for the new
+ confidentiality level. In Calls for Review and other similar
+ messages, the Team <span class="rfc2119">SHOULD</span> remind
+ recipients to provide such alternatives.</li>
+ <li>The Team <span class="rfc2119">MUST NOT</span> attribute the
+ version for the new confidentiality level to the author without the
+ author's consent.</li>
+ <li>If the author has not conveyed to the Team a version that is
+ suitable for another confidentiality level, the Team <span class="rfc2119">MAY</span>
+ make available a version that reasonably communicates what is
+ required, while respecting the original level of confidentiality,
+ and without attribution to the original author.</li>
+ </ol>
+ </section>
+ <section class="issue" id="chapterActivities">
+ <h2>5 Activities</h2>
+ <p><em>This section is being removed, leaving internal management of
+ work to W3C Team. In <strong>this</strong> draft, points not
+ covered elsewhere and relevant beyond the structure of "Activites"
+ have been left here, until there is a resolution on what to do about
+ them.</em></p>
+ <p>W3C starts an Activity based on interest from the Members and Team. <span
+ class="issue">Should we move this to charters, or remove it as
+ obvious?</span></p>
+ <p>Based on input from the Team and Members about the structure and
+ scope of an Activity, the Team sends an <a href="#ActivityProposal">Activity
+ Proposal</a> to the Advisory Committee. This is a proposal to
+ dedicate Team and Member resources to a particular area of Web
+ technology or policy, and when there is consensus about the
+ motivation, scope, and structure of the proposed work, W3C starts a
+ new Activity. <span class="issue">Move this to cover charter
+ development</span></p>
+ <p>The progress of each Activity is documented in an Activity Statement.
+ At least before each <a href="#ACMeetings">Advisory Committee meeting</a>,
+ the Team <span class="rfc2119">SHOULD</span> revise the Activity
+ Statement for each Activity that has not been closed. <span class="issue">Should
+ we put this requirement on charters?</span></p>
+ <h3>5.2 Advisory Committee Review of an Activity Proposal</h3>
+ <p>The Director <span class="rfc2119">MUST</span> solicit <a href="#ReviewAppeal">Advisory
+ Committee review</a> of every proposal to create, substantively
+ modify, or <strong>extend</strong> an Activity. <span class="issue"><strong></strong>currently
+ charters can be extended without review - should that be changed?</span>
+ The review period <span class="rfc2119">MUST</span> be at least <span
+ class="time-interval">four weeks</span>. <span class="issue">Keep four
+ week requirement for charter review (probably yes)?<br>
+ </span></p>
+ <p>The Director announces to the Advisory Committee whether there is
+ consensus within W3C to create or modify the Activity (possibly with
+ changes suggested during the review). For a new Activity, this
+ announcement officially creates the Activity. <span class="issue">Move
+ this to cover charter development</span></p>
+ <p>If there was <a href="#def-Dissent">dissent</a>, Advisory Committee
+ representatives <span class="rfc2119">MAY</span> <a href="#ACAppeal">appeal</a>
+ a decision to create, modify, or extend the Activity. <span class="issue">This
+ is different from the equivalent for charters</span></p>
+ <h3>5.6 Activity Proposals</h3>
+ <p>An Activity Proposal defines the initial scope and structure of an
+ Activity. The proposal <span class="rfc2119">MUST</span> include or
+ reference the following information:</p>
+ <ul>
+ <li>Context information. Why is this Activity being proposed now? What
+ is the situation in the world (e.g., with respect to the Web
+ community, market, research, or society)? within the scope of the
+ proposal? Who or what currently exists that is pertinent to this
+ Activity? Is the community mature/growing/developing a niche? What
+ competing technologies exist? What competing organizations exist? <span
+ class="issue">For Activities the appeal required dissent in the
+ review. Should we have that constraint?</span></li>
+ <li>A description of the Activity's scope. How might a potential
+ Recommendation interact and overlap with existing international
+ standards and Recommendations? What organizations are likely to be
+ affected by potential overlap (see the section on <a href="#Liaisons">liaisons
+ with other organizations</a>)? What should be changed if the
+ Activity is approved? <span class="issue">Do we need this info
+ beyond the dependency information already required?</span></li>
+ <li>The proposal <span class="rfc2119">MAY</span> specify the
+ threshold level of effort that Members are expected to pledge in
+ order for the Activity to be accepted. <span class="issue">The team
+ adopted a best practice to do this</span></li>
+ <li>Intellectual property information. What are the intellectual
+ property (including patents and copyright) considerations affecting
+ the success of the Activity? 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>]? <span
+ class="issue">Should we put this requirement on charters?</span></li>
+ <li>A list of supporters and references. What community is expected to
+ benefit from this Activity? Are members of this community part of
+ W3C now? Are they expected to join the effort? <span class="issue">Should
+ we put this requirement on charters?</span></li>
+ </ul>
+ </section>
+ <section id="ChapterGroups">
+ <h2>6 <a id="GAGeneral">Working Groups, Interest Groups, and
+ Coordination Groups</a></h2>
+ <p><a id="GAGroups">This document defines three types of groups:</a></p>
+ <ol>
+ <li><a href="#GroupsWG">Working Groups.</a> Working Groups typically
+ produce deliverables (e.g., <a href="#rec-advance">Recommendation
+ Track technical reports</a>, software, test suites, and reviews of
+ the deliverables of other groups). There are <a href="#good-standing">Good
+ Standing</a> requirements for Working Group participation as well
+ as additional participation requirements described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
+ <li><a href="#GroupsIG">Interest Groups.</a> The primary goal of an
+ Interest Group is to bring together people who wish to evaluate
+ potential Web technologies and policies. An Interest Group is a
+ forum for the exchange of ideas.</li>
+ <li><a href="#GroupsCG">Coordination Groups.</a> A Coordination Group
+ manages dependencies and facilitates communication with other
+ groups, within or outside of W3C.</li>
+ </ol>
+ <p>Neither Interest Groups nor Coordination Groups publish <a href="#RecsW3C">Recommendation
+ Track technical reports</a>; see information about <a href="#WGNote">maturity
+ levels for Interest Groups and Coordination Groups</a>.</p>
+ <h3>6.1 <a id="ReqsAllGroups">Requirements for All Working, Interest,
+ and Coordination Groups</a></h3>
+ <p>Each group <span class="rfc2119">MUST</span> have a charter.
+ Requirements for the charter depend on the group type. All group
+ charters <span class="rfc2119">MUST</span> be public (even if other
+ proceedings of the group are <a href="#Member-only">Member-only</a>).
+ Existing charters that are not yet public <span class="rfc2119">MUST</span>
+ be made public when next revised or extended (with attention to <a href="#confidentiality-change">changing
+ confidentiality level</a>).</p>
+ <p>Each group <span class="rfc2119">MUST</span> have a <a id="GeneralChairs">Chair</a>
+ (or co-Chairs) to coordinate the group's tasks. The Director appoints
+ (and re-appoints) Chairs for all groups. The Chair is a <a href="#member-rep">Member
+ representative</a>, a <a href="#Team">Team representative</a>, or
+ an <a href="#invited-expert-wg">Invited Expert</a> (invited by the
+ Director). The requirements of this document that apply to those types
+ of participants apply to Chairs as well. The <a href="/Guide/chair-roles">role
+ of the Chair [MEM14]</a> is described in the <a href="http://www.w3.org/Guide/">Member
+ guide</a> [<a href="#ref-guide">MEM9</a>].</p>
+ <p>Each group <span class="rfc2119">MUST</span> have a <a id="TeamContact">Team
+ Contact</a>, who acts as the interface between the Chair, group
+ participants, and the rest of the Team. The <a href="/Guide/staff-contact">role
+ of the Team Contact</a> is described in the Member guide. The Chair
+ and the Team Contact of a group <span class="rfc2119">SHOULD NOT</span>
+ be the same individual.</p>
+ <p>Each group <span class="rfc2119">MUST</span> have an archived
+ mailing list for formal group communication (e.g., for meeting
+ announcements and minutes, documentation of decisions, and <a href="#FormalObjection">Formal
+ Objections</a> to decisions). It is the responsibility of the Chair
+ and Team Contact to ensure that new participants are subscribed to all
+ relevant mailing lists. Refer to the list of <a href="http://www.w3.org/Member/Mail/">group
mailing
- lists</a> [<a href="#ref-mailing-lists">MEM2</a>].</p>
- <p>A Chair <span class="rfc2119">MAY</span> form task forces (composed of
- group participants) to carry out assignments for the group. The scope of
- these assignments <span class="rfc2119">MUST NOT</span> exceed the
- scope of the group's charter. A group <span class="rfc2119">SHOULD</span>
- document the process it uses to create task forces (e.g., each task
- force might have an informal "charter"). Task forces do not publish <a
- href="#Reports">technical reports</a>; the Working Group <span class="rfc2119">MAY</span>
- choose to publish their results as part of a technical report.</p>
- <h3>6.2 <a id="GroupsWG">Working Groups</a> and <a id="GroupsIG">Interest
- Groups</a></h3>
- <p>Although Working Groups and Interest Groups have different purposes,
- they share some characteristics, and so are defined together in the
- following sections.</p>
- <h4>6.2.1 <a id="group-participation">Working Group and Interest Group
- Participation Requirements</a></h4>
- <p>There are three types of individual <a id="wgparticipant">participants
- in a Working Group</a>: <a href="#member-rep">Member representatives</a>,
- <a href="#invited-expert-wg">Invited Experts</a>, and <a href="#Team">Team
- representatives</a> (including the <a href="#TeamContact">Team
- Contact</a>).</p>
- <p>There are four types of individual <a id="igparticipant">participants
- in an Interest Group</a>: the same three types as for Working Groups
- plus, for an Interest Group where the only <a href="#ig-mail-only">participation
- requirement is mailing list subscription</a>, <a id="public-participant-ig">public
- participants</a>.</p>
- <p>Except where noted in this document or in a group charter, all
- participants share the same rights and responsibilities in a group; see
- also the <a href="#ParticipationCriteria">individual participation
- criteria</a>.</p>
- <p>A participant <span class="rfc2119">MUST</span> represent at most one
- organization in a Working Group or Interest Group.</p>
- <p>An individual <span class="rfc2119">MAY</span> become a Working or
- Interest Group participant at any time during the group's 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 <span
- class="rfc2119">MAY</span> designate a <a id="mtg-substitute">substitute</a>
- to attend a <a href="#GeneralMeetings">meeting</a> and <span class="rfc2119">SHOULD</span>
- inform the Chair. The substitute <span class="rfc2119">MAY</span> act
- on behalf of the participant, including for <a href="#Votes">votes</a>.
- For the substitute to vote, the participant <span class="rfc2119">MUST</span>
- 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 <span class="rfc2119">SHOULD</span> authorize
- another participant to act as <a href="#proxy">proxy</a> for votes. For
- the purposes of <a href="#good-standing">Good Standing</a>, the regular
- representative and the substitute are considered the same participant.</p>
- <p>To allow rapid progress, Working Groups are intended to be small
- (typically fewer than 15 people) and composed of experts in the area
- defined by the charter. In principle, Interest Groups have no limit on
- the number of participants. When a Working Group grows too large to be
- effective, W3C <span class="rfc2119">MAY</span> split it into an
- Interest Group (a discussion forum) and a much smaller Working Group (a
- core group of highly dedicated participants).</p>
- <p>See also the licensing obligations on Working Group participants in <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>], and the
- patent claim exclusion process of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section
- 4</a>.</p>
- <h5>6.2.1.1 <a id="member-rep-wg">Member Representative</a> in a Working
- Group</h5>
- <p>An individual is a Member representative in a Working Group if all of
- the following conditions are satisfied:</p>
- <ul>
- <li>the Advisory Committee representative of the Member in question has
- designated the individual as a Working Group participant, and</li>
- <li>the individual qualifies for <a href="#member-rep">Member
- representation</a>.</li>
- </ul>
- <p><a id="member-rep-info">To designate an individual as a Member
- representative in a Working Group</a>, an Advisory Committee
- representative <span class="rfc2119">MUST</span> provide the Chair and
- Team Contact with all of the following information, in addition to any
- other information required by the <a href="#cfp">Call for Participation</a>
- and charter (including the participation requirements of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
- Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]):</p>
- <ol>
- <li>The name of the W3C Member the individual represents and whether the
- individual is an employee of that Member organization;</li>
- <li>A statement that the individual accepts the participation terms set
- forth in the charter (with an indication of charter date or version);</li>
- <li>A statement that the Member will provide the necessary financial
- support for participation (e.g., for travel, telephone calls, and
- conferences).</li>
- </ol>
- <p>A Member participates in a Working Group from the moment the first
- Member representative joins the group until either of the 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>
- </ul>
- <h5>6.2.1.2 <a id="member-rep-ig">Member Representative</a> in an
- Interest Group</h5>
- <p>When the participation requirements exceed <a href="#ig-mail-only">Interest
-Group
- mailing list subscription</a>, an individual is a Member
- representative in an Interest Group if all of the following conditions
- are satisfied:</p>
- <ul>
- <li>the Advisory Committee representative of the Member in question has
- designated the individual as an Interest Group participant, and</li>
- <li>the individual qualifies for <a href="#member-rep">Member
- representation</a>.</li>
- </ul>
- <p>To designate an individual as a Member representative in an Interest
- Group, the Advisory Committee representative <span class="rfc2119">MUST</span>
- follow the instructions in the <a href="#cfp">Call for Participation</a>
- and charter.</p>
- <p>Member participation in an Interest Group ceases under the same
- conditions as for a Working Group.</p>
- <h5>6.2.1.3 <a id="invited-expert-wg">Invited Expert</a> in a Working
- Group</h5>
- <p>The Chair <span class="rfc2119">MAY</span> invite an individual with a
- particular expertise to participate in a Working Group. This individual
- <span class="rfc2119">MAY</span> represent an organization in the group
- (e.g., if acting as a liaison with another organization).</p>
- <p>An individual is an Invited Expert in a Working Group if all of the
- following conditions are satisfied:</p>
- <ul>
- <li>the Chair has designated the individual as a group participant,</li>
- <li>the Team Contact has agreed with the Chair's choice, and</li>
- <li>the individual has provided the <a href="#inv-expert-info">information
-required
- of an Invited Expert</a> to the Chair and Team Contact.</li>
- </ul>
- <p>To designate an individual as an Invited Expert in a Working Group, the
- Chair <span class="rfc2119">MUST</span> inform the Team Contact and
- provide rationale for the choice. When the Chair and the Team Contact
- disagree about a designation, the <a href="#def-Director">Director</a>
- determines whether the individual will be invited to participate in the
- Working Group.</p>
- <p><a id="inv-expert-info">To be able to participate in a Working Group as
- an Invited Expert</a>, an individual <span class="rfc2119">MUST</span>
- do all of the following:</p>
- <ul>
- <li>identify the organization, if any, the individual represents as a
- participant in this group,</li>
- <li>agree to the terms of the <a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">invited
- expert and collaborators agreement</a> [<a href="#ref-invited-expert">PUB17</a>],</li>
- <li>accept the participation terms set forth in the charter (including
- the participation requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
- 3</a> (especially 3.4) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section
- 6</a> (especially 6.10) of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
- Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]). Indicate
- a specific charter date or version,</li>
- <li>disclose whether the individual is an employee of a W3C Member; see
- the <a href="#coi">conflict of interest policy</a>,</li>
- <li>provide a statement of who will provide the necessary financial
- support for the individual's participation (e.g., for travel,
- telephone calls, and conferences), and</li>
- <li>if the individual's employer (including a self-employed individual)
- or the organization the individual represents is not a W3C Member,
- indicate whether that organization intends to join W3C. If the
- organization does not intend to join W3C, indicate reasons the
- individual is aware of for this choice.</li>
- </ul>
- <p>The Chair <span class="rfc2119">SHOULD NOT</span> designate as an
- Invited Expert in a Working Group an individual who is an employee of a
- W3C Member. The Chair <span class="rfc2119">MUST NOT</span> use Invited
- Expert status to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
- <p>An Invited Expert 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>the Chair or Director withdraws the invitation to participate, or</li>
- <li>the individual <a href="#resignation">resigns</a>.</li>
- </ul>
- <h5>6.2.1.4 <a id="invited-expert-ig">Invited Expert</a> in an Interest
- Group</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>
- <h5>6.2.1.5 <a id="team-rep-wg">Team Representative in a Working Group</a></h5>
- <p>An individual is a Team representative in a Working Group when so
- designated by W3C management.</p>
- <p>An 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>
- <h5>6.2.1.6 <a id="team-rep-ig">Team Representative in an Interest Group</a></h5>
- <p>When the participation requirements exceed <a href="#ig-mail-only">Interest
+ lists</a> [<a href="#ref-mailing-lists">MEM2</a>].</p>
+ <p>A Chair <span class="rfc2119">MAY</span> form task forces (composed
+ of group participants) to carry out assignments for the group. The
+ scope of these assignments <span class="rfc2119">MUST NOT</span>
+ exceed the scope of the group's charter. A group <span class="rfc2119">SHOULD</span>
+ document the process it uses to create task forces (e.g., each task
+ force might have an informal "charter"). Task forces do not publish <a
+ href="#Reports">technical reports</a>; the Working Group <span class="rfc2119">MAY</span>
+ choose to publish their results as part of a technical report.</p>
+ <h3>6.2 <a id="GroupsWG">Working Groups</a> and <a id="GroupsIG">Interest
+ Groups</a></h3>
+ <p>Although Working Groups and Interest Groups have different purposes,
+ they share some characteristics, and so are defined together in the
+ following sections.</p>
+ <h4>6.2.1 <a id="group-participation">Working Group and Interest Group
+ Participation Requirements</a></h4>
+ <p>There are three types of individual <a id="wgparticipant">participants
+ in a Working Group</a>: <a href="#member-rep">Member
+ representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
+ and <a href="#Team">Team representatives</a> (including the <a href="#TeamContact">Team
+ Contact</a>).</p>
+ <p>There are four types of individual <a id="igparticipant">participants
+ in an Interest Group</a>: the same three types as for Working Groups
+ plus, for an Interest Group where the only <a href="#ig-mail-only">participation
+ requirement is mailing list subscription</a>, <a id="public-participant-ig">public
+ participants</a>.</p>
+ <p>Except where noted in this document or in a group charter, all
+ participants share the same rights and responsibilities in a group;
+ see also the <a href="#ParticipationCriteria">individual
+ participation criteria</a>.</p>
+ <p>A participant <span class="rfc2119">MUST</span> represent at most
+ one organization in a Working Group or Interest Group.</p>
+ <p>An individual <span class="rfc2119">MAY</span> become a Working or
+ Interest Group participant at any time during the group's 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 <span
+ class="rfc2119">MAY</span> designate a <a id="mtg-substitute">substitute</a>
+ to attend a <a href="#GeneralMeetings">meeting</a> and <span class="rfc2119">SHOULD</span>
+ inform the Chair. The substitute <span class="rfc2119">MAY</span> act
+ on behalf of the participant, including for <a href="#Votes">votes</a>.
+ For the substitute to vote, the participant <span class="rfc2119">MUST</span>
+ 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 <span class="rfc2119">SHOULD</span> authorize
+ another participant to act as <a href="#proxy">proxy</a> for votes.
+ For the purposes of <a href="#good-standing">Good Standing</a>, the
+ regular representative and the substitute are considered the same
+ participant.</p>
+ <p>To allow rapid progress, Working Groups are intended to be small
+ (typically fewer than 15 people) and composed of experts in the area
+ defined by the charter. In principle, Interest Groups have no limit on
+ the number of participants. When a Working Group grows too large to be
+ effective, W3C <span class="rfc2119">MAY</span> split it into an
+ Interest Group (a discussion forum) and a much smaller Working Group
+ (a core group of highly dedicated participants).</p>
+ <p>See also the licensing obligations on Working Group participants in <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>], and the
+ patent claim exclusion process of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section
+ 4</a>.</p>
+ <h5>6.2.1.1 <a id="member-rep-wg">Member Representative</a> in a
+ Working Group</h5>
+ <p>An individual is a Member representative in a Working Group if all of
+ the following conditions are satisfied:</p>
+ <ul>
+ <li>the Advisory Committee representative of the Member in question
+ has designated the individual as a Working Group participant, and</li>
+ <li>the individual qualifies for <a href="#member-rep">Member
+ representation</a>.</li>
+ </ul>
+ <p><a id="member-rep-info">To designate an individual as a Member
+ representative in a Working Group</a>, an Advisory Committee
+ representative <span class="rfc2119">MUST</span> provide the Chair
+ and Team Contact with all of the following information, in addition to
+ any other information required by the <a href="#cfp">Call for
+ Participation</a> and charter (including the participation
+ requirements of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]):</p>
+ <ol>
+ <li>The name of the W3C Member the individual represents and whether
+ the individual is an employee of that Member organization;</li>
+ <li>A statement that the individual accepts the participation terms
+ set forth in the charter (with an indication of charter date or
+ version);</li>
+ <li>A statement that the Member will provide the necessary financial
+ support for participation (e.g., for travel, telephone calls, and
+ conferences).</li>
+ </ol>
+ <p>A Member participates in a Working Group from the moment the first
+ Member representative joins the group until either of the 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>
+ </ul>
+ <h5>6.2.1.2 <a id="member-rep-ig">Member Representative</a> in an
+ Interest Group</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>
- <h5>6.2.1.7 <a id="good-standing">Good Standing in a Working Group</a></h5>
- <p>Participation by an individual in a Working Group on an ongoing basis
- implies a serious commitment to the charter, including all of the
- following:</p>
- <ul>
- <li>attending most meetings of the Working Group.</li>
- <li>providing deliverables or drafts of deliverables in a timely
- fashion.</li>
- <li>being familiar with the relevant documents of the Working Group,
- including minutes of past meetings.</li>
- <li>following discussions on relevant mailing list(s).</li>
- </ul>
- <p>At the first Working Group meeting that follows any <a href="#cfp">Call
- for Participation</a>, all participants are in Good Standing. If a
- Member or Invited Expert joins the Working Group after the end of that
- meeting, the Member Representative or Invited Expert does not attain
- Good Standing until the start of the second consecutive meeting that
- individual attends.</p>
- <p>When the Chair and the <a href="#TeamContact">Team Contact</a> agree,
- the Chair <span class="rfc2119">MAY</span> declare that a participant
- is no longer in Good Standing (henceforth called "Bad Standing"). If
- there is disagreement between the Chair and the Team Contact about
- standing, the Director determines the participant's standing. The Chair
- <span class="rfc2119">MAY</span> declare a Team participant to be in Bad
- Standing, but it is clearly preferable for the Chair, Team participant,
- and W3C management to resolve issues internally.</p>
- <p>A participant <span class="rfc2119">MAY</span> be declared in Bad
- Standing in any of the following circumstances:</p>
- <ul>
- <li>the individual has missed more than one of the last three <a href="#distributed-meeting">distributed
- meetings</a>.</li>
- <li>the individual has missed more than one of the last three <a href="#ftf-meeting">face-to-face
- meetings</a>.</li>
- <li>the individual has not provided deliverables in a timely fashion
- twice in sequence.</li>
- <li>the individual has not followed the <a href="#coi">conflict of
- interest policy</a> by disclosing information to the rest of the
- group.</li>
- </ul>
- <p>Although all participants representing an organization <span class="rfc2119">SHOULD</span>
- attend all meetings, attendance by one representative of an organization
- satisfies the meeting attendance requirement for all representatives of
- the organization.</p>
- <p>The above criteria <span class="rfc2119">MAY</span> be relaxed if the
- Chair and Team Contact agree that doing so will not set back the Working
- Group. For example, the attendance requirement can be relaxed for
- reasons of expense (e.g., cost of travel) or scheduling (for example, an
- exceptional teleconference is scheduled at 3:00 a.m. local time for the
- participant). It is the responsibility of the Chair and Team Contact to
- apply criteria for Good Standing consistently.</p>
- <p>When a participant risks losing Good Standing, the Chair and Team
- Contact are expected to discuss the matter with the participant and the
- participant's Advisory Committee representative (or W3C management for
- the Team) before declaring the participant in Bad Standing.</p>
- <p>The Chair declares a participant in Bad Standing by informing the
- participant's Advisory Committee representative and the participant of
- the decision. If the Advisory Committee representative and Chair differ
- in opinion, the Advisory Committee representative <span class="rfc2119">MAY</span>
- ask the <a href="#def-Director">Director</a> to confirm or deny the
- decision. <a href="#invited-expert-wg">Invited Experts</a> declared in
- Bad Standing <span class="rfc2119">MAY</span> appeal to the Director.</p>
- <p>The Chair and Team Contact restore Good Standing and <span class="rfc2119">SHOULD</span>
- do so when the individual in Bad Standing satisfies the above criteria.
- The Chair <span class="rfc2119">MUST</span> inform the individual's
- Advisory Committee representative of any change in standing.</p>
- <p>When a Member representative permanently replaces another (i.e., is not
- simply a temporary <a href="#mtg-substitute">substitute</a>), the new
- participant inherits the standing of the departing participant.</p>
- <p>Changes in an individual's standing in a Working Group have no effect
- on the obligations associated with Working Group participation that are
- described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
- Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
- <p><strong>Note:</strong> In general, the time commitment for
- participating in an Interest Group is less than that for a Working
- Group; see the section on <a href="#ig-charter-participation">participation
- provisions in an Interest Group charter</a>.</p>
- <h4>6.2.2 <a id="WGCharterDevelopment">Working Group and Interest Group
- Charter Development</a></h4>
- <p>The Team <span class="rfc2119">MUST</span> notify the Advisory
- Committee when a charter for a new Working Group or Interest Group is in
- development. The suggestions for building support around an <a href="#ActivityDevelopment">Activity
- Proposal</a> apply to charters as well.</p>
- <p>W3C <span class="rfc2119">MAY</span> begin work on a Working Group or
- Interest Group charter at any time. A Working Group or Interest Group <span
- class="rfc2119">MUST</span> be part of an approved <a href="#def-Activity">Activity</a>.</p>
- <h4>6.2.3 <a id="CharterReview">Advisory Committee Review</a> of a
- Working Group or Interest Group Charter</h4>
- <p>The Director <span class="rfc2119">MUST</span> solicit <a href="#ReviewAppeal">Advisory
- Committee review</a> of every new or substantively modified Working
- Group or Interest Group charter. The Director is <span class="rfc2119">NOT
- REQUIRED</span> to solicit Advisory Committee review prior to a
- charter extension or for minor changes.</p>
- <p>The Director's Call for Review of a substantively modified charter <span
- class="rfc2119">MUST</span> highlight important changes (e.g.,
- regarding deliverables or resource allocation) and include rationale for
- the changes.</p>
- <h4>6.2.4 <a id="cfp">Call for Participation in a Working Group or
- Interest Group</a></h4>
- <p>After Advisory Committee review of a Working Group or Interest Group
- charter, the Director <span class="rfc2119">MAY</span> issue a Call for
- Participation to the Advisory Committee. For a new group, this
- announcement officially creates the group. The announcement <span class="rfc2119">MUST</span>
- 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>
- <span class="rfc2119">MUST</span> be designated (or re-designated).</p>
- <p>Advisory Committee representatives <span class="rfc2119">MAY</span> <a
- href="#ACAppeal">appeal</a> creation or substantive modification of a
- Working Group or Interest Group charter.</p>
- <h4>6.2.5 <a id="charter-extension">Working Group and Interest Group
- Charter Extension</a></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 <span class="rfc2119">MUST</span>
- indicate the new duration, which <span class="rfc2119">MUST NOT</span>
- exceed the duration of the Activity to which the group belongs. The
- announcement <span class="rfc2119">MUST</span> 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 <span class="rfc2119">NOT REQUIRED</span> to re-designate <a
- href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited
- Experts</a>.</p>
- <p>Advisory Committee representatives <span class="rfc2119">MAY</span> <a
- href="#ACAppeal">appeal</a> the extension of a Working Group or
- Interest Group charter.</p>
- <h4>6.2.6 <a id="WGCharter">Working Group and Interest Group Charters</a></h4>
- <p>A Working Group or Interest Group charter <span class="rfc2119">MUST</span>
- 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 <span
- class="rfc2119">NOT REQUIRED</span> 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 <span class="rfc2119">MUST</span>
- 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 <span class="rfc2119">MUST</span>
- specify when required deliverables are expected from the other groups.
- The charter <span class="rfc2119">SHOULD</span> 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 <span class="rfc2119">SHOULD</span> specify
- expected conformance to the deliverables of the other groups;</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>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>
- </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 <span class="rfc2119">MAY</span>
- include provisions regarding participation, including specifying that
- the <a id="ig-mail-only">only requirement for participation (by anyone)
- in the Interest Group</a> is subscription to the Interest Group
- mailing list. This type of Interest Group <span class="rfc2119">MAY</span>
- have <a href="#public-participant-ig">public participants</a>.</p>
- <p>A charter <span class="rfc2119">MAY</span> include additional voting
- procedures, but those procedures <span class="rfc2119">MUST NOT</span>
- conflict with the <a href="#Votes">voting requirements</a> of the
- Process Document.</p>
- <p>A charter <span class="rfc2119">MAY</span> include provisions other
- than those required by this document. The charter <span class="rfc2119">SHOULD</span>
- 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>6.2.7 <a id="three-month-rule">Working Group "Heartbeat" Requirement</a></h4>
- <p>It is important that a Working Group keep the Membership and public
- informed of its activity and progress. To this end, each Working Group <span
- class="rfc2119">SHOULD</span> publish in the <a href="http://www.w3.org/TR/">W3C
- technical reports index</a> a new draft of <em>each active technical
- report</em> at least once every three months. An active technical
- report is a Working Draft, Candidate Recommendation, Proposed
- Recommendation, or Proposed Edited Recommendation. Each Working Group <span
- class="rfc2119">MUST</span> publish a new draft of <em>at least one
- of its active technical reports</em> on the <a href="http://www.w3.org/TR/">W3C
- technical reports index</a> [<a href="#ref-doc-list">PUB11</a>] at
- least once every three months.</p>
- <p>Public progress reports are also important when a Working Group does
- not update a technical report within three months (for example, when the
- delay is due to a challenging technical issue) or when a Working Group
- has no active technical reports (for example, because it is developing a
- test suite).</p>
- <p>In exceptional cases, the Chair <span class="rfc2119">MAY</span> ask
- the Director to be excused from this publication requirement. However,
- in this case, the Working Group <span class="rfc2119">MUST</span> issue
- a public status report with rationale why a new draft has not been
- published.</p>
- <p>There are several reasons for this Working Group "heartbeat"
- requirement:</p>
- <ul>
- <li>To promote public accountability;</li>
- <li>To encourage Working Groups to keep moving forward, and to
- incorporate their decisions into readable public documents. People
- cannot be expected to read several months of a group's mailing list
- archive to understand where the group stands;</li>
- <li>To notify interested parties of updated work in familiar a place
- such as the W3C home page and index of technical reports.</li>
- </ul>
- <p>As an example, suppose a Working Group has one technical report as a
- deliverable, which it publishes as a Proposed Recommendation. Per the
- heartbeat requirement, the Working Group is required to publish a new
- draft of the Proposed Recommendation at least once every three months,
- even if it is only to revise the status of the Proposed Recommendation
- document (e.g., to provide an update on the status of the decision to
- advance). The heartbeat requirement stops when the document becomes a
- Recommendation (or a Working Group Note).</p>
- <h4>6.2.8 <a id="GeneralTermination">Working Group and Interest Group
- Closure</a></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, <span class="rfc2119">MAY</span>
- close a group prior to the date specified in the charter in any of the
- following circumstances:</p>
- <ul>
- <li>There are insufficient resources to produce chartered deliverables
- or to maintain the group, according to priorities established within
- W3C.</li>
- <li>The group produces chartered deliverables ahead of schedule.</li>
- <li>The Activity to which the group belongs terminates.</li>
- </ul>
- <p>The Director closes a Working Group or Interest Group by announcement
- to the Advisory Committee.</p>
- <p>Closing a Working Group has implications with respect to the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
- Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
- <h3>6.3 <a id="GroupsCG">Coordination Groups</a></h3>
- <p>W3C Activities interact in many ways. There are dependencies between
- groups within the same Activity or in different Activities. There are
- also dependencies between W3C Activities and the activities of other
- organizations. Examples of dependencies include the use by one
- technology of another being developed elsewhere, scheduling constraints
- between groups, and the synchronization of publicity for the
- announcement of deliverables. Coordination Groups are created to manage
- dependencies so that issues are resolved fairly and the solutions are
- consistent with W3C's mission and results.</p>
- <p>Where a Coordination Group's scope covers two groups with unresolved
- disputes or tensions, it is the first locus of resolution of these
- disputes.</p>
- <h4>6.3.1 <a id="CGParticipation">Coordination Group Participation
- Requirements</a></h4>
- <p>There are four types <a id="cgparticipant">participants in a
- Coordination Group</a>: the <a href="#GeneralChairs">Chair</a>, the
- Chair of each coordinated group (to promote effective communication
- among the groups), Invited Experts (e.g., liaisons to groups inside or
- outside W3C), and Team representatives (including the <a href="#TeamContact">Team
- Contact</a>). The requirements for Invited Expert participation are
- the same as for an <a href="#invited-expert-wg">Invited Expert in a
- Working Group</a>.</p>
- <p>Coordination Group participants <span class="rfc2119">MUST</span>
- follow the <a href="#coi">conflict of interest policy</a> by disclosing
- information to the rest of the group.</p>
- <p>There are no Good Standing requirements for Coordination Group
- participation; regular participation in a relevant Coordination Group is
- one of the <a href="/Guide/chair-roles">roles of a group Chair [MEM14]</a>.</p>
- <h4>6.3.2 <a id="CGCreation">Coordination Group Creation and Closure</a></h4>
- <p>The Director creates or modifies a Coordination Group by sending the <a
- href="#CGCharter">Coordination Group charter</a> to the Advisory
- Committee. A Coordination Group <span class="rfc2119">MAY</span> be
- created as part of an <a href="#ActivityProposal">Activity Proposal</a>
- (for example to coordinate other groups in the Activity or to draw up
- charters of future groups), or during the life of an Activity when
- dependencies arise. A Coordination Group <span class="rfc2119">MAY</span>
- operate as part of several W3C Activities.</p>
- <p>A Coordination Group <span class="rfc2119">SHOULD</span> close when
- there is no longer a perceived need for coordination.</p>
- <h4>6.3.3 <a id="CGCharter">Coordination Group Charters</a></h4>
- <p>A Coordination Group charter <span class="rfc2119">MUST</span> include
- all of the following information:</p>
- <ul>
- <li>The group's mission;</li>
- <li>The scope of the group's work, including the names of coordinated
- groups and contact information for those groups;</li>
- <li>Any dependencies by groups within or outside of W3C on this group;</li>
- <li>Any dependencies of this group on other groups within or outside of
- W3C; see the section on <a href="#Liaisons">liaisons with other
- organizations</a>.</li>
- <li>The <a href="#confidentiality-levels">level of confidentiality</a>
- of the group's proceedings;</li>
- <li>Meeting mechanisms and expected frequency;</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 level of involvement by the Team.</li>
- </ul>
- <p>A charter <span class="rfc2119">MAY</span> include additional voting
- procedures, but those procedures <span class="rfc2119">MUST NOT</span>
- conflict with the <a href="#Votes">voting requirements</a> of the
- Process Document.</p>
- <p>A charter <span class="rfc2119">MAY</span> include provisions other
- than those required by this document. The charter <span class="rfc2119">SHOULD</span>
- highlight whether additional provisions impose constraints beyond those
- of the W3C Process Document.</p>
+ mailing list subscription</a>, an individual is a Member
+ representative in an Interest Group if all of the following conditions
+ are satisfied:</p>
+ <ul>
+ <li>the Advisory Committee representative of the Member in question
+ has designated the individual as an Interest Group participant, and</li>
+ <li>the individual qualifies for <a href="#member-rep">Member
+ representation</a>.</li>
+ </ul>
+ <p>To designate an individual as a Member representative in an Interest
+ Group, the Advisory Committee representative <span class="rfc2119">MUST</span>
+ follow the instructions in the <a href="#cfp">Call for Participation</a>
+ and charter.</p>
+ <p>Member participation in an Interest Group ceases under the same
+ conditions as for a Working Group.</p>
+ <h5>6.2.1.3 <a id="invited-expert-wg">Invited Expert</a> in a Working
+ Group</h5>
+ <p>The Chair <span class="rfc2119">MAY</span> invite an individual with
+ a particular expertise to participate in a Working Group. This
+ individual <span class="rfc2119">MAY</span> represent an organization
+ in the group (e.g., if acting as a liaison with another organization).</p>
+ <p>An individual is an Invited Expert in a Working Group if all of the
+ following conditions are satisfied:</p>
+ <ul>
+ <li>the Chair has designated the individual as a group participant,</li>
+ <li>the Team Contact has agreed with the Chair's choice, and</li>
+ <li>the individual has provided the <a href="#inv-expert-info">information
+required
+ of an Invited Expert</a> to the Chair and Team Contact.</li>
+ </ul>
+ <p>To designate an individual as an Invited Expert in a Working Group,
+ the Chair <span class="rfc2119">MUST</span> inform the Team Contact
+ and provide rationale for the choice. When the Chair and the Team
+ Contact disagree about a designation, the <a href="#def-Director">Director</a>
+ determines whether the individual will be invited to participate in
+ the Working Group.</p>
+ <p><a id="inv-expert-info">To be able to participate in a Working Group
+ as an Invited Expert</a>, an individual <span class="rfc2119">MUST</span>
+ do all of the following:</p>
+ <ul>
+ <li>identify the organization, if any, the individual represents as a
+ participant in this group,</li>
+ <li>agree to the terms of the <a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">invited
+ expert and collaborators agreement</a> [<a href="#ref-invited-expert">PUB17</a>],</li>
+ <li>accept the participation terms set forth in the charter (including
+ the participation requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+ 3</a> (especially 3.4) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section
+ 6</a> (especially 6.10) of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]).
+ Indicate a specific charter date or version,</li>
+ <li>disclose whether the individual is an employee of a W3C Member;
+ see the <a href="#coi">conflict of interest policy</a>,</li>
+ <li>provide a statement of who will provide the necessary financial
+ support for the individual's participation (e.g., for travel,
+ telephone calls, and conferences), and</li>
+ <li>if the individual's employer (including a self-employed
+ individual) or the organization the individual represents is not a
+ W3C Member, indicate whether that organization intends to join W3C.
+ If the organization does not intend to join W3C, indicate reasons
+ the individual is aware of for this choice.</li>
+ </ul>
+ <p>The Chair <span class="rfc2119">SHOULD NOT</span> designate as an
+ Invited Expert in a Working Group an individual who is an employee of
+ a W3C Member. The Chair <span class="rfc2119">MUST NOT</span> use
+ Invited Expert status to circumvent participation limits imposed by
+ the <a href="#WGCharter">charter</a>.</p>
+ <p>An Invited Expert 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>the Chair or Director withdraws the invitation to participate, or</li>
+ <li>the individual <a href="#resignation">resigns</a>.</li>
+ </ul>
+ <h5>6.2.1.4 <a id="invited-expert-ig">Invited Expert</a> in an Interest
+ Group</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>
+ <h5>6.2.1.5 <a id="team-rep-wg">Team Representative in a Working Group</a></h5>
+ <p>An individual is a Team representative in a Working Group when so
+ designated by W3C management.</p>
+ <p>An 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>
+ <h5>6.2.1.6 <a id="team-rep-ig">Team Representative in an Interest
+ Group</a></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>
+ <h5>6.2.1.7 <a id="good-standing">Good Standing in a Working Group</a></h5>
+ <p>Participation by an individual in a Working Group on an ongoing basis
+ implies a serious commitment to the charter, including all of the
+ following:</p>
+ <ul>
+ <li>attending most meetings of the Working Group.</li>
+ <li>providing deliverables or drafts of deliverables in a timely
+ fashion.</li>
+ <li>being familiar with the relevant documents of the Working Group,
+ including minutes of past meetings.</li>
+ <li>following discussions on relevant mailing list(s).</li>
+ </ul>
+ <p>At the first Working Group meeting that follows any <a href="#cfp">Call
+ for Participation</a>, all participants are in Good Standing. If a
+ Member or Invited Expert joins the Working Group after the end of that
+ meeting, the Member Representative or Invited Expert does not attain
+ Good Standing until the start of the second consecutive meeting that
+ individual attends.</p>
+ <p>When the Chair and the <a href="#TeamContact">Team Contact</a>
+ agree, the Chair <span class="rfc2119">MAY</span> declare that a
+ participant is no longer in Good Standing (henceforth called "Bad
+ Standing"). If there is disagreement between the Chair and the Team
+ Contact about standing, the Director determines the participant's
+ standing. The Chair <span class="rfc2119">MAY</span> declare a Team
+ participant to be in Bad Standing, but it is clearly preferable for
+ the Chair, Team participant, and W3C management to resolve issues
+ internally.</p>
+ <p>A participant <span class="rfc2119">MAY</span> be declared in Bad
+ Standing in any of the following circumstances:</p>
+ <ul>
+ <li>the individual has missed more than one of the last three <a href="#distributed-meeting">distributed
+ meetings</a>.</li>
+ <li>the individual has missed more than one of the last three <a href="#ftf-meeting">face-to-face
+ meetings</a>.</li>
+ <li>the individual has not provided deliverables in a timely fashion
+ twice in sequence.</li>
+ <li>the individual has not followed the <a href="#coi">conflict of
+ interest policy</a> by disclosing information to the rest of the
+ group.</li>
+ </ul>
+ <p>Although all participants representing an organization <span class="rfc2119">SHOULD</span>
+ attend all meetings, attendance by one representative of an
+ organization satisfies the meeting attendance requirement for all
+ representatives of the organization.</p>
+ <p>The above criteria <span class="rfc2119">MAY</span> be relaxed if
+ the Chair and Team Contact agree that doing so will not set back the
+ Working Group. For example, the attendance requirement can be relaxed
+ for reasons of expense (e.g., cost of travel) or scheduling (for
+ example, an exceptional teleconference is scheduled at 3:00 a.m. local
+ time for the participant). It is the responsibility of the Chair and
+ Team Contact to apply criteria for Good Standing consistently.</p>
+ <p>When a participant risks losing Good Standing, the Chair and Team
+ Contact are expected to discuss the matter with the participant and
+ the participant's Advisory Committee representative (or W3C management
+ for the Team) before declaring the participant in Bad Standing.</p>
+ <p>The Chair declares a participant in Bad Standing by informing the
+ participant's Advisory Committee representative and the participant of
+ the decision. If the Advisory Committee representative and Chair
+ differ in opinion, the Advisory Committee representative <span class="rfc2119">MAY</span>
+ ask the <a href="#def-Director">Director</a> to confirm or deny the
+ decision. <a href="#invited-expert-wg">Invited Experts</a> declared
+ in Bad Standing <span class="rfc2119">MAY</span> appeal to the
+ Director.</p>
+ <p>The Chair and Team Contact restore Good Standing and <span class="rfc2119">SHOULD</span>
+ do so when the individual in Bad Standing satisfies the above
+ criteria. The Chair <span class="rfc2119">MUST</span> inform the
+ individual's Advisory Committee representative of any change in
+ standing.</p>
+ <p>When a Member representative permanently replaces another (i.e., is
+ not simply a temporary <a href="#mtg-substitute">substitute</a>), the
+ new participant inherits the standing of the departing participant.</p>
+ <p>Changes in an individual's standing in a Working Group have no effect
+ on the obligations associated with Working Group participation that
+ are described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ <p><strong>Note:</strong> In general, the time commitment for
+ participating in an Interest Group is less than that for a Working
+ Group; see the section on <a href="#ig-charter-participation">participation
+ provisions in an Interest Group charter</a>.</p>
+ <h4>6.2.2 <a id="WGCharterDevelopment">Working Group and Interest Group
+ Charter Development</a></h4>
+ <p>The Team <span class="rfc2119">MUST</span> 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 <span class="rfc2119">MAY</span>
+ express their general support on the <a href="#ACCommunication">Advisory
+ Committee discussion list</a>.</p>
+ <p>W3C <span class="rfc2119">MAY</span> begin work on a Working Group
+ or Interest Group charter at any time.</p>
+ <h4>6.2.3 <a id="CharterReview">Advisory Committee Review</a> of a
+ Working Group or Interest Group Charter</h4>
+ <p>The Director <span class="rfc2119">MUST</span> solicit <a href="#ReviewAppeal">Advisory
+ Committee review</a> of every new or substantively modified Working
+ Group or Interest Group charter. The Director is <span class="rfc2119">NOT
+ REQUIRED</span> to solicit Advisory Committee review prior to a
+ charter extension or for minor changes.</p>
+ <p>The Director's Call for Review of a substantively modified charter <span
+ class="rfc2119">MUST</span> highlight important changes (e.g.,
+ regarding deliverables or resource allocation) and include rationale
+ for the changes.</p>
+ <h4>6.2.4 <a id="cfp">Call for Participation in a Working Group or
+ Interest Group</a></h4>
+ <p>After Advisory Committee review of a Working Group or Interest Group
+ charter, the Director <span class="rfc2119">MAY</span> issue a Call
+ for Participation to the Advisory Committee. Charters <span class="rfc2119">MAY</span>
+ 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 <span class="rfc2119">MUST</span> 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> <span class="rfc2119">MUST</span> be designated (or
+ re-designated).</p>
+ <p>Advisory Committee representatives <span class="rfc2119">MAY</span>
+ <a href="#ACAppeal">appeal</a> creation or substantive modification of
+ a Working Group or Interest Group charter. <span class="issue">For Activities
+ the appeal required dissent in the review. Should we have that
+ constraint?</span></p>
+ <h4>6.2.5 <a id="charter-extension">Working Group and Interest Group
+ Charter Extension</a></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 <span class="rfc2119">MUST</span>
+ indicate the new duration. The announcement <span class="rfc2119">MUST</span>
+ 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 <span class="rfc2119">NOT REQUIRED</span> to re-designate <a
+ href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited
+ Experts</a>.</p>
+ <p>Advisory Committee representatives <span class="rfc2119">MAY</span>
+ <a href="#ACAppeal">appeal</a> the extension of a Working Group or
+ Interest Group charter. <span class="issue">For Activities the appeal
+ required dissent in the review. Should we have that constraint?</span></p>
+ <h4>6.2.6 <a id="WGCharter">Working Group and Interest Group Charters</a></h4>
+ <p>A Working Group or Interest Group charter <span class="rfc2119">MUST</span>
+ 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 <span class="rfc2119">NOT REQUIRED</span> 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 <span
+ class="rfc2119">MUST</span> 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 <span class="rfc2119">MUST</span>
+ specify when required deliverables are expected from the other
+ groups. The charter <span class="rfc2119">SHOULD</span> 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 <span class="rfc2119">SHOULD</span>
+ specify expected conformance to the deliverables of the other
+ groups;</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 <span class="rfc2119">MUST NOT</span> be sooner than
+ <span class="time-interval">eight weeks</span> after the date of the
+ proposal. <span class="issue">This was adopted from Activities. Is
+ 8 weeks from the proposal date enough, or should it be from e.g.
+ Call for Participation, or should we move the requirement to the
+ meetings information, or…?</span></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>
+ </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 <span class="rfc2119">MAY</span>
+ include provisions regarding participation, including specifying that
+ the <a id="ig-mail-only">only requirement for participation (by
+ anyone) in the Interest Group</a> is subscription to the Interest
+ Group mailing list. This type of Interest Group <span class="rfc2119">MAY</span>
+ have <a href="#public-participant-ig">public participants</a>.</p>
+ <p>A charter <span class="rfc2119">MAY</span> include additional voting
+ procedures, but those procedures <span class="rfc2119">MUST NOT</span>
+ conflict with the <a href="#Votes">voting requirements</a> of the
+ Process Document.</p>
+ <p>A charter <span class="rfc2119">MAY</span> include provisions other
+ than those required by this document. The charter <span class="rfc2119">SHOULD</span>
+ 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>6.2.7 <a id="three-month-rule">Working Group "Heartbeat"
+ Requirement</a></h4>
+ <p>It is important that a Working Group keep the Membership and public
+ informed of its activity and progress. To this end, each Working Group
+ <span class="rfc2119">SHOULD</span> publish in the <a href="http://www.w3.org/TR/">W3C
+ technical reports index</a> a new draft of <em>each active
+ technical report</em> at least once every three months. An active
+ technical report is a Working Draft, Candidate Recommendation,
+ Proposed Recommendation, or Proposed Edited Recommendation. Each
+ Working Group <span class="rfc2119">MUST</span> publish a new draft
+ of <em>at least one of its active technical reports</em> on the <a href="http://www.w3.org/TR/">W3C
+ technical reports index</a> [<a href="#ref-doc-list">PUB11</a>] at
+ least once every three months.</p>
+ <p>Public progress reports are also important when a Working Group does
+ not update a technical report within three months (for example, when
+ the delay is due to a challenging technical issue) or when a Working
+ Group has no active technical reports (for example, because it is
+ developing a test suite).</p>
+ <p>In exceptional cases, the Chair <span class="rfc2119">MAY</span> ask
+ the Director to be excused from this publication requirement. However,
+ in this case, the Working Group <span class="rfc2119">MUST</span>
+ issue a public status report with rationale why a new draft has not
+ been published.</p>
+ <p>There are several reasons for this Working Group "heartbeat"
+ requirement:</p>
+ <ul>
+ <li>To promote public accountability;</li>
+ <li>To encourage Working Groups to keep moving forward, and to
+ incorporate their decisions into readable public documents. People
+ cannot be expected to read several months of a group's mailing list
+ archive to understand where the group stands;</li>
+ <li>To notify interested parties of updated work in familiar a place
+ such as the W3C home page and index of technical reports.</li>
+ </ul>
+ <p>As an example, suppose a Working Group has one technical report as a
+ deliverable, which it publishes as a Proposed Recommendation. Per the
+ heartbeat requirement, the Working Group is required to publish a new
+ draft of the Proposed Recommendation at least once every three months,
+ even if it is only to revise the status of the Proposed Recommendation
+ document (e.g., to provide an update on the status of the decision to
+ advance). The heartbeat requirement stops when the document becomes a
+ Recommendation (or a Working Group Note).</p>
+ <h4>6.2.8 <a id="GeneralTermination">Working Group and Interest Group
+ Closure</a></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, <span class="rfc2119">MAY</span>
+ close a group prior to the date specified in the charter in any of the
+ following circumstances:</p>
+ <ul>
+ <li>There are insufficient resources to produce chartered deliverables
+ or to maintain the group, according to priorities established within
+ W3C.</li>
+ <li>The group produces chartered deliverables ahead of schedule.</li>
+ <li>The Activity to which the group belongs terminates.</li>
+ </ul>
+ <p>The Director closes a Working Group or Interest Group by announcement
+ to the Advisory Committee.</p>
+ <p>Closing a Working Group has implications with respect to the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ <h3>6.3 <a id="GroupsCG">Coordination Groups</a></h3>
+ <p>W3C Activities interact in many ways. There are dependencies between
+ groups within the same Activity or in different Activities. There are
+ also dependencies between W3C Activities and the activities of other
+ organizations. Examples of dependencies include the use by one
+ technology of another being developed elsewhere, scheduling
+ constraints between groups, and the synchronization of publicity for
+ the announcement of deliverables. Coordination Groups are created to
+ manage dependencies so that issues are resolved fairly and the
+ solutions are consistent with W3C's mission and results.</p>
+ <p>Where a Coordination Group's scope covers two groups with unresolved
+ disputes or tensions, it is the first locus of resolution of these
+ disputes.</p>
+ <h4>6.3.1 <a id="CGParticipation">Coordination Group Participation
+ Requirements</a></h4>
+ <p>There are four types <a id="cgparticipant">participants in a
+ Coordination Group</a>: the <a href="#GeneralChairs">Chair</a>, the
+ Chair of each coordinated group (to promote effective communication
+ among the groups), Invited Experts (e.g., liaisons to groups inside or
+ outside W3C), and Team representatives (including the <a href="#TeamContact">Team
+ Contact</a>). The requirements for Invited Expert participation are
+ the same as for an <a href="#invited-expert-wg">Invited Expert in a
+ Working Group</a>.</p>
+ <p>Coordination Group participants <span class="rfc2119">MUST</span>
+ follow the <a href="#coi">conflict of interest policy</a> by
+ disclosing information to the rest of the group.</p>
+ <p>There are no Good Standing requirements for Coordination Group
+ participation; regular participation in a relevant Coordination Group
+ is one of the <a href="/Guide/chair-roles">roles of a group Chair
+ [MEM14]</a>.</p>
+ <h4>6.3.2 <a id="CGCreation">Coordination Group Creation and Closure</a></h4>
+ <p>The Director creates or modifies a Coordination Group by sending the
+ <a href="#CGCharter">Coordination Group charter</a> to the Advisory
+ Committee. A Coordination Group <span class="rfc2119">MAY</span> be
+ created as part of an <a href="#ActivityProposal">Activity Proposal</a>
+ (for example to coordinate other groups in the Activity or to draw up
+ charters of future groups), or during the life of an Activity when
+ dependencies arise. A Coordination Group <span class="rfc2119">MAY</span>
+ operate as part of several W3C Activities.</p>
+ <p>A Coordination Group <span class="rfc2119">SHOULD</span> close when
+ there is no longer a perceived need for coordination.</p>
+ <h4>6.3.3 <a id="CGCharter">Coordination Group Charters</a></h4>
+ <p>A Coordination Group charter <span class="rfc2119">MUST</span>
+ include all of the following information:</p>
+ <ul>
+ <li>The group's mission;</li>
+ <li>The scope of the group's work, including the names of coordinated
+ groups and contact information for those groups;</li>
+ <li>Any dependencies by groups within or outside of W3C on this group;</li>
+ <li>Any dependencies of this group on other groups within or outside
+ of W3C; see the section on <a href="#Liaisons">liaisons with other
+ organizations</a>.</li>
+ <li>The <a href="#confidentiality-levels">level of confidentiality</a>
+ of the group's proceedings;</li>
+ <li>Meeting mechanisms and expected frequency;</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 level of involvement by the Team.</li>
+ </ul>
+ <p>A charter <span class="rfc2119">MAY</span> include additional voting
+ procedures, but those procedures <span class="rfc2119">MUST NOT</span>
+ conflict with the <a href="#Votes">voting requirements</a> of the
+ Process Document.</p>
+ <p>A charter <span class="rfc2119">MAY</span> include provisions other
+ than those required by this document. The charter <span class="rfc2119">SHOULD</span>
+ highlight whether additional provisions impose constraints beyond
+ those of the W3C Process Document.</p>
+ </section>
<h2 id="Reports">7 W3C Technical Report Development Process</h2>
<p>The W3C technical report development process is the set of steps and
requirements followed by W3C <a href="#GroupsWG">Working Groups</a> to
@@ -3510,16 +3448,22 @@
Klensin (MCI), Tim Krauskopf (Spyglass), Kari Laihonen (Ericsson), Ken
Laskey (MITRE), Ora Lassila (Nokia), Håkon Wium Lie (Opera Software),
Chris Lilley (W3C), Bede McCall (MITRE), Giri Mandyam (Qualcomm), Larry
- Masinter (Adobe Systems),
- Qiuling Pan (Huawei),
- TV Raman (Google), Thomas Reardon (Microsoft), Claus von Riegen (SAP
- AG), David Singer (Apple), David Singer (IBM), Ralph Swick (W3C), Anne
- van Kesteren, Jean-Charles Verdié (MStar), Chris Wilson (Google), Lauren
- Wood (unaffiliated), Steve Zilles (Adobe Systems).</p>
+ Masinter (Adobe Systems), Qiuling Pan (Huawei), TV Raman (Google),
+ Thomas Reardon (Microsoft), Claus von Riegen (SAP AG), David Singer
+ (Apple), David Singer (IBM), Ralph Swick (W3C), Anne van Kesteren,
+ Jean-Charles Verdié (MStar), Chris Wilson (Google), Lauren Wood
+ (unaffiliated), Steve Zilles (Adobe Systems).</p>
<h2 id="changes">15 Changes</h2>
- <p>This document is effectively the same as the 1 August 2014 Process<a href="#Reports"></a>.
- <a href="https://dvcs.w3.org/hg/AB/">Detailed change logs</a> are
- available.</p>
+ <p>This document is based on 1 August 2014 Process. <a href="https://dvcs.w3.org/hg/AB/">Detailed
+ change logs</a> are available.</p>
+ <p>Notable changes include:</p>
+ <ul>
+ <li>Remove <a id="def-Activity">A</a><a id="ActivityStatement">c</a><a
+ id="ActivityDevelopment">t</a><a id="ActivityCreation">i</a><a id="ActivityModification">v</a><a
+ id="ActivityExtension">i</a><a id="ActivityTermination">t</a><a id="ActivityProposal">ies</a>
+ <a id="Activities">f</a>rom the Process (as resolved multiple times
+ since 2007) </li>
+ </ul>
</div>
</body>
</html>