World Wide Web Consortium Process Document (original) (raw)
14 October 2005
On 1 August 2014, W3C began a transition away from this document; see the current W3C Process Document.
This version:
http://www.w3.org/2005/10/Process-20051014/
Latest operative version:
http://www.w3.org/Consortium/Process/
Previous operative version:
http://www.w3.org/2004/02/Process-20040205/
Editor:
Ian Jacobs, W3C
Please refer to the errata for this document, which may include some normative corrections.
This document is also available in these non-normative packages: single HTML file, self-contained gzipped tar archive, self-contained zip archive.
There may be translationsof this document.
Copyright © 1996-2005 W3C® (MIT, ERCIM,Keio), All Rights Reserved. W3C liability, trademark, document use and software licensingrules apply. Your interactions with this site are in accordance with ourpublic and Member privacy statements.
Abstract
The mission of the World Wide Web Consortium (W3C) 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.
For more information about the W3C mission and the history of W3C, please refer to About W3C [PUB15].
Status of this Document
This is the 14 October 2005 version of the W3C Process Document. This document has been produced by the W3C Advisory Board and reviewed by the W3C Membersand Team.
The list of changes to the public Process Document is available on the Web.
W3C, including all existing chartered groups, follows the most recent operative Process Document announced to the Membership.
Please send comments about this document to process-issues@w3.org (Member-only archive).
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 Process Plan page. General information about W3C is available on the Web, including information about becoming a W3C Member.
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 RFC 2119[RFC2119]. The term NOT REQUIRED (not defined in RFC 2119) indicates exemption.
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.
Relation of Process Document to Patent Policy
W3C Members' attention is called to the fact that provisions of the Process Document are binding on Members per the Membership Agreement [PUB6]. The Patent Policy W3C Patent Policy [PUB33] is incorporated by normative reference as a part of the Process Document, and is thus equally binding.
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.
In the Process Document, the term "participant" refers to an individual, not an organization.
Table of Contents
- 1 Introduction
- 2 Members, Advisory Committee, Team, Advisory Board, Technical Architecture Group
- 3 General Policies for W3C Groups
- 4 Dissemination Policies
- 5 Activities
- 6 Working Groups, Interest Groups, and Coordination Groups
- 7 W3C Technical Report Development Process
- 8 Advisory Committee Reviews, Appeals, and Votes
- 9 Workshops and Symposia
- 10 Liaisons
- 11 Member Submission Process
- 12 Process Evolution
- 13 References
- 14 Acknowledgments
Expanded table of contents
- 1 Introduction
- 2 Members, Advisory Committee, Team, Advisory Board, Technical Architecture Group
- 2.1 Members
* 2.1.1 Rights of Members
* 2.1.2 Related Members
* 2.1.3 Advisory Committee (AC) - 2.2 The W3C Team
* 2.2.1 Team Submissions - 2.3 Advisory Board (AB)
* 2.3.1 Advisory Board Participation - 2.4 Technical Architecture Group (TAG)
* 2.4.1 Technical Architecture Group Participation - 2.5 Advisory Board and Technical Architecture Group Participation
* 2.5.1 Advisory Board and Technical Architecture Group Participation Constraints
* 2.5.2 Advisory Board and Technical Architecture Group Elections
* 2.5.3 Advisory Board and Technical Architecture Group Vacated Seats
- 2.1 Members
- 3 General Policies for W3C Groups
- 3.1 Individual Participation Criteria
* 3.1.1 Conflict of Interest Policy
* 3.1.2 Individuals Representing a Member Organization - 3.2 Meetings
- 3.3 Consensus
* 3.3.1 Managing Dissent
* 3.3.2 Recording and Reporting Formal Objections
* 3.3.3 Formally Addressing an Issue
* 3.3.4 Reopening a Decision When Presented With New Information - 3.4 Votes
- 3.5 Appeal of a Chair's Decision
- 3.6 Resignation from a Group
- 3.1 Individual Participation Criteria
- 4 Dissemination Policies
- 5 Activities
- 6 Working Groups, Interest Groups, and Coordination Groups
- 6.1 Requirements for All Working, Interest, and Coordination Groups
- 6.2 Working Groups and Interest Groups
* 6.2.1 Working Group and Interest Group Participation Requirements
* 6.2.2 Working Group and Interest Group Charter Development
* 6.2.3 Advisory Committee Review of a Working Group or Interest Group Charter
* 6.2.4 Call for Participation in a Working Group or Interest Group
* 6.2.5 Working Group and Interest Group Charter Extension
* 6.2.6 Working Group and Interest Group Charters
* 6.2.7 Working Group "Heartbeat" Requirement
* 6.2.8 Working Group and Interest Group Closure - 6.3 Coordination Groups
* 6.3.1 Coordination Group Participation Requirements
* 6.3.2 Coordination Group Creation and Closure
* 6.3.3 Coordination Group Charters
- 7 W3C Technical Report Development Process
- 7.1 Maturity Levels
* 7.1.1 Maturity Level for Work in Progress
* 7.1.2 Maturity Levels of the Recommendation Track
* 7.1.3 Maturity Level When Ending Work on a Technical Report
* 7.1.4 Maturity Level When Editing a Recommendation
* 7.1.5 Maturity Levels When Rescinding a Recommendation
* 7.1.6 Maturity Levels For Interest Group and Coordination Group Technical Reports - 7.2 General Requirements for Advancement on the Recommendation Track
- 7.3 Reviews and Review Responsibilities
- 7.4 Advancing a Technical Report to Recommendation
* 7.4.1 First Public Working Draft
* 7.4.2 Last Call Announcement
* 7.4.3 Call for Implementations
* 7.4.4 Call for Review of a Proposed Recommendation
* 7.4.5 Publication of a W3C Recommendation
* 7.4.6 Returning a Document to a Working Group for Further Work - 7.5 Ending Work on a Technical Report
- 7.6 Modifying a W3C Recommendation
* 7.6.1 Errata Management
* 7.6.2 Classes of Changes to a Recommendation
* 7.6.3 Call for Review of an Edited Recommendation
* 7.6.4 Call for Review of Proposed Corrections - 7.7 Rescinding a W3C Recommendation
* 7.7.1 Proposal to Rescind a Recommendation
* 7.7.2 Publication of a Rescinded Recommendation - 7.8 General Information about Technical Reports
* 7.8.1 Document Status Section
- 7.1 Maturity Levels
- 8 Advisory Committee Reviews, Appeals, and Votes
- 9 Workshops and Symposia
- 10 Liaisons
- 11 Member Submission Process
- 12 Process Evolution
- 13 References
- 14 Acknowledgments