--- a/cover.html Wed Jul 29 10:06:49 2015 -0400
+++ b/cover.html Wed Jul 29 10:35:44 2015 -0400
@@ -319,7 +319,7 @@
likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to discuss topics that interest the W3C community.</li>
<li>When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an <a href="#ACCommunication">Advisory
Committee mailing list</a>), the Director announces the development of a proposal for one or more new <a href="#WGCharterDevelopment">Interest
- Group or Working Group charters</a>, depending on the breadth of the topic of interest. W3C Members <a href="#ActivityCreation">review</a>
+ Group or Working Group charters</a>, depending on the breadth of the topic of interest. W3C Members <a href="#CharterReview">review</a>
the proposed charters. When there is support within W3C for investing resources in the topic of interest, the Director approves
the group(s) and they begin their work.</li>
<li>There are three types of Working Group participants: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited
@@ -438,7 +438,7 @@
additional email addresses, at the discretion of the Team.</p>
<h5 id="ACMeetings">2.1.3.2 Advisory Committee Meetings</h5>
<p>The Team organizes a <a href="#ftf-meeting">face-to-face meeting</a> for the Advisory Committee <span class="time-interval">twice
- a year</span>. The Team appoints the Chair of these meetings (generally the <a href="#def-W3CChair">CEO</a>). At each Advisory
+ a year</span>. The Team appoints the Chair of these meetings (generally the CEO). At each Advisory
Committee meeting, the Team <em class="rfc2119">should</em> provide an update to the Advisory Committee about:</p>
<dl>
<dt><em>Resources</em></dt>
@@ -510,7 +510,7 @@
Advisory Board meetings) are available at the <a href="http://www.w3.org/2002/ab/">Advisory Board home page</a> [<a href="#ref-ab-home">PUB30</a>].</p>
<h4 id="ABParticipation">2.3.1 Advisory Board Participation</h4>
<p>The Advisory Board consists of nine elected participants and a Chair. The Team appoints the Chair of the <a href="#AB">Advisory
- Board</a>, who is generally the <a href="#def-W3CChair">CEO</a>.</p>
+ Board</a>, who is generally the CEO.</p>
<p>The remaining nine Advisory Board participants are elected by the W3C Advisory Committee following the <a href="#AB-TAG-elections">AB/TAG
nomination and election process</a>.</p>
<p>With the exception of the Chair, the terms of all Advisory Board participants are for <span class="time-interval">two years</span>.
@@ -529,7 +529,7 @@
architecture; see also the <a href="#AB">Advisory Board</a>.</p>
<p>The TAG's scope is limited to technical issues about Web architecture. The TAG <em class="rfc2119">should not</em> consider
administrative, process, or organizational policy issues of W3C, which are generally addressed by the W3C Advisory Committee,
- Advisory Board, and Team. Please refer to the <a href="http://www.w3.org/2001/07/19-tag">TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
+ Advisory Board, and Team. Please refer to the <a href="http://www.w3.org/2004/10/27-tag-charter">TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
for more information about the background and scope of the TAG, and the expected qualifications of TAG participants.</p>
<p>The Team <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
<ul>
@@ -544,7 +544,7 @@
Committee and other group Chairs. The TAG <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory
Committee meeting</a>.</p>
<p>When the TAG votes to resolve an issue, each TAG participant (whether appointed, elected, or the Chair) has one vote; see also the
- section on <a href="http://www.w3.org/2001/07/19-tag#Voting">voting in the TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
+ section on <a href="http://www.w3.org/2004/10/27-tag-charter#Voting">voting in the TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
and the general section on <a href="#Votes">votes</a> in this Process Document.</p>
<p>Details about the TAG (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings) are available
at the <a href="http://www.w3.org/2001/tag/">TAG home page</a> [<a href="#ref-tag-home">PUB26</a>].</p>
@@ -1104,7 +1104,7 @@
href="#ACCommunication">Advisory Committee discussion list</a>.</p>
<p>W3C <em class="rfc2119">may</em> begin work on a Working Group or Interest Group charter at any time.</p>
<h4>5.2.3 <dfn id="CharterReview">Advisory Committee Review of a Working Group or Interest Group Charter</dfn></h4>
- <p>The Director <em class="rfc2119">must</em> solicit <a href="#ReviewAppeal">Advisory Committee review</a> of every new or
+ <p>The Director <em class="rfc2119">must</em> solicit <a href="#ACReview">Advisory Committee review</a> of every new or
substantively modified Working Group or Interest Group charter. The Director is <em class="rfc2119">not required</em> to solicit
Advisory Committee review prior to a charter extension or for minor changes. The review period <em class="rfc2119">must</em> be
at least four weeks.</p>
@@ -1318,7 +1318,7 @@
any way by W3C.</p>
<h3 id="requirements-and-definitions">6.2 General requirements and definitions</h3>
<p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a W3C Technical
- Report on its <a href="http://www.w3.org/TR/">Technical Reports page http://www.w3.org/TR</a> [<a href="#rdf-doc-list">PUB11</a>].</p>
+ Report on its <a href="http://www.w3.org/TR/">Technical Reports page http://www.w3.org/TR</a> [<a href="#ref-doc-list">PUB11</a>].</p>
<h4 id="general-requirements">6.2.1 General requirements for Technical Reports</h4>
<p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public
document. The <a href="http://www.w3.org/TR/">index of W3C technical reports</a> [<a href="#ref-doc-list">PUB11</a>] is available
@@ -1340,7 +1340,7 @@
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 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="http://www.w3.org/Guide/pubrules">Publication
- Rules</a> [<a href="#rdf-pubrules">PUB31</a>](e.g., for <span id="DocumentName">naming</span>, status information, style, and <span
+ Rules</a> [<a href="#ref-pubrules">PUB31</a>](e.g., for <span id="DocumentName">naming</span>, status information, style, and <span
id="document-copyright">copyright requirements</span>). These rules are subject to change by the Team from time to time. The Team
<em class="rfc2119">must</em> inform group Chairs and the Advisory Committee of any changes to these rules.</p>
<p>The primary language for W3C Technical Reports is English. W3C encourages the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
@@ -1380,7 +1380,7 @@
approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document,
who has provided comments, the record of requests to and responses from reviewers, especially <a href="http://www.w3.org/Guide/Charter.html#horizontal-review">W3C
Horizontal Groups</a> and groups identified as dependencies in the charter or identified as <a href="http://www.w3.org/2001/11/StdLiaison.html">liaisons</a>
- [<a href="#rdf-liaison-list">PUB29</a>], and seek evidence of clear communication to the general public about appropriate times and
+ [<a href="#ref-liaison-list">PUB29</a>], and seek evidence of clear communication to the general public about appropriate times and
which content to review and whether such reviews actually occurred. </p>
<p>For example, inviting review of new or significantly revised sections published in Working Drafts, and tracking those comments and
the Working Group's responses, is generally a good practice which would often be considered positive evidence of wide review.
@@ -1435,7 +1435,7 @@
<dd>Changes that add a new functionality, element, etc.</dd>
</dl>
<h3 id="working-draft">6.3 Working Draft</h3>
- <p>A Public Working Draft is published on the <a href="http://www.w3.org/TR/">W3C's Technical Reports page</a> [<a href="#rdf-doc-list">PUB11</a>]
+ <p>A Public Working Draft is published on the <a href="http://www.w3.org/TR/">W3C's Technical Reports page</a> [<a href="#ref-doc-list">PUB11</a>]
for review, and for simple historical reference. For all Public Working Drafts a Working Group</p>
<ul>
<li> <em class="rfc2119">should</em> document outstanding issues, and parts of the document on which the Working Group does not
@@ -2035,46 +2035,46 @@
<dd><cite><a href="http://www.w3.org/Consortium/Member/List">The list of current W3C Members</a></cite></dd>
<dt id="ref-activity-list">[PUB9]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/activities">The list of W3C Activities</a></cite></dd>
- <dt id="rdf-submission-list">[PUB10]</dt>
+ <dt id="ref-submission-list">[PUB10]</dt>
<dd><cite><a href="http://www.w3.org/Submission/">The list of acknowledged Member Submissions</a></cite></dd>
- <dt id="rdf-doc-list">[PUB11]</dt>
+ <dt id="ref-doc-list">[PUB11]</dt>
<dd><cite><a href="http://www.w3.org/TR/">The W3C technical reports index</a></cite></dd>
- <dt id="rdf-submission-overview">[PUB13]</dt>
+ <dt id="ref-submission-overview">[PUB13]</dt>
<dd><cite><a href="http://www.w3.org/Submission/1996/Template/">Submission request overview</a></cite></dd>
- <dt id="rdf-people">[PUB14]</dt>
+ <dt id="ref-people">[PUB14]</dt>
<dd><cite><a href="http://www.w3.org/People/">The W3C Team</a></cite></dd>
- <dt id="rdf-mission">[PUB15]</dt>
+ <dt id="ref-mission">[PUB15]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/">About the World Wide Web Consortium</a></cite></dd>
- <dt id="rdf-team-submission-list">[PUB16]</dt>
+ <dt id="ref-team-submission-list">[PUB16]</dt>
<dd><cite><a href="http://www.w3.org/TeamSubmission/">The list of published Team Submissions</a></cite></dd>
- <dt id="rdf-invited-expert">[PUB17]</dt>
+ <dt id="ref-invited-expert">[PUB17]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and collaborators agreement</a></cite></dd>
- <dt id="rdf-doc-license">[PUB18]</dt>
+ <dt id="ref-doc-license">[PUB18]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a></cite></dd>
- <dt id="rdf-software-license">[PUB19]</dt>
+ <dt id="ref-software-license">[PUB19]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-software">W3C Software Notice and License</a></cite></dd>
- <dt id="rdf-translations">[PUB20]</dt>
+ <dt id="ref-translations">[PUB20]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/Translation/">Translations of W3C technical reports</a></cite></dd>
- <dt id="rdf-pub-mailing-lists">[PUB21]</dt>
+ <dt id="ref-pub-mailing-lists">[PUB21]</dt>
<dd><cite><a href="http://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
- <dt id="rdf-coi">[PUB23]</dt>
+ <dt id="ref-coi">[PUB23]</dt>
<dd><cite><a href="http://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="rdf-tag-charter">[PUB25]</dt>
- <dd><cite><a href="http://www.w3.org/2001/07/19-tag">Technical Architecture Group (TAG) Charter</a></cite></dd>
- <dt id="rdf-tag-home">[PUB26]</dt>
+ <dt id="ref-tag-charter">[PUB25]</dt>
+ <dd><cite><a href="http://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="http://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
- <dt id="rdf-rec-tips">[PUB27]</dt>
+ <dt id="ref-rec-tips">[PUB27]</dt>
<dd><cite><a href="http://www.w3.org/2002/05/rec-tips">Tips for Getting to Recommendation Faster</a></cite></dd>
- <dt id="rdf-liaison-list">[PUB28]</dt>
+ <dt id="ref-liaison-list">[PUB28]</dt>
<dd><cite><a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a></cite></dd>
- <dt id="rdf-ab-home">[PUB30]</dt>
+ <dt id="ref-ab-home">[PUB30]</dt>
<dd><cite><a href="http://www.w3.org/2002/ab/">The Advisory Board home page</a></cite></dd>
- <dt id="rdf-pubrules">[PUB31]</dt>
+ <dt id="ref-pubrules">[PUB31]</dt>
<dd><cite><a href="http://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
- <dt id="rdf-fellows">[PUB32]</dt>
+ <dt id="ref-fellows">[PUB32]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a></cite></dd>
- <dt id="rdf-patentpolicy">[PUB33]</dt>
+ <dt id="ref-patentpolicy">[PUB33]</dt>
<dd><cite><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
<a href="http://www.w3.org/Consortium/Patent-Policy/">latest version of the W3C Patent Policy</a> is available at
http://www.w3.org/Consortium/Patent-Policy/.</dd>
@@ -2084,32 +2084,32 @@
<h3>12.2 <a id="member-refs">Member-only Resources</a></h3>
<p>The following <a href="#Member-only">Member-only</a> information is available at the <a href="http://www.w3.org/">W3C Web site</a>.</p>
<dl>
- <dt id="rdf-current-ac">[MEM1]</dt>
+ <dt id="ref-current-ac">[MEM1]</dt>
<dd><cite><a href="http://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
- <dt id="rdf-mailing-lists">[MEM2]</dt>
+ <dt id="ref-mailing-lists">[MEM2]</dt>
<dd><cite><a href="http://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
- <dt id="rdf-calendar">[MEM3]</dt>
+ <dt id="ref-calendar">[MEM3]</dt>
<dd>The <cite><a href="http://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
- <dt id="rdf-new-member">[MEM4]</dt>
+ <dt id="ref-new-member">[MEM4]</dt>
<dd>The <cite><a href="http://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>
- <dt id="rdf-ac-meetings">[MEM5]</dt>
+ <dt id="ref-ac-meetings">[MEM5]</dt>
<dd><cite><a href="http://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
- <dt id="rdf-member-web">[MEM6]</dt>
+ <dt id="ref-member-web">[MEM6]</dt>
<dd><cite><a href="http://www.w3.org/Member/">Member Web site</a></cite></dd>
- <dt id="rdf-member-sub">[MEM8]</dt>
+ <dt id="ref-member-sub">[MEM8]</dt>
<dd><cite><a href="http://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
- <dt id="rdf-guide">[MEM9]</dt>
+ <dt id="ref-guide">[MEM9]</dt>
<dd><cite><a href="http://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other
collaborators</dd>
- <dt id="rdf-discipline-gl">[MEM14]</dt>
+ <dt id="ref-discipline-gl">[MEM14]</dt>
<dd><cite><a href="http://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
- <dt id="rdf-election-howto">[MEM15]</dt>
+ <dt id="ref-election-howto">[MEM15]</dt>
<dd><cite><a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
</dl>
<h3 id="other-refs">12.3 Other References</h3>
<dl>
- <dt id="rdf-RFC2119">[RFC2119]</dt>
+ <dt id="ref-RFC2119">[RFC2119]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">"Key words for use in RFCs to Indicate Requirement Levels"</a></cite>, S.
Bradner, March 1997.</dd>
<dt id="ref-RFC2777">[RFC2777]</dt>