--- a/cover.html Wed Aug 03 19:49:06 2016 +0200
+++ b/cover.html Mon Oct 10 03:02:52 2016 +0200
@@ -3,7 +3,7 @@
<head>
<meta charset="utf-8">
<meta name="keywords" content="W3C Process, Consortium, Team, Recommendation, Advisory Committee,
-Advisory Board, Working Group, Coordination Group, Interest Group, W3C Activity, Workshop, charter,Working Draft, Process Document, Candidate Recommendation, Director, Proposed Recommendation, Submission request">
+Advisory Board, Working Group, Coordination Group, Interest Group, W3C Activity, Workshop, charter, Working Draft, Process Document, Candidate Recommendation, Director, Proposed Recommendation, Submission request">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/base.css">
<title>World Wide Web Consortium Process Document</title>
<style type="text/css">
@@ -29,9 +29,7 @@
<h2 class="notoc">3 August 2016 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>
- <dt>Previous Editor's version:</dt>
- <dd><a href="https://dvcs.w3.org/hg/AB/raw-file/64c6d6a5b1c0/cover.html">https://dvcs.w3.org/hg/AB/raw-file/64c6d6a5b1c0/cover.html</a></dd>
+ <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>
<dt>Latest operative version:</dt>
<dd><a href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a></dd>
<dt>Editor:</dt>
@@ -317,11 +315,12 @@
promote the development of high-quality standards based on the <a href="#Consensus">consensus</a> of the Membership, Team,
and public. W3C processes promote fairness, responsiveness, and progress: all facets of the W3C mission.
This document describes the processes W3C follows in pursuit of its mission.</p>
+
<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>
+ <a href="#RecsW3C">W3C Recommendation</a> - a Web standard.</p>
<ol>
- <li>People generate interest in a particular topic (e.g., Web services). For instance, Members express interest in the form
+ <li>People generate interest in a particular topic. For instance, Members express interest in the form
of <a href="#Submission">Member Submissions</a>, and the <a href="#Team">Team</a> monitors work inside and outside of W3C
for signs of interest. Also, W3C is likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to
discuss topics that interest the W3C community.</li>
@@ -445,12 +444,12 @@
who, though not employed by the organization, <em class="rfc2119">may</em> exercise the rights of
<a href="#member-rep">Member representatives</a>.
- <p>For Member Consortia who have individual persons as members these individuals <em class="rfc2119">must</em> disclose their
- employment affiliation when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a> apply.
- Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the W3C Member organization
- and not the particular interests of their employers.</p>
-
- <p>For Member Consortia who have organizations as Members, all such designated representatives must be an
+ <p>For Member Consortia that have individual people as members these individuals <em class="rfc2119">must</em> disclose
+ their employment affiliation when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a>
+ apply. Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the
+ W3C Member organization and not the particular interests of their employers.</p>
+
+ <p>For Member Consortia that have organizations as Members, all such designated representatives must be an
official representative of the Member organization (i.e. a Committee or Task Force Chairperson) and
<em class="rfc2119">must</em> disclose their employment affiliation when participating in W3C work. Provisions for
<a href="#MemberRelated">related Members</a> apply.
@@ -511,7 +510,7 @@
<dt><em>Resources</em></dt>
<dd>
<ul>
- <li>The number of Full and Affiliate W3C Members.</li>
+ <li>The number of W3C Members at each level.</li>
<li>An overview of the financial status of W3C.</li>
</ul>
</dd>
@@ -806,8 +805,8 @@
W3C membership evolves (since, for example, the individual might have a relationship with an organization that joins or
leaves W3C). Each section in this document that describes a W3C group provides more detail about the disclosure mechanisms
for that group.</p>
- <p>The ability of an individual to fulfill a role within a group without risking a conflict of interest is clearly a
- function of the individual's affiliations. When these affiliations change, the individual's assignment to the role
+ <p>The ability of an individual to fulfill a role within a group without risking a conflict of interest depends on
+ the individual's affiliations. When these affiliations change, the individual's assignment to the role
<em class="rfc2119">must</em> be evaluated. The role <em class="rfc2119">may</em> be reassigned according to the
appropriate process. For instance, the Director <em class="rfc2119">may</em> 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
@@ -1073,8 +1072,8 @@
<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="https://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
+ (e.g., weekly) news service and maintains a <a href="https://www.w3.org/participate/eventscal">calendar</a>
+ [<a href="#ref-calendar">PUB36</a>] of official W3C events. Members are encouraged to send schedule and event information
to the Team for inclusion on this calendar.</p>
<h3 id"confidentiality-levels"="">4.1 Confidentiality Levels</h3>
@@ -1149,16 +1148,14 @@
<p>Each group <em class="rfc2119">must</em> have a charter. Requirements for the charter depend on the group type.
All group charters <em class="rfc2119">must</em> be public (even if other proceedings of the group are
- <a href="#Member-only">Member-only</a>). Existing charters that are not yet public <em class="rfc2119">must</em>
- be made public when next revised or extended (with attention to
- <a href="#confidentiality-change">changing confidentiality level</a>).</p>
+ <a href="#Member-only">Member-only</a>).</p>
<p>Each group <em class="rfc2119">must</em> have a <dfn id="GeneralChairs">Chair</dfn> (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="https://www.w3.org/Guide/">Member guide</a> [<a href="#ref-guide">MEM9</a>].</p>
+ <a href="/Guide/chair-roles">role of the Chair</a> is described in the
+ <a href="https://www.w3.org/Guide/">Art of Consensus</a> [<a href="#ref-guide">PUB37</a>].</p>
<p>Each group <em class="rfc2119">must</em> have a <dfn id="TeamContact">Team Contact</dfn>, 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
@@ -1442,7 +1439,7 @@
<p>The <dfn>Reference Draft</dfn> is the latest Working Draft published within 90 days of the
<a href="#first-wd">First Public Working Draft</a> or if no Public Working Draft has been published within 90 days of the
First Public Working Draft it is that First Public Working Draft. It is the specific draft against which exclusions are
- made, as per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-exclusion-with">section 4.1</a> of the
+ made, as per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-exclusion-with">section 4.1</a> of the
<a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
<p>The Adopted Working Draft and the most recent Reference Draft or <a href="#last-call">Candidate Recommendation</a>
@@ -1518,7 +1515,7 @@
<a href="#last-call">Candidate Recommendation</a> phase. This allows the entire W3C membership to provide feedback
on whether the specification is appropriate as a W3C Recommendation, while the Working Group formally collects
implementation experience to demonstrate that the specification works in practice. The next phase is a
- Proposed Recommendation, to finalize the review of W3C Members. If the Director determines that W3C member review
+ Proposed Recommendation, to finalize the review of W3C Members. If the Director determines that W3C Member review
supports a specification becoming a standard, W3C publishes it as a Recommendation.</p>
<p>Groups may also publish documents as W3C Notes, typically either to document information other than technical
specifications, such as use cases motivating a specification and best practices for its use, or to clarify the
@@ -1696,7 +1693,7 @@
<li>gather <a href="#implementation-experience">implementation experience</a></li>
<li>begin formal review by the Advisory Committee, who <em class="rfc2119">may</em> recommend that the document
be published as a W3C Recommendation, returned to the Working Group for further work, or abandoned.</li>
- <li>Provide an exclusion opportunity as per the
+ <li>Provide an exclusion opportunity per the
<a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
A Candidate Recommendation under this process corresponds to the "Last Call Working Draft" discussed in the
Patent Policy.</li>
@@ -1707,7 +1704,7 @@
a stage.</dd>
<dt id="RecsPR">Proposed Recommendation</dt>
<dd>A Proposed Recommendation is a document that has been accepted by the W3C Director as of sufficient quality to become
- a W3C Recommendation. This phase establishes a deadline for the Advisory Committee review which begins with
+ a W3C Recommendation. This phase establishes a deadline for the Advisory Committee review that begins with
Candidate Recommendation. Substantive changes <em class="rfc2119">must</em> not be made to a Proposed Recommendation
except by publishing a new Working Draft or Candidate Recommendation.</dd>
<dt id="RecsW3C">W3C Recommendation (REC)</dt>
@@ -1715,15 +1712,22 @@
has received the endorsement of W3C Members and the Director. W3C recommends the wide deployment of its Recommendations
as standards for the Web. The W3C Royalty-Free IPR licenses granted under the Patent Policy apply to
W3C Recommendations.</dd>
+ <dt id="RecsObs">Obsolete Recommendation</dt>
+ <dd>An Obsolete Recommendation is a specification that W3C does not believe has sufficient market relevance to continue
+ recommending that the community implement it, but does not consider that there are fundamental problems that require the
+ Recommendation be Rescinded. It is possible for an Obsolete Recommendation to receive sufficient market uptake that W3C
+ decides to restore it to Recommendation status. An Obsolete Recommendation has the same status as a W3C Recommendation
+ with regards to W3C Royalty-Free IPR licenses granted under the Patent Policy.</dd>
+ <dt id="RescindedRec">Rescinded Recommendation</dt>
+ <dd>A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses, and believes is unlikely to ever
+ be restored to Recommendation Status. See also clause 10 of the licensing
+ requirements for W3C Recommendations in
+ <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section 5</a> of the
+ <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</dd>
<dt id="WGNote">Working Group Note, Interest Group Note (NOTE) </dt>
<dd>A Working Group Note or Interest Group Note is published by a chartered Working Group or Interest Group to provide
a stable reference for a useful document that is not intended to be a formal standard, or to document work that was
abandoned without producing a Recommendation.</dd>
- <dt id="RescindedRec">Rescinded Recommendation</dt>
- <dd>A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses. See also clause 10 of the licensing
- requirements for W3C Recommendations in
- <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section 5</a> of the
- <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</dd>
</dl>
<p>Working Groups and Interest Groups <em class="rfc2119">may</em> make available "Editor's drafts". Editor's drafts have
@@ -1756,7 +1760,7 @@
<p>Every Technical Report published as part of the Technical Report development process is edited by one or more editors
appointed by a Group Chair. It is the responsibility of these editors to ensure that the decisions of the Group are
correctly reflected in subsequent drafts of the technical report. An editor <em class="rfc2119">must</em> be a participant,
- as a Member representative, Team representative, or Invited Expert in the Group responsible for the document(s) they are
+ per <a href="#group-participation">section 5.2.1</a> in the Group responsible for the document(s) they are
editing. </p>
<p>The Team is <em class="rfc2119">not required</em> to publish a Technical Report that does not conform to the Team's
<a href="https://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>](e.g., for
@@ -1863,10 +1867,10 @@
<dd>Changes that reasonable implementers would not interpret as changing architectural or interoperability requirements
or their implementation. Changes which resolve ambiguities in the specification are considered to change
(by clarification) the implementation requirements and do not fall into this class.</dd>
- <dd>Examples of changes in this class are correcting non-normative code examples where the code clearly conflicts with
+ <dd>Examples of changes in this class include correcting non-normative code examples where the code clearly conflicts with
normative requirements, clarifying informative use cases or other non-normative text, fixing typos or grammatical errors
where the change does not change implementation requirements. If there is any doubt or dissent as to whether requirements
- are changed, such changes do not belong to this class..</dd>
+ are changed, such changes do not fall into this class.</dd>
<dt>3. Corrections that do not add new features</dt>
<dd>These changes <em class="rfc2119">may</em> affect conformance to the specification. A change that affects conformance
is one that:
@@ -2285,7 +2289,7 @@
Such error reports <em class="rfc2119">should</em> be processed no less frequently than quarterly. Readers of the
Recommendation <em class="rfc2119">should</em>
be able easily to find and see the errata that apply to that specific Recommendation.</p>
- <p> Working groups may decide how to document errata. The best practice is a document that identifies itself as based on the
+ <p> Working Groups may decide how to document errata. The best practice is a document that identifies itself as based on the
Recommendation text and clearly identifies the errata and any proposed corrections; other approaches include various forms
of an errata page, possibly auto-generated from a database.</p>
<p>An erratum is resolved by an informative, "proposed" correction generated by the Working Group. A correction becomes part
@@ -2300,15 +2304,15 @@
A Working Group, provided there are no votes against the resolution to publish <em class="rfc2119">may</em> request
publication of a <a href="#rec-pr">Proposed Recommendation</a> or W3C <em class="rfc2119">may</em> publish a
<a href="#rec-pr">Proposed Recommendation</a> to make this class of change without passing through earlier maturity levels.
- Such publications <em class="rfc2119">may</em> be called a <dfn>Proposed Edited Recommendation</dfn>.</p>
+ Such publications are called <dfn>Proposed Edited Recommendation</dfn>s.</p>
<p>To make corrections to a Recommendation that produce <a href="#substantive-change">substantive changes</a> but do not
add new features, or where there were votes against publishing the corrections directly as a
<a href="#rec-pr">Proposed Recommendation</a>, a Working Group <em class="rfc2119">may</em> request publication of a
<a href="#last-call">Candidate Recommendation</a>, without passing through earlier maturity levels.</p>
- <p>In the latter two cases, the resulting Recommendation <em class="rfc2119">may</em> be called an
+ <p>In the latter two cases, the resulting Recommendation is called an
<dfn id="rec-edited">Edited Recommendation</dfn>.</p>
- <p>When requesting the publication of an edited Recommendation as described in this section, in addition to meeting the
+ <p>When requesting the publication of an Edited Recommendation as described in this section, in addition to meeting the
requirements for the relevant maturity level, a Working Group</p>
<ul>
<li><em class="rfc2119">must</em> show that the changes to the document have received
@@ -2321,20 +2325,23 @@
<h3 id="Note">6.8 Publishing a Working Group or Interest Group Note</h3>
- <p>Working Groups and Interest Groups publish material that is not a formal specification as Notes. This includes supporting
- documentation for a specification such as explanations of design principles or use cases and requirements,
- non-normative guides to good practices, as well as specifications where work has been stopped and there is no
- longer consensus for making them a new standard.</p>
+ <p>Working Groups and Interest Groups <em class="rfc2119">may</a> publish work as W3C Notes. Examples include:</p>
+ <ul>
+ <li>supporting documentation for a specification, such as explanations of design principles or
+ use cases and requirements,</li>
+ <li>non-normative guides to good practices,
+ <li>specifications where work has been stopped and there is no longer consensus for making them a new standard.</li>
+ </ul>
<p>In order to publish a Note, a Working Group or Interest Group: </p>
<ul>
- <li> <em class="rfc2119">may</em> publish a Note with or without its prior publication as a Working Draft.</li>
+ <li><em class="rfc2119">may</em> publish a Note with or without its prior publication as a Working Draft.</li>
<li><em class="rfc2119">must</em> record the group's decision to request publication as a Note, and</li>
<li><em class="rfc2119">should</em> publish documentation of significant changes to the technical report since any previous
publication.</li>
</ul>
<p>Possible next steps:</p>
<ul>
- <li>End state: A technical report <em class="rfc2119">may</em> remain a Working Group Note indefinitely</li>
+ <li>End state: A technical report <em class="rfc2119">may</em> remain a Working or Interest Group Note indefinitely</li>
<li>A Working Group <em class="rfc2119">may</em> resume work on technical report within the scope of its charter at any
time, at the maturity level the specification had before publication as a Note</li>
</ul>
@@ -2343,17 +2350,23 @@
<h3 id="rec-rescind">6.9 Obsoleting or Rescinding a W3C Recommendation</h3>
+ <p>It is possible W3C decides that a particular Recommendation should no longer be recommended for implementation.
+ There are two designations for such resignations, chosen depending on how strongly W3C wishes to advise against
+ using the specification.</p>
+
+ <p>W3C <em class="r4fc2119">may</em> obsolete a Recommendation, for example if the W3C Community decides that
+ the Recommendation no longer represents best practices, or is not adopted and is not apparently likely to be adopted.
+ An Obsolete Recommendation <em class="r4fc2119">may</em> be restored to normal Recommendation,
+ for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
+
<p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example if the Recommendation contains many
errors that conflict with a later version, or if W3C discovers burdensome patent claims that affect implementers
and cannot be resolved; see the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
[<a href="#ref-patentpolicy">PUB33</a>] and in particular
<a href="https://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section 5</a> (bullet 10) and
- <a href="https://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section 7.5</a>.</p>
-
- <p>W3C may obsolete a Recommendation, for example if the W3C Community decides that the Recommendation
- no longer represents best practices, or is not adopted and is unlikely to be adopted. Obsoletion may be reversed,
- using the same process as for obsoleting a Recommendation, if for example a specification is later more broadly
- adopted.</p>
+ <a href="https://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section 7.5</a>. A Recommendation
+ <em class="r4fc2119">should not</em> be rescinded if W3C believes there is a reasonable prospect of it being
+ restored. However a Rescinded Recommendation <em class="r4fc2119">may</em> be restored to a normal Recommendation.</p>
<p>W3C only rescinds or obsoletes entire Recommendations. To rescind or obsolete some part of a Recommendation,
W3C follows the process for <a href="#rec-modify">modifying a Recommendation</a>.</p>
@@ -2363,27 +2376,27 @@
although it is not recommended for future implementation; a Rescinded Recommendation ceases to be in effect
and no new licenses are granted under the Patent Policy.</p>
- <p>The Director <em class="rfc2119">may</em> recommend obsoleting or rescinding a Recommendation. The Director
- <em class="rfc2119">must</em> begin a review of a proposal to obsolete, un-obsolete or rescind a Recommendation
+ <p>The Director <em class="rfc2119">may</em> recommend obsoleting rescinding or restoring a Recommendation. The Director
+ <em class="rfc2119">must</em> begin a review of a proposal to obsolete, rescind or restore a Recommendation
when requested to do so by any of the following:</p>
<ul>
<li>The Working Group who produced, or is chartered to maintain, the Recommendation.</li>
<li>The TAG, if there is no such Working Group</li>
<li>Any individual who made a request to the relevant Working Group as described above, or the TAG if such a group
- does not exist, to consider a Recommendation for obsoletion or rescindment, whose request was not answered
+ does not exist, to obsolete, rescind, or restore a Recommendation, where the request was not answered
within 90 days</li>
<li>5% of the members of the Advisory Committee</li>
</ul>
- <p id="proposed-rescinded-rec">For any review of a proposal to obsolete or rescind a Recommendation the Director
- <em class="">must</em>:</p>
+ <p id="proposed-rescinded-rec">For any review of a proposal to obsolete rescind, or restore a Recommendation the Director
+ <em class="rfc2119">must</em>:</p>
<ul>
- <li>Announce the proposal to all Working Group Chairs, and to the Public.</li>
- <li>indicate that this is a proposal to Rescind, Obsolete, or reverse the Obsoletion of, a Recommendation</li>
- <li>identify the Recommendation by URL.</li>
- <li>publish a rationale for rescinding the Recommendation.</li>
+ <li>Announce the proposal to all Working Group Chairs, and to the Public</li>
+ <li>indicate that this is a proposal to Rescind, Obsolete, or restore, a Recommendation</li>
+ <li>identify the Recommendation by URL</li>
+ <li>publish a rationale for the proposal</li>
<li>identify known dependencies and solicit review from all dependent Working Groups</li>
<li>solicit public review</li>
<li>specify the deadline for review comments, which must be at least four weeks after the Director's announcement</li>
@@ -2392,7 +2405,7 @@
<p>and <em class="rfc2119">should</em></p>
<ul>
- <li>identify known implementation</li>
+ <li>identify known implementation.</li>
</ul>
<p>If there was any <a href="#def-Dissent" rel="glossary"><span class="dfn-instance">dissent</span></a>
@@ -2404,15 +2417,15 @@
<p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an
<a href="#ACAppeal">Advisory Committee Appeal</a> of the Director's decision.</p>
- <p>An Obsolete or Rescinded Recommendation <em class="rfc2119">must</em> be published with up to date status.
+ <p>W3C <em class="rfc2119">must</em> publish an Obsolete or Rescinded Recommendation with up to date status.
The updated version <em class="rfc2119">may</em> remove the main body of the document. The Status of this Document section
<em class="rfc2119">should</em> link to an explanation of the Obsolete or Rescinded status as appropriate.</p>
<p>Once W3C has published a Rescinded Recommendation, future W3C technical reports
<em class="rfc2119">must not</em> include normative references to that technical report.</p>
- <p><span style="font-weight: bold;">Note:</span> the original Recommendation document will continue to be available at its
- version-specific URL.</p>
+ <p><span style="font-weight: bold;">Note:</span> W3C strives to ensure that all Technical Reports will continue to be
+ available at their version-specific URL.</p>
<h3 id="further-reading">Further reading</h3>
@@ -2443,7 +2456,7 @@
<h4 id="ACReviewStart">7.1.1 Start of a Review Period</h4>
<p>Each Advisory Committee review period begins with a Call for Review from the Team to the Advisory Committee. The
- <dfn id="reviewform">review form</dfn> describes the proposal, raises attention to deadlines, estimates when the decision
+ <dfn id="reviewform">Call for Review</dfn> describes the proposal, raises attention to deadlines, estimates when the decision
will be available, and includes other practical information. Each Member organization <em class="rfc2119">may</em> send one
review, which <em class="rfc2119">must</em> be returned by its Advisory Committee representative.</p>
@@ -2827,7 +2840,7 @@
<dt id="ref-coi">[PUB23]</dt>
<dd><cite><a href="https://www.w3.org/2000/09/06-conflictpolicy">Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities</a></cite></dd>
<dt id="ref-tag-charter">[PUB25]</dt>
- <dd><cite><a href="https://www.w3.org/2004/10/27-tag">Technical Architecture Group (TAG) Charter</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2004/10/27-tag-charter">Technical Architecture Group (TAG) Charter</a></cite></dd>
<dt id="ref-tag-home">[PUB26]</dt>
<dd><cite><a href="https://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
<dt id="ref-rec-tips">[PUB27]</dt>
@@ -2846,6 +2859,12 @@
https://www.w3.org/Consortium/Patent-Policy/.</dd>
<dt id="in-place-tr-mod">[PUB35]</dt>
<dd><cite><a href="https://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
+ <dt id="ref-calendar">[PUB36]</dt>
+ <dd>The <cite><a href="https://www.w3.org/participate/eventscal">calendar of all scheduled official W3C events</a></cite> replaced the <a href="https://www.w3.org/Member/Eventscal">former member-confidential version</a> [<a href="#oldref-mem-calendar">MEM3</a>].</dd>
+ <dt id="ref-guide">[PUB37]</dt>
+ <dd><cite><a href="https://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other collaborators</dd>
+ <dt id="ref-cepc">[PUB38]</dt>
+ <dd><cite><a href="https://www.w3.org/Consortium/cepc/">W3C Code of Ethics and Professional Conduct</a></cite></dd>
</dl>
<h3>12.2 <a id="member-refs">Member-only Resources</a></h3>
@@ -2858,18 +2877,18 @@
<dd><cite><a href="https://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
<dt id="ref-mailing-lists">[MEM2]</dt>
<dd><cite><a href="https://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
- <dt id="ref-calendar">[MEM3]</dt>
- <dd>The <cite><a href="https://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
+ <dt id="oldref-mem-calendar">[MEM3]</dt>
+ <dd>The Member-only <cite><a href="https://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite> is no longer maintained. The information is now maintained in the public calendar [<a href="#ref-calendar">PUB36</a>]</dd>
<dt id="ref-new-member">[MEM4]</dt>
- <dd>The <cite><a href="https://www.w3.org/Member/Intro">New Member Orientation</a></cite>, which includes an introduction to W3C processes from a practical standpoint, including relevant email addresses.</dd>
+ <dd>There is a <cite><a href="https://www.w3.org/Member/faq.html">Member intro and FAQ</a></cite> as well as the <cite><a href="https://www.w3.org/Member/Intro">Process, Patent Policy, Finances Guide</a></cite> previously known as the "New Member Orientation", which includes an introduction to W3C processes from a practical standpoint, including relevant email addresses.</dd>
<dt id="ref-ac-meetings">[MEM5]</dt>
<dd><cite><a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
<dt id="ref-member-web">[MEM6]</dt>
<dd><cite><a href="https://www.w3.org/Member/">Member Web site</a></cite></dd>
<dt id="ref-member-sub">[MEM8]</dt>
<dd><cite><a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
- <dt id="ref-guide">[MEM9]</dt>
- <dd><cite><a href="https://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other collaborators</dd>
+ <dt>[MEM9]</dt>
+ <dd><cite><a href="https://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other collaborators, is now a Public resource [<a href="ref-guide">PUB37</a>]</dd>
<dt id="ref-discipline-gl">[MEM14]</dt>
<dd><cite><a href="https://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
<dt id="ref-election-howto">[MEM15]</dt>
@@ -2887,11 +2906,13 @@
<h2 id="acks">13 Acknowledgments</h2>
- <p>The following individuals have contributed to this proposal for a revised Process: Daniel Appelquist,
+ <p>The following individuals (some as individuals, others with the affiliation listed) have contributed to this
+ proposal for a revised Process: Daniel Appelquist,
David Baron (Mozilla), J Alan Bird (W3C), Carine Bournez (W3C), Wayne Carr (Intel),
Tantek Çelik (Mozilla), Michael Champion (W3C), Maria Courtemanche (IBM), Donald Deutsch (Oracle),
Geoffrey Creighton (Microsoft), Kevin Fleming (Bloomberg), Virginia Fournier (Apple), Virginie Galindo (Gemalto),
- Daniel Glazman (Disruptive Innovations), Michael Geldblum (Oracle), Jeff Jaffe (W3C), Jay Junichi Kishigami (NTT),
+ Daniel Glazman (Disruptive Innovations), Michael Geldblum (Oracle), Ian Jacobs (W3C), Jeff Jaffe (W3C),
+ Jay Junichi Kishigami (NTT),
Mark Nottingham, Peter Patel-Schneider, Scott Peterson (Google), Delfí Ramírez, Florian Rivoal, Wendy Seltzer (W3C),
David Singer (Apple), Geoffrey Snedden, Josh Soref, Ralph Swick (W3C),
Léonie Watson (The Paciello Group), Ben Wilson, Chris Wilson (Google), Rigo Wenning (W3C), Helene Workman (Apple),