cover.html
branchPP-20150428
changeset 163 8afe5da258a5
parent 161 a349a1fad124
child 165 ac35a25720eb
equal deleted inserted replaced
162:de3056dbd9de 163:8afe5da258a5
   317         <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
   317         <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
   318             Submissions</a>, and the <a href="#Team">Team</a> monitors work inside and outside of W3C for signs of interest. Also, W3C is
   318             Submissions</a>, and the <a href="#Team">Team</a> monitors work inside and outside of W3C for signs of interest. Also, W3C is
   319           likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to discuss topics that interest the W3C community.</li>
   319           likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to discuss topics that interest the W3C community.</li>
   320         <li>When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an <a href="#ACCommunication">Advisory
   320         <li>When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an <a href="#ACCommunication">Advisory
   321             Committee mailing list</a>), the Director announces the development of a proposal for one or more new <a href="#WGCharterDevelopment">Interest
   321             Committee mailing list</a>), the Director announces the development of a proposal for one or more new <a href="#WGCharterDevelopment">Interest
   322             Group or Working Group charters</a>, depending on the breadth of the topic of interest. W3C Members <a href="#ActivityCreation">review</a>
   322             Group or Working Group charters</a>, depending on the breadth of the topic of interest. W3C Members <a href="#CharterReview">review</a>
   323           the proposed charters. When there is support within W3C for investing resources in the topic of interest, the Director approves
   323           the proposed charters. When there is support within W3C for investing resources in the topic of interest, the Director approves
   324           the group(s) and they begin their work.</li>
   324           the group(s) and they begin their work.</li>
   325         <li>There are three types of Working Group participants: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited
   325         <li>There are three types of Working Group participants: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited
   326             Experts</a>, and <a href="#Team">Team representatives</a>. Team representatives both contribute to the technical work and help
   326             Experts</a>, and <a href="#Team">Team representatives</a>. Team representatives both contribute to the technical work and help
   327           ensure the group's proper integration with the rest of W3C. The <a href="#WGCharter">Working Group charter</a> sets expectations
   327           ensure the group's proper integration with the rest of W3C. The <a href="#WGCharter">Working Group charter</a> sets expectations
   436       <p>An Advisory Committee representative <em class="rfc2119">may</em> request that additional individuals from their organization be
   436       <p>An Advisory Committee representative <em class="rfc2119">may</em> request that additional individuals from their organization be
   437         subscribed to these lists. Failure to contain distribution internally <em class="rfc2119">may</em> result in suspension of
   437         subscribed to these lists. Failure to contain distribution internally <em class="rfc2119">may</em> result in suspension of
   438         additional email addresses, at the discretion of the Team.</p>
   438         additional email addresses, at the discretion of the Team.</p>
   439       <h5 id="ACMeetings">2.1.3.2 Advisory Committee Meetings</h5>
   439       <h5 id="ACMeetings">2.1.3.2 Advisory Committee Meetings</h5>
   440       <p>The Team organizes a <a href="#ftf-meeting">face-to-face meeting</a> for the Advisory Committee <span class="time-interval">twice
   440       <p>The Team organizes a <a href="#ftf-meeting">face-to-face meeting</a> for the Advisory Committee <span class="time-interval">twice
   441           a year</span>. The Team appoints the Chair of these meetings (generally the <a href="#def-W3CChair">CEO</a>). At each Advisory
   441           a year</span>. The Team appoints the Chair of these meetings (generally the CEO). At each Advisory
   442         Committee meeting, the Team <em class="rfc2119">should</em> provide an update to the Advisory Committee about:</p>
   442         Committee meeting, the Team <em class="rfc2119">should</em> provide an update to the Advisory Committee about:</p>
   443       <dl>
   443       <dl>
   444         <dt><em>Resources</em></dt>
   444         <dt><em>Resources</em></dt>
   445         <dd>
   445         <dd>
   446           <ul>
   446           <ul>
   508           Committee meeting</a>.</p>
   508           Committee meeting</a>.</p>
   509       <p>Details about the Advisory Board (e.g., the list of Advisory Board participants, mailing list information, and summaries of
   509       <p>Details about the Advisory Board (e.g., the list of Advisory Board participants, mailing list information, and summaries of
   510         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>
   510         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>
   511       <h4 id="ABParticipation">2.3.1 Advisory Board Participation</h4>
   511       <h4 id="ABParticipation">2.3.1 Advisory Board Participation</h4>
   512       <p>The Advisory Board consists of nine elected participants and a Chair. The Team appoints the Chair of the <a href="#AB">Advisory
   512       <p>The Advisory Board consists of nine elected participants and a Chair. The Team appoints the Chair of the <a href="#AB">Advisory
   513           Board</a>, who is generally the <a href="#def-W3CChair">CEO</a>.</p>
   513           Board</a>, who is generally the CEO.</p>
   514       <p>The remaining nine Advisory Board participants are elected by the W3C Advisory Committee following the <a href="#AB-TAG-elections">AB/TAG
   514       <p>The remaining nine Advisory Board participants are elected by the W3C Advisory Committee following the <a href="#AB-TAG-elections">AB/TAG
   515           nomination and election process</a>.</p>
   515           nomination and election process</a>.</p>
   516       <p>With the exception of the Chair, the terms of all Advisory Board participants are for <span class="time-interval">two years</span>.
   516       <p>With the exception of the Chair, the terms of all Advisory Board participants are for <span class="time-interval">two years</span>.
   517         Terms are staggered so that each year, either four or five terms expire. If an individual is elected to fill an incomplete term,
   517         Terms are staggered so that each year, either four or five terms expire. If an individual is elected to fill an incomplete term,
   518         that individual's term ends at the normal expiration date of that term. Regular Advisory Board terms begin on 1 July and end on 30
   518         that individual's term ends at the normal expiration date of that term. Regular Advisory Board terms begin on 1 July and end on 30
   527       </ol>
   527       </ol>
   528       <p>The TAG hears appeals of <a href="#SubmissionNo">Member Submission requests</a> that are rejected for reasons related to Web
   528       <p>The TAG hears appeals of <a href="#SubmissionNo">Member Submission requests</a> that are rejected for reasons related to Web
   529         architecture; see also the <a href="#AB">Advisory Board</a>.</p>
   529         architecture; see also the <a href="#AB">Advisory Board</a>.</p>
   530       <p>The TAG's scope is limited to technical issues about Web architecture. The TAG <em class="rfc2119">should not</em> consider
   530       <p>The TAG's scope is limited to technical issues about Web architecture. The TAG <em class="rfc2119">should not</em> consider
   531         administrative, process, or organizational policy issues of W3C, which are generally addressed by the W3C Advisory Committee,
   531         administrative, process, or organizational policy issues of W3C, which are generally addressed by the W3C Advisory Committee,
   532         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>]
   532         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>]
   533         for more information about the background and scope of the TAG, and the expected qualifications of TAG participants.</p>
   533         for more information about the background and scope of the TAG, and the expected qualifications of TAG participants.</p>
   534       <p>The Team <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
   534       <p>The Team <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
   535       <ul>
   535       <ul>
   536         <li>a public discussion (not just input) list for issues of Web architecture. The TAG will conduct its public business on this list.</li>
   536         <li>a public discussion (not just input) list for issues of Web architecture. The TAG will conduct its public business on this list.</li>
   537         <li>a <a href="#Member-only">Member-only</a> list for discussions within the TAG and for requests to the TAG that, for whatever
   537         <li>a <a href="#Member-only">Member-only</a> list for discussions within the TAG and for requests to the TAG that, for whatever
   542         use a list that will be <a href="#Member-only">Member-only</a>.</p>
   542         use a list that will be <a href="#Member-only">Member-only</a>.</p>
   543       <p>The TAG <em class="rfc2119">should</em> send a summary of each of its <a href="#GeneralMeetings">meetings</a> to the Advisory
   543       <p>The TAG <em class="rfc2119">should</em> send a summary of each of its <a href="#GeneralMeetings">meetings</a> to the Advisory
   544         Committee and other group Chairs. The TAG <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory
   544         Committee and other group Chairs. The TAG <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory
   545           Committee meeting</a>.</p>
   545           Committee meeting</a>.</p>
   546       <p>When the TAG votes to resolve an issue, each TAG participant (whether appointed, elected, or the Chair) has one vote; see also the
   546       <p>When the TAG votes to resolve an issue, each TAG participant (whether appointed, elected, or the Chair) has one vote; see also the
   547         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>]
   547         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>]
   548         and the general section on <a href="#Votes">votes</a> in this Process Document.</p>
   548         and the general section on <a href="#Votes">votes</a> in this Process Document.</p>
   549       <p>Details about the TAG (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings) are available
   549       <p>Details about the TAG (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings) are available
   550         at the <a href="http://www.w3.org/2001/tag/">TAG home page</a> [<a href="#ref-tag-home">PUB26</a>].</p>
   550         at the <a href="http://www.w3.org/2001/tag/">TAG home page</a> [<a href="#ref-tag-home">PUB26</a>].</p>
   551       <h4 id="tag-participation">2.4.1 Technical Architecture Group Participation</h4>
   551       <h4 id="tag-participation">2.4.1 Technical Architecture Group Participation</h4>
   552       <p>The TAG consists of eight elected or appointed participants and a Chair. The Team appoints the Chair of the TAG, who is generally
   552       <p>The TAG consists of eight elected or appointed participants and a Chair. The Team appoints the Chair of the TAG, who is generally
  1102           Committee when a charter for a new Working Group or Interest Group is in development. This is intended to raise awareness, even if
  1102           Committee when a charter for a new Working Group or Interest Group is in development. This is intended to raise awareness, even if
  1103           no formal proposal is yet available. Advisory Committee representatives <em class="rfc2119">may</em> provide feedback on the <a
  1103           no formal proposal is yet available. Advisory Committee representatives <em class="rfc2119">may</em> provide feedback on the <a
  1104             href="#ACCommunication">Advisory Committee discussion list</a>.</p>
  1104             href="#ACCommunication">Advisory Committee discussion list</a>.</p>
  1105         <p>W3C <em class="rfc2119">may</em> begin work on a Working Group or Interest Group charter at any time.</p>
  1105         <p>W3C <em class="rfc2119">may</em> begin work on a Working Group or Interest Group charter at any time.</p>
  1106         <h4>5.2.3 <dfn id="CharterReview">Advisory Committee Review of a Working Group or Interest Group Charter</dfn></h4>
  1106         <h4>5.2.3 <dfn id="CharterReview">Advisory Committee Review of a Working Group or Interest Group Charter</dfn></h4>
  1107         <p>The Director <em class="rfc2119">must</em> solicit <a href="#ReviewAppeal">Advisory Committee review</a> of every new or
  1107         <p>The Director <em class="rfc2119">must</em> solicit <a href="#ACReview">Advisory Committee review</a> of every new or
  1108           substantively modified Working Group or Interest Group charter. The Director is <em class="rfc2119">not required</em> to solicit
  1108           substantively modified Working Group or Interest Group charter. The Director is <em class="rfc2119">not required</em> to solicit
  1109           Advisory Committee review prior to a charter extension or for minor changes. The review period <em class="rfc2119">must</em> be
  1109           Advisory Committee review prior to a charter extension or for minor changes. The review period <em class="rfc2119">must</em> be
  1110           at least four weeks.</p>
  1110           at least four weeks.</p>
  1111         <p>The Director's Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight important changes
  1111         <p>The Director's Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight important changes
  1112           (e.g., regarding deliverables or resource allocation) and include rationale for the changes.</p>
  1112           (e.g., regarding deliverables or resource allocation) and include rationale for the changes.</p>
  1316       <p>Working Groups and Interest Groups <em class="rfc2119">may</em> make available "Editor's drafts". Editor's drafts have no official
  1316       <p>Working Groups and Interest Groups <em class="rfc2119">may</em> make available "Editor's drafts". Editor's drafts have no official
  1317         standing whatsoever, and do not necessarily imply consensus of a Working Group or Interest Group, nor are their contents endorsed in
  1317         standing whatsoever, and do not necessarily imply consensus of a Working Group or Interest Group, nor are their contents endorsed in
  1318         any way by W3C.</p>
  1318         any way by W3C.</p>
  1319       <h3 id="requirements-and-definitions">6.2 General requirements and definitions</h3>
  1319       <h3 id="requirements-and-definitions">6.2 General requirements and definitions</h3>
  1320       <p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a W3C Technical
  1320       <p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a W3C Technical
  1321         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>
  1321         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>
  1322       <h4 id="general-requirements">6.2.1 General requirements for Technical Reports</h4>
  1322       <h4 id="general-requirements">6.2.1 General requirements for Technical Reports</h4>
  1323       <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public
  1323       <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public
  1324         document. The <a href="http://www.w3.org/TR/">index of W3C technical reports</a> [<a href="#ref-doc-list">PUB11</a>] is available
  1324         document. The <a href="http://www.w3.org/TR/">index of W3C technical reports</a> [<a href="#ref-doc-list">PUB11</a>] is available
  1325         at the W3C Web site. W3C strives to make archival documents indefinitely available at their original address in their original form.</p>
  1325         at the W3C Web site. W3C strives to make archival documents indefinitely available at their original address in their original form.</p>
  1326       <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate
  1326       <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate
  1338       <p>Every Technical Report published as part of the Technical Report development process is edited by one or more editors appointed by
  1338       <p>Every Technical Report published as part of the Technical Report development process is edited by one or more editors appointed by
  1339         a Group Chair. It is the responsibility of these editors to ensure that the decisions of the Group are correctly reflected in
  1339         a Group Chair. It is the responsibility of these editors to ensure that the decisions of the Group are correctly reflected in
  1340         subsequent drafts of the technical report. An editor <em class="rfc2119">must</em> be a participant, as a Member representative,
  1340         subsequent drafts of the technical report. An editor <em class="rfc2119">must</em> be a participant, as a Member representative,
  1341         Team representative, or Invited Expert in the Group responsible for the document(s) they are editing. </p>
  1341         Team representative, or Invited Expert in the Group responsible for the document(s) they are editing. </p>
  1342       <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
  1342       <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
  1343           Rules</a> [<a href="#rdf-pubrules">PUB31</a>](e.g., for <span id="DocumentName">naming</span>, status information, style, and <span
  1343           Rules</a> [<a href="#ref-pubrules">PUB31</a>](e.g., for <span id="DocumentName">naming</span>, status information, style, and <span
  1344           id="document-copyright">copyright requirements</span>). These rules are subject to change by the Team from time to time. The Team
  1344           id="document-copyright">copyright requirements</span>). These rules are subject to change by the Team from time to time. The Team
  1345         <em class="rfc2119">must</em> inform group Chairs and the Advisory Committee of any changes to these rules.</p>
  1345         <em class="rfc2119">must</em> inform group Chairs and the Advisory Committee of any changes to these rules.</p>
  1346       <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
  1346       <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
  1347           about translations of W3C technical reports</a> [<a href="#ref-translations">PUB18</a>] is available at the W3C Web site.</p>
  1347           about translations of W3C technical reports</a> [<a href="#ref-translations">PUB18</a>] is available at the W3C Web site.</p>
  1348       <h4 id="transition-reqs">6.2.2 Advancement on the Recommendation Track</h4>
  1348       <h4 id="transition-reqs">6.2.2 Advancement on the Recommendation Track</h4>
  1378         to actually perform reviews of and provide comments on the specification. A second objective is to encourage groups to request
  1378         to actually perform reviews of and provide comments on the specification. A second objective is to encourage groups to request
  1379         reviews early enough that comments and suggested changes may still be reasonably incorporated in response to the review. Before
  1379         reviews early enough that comments and suggested changes may still be reasonably incorporated in response to the review. Before
  1380         approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document,
  1380         approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document,
  1381         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
  1381         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
  1382           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>
  1382           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>
  1383         [<a href="#rdf-liaison-list">PUB29</a>], and seek evidence of clear communication to the general public about appropriate times and
  1383         [<a href="#ref-liaison-list">PUB29</a>], and seek evidence of clear communication to the general public about appropriate times and
  1384         which content to review and whether such reviews actually occurred. </p>
  1384         which content to review and whether such reviews actually occurred. </p>
  1385       <p>For example, inviting review of new or significantly revised sections published in Working Drafts, and tracking those comments and
  1385       <p>For example, inviting review of new or significantly revised sections published in Working Drafts, and tracking those comments and
  1386         the Working Group's responses, is generally a good practice which would often be considered positive evidence of wide review.
  1386         the Working Group's responses, is generally a good practice which would often be considered positive evidence of wide review.
  1387         Working Groups <em class="rfc2119">should</em> announce to other W3C Working Groups as well as the general public, especially those
  1387         Working Groups <em class="rfc2119">should</em> announce to other W3C Working Groups as well as the general public, especially those
  1388         affected by this specification, a proposal to enter Candidate Recommendation (for example in approximately four weeks). By contrast
  1388         affected by this specification, a proposal to enter Candidate Recommendation (for example in approximately four weeks). By contrast
  1433         </dd>
  1433         </dd>
  1434         <dt>4. New features</dt>
  1434         <dt>4. New features</dt>
  1435         <dd>Changes that add a new functionality, element, etc.</dd>
  1435         <dd>Changes that add a new functionality, element, etc.</dd>
  1436       </dl>
  1436       </dl>
  1437       <h3 id="working-draft">6.3 Working Draft</h3>
  1437       <h3 id="working-draft">6.3 Working Draft</h3>
  1438       <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>]
  1438       <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>]
  1439         for review, and for simple historical reference. For all Public Working Drafts a Working Group</p>
  1439         for review, and for simple historical reference. For all Public Working Drafts a Working Group</p>
  1440       <ul>
  1440       <ul>
  1441         <li> <em class="rfc2119">should</em> document outstanding issues, and parts of the document on which the Working Group does not
  1441         <li> <em class="rfc2119">should</em> document outstanding issues, and parts of the document on which the Working Group does not
  1442           have consensus, and</li>
  1442           have consensus, and</li>
  1443         <li> <em class="rfc2119">may</em> request publication of a Working Draft even if its content is considered unstable and does not
  1443         <li> <em class="rfc2119">may</em> request publication of a Working Draft even if its content is considered unstable and does not
  2033         <dd><cite><a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a></cite></dd>
  2033         <dd><cite><a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a></cite></dd>
  2034         <dt id="ref-current-mem">[PUB8]</dt>
  2034         <dt id="ref-current-mem">[PUB8]</dt>
  2035         <dd><cite><a href="http://www.w3.org/Consortium/Member/List">The list of current W3C Members</a></cite></dd>
  2035         <dd><cite><a href="http://www.w3.org/Consortium/Member/List">The list of current W3C Members</a></cite></dd>
  2036         <dt id="ref-activity-list">[PUB9]</dt>
  2036         <dt id="ref-activity-list">[PUB9]</dt>
  2037         <dd><cite><a href="http://www.w3.org/Consortium/activities">The list of W3C Activities</a></cite></dd>
  2037         <dd><cite><a href="http://www.w3.org/Consortium/activities">The list of W3C Activities</a></cite></dd>
  2038         <dt id="rdf-submission-list">[PUB10]</dt>
  2038         <dt id="ref-submission-list">[PUB10]</dt>
  2039         <dd><cite><a href="http://www.w3.org/Submission/">The list of acknowledged Member Submissions</a></cite></dd>
  2039         <dd><cite><a href="http://www.w3.org/Submission/">The list of acknowledged Member Submissions</a></cite></dd>
  2040         <dt id="rdf-doc-list">[PUB11]</dt>
  2040         <dt id="ref-doc-list">[PUB11]</dt>
  2041         <dd><cite><a href="http://www.w3.org/TR/">The W3C technical reports index</a></cite></dd>
  2041         <dd><cite><a href="http://www.w3.org/TR/">The W3C technical reports index</a></cite></dd>
  2042         <dt id="rdf-submission-overview">[PUB13]</dt>
  2042         <dt id="ref-submission-overview">[PUB13]</dt>
  2043         <dd><cite><a href="http://www.w3.org/Submission/1996/Template/">Submission request overview</a></cite></dd>
  2043         <dd><cite><a href="http://www.w3.org/Submission/1996/Template/">Submission request overview</a></cite></dd>
  2044         <dt id="rdf-people">[PUB14]</dt>
  2044         <dt id="ref-people">[PUB14]</dt>
  2045         <dd><cite><a href="http://www.w3.org/People/">The W3C Team</a></cite></dd>
  2045         <dd><cite><a href="http://www.w3.org/People/">The W3C Team</a></cite></dd>
  2046         <dt id="rdf-mission">[PUB15]</dt>
  2046         <dt id="ref-mission">[PUB15]</dt>
  2047         <dd><cite><a href="http://www.w3.org/Consortium/">About the World Wide Web Consortium</a></cite></dd>
  2047         <dd><cite><a href="http://www.w3.org/Consortium/">About the World Wide Web Consortium</a></cite></dd>
  2048         <dt id="rdf-team-submission-list">[PUB16]</dt>
  2048         <dt id="ref-team-submission-list">[PUB16]</dt>
  2049         <dd><cite><a href="http://www.w3.org/TeamSubmission/">The list of published Team Submissions</a></cite></dd>
  2049         <dd><cite><a href="http://www.w3.org/TeamSubmission/">The list of published Team Submissions</a></cite></dd>
  2050         <dt id="rdf-invited-expert">[PUB17]</dt>
  2050         <dt id="ref-invited-expert">[PUB17]</dt>
  2051         <dd><cite><a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and collaborators agreement</a></cite></dd>
  2051         <dd><cite><a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and collaborators agreement</a></cite></dd>
  2052         <dt id="rdf-doc-license">[PUB18]</dt>
  2052         <dt id="ref-doc-license">[PUB18]</dt>
  2053         <dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a></cite></dd>
  2053         <dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a></cite></dd>
  2054         <dt id="rdf-software-license">[PUB19]</dt>
  2054         <dt id="ref-software-license">[PUB19]</dt>
  2055         <dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-software">W3C Software Notice and License</a></cite></dd>
  2055         <dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-software">W3C Software Notice and License</a></cite></dd>
  2056         <dt id="rdf-translations">[PUB20]</dt>
  2056         <dt id="ref-translations">[PUB20]</dt>
  2057         <dd><cite><a href="http://www.w3.org/Consortium/Translation/">Translations of W3C technical reports</a></cite></dd>
  2057         <dd><cite><a href="http://www.w3.org/Consortium/Translation/">Translations of W3C technical reports</a></cite></dd>
  2058         <dt id="rdf-pub-mailing-lists">[PUB21]</dt>
  2058         <dt id="ref-pub-mailing-lists">[PUB21]</dt>
  2059         <dd><cite><a href="http://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
  2059         <dd><cite><a href="http://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
  2060         <dt id="rdf-coi">[PUB23]</dt>
  2060         <dt id="ref-coi">[PUB23]</dt>
  2061         <dd><cite><a href="http://www.w3.org/2000/09/06-conflictpolicy">Conflict of Interest Policy for W3C Team Members Engaged in Outside
  2061         <dd><cite><a href="http://www.w3.org/2000/09/06-conflictpolicy">Conflict of Interest Policy for W3C Team Members Engaged in Outside
  2062               Professional Activities</a></cite></dd>
  2062               Professional Activities</a></cite></dd>
  2063         <dt id="rdf-tag-charter">[PUB25]</dt>
  2063         <dt id="ref-tag-charter">[PUB25]</dt>
  2064         <dd><cite><a href="http://www.w3.org/2001/07/19-tag">Technical Architecture Group (TAG) Charter</a></cite></dd>
  2064         <dd><cite><a href="http://www.w3.org/2004/10/27-tag-charter">Technical Architecture Group (TAG) Charter</a></cite></dd>
  2065         <dt id="rdf-tag-home">[PUB26]</dt>
  2065         <dt id="ref-tag-home">[PUB26]</dt>
  2066         <dd><cite><a href="http://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
  2066         <dd><cite><a href="http://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
  2067         <dt id="rdf-rec-tips">[PUB27]</dt>
  2067         <dt id="ref-rec-tips">[PUB27]</dt>
  2068         <dd><cite><a href="http://www.w3.org/2002/05/rec-tips">Tips for Getting to Recommendation Faster</a></cite></dd>
  2068         <dd><cite><a href="http://www.w3.org/2002/05/rec-tips">Tips for Getting to Recommendation Faster</a></cite></dd>
  2069         <dt id="rdf-liaison-list">[PUB28]</dt>
  2069         <dt id="ref-liaison-list">[PUB28]</dt>
  2070         <dd><cite><a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a></cite></dd>
  2070         <dd><cite><a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a></cite></dd>
  2071         <dt id="rdf-ab-home">[PUB30]</dt>
  2071         <dt id="ref-ab-home">[PUB30]</dt>
  2072         <dd><cite><a href="http://www.w3.org/2002/ab/">The Advisory Board home page</a></cite></dd>
  2072         <dd><cite><a href="http://www.w3.org/2002/ab/">The Advisory Board home page</a></cite></dd>
  2073         <dt id="rdf-pubrules">[PUB31]</dt>
  2073         <dt id="ref-pubrules">[PUB31]</dt>
  2074         <dd><cite><a href="http://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
  2074         <dd><cite><a href="http://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
  2075         <dt id="rdf-fellows">[PUB32]</dt>
  2075         <dt id="ref-fellows">[PUB32]</dt>
  2076         <dd><cite><a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a></cite></dd>
  2076         <dd><cite><a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a></cite></dd>
  2077         <dt id="rdf-patentpolicy">[PUB33]</dt>
  2077         <dt id="ref-patentpolicy">[PUB33]</dt>
  2078         <dd><cite><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
  2078         <dd><cite><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
  2079           <a href="http://www.w3.org/Consortium/Patent-Policy/">latest version of the W3C Patent Policy</a> is available at
  2079           <a href="http://www.w3.org/Consortium/Patent-Policy/">latest version of the W3C Patent Policy</a> is available at
  2080           http://www.w3.org/Consortium/Patent-Policy/.</dd>
  2080           http://www.w3.org/Consortium/Patent-Policy/.</dd>
  2081         <dt id="in-place-tr-mod">[PUB35]</dt>
  2081         <dt id="in-place-tr-mod">[PUB35]</dt>
  2082         <dd><cite><a href="http://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
  2082         <dd><cite><a href="http://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
  2083       </dl>
  2083       </dl>
  2084       <h3>12.2 <a id="member-refs">Member-only Resources</a></h3>
  2084       <h3>12.2 <a id="member-refs">Member-only Resources</a></h3>
  2085       <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>
  2085       <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>
  2086       <dl>
  2086       <dl>
  2087         <dt id="rdf-current-ac">[MEM1]</dt>
  2087         <dt id="ref-current-ac">[MEM1]</dt>
  2088         <dd><cite><a href="http://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
  2088         <dd><cite><a href="http://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
  2089         <dt id="rdf-mailing-lists">[MEM2]</dt>
  2089         <dt id="ref-mailing-lists">[MEM2]</dt>
  2090         <dd><cite><a href="http://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
  2090         <dd><cite><a href="http://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
  2091         <dt id="rdf-calendar">[MEM3]</dt>
  2091         <dt id="ref-calendar">[MEM3]</dt>
  2092         <dd>The <cite><a href="http://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
  2092         <dd>The <cite><a href="http://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
  2093         <dt id="rdf-new-member">[MEM4]</dt>
  2093         <dt id="ref-new-member">[MEM4]</dt>
  2094         <dd>The <cite><a href="http://www.w3.org/Member/Intro">New Member Orientation</a></cite>, which includes an introduction to W3C
  2094         <dd>The <cite><a href="http://www.w3.org/Member/Intro">New Member Orientation</a></cite>, which includes an introduction to W3C
  2095           processes from a practical standpoint, including relevant email addresses.</dd>
  2095           processes from a practical standpoint, including relevant email addresses.</dd>
  2096         <dt id="rdf-ac-meetings">[MEM5]</dt>
  2096         <dt id="ref-ac-meetings">[MEM5]</dt>
  2097         <dd><cite><a href="http://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
  2097         <dd><cite><a href="http://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
  2098         <dt id="rdf-member-web">[MEM6]</dt>
  2098         <dt id="ref-member-web">[MEM6]</dt>
  2099         <dd><cite><a href="http://www.w3.org/Member/">Member Web site</a></cite></dd>
  2099         <dd><cite><a href="http://www.w3.org/Member/">Member Web site</a></cite></dd>
  2100         <dt id="rdf-member-sub">[MEM8]</dt>
  2100         <dt id="ref-member-sub">[MEM8]</dt>
  2101         <dd><cite><a href="http://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
  2101         <dd><cite><a href="http://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
  2102         <dt id="rdf-guide">[MEM9]</dt>
  2102         <dt id="ref-guide">[MEM9]</dt>
  2103         <dd><cite><a href="http://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other
  2103         <dd><cite><a href="http://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other
  2104           collaborators</dd>
  2104           collaborators</dd>
  2105         <dt id="rdf-discipline-gl">[MEM14]</dt>
  2105         <dt id="ref-discipline-gl">[MEM14]</dt>
  2106         <dd><cite><a href="http://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
  2106         <dd><cite><a href="http://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
  2107         <dt id="rdf-election-howto">[MEM15]</dt>
  2107         <dt id="ref-election-howto">[MEM15]</dt>
  2108         <dd><cite><a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
  2108         <dd><cite><a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
  2109       </dl>
  2109       </dl>
  2110       <h3 id="other-refs">12.3 Other References</h3>
  2110       <h3 id="other-refs">12.3 Other References</h3>
  2111       <dl>
  2111       <dl>
  2112         <dt id="rdf-RFC2119">[RFC2119]</dt>
  2112         <dt id="ref-RFC2119">[RFC2119]</dt>
  2113         <dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">"Key words for use in RFCs to Indicate Requirement Levels"</a></cite>, S.
  2113         <dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">"Key words for use in RFCs to Indicate Requirement Levels"</a></cite>, S.
  2114           Bradner, March 1997.</dd>
  2114           Bradner, March 1997.</dd>
  2115         <dt id="ref-RFC2777">[RFC2777]</dt>
  2115         <dt id="ref-RFC2777">[RFC2777]</dt>
  2116         <dd><cite><a href="http://www.ietf.org/rfc/rfc2777.txt">"Publicly Verifiable Nomcom Random Selection"</a></cite>, D. Eastlake 3rd,
  2116         <dd><cite><a href="http://www.ietf.org/rfc/rfc2777.txt">"Publicly Verifiable Nomcom Random Selection"</a></cite>, D. Eastlake 3rd,
  2117           February 2000.</dd>
  2117           February 2000.</dd>