--- a/cover.html Sat Sep 13 23:13:45 2014 +0200
+++ b/cover.html Sat Sep 13 23:40:10 2014 +0200
@@ -19,7 +19,7 @@
<div class="head"><a href="http://www.w3.org/"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home"
height="48" width="72"></a>
<h1>W3C Draft Process Document</h1>
- <h2 class="notoc">14 August 2014 Editor's Draft</h2>
+ <h2 class="notoc">14 September 2014 Editor's Draft</h2>
<dl>
<dt>Latest Editor's version:</dt>
<dd> <a href="https://dvcs.w3.org/hg/AB/raw-file/default/cover.html">https://dvcs.w3.org/hg/AB/raw-file/default/cover.html</a></dd>
@@ -61,15 +61,21 @@
<p>For more information about the W3C mission and the history of W3C, please
refer to <a href="http://www.w3.org/Consortium/">About W3C</a> [<a href="#ref-mission">PUB15</a>].</p>
<h2 class="notoc"><a id="status">Status of this Document</a></h2>
- <p>This is the 14 August 2014 Editor's draft for the next version of the W3C
- Process Document. This document is a copy of the 1 August 2014 Process,
- developed between the <a href="/2002/ab/">W3C Advisory Board</a> and the
- <a href="http://www.w3.org/community/w3process/">Revising W3C Process
- Community Group</a> and adopted as the currently operative Process.
- During the rest of 2014 the document will be developed, in preparation for
- adopting a revised process in 2015.</p>
+ <p>This is the 14 September 2014 Editor's draft for the proposed next
+ version of the W3C Process Document. This document is based on the 1
+ August 2014 Process, developed between the <a href="/2002/ab/">W3C
+ Advisory Board</a> and the <a href="http://www.w3.org/community/w3process/">Revising
+ W3C Process Community Group</a> and adopted as the currently operative
+ Process. During the rest of 2014 the document will be developed in
+ preparation for adopting a revised process in 2015.</p>
<p>W3C, including all existing chartered groups, follows the <a href="http://www.w3.org/Consortium/Process/">most
recent operative Process Document</a> announced to the Membership.</p>
+ <p>In <em>this draft</em>, Section 5 (Activities) has been almost
+ completely removed, with a few requirements moved to other parts of the
+ process. Two short pieces remain temporarily, pending a decision about
+ whether to maintain the requirements they include. This draft will be
+ considered by the Advisory Board at its face to face meeting on 16/17
+ September. Public comment is also invited on the draft.</p>
<p>Please send comments about this document to the <a href="http://www.w3.org/community/w3process/">Revising
W3C Process Community Group</a> (<a href="http://lists.w3.org/Archives/Public/public-w3process/">Mailing
list archive</a>, publicly available) or to process-issues@w3.org (<a href="http://lists.w3.org/Archives/Member/process-issues">Member-only
@@ -395,7 +401,9 @@
<p>Here is a general overview of how W3C standardizes a Web technology. In
many cases, the goal of this work is a <a href="#RecsW3C">W3C
Recommendation</a>, the W3C equivalent of a Web standard.</p>
- <ol>
+ <p class="issue">The following text assumes Activities exist, and is
+ related to an old piece of work that many people don't know.</p>
+ <ol class="issue">
<li>People generate interest in a particular topic (e.g., Web services).
For instance, Members express interest in the form of <a href="#Submission">Member
Submissions</a>, and the <a href="#Team">Team</a> monitors work
@@ -406,7 +414,7 @@
<li>When there is enough interest in a topic (e.g., after a successful
Workshop and/or discussion on an <a href="#ACCommunication">Advisory
Committee mailing list</a>), the Director announces the <a href="#ActivityDevelopment">development
- of a proposal for a new Activity</a> or <a href="#WGCharterDevelopment">Working
+ of a proposal for a new</a> or <a href="#WGCharterDevelopment">Working
Group charter</a>, depending on the breadth of the topic of
interest. An <a href="#ActivityProposal">Activity Proposal</a>
describes the scope, duration, and other characteristics of the
@@ -473,7 +481,7 @@
<ul>
<li>reviews plans for W3C at each <a href="#ACMeetings">Advisory
Committee meeting</a>;</li>
- <li>reviews formal proposals from the W3C Director: <a href="#ActivityProposal">Activity
+ <li>reviews formal proposals from the W3C Director: <a href="#CharterReview">Charter
Proposals</a>, <a href="#RecsPR">Proposed Recommendations</a>,
and <a href="#GAProcess">Proposed Process Documents</a>.</li>
<li>elects the <a href="#AB">Advisory Board</a> participants other
@@ -618,9 +626,10 @@
<ul>
<li>The allocation of the annual budget, including size of the Team
and their approximate deployment.</li>
- <li>A list of all Activities and brief status statement about each,
- in particular those started or terminated since the previous
- Advisory Committee meeting.</li>
+ <li>A list of all <span class="issue">Activities (should this apply
+ to WGs and IGs now Activities have been removed? ISSUE-115)</span>
+ and brief status statement about each, in particular those started
+ or terminated since the previous Advisory Committee meeting.</li>
<li>The allocation of resources to pursuing <a href="#Liaisons">liaisons</a>
with other organizations.</li>
</ul>
@@ -648,7 +657,7 @@
as part of the Team; see the <a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C
Fellows Program</a> [<a href="#ref-fellows">PUB32</a>]. The Team
provides technical leadership about Web technologies, organizes and
- manages W3C Activities to reach goals within practical constraints (such
+ manages W3C activities to reach goals within practical constraints (such
as resources available), and communicates with the Members and the
public about the Web and W3C technologies.</p>
<p>The Team is led by the Director, W3C Chair, and Chief Operating
@@ -659,11 +668,11 @@
at W3C and as such, is responsible for assessing <a href="#def-Consensus"
id="DirectorDecision">consensus</a> within W3C for architectural
choices, publication of <a href="#Reports">technical reports</a>, and
- new <a href="#Activities">Activities</a>. The Director appoints group <a
- href="#GeneralChairs">Chairs</a> and has the role of "tie-breaker" for
- questions of <a href="#good-standing">Good Standing</a> in a Working
- Group or <a href="#WGAppeals">appeal of a Working Group decision</a>.
- The Director is generally Chair of the <a href="#TAG">TAG</a>.</p>
+ new activities. The Director appoints group <a href="#GeneralChairs">Chairs</a>
+ and has the role of "tie-breaker" for questions of <a href="#good-standing">Good
+ Standing</a> in a Working Group or <a href="#WGAppeals">appeal of a
+ Working Group decision</a>. The Director is generally Chair of the <a
+ href="#TAG">TAG</a>.</p>
<p>The <a id="def-W3CChair">W3C Chair</a> leads Member relations, and <a
href="#Liaisons">liaisons</a> with other organizations, governments,
and the public.</p>
@@ -968,7 +977,7 @@
<li>Social competence in one's role</li>
</ol>
<p>Advisory Committee representatives who nominate individuals from their
- organization for participation in W3C Activities are responsible for
+ organization for participation in W3C activities are responsible for
assessing and attesting to the qualities of those nominees.</p>
<p>See also the participation requirements described in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section
6</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
@@ -991,8 +1000,7 @@
the appropriate process. For instance, the Director <span class="rfc2119">MAY</span>
appoint a new group Chair when the current Chair changes affiliations
(e.g., if there is a risk of conflict of interest, or if there is risk
- that the Chair's new employer will be over-represented within a W3C
- Activity).</p>
+ that the Chair's new employer will be over-represented within a W3C activity).</p>
<p>The following are some scenarios where disclosure is appropriate:</p>
<ul>
<li>Paid consulting for an organization whose activity is relevant to
@@ -1314,7 +1322,8 @@
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>
+ <li>Public results of W3C Activities <span class="issue">Working
+ group/IG documents, mailing lists, what?</span> 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
@@ -1982,7 +1991,11 @@
(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>
+ operate as part of several W3C Activities. <span class="issue">What
+ to do with this? <a href="https://www.w3.org/community/w3process/track/issues/129">ISSUE-129</a>
+ already proposes to remove Coordination Groups. Otherwise, we'll
+ need to explain them without Activities (which is just editorial
+ work) </span></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>
@@ -2834,10 +2847,10 @@
decisions and decisions by the Director. A <a id="def-w3c-decision">W3C
decision</a> is one where the Director (or the Director's delegate)
has exercised the role of assessing consensus after an <a href="#ACReview">Advisory
- Committee review</a> of an <a href="#ActivityProposal">Activity
- Proposal</a>, after a <a href="#cfr">Call for Review of a Proposed
- Recommendation</a>, after a <a href="#cfr-edited">Call for Review of
- a Proposed Recommendation</a>, after a <a href="#proposed-rescinded-rec">Proposal
+ Committee review</a> of an <a href="#CharterReview">Charter Proposal</a>,
+ after a <a href="#cfr">Call for Review of a Proposed Recommendation</a>,
+ after a <a href="#cfr-edited">Call for Review of a Proposed
+ Recommendation</a>, after a <a href="#proposed-rescinded-rec">Proposal
to Rescind a W3C Recommendation</a>, and after a <a href="#GAProcess">Proposed
Process
Document</a> review.</p>
@@ -2954,7 +2967,7 @@
seat".</p>
<h2>9 <a id="GAEvents">Workshops and Symposia</a></h2>
<p>The Team organizes <a id="EventsW">Workshops</a> and <a id="EventsS">Symposia</a>
- to promote early involvement in the development of W3C Activities from
+ to promote early involvement in the development of W3C activities from
Members and the public.</p>
<p>The goal of a Workshop is usually either to convene experts and other
interested parties for an exchange of ideas about a technology or
@@ -2968,7 +2981,7 @@
indicate participation requirements or limits, and expected deliverables
(e.g., reports and minutes). Organization of an event does not guarantee
further investment by W3C in a particular topic, but <span class="rfc2119">MAY</span>
- lead to proposals for new Activities or groups.</p>
+ lead to proposals for new activities or groups.</p>
<p>Workshops and Symposia generally last one to three days. If a Workshop
is being organized to address the pressing concerns of Members, the Team
<span class="rfc2119">MUST</span> issue the Call for Participation no
@@ -3089,7 +3102,8 @@
<p>After acknowledgment, the Submitter(s) <span class="rfc2119">MUST NOT</span>,
<strong>under any circumstances</strong>, imply W3C investment in the
Member Submission until, and unless, the material has been adopted as
- part of a W3C <a href="#def-Activity">Activity</a>.</p>
+ part of a W3C <a href="#def-Activity">Activity</a>. <span class="issue">Working
+ Group?</span></p>
<h4>11.1.1 <a id="SubmissionScope">Scope of Member Submissions</a></h4>
<p>When a technology overlaps in scope with the work of a chartered
Working Group, Members <span class="rfc2119">SHOULD</span> <a href="#group-participation">participate
@@ -3101,10 +3115,9 @@
NOT</span> publish the contributed documents as Working Group Notes
since Working Group Notes represent group output, not input to the
group.</p>
- <p>On the other hand, while W3C is in the early stages of developing an
- Activity Proposal or charter, Members <span class="rfc2119">SHOULD</span>
- use the Submission process to build consensus around concrete proposals
- for new work.</p>
+ <p>On the other hand, while W3C is in the early stages of developing a
+ charter, Members <span class="rfc2119">SHOULD</span> use the Submission
+ process to build consensus around concrete proposals for new work.</p>
<p>Members <span class="rfc2119">SHOULD NOT</span> submit materials
covering topics well outside the scope of <a href="http://www.w3.org/Consortium/mission">W3C's
mission</a> [<a href="#ref-mission">PUB15</a>].</p>