Adding other chapters to prepare full version.
authorcharles
Wed, 19 Mar 2014 13:18:55 +0100
changeset 96 e2d162dfd842
parent 95 881ab929e726
child 97 18cca5e3bf7a
Adding other chapters to prepare full version.
acks.html
acreview.html
activities.html
comm.html
cover.html
events.html
groups.html
liaisons.html
organization.html
policies.html
processdoc.html
refs.html
submission.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/acks.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,56 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>14 Acknowledgments</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="previous" href="refs.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="p" rel="Prev" href="refs.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>14 <a name="acks" id="acks">Acknowledgments</a></h2>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>The following individuals participated in the preparation of this document
+while serving (at different times) on the W3C Advisory Board: Jean-François
+Abramatic (ILOG, and before that W3C Chair), Ann Bassetti (The Boeing Company),
+Jim Bell (HP), Klaus Birkenbihl (Fraunhofer Gesellschaft), Carl Cargill (Sun
+Microsystems), Paul Cotton (Microsoft), Don Deutsch (Oracle), David Fallside
+(IBM), Paul Grosso (Arbortext), Eduardo Gutentag (Sun Microsystems), Steve
+Holbrook (IBM), Renato Iannella (IPR Systems), Ken Laskey (MITRE), Ora Lassila
+(Nokia), Håkon Wium Lie (Opera Software), Larry Masinter (Adobe Systems), Bede
+McCall (MITRE), Thomas Reardon (Microsoft), Claus von Riegen (SAP AG), David
+Singer (IBM), Lauren Wood (unaffiliated), and Steve Zilles (Adobe Systems).</p>
+<p>Early drafts of the W3C Process Document were prepared by a special <a name=
+"erb" id="erb">Process Working Group</a>. The Working Group was elected by the
+Advisory Committee representatives on 16 September 1996 and closed in November
+1997. The following individuals participated in the Process Working Group (with
+their affiliations at that time): Carl Cargill (Netscape), Wendy Fong
+(Hewlett-Packard), John Klensin (MCI), Tim Krauskopf (Spyglass), Kari Laihonen
+(Ericsson), Thomas Reardon (Microsoft), David Singer (IBM), and Steve Zilles
+(Adobe). The Team members involved in the Process Working Group were:
+Jean-François Abramatic, Tim Berners-Lee, Ian Jacobs, and Sally Khudairi.</p>
+<p>Thanks also to Don Brutzman (Web3D) for earlier work on liaisons.</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="p" rel="Prev" href="refs.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/acreview.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,194 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>8 Advisory Committee Reviews, Appeals, and Votes</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="events.html" />
+<link rel="previous" href="tr.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="events.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="tr.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>8 <a name="ReviewAppeal" id="ReviewAppeal">Advisory Committee Reviews,
+Appeals, and Votes</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#ACReview" class="tocxref">8.1 Advisory Committee
+Reviews</a>
+<ul class="toc">
+<li class="tocline4"><a href="#ACReviewStart" class="tocxref">8.1.1 Start of a
+Review Period</a></li>
+<li class="tocline4"><a href="#ACReviewAfter" class="tocxref">8.1.2 After the
+Review Period</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#ACAppeal" class="tocxref">8.2 Appeal by Advisory
+Committee Representatives</a></li>
+<li class="tocline3"><a href="#ACVotes" class="tocxref">8.3 Advisory Committee
+Votes</a></li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>This section describes how the Advisory Committee reviews proposals from the
+Director and how Advisory Committee representatives appeal W3C decisions and
+decisions by the Director. A <a name="def-w3c-decision" 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=
+"activities.html#ActivityProposal">Activity Proposal</a>, after a <a href=
+"tr.html#cfr">Call for Review of a Proposed Recommendation</a>, after a
+<a href="tr.html#cfr-edited">Call for Review of a Proposed Recommendation</a>,
+after a <a href="tr.html#proposed-rescinded-rec">Proposal to Rescind a W3C
+Recommendation</a>, and after a <a href="processdoc.html#GAProcess">Proposed
+Process Document</a> review.</p>
+<h3>8.1 <a name="ACReview" id="ACReview">Advisory Committee Reviews</a></h3>
+<p>The Advisory Committee reviews:</p>
+<ul>
+<li>proposals for <a href="activities.html#ActivityCreation">new</a>, <a href=
+"activities.html#ActivityModification">modified</a>, and <a href=
+"activities.html#ActivityExtension">extended Activities</a>,</li>
+<li><a href="groups.html#CharterReview">new and modified Working and Interest
+Groups</a>,</li>
+<li><a href="tr.html#cfr">Proposed Recommendations</a>, <a href=
+"tr.html#cfr-edited">Proposed Edited Recommendations</a>, <a href=
+"tr.html#proposed-rescinded-rec">Proposal to Rescind a Recommendation</a>,
+and</li>
+<li><a href="processdoc.html#GAProcess">Proposed changes to the W3C
+process</a>.</li>
+</ul>
+<h4>8.1.1 <a name="ACReviewStart" id="ACReviewStart">Start of a Review
+Period</a></h4>
+<p>Each Advisory Committee review period begins with a Call for Review from the
+Team to the Advisory Committee. The <a name="reviewform" id="reviewform">review
+form</a> describes the proposal, raises attention to deadlines, estimates when
+the decision will be available, and includes other practical information. Each
+Member organization <span class="rfc2119">MAY</span> send one review, which
+<span class="rfc2119">MUST</span> be returned by its Advisory Committee
+representative.</p>
+<p>The Team <span class="rfc2119">MUST</span> provide two channels for Advisory
+Committee review comments:</p>
+<ol>
+<li>an archived <a href="comm.html#Team-only">Team-only</a> channel; this is
+the default channel for reviews.</li>
+<li>an archived <a href="comm.html#Member-only">Member-only</a> channel.</li>
+</ol>
+<p>Reviewers <span class="rfc2119">MAY</span> send information to either or
+both channels. They <span class="rfc2119">MAY</span> also share their reviews
+with other Members on the <a href="organization.html#ACCommunication">Advisory
+Committee discussion list</a>.</p>
+<p>A Member organization <span class="rfc2119">MAY</span> modify its review
+during a review period (e.g., in light of comments from other Members).</p>
+<h4>8.1.2 <a name="ACReviewAfter" id="ACReviewAfter">After the Review
+Period</a></h4>
+<p>After the review period, the Director <span class="rfc2119">MUST</span>
+announce to the Advisory Committee the level of support for the proposal
+(<a href="policies.html#def-Consensus">consensus</a> or <a href=
+"policies.html#def-Dissent">dissent</a>). The Director <span class=
+"rfc2119">MUST</span> also indicate whether there were any Formal Objections,
+with attention to <a href="comm.html#confidentiality-change">changing
+confidentiality level</a>. This <a href="#def-w3c-decision">W3C decision</a> is
+generally one of the following:</p>
+<ol>
+<li>The proposal is approved, possibly with <a href=
+"tr.html#minor-change">minor changes</a> integrated.</li>
+<li>The proposal is approved, possibly with <a href=
+"tr.html#substantive-change">substantive changes</a> integrated. In this case
+the Director's announcement <span class="rfc2119">MUST</span> include rationale
+for the decision to advance the document despite the proposal for a substantive
+change.</li>
+<li>The proposal is returned for additional work, with a request to the
+initiator to <a href="policies.html#formal-address">formally address</a>
+certain issues.</li>
+<li>The proposal is rejected.</li>
+</ol>
+<p>This document does not specify time intervals between the end of an Advisory
+Committee review period and the <a href="#def-w3c-decision">W3C decision</a>.
+This is to ensure that the Members and Team have sufficient time to consider
+comments gathered during the review. The Advisory Committee <span class=
+"rfc2119">SHOULD NOT</span> expect an announcement sooner than <span class=
+"time-interval">two weeks</span> after the end of a Proposed Recommendation
+review period. If, after <span class="time-interval">three weeks</span>, the
+Director has not announced the outcome, the Director <span class=
+"rfc2119">SHOULD</span> provide the Advisory Committee with an update.</p>
+<h3>8.2 <a name="ACAppeal" id="ACAppeal">Appeal by Advisory Committee
+Representatives</a></h3>
+<p>Advisory Committee representatives <span class="rfc2119">MAY</span> appeal
+certain decisions, though appeals are only expected to occur in extraordinary
+circumstances.</p>
+<p>When Advisory Committee review immediately precedes a decision, Advisory
+Committee representatives <span class="rfc2119">MAY</span> only appeal when
+there is <a href="policies.html#def-Dissent">dissent</a>. These decisions
+are:</p>
+<ul>
+<li><a href="tr.html#rec-publication">Publication of a Recommendation</a> or
+<a href="tr.html#publication-rescinded-rec">Publication of a Rescinded
+Recommendation</a>,</li>
+<li><a href="activities.html#ActivityProposal">Activity creation</a>, <a href=
+"activities.html#ActivityModification">modification</a>, or <a href=
+"activities.html#ActivityExtension">extension</a>,</li>
+<li><a href="groups.html#cfp">Working or Interest Group creation</a> or
+<a href="groups.html#charter-extension">extension</a>,</li>
+<li>Changes to the <a href="processdoc.html#GAProcess">W3C process</a>.</li>
+</ul>
+<p>Advisory Committee representatives <span class="rfc2119">MAY</span> always
+appeal the following decisions:</p>
+<ul>
+<li><a href="activities.html#ActivityTermination">Activity closure</a>,</li>
+<li><a href="groups.html#charter-extension">Working or Interest Group
+extension</a> or <a href="groups.html#GeneralTermination">closure</a>,</li>
+<li><a href="tr.html#cfi">Call for Implementations</a>, <a href=
+"tr.html#cfr">Call for Review of a Proposed Recommendation</a>, <a href=
+"tr.html#cfr-edited">Call for Review of an Edited Recommendation</a>, or
+<a href="tr.html#proposed-rescinded-rec">Proposal to Rescind a
+Recommendation</a></li>
+<li>the Director's intention to sign a <a href="liaisons.html#mou">Memorandum
+of Understanding</a> with another organization.</li>
+</ul>
+<p>In all cases, an appeal <span class="rfc2119">MUST</span> be initiated
+within <span class="time-interval">three weeks</span> of the decision.</p>
+<p>An Advisory Committee representative initiates an appeal by sending a
+request to the Team (explained in detail in the <a href=
+"http://www.w3.org/Member/Intro">New Member Orientation</a>). The Team
+<span class="rfc2119">MUST</span> announce the appeal process to the Advisory
+Committee and provide an address for comments from Advisory Committee
+representatives. The archive of these comments <span class=
+"rfc2119">MUST</span> be Member-visible. If, within <span class=
+"time-interval">one week</span> of the Team's announcement, 5% or more of the
+Advisory Committee support the appeal request, the Team <span class=
+"rfc2119">MUST</span> organize an appeal vote asking the Advisory Committee to
+approve or reject the decision. <!-- Voting procedure to be determined --></p>
+<h3>8.3 <a name="ACVotes" id="ACVotes">Advisory Committee Votes</a></h3>
+<p>The Advisory Committee votes in <a href=
+"organization.html#AB-TAG-elections">elections for seats on the TAG or Advisory
+Board</a>, and in the event of a formal appeal of a <a href=
+"#def-w3c-decision">W3C decision</a>. Whenever the Advisory Committee votes,
+each Member or group of <a href="organization.html#MemberRelated">related
+Members</a> has one vote. In the case of <a href=
+"organization.html#AB-TAG-elections">Advisory Board and TAG elections</a>, "one
+vote" means "one vote per available seat".</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="events.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="tr.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/activities.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,215 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>5 Activities</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="groups.html" />
+<link rel="previous" href="comm.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="groups.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="comm.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>5 <a name="Activities" id="Activities">Activities</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#ActivityDevelopment" class="tocxref">5.1
+Activity Proposal Development</a></li>
+<li class="tocline3"><a href="#ActivityCreation" class="tocxref">5.2 Advisory
+Committee Review of an Activity Proposal</a></li>
+<li class="tocline3"><a href="#ActivityModification" class="tocxref">5.3
+Modification of an Activity</a></li>
+<li class="tocline3"><a href="#ActivityExtension" class="tocxref">5.4 Extension
+of an Activity</a></li>
+<li class="tocline3"><a href="#ActivityTermination" class="tocxref">5.5
+Activity Closure</a></li>
+<li class="tocline3"><a href="#BPCreation" class="tocxref">5.6 Activity
+Proposals</a></li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>This section describes the mechanisms for establishing consensus within the
+areas of Web development the Consortium chooses to pursue. An <a name=
+"def-Activity" id="def-Activity">Activity</a> organizes the work necessary for
+the development or evolution of a Web technology.</p>
+<p>W3C starts an Activity based on interest from the Members and Team. W3C
+Members build interest around new work through discussions among Advisory
+Committee representatives, Chairs, and Team, and through the <a href=
+"submission.html#Submission">Submission process</a>. The Team tracks Web
+developments inside and outside W3C, manages <a href=
+"liaisons.html#Liaisons">liaisons</a>, and organizes <a href=
+"events.html#EventsW">Workshops</a>.</p>
+<p>Based on input from the Team and Members about the structure and scope of an
+Activity, the Team sends an <a href="#ActivityProposal">Activity Proposal</a>
+to the Advisory Committee. This is a proposal to dedicate Team and Member
+resources to a particular area of Web technology or policy, and when there is
+consensus about the motivation, scope, and structure of the proposed work, W3C
+starts a new Activity.</p>
+<p>Each Activity has its own structure that generally includes Working Groups,
+Interest Groups, and Coordination Groups. Within the framework of an Activity,
+these groups produce technical reports, review the work of other groups, and
+develop sample code or test suites.</p>
+<p>The progress of each Activity is documented in an <a name=
+"ActivityStatement" id="ActivityStatement">Activity Statement</a>. Activity
+Statements describe the goals of the Activity, completed and unfinished
+deliverables, changing perspectives based on experience, and future plans. At
+least before each <a href="organization.html#ACMeetings">Advisory Committee
+meeting</a>, the Team <span class="rfc2119">SHOULD</span> revise the Activity
+Statement for each Activity that has not been closed.</p>
+<p>Refer to the <a href="http://www.w3.org/Consortium/activities">list of W3C
+Activities</a> [<a href="refs.html#ref-activity-list">PUB9</a>].
+<strong>Note:</strong> This list <span class="rfc2119">MAY</span> include some
+Activities that began prior to the formalization in 1997 of the Activity
+creation process.</p>
+<h3>5.1 <a name="ActivityDevelopment" id="ActivityDevelopment">Activity
+Proposal Development</a></h3>
+<p>The Team <span class="rfc2119">MUST</span> notify the Advisory Committee
+when a proposal for a new or modified Activity is in development. This is
+intended to raise awareness, even if no formal proposal is yet available.
+Advisory Committee representatives <span class="rfc2119">MAY</span> express
+their general support on the <a href=
+"organization.html#ACCommunication">Advisory Committee discussion list</a>. The
+Team <span class="rfc2119">MAY</span> incorporate discussion points into an
+Activity Proposal. Refer to additional <a href=
+"http://www.w3.org/2002/05/rec-tips">tips on getting to Recommendation
+faster</a> [<a href="refs.html#ref-rec-tips">PUB27</a>].</p>
+<h3>5.2 <a name="ActivityCreation" id="ActivityCreation">Advisory Committee
+Review</a> of an Activity Proposal</h3>
+<p>The Director <span class="rfc2119">MUST</span> solicit <a href=
+"acreview.html#ReviewAppeal">Advisory Committee review</a> of every proposal to
+create, substantively modify, or extend an Activity.</p>
+<p>After a Call for Review from the Director, the Advisory Committee <a href=
+"acreview.html#ACReview">reviews</a> and comments on the proposal. The review
+period <span class="rfc2119">MUST</span> be at least <span class=
+"time-interval">four weeks</span>.</p>
+<p>The Director announces to the Advisory Committee whether there is consensus
+within W3C to create or modify the Activity (possibly with changes suggested
+during the review). For a new Activity, this announcement officially creates
+the Activity. This announcement <span class="rfc2119">MAY</span> include a
+<a href="groups.html#cfp">Call for Participation</a> in any groups created as
+part of the Activity.</p>
+<p>If there was <a href="policies.html#def-Dissent">dissent</a>, Advisory
+Committee representatives <span class="rfc2119">MAY</span> <a href=
+"acreview.html#ACAppeal">appeal</a> a decision to create, modify, or extend the
+Activity. <strong>Note:</strong> There is no appeal of a decision <em>not</em>
+to create an Activity; in general, drafting a new Activity Proposal will be
+simpler than following the appeal process.</p>
+<h3>5.3 <a name="ActivityModification" id="ActivityModification">Modification
+of an Activity</a></h3>
+<p>Activities are intended to be flexible. W3C expects participants to be able
+to adapt in the face of new ideas (e.g., Member Submission requests) and
+increased understanding of goals and context, while remaining true to the
+intent of the original Activity Proposal. If it becomes necessary to make
+substantive changes to an Activity (e.g., because significant additional
+resources are necessary or because the Activity's scope has clearly changed
+from the original proposal), then the Director <span class=
+"rfc2119">MUST</span> solicit <a href="#ActivityCreation">Advisory Committee
+review</a> of a complete <a href="#BPCreation">Activity Proposal</a>, including
+rationale for the changes.</p>
+<h3>5.4 <a name="ActivityExtension" id="ActivityExtension">Extension of an
+Activity</a></h3>
+<p>When the Director solicits <a href="#ActivityCreation">Advisory Committee
+review</a> of a proposal to extend the duration of an Activity with no other
+substantive modifications to the composition of the Activity, the proposal
+<span class="rfc2119">MUST</span> indicate the new duration and include
+rationale for the extension. The Director is <span class="rfc2119">NOT
+REQUIRED</span> to submit a complete <a href="#BPCreation">Activity
+Proposal</a>.</p>
+<h3>5.5 <a name="ActivityTermination" id="ActivityTermination">Activity
+Closure</a></h3>
+<p>An Activity Proposal specifies a duration for the Activity. The Director,
+subject to <a href="acreview.html#ACAppeal">appeal</a> by Advisory Committee
+representatives, <span class="rfc2119">MAY</span> close an Activity prior to
+the date specified in the proposal in any of the following circumstances:</p>
+<ul>
+<li>Groups in the Activity fail to produce chartered deliverables.</li>
+<li>Groups in the Activity produce chartered deliverables ahead of
+schedule.</li>
+<li>There are insufficient resources to maintain the Activity, according to
+priorities established within W3C.</li>
+</ul>
+<p>The Director closes an Activity by announcement to the Advisory
+Committee.</p>
+<h3>5.6 <a name="BPCreation" id="BPCreation"></a><a name="ActivityProposal" id=
+"ActivityProposal">Activity Proposals</a></h3>
+<p>An Activity Proposal defines the initial scope and structure of an Activity.
+The proposal <span class="rfc2119">MUST</span> include or reference the
+following information:</p>
+<ul>
+<li>An Activity summary. What is the nature of the Activity (e.g., to track
+developments, create technical reports, develop code, organize pilot
+experiments, or for education)? Who or what group wants this (providers or
+users)?</li>
+<li>Context information. Why is this Activity being proposed now? What is the
+situation in the world (e.g., with respect to the Web community, market,
+research, or society)? within the scope of the proposal? Who or what currently
+exists that is pertinent to this Activity? Is the community
+mature/growing/developing a niche? What competing technologies exist? What
+competing organizations exist?</li>
+<li>A description of the Activity's scope. How might a potential Recommendation
+interact and overlap with existing international standards and Recommendations?
+What organizations are likely to be affected by potential overlap (see the
+section on <a href="liaisons.html#Liaisons">liaisons with other
+organizations</a>)? What should be changed if the Activity is approved?</li>
+<li>A description of the Activity's initial deployment, including:
+<ul>
+<li>The duration of the Activity.</li>
+<li>What <a href="groups.html#GAGroups">groups</a> will be created as part of
+this Activity and how those groups will be coordinated. For each group, the
+proposal <span class="rfc2119">MUST</span> include a provisional charter.
+Groups <span class="rfc2119">MAY</span> be scheduled to run concurrently or
+sequentially (either because of a dependency or an expected overlap in
+membership and the desirability of working on one subject at a time). These
+charters <span class="rfc2119">MAY</span> be amended based on review comments
+before the Director issues a <a href="groups.html#cfp">Call for
+Participation</a>.</li>
+<li>The expected timeline of the Activity, including proposed deliverable dates
+and scheduled <a href="events.html#GAEvents">Workshops and Symposia</a>.</li>
+<li>If known, the date of the first <a href=
+"policies.html#ftf-meeting">face-to-face meeting</a> of each proposed group.
+The date of the first face-to-face meeting of a proposed group <span class=
+"rfc2119">MUST NOT</span> be sooner than <span class="time-interval">eight
+weeks</span> after the date of the <a href="#ActivityProposal">Activity
+Proposal</a>.</li>
+</ul>
+</li>
+<li>A summary of resources (Member, Team, administrative, technical, and
+financial) expected to be dedicated to the Activity. The proposal <span class=
+"rfc2119">MAY</span> specify the threshold level of effort that Members are
+expected to pledge in order for the Activity to be accepted.</li>
+<li>Information about known dependencies within W3C or outside of W3C.</li>
+<li>Intellectual property information. What are the intellectual property
+(including patents and copyright) considerations affecting the success of the
+Activity? In particular, is there any reason to believe that it will be
+difficult to meet the Royalty-Free licensing goals of section 2 of the <a href=
+"http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href=
+"refs.html#ref-patentpolicy">PUB33</a>]?</li>
+<li>A list of supporters and references. What community is expected to benefit
+from this Activity? Are members of this community part of W3C now? Are they
+expected to join the effort?</li>
+</ul>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="groups.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="comm.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/comm.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,150 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>4 Dissemination Policies</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="activities.html" />
+<link rel="previous" href="policies.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="activities.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="policies.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>4 <a name="dissemination" id="dissemination">Dissemination
+Policies</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#confidentiality-levels" class="tocxref">4.1
+Confidentiality Levels</a>
+<ul class="toc">
+<li class="tocline4"><a href="#confidentiality-change" class="tocxref">4.1.1
+Changing Confidentiality Level</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>The Team is responsible for managing communication within W3C and with the
+general public (e.g., news services, press releases, managing the Web site and
+access privileges, and managing calendars). Members <span class=
+"rfc2119">SHOULD</span> solicit review by the Team prior to issuing press
+releases about their work within W3C.</p>
+<p>The Team makes every effort to ensure the persistence and availability of
+the following public information:</p>
+<ul>
+<li><a href="tr.html#Reports">W3C technical reports</a> whose publication has
+been approved by the Director. Per the Membership Agreement, W3C technical
+reports (and software) are available free of charge to the general public;
+(refer to the <a href=
+"http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document
+License</a> [<a href="refs.html#ref-doc-license">PUB18</a>]).</li>
+<li>A <a href="http://www.w3.org/Consortium/#mission">mission statement</a>
+[<a href="refs.html#ref-mission">PUB15</a>] that explains the purpose and
+mission of W3C, the key benefits for Members, and the organizational structure
+of W3C.</li>
+<li>Legal documents, including the <a href=
+"http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+Agreement</a> [<a href="refs.html#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=
+"events.html#GAEvents">Workshops</a>.</li>
+</ul>
+<p>To keep the Members abreast of W3C meetings, Workshops, and review
+deadlines, the Team provides them with a regular (e.g., weekly) news service
+and maintains a <a href="http://www.w3.org/Member/Eventscal">calendar</a>
+[<a href="refs.html#ref-calendar">MEM3</a>] of official W3C events. Members are
+encouraged to send schedule and event information to the Team for inclusion on
+this calendar.</p>
+<h3>4.1 <a name="confidentiality-levels" id=
+"confidentiality-levels">Confidentiality Levels</a></h3>
+<p>There are three principal levels of access to W3C information (on the W3C
+Web site, in W3C meetings, etc.): public, Member-only, and Team-only.</p>
+<p>While much information made available by W3C is public, <a name=
+"Member-only" id="Member-only">"Member-only" information</a> is available to
+authorized parties only, including representatives of Member organizations,
+<a href="groups.html#invited-expert-wg">Invited Experts</a>, the Advisory
+Board, the TAG, and the Team. For example, the <a href=
+"groups.html#WGCharter">charter</a> of some Working Groups may specify a
+Member-only confidentiality level for group proceedings.</p>
+<p><a name="Team-only" id="Team-only">"Team-only" information</a> is available
+to the Team and other authorized parties.</p>
+<p>Those authorized to access Member-only and Team-only information:</p>
+<ul>
+<li><span class="rfc2119">MUST</span> treat the information as confidential
+within W3C,</li>
+<li><span class="rfc2119">MUST</span> use reasonable efforts to maintain the
+proper level confidentiality, and</li>
+<li><span class="rfc2119">MUST NOT</span> release this information to the
+general public or press.</li>
+</ul>
+<p>The Team <span class="rfc2119">MUST</span> provide mechanisms to protect the
+confidentiality of Member-only information and ensure that authorized parties
+have proper access to this information. Documents <span class=
+"rfc2119">SHOULD</span> clearly indicate whether they require Member-only
+confidentiality. Individuals uncertain of the confidentiality level of a piece
+of information <span class="rfc2119">SHOULD</span> contact the Team.</p>
+<p>Advisory Committee representatives <span class="rfc2119">MAY</span>
+authorize Member-only access to <a href="policies.html#member-rep">Member
+representatives</a> and other individuals employed by the Member who are
+considered appropriate recipients. For instance, it is the responsibility of
+the Advisory Committee representative and other employees and official
+representatives of the organization to ensure that Member-only news
+announcements are distributed for internal use only within their organization.
+Information about Member mailing lists is available in the <a href=
+"http://www.w3.org/Member/Intro">New Member Orientation</a>.</p>
+<h4>4.1.1 <a name="confidentiality-change" id="confidentiality-change">Changing
+Confidentiality Level</a></h4>
+<p>As a benefit of membership, W3C provides some Team-only and Member-only
+channels for certain types of communication. For example, Advisory Committee
+representatives can send <a href="acreview.html#ACReview">reviews</a> to a
+Team-only channel. However, for W3C processes with a significant public
+component, such as the technical report development process, it is also
+important for information that affects decision-making to be publicly
+available. The Team <span class="rfc2119">MAY</span> need to communicate
+Team-only information to a Working Group or the public. Similarly, a Working
+Group whose proceedings are Member-only <span class="rfc2119">MUST</span> make
+public information pertinent to the technical report development process.</p>
+<p>This document clearly indicates which information <span class=
+"rfc2119">MUST</span> be available to Members or the public, even though that
+information was initially communicated on Team-only or Member-only channels.
+Only the Team and parties authorized by the Team change the level of
+confidentiality of this information. When doing so:</p>
+<ol>
+<li>The Team <span class="rfc2119">MUST</span> use a version of the information
+that was expressly provided by the author for the new confidentiality level. In
+Calls for Review and other similar messages, the Team <span class=
+"rfc2119">SHOULD</span> remind recipients to provide such alternatives.</li>
+<li>The Team <span class="rfc2119">MUST NOT</span> attribute the version for
+the new confidentiality level to the author without the author's consent.</li>
+<li>If the author has not conveyed to the Team a version that is suitable for
+another confidentiality level, the Team <span class="rfc2119">MAY</span> make
+available a version that reasonably communicates what is required, while
+respecting the original level of confidentiality, and without attribution to
+the original author.</li>
+</ol>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="activities.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="policies.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/cover.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,572 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="keywords" content=
+"W3C, World Wide Web, Web, WWW, Consortium, process, Team, Recommendation, Advisory Committee, Advisory Board, Working Group, Coordination Group, Interest Group, W3C Activity, Workshop, Symposium, charter, Activity Proposal, Working Draft, Process Document, Candidate Recommendation, Director, Proposed Recommendation, Last Call, Submission request" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>World Wide Web Consortium Process Document</title>
+
+<style type="text/css">
+/*<![CDATA[*/
+     .about { margin-left: 3em; margin-right: 3em; font-size: .83em}
+     table { margin-left: auto; margin-right: auto }
+     .diagram { text-align: center; margin: 2.5em 0 }
+/*]]>*/
+</style>
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="c" rel="Contents" href="#toc">contents</a>] &nbsp;</p>
+</map></div>
+</div>
+<div class="head"><a href="http://www.w3.org/"><img height="48" width="72" alt=
+"W3C" src="http://www.w3.org/Icons/w3c_home" /></a>
+<h1>World Wide Web Consortium Process Document</h1>
+<h2 class="notoc">14 October 2005</h2>
+<dl>
+<dt>This version:</dt>
+<dd><a href=
+"http://www.w3.org/2005/10/Process-20051014/">http://www.w3.org/2005/10/Process-20051014/</a></dd>
+<dt>Latest operative version:</dt>
+<dd><a href=
+"http://www.w3.org/Consortium/Process/">http://www.w3.org/Consortium/Process/</a></dd>
+<dt>Previous operative version:</dt>
+<dd><a href=
+"http://www.w3.org/2004/02/Process-20040205/">http://www.w3.org/2004/02/Process-20040205/</a></dd>
+<dt>Editor:</dt>
+<dd>Ian Jacobs, <a href="http://www.w3.org/">W3C</a></dd>
+</dl>
+<p>Please refer to the <a href=
+"http://www.w3.org/Consortium/Process/errata"><strong>errata</strong></a> for
+this document, which may include some normative corrections.</p>
+<p>This document is also available in these non-normative packages: <a href=
+"process.html">single&nbsp;HTML&nbsp;file</a>, <a href=
+"process.tgz">self-contained&nbsp;gzipped&nbsp;tar&nbsp;archive</a>, <a href=
+"process.zip">self-contained&nbsp;zip&nbsp;archive.</a></p>
+<p>There may be <a href=
+"http://www.w3.org/Consortium/Translation/"><strong>translations</strong></a>
+of this document.</p>
+<p class="copyright"><a href=
+"http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
+1996-2005 <a href="/"><acronym title=
+"World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href=
+"http://www.csail.mit.edu/"><acronym title=
+"Massachusetts Institute of Technology">MIT</acronym></a>, <a href=
+"http://www.ercim.org/"><acronym title=
+"European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
+<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href=
+"/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href=
+"/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a rel="Copyright"
+href="/Consortium/Legal/copyright-documents">document use</a> and <a rel=
+"Copyright" href="/Consortium/Legal/copyright-software">software licensing</a>
+rules apply. Your interactions with this site are in accordance with our
+<a href="/Consortium/Legal/privacy-statement#Public">public</a> and <a href=
+"/Consortium/Legal/privacy-statement#Members">Member</a> privacy
+statements.</p>
+<hr /></div>
+<h2 class="notoc"><a name="abstract" id="abstract">Abstract</a></h2>
+<p>The mission of the World Wide Web Consortium (<acronym>W3C</acronym>) is to
+lead the World Wide Web to its full potential by developing common protocols
+that promote its evolution and ensure its interoperability. The W3C Process
+Document describes the organizational structure of the W3C and the processes
+related to the responsibilities and functions they exercise to enable W3C to
+accomplish its mission. This document does not describe the internal workings
+of the Team or W3C's public communication mechanisms.</p>
+<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=
+"refs.html#ref-mission">PUB15</a>].</p>
+<h2 class="notoc"><a name="status" id="status">Status of this Document</a></h2>
+<p>This is the 14 October 2005 version of the W3C Process Document. This
+document has been produced by the <a href="/Member/Board/">W3C Advisory
+Board</a> and reviewed by the <a href="/Consortium/Member/List">W3C Members</a>
+and Team.</p>
+<p>The <a href="/Consortium/Process/ProcessChanges">list of changes to the
+public Process Document</a> is available on the Web.</p>
+<p>W3C, including all existing chartered groups, follows the most recent
+operative Process Document announced to the Membership.</p>
+<p>Please send comments about this document to [email protected] (<a href=
+"http://lists.w3.org/Archives/Member/process-issues/">Member-only
+archive</a>).</p>
+<p>Additional Member-only information about the Process Document (e.g., issues
+lists, Member-only drafts, and changes to Member-only drafts) is available from
+the <a href="/Consortium/Process/Plan/">Process Plan page</a>. General
+information <a href="/Consortium/">about W3C</a> is available on the Web,
+including information about <a href="/Consortium/join">becoming a W3C
+Member</a>.</p>
+<p>The terms MUST, MUST NOT, SHOULD, SHOULD NOT, REQUIRED, and MAY when
+highlighted (through style sheets, and in uppercase in the source) are used in
+accordance with <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>
+[<a href="refs.html#ref-RFC2119">RFC2119</a>]. The term NOT REQUIRED (not
+defined in RFC 2119) indicates exemption.</p>
+<p>Some terms have been capitalized in this document (and in other W3C
+materials) to indicate that they are entities with special relevance to the W3C
+Process. These terms are defined herein, and readers should be aware that the
+ordinary (English) definitions are incomplete for purposes of understanding
+this document.</p>
+<h2 class="notoc"><a name="pp" id="pp">Relation of Process Document to Patent
+Policy</a></h2>
+<p>W3C Members' attention is called to the fact that provisions of the Process
+Document are binding on Members per the <a href=
+"http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+Agreement</a> [<a href="refs.html#ref-member-agreement">PUB6</a>]. The Patent
+Policy <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
+Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>] is incorporated by
+normative reference as a part of the Process Document, and is thus equally
+binding.</p>
+<p>The Patent Policy places additional obligations on Members, Team, and other
+participants in W3C. The Process Document does not restate those requirements
+but includes references to them. The Process Document and Patent Policy have
+been designed so that they may evolve independently.</p>
+<p>In the Process Document, the term "participant" refers to an individual, not
+an organization.</p>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<div class="toc">
+<h2 class="notoc"><a name="toc" id="toc">Table of Contents</a></h2>
+<div class="noprint">
+<ul class="toc">
+<li class="tocline2"><a href="intro.html#Intro" class="tocxref">1
+Introduction</a></li>
+<li class="tocline2"><a href="organization.html#Organization" class="tocxref">2
+Members, Advisory Committee, Team, Advisory Board, Technical Architecture
+Group</a></li>
+<li class="tocline2"><a href="policies.html#Policies" class="tocxref">3 General
+Policies for W3C Groups</a></li>
+<li class="tocline2"><a href="comm.html#dissemination" class="tocxref">4
+Dissemination Policies</a></li>
+<li class="tocline2"><a href="activities.html#Activities" class="tocxref">5
+Activities</a></li>
+<li class="tocline2"><a href="groups.html#GAGeneral" class="tocxref">6 Working
+Groups, Interest Groups, and Coordination Groups</a></li>
+<li class="tocline2"><a href="tr.html#Reports" class="tocxref">7 W3C Technical
+Report Development Process</a></li>
+<li class="tocline2"><a href="acreview.html#ReviewAppeal" class="tocxref">8
+Advisory Committee Reviews, Appeals, and Votes</a></li>
+<li class="tocline2"><a href="events.html#GAEvents" class="tocxref">9 Workshops
+and Symposia</a></li>
+<li class="tocline2"><a href="liaisons.html#Liaisons" class="tocxref">10
+Liaisons</a></li>
+<li class="tocline2"><a href="submission.html#Submission" class="tocxref">11
+Member Submission Process</a></li>
+<li class="tocline2"><a href="processdoc.html#GAProcess" class="tocxref">12
+Process Evolution</a></li>
+<li class="tocline2"><a href="refs.html#references" class="tocxref">13
+References</a></li>
+<li class="tocline2"><a href="acks.html#acks" class="tocxref">14
+Acknowledgments</a></li>
+</ul>
+</div>
+</div>
+<div class="longtoc">
+<div class="noprint">
+<h3 class="notoc"><a name="fulltoc" id="fulltoc">Expanded table of
+contents</a></h3>
+</div>
+<ul class="toc">
+<li class="tocline2"><a href="intro.html#Intro" name="Intro" id="Intro">1
+Introduction</a></li>
+<li class="tocline2"><a href="organization.html#Organization" name=
+"Organization" id="Organization">2 Members, Advisory Committee, Team, Advisory
+Board, Technical Architecture Group</a>
+<ul class="toc">
+<li class="tocline3"><a href="organization.html#Members" name="Members" id=
+"Members">2.1 Members</a><a name="MemberSubscription" id=
+"MemberSubscription"></a><a name="IndividualParticipation" id=
+"IndividualParticipation"></a>
+<ul class="toc">
+<li class="tocline4"><a href="organization.html#MemberBenefits" name=
+"MemberBenefits" id="MemberBenefits">2.1.1 Rights of Members</a></li>
+<li class="tocline4"><a href="organization.html#MemberRelated" name=
+"MemberRelated" id="MemberRelated">2.1.2 Related Members</a></li>
+<li class="tocline4"><a href="organization.html#AC" name="AC" id="AC">2.1.3
+Advisory Committee (AC)</a><a name="ACCommunication" id=
+"ACCommunication"></a><a name="ACMeetings" id="ACMeetings"></a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="organization.html#Team" name="Team" id="Team">2.2
+The W3C Team</a><a name="fellows" id="fellows"></a><a name="def-Director" id=
+"def-Director"></a><a name="DirectorDecision" id=
+"DirectorDecision"></a><a name="def-W3CChair" id="def-W3CChair"></a><a name=
+"def-COO" id="def-COO"></a><a name="hosts" id="hosts"></a>
+<ul class="toc">
+<li class="tocline4"><a href="organization.html#TeamSubmission" name=
+"TeamSubmission" id="TeamSubmission">2.2.1 Team Submissions</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="organization.html#AB" name="AB" id="AB">2.3
+Advisory Board (AB)</a>
+<ul class="toc">
+<li class="tocline4"><a href="organization.html#ABParticipation" name=
+"ABParticipation" id="ABParticipation">2.3.1 Advisory Board
+Participation</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="organization.html#TAG" name="TAG" id="TAG">2.4
+Technical Architecture Group (TAG)</a>
+<ul class="toc">
+<li class="tocline4"><a href="organization.html#tag-participation" name=
+"tag-participation" id="tag-participation">2.4.1 Technical Architecture Group
+Participation</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="organization.html#AB-TAG-participation" name=
+"AB-TAG-participation" id="AB-TAG-participation">2.5 Advisory Board and
+Technical Architecture Group Participation</a>
+<ul class="toc">
+<li class="tocline4"><a href="organization.html#AB-TAG-constraints" name=
+"AB-TAG-constraints" id="AB-TAG-constraints">2.5.1 Advisory Board and Technical
+Architecture Group Participation Constraints</a></li>
+<li class="tocline4"><a href="organization.html#AB-TAG-elections" name=
+"AB-TAG-elections" id="AB-TAG-elections">2.5.2 Advisory Board and Technical
+Architecture Group Elections</a><a name="random" id="random"></a></li>
+<li class="tocline4"><a href="organization.html#AB-TAG-vacated" name=
+"AB-TAG-vacated" id="AB-TAG-vacated">2.5.3 Advisory Board and Technical
+Architecture Group Vacated Seats</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="tocline2"><a href="policies.html#Policies" name="Policies" id=
+"Policies">3 General Policies for W3C Groups</a><a name="participant" id=
+"participant"></a>
+<ul class="toc">
+<li class="tocline3"><a href="policies.html#ParticipationCriteria" name=
+"ParticipationCriteria" id="ParticipationCriteria">3.1 Individual Participation
+Criteria</a>
+<ul class="toc">
+<li class="tocline4"><a href="policies.html#coi" name="coi" id="coi">3.1.1
+Conflict of Interest Policy</a></li>
+<li class="tocline4"><a href="policies.html#member-rep" name="member-rep" id=
+"member-rep">3.1.2 Individuals Representing a Member Organization</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="policies.html#GeneralMeetings" name=
+"GeneralMeetings" id="GeneralMeetings">3.2 Meetings</a><a name="ftf-meeting"
+id="ftf-meeting"></a><a name="distributed-meeting" id=
+"distributed-meeting"></a></li>
+<li class="tocline3"><a href="policies.html#Consensus" name="Consensus" id=
+"Consensus">3.3 Consensus</a><a name="def-Consensus" id=
+"def-Consensus"></a><a name="def-Unanimity" id="def-Unanimity"></a><a name=
+"def-Dissent" id="def-Dissent"></a>
+<ul class="toc">
+<li class="tocline4"><a href="policies.html#managing-dissent" name=
+"managing-dissent" id="managing-dissent">3.3.1 Managing Dissent</a></li>
+<li class="tocline4"><a href="policies.html#WGArchiveMinorityViews" name=
+"WGArchiveMinorityViews" id="WGArchiveMinorityViews">3.3.2 Recording and
+Reporting Formal Objections</a><a name="FormalObjection" id=
+"FormalObjection"></a></li>
+<li class="tocline4"><a href="policies.html#formal-address" name=
+"formal-address" id="formal-address">3.3.3 Formally Addressing an
+Issue</a></li>
+<li class="tocline4"><a href="policies.html#WGChairReopen" name="WGChairReopen"
+id="WGChairReopen">3.3.4 Reopening a Decision When Presented With New
+Information</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="policies.html#Votes" name="Votes" id="Votes">3.4
+Votes</a><a name="proxy" id="proxy"></a></li>
+<li class="tocline3"><a href="policies.html#WGAppeals" name="WGAppeals" id=
+"WGAppeals">3.5 Appeal of a Chair's Decision</a></li>
+<li class="tocline3"><a href="policies.html#resignation" name="resignation" id=
+"resignation">3.6 Resignation from a Group</a></li>
+</ul>
+</li>
+<li class="tocline2"><a href="comm.html#dissemination" name="dissemination" id=
+"dissemination">4 Dissemination Policies</a>
+<ul class="toc">
+<li class="tocline3"><a href="comm.html#confidentiality-levels" name=
+"confidentiality-levels" id="confidentiality-levels">4.1 Confidentiality
+Levels</a><a name="Member-only" id="Member-only"></a><a name="Team-only" id=
+"Team-only"></a>
+<ul class="toc">
+<li class="tocline4"><a href="comm.html#confidentiality-change" name=
+"confidentiality-change" id="confidentiality-change">4.1.1 Changing
+Confidentiality Level</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="tocline2"><a href="activities.html#Activities" name="Activities" id=
+"Activities">5 Activities</a><a name="def-Activity" id=
+"def-Activity"></a><a name="ActivityStatement" id="ActivityStatement"></a>
+<ul class="toc">
+<li class="tocline3"><a href="activities.html#ActivityDevelopment" name=
+"ActivityDevelopment" id="ActivityDevelopment">5.1 Activity Proposal
+Development</a></li>
+<li class="tocline3"><a href="activities.html#ActivityCreation" name=
+"ActivityCreation" id="ActivityCreation">5.2 Advisory Committee Review of an
+Activity Proposal</a></li>
+<li class="tocline3"><a href="activities.html#ActivityModification" name=
+"ActivityModification" id="ActivityModification">5.3 Modification of an
+Activity</a></li>
+<li class="tocline3"><a href="activities.html#ActivityExtension" name=
+"ActivityExtension" id="ActivityExtension">5.4 Extension of an
+Activity</a></li>
+<li class="tocline3"><a href="activities.html#ActivityTermination" name=
+"ActivityTermination" id="ActivityTermination">5.5 Activity Closure</a></li>
+<li class="tocline3"><a href="activities.html#BPCreation" name="BPCreation" id=
+"BPCreation">5.6 Activity Proposals</a><a name="ActivityProposal" id=
+"ActivityProposal"></a></li>
+</ul>
+</li>
+<li class="tocline2"><a href="groups.html#GAGeneral" name="GAGeneral" id=
+"GAGeneral">6 Working Groups, Interest Groups, and Coordination
+Groups</a><a name="GAGroups" id="GAGroups"></a>
+<ul class="toc">
+<li class="tocline3"><a href="groups.html#ReqsAllGroups" name="ReqsAllGroups"
+id="ReqsAllGroups">6.1 Requirements for All Working, Interest, and Coordination
+Groups</a><a name="GeneralChairs" id="GeneralChairs"></a><a name="TeamContact"
+id="TeamContact"></a></li>
+<li class="tocline3"><a href="groups.html#GroupsWG" name="GroupsWG" id=
+"GroupsWG">6.2 Working Groups and Interest Groups</a><a name="GroupsIG" id=
+"GroupsIG"></a>
+<ul class="toc">
+<li class="tocline4"><a href="groups.html#group-participation" name=
+"group-participation" id="group-participation">6.2.1 Working Group and Interest
+Group Participation Requirements</a><a name="wgparticipant" id=
+"wgparticipant"></a><a name="igparticipant" id="igparticipant"></a><a name=
+"public-participant-ig" id="public-participant-ig"></a><a name="mtg-substitute"
+id="mtg-substitute"></a><a name="member-rep-wg" id="member-rep-wg"></a><a name=
+"member-rep-info" id="member-rep-info"></a><a name="member-rep-ig" id=
+"member-rep-ig"></a><a name="invited-expert-wg" id=
+"invited-expert-wg"></a><a name="inv-expert-info" id=
+"inv-expert-info"></a><a name="invited-expert-ig" id=
+"invited-expert-ig"></a><a name="team-rep-wg" id="team-rep-wg"></a><a name=
+"team-rep-ig" id="team-rep-ig"></a><a name="good-standing" id=
+"good-standing"></a></li>
+<li class="tocline4"><a href="groups.html#WGCharterDevelopment" name=
+"WGCharterDevelopment" id="WGCharterDevelopment">6.2.2 Working Group and
+Interest Group Charter Development</a></li>
+<li class="tocline4"><a href="groups.html#CharterReview" name="CharterReview"
+id="CharterReview">6.2.3 Advisory Committee Review of a Working Group or
+Interest Group Charter</a></li>
+<li class="tocline4"><a href="groups.html#cfp" name="cfp" id="cfp">6.2.4 Call
+for Participation in a Working Group or Interest Group</a></li>
+<li class="tocline4"><a href="groups.html#charter-extension" name=
+"charter-extension" id="charter-extension">6.2.5 Working Group and Interest
+Group Charter Extension</a></li>
+<li class="tocline4"><a href="groups.html#WGCharter" name="WGCharter" id=
+"WGCharter">6.2.6 Working Group and Interest Group Charters</a><a name=
+"ig-mail-only" id="ig-mail-only"></a></li>
+<li class="tocline4"><a href="groups.html#three-month-rule" name=
+"three-month-rule" id="three-month-rule">6.2.7 Working Group "Heartbeat"
+Requirement</a></li>
+<li class="tocline4"><a href="groups.html#GeneralTermination" name=
+"GeneralTermination" id="GeneralTermination">6.2.8 Working Group and Interest
+Group Closure</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="groups.html#GroupsCG" name="GroupsCG" id=
+"GroupsCG">6.3 Coordination Groups</a>
+<ul class="toc">
+<li class="tocline4"><a href="groups.html#CGParticipation" name=
+"CGParticipation" id="CGParticipation">6.3.1 Coordination Group Participation
+Requirements</a><a name="cgparticipant" id="cgparticipant"></a></li>
+<li class="tocline4"><a href="groups.html#CGCreation" name="CGCreation" id=
+"CGCreation">6.3.2 Coordination Group Creation and Closure</a></li>
+<li class="tocline4"><a href="groups.html#CGCharter" name="CGCharter" id=
+"CGCharter">6.3.3 Coordination Group Charters</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="tocline2"><a href="tr.html#Reports" name="Reports" id="Reports">7
+W3C Technical Report Development Process</a>
+<ul class="toc">
+<li class="tocline3"><a href="tr.html#maturity-levels" name="maturity-levels"
+id="maturity-levels">7.1 Maturity Levels</a><a name="tr-init-state" id=
+"tr-init-state"></a><a name="tr-end-state" id="tr-end-state"></a>
+<ul class="toc">
+<li class="tocline4"><a href="tr.html#q73" name="q73" id="q73">7.1.1 Maturity
+Level for Work in Progress</a><a name="RecsWD" id="RecsWD"></a></li>
+<li class="tocline4"><a href="tr.html#q74" name="q74" id="q74">7.1.2 Maturity
+Levels of the Recommendation Track</a><a name="RecsCR" id="RecsCR"></a><a name=
+"RecsPR" id="RecsPR"></a><a name="RecsW3C" id="RecsW3C"></a></li>
+<li class="tocline4"><a href="tr.html#q75" name="q75" id="q75">7.1.3 Maturity
+Level When Ending Work on a Technical Report</a><a name="WGNote" id=
+"WGNote"></a></li>
+<li class="tocline4"><a href="tr.html#q76" name="q76" id="q76">7.1.4 Maturity
+Level When Editing a Recommendation</a><a name="ProposedEditedRec" id=
+"ProposedEditedRec"></a></li>
+<li class="tocline4"><a href="tr.html#q77" name="q77" id="q77">7.1.5 Maturity
+Levels When Rescinding a Recommendation</a><a name="RescindedRec" id=
+"RescindedRec"></a></li>
+<li class="tocline4"><a href="tr.html#q78" name="q78" id="q78">7.1.6 Maturity
+Levels For Interest Group and Coordination Group Technical Reports</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="tr.html#transition-reqs" name="transition-reqs"
+id="transition-reqs">7.2 General Requirements for Advancement on the
+Recommendation Track</a><a name="substantive-change" id=
+"substantive-change"></a><a name="minor-change" id="minor-change"></a></li>
+<li class="tocline3"><a href="tr.html#doc-reviews" name="doc-reviews" id=
+"doc-reviews">7.3 Reviews and Review Responsibilities</a></li>
+<li class="tocline3"><a href="tr.html#rec-advance" name="rec-advance" id=
+"rec-advance">7.4 Advancing a Technical Report to Recommendation</a>
+<ul class="toc">
+<li class="tocline4"><a href="tr.html#first-wd" name="first-wd" id=
+"first-wd">7.4.1 First Public Working Draft</a></li>
+<li class="tocline4"><a href="tr.html#last-call" name="last-call" id=
+"last-call">7.4.2 Last Call Announcement</a></li>
+<li class="tocline4"><a href="tr.html#cfi" name="cfi" id="cfi">7.4.3 Call for
+Implementations</a><a name="at-risk-feature" id="at-risk-feature"></a></li>
+<li class="tocline4"><a href="tr.html#cfr" name="cfr" id="cfr">7.4.4 Call for
+Review of a Proposed Recommendation</a></li>
+<li class="tocline4"><a href="tr.html#rec-publication" name="rec-publication"
+id="rec-publication">7.4.5 Publication of a W3C Recommendation</a></li>
+<li class="tocline4"><a href="tr.html#return-to-wg" name="return-to-wg" id=
+"return-to-wg">7.4.6 Returning a Document to a Working Group for Further
+Work</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="tr.html#tr-end" name="tr-end" id="tr-end">7.5
+Ending Work on a Technical Report</a></li>
+<li class="tocline3"><a href="tr.html#rec-modify" name="rec-modify" id=
+"rec-modify">7.6 Modifying a W3C Recommendation</a>
+<ul class="toc">
+<li class="tocline4"><a href="tr.html#errata" name="errata" id="errata">7.6.1
+Errata Management</a></li>
+<li class="tocline4"><a href="tr.html#correction-classes" name=
+"correction-classes" id="correction-classes">7.6.2 Classes of Changes to a
+Recommendation</a></li>
+<li class="tocline4"><a href="tr.html#cfr-edited" name="cfr-edited" id=
+"cfr-edited">7.6.3 Call for Review of an Edited Recommendation</a></li>
+<li class="tocline4"><a href="tr.html#cfr-corrections" name="cfr-corrections"
+id="cfr-corrections">7.6.4 Call for Review of Proposed Corrections</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="tr.html#rec-rescind" name="rec-rescind" id=
+"rec-rescind">7.7 Rescinding a W3C Recommendation</a>
+<ul class="toc">
+<li class="tocline4"><a href="tr.html#proposed-rescinded-rec" name=
+"proposed-rescinded-rec" id="proposed-rescinded-rec">7.7.1 Proposal to Rescind
+a Recommendation</a></li>
+<li class="tocline4"><a href="tr.html#publication-rescinded-rec" name=
+"publication-rescinded-rec" id="publication-rescinded-rec">7.7.2 Publication of
+a Rescinded Recommendation</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="tr.html#DocumentsGeneral" name="DocumentsGeneral"
+id="DocumentsGeneral">7.8 General Information about Technical
+Reports</a><a name="DocumentName" id="DocumentName"></a><a name=
+"document-copyright" id="document-copyright"></a>
+<ul class="toc">
+<li class="tocline4"><a href="tr.html#DocumentStatus" name="DocumentStatus" id=
+"DocumentStatus">7.8.1 Document Status Section</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li class="tocline2"><a href="acreview.html#ReviewAppeal" name="ReviewAppeal"
+id="ReviewAppeal">8 Advisory Committee Reviews, Appeals, and Votes</a><a name=
+"def-w3c-decision" id="def-w3c-decision"></a>
+<ul class="toc">
+<li class="tocline3"><a href="acreview.html#ACReview" name="ACReview" id=
+"ACReview">8.1 Advisory Committee Reviews</a>
+<ul class="toc">
+<li class="tocline4"><a href="acreview.html#ACReviewStart" name="ACReviewStart"
+id="ACReviewStart">8.1.1 Start of a Review Period</a><a name="reviewform" id=
+"reviewform"></a></li>
+<li class="tocline4"><a href="acreview.html#ACReviewAfter" name="ACReviewAfter"
+id="ACReviewAfter">8.1.2 After the Review Period</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="acreview.html#ACAppeal" name="ACAppeal" id=
+"ACAppeal">8.2 Appeal by Advisory Committee Representatives</a></li>
+<li class="tocline3"><a href="acreview.html#ACVotes" name="ACVotes" id=
+"ACVotes">8.3 Advisory Committee Votes</a></li>
+</ul>
+</li>
+<li class="tocline2"><a href="events.html#GAEvents" name="GAEvents" id=
+"GAEvents">9 Workshops and Symposia</a><a name="EventsW" id=
+"EventsW"></a><a name="EventsS" id="EventsS"></a><a name="EventsC" id=
+"EventsC"></a></li>
+<li class="tocline2"><a href="liaisons.html#Liaisons" name="Liaisons" id=
+"Liaisons">10 Liaisons</a><a name="mou" id="mou"></a></li>
+<li class="tocline2"><a href="submission.html#Submission" name="Submission" id=
+"Submission">11 Member Submission Process</a><a name="MemberSubmission" id=
+"MemberSubmission"></a>
+<ul class="toc">
+<li class="tocline3"><a href="submission.html#SubmissionRights" name=
+"SubmissionRights" id="SubmissionRights">11.1 Submitter Rights and
+Obligations</a>
+<ul class="toc">
+<li class="tocline4"><a href="submission.html#SubmissionScope" name=
+"SubmissionScope" id="SubmissionScope">11.1.1 Scope of Member
+Submissions</a></li>
+<li class="tocline4"><a href="submission.html#SubmissionReqs" name=
+"SubmissionReqs" id="SubmissionReqs">11.1.2 Information Required in a
+Submission Request</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="submission.html#TeamSubmissionRights" name=
+"TeamSubmissionRights" id="TeamSubmissionRights">11.2 Team Rights and
+Obligations</a><a name="validation-notice" id="validation-notice"></a></li>
+<li class="tocline3"><a href="submission.html#SubmissionYes" name=
+"SubmissionYes" id="SubmissionYes">11.3 Acknowledgment of a Submission
+Request</a></li>
+<li class="tocline3"><a href="submission.html#SubmissionNo" name="SubmissionNo"
+id="SubmissionNo">11.4 Rejection of a Submission Request</a></li>
+</ul>
+</li>
+<li class="tocline2"><a href="processdoc.html#GAProcess" name="GAProcess" id=
+"GAProcess">12 Process Evolution</a><a name="ProcessDoc" id=
+"ProcessDoc"></a></li>
+<li class="tocline2"><a href="refs.html#references" name="references" id=
+"references">13 References</a>
+<ul class="toc">
+<li class="tocline3"><a href="refs.html#public-refs" name="public-refs" id=
+"public-refs">13.1 Public Resources</a><a name="ref-join-w3c" id=
+"ref-join-w3c"></a><a name="ref-member-agreement" id=
+"ref-member-agreement"></a><a name="ref-current-mem" id=
+"ref-current-mem"></a><a name="ref-activity-list" id=
+"ref-activity-list"></a><a name="ref-submission-list" id=
+"ref-submission-list"></a><a name="ref-doc-list" id="ref-doc-list"></a><a name=
+"ref-submission-overview" id="ref-submission-overview"></a><a name="ref-people"
+id="ref-people"></a><a name="ref-mission" id="ref-mission"></a><a name=
+"ref-team-submission-list" id="ref-team-submission-list"></a><a name=
+"ref-invited-expert" id="ref-invited-expert"></a><a name="ref-doc-license" id=
+"ref-doc-license"></a><a name="ref-software-license" id=
+"ref-software-license"></a><a name="ref-translations" id=
+"ref-translations"></a><a name="ref-pub-mailing-lists" id=
+"ref-pub-mailing-lists"></a><a name="ref-coi" id="ref-coi"></a><a name=
+"ref-tag-charter" id="ref-tag-charter"></a><a name="ref-tag-home" id=
+"ref-tag-home"></a><a name="ref-rec-tips" id="ref-rec-tips"></a><a name=
+"ref-liaison-list" id="ref-liaison-list"></a><a name="ref-ab-home" id=
+"ref-ab-home"></a><a name="ref-pubrules" id="ref-pubrules"></a><a name=
+"ref-fellows" id="ref-fellows"></a><a name="ref-patentpolicy" id=
+"ref-patentpolicy"></a></li>
+<li class="tocline3"><a href="refs.html#member-refs" name="member-refs" id=
+"member-refs">13.2 Member-only Resources</a><a name="ref-current-ac" id=
+"ref-current-ac"></a><a name="ref-mailing-lists" id=
+"ref-mailing-lists"></a><a name="ref-calendar" id="ref-calendar"></a><a name=
+"ref-new-member" id="ref-new-member"></a><a name="ref-ac-meetings" id=
+"ref-ac-meetings"></a><a name="ref-member-web" id="ref-member-web"></a><a name=
+"ref-member-sub" id="ref-member-sub"></a><a name="ref-guide" id=
+"ref-guide"></a><a name="ref-discipline-gl" id="ref-discipline-gl"></a><a name=
+"ref-election-howto" id="ref-election-howto"></a></li>
+<li class="tocline3"><a href="refs.html#other-refs" name="other-refs" id=
+"other-refs">13.3 Other References</a><a name="ref-RFC2119" id=
+"ref-RFC2119"></a><a name="ref-RFC2777" id="ref-RFC2777"></a></li>
+</ul>
+</li>
+<li class="tocline2"><a href="acks.html#acks" name="acks" id="acks">14
+Acknowledgments</a></li>
+</ul>
+</div>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<p>[<a accesskey="c" rel="Contents" href="#toc">contents</a>] &nbsp;</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/events.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,71 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>9 Workshops and Symposia</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="liaisons.html" />
+<link rel="previous" href="acreview.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="liaisons.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="acreview.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>9 <a name="GAEvents" id="GAEvents">Workshops and Symposia</a></h2>
+<div class="toc"></div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>The Team organizes <a name="EventsW" id="EventsW">Workshops</a> and <a name=
+"EventsS" id="EventsS">Symposia</a> 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 policy, or to
+address the pressing concerns of W3C Members. Organizers of the first type of
+Workshop <span class="rfc2119">MAY</span> solicit position papers for the
+Workshop program and <span class="rfc2119">MAY</span> use those papers to
+choose attendees and/or presenters.</p>
+<p>The goal of a Symposium is usually to educate interested parties about a
+particular subject.</p>
+<p>The Call for Participation in a Workshop or Symposium <span class=
+"rfc2119">MAY</span> 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>
+<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 later
+than <span class="time-interval">six weeks</span> prior to the Workshop's
+scheduled start date. For other Workshops and Symposia, the Team <span class=
+"rfc2119">MUST</span> issue a Call for Participation no later than <span class=
+"time-interval">eight weeks</span> prior to the meeting's scheduled start date.
+This helps ensure that speakers and authors have adequate time to prepare
+position papers and talks.</p>
+<p><strong>Note:</strong> In general, W3C does not organize <a name="EventsC"
+id="EventsC">conferences</a>. Currently, W3C presents its work to the public at
+the annual World Wide Web Conference, which is coordinated by the <a href=
+"http://www.iw3c2.org/">International World Wide Web Conference Committee</a>
+(<acronym>IW3C2</acronym>).</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="liaisons.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="acreview.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/groups.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,649 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>6 Working Groups, Interest Groups, and Coordination Groups</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="tr.html" />
+<link rel="previous" href="activities.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="tr.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="activities.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>6 <a name="GAGeneral" id="GAGeneral">Working Groups, Interest Groups, and
+Coordination Groups</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#ReqsAllGroups" class="tocxref">6.1 Requirements
+for All Working, Interest, and Coordination Groups</a></li>
+<li class="tocline3"><a href="#GroupsWG" class="tocxref">6.2 Working Groups and
+Interest Groups</a>
+<ul class="toc">
+<li class="tocline4"><a href="#group-participation" class="tocxref">6.2.1
+Working Group and Interest Group Participation Requirements</a></li>
+<li class="tocline4"><a href="#WGCharterDevelopment" class="tocxref">6.2.2
+Working Group and Interest Group Charter Development</a></li>
+<li class="tocline4"><a href="#CharterReview" class="tocxref">6.2.3 Advisory
+Committee Review of a Working Group or Interest Group Charter</a></li>
+<li class="tocline4"><a href="#cfp" class="tocxref">6.2.4 Call for
+Participation in a Working Group or Interest Group</a></li>
+<li class="tocline4"><a href="#charter-extension" class="tocxref">6.2.5 Working
+Group and Interest Group Charter Extension</a></li>
+<li class="tocline4"><a href="#WGCharter" class="tocxref">6.2.6 Working Group
+and Interest Group Charters</a></li>
+<li class="tocline4"><a href="#three-month-rule" class="tocxref">6.2.7 Working
+Group "Heartbeat" Requirement</a></li>
+<li class="tocline4"><a href="#GeneralTermination" class="tocxref">6.2.8
+Working Group and Interest Group Closure</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#GroupsCG" class="tocxref">6.3 Coordination
+Groups</a>
+<ul class="toc">
+<li class="tocline4"><a href="#CGParticipation" class="tocxref">6.3.1
+Coordination Group Participation Requirements</a></li>
+<li class="tocline4"><a href="#CGCreation" class="tocxref">6.3.2 Coordination
+Group Creation and Closure</a></li>
+<li class="tocline4"><a href="#CGCharter" class="tocxref">6.3.3 Coordination
+Group Charters</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p><a name="GAGroups" id="GAGroups">This document defines three types of
+groups:</a></p>
+<ol>
+<li><a href="#GroupsWG">Working Groups.</a> Working Groups typically produce
+deliverables (e.g., <a href="tr.html#rec-advance">Recommendation Track
+technical reports</a>, software, test suites, and reviews of the deliverables
+of other groups). There are <a href="#good-standing">Good Standing</a>
+requirements for Working Group participation as well as additional
+participation requirements described in the <a href=
+"http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href=
+"refs.html#ref-patentpolicy">PUB33</a>].</li>
+<li><a href="#GroupsIG">Interest Groups.</a> The primary goal of an Interest
+Group is to bring together people who wish to evaluate potential Web
+technologies and policies. An Interest Group is a forum for the exchange of
+ideas.</li>
+<li><a href="#GroupsCG">Coordination Groups.</a> A Coordination Group manages
+dependencies and facilitates communication with other groups, within or outside
+of W3C.</li>
+</ol>
+<p>Neither Interest Groups nor Coordination Groups publish <a href=
+"#rec-track-doc">Recommendation Track technical reports</a>; see information
+about <a href="#ig-cg-notes">maturity levels for Interest Groups and
+Coordination Groups</a>.</p>
+<h3>6.1 <a name="ReqsAllGroups" id="ReqsAllGroups">Requirements for All
+Working, Interest, and Coordination Groups</a></h3>
+<p>Each group <span class="rfc2119">MUST</span> have a charter. Requirements
+for the charter depend on the group type. All group charters <span class=
+"rfc2119">MUST</span> be public (even if other proceedings of the group are
+<a href="comm.html#Member-only">Member-only</a>). Existing charters that are
+not yet public <span class="rfc2119">MUST</span> be made public when next
+revised or extended (with attention to <a href=
+"comm.html#confidentiality-change">changing confidentiality level</a>).</p>
+<p>Each group <span class="rfc2119">MUST</span> have a <a name="GeneralChairs"
+id="GeneralChairs">Chair</a> (or co-Chairs) to coordinate the group's tasks.
+The Director appoints (and re-appoints) Chairs for all groups. The Chair is a
+<a href="policies.html#member-rep">Member representative</a>, a <a href=
+"organization.html#Team">Team representative</a>, or an <a href=
+"#invited-expert-wg">Invited Expert</a> (invited by the Director). The
+requirements of this document that apply to those types of participants apply
+to Chairs as well. The <a href="/Guide/chair-roles">role of the Chair
+[MEM14]</a> is described in the <a href="http://www.w3.org/Guide/">Member
+guide</a> [<a href="refs.html#ref-guide">MEM9</a>].</p>
+<p>Each group <span class="rfc2119">MUST</span> have a <a name="TeamContact"
+id="TeamContact">Team Contact</a>, who acts as the interface between the Chair,
+group participants, and the rest of the Team. The <a href=
+"/Guide/staff-contact">role of the Team Contact</a> is described in the Member
+guide. The Chair and the Team Contact of a group <span class="rfc2119">SHOULD
+NOT</span> be the same individual.</p>
+<p>Each group <span class="rfc2119">MUST</span> have an archived mailing list
+for formal group communication (e.g., for meeting announcements and minutes,
+documentation of decisions, and <a href="policies.html#FormalObjection">Formal
+Objections</a> to decisions). It is the responsibility of the Chair and Team
+Contact to ensure that new participants are subscribed to all relevant mailing
+lists. Refer to the list of <a href="http://www.w3.org/Member/Mail/">group
+mailing lists</a> [<a href="refs.html#ref-mailing-lists">MEM2</a>].</p>
+<p>A Chair <span class="rfc2119">MAY</span> form task forces (composed of group
+participants) to carry out assignments for the group. The scope of these
+assignments <span class="rfc2119">MUST NOT</span> exceed the scope of the
+group's charter. A group <span class="rfc2119">SHOULD</span> document the
+process it uses to create task forces (e.g., each task force might have an
+informal "charter"). Task forces do not publish <a href=
+"tr.html#Reports">technical reports</a>; the Working Group <span class=
+"rfc2119">MAY</span> choose to publish their results as part of a technical
+report.</p>
+<h3>6.2 <a name="GroupsWG" id="GroupsWG">Working Groups</a> and <a name=
+"GroupsIG" id="GroupsIG">Interest Groups</a></h3>
+<p>Although Working Groups and Interest Groups have different purposes, they
+share some characteristics, and so are defined together in the following
+sections.</p>
+<h4>6.2.1 <a name="group-participation" id="group-participation">Working Group
+and Interest Group Participation Requirements</a></h4>
+<p>There are three types of individual <a name="wgparticipant" id=
+"wgparticipant">participants in a Working Group</a>: <a href=
+"policies.html#member-rep">Member representatives</a>, <a href=
+"#invited-expert-wg">Invited Experts</a>, and <a href=
+"organization.html#Team">Team representatives</a> (including the <a href=
+"#TeamContact">Team Contact</a>).</p>
+<p>There are four types of individual <a name="igparticipant" id=
+"igparticipant">participants in an Interest Group</a>: the same three types as
+for Working Groups plus, for an Interest Group where the only <a href=
+"#ig-mail-only">participation requirement is mailing list subscription</a>,
+<a name="public-participant-ig" id="public-participant-ig">public
+participants</a>.</p>
+<p>Except where noted in this document or in a group charter, all participants
+share the same rights and responsibilities in a group; see also the <a href=
+"policies.html#ParticipationCriteria">individual participation
+criteria</a>.</p>
+<p>A participant <span class="rfc2119">MUST</span> represent at most one
+organization in a Working Group or Interest Group.</p>
+<p>An individual <span class="rfc2119">MAY</span> become a Working or Interest
+Group participant at any time during the group's existence. See also relevant
+requirements in <a href=
+"http://www.w3.org/Consortium/Patent-Policy#sec-join">section 4.3</a> of the
+<a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
+[<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
+<p>On an exceptional basis, a Working or Interest Group participant
+<span class="rfc2119">MAY</span> designate a <a name="mtg-substitute" id=
+"mtg-substitute">substitute</a> to attend a <a href=
+"policies.html#GeneralMeetings">meeting</a> and <span class=
+"rfc2119">SHOULD</span> inform the Chair. The substitute <span class=
+"rfc2119">MAY</span> act on behalf of the participant, including for <a href=
+"policies.html#Votes">votes</a>. For the substitute to vote, the participant
+<span class="rfc2119">MUST</span> inform the Chair in writing in advance. As a
+courtesy to the group, if the substitute is not well-versed in the group's
+discussions, the regular participant <span class="rfc2119">SHOULD</span>
+authorize another participant to act as <a href="policies.html#proxy">proxy</a>
+for votes. For the purposes of <a href="#good-standing">Good Standing</a>, the
+regular representative and the substitute are considered the same
+participant.</p>
+<p>To allow rapid progress, Working Groups are intended to be small (typically
+fewer than 15 people) and composed of experts in the area defined by the
+charter. In principle, Interest Groups have no limit on the number of
+participants. When a Working Group grows too large to be effective, W3C
+<span class="rfc2119">MAY</span> split it into an Interest Group (a discussion
+forum) and a much smaller Working Group (a core group of highly dedicated
+participants).</p>
+<p>See also the licensing obligations on Working Group participants in <a href=
+"http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section 3</a> of
+the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
+[<a href="refs.html#ref-patentpolicy">PUB33</a>], and the patent claim
+exclusion process of <a href=
+"http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
+<h5>6.2.1.1 <a name="member-rep-wg" id="member-rep-wg">Member
+Representative</a> in a Working Group</h5>
+<p>An individual is a Member representative in a Working Group if all of the
+following conditions are satisfied:</p>
+<ul>
+<li>the Advisory Committee representative of the Member in question has
+designated the individual as a Working Group participant, and</li>
+<li>the individual qualifies for <a href="policies.html#member-rep">Member
+representation</a>.</li>
+</ul>
+<p><a name="member-rep-info" id="member-rep-info">To designate an individual as
+a Member representative in a Working Group</a>, an Advisory Committee
+representative <span class="rfc2119">MUST</span> provide the Chair and Team
+Contact with all of the following information, in addition to any other
+information required by the <a href="#cfp">Call for Participation</a> and
+charter (including the participation requirements of the <a href=
+"http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href=
+"refs.html#ref-patentpolicy">PUB33</a>]):</p>
+<ol>
+<li>The name of the W3C Member the individual represents and whether the
+individual is an employee of that Member organization;</li>
+<li>A statement that the individual accepts the participation terms set forth
+in the charter (with an indication of charter date or version);</li>
+<li>A statement that the Member will provide the necessary financial support
+for participation (e.g., for travel, telephone calls, and conferences).</li>
+</ol>
+<p>A Member participates in a Working Group from the moment the first Member
+representative joins the group until either of the following occurs:</p>
+<ul>
+<li>the group closes, or</li>
+<li>the Member <a href="policies.html#resignation">resigns</a> from the Working
+Group; this is done through the Member's Advisory Committee
+representative.</li>
+</ul>
+<h5>6.2.1.2 <a name="member-rep-ig" id="member-rep-ig">Member
+Representative</a> in an Interest Group</h5>
+<p>When the participation requirements exceed <a href="#ig-mail-only">Interest
+Group mailing list subscription</a>, an individual is a Member representative
+in an Interest Group if all of the following conditions are satisfied:</p>
+<ul>
+<li>the Advisory Committee representative of the Member in question has
+designated the individual as an Interest Group participant, and</li>
+<li>the individual qualifies for <a href="policies.html#member-rep">Member
+representation</a>.</li>
+</ul>
+<p>To designate an individual as a Member representative in an Interest Group,
+the Advisory Committee representative <span class="rfc2119">MUST</span> follow
+the instructions in the <a href="#cfp">Call for Participation</a> and
+charter.</p>
+<p>Member participation in an Interest Group ceases under the same conditions
+as for a Working Group.</p>
+<h5>6.2.1.3 <a name="invited-expert-wg" id="invited-expert-wg">Invited
+Expert</a> in a Working Group</h5>
+<p>The Chair <span class="rfc2119">MAY</span> invite an individual with a
+particular expertise to participate in a Working Group. This individual
+<span class="rfc2119">MAY</span> represent an organization in the group (e.g.,
+if acting as a liaison with another organization).</p>
+<p>An individual is an Invited Expert in a Working Group if all of the
+following conditions are satisfied:</p>
+<ul>
+<li>the Chair has designated the individual as a group participant,</li>
+<li>the Team Contact has agreed with the Chair's choice, and</li>
+<li>the individual has provided the <a href="#inv-expert-info">information
+required of an Invited Expert</a> to the Chair and Team Contact.</li>
+</ul>
+<p>To designate an individual as an Invited Expert in a Working Group, the
+Chair <span class="rfc2119">MUST</span> inform the Team Contact and provide
+rationale for the choice. When the Chair and the Team Contact disagree about a
+designation, the <a href="organization.html#def-Director">Director</a>
+determines whether the individual will be invited to participate in the Working
+Group.</p>
+<p><a name="inv-expert-info" id="inv-expert-info">To be able to participate in
+a Working Group as an Invited Expert</a>, an individual <span class=
+"rfc2119">MUST</span> do all of the following:</p>
+<ul>
+<li>identify the organization, if any, the individual represents as a
+participant in this group,</li>
+<li>agree to the terms of the <a href=
+"http://www.w3.org/Consortium/Legal/collaborators-agreement">invited expert and
+collaborators agreement</a> [<a href=
+"refs.html#ref-invited-expert">PUB17</a>],</li>
+<li>accept the participation terms set forth in the charter (including the
+participation requirements of <a href=
+"http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section 3</a>
+(especially 3.4) and <a href=
+"http://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section 6</a>
+(especially 6.10) of the <a href=
+"http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href=
+"refs.html#ref-patentpolicy">PUB33</a>]). Indicate a specific charter date or
+version,</li>
+<li>disclose whether the individual is an employee of a W3C Member; see the
+<a href="policies.html#coi">conflict of interest policy</a>,</li>
+<li>provide a statement of who will provide the necessary financial support for
+the individual's participation (e.g., for travel, telephone calls, and
+conferences), and</li>
+<li>if the individual's employer (including a self-employed individual) or the
+organization the individual represents is not a W3C Member, indicate whether
+that organization intends to join W3C. If the organization does not intend to
+join W3C, indicate reasons the individual is aware of for this choice.</li>
+</ul>
+<p>The Chair <span class="rfc2119">SHOULD NOT</span> designate as an Invited
+Expert in a Working Group an individual who is an employee of a W3C Member. The
+Chair <span class="rfc2119">MUST NOT</span> use Invited Expert status to
+circumvent participation limits imposed by the <a href=
+"#WGCharter">charter</a>.</p>
+<p>An Invited Expert participates in a Working Group from the moment the
+individual joins the group until any of the following occurs:</p>
+<ul>
+<li>the group closes, or</li>
+<li>the Chair or Director withdraws the invitation to participate, or</li>
+<li>the individual <a href="policies.html#resignation">resigns</a>.</li>
+</ul>
+<h5>6.2.1.4 <a name="invited-expert-ig" id="invited-expert-ig">Invited
+Expert</a> in an Interest Group</h5>
+<p>When the participation requirements exceed <a href="#ig-mail-only">Interest
+Group mailing list subscription</a>, the participation requirements for an
+Invited Expert in an Interest Group are the same as those for an <a href=
+"#invited-expert-wg">Invited Expert in a Working Group</a>.</p>
+<h5>6.2.1.5 <a name="team-rep-wg" id="team-rep-wg">Team Representative in a
+Working Group</a></h5>
+<p>An individual is a Team representative in a Working Group when so designated
+by W3C management.</p>
+<p>An Team representative participates in a Working Group from the moment the
+individual joins the group until any of the following occurs:</p>
+<ul>
+<li>the group closes, or</li>
+<li>W3C management changes Team representation by sending email to the Chair,
+cc'ing the group mailing list.</li>
+</ul>
+<p>The Team participates in a Working Group from the moment the Director
+announces the creation of the group until the group closes.</p>
+<h5>6.2.1.6 <a name="team-rep-ig" id="team-rep-ig">Team Representative in an
+Interest Group</a></h5>
+<p>When the participation requirements exceed <a href="#ig-mail-only">Interest
+Group mailing list subscription</a>, an individual is a Team representative in
+an Interest Group when so designated by W3C management.</p>
+<h5>6.2.1.7 <a name="good-standing" id="good-standing">Good Standing in a
+Working Group</a></h5>
+<p>Participation by an individual in a Working Group on an ongoing basis
+implies a serious commitment to the charter, including all of the
+following:</p>
+<ul>
+<li>attending most meetings of the Working Group.</li>
+<li>providing deliverables or drafts of deliverables in a timely fashion.</li>
+<li>being familiar with the relevant documents of the Working Group, including
+minutes of past meetings.</li>
+<li>following discussions on relevant mailing list(s).</li>
+</ul>
+<p>At the first Working Group meeting that follows any <a href="#cfp">Call for
+Participation</a>, all participants are in Good Standing. If a Member or
+Invited Expert joins the Working Group after the end of that meeting, the
+Member Representative or Invited Expert does not attain Good Standing until the
+start of the second consecutive meeting that individual attends.</p>
+<p>When the Chair and the <a href="#TeamContact">Team Contact</a> agree, the
+Chair <span class="rfc2119">MAY</span> declare that a participant is no longer
+in Good Standing (henceforth called "Bad Standing"). If there is disagreement
+between the Chair and the Team Contact about standing, the Director determines
+the participant's standing. The Chair <span class="rfc2119">MAY</span> declare
+a Team participant to be in Bad Standing, but it is clearly preferable for the
+Chair, Team participant, and W3C management to resolve issues internally.</p>
+<p>A participant <span class="rfc2119">MAY</span> be declared in Bad Standing
+in any of the following circumstances:</p>
+<ul>
+<li>the individual has missed more than one of the last three <a href=
+"policies.html#distributed-meeting">distributed meetings</a>.</li>
+<li>the individual has missed more than one of the last three <a href=
+"policies.html#ftf-meeting">face-to-face meetings</a>.</li>
+<li>the individual has not provided deliverables in a timely fashion twice in
+sequence.</li>
+<li>the individual has not followed the <a href="policies.html#coi">conflict of
+interest policy</a> by disclosing information to the rest of the group.</li>
+</ul>
+<p>Although all participants representing an organization <span class=
+"rfc2119">SHOULD</span> attend all meetings, attendance by one representative
+of an organization satisfies the meeting attendance requirement for all
+representatives of the organization.</p>
+<p>The above criteria <span class="rfc2119">MAY</span> be relaxed if the Chair
+and Team Contact agree that doing so will not set back the Working Group. For
+example, the attendance requirement can be relaxed for reasons of expense
+(e.g., cost of travel) or scheduling (for example, an exceptional
+teleconference is scheduled at 3:00 a.m. local time for the participant). It is
+the responsibility of the Chair and Team Contact to apply criteria for Good
+Standing consistently.</p>
+<p>When a participant risks losing Good Standing, the Chair and Team Contact
+are expected to discuss the matter with the participant and the participant's
+Advisory Committee representative (or W3C management for the Team) before
+declaring the participant in Bad Standing.</p>
+<p>The Chair declares a participant in Bad Standing by informing the
+participant's Advisory Committee representative and the participant of the
+decision. If the Advisory Committee representative and Chair differ in opinion,
+the Advisory Committee representative <span class="rfc2119">MAY</span> ask the
+<a href="organization.html#def-Director">Director</a> to confirm or deny the
+decision. <a href="#invited-expert-wg">Invited Experts</a> declared in Bad
+Standing <span class="rfc2119">MAY</span> appeal to the Director.</p>
+<p>The Chair and Team Contact restore Good Standing and <span class=
+"rfc2119">SHOULD</span> do so when the individual in Bad Standing satisfies the
+above criteria. The Chair <span class="rfc2119">MUST</span> inform the
+individual's Advisory Committee representative of any change in standing.</p>
+<p>When a Member representative permanently replaces another (i.e., is not
+simply a temporary <a href="#mtg-substitute">substitute</a>), the new
+participant inherits the standing of the departing participant.</p>
+<p>Changes in an individual's standing in a Working Group have no effect on the
+obligations associated with Working Group participation that are described in
+the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
+[<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
+<p><strong>Note:</strong> In general, the time commitment for participating in
+an Interest Group is less than that for a Working Group; see the section on
+<a href="#ig-charter-participation">participation provisions in an Interest
+Group charter</a>.</p>
+<h4>6.2.2 <a name="WGCharterDevelopment" id="WGCharterDevelopment">Working
+Group and Interest Group Charter Development</a></h4>
+<p>The Team <span class="rfc2119">MUST</span> notify the Advisory Committee
+when a charter for a new Working Group or Interest Group is in development. The
+suggestions for building support around an <a href=
+"activities.html#ActivityDevelopment">Activity Proposal</a> apply to charters
+as well.</p>
+<p>W3C <span class="rfc2119">MAY</span> begin work on a Working Group or
+Interest Group charter at any time. A Working Group or Interest Group
+<span class="rfc2119">MUST</span> be part of an approved <a href=
+"activities.html#def-Activity">Activity</a>.</p>
+<h4>6.2.3 <a name="CharterReview" id="CharterReview">Advisory Committee
+Review</a> of a Working Group or Interest Group Charter</h4>
+<p>The Director <span class="rfc2119">MUST</span> solicit <a href=
+"acreview.html#ReviewAppeal">Advisory Committee review</a> of every new or
+substantively modified Working Group or Interest Group charter. The Director is
+<span class="rfc2119">NOT REQUIRED</span> to solicit Advisory Committee review
+prior to a charter extension or for minor changes.</p>
+<p>The Director's Call for Review of a substantively modified charter
+<span class="rfc2119">MUST</span> highlight important changes (e.g., regarding
+deliverables or resource allocation) and include rationale for the changes.</p>
+<h4>6.2.4 <a name="cfp" id="cfp">Call for Participation in a Working Group or
+Interest Group</a></h4>
+<p>After Advisory Committee review of a Working Group or Interest Group
+charter, the Director <span class="rfc2119">MAY</span> issue a Call for
+Participation to the Advisory Committee. For a new group, this announcement
+officially creates the group. The announcement <span class=
+"rfc2119">MUST</span> include a reference to the <a href=
+"#WGCharter">charter</a>, the name(s) of the group's <a href=
+"#GeneralChairs">Chair(s)</a>, and the name of the <a href="#TeamContact">Team
+Contact</a>.</p>
+<p>After a Call for Participation, any <a href=
+"policies.html#member-rep">Member representatives</a> and <a href=
+"#invited-expert-wg">Invited Experts</a> <span class="rfc2119">MUST</span> be
+designated (or re-designated).</p>
+<p>Advisory Committee representatives <span class="rfc2119">MAY</span> <a href=
+"acreview.html#ACAppeal">appeal</a> creation or substantive modification of a
+Working Group or Interest Group charter.</p>
+<h4>6.2.5 <a name="charter-extension" id="charter-extension">Working Group and
+Interest Group Charter Extension</a></h4>
+<p>To extend a Working Group or Interest Group charter with no other
+substantive modifications, the Director announces the extension to the Advisory
+Committee. The announcement <span class="rfc2119">MUST</span> indicate the new
+duration, which <span class="rfc2119">MUST NOT</span> exceed the duration of
+the Activity to which the group belongs. The announcement <span class=
+"rfc2119">MUST</span> also include rationale for the extension, a reference to
+the <a href="#WGCharter">charter</a>, the name(s) of the group's <a href=
+"#GeneralChairs">Chair(s)</a>, the name of the <a href="#TeamContact">Team
+Contact</a>, and instructions for joining the group.</p>
+<p>After a charter extension, Advisory Committee representatives and the Chair
+are <span class="rfc2119">NOT REQUIRED</span> to re-designate <a href=
+"policies.html#member-rep">Member representatives</a> and <a href=
+"#invited-expert-wg">Invited Experts</a>.</p>
+<p>Advisory Committee representatives <span class="rfc2119">MAY</span> <a href=
+"acreview.html#ACAppeal">appeal</a> the extension of a Working Group or
+Interest Group charter.</p>
+<h4>6.2.6 <a name="WGCharter" id="WGCharter">Working Group and Interest Group
+Charters</a></h4>
+<p>A Working Group or Interest Group charter <span class="rfc2119">MUST</span>
+include all of the following information.</p>
+<ul>
+<li>The group's mission (e.g., develop a technology or process, review the work
+of other groups);</li>
+<li>The scope of the group's work and criteria for success;</li>
+<li>The duration of the group (typically from six months to two years);</li>
+<li>The nature of any deliverables (technical reports, reviews of the
+deliverables of other groups, or software), expected milestones, and the
+process for the group participants to approve the release of these deliverables
+(including public intermediate results). A charter is <span class="rfc2119">NOT
+REQUIRED</span> to include the schedule for a review of another group's
+deliverables;</li>
+<li>Any dependencies by groups within or outside of W3C on the deliverables of
+this group. For any dependencies, the charter <span class="rfc2119">MUST</span>
+specify the mechanisms for communication about the deliverables;</li>
+<li>Any dependencies of this group on other groups within or outside of W3C.
+For example, one group's charter might specify that another group is expected
+to review a technical report before it can become a Recommendation. For any
+dependencies, the charter <span class="rfc2119">MUST</span> specify when
+required deliverables are expected from the other groups. The charter
+<span class="rfc2119">SHOULD</span> set expectations about how coordination
+with those groups will take place; see the section on <a href=
+"liaisons.html#Liaisons">liaisons with other organizations</a>. Finally, the
+charter <span class="rfc2119">SHOULD</span> specify expected conformance to the
+deliverables of the other groups;</li>
+<li>The <a href="comm.html#confidentiality-levels">level of confidentiality</a>
+of the group's proceedings and deliverables;</li>
+<li>Meeting mechanisms and expected frequency;</li>
+<li>Communication mechanisms to be employed within the group, between the group
+and the rest of W3C, and with the general public;</li>
+<li>An estimate of the expected time commitment from participants;</li>
+<li>The expected time commitment and level of involvement by the Team (e.g., to
+track developments, write and edit technical reports, develop code, or organize
+pilot experiments).</li>
+</ul>
+<p>See also the charter requirements of <a href=
+"http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section 2</a> and
+<a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
+Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
+<p id="ig-charter-participation">An Interest Group charter <span class=
+"rfc2119">MAY</span> include provisions regarding participation, including
+specifying that the <a name="ig-mail-only" id="ig-mail-only">only requirement
+for participation (by anyone) in the Interest Group</a> is subscription to the
+Interest Group mailing list. This type of Interest Group <span class=
+"rfc2119">MAY</span> have <a href="#public-participant-ig">public
+participants</a>.</p>
+<p>A charter <span class="rfc2119">MAY</span> include additional voting
+procedures, but those procedures <span class="rfc2119">MUST NOT</span> conflict
+with the <a href="policies.html#Votes">voting requirements</a> of the Process
+Document.</p>
+<p>A charter <span class="rfc2119">MAY</span> include provisions other than
+those required by this document. The charter <span class=
+"rfc2119">SHOULD</span> highlight whether additional provisions impose
+constraints beyond those of the W3C Process Document (e.g., limits on the
+number of individuals in a Working Group who represent the same Member
+organization or group of <a href="organization.html#MemberRelated">related
+Members</a>).</p>
+<h4>6.2.7 <a name="three-month-rule" id="three-month-rule">Working Group
+"Heartbeat" Requirement</a></h4>
+<p>It is important that a Working Group keep the Membership and public informed
+of its activity and progress. To this end, each Working Group <span class=
+"rfc2119">SHOULD</span> publish in the <a href="http://www.w3.org/TR/">W3C
+technical reports index</a> a new draft of <em>each active technical
+report</em> at least once every three months. An active technical report is a
+Working Draft, Candidate Recommendation, Proposed Recommendation, or Proposed
+Edited Recommendation. Each Working Group <span class="rfc2119">MUST</span>
+publish a new draft of <em>at least one of its active technical reports</em> on
+the <a href="http://www.w3.org/TR/">W3C technical reports index</a> [<a href=
+"refs.html#ref-doc-list">PUB11</a>] at least once every three months.</p>
+<p>Public progress reports are also important when a Working Group does not
+update a technical report within three months (for example, when the delay is
+due to a challenging technical issue) or when a Working Group has no active
+technical reports (for example, because it is developing a test suite).</p>
+<p>In exceptional cases, the Chair <span class="rfc2119">MAY</span> ask the
+Director to be excused from this publication requirement. However, in this
+case, the Working Group <span class="rfc2119">MUST</span> issue a public status
+report with rationale why a new draft has not been published.</p>
+<p>There are several reasons for this Working Group "heartbeat"
+requirement:</p>
+<ul>
+<li>To promote public accountability;</li>
+<li>To encourage Working Groups to keep moving forward, and to incorporate
+their decisions into readable public documents. People cannot be expected to
+read several months of a group's mailing list archive to understand where the
+group stands;</li>
+<li>To notify interested parties of updated work in familiar a place such as
+the W3C home page and index of technical reports.</li>
+</ul>
+<p>As an example, suppose a Working Group has one technical report as a
+deliverable, which it publishes as a Proposed Recommendation. Per the heartbeat
+requirement, the Working Group is required to publish a new draft of the
+Proposed Recommendation at least once every three months, even if it is only to
+revise the status of the Proposed Recommendation document (e.g., to provide an
+update on the status of the decision to advance). The heartbeat requirement
+stops when the document becomes a Recommendation (or a Working Group Note).</p>
+<h4>6.2.8 <a name="GeneralTermination" id="GeneralTermination">Working Group
+and Interest Group Closure</a></h4>
+<p>A Working Group or Interest Group charter specifies a duration for the
+group. The Director, subject to <a href="acreview.html#ACAppeal">appeal</a> by
+Advisory Committee representatives, <span class="rfc2119">MAY</span> close a
+group prior to the date specified in the charter in any of the following
+circumstances:</p>
+<ul>
+<li>There are insufficient resources to produce chartered deliverables or to
+maintain the group, according to priorities established within W3C.</li>
+<li>The group produces chartered deliverables ahead of schedule.</li>
+<li>The Activity to which the group belongs terminates.</li>
+</ul>
+<p>The Director closes a Working Group or Interest Group by announcement to the
+Advisory Committee.</p>
+<p>Closing a Working Group has implications with respect to the <a href=
+"http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href=
+"refs.html#ref-patentpolicy">PUB33</a>].</p>
+<h3>6.3 <a name="GroupsCG" id="GroupsCG">Coordination Groups</a></h3>
+<p>W3C Activities interact in many ways. There are dependencies between groups
+within the same Activity or in different Activities. There are also
+dependencies between W3C Activities and the activities of other organizations.
+Examples of dependencies include the use by one technology of another being
+developed elsewhere, scheduling constraints between groups, and the
+synchronization of publicity for the announcement of deliverables. Coordination
+Groups are created to manage dependencies so that issues are resolved fairly
+and the solutions are consistent with W3C's mission and results.</p>
+<p>Where a Coordination Group's scope covers two groups with unresolved
+disputes or tensions, it is the first locus of resolution of these
+disputes.</p>
+<h4>6.3.1 <a name="CGParticipation" id="CGParticipation">Coordination Group
+Participation Requirements</a></h4>
+<p>There are four types <a name="cgparticipant" id="cgparticipant">participants
+in a Coordination Group</a>: the <a href="#GeneralChairs">Chair</a>, the Chair
+of each coordinated group (to promote effective communication among the
+groups), Invited Experts (e.g., liaisons to groups inside or outside W3C), and
+Team representatives (including the <a href="#TeamContact">Team Contact</a>).
+The requirements for Invited Expert participation are the same as for an
+<a href="#invited-expert-wg">Invited Expert in a Working Group</a>.</p>
+<p>Coordination Group participants <span class="rfc2119">MUST</span> follow the
+<a href="policies.html#coi">conflict of interest policy</a> by disclosing
+information to the rest of the group.</p>
+<p>There are no Good Standing requirements for Coordination Group
+participation; regular participation in a relevant Coordination Group is one of
+the <a href="/Guide/chair-roles">roles of a group Chair [MEM14]</a>.</p>
+<h4>6.3.2 <a name="CGCreation" id="CGCreation">Coordination Group Creation and
+Closure</a></h4>
+<p>The Director creates or modifies a Coordination Group by sending the
+<a href="#CGCharter">Coordination Group charter</a> to the Advisory Committee.
+A Coordination Group <span class="rfc2119">MAY</span> be created as part of an
+<a href="activities.html#ActivityProposal">Activity Proposal</a> (for example
+to coordinate other groups in the Activity or to draw up charters of future
+groups), or during the life of an Activity when dependencies arise. A
+Coordination Group <span class="rfc2119">MAY</span> operate as part of several
+W3C Activities.</p>
+<p>A Coordination Group <span class="rfc2119">SHOULD</span> close when there is
+no longer a perceived need for coordination.</p>
+<h4>6.3.3 <a name="CGCharter" id="CGCharter">Coordination Group
+Charters</a></h4>
+<p>A Coordination Group charter <span class="rfc2119">MUST</span> include all
+of the following information:</p>
+<ul>
+<li>The group's mission;</li>
+<li>The scope of the group's work, including the names of coordinated groups
+and contact information for those groups;</li>
+<li>Any dependencies by groups within or outside of W3C on this group;</li>
+<li>Any dependencies of this group on other groups within or outside of W3C;
+see the section on <a href="liaisons.html#Liaisons">liaisons with other
+organizations</a>.</li>
+<li>The <a href="comm.html#confidentiality-levels">level of confidentiality</a>
+of the group's proceedings;</li>
+<li>Meeting mechanisms and expected frequency;</li>
+<li>Communication mechanisms to be employed within the group, between the group
+and the rest of W3C, and with the general public;</li>
+<li>An estimate of the expected time commitment from participants;</li>
+<li>The expected level of involvement by the Team.</li>
+</ul>
+<p>A charter <span class="rfc2119">MAY</span> include additional voting
+procedures, but those procedures <span class="rfc2119">MUST NOT</span> conflict
+with the <a href="policies.html#Votes">voting requirements</a> of the Process
+Document.</p>
+<p>A charter <span class="rfc2119">MAY</span> include provisions other than
+those required by this document. The charter <span class=
+"rfc2119">SHOULD</span> highlight whether additional provisions impose
+constraints beyond those of the W3C Process Document.</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="tr.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="activities.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/liaisons.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,60 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>10 Liaisons</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="submission.html" />
+<link rel="previous" href="events.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="submission.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="events.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>10 <a name="Liaisons" id="Liaisons">Liaisons</a></h2>
+<div class="toc"></div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>W3C uses the term "liaison" to refer to coordination of activities with a
+variety of organizations, through a number of mechanisms ranging from very
+informal (e.g., an individual from another organization participates in a W3C
+Working Group, or just follows its work) to mutual membership, to even more
+formal agreements. Liaisons are not meant to substitute for W3C membership.</p>
+<p>All liaisons <span class="rfc2119">MUST</span> be coordinated by the Team
+due to requirements for public communication; patent, copyright, and other IPR
+policies; confidentiality agreements; and mutual membership agreements.</p>
+<p>The W3C Director <span class="rfc2119">MAY</span> negotiate and sign a
+<a name="mou" id="mou">Memorandum of Understanding (<acronym>MoU</acronym>)</a>
+with another organization. Before signing the MoU, the Team <span class=
+"rfc2119">MUST</span> inform the Advisory Committee of the intent to sign and
+make the MoU available for Advisory Committee review; the Advisory Committee
+<span class="rfc2119">MAY</span> <a href="acreview.html#ACAppeal">appeal</a>.
+Once approved, a Memorandum of Understanding <span class=
+"rfc2119">SHOULD</span> be made public.</p>
+<p>Information about <a href="http://www.w3.org/2001/11/StdLiaison">W3C
+liaisons with other organizations</a> and the guidelines W3C follows when
+creating a liaison [<a href="refs.html#ref-liaison-list">PUB28</a>] is
+available on the Web.</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="submission.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="events.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/organization.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,591 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>2 Members, Advisory Committee, Team, Advisory Board, Technical
+Architecture Group</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="policies.html" />
+<link rel="previous" href="intro.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="policies.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="intro.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>2 <a name="Organization" id="Organization">Members, Advisory Committee,
+Team, Advisory Board, Technical Architecture Group</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#Members" class="tocxref">2.1 Members</a>
+<ul class="toc">
+<li class="tocline4"><a href="#MemberBenefits" class="tocxref">2.1.1 Rights of
+Members</a></li>
+<li class="tocline4"><a href="#MemberRelated" class="tocxref">2.1.2 Related
+Members</a></li>
+<li class="tocline4"><a href="#AC" class="tocxref">2.1.3 Advisory Committee
+(AC)</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#Team" class="tocxref">2.2 The W3C Team</a>
+<ul class="toc">
+<li class="tocline4"><a href="#TeamSubmission" class="tocxref">2.2.1 Team
+Submissions</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#AB" class="tocxref">2.3 Advisory Board (AB)</a>
+<ul class="toc">
+<li class="tocline4"><a href="#ABParticipation" class="tocxref">2.3.1 Advisory
+Board Participation</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#TAG" class="tocxref">2.4 Technical Architecture
+Group (TAG)</a>
+<ul class="toc">
+<li class="tocline4"><a href="#tag-participation" class="tocxref">2.4.1
+Technical Architecture Group Participation</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#AB-TAG-participation" class="tocxref">2.5
+Advisory Board and Technical Architecture Group Participation</a>
+<ul class="toc">
+<li class="tocline4"><a href="#AB-TAG-constraints" class="tocxref">2.5.1
+Advisory Board and Technical Architecture Group Participation
+Constraints</a></li>
+<li class="tocline4"><a href="#AB-TAG-elections" class="tocxref">2.5.2 Advisory
+Board and Technical Architecture Group Elections</a></li>
+<li class="tocline4"><a href="#AB-TAG-vacated" class="tocxref">2.5.3 Advisory
+Board and Technical Architecture Group Vacated Seats</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>W3C's mission is to lead the Web to its full potential. W3C <a href=
+"#Members">Member</a> organizations provide resources to this end, and the W3C
+<a href="#Team">Team</a> provides the technical leadership and organization to
+coordinate the effort.</p>
+<h3>2.1 <a name="Members" id="Members">Members</a></h3>
+<p>W3C Members are primarily represented in W3C processes as follows:</p>
+<ol>
+<li>The <a href="#AC">Advisory Committee</a> is composed of one representative
+from each Member organization (refer to the <a href=
+"comm.html#Member-only">Member-only</a> list of <a href=
+"http://www.w3.org/Member/ACList">current Advisory Committee
+representatives</a> [<a href="refs.html#ref-current-ac">MEM1</a>]). The
+Advisory Committee:
+<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=
+"activities.html#ActivityProposal">Activity Proposals</a>, <a href=
+"tr.html#RecsPR">Proposed Recommendations</a>, and <a href=
+"processdoc.html#GAProcess">Proposed Process Documents</a>.</li>
+<li>elects the <a href="#AB">Advisory Board</a> participants other than the
+Advisory Board Chair.</li>
+<li>elects 5 of the 9 participants on the <a href="#TAG">Technical Architecture
+Group</a>.</li>
+</ul>
+Advisory Committee representatives have <a href=
+"acreview.html#ACAppeal">appeal</a> powers for some processes described in this
+document.</li>
+<li>Representatives of Member organizations participate in <a href=
+"groups.html#GAGeneral">Working Groups, Interest Groups, and Coordination
+Groups</a> and author and review <a href="#Recs">technical reports</a>.</li>
+</ol>
+<p><a name="MemberSubscription" id="MemberSubscription">W3C membership</a> is
+open to all entities, as described in "<a href=
+"http://www.w3.org/Consortium/join">How to Join W3C</a>" [<a href=
+"refs.html#ref-join-w3c">PUB5</a>]; (refer to the public list of <a href=
+"http://www.w3.org/Consortium/Member/List">current W3C Members</a> [<a href=
+"refs.html#ref-current-mem">PUB8</a>]). Organizations subscribe according to
+the <a href=
+"http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+Agreement</a> [<a href="refs.html#ref-member-agreement">PUB6</a>]. The <a href=
+"#Team">Team</a> <span class="rfc2119">MUST</span> ensure that Member
+participation agreements remain <a href="comm.html#Team-only">Team-only</a> and
+that no Member receives preferential treatment within W3C.</p>
+<p><a name="IndividualParticipation" id="IndividualParticipation">W3C does not
+have a class of membership tailored to, or priced for individuals</a>. However,
+an individual <span class="rfc2119">MAY</span> join W3C as an Affiliate Member.
+In this case the same restrictions pertaining to <a href=
+"#MemberRelated">related Members</a> apply when the individual also <a href=
+"policies.html#member-rep">represents</a> another W3C Member.</p>
+<h4>2.1.1 <a name="MemberBenefits" id="MemberBenefits">Rights of
+Members</a></h4>
+<p>Each Member organization enjoys the following rights and benefits:</p>
+<ul>
+<li>A seat on the <a href="#AC">Advisory Committee</a>;</li>
+<li>Access to <a href="comm.html#Member-only">Member-only</a> information;</li>
+<li>The <a href="submission.html#Submission">Member Submission</a>
+process;</li>
+<li>Use of the W3C Member logo on promotional material and to publicize the
+Member's participation in W3C. For more information, please refer to the Member
+logo usage policy described in the <a href="http://www.w3.org/Member/Intro">New
+Member Orientation</a> [<a href="refs.html#ref-new-member">MEM4</a>].</li>
+</ul>
+<p>Furthermore, representatives of Member organizations participate in W3C as
+follows:</p>
+<ul>
+<li>In <a href="groups.html#GAGeneral">Working Groups, Interest Groups, and
+Coordination Groups</a>.</li>
+<li>In <a href="events.html#GAEvents">Workshops and Symposia</a>;</li>
+<li>On the Team, as <a href="#fellows">W3C Fellows</a>.</li>
+</ul>
+<p>In the case (described in paragraph 5g of the <a href=
+"http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+Agreement</a>), where a Member organization is itself a consortium, user
+society, or otherwise has members or sponsors, the organization's paid staff
+and Advisory Committee representative exercise all the rights and privileges of
+W3C membership. In addition, the Advisory Committee representative <span class=
+"rfc2119">MAY</span> designate up to four (or more at the Team's discretion)
+individuals who, though not employed by the organization, <span class=
+"rfc2119">MAY</span> exercise the rights of <a href=
+"policies.html#member-rep">Member representatives</a>. These individuals
+<span class="rfc2119">MUST</span> disclose their employment affiliation when
+participating in W3C work. Provisions for <a href="#MemberRelated">related
+Members</a> apply. Furthermore, these individuals are expected to represent the
+broad interests of the W3C Member organization and not the parochial interests
+of their employers.</p>
+<p>The rights and benefits of W3C membership are contingent upon conformance to
+the processes described in this document. The vast majority of W3C Members
+faithfully follow the spirit as well as the letter of these processes. When
+serious and/or repeated violations do occur, and repeated attempts to address
+these violations have not resolved the situation, the Director <span class=
+"rfc2119">MAY</span> take disciplinary action. Arbitration in the case of
+further disagreement is governed by paragraph 19 of the Membership Agreement.
+Refer to the <a href="http://www.w3.org/2002/09/discipline">Guidelines for
+Disciplinary Action</a> [<a href="refs.html#ref-discipline-gl">MEM14</a>].</p>
+<h4>2.1.2 <a name="MemberRelated" id="MemberRelated">Related Members</a></h4>
+<p>In the interest of ensuring the integrity of the consensus process, Member
+involvement in some of the processes in this document is affected by related
+Member status. As used herein, two Members are related if:</p>
+<ol>
+<li>Either Member is a subsidiary of the other, or</li>
+<li>Both Members are subsidiaries of a common entity, or</li>
+<li>The Members have an employment contract or consulting contract that affects
+W3C participation.</li>
+</ol>
+<p>A <em>subsidiary</em> is an organization of which effective control and/or
+majority ownership rests with another, single organization.</p>
+<p>Related Members <span class="rfc2119">MUST</span> disclose these
+relationships according to the mechanisms described in the <a href=
+"http://www.w3.org/Member/Intro">New Member Orientation</a> [<a href=
+"refs.html#ref-new-member">MEM4</a>].</p>
+<h4>2.1.3 <a name="AC" id="AC">Advisory Committee (AC)</a></h4>
+<p>When an organization joins W3C (see "<a href=
+"http://www.w3.org/Consortium/join">How to Join W3C</a>" [<a href=
+"refs.html#ref-join-w3c">PUB5</a>]), it <span class="rfc2119">MUST</span> name
+its Advisory Committee representative as part of the Membership Agreement. The
+<a href="http://www.w3.org/Member/Intro">New Member Orientation</a> explains
+how to subscribe or unsubscribe to Advisory Committee mailing lists, provides
+information about Advisory Committee meetings, explains how to name a new
+Advisory Committee representative, and more. Advisory Committee representatives
+<span class="rfc2119">MUST</span> follow the <a href=
+"policies.html#coi">conflict of interest policy</a> by disclosing information
+according to the mechanisms described in the New Member Orientation. See also
+the additional roles of Advisory Committee representatives described in the
+<a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
+[<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
+<p>Additional information for Members is available at the <a href=
+"http://www.w3.org/Member/">Member Web site</a> [<a href=
+"refs.html#ref-member-web">MEM6</a>].</p>
+<h5>2.1.3.1 <a name="ACCommunication" id="ACCommunication">Advisory Committee
+Mailing Lists</a></h5>
+<p>The Team <span class="rfc2119">MUST</span> provide two mailing lists for use
+by the Advisory Committee:</p>
+<ol>
+<li>One for official announcements (e.g., those required by this document) from
+the Team to the Advisory Committee. This list is read-only for Advisory
+Committee representatives.</li>
+<li>One for discussion among Advisory Committee representatives. Though this
+list is primarily for Advisory Committee representatives, the Team <span class=
+"rfc2119">MUST</span> monitor discussion and <span class=
+"rfc2119">SHOULD</span> participate in discussion when appropriate. Ongoing
+detailed discussions <span class="rfc2119">SHOULD</span> be moved to other
+appropriate lists (new or existing, such as a mailing list created for a
+<a href="events.html#GAEvents">Workshop</a>).</li>
+</ol>
+<p>An Advisory Committee representative <span class="rfc2119">MAY</span>
+request that additional individuals from their organization be subscribed to
+these lists. Failure to contain distribution internally <span class=
+"rfc2119">MAY</span> result in suspension of additional email addresses, at the
+discretion of the Team.</p>
+<h5>2.1.3.2 <a name="ACMeetings" id="ACMeetings">Advisory Committee
+Meetings</a></h5>
+<p>The Team organizes a <a href="policies.html#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">W3C Chair</a> or <a href="#def-COO">Chief Operating
+Officer</a>). At each Advisory Committee meeting, the Team <span class=
+"rfc2119">SHOULD</span> provide an update to the Advisory Committee about:</p>
+<dl>
+<dt><em>Resources</em></dt>
+<dd>
+<ul>
+<li>The number of Full and Affiliate W3C Members.</li>
+<li>An overview of the financial status of W3C.</li>
+</ul>
+</dd>
+<dt><em>Allocations</em></dt>
+<dd>
+<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>The allocation of resources to pursuing <a href=
+"liaisons.html#Liaisons">liaisons</a> with other organizations.</li>
+</ul>
+</dd>
+</dl>
+<p>Each Member organization <span class="rfc2119">SHOULD</span> send one
+<a href="policies.html#member-rep">representative</a> to each Advisory
+Committee meeting. In exceptional circumstances (e.g., during a period of
+transition between representatives from an organization), the meeting Chair
+<span class="rfc2119">MAY</span> allow a Member organization to send two
+representatives to a meeting.</p>
+<p>The Team <span class="rfc2119">MUST</span> announce the date and location of
+each Advisory Committee meeting no later than at the end of the previous
+meeting; <span class="time-interval">one year's</span> notice is preferred. The
+Team <span class="rfc2119">MUST</span> announce the region of each Advisory
+Committee meeting at least <span class="time-interval">one year</span> in
+advance.</p>
+<p>More information about <a href="http://www.w3.org/Member/Meeting/">Advisory
+Committee meetings</a> [<a href="refs.html#ref-ac-meetings">MEM5</a>] is
+available at the Member Web site.</p>
+<h3>2.2 <a name="Team" id="Team">The W3C Team</a></h3>
+<p>The Team consists of the W3C paid staff, unpaid interns, and W3C Fellows.
+<a name="fellows" id="fellows">W3C Fellows</a> are Member employees working as
+part of the Team; see the <a href=
+"http://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a>
+[<a href="refs.html#ref-fellows">PUB32</a>]. The Team provides technical
+leadership about Web technologies, organizes and 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 Officer.
+These individuals <span class="rfc2119">MAY</span> delegate responsibility
+(generally to other individuals in the Team) for any of their roles described
+in this document.</p>
+<p>The <a name="def-Director" id="def-Director">Director</a> is the lead
+technical architect at W3C and as such, is responsible for assessing <a name=
+"DirectorDecision" href="policies.html#def-Consensus" id=
+"DirectorDecision">consensus</a> within W3C for architectural choices,
+publication of <a href="tr.html#Reports">technical reports</a>, and new
+<a href="activities.html#Activities">Activities</a>. The Director appoints
+group <a href="groups.html#GeneralChairs">Chairs</a> and has the role of
+"tie-breaker" for questions of <a href="groups.html#good-standing">Good
+Standing</a> in a Working Group or <a href="policies.html#WGAppeals">appeal of
+a Working Group decision</a>. The Director is generally Chair of the <a href=
+"#TAG">TAG</a>.</p>
+<p>The <a name="def-W3CChair" id="def-W3CChair">W3C Chair</a> leads Member
+relations, and <a href="liaisons.html#Liaisons">liaisons</a> with other
+organizations, governments, and the public.</p>
+<p>The <a name="def-COO" id="def-COO">Chief Operating Officer</a>
+(<acronym>COO</acronym>) leads the operation of W3C as an organization: a
+collection of people, <a href="#hosts">Host institutions</a>, and
+processes.</p>
+<p>Team administrative information such as Team salaries, detailed budgeting,
+and other business decisions are <a href="comm.html#Team-only">Team-only</a>,
+subject to oversight by the Host institutions.</p>
+<p><strong>Note:</strong> W3C is not currently incorporated. For legal
+contracts, W3C is represented by three <a name="hosts" id="hosts">"Host"
+institutions</a>: the European Research Consortium for Informatics and
+Mathematics (<acronym>ERCIM</acronym>), Keio University, and the Massachusetts
+Institute of Technology (<acronym>MIT</acronym>). Within W3C, the Host
+institutions are governed by joint sponsorship contracts; the Hosts themselves
+are not W3C Members.</p>
+<h4>2.2.1 <a name="TeamSubmission" id="TeamSubmission">Team
+Submissions</a></h4>
+<p>Team members <span class="rfc2119">MAY</span> request that the Director
+publish information at the W3C Web site. At the Director's discretion, these
+documents are published as "Team Submissions". These documents are analogous to
+<a href="submission.html#Submission">Member Submissions</a> (e.g., in <a href=
+"submission.html#SubmissionScope">expected scope</a>). However, there is no
+additional Team comment. The <a href="tr.html#DocumentStatus">document status
+section</a> of a Team Submission indicates the level of Team consensus about
+the published material.</p>
+<p>Team Submissions are <strong>not</strong> part of the <a href=
+"tr.html#Reports">technical report development process</a>.</p>
+<p>The list of <a href="http://www.w3.org/TeamSubmission/">published Team
+Submissions</a> [<a href="refs.html#ref-team-submission-list">PUB16</a>] is
+available at the W3C Web site.</p>
+<h3>2.3 <a name="AB" id="AB">Advisory Board (AB)</a></h3>
+<p>Created in March 1998, the Advisory Board provides ongoing guidance to the
+Team on issues of strategy, management, legal matters, process, and conflict
+resolution. The Advisory Board also serves the Members by tracking issues
+raised between Advisory Committee meetings, soliciting Member comments on such
+issues, and proposing actions to resolve these issues. The Advisory Board
+manages the <a href="processdoc.html#GAProcess">evolution of the Process
+Document</a>. The Advisory Board hears appeals of <a href=
+"submission.html#SubmissionNo">Member Submission requests</a> that are rejected
+for reasons unrelated to Web architecture; see also the <a href=
+"#TAG">TAG</a>.</p>
+<p>The Advisory Board is <strong>not</strong> a board of directors and has no
+decision-making authority within W3C; its role is strictly advisory.</p>
+<p>The Team <span class="rfc2119">MUST</span> make available a mailing list for
+the Advisory Board to use for its communication, confidential to the Advisory
+Board and Team.</p>
+<p>The Advisory Board <span class="rfc2119">SHOULD</span> send a summary of
+each of its meetings to the Advisory Committee and other group Chairs. The
+Advisory Board <span class="rfc2119">SHOULD</span> also report on its
+activities at each <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
+<p>Details about the Advisory Board (e.g., the list of Advisory Board
+participants, mailing list information, and summaries of Advisory Board
+meetings) are available at the <a href="http://www.w3.org/2002/ab/">Advisory
+Board home page</a> [<a href="refs.html#ref-ab-home">PUB30</a>].</p>
+<h4>2.3.1 <a name="ABParticipation" id="ABParticipation">Advisory Board
+Participation</a></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">W3C Chair</a>.</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>. Terms are
+staggered so that each year, either four or five terms expire. If an individual
+is elected to fill an incomplete term, 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 June.</p>
+<h3>2.4 <a name="TAG" id="TAG">Technical Architecture Group (TAG)</a></h3>
+<p>Created in February 2001, the mission of the TAG is stewardship of the Web
+architecture. There are three aspects to this mission:</p>
+<ol>
+<li>to document and build consensus around principles of Web architecture and
+to interpret and clarify these principles when necessary;</li>
+<li>to resolve issues involving general Web architecture brought to the
+TAG;</li>
+<li>to help coordinate cross-technology architecture developments inside and
+outside W3C.</li>
+</ol>
+<p>The TAG hears appeals of <a href="submission.html#SubmissionNo">Member
+Submission requests</a> that are rejected for reasons related to Web
+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 <span class="rfc2119">SHOULD NOT</span> 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=
+"refs.html#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 <span class="rfc2119">MUST</span> make available two mailing lists
+for the TAG:</p>
+<ul>
+<li>a public discussion (not just input) list for issues of Web architecture.
+The TAG will conduct its public business on this list.</li>
+<li>a <a href="comm.html#Member-only">Member-only</a> list for discussions
+within the TAG and for requests to the TAG that, for whatever reason, cannot be
+made on the public list.</li>
+</ul>
+<p>The TAG <span class="rfc2119">MAY</span> also request the creation of
+additional topic-specific, public mailing lists. For some TAG discussions
+(e.g., an appeal of a <a href="submission.html#SubmissionNo">rejected Member
+Submission request</a>), the TAG <span class="rfc2119">MAY</span> use a list
+that will be <a href="comm.html#Member-only">Member-only</a>.</p>
+<p>The TAG <span class="rfc2119">SHOULD</span> send a summary of each of its
+<a href="policies.html#GeneralMeetings">meetings</a> to the Advisory Committee
+and other group Chairs. The TAG <span class="rfc2119">SHOULD</span> 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="refs.html#ref-tag-charter">PUB25</a>] and the general section on
+<a href="policies.html#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=
+"refs.html#ref-tag-home">PUB26</a>].</p>
+<h4>2.4.1 <a id="tag-participation" name="tag-participation">Technical
+Architecture Group Participation</a></h4>
+<p>The TAG consists of eight elected or appointed participants and a Chair. The
+Team appoints the Chair of the TAG, who is generally the <a href=
+"#def-Director">Director</a>.</p>
+<p>Three TAG participants are appointed by the Director. Appointees are
+<span class="rfc2119">NOT REQUIRED</span> to be on the W3C Team. The Director
+<span class="rfc2119">MAY</span> appoint <a href="#fellows">W3C Fellows</a> to
+the TAG.</p>
+<p>The remaining five TAG 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 TAG participants are for
+<span class="time-interval">two years</span>. Terms are staggered so that each
+year, either two or three elected terms, and either one or two appointed terms
+expire. If an individual is appointed or elected to fill an incomplete term,
+that individual's term ends at the normal expiration date of that term. Regular
+TAG terms begin on 1 February and end on 31 January.</p>
+<h3>2.5 <a name="AB-TAG-participation" id="AB-TAG-participation">Advisory Board
+and Technical Architecture Group Participation</a></h3>
+<p>Advisory Board and TAG participants have a special role within W3C: they are
+elected by the Membership and appointed by the Director with the expectation
+that they will use their best judgment to find the best solutions for the Web,
+not just for any particular network, technology, vendor, or user. Advisory
+Board and TAG participants are expected to participate regularly and fully.
+<a href="groups.html#good-standing">Good Standing</a> rules as defined for
+Working Group participants also apply to Advisory Board and TAG participants.
+Advisory Board and TAG participants <span class="rfc2119">SHOULD</span> attend
+<a href="#ACMeetings">Advisory Committee meetings</a>.</p>
+<p>An individual participates on the Advisory Board or TAG from the moment the
+individual's term begins until the term ends or the seat is <a href=
+"#AB-TAG-vacated">vacated</a>. Although Advisory Board and TAG participants do
+not advocate for the commercial interests of their employers, their
+participation does carry the responsibilities associated with Member
+representation, Invited Expert status, or Team representation (as described in
+the section on the <a href="#AB-TAG-elections">AB/TAG nomination and election
+process</a>). See also the licensing obligations on TAG participants in
+<a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
+Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>], and the claim
+exclusion process of <a href=
+"http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
+<h4>2.5.1 <a id="AB-TAG-constraints" name="AB-TAG-constraints">Advisory Board
+and Technical Architecture Group Participation Constraints</a></h4>
+<p>Given the few seats available on the Advisory Board and the TAG, and in
+order to ensure that the diversity of W3C Members is represented:</p>
+<ul>
+<li>A Member organization is permitted at most one participant on the TAG.</li>
+<li>A Member organization is permitted at most one participant on the AB.</li>
+<li>An individual <span class="rfc2119">MUST NOT</span> participate on both the
+TAG and the AB.</li>
+</ul>
+<p>If, for whatever reason, these constraints are not satisfied (e.g., because
+a TAG or AB participant changes jobs), one participant <span class=
+"rfc2119">MUST</span> cease TAG or AB participation until the situation has
+been resolved. If after <span class="time-interval">30 days</span> the
+situation has not been resolved, the Chair will declare one participant's seat
+to be vacant. When more than one individual is involved, the <a href=
+"#random">verifiable random selection procedure</a> described below will be
+used to choose one person for continued participation.</p>
+<h4>2.5.2 <a id="AB-TAG-elections" name="AB-TAG-elections">Advisory Board and
+Technical Architecture Group Elections</a></h4>
+<p>The Advisory Board and a portion of the Technical Architecture Group are
+elected by the Advisory Committee. An election begins when the Team sends a
+Call for Nominations to the Advisory Committee. Any Call for Nominations
+specifies the number of available seats, the deadline for nominations, and the
+address where nominations are sent. The Director <span class=
+"rfc2119">SHOULD</span> announce appointments no later than the start of a
+nomination period, and generally as part of the Call for Nominations.</p>
+<p>Each Member (or group of <a href="#MemberRelated">related Members</a>)
+<span class="rfc2119">MAY</span> nominate one individual. A nomination
+<span class="rfc2119">MUST</span> be made with the consent of the nominee. In
+order for an individual to be nominated as a Member representative, the
+individual <span class="rfc2119">MUST</span> qualify for <a href=
+"policies.html#member-rep">Member representation</a> and the Member's Advisory
+Committee representative <span class="rfc2119">MUST</span> include in the
+nomination the (same) <a href="groups.html#member-rep-info">information
+required for a Member representative in a Working Group</a>. In order for an
+individual to be nominated as an Invited Expert, the individual <span class=
+"rfc2119">MUST</span> provide the (same) <a href=
+"groups.html#inv-expert-info">information required for an Invited Expert in a
+Working Group</a> and the nominating Advisory Committee representative
+<span class="rfc2119">MUST</span> include that information in the nomination.
+In order for an individual to be nominated as a Team representative, the
+nominating Advisory Committee representative <span class="rfc2119">MUST</span>
+first secure approval from Team management. A nominee is <span class=
+"rfc2119">NOT REQUIRED</span> to be an employee of a Member organization, and
+<span class="rfc2119">MAY</span> be a <a href="#fellows">W3C Fellow</a>. Each
+nomination <span class="rfc2119">SHOULD</span> include a few informative
+paragraphs about the nominee.</p>
+<p>If, after the deadline for nominations, the number of nominees is:</p>
+<ul>
+<li>Equal to the number of available seats, those nominees are thereby elected.
+This situation constitutes a tie for the purposes of assigning <a href=
+"#short-term">short terms</a>.</li>
+<li>Less than the number of available seats, Calls for Nominations are issued
+until a sufficient number of people have been nominated. Those already
+nominated do not need to be renominated after a renewed call.</li>
+<li>Greater than the number of available seats, the Team issues a Call for
+Votes that includes the names of all candidates, the number of available seats,
+the deadline for votes, and the address where votes are sent.</li>
+</ul>
+<p>When there is a vote, each Member (or group of <a href=
+"#MemberRelated">related Members</a>) <span class="rfc2119">MAY</span> vote for
+as many candidates as there are available seats; see the section on <a href=
+"acreview.html#ACVotes">Advisory Committee votes</a>. Once the deadline for
+votes has passed, the Team announces the results to the Advisory Committee. The
+candidates with the most votes are elected to the available seats. In case of a
+tie where there are more apparent winners than available seats (e.g., three
+candidates receive 10 votes each for two seats), the <a href=
+"#random">verifiable random selection procedure</a> described below will be
+used to fill the available seats.</p>
+<p id="short-term">The shortest term is assigned to the elected individual who
+received the fewest votes, the next shortest to the elected individual who
+received the next fewest, and so on. In the case of a tie among those eligible
+for a short term, the <a href="#random">verifiable random selection
+procedure</a> described below will be used to assign the short term.</p>
+<p>Refer to <a href="http://www.w3.org/2002/10/election-howto">How to Organize
+an Advisory Board or TAG election</a> [<a href=
+"refs.html#ref-election-howto">MEM15</a>] for more details.</p>
+<h5>2.5.2.1 <a name="random" id="random">Verifiable Random Selection
+Procedure</a></h5>
+<p>When it is necessary to use a verifiable random selection process (e.g., in
+an AB or TAG election, to "draw straws" in case of a tie or to fill a short
+term), W3C uses the random and verifiable procedure defined in <a href=
+"http://www.ietf.org/rfc/rfc2777.txt">RFC 2777</a> [<a href=
+"refs.html#ref-RFC2777">RFC2777</a>]. The procedure orders an input list of
+names (listed in alphabetical order by family name unless otherwise specified)
+into a "result order."</p>
+<p>W3C applies this procedure as follows:</p>
+<ol>
+<li>When N people have tied for M (less than N) seats. In this case, only the
+names of the N individuals who tied are provided as input to the procedure. The
+M seats are assigned in result order.</li>
+<li>After all elected individuals have been identified, when N people are
+eligible for M (less than N) short terms. In this case, only the names of those
+N individuals are provided as input to the procedure. The short terms are
+assigned in result order.</li>
+</ol>
+<h4>2.5.3 <a id="AB-TAG-vacated" name="AB-TAG-vacated">Advisory Board and
+Technical Architecture Group Vacated Seats</a></h4>
+<p>An Advisory Board or TAG participant's seat is vacated when either of the
+following occurs:</p>
+<ul>
+<li>the participant <a href="policies.html#resignation">resigns</a>, or</li>
+<li>the Chair asks the participant to <a href=
+"policies.html#resignation">resign</a>, for example because the participant has
+failed to remain in <a href="groups.html#good-standing">Good Standing</a>.</li>
+</ul>
+<p>When an Advisory Board or TAG participant changes affiliations, as long as
+<a href="#AB-TAG-constraints">Advisory Board and TAG participation
+constraints</a> are respected, the individual <span class="rfc2119">MAY</span>
+continue to participate until the next regularly scheduled election for that
+group. Otherwise, the seat is vacated.</p>
+<p>Vacated seats are filled according to this schedule:</p>
+<ul>
+<li>When an appointed TAG seat is vacated, the Director <span class=
+"rfc2119">MAY</span> re-appoint someone immediately, but no later than the next
+regularly scheduled election.</li>
+<li>When an elected seat on either the AB or TAG is vacated, the seat is filled
+at the next regularly scheduled election for the group unless the group Chair
+requests that W3C hold an election before then (for instance, due to the
+group's workload). The group Chair <span class="rfc2119">SHOULD NOT</span>
+request an exceptional election if the next regularly scheduled election is
+fewer than three months away.</li>
+</ul>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="policies.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="intro.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/policies.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,419 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>3 General Policies for W3C Groups</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="comm.html" />
+<link rel="previous" href="organization.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="comm.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="organization.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>3 <a name="Policies" id="Policies">General Policies for W3C Groups</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#ParticipationCriteria" class="tocxref">3.1
+Individual Participation Criteria</a>
+<ul class="toc">
+<li class="tocline4"><a href="#coi" class="tocxref">3.1.1 Conflict of Interest
+Policy</a></li>
+<li class="tocline4"><a href="#member-rep" class="tocxref">3.1.2 Individuals
+Representing a Member Organization</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#GeneralMeetings" class="tocxref">3.2
+Meetings</a></li>
+<li class="tocline3"><a href="#Consensus" class="tocxref">3.3 Consensus</a>
+<ul class="toc">
+<li class="tocline4"><a href="#managing-dissent" class="tocxref">3.3.1 Managing
+Dissent</a></li>
+<li class="tocline4"><a href="#WGArchiveMinorityViews" class="tocxref">3.3.2
+Recording and Reporting Formal Objections</a></li>
+<li class="tocline4"><a href="#formal-address" class="tocxref">3.3.3 Formally
+Addressing an Issue</a></li>
+<li class="tocline4"><a href="#WGChairReopen" class="tocxref">3.3.4 Reopening a
+Decision When Presented With New Information</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#Votes" class="tocxref">3.4 Votes</a></li>
+<li class="tocline3"><a href="#WGAppeals" class="tocxref">3.5 Appeal of a
+Chair's Decision</a></li>
+<li class="tocline3"><a href="#resignation" class="tocxref">3.6 Resignation
+from a Group</a></li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>This section describes general policies for W3C groups regarding
+participation, meeting requirements, and decision-making. These policies apply
+to <a name="participant" id="participant">participants</a> in the following
+groups: <a href="organization.html#AC">Advisory Committee</a>, <a href=
+"organization.html#ABParticipation">Advisory Board</a>, <a href=
+"organization.html#tag-participation">TAG</a>, <a href=
+"groups.html#wgparticipant">Working Groups</a>, <a href=
+"groups.html#igparticipant">Interest Groups</a>, and <a href=
+"groups.html#cgparticipant">Coordination Groups</a>.</p>
+<h3>3.1 <a name="ParticipationCriteria" id="ParticipationCriteria">Individual
+Participation Criteria</a></h3>
+<p>There are three qualities an individual is expected to demonstrate in order
+to participate in W3C:</p>
+<ol>
+<li>Technical competence in one's role</li>
+<li>The ability to act fairly</li>
+<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 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 Patent Policy</a>
+[<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
+<h4>3.1.1 <a name="coi" id="coi">Conflict of Interest Policy</a></h4>
+<p>Individuals participating materially in W3C work <span class=
+"rfc2119">MUST</span> disclose significant relationships when those
+relationships might reasonably be perceived as creating a conflict of interest
+with the individual's role at W3C. These disclosures <span class=
+"rfc2119">MUST</span> be kept up-to-date as the individual's affiliations
+change and 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 <span class="rfc2119">MUST</span> be evaluated. The role <span class=
+"rfc2119">MAY</span> be reassigned according to 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>
+<p>The following are some scenarios where disclosure is appropriate:</p>
+<ul>
+<li>Paid consulting for an organization whose activity is relevant to W3C, or
+any consulting compensated with equity (shares of stock, stock options, or
+other forms of corporate equity).</li>
+<li>A decision-making role/responsibility (such as participating on the Board)
+in other organizations relevant to W3C.</li>
+<li>A position on a publicly visible advisory body, even if no decision making
+authority is involved.</li>
+</ul>
+<p>Individuals seeking assistance on these matters <span class=
+"rfc2119">SHOULD</span> contact the Team.</p>
+<p>Team members are subject to the <a href=
+"http://www.w3.org/2000/09/06-conflictpolicy">W3C Team conflict of interest
+policy</a> [<a href="refs.html#ref-coi">PUB23</a>].</p>
+<h4>3.1.2 <a name="member-rep" id="member-rep">Individuals Representing a
+Member Organization</a></h4>
+<p>Generally, individuals representing a Member in an official capacity within
+W3C are employees of the Member organization. However, an Advisory Committee
+representative <span class="rfc2119">MAY</span> designate a non-employee to
+represent the Member. Non-employee Member representatives <span class=
+"rfc2119">MUST</span> disclose relevant affiliations to the Team and to any
+group in which the individual participates.</p>
+<p>In exceptional circumstances (e.g., situations that might jeopardize the
+progress of a group or create a <a href="#coi">conflict of interest</a>), the
+<a href="organization.html#def-Director">Director</a> <span class=
+"rfc2119">MAY</span> decline to allow an individual designated by an Advisory
+Committee representative to participate in a group.</p>
+<p>A group charter <span class="rfc2119">MAY</span> limit the number of
+individuals representing a W3C Member (or group of <a href=
+"organization.html#MemberRelated">related Members</a>).</p>
+<h3>3.2 <a name="GeneralMeetings" id="GeneralMeetings">Meetings</a></h3>
+<p>W3C groups (including the <a href="organization.html#ACMeetings">Advisory
+Committee</a>, <a href="organization.html#AB">Advisory Board</a>, <a href=
+"organization.html#TAG">TAG</a>, and <a href="groups.html#GroupsWG">Working
+Groups</a>) <span class="rfc2119">SHOULD</span> observe the meeting
+requirements in this section.</p>
+<p>W3C distinguishes two types of meetings:</p>
+<ol>
+<li>A <a name="ftf-meeting" id="ftf-meeting">face-to-face meeting</a> is one
+where most of the attendees are expected to participate in the same physical
+location.</li>
+<li>A <a name="distributed-meeting" id="distributed-meeting">distributed
+meeting</a> is one where most of the attendees are expected to participate from
+remote locations (e.g., by telephone, video conferencing, or <acronym title=
+"Internet Relay Chat">IRC</acronym>).</li>
+</ol>
+<p>A Chair <span class="rfc2119">MAY</span> invite an individual with a
+particular expertise to attend a meeting on an exceptional basis. This person
+is a meeting guest, not a group <a href="#participant">participant</a>. Meeting
+guests do not have <a href="#Votes">voting rights</a>. It is the responsibility
+of the Chair to ensure that all meeting guests respect the chartered <a href=
+"comm.html#confidentiality-levels">level of confidentiality</a> and other group
+requirements.</p>
+<p>Meeting announcements <span class="rfc2119">SHOULD</span> be sent to all
+appropriate group mailing lists, i.e., those most relevant to the anticipated
+meeting participants.</p>
+<p>The following table lists requirements for organizing a meeting:</p>
+<table summary=
+"Requirements for face-to-face meetings and distributed meetings" border="1"
+cellpadding="5">
+<tbody>
+<tr align="left">
+<th align="left"></th>
+<th align="left">Face-to-face meetings</th>
+<th align="left">Distributed meetings</th>
+</tr>
+<tr>
+<th align="left">Meeting announcement (before)</th>
+<td><span class="time-interval">eight weeks<sup>*</sup></span></td>
+<td><span class="time-interval">one week<sup>*</sup></span></td>
+</tr>
+<tr>
+<th align="left">Agenda available (before)</th>
+<td><span class="time-interval">two weeks</span></td>
+<td><span class="time-interval">24 hours</span> (or longer if a meeting is
+scheduled after a weekend or holiday)</td>
+</tr>
+<tr>
+<th align="left">Participation confirmed (before)</th>
+<td><span class="time-interval">three days</span></td>
+<td><span class="time-interval">24 hours</span></td>
+</tr>
+<tr>
+<th align="left">Action items available (after)</th>
+<td><span class="time-interval">three days</span></td>
+<td><span class="time-interval">24 hours</span></td>
+</tr>
+<tr>
+<th align="left">Minutes available (after)</th>
+<td><span class="time-interval">two weeks</span></td>
+<td><span class="time-interval">48 hours</span></td>
+</tr>
+</tbody>
+</table>
+<p><sup>*</sup> To allow proper planning (e.g., travel arrangements), the Chair
+is responsible for giving sufficient advance notice about the date and location
+of a meeting. Shorter notice for a meeting is allowed provided that there are
+no objections from group participants.</p>
+<h3>3.3 <a name="Consensus" id="Consensus">Consensus</a></h3>
+<p>Consensus is a core value of W3C. To promote consensus, the W3C process
+requires Chairs to ensure that groups consider all legitimate views and
+objections, and endeavor to resolve them, whether these views and objections
+are expressed by the active participants of the group or by others (e.g.,
+another W3C group, a group in another organization, or the general public).
+Decisions <span class="rfc2119">MAY</span> be made during meetings (<a href=
+"#ftf-meeting">face-to-face</a> or <a href=
+"#distributed-meeting">distributed</a>) as well as through email.
+<strong>Note:</strong> The Director, W3C Chair, and COO have the role of
+assessing consensus within the Advisory Committee.</p>
+<p>The following terms are used in this document to describe the level of
+support for a decision among a set of eligible individuals:</p>
+<ol>
+<li><a name="def-Consensus" id="def-Consensus">Consensus</a>: A substantial
+number of individuals in the set support the decision and nobody in the set
+registers a <a href="#FormalObjection">Formal Objection</a>. Individuals in the
+set may abstain. Abstention is either an explicit expression of no opinion or
+silence by an individual in the set. <a name="def-Unanimity" id=
+"def-Unanimity">Unanimity</a> is the particular case of consensus where all
+individuals in the set support the decision (i.e., no individual in the set
+abstains).</li>
+<li><a name="def-Dissent" id="def-Dissent">Dissent</a>: At least one individual
+in the set registers a <a href="#FormalObjection">Formal Objection</a>.</li>
+</ol>
+<p>By default, the set of individuals eligible to participate in a decision is
+the set of group participants in <a href="groups.html#good-standing">Good
+Standing</a>. The Process Document does not require a quorum for decisions
+(i.e., the minimal number of eligible participants required to be present
+before the Chair can call a question). A charter <span class=
+"rfc2119">MAY</span> include a quorum requirement for consensus decisions.</p>
+<p>Where unanimity is not possible, a group <span class="rfc2119">SHOULD</span>
+strive to make consensus decisions where there is significant support and few
+abstentions. The Process Document does not require a particular percentage of
+eligible participants to agree to a motion in order for a decision to be made.
+To avoid decisions where there is widespread apathy, (i.e., little support and
+many abstentions), groups <span class="rfc2119">SHOULD</span> set minimum
+thresholds of active support before a decision can be recorded. The appropriate
+percentage <span class="rfc2119">MAY</span> vary depending on the size of the
+group and the nature of the decision. A charter <span class=
+"rfc2119">MAY</span> include threshold requirements for consensus decisions.
+For instance, a charter might require a supermajority of eligible participants
+(i.e., some established percentage above 50%) to support certain types of
+consensus decisions.</p>
+<h4>3.3.1 <a name="managing-dissent" id="managing-dissent">Managing
+Dissent</a></h4>
+<p>In some cases, even after careful consideration of all points of view, a
+group might find itself unable to reach consensus. The Chair <span class=
+"rfc2119">MAY</span> record a decision where there is dissent (i.e., there is
+at least one <a href="#FormalObjection">Formal Objection</a>) so that the group
+may make progress (for example, to produce a deliverable in a timely manner).
+Dissenters cannot stop a group's work simply by saying that they cannot live
+with a decision. When the Chair believes that the Group has duly considered the
+legitimate concerns of dissenters as far as is possible and reasonable, the
+group <span class="rfc2119">SHOULD</span> move on.</p>
+<p>Groups <span class="rfc2119">SHOULD</span> favor proposals that create the
+weakest objections. This is preferred over proposals that are supported by a
+large majority but that cause strong objections from a few people. As part of
+making a decision where there is dissent, the Chair is expected to be aware of
+which participants work for the same (or <a href=
+"organization.html#MemberRelated">related</a>) Member organizations and weigh
+their input accordingly.</p>
+<h4>3.3.2 <a name="WGArchiveMinorityViews" id=
+"WGArchiveMinorityViews">Recording and Reporting Formal Objections</a></h4>
+<p>In the W3C process, an individual may register a Formal Objection to a
+decision. A <a id="FormalObjection" name="FormalObjection">Formal Objection</a>
+to a group decision is one that the reviewer requests that the Director
+consider as part of evaluating the related decision (e.g., in response to a
+<a href="tr.html#rec-advance">request to advance</a> a technical report).
+<strong>Note:</strong> In this document, the term "Formal Objection" is used to
+emphasize this process implication: Formal Objections receive Director
+consideration. The word "objection" used alone has ordinary English
+connotations.</p>
+<p>An individual who registers a Formal Objection <span class=
+"rfc2119">SHOULD</span> cite technical arguments and propose changes that would
+remove the Formal Objection; these proposals <span class="rfc2119">MAY</span>
+be vague or incomplete. Formal Objections that do not provide substantive
+arguments or rationale are unlikely to receive serious consideration by the
+Director.</p>
+<p>A record of each Formal Objection <span class="rfc2119">MUST</span> be
+<a href="comm.html#confidentiality-change">publicly available</a>. A Call for
+Review (of a document) to the Advisory Committee <span class=
+"rfc2119">MUST</span> identify any Formal Objections.</p>
+<h4>3.3.3 <a name="formal-address" id="formal-address">Formally Addressing an
+Issue</a></h4>
+<p>In the context of this document, a group has formally addressed an issue
+when it has sent a public, substantive response to the reviewer who raised the
+issue. A substantive response is expected to include rationale for decisions
+(e.g., a technical explanation, a pointer to charter scope, or a pointer to a
+requirements document). The adequacy of a response is measured against what a
+W3C reviewer would generally consider to be technically sound. If a group
+believes that a reviewer's comments result from a misunderstanding, the group
+<span class="rfc2119">SHOULD</span> seek clarification before reaching a
+decision.</p>
+<p>As a courtesy, both Chairs and reviewers <span class="rfc2119">SHOULD</span>
+set expectations for the schedule of responses and acknowledgments. The group
+<span class="rfc2119">SHOULD</span> reply to a reviewer's initial comments in a
+timely manner. The group <span class="rfc2119">SHOULD</span> set a time limit
+for acknowledgment by a reviewer of the group's substantive response; a
+reviewer cannot block a group's progress. It is common for a reviewer to
+require a week or more to acknowledge and comment on a substantive response.
+The group's responsibility to respond to reviewers does not end once a
+reasonable amount of time has elapsed. However, reviewers <span class=
+"rfc2119">SHOULD</span> realize that their comments will carry less weight if
+not sent to the group in a timely manner.</p>
+<p>Substantive responses <span class="rfc2119">SHOULD</span> be recorded. The
+group <span class="rfc2119">SHOULD</span> maintain an accurate summary of all
+substantive issues and responses to them (e.g., in the form of an issues list
+with links to mailing list archives).</p>
+<h4>3.3.4 <a name="WGChairReopen" id="WGChairReopen">Reopening a Decision When
+Presented With New Information</a></h4>
+<p>The Chair <span class="rfc2119">MAY</span> reopen a decision when presented
+with new information, including:</p>
+<ul>
+<li>additional technical information,</li>
+<li>comments by email from participants who were unable to attend a scheduled
+meeting,</li>
+<li>comments by email from meeting attendees who chose not to speak out during
+a meeting (e.g., so they could confer later with colleagues or for cultural
+reasons).</li>
+</ul>
+<p>The Chair <span class="rfc2119">SHOULD</span> record that a decision has
+been reopened, and <span class="rfc2119">MUST</span> do so upon request from a
+group participant.</p>
+<h3>3.4 <a name="Votes" id="Votes">Votes</a></h3>
+<p>A group <span class="rfc2119">SHOULD</span> only conduct a vote to resolve a
+<em>substantive issue</em> after the Chair has determined that all available
+means of <a href="#Consensus">reaching consensus</a> through technical
+discussion and compromise have failed, and that a vote is necessary to break a
+deadlock. In this case the Chair <span class="rfc2119">MUST</span> record
+(e.g., in the minutes of the meeting or in an archived email message):</p>
+<ul>
+<li>an explanation of the issue being voted on;</li>
+<li>the decision to conduct a vote (e.g., a simple majority vote) to resolve
+the issue;</li>
+<li>the outcome of the vote;</li>
+<li>any Formal Objections.</li>
+</ul>
+<p>In order to vote to resolve a substantive issue, an individual <span class=
+"rfc2119">MUST</span> be a group <a href="#participant">participant</a> in
+<a href="groups.html#good-standing">Good Standing</a>. Each organization
+represented in the group <span class="rfc2119">MUST</span> have at most one
+vote, even when the organization is represented by several participants in the
+group (including Invited Experts). For the purposes of voting:</p>
+<ul>
+<li>A Member or group of <a href="organization.html#MemberRelated">related
+Members</a> is considered a single organization.</li>
+<li>The <a href="organization.html#Team">Team</a> is considered an
+organization.</li>
+</ul>
+<p>Unless the charter states otherwise, <a href=
+"groups.html#invited-expert-wg">Invited Experts</a> <span class=
+"rfc2119">MAY</span> vote.</p>
+<p>If a participant is unable to attend a vote, that individual <span class=
+"rfc2119">MAY</span> authorize anyone at the meeting to act as a <a name=
+"proxy" id="proxy">proxy</a>. The absent participant <span class=
+"rfc2119">MUST</span> inform the Chair in writing who is acting as proxy, with
+written instructions on the use of the proxy. For a Working Group or Interest
+Group, see the related requirements regarding an individual who attends a
+meeting as a <a href="groups.html#mtg-substitute">substitute</a> for a
+participant.</p>
+<p>A group <span class="rfc2119">MAY</span> vote for other purposes than to
+resolve a substantive issue. For instance, the Chair often conducts a "straw
+poll" vote as a means of determining whether there is consensus about a
+potential decision.</p>
+<p>A group <span class="rfc2119">MAY</span> also vote to make a process
+decision. For example, it is appropriate to decide by simple majority whether
+to hold a meeting in San Francisco or San Jose (there's not much difference
+geographically). When simple majority votes are used to decide minor issues,
+the minority are <span class="rfc2119">NOT REQUIRED</span> to state the reasons
+for their dissent, and the group is <span class="rfc2119">NOT REQUIRED</span>
+to record individual votes.</p>
+<p>A group charter <span class="rfc2119">SHOULD</span> include formal voting
+procedures (e.g., quorum or threshold requirements) for making decisions about
+substantive issues.</p>
+<p>Procedures for <a href="acreview.html#ACVotes">Advisory Committee votes</a>
+are described separately.</p>
+<h3>3.5 <a name="WGAppeals" id="WGAppeals">Appeal of a Chair's
+Decision</a></h3>
+<p>Groups resolve issues through dialog. Individuals who disagree strongly with
+a decision <span class="rfc2119">SHOULD</span> register with the Chair any
+<a href="#FormalObjection">Formal Objections</a> (e.g., to a decision made as
+the result of a <a href="#Votes">vote</a>).</p>
+<p>When group participants believe that their concerns are not being duly
+considered by the group, they <span class="rfc2119">MAY</span> ask the <a href=
+"organization.html#def-Director">Director</a> (for representatives of a Member
+organization, via their Advisory Committee representative) to confirm or deny
+the decision. The participants <span class="rfc2119">SHOULD</span> also make
+their requests known to the <a href="groups.html#TeamContact">Team Contact</a>.
+The Team Contact <span class="rfc2119">MUST</span> inform the Director when a
+group participant has raised concerns about due process.</p>
+<p>Any requests to the Director to confirm a decision <span class=
+"rfc2119">MUST</span> include a summary of the issue (whether technical or
+procedural), decision, and rationale for the objection. All counter-arguments,
+rationales, and decisions <span class="rfc2119">MUST</span> be recorded.</p>
+<p>Procedures for <a href="acreview.html#ACAppeal">Advisory Committee
+appeals</a> are described separately.</p>
+<h3>3.6 <a name="resignation" id="resignation">Resignation from a
+Group</a></h3>
+<p>A W3C Member or Invited Expert <span class="rfc2119">MAY</span> resign from
+a group. The Team will establish administrative procedures for resignation. See
+section 4.2. of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+Patent Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>] for
+information about obligations remaining after resignation from certain
+groups.</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="comm.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="organization.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/processdoc.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,66 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>12 Process Evolution</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="refs.html" />
+<link rel="previous" href="submission.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="refs.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="submission.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>12 <a name="GAProcess" id="GAProcess">Process Evolution</a></h2>
+<div class="toc"></div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>The <a name="ProcessDoc" id="ProcessDoc">W3C Process Document</a> undergoes
+similar consensus-building processes as technical reports, with the <a href=
+"organization.html#AB">Advisory Board</a> acting as the sponsoring Working
+Group.</p>
+<p>The Advisory Board initiates review of a Process Document as follows:</p>
+<ol>
+<li>The Team sends a Call for Review to the Advisory Committee and other W3C
+groups.</li>
+<li>After comments have been <a href="policies.html#formal-address">formally
+addressed</a> and the document possibly modified, the Team seeks endorsement
+from the Members by initiating an <a href="acreview.html#ACReview">Advisory
+Committee review</a> of a Proposed Process Document. The review period
+<span class="rfc2119">MUST</span> last at least <span class=
+"time-interval">four weeks</span>.</li>
+<li><a href="acreview.html#ACReviewAfter">After the Advisory Committee
+review</a>, if there is consensus, the Team enacts the new process officially
+by announcing the <a href="acreview.html#def-w3c-decision">W3C decision</a> to
+the Advisory Committee. If there was <a href=
+"policies.html#def-Dissent">dissent</a>, Advisory Committee representatives
+<span class="rfc2119">MAY</span> <a href="acreview.html#ACAppeal">appeal</a>
+the decision.</li>
+</ol>
+<p>W3C <span class="rfc2119">MAY</span> also modify a Process Document by
+following the processes for <a href="tr.html#rec-modify">modifying a
+Recommendation</a>.</p>
+<p>Reviews of the Process Document are not public reviews.</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="refs.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="submission.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/refs.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,182 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>13 References</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="acks.html" />
+<link rel="previous" href="processdoc.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="acks.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="processdoc.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>13 <a name="references" id="references">References</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#public-refs" class="tocxref">13.1 Public
+Resources</a></li>
+<li class="tocline3"><a href="#member-refs" class="tocxref">13.2 Member-only
+Resources</a></li>
+<li class="tocline3"><a href="#other-refs" class="tocxref">13.3 Other
+References</a></li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<h3>13.1 <a name="public-refs" id="public-refs">Public Resources</a></h3>
+<p>The following public information is available at the <a href=
+"http://www.w3.org/">W3C Web site</a>.</p>
+<dl>
+<dt><a name="ref-join-w3c" id="ref-join-w3c"><b>[PUB5]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/join">How to Join
+W3C</a></cite></dd>
+<dt><a name="ref-member-agreement" id=
+"ref-member-agreement"><b>[PUB6]</b></a></dt>
+<dd><cite><a href=
+"http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+Agreement</a></cite></dd>
+<dt><a name="ref-current-mem" id="ref-current-mem"><b>[PUB8]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/Member/List">The list of
+current W3C Members</a></cite></dd>
+<dt><a name="ref-activity-list" id="ref-activity-list"><b>[PUB9]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/activities">The list of W3C
+Activities</a></cite></dd>
+<dt><a name="ref-submission-list" id=
+"ref-submission-list"><b>[PUB10]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Submission/">The list of acknowledged
+Member Submissions</a></cite></dd>
+<dt><a name="ref-doc-list" id="ref-doc-list"><b>[PUB11]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/TR/">The W3C technical reports
+index</a></cite></dd>
+<dt><a name="ref-submission-overview" id=
+"ref-submission-overview"><b>[PUB13]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Submission/1996/Template/">Submission
+request overview</a></cite></dd>
+<dt><a name="ref-people" id="ref-people"><b>[PUB14]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/People/">The W3C Team</a></cite></dd>
+<dt><a name="ref-mission" id="ref-mission"><b>[PUB15]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/">About the World Wide Web
+Consortium</a></cite></dd>
+<dt><a name="ref-team-submission-list" id=
+"ref-team-submission-list"><b>[PUB16]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/TeamSubmission/">The list of published
+Team Submissions</a></cite></dd>
+<dt><a name="ref-invited-expert" id=
+"ref-invited-expert"><b>[PUB17]</b></a></dt>
+<dd><cite><a href=
+"http://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and
+collaborators agreement</a></cite></dd>
+<dt><a name="ref-doc-license" id="ref-doc-license"><b>[PUB18]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
+Document License</a></cite></dd>
+<dt><a name="ref-software-license" id=
+"ref-software-license"><b>[PUB19]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-software">W3C
+Software Notice and License</a></cite></dd>
+<dt><a name="ref-translations" id="ref-translations"><b>[PUB20]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/Translation/">Translations of
+W3C technical reports</a></cite></dd>
+<dt><a name="ref-pub-mailing-lists" id=
+"ref-pub-mailing-lists"><b>[PUB21]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Mail/">Public W3C mailing
+lists</a></cite></dd>
+<dt><a name="ref-coi" id="ref-coi"><b>[PUB23]</b></a></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><a name="ref-tag-charter" id="ref-tag-charter"><b>[PUB25]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/2001/07/19-tag">Technical Architecture
+Group (TAG) Charter</a></cite></dd>
+<dt><a name="ref-tag-home" id="ref-tag-home"><b>[PUB26]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/2001/tag/">The TAG home
+page</a></cite></dd>
+<dt><a name="ref-rec-tips" id="ref-rec-tips"><b>[PUB27]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/2002/05/rec-tips">Tips for Getting to
+Recommendation Faster</a></cite></dd>
+<dt><a name="ref-liaison-list" id="ref-liaison-list"><b>[PUB28]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons with
+other organizations</a></cite></dd>
+<dt><a name="ref-ab-home" id="ref-ab-home"><b>[PUB30]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/2002/ab/">The Advisory Board home
+page</a></cite></dd>
+<dt><a name="ref-pubrules" id="ref-pubrules"><b>[PUB31]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Guide/pubrules">Publication
+Rules</a></cite></dd>
+<dt><a name="ref-fellows" id="ref-fellows"><b>[PUB32]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C
+Fellows Program</a></cite></dd>
+<dt><a name="ref-patentpolicy" id="ref-patentpolicy"><b>[PUB33]</b></a></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>
+</dl>
+<h3>13.2 <a name="member-refs" id="member-refs">Member-only Resources</a></h3>
+<p>The following <a href="comm.html#Member-only">Member-only</a> information is
+available at the <a href="http://www.w3.org/">W3C Web site</a>.</p>
+<dl>
+<dt><a name="ref-current-ac" id="ref-current-ac"><b>[MEM1]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Member/ACList">Current Advisory Committee
+representatives</a></cite></dd>
+<dt><a name="ref-mailing-lists" id="ref-mailing-lists"><b>[MEM2]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Member/Mail/">Group mailing
+lists</a></cite></dd>
+<dt><a name="ref-calendar" id="ref-calendar"><b>[MEM3]</b></a></dt>
+<dd>The <cite><a href="http://www.w3.org/Member/Eventscal">calendar of all
+scheduled official W3C events</a></cite></dd>
+<dt><a name="ref-new-member" id="ref-new-member"><b>[MEM4]</b></a></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><a name="ref-ac-meetings" id="ref-ac-meetings"><b>[MEM5]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Member/Meeting/">Advisory Committee
+meetings</a></cite></dd>
+<dt><a name="ref-member-web" id="ref-member-web"><b>[MEM6]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/Member/">Member Web site</a></cite></dd>
+<dt><a name="ref-member-sub" id="ref-member-sub"><b>[MEM8]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/2000/09/submission">How to send a
+Submission request</a></cite></dd>
+<dt><a name="ref-guide" id="ref-guide"><b>[MEM9]</b></a></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><a name="ref-discipline-gl" id="ref-discipline-gl"><b>[MEM14]</b></a></dt>
+<dd><cite><a href="http://www.w3.org/2002/09/discipline">Guidelines for
+Disciplinary Action</a></cite></dd>
+<dt><a name="ref-election-howto" id=
+"ref-election-howto"><b>[MEM15]</b></a></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>13.3 <a name="other-refs" id="other-refs">Other References</a></h3>
+<dl>
+<dt><a name="ref-RFC2119" id="ref-RFC2119"><b>[RFC2119]</b></a></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><a name="ref-RFC2777" id="ref-RFC2777"><b>[RFC2777]</b></a></dt>
+<dd><cite><a href="http://www.ietf.org/rfc/rfc2777.txt">"Publicly Verifiable
+Nomcom Random Selection"</a></cite>, D. Eastlake 3rd, February 2000.</dd>
+</dl>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="acks.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="processdoc.html">previous chapter</a>]
+&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/submission.html	Wed Mar 19 13:18:55 2014 +0100
@@ -0,0 +1,280 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta name="generator" content=
+"HTML Tidy for Linux/x86 (vers 12 April 2005), see www.w3.org" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<link rel="stylesheet" href="style/default.css" type="text/css" />
+<link rel="stylesheet" type="text/css" href=
+"http://www.w3.org/StyleSheets/TR/base.css" />
+<title>11 Member Submission Process</title>
+<link rel="contents" href="cover.html#toc" />
+<link rel="next" href="processdoc.html" />
+<link rel="previous" href="liaisons.html" />
+</head>
+<body>
+<div class="noprint">
+<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
+"navbar-top">
+<p>[<a accesskey="n" rel="Next" href="processdoc.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="liaisons.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+<hr /></map></div>
+</div>
+<h1>W3C Process Document</h1>
+<h2>11 <a name="Submission" id="Submission">Member Submission Process</a></h2>
+<div class="toc">
+<ul class="toc">
+<li class="tocline3"><a href="#SubmissionRights" class="tocxref">11.1 Submitter
+Rights and Obligations</a>
+<ul class="toc">
+<li class="tocline4"><a href="#SubmissionScope" class="tocxref">11.1.1 Scope of
+Member Submissions</a></li>
+<li class="tocline4"><a href="#SubmissionReqs" class="tocxref">11.1.2
+Information Required in a Submission Request</a></li>
+</ul>
+</li>
+<li class="tocline3"><a href="#TeamSubmissionRights" class="tocxref">11.2 Team
+Rights and Obligations</a></li>
+<li class="tocline3"><a href="#SubmissionYes" class="tocxref">11.3
+Acknowledgment of a Submission Request</a></li>
+<li class="tocline3"><a href="#SubmissionNo" class="tocxref">11.4 Rejection of
+a Submission Request</a></li>
+</ul>
+</div>
+<!--NewPage-->
+<!-- this is for html2ps -->
+<p>The Member Submission process allows Members to propose technology or other
+ideas for consideration by the Team. After review, the Team <span class=
+"rfc2119">MAY</span> publish the material at the W3C Web site. The formal
+process affords Members a record of their contribution and gives them a
+mechanism for disclosing the details of the transaction with the Team
+(including IPR claims). The Team also publishes review comments on the
+Submitted materials for W3C Members, the public, and the media.</p>
+<p>A <a name="MemberSubmission" id="MemberSubmission">Member Submission</a>
+consists of:</p>
+<ul>
+<li>One or more documents developed outside of the W3C process, and</li>
+<li>Information about the documents, provided by the Submitter.</li>
+</ul>
+<p>One or more Members (called the "Submitter(s)") <span class=
+"rfc2119">MAY</span> participate in a Member Submission. Only W3C Members
+<span class="rfc2119">MAY</span> be listed as Submitter(s).</p>
+<p>The Submission process consists of the following steps:</p>
+<ol>
+<li>One of the Submitter(s) sends a request to the Team to acknowledge the
+Submission request. The Team and Submitter(s) communicate to ensure that the
+Member Submission is complete.</li>
+<li>After Team review, the Director <span class="rfc2119">MUST</span> either
+acknowledge or reject the Submission request.
+<ul>
+<li>If <a href="#SubmissionYes">acknowledged</a>, the Team <span class=
+"rfc2119">MUST</span> publish the Member Submission at the public W3C Web site,
+in addition to Team comments about the Member Submission.</li>
+<li>If <a href="#SubmissionNo">rejected</a>, the Submitter(s) <span class=
+"rfc2119">MAY</span> appeal to either the <a href=
+"organization.html#TAG">TAG</a> or the <a href="organization.html#AB">Advisory
+Board</a>.</li>
+</ul>
+</li>
+</ol>
+<p><strong>Note:</strong> To avoid confusion about the Member Submission
+process, please note that:</p>
+<ul>
+<li>Documents in a Member Submission are developed outside of W3C. These
+documents are <strong>not</strong> part of the <a href=
+"tr.html#Reports">technical report development process</a> (and therefore are
+not included in the <a href="http://www.w3.org/TR/">index of W3C technical
+reports</a>). Members wishing to have documents developed outside of W3C
+published by W3C <span class="rfc2119">MUST</span> follow the Member Submission
+process.</li>
+<li>The Submission process is <strong>not</strong> a means by which Members ask
+for "ratification" of these documents as <a href="tr.html#RecsW3C">W3C
+Recommendations</a>.</li>
+<li>There is no requirement or guarantee that technology which is part of an
+acknowledged Submission request will receive further consideration by W3C
+(e.g., by a W3C Working Group).</li>
+</ul>
+<p>Publication of a Member Submission by W3C does not imply endorsement by W3C,
+including the W3C Team or Members. The acknowledgment of a Submission request
+does not imply that any action will be taken by W3C. It merely records publicly
+that the Submission request has been made by the Submitter. A Member Submission
+published by W3C <span class="rfc2119">MUST NOT</span> be referred to as "work
+in progress" of the W3C.</p>
+<p>The list of <a href="http://www.w3.org/Submission/">acknowledged Member
+Submissions</a> [<a href="refs.html#ref-submission-list">PUB10</a>] is
+available at the W3C Web site.</p>
+<h3>11.1 <a name="SubmissionRights" id="SubmissionRights">Submitter Rights and
+Obligations</a></h3>
+<p>When more than one Member jointly participates in a Submission request, only
+one Member formally sends in the request. That Member <span class=
+"rfc2119">MUST</span> copy each of the Advisory Committee representatives of
+the other participating Members, and each of those Advisory Committee
+representatives <span class="rfc2119">MUST</span> confirm (by email to the
+Team) their participation in the Submission request.</p>
+<p>At any time prior to acknowledgment, any Submitter <span class=
+"rfc2119">MAY</span> withdraw support for a Submission request (described in
+"<a href="http://www.w3.org/2000/09/submission">How to send a Submission
+request</a>"). A Submission request is "withdrawn" when no Submitter(s) support
+it. The Team <span class="rfc2119">MUST NOT</span> make statements about
+withdrawn Submission requests.</p>
+<p>Prior to acknowledgment, the Submitter(s) <span class="rfc2119">MUST
+NOT</span>, <strong>under any circumstances</strong>, refer to a document as
+"submitted to the World Wide Web Consortium" or "under consideration by W3C" or
+any similar phrase either in public or Member communication. The Submitter(s)
+<span class="rfc2119">MUST NOT</span> imply in public or Member communication
+that W3C is working (with the Submitter(s)) on the material in the Member
+Submission. The Submitter(s) <span class="rfc2119">MAY</span> publish the
+documents in the Member Submission prior to acknowledgment (without reference
+to the Submission request).</p>
+<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="activities.html#def-Activity">Activity</a>.</p>
+<h4>11.1.1 <a name="SubmissionScope" 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=
+"groups.html#group-participation">participate in the Working Group</a> and
+contribute the technology to the group's process rather than seek publication
+through the Member Submission process. The Working Group <span class=
+"rfc2119">MAY</span> incorporate the contributed technology into its
+deliverables. If the Working Group does not incorporate the technology, it
+<span class="rfc2119">SHOULD 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>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=
+"refs.html#ref-mission">PUB15</a>].</p>
+<h4>11.1.2 <a name="SubmissionReqs" id="SubmissionReqs">Information Required in
+a Submission Request</a></h4>
+<p>The Submitter(s) and any other authors of the submitted material
+<span class="rfc2119">MUST</span> agree that, if the request is acknowledged,
+the documents in the Member Submission will be subject to the <a href=
+"http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document
+License</a> [<a href="refs.html#ref-doc-license">PUB18</a>] and will include a
+reference to it. The Submitter(s) <span class="rfc2119">MAY</span> hold the
+copyright for the documents in a Member Submission.</p>
+<p>The request must satisfy the Member Submission licensing commitments of
+<a href="http://www.w3.org/Consortium/Patent-Policy#sec-submissions">section
+3.3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
+Policy</a> [<a href="refs.html#ref-patentpolicy">PUB33</a>].</p>
+<p>The Submitter(s) <span class="rfc2119">MUST</span> include the following
+information:</p>
+<ul>
+<li>The list of all submitting Members.</li>
+<li>Position statements from all submitting Members (gathered by the
+Submitter). All position statements must appear in a separate document.</li>
+<li>Complete electronic copies of any documents submitted for consideration
+(e.g., a technical specification, a position paper, etc.) If the Submission
+request is acknowledged, these documents will be published by W3C and therefore
+must satisfy the Communication Team's <a href=
+"http://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href=
+"refs.html#ref-pubrules">PUB31</a>]. Submitters may hold the copyright for the
+material contained in these documents, but when published by W3C, these
+documents <span class="rfc2119">MUST</span> be subject to the provisions of the
+<a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document
+License</a> [<a href="refs.html#ref-doc-license">PUB18</a>].</li>
+</ul>
+<p>The request <span class="rfc2119">MUST</span> also answer the following
+questions.</p>
+<ul>
+<li>What proprietary technology is required to implement the areas addressed by
+the request, and what terms are associated with its use? Again, many answers
+are possible, but the specific answer will affect the Team's decision.</li>
+<li>What resources, if any, does the Submitter intend to make available if the
+W3C acknowledges the Submission request and takes action on it?</li>
+<li>What action would the Submitter like W3C to take if the Submission request
+is acknowledged?</li>
+<li>What mechanisms are there to make changes to the specification being
+submitted? This includes, but is not limited to, stating where change control
+will reside if the request is acknowledged.</li>
+</ul>
+<p>For other administrative requirements related to Submission requests, see
+"<a href="http://www.w3.org/2000/09/submission">How to send a Submission
+request</a>" [<a href="refs.html#ref-member-sub">MEM8</a>].</p>
+<h3>11.2 <a name="TeamSubmissionRights" id="TeamSubmissionRights">Team Rights
+and Obligations</a></h3>
+<p>Although they are not technical reports, the documents in a Member
+Submission <span class="rfc2119">MUST</span> fulfill the requirements
+established by the Team, including the Team's <a href=
+"http://www.w3.org/Guide/pubrules">Publication Rules</a>.</p>
+<p>The Team sends a <a name="validation-notice" id=
+"validation-notice">validation notice</a> to the Submitter(s) once the Team has
+reviewed a Submission request and judged it complete and correct.</p>
+<p>Prior to a decision to <a href="#SubmissionYes">acknowledge</a> or <a href=
+"#SubmissionNo">reject</a> the request, the request is <a href=
+"comm.html#Team-only">Team-only</a>, and the Team <span class=
+"rfc2119">MUST</span> hold it in the strictest confidentiality. In particular,
+the Team <span class="rfc2119">MUST NOT</span> comment to the media about the
+Submission request.</p>
+<h3>11.3 <a name="SubmissionYes" id="SubmissionYes">Acknowledgment of a
+Submission Request</a></h3>
+<p>The Director <a href="#SubmissionYes">acknowledges</a> a Submission request
+by sending an announcement to the Advisory Committee. Though the announcement
+<span class="rfc2119">MAY</span> be made at any time, the Submitter(s) can
+expect an announcement between <span class="time-interval">four to six
+weeks</span> after the <a href="#validation-notice">validation notice</a>. The
+Team <span class="rfc2119">MUST</span> keep the Submitter(s) informed of when
+an announcement is likely to be made.</p>
+<p>Once a Submission request has been acknowledged, the Team <span class=
+"rfc2119">MUST</span>:</p>
+<ul>
+<li>Publish the Member Submission.</li>
+<li>Publish Team comments about the Submission request.</li>
+</ul>
+<p>If the Submitter(s) wishes to modify a document published as the result of
+acknowledgment, the Submitter(s) <span class="rfc2119">MUST</span> start the
+Submission process from the beginning, even just to correct editorial
+changes.</p>
+<h3>11.4 <a name="SubmissionNo" id="SubmissionNo">Rejection of a Submission
+Request</a></h3>
+<p>The Director <span class="rfc2119">MAY</span> reject a Submission request
+for a variety of reasons, including any of the following:</p>
+<ul>
+<li>The ideas expressed in the request overlap in scope with the work of a
+chartered Working Group, and acknowledgment might jeopardize the progress of
+the group.</li>
+<li>The IPR statement made by the Submitter(s) is inconsistent with the W3C's
+<a href="http://www.w3.org/Consortium/Patent-Policy">Patent Policy</a>
+[<a href="refs.html#ref-patentpolicy">PUB33</a>], <a href=
+"http://www.w3.org/Consortium/Legal/copyright-documents">Document License</a>
+[<a href="refs.html#ref-doc-license">PUB18</a>], or other IPR policies.</li>
+<li>The ideas expressed in the request are poor, might harm the Web, or run
+counter to <a href="http://www.w3.org/Consortium/#mission">W3C's
+mission</a>.</li>
+<li>The ideas expressed in the request lie well outside the scope of W3C's
+mission.</li>
+</ul>
+<p>In case of a rejection, the Team <span class="rfc2119">MUST</span> inform
+the Advisory Committee representative(s) of the Submitter(s). If requested by
+the Submitter(s), the Team <span class="rfc2119">MUST</span> provide rationale
+to the Submitter(s) about the rejection. Other than to the Submitter(s), the
+Team <span class="rfc2119">MUST NOT</span> make statements about why a
+Submission request was rejected.</p>
+<p>The Advisory Committee representative(s) of the Submitters(s) <span class=
+"rfc2119">MAY</span> appeal the rejection to the <a href=
+"organization.html#TAG">TAG</a> if the reasons are related to Web architecture,
+or to the <a href="organization.html#AB">Advisory Board</a> if the request is
+rejected for other reasons. In this case the Team <span class=
+"rfc2119">SHOULD</span> make available its rationale for the rejection to the
+appropriate body. The Team will establish a process for such appeals that
+ensures the appropriate <a href="comm.html#confidentiality-levels">level of
+confidentiality</a>.</p>
+<div class="noprint">
+<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
+"navbar-bottom">
+<hr />
+<p>[<a accesskey="n" rel="Next" href="processdoc.html">next chapter</a>] &nbsp;
+[<a accesskey="p" rel="Prev" href="liaisons.html">previous chapter</a>] &nbsp;
+[<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
+</map></div>
+</div>
+</body>
+</html>