author charles
Sun, 18 Dec 2016 19:19:59 +0100
changeset 217 1e7b17417e03
parent 103 5508dec95a6a
permissions -rw-r--r--
Additional missing comma etc identified by dsinger (thank you)
<!DOCTYPE html">
<html lang="en">
    <meta charset="utf-8">
<link rel="stylesheet" href="style/default.css" type="text/css">
<link rel="stylesheet" type="text/css" href=
<title>1 Introduction</title>
<link rel="contents" href="cover.html#toc">
<link rel="next" href="organization.html">
    <style type="text/css">
      .rfc2119 {font-variant:small-caps}
</style> <link href="" rel="stylesheet">
    <!--[if lt IE 9]><script src='undefined://'></script><![endif]-->
<div class="noprint">
<div class="navbar"><map name="navbar-top" title="Navigation Bar" id=
<p>[<a accesskey="n" rel="Next" href="organization.html">next chapter</a>]
&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>
<h1>Editor's draft proposed new W3C Process Document</h1>
<h2>1 <a name="Intro" id="Intro">Introduction</a></h2>
<div class="toc"></div>
<!-- this is for html2ps -->
<p>Most W3C work revolves around the standardization of Web technologies. To
accomplish this work, W3C follows processes that promote the development of
high-quality standards based on the <a href=
"policies.html#Consensus">consensus</a> of the Membership, Team, and public.
W3C processes promote fairness, responsiveness, and progress: all facets of the
W3C mission. This document describes the processes W3C follows in pursuit of
its mission.</p>
<p>Here is a general overview of how W3C standardizes a Web technology. In many
cases, the goal of this work is a <a href="tr.html#RecsW3C">W3C
Recommendation</a>, the W3C equivalent of a Web standard.</p>
<li>People generate interest in a particular topic (e.g., Web services). For
instance, Members express interest in the form of <a href=
"submission.html#Submission">Member Submissions</a>, and the <a href=
"organization.html#Team">Team</a> monitors work inside and outside of W3C for
signs of interest. Also, W3C is likely to organize a <a href=
"events.html#GAEvents">Workshop</a> to bring people together to discuss topics
that interest the W3C community. This was the case, for example, with Web
<li>When there is enough interest in a topic (e.g., after a successful Workshop
and/or discussion on an <a href="organization.html#ACCommunication">Advisory
Committee mailing list</a>), the Director announces the <a href=
"activities.html#ActivityDevelopment">development of a proposal for a new
Activity</a> or <a href="groups.html#WGCharterDevelopment">Working Group
charter</a>, depending on the breadth of the topic of interest. An <a href=
"activities.html#ActivityProposal">Activity Proposal</a> describes the scope,
duration, and other characteristics of the intended work, and includes the
charters of one or more <a href="groups.html#GAGeneral">Working Groups,
Interest Groups, and possibly Coordination Groups</a> to carry out the work.
W3C Members <a href="activities.html#ActivityCreation">review each Activity
Proposal</a> and the associated Working Group charters. When there is support
within W3C for investing resources in the topic of interest, the Director
approves the new Activity and groups get down to work. For the Web Services
Activity, the initial Activity Proposal called for one Working Group to work on
Web Services Architecture and one to work on a language for Web Services
Description. The Activity Proposal also incorporated an existing Working Group
(from another Activity) working on XML Protocols.</li>
<li>There are three types of Working Group participants: <a href=
"policies.html#member-rep">Member representatives</a>, <a href=
"groups.html#invited-expert-wg">Invited Experts</a>, and <a href=
"organization.html#Team">Team representatives</a>. Team representatives both
contribute to the technical work and help ensure the group's proper integration
with the rest of W3C. The <a href="groups.html#WGCharter">Working Group
charter</a> sets expectations about each group's deliverables (e.g., <a href=
"tr.html#Reports">technical reports</a>, test suites, and tutorials).</li>
<li>Working Groups generally create specifications and guidelines that undergo
cycles of revision and review as they <a href="tr.html#rec-advance">advance to
W3C Recommendation</a> status. The W3C process for producing these technical
reports includes significant review by the Members and public, and requirements
that the Working Group be able to show implementation and interoperability
experience. At the end of the process, the Advisory Committee reviews the
mature technical report, and if there is support, W3C publishes it as a
<a href="tr.html#RecsW3C">Recommendation</a>.</li>
<p>The Process Document promotes the goals of quality and fairness in technical
decisions by encouraging <a href="policies.html#Consensus">consensus</a>,
requiring reviews (by both Members and public) as part of the <a href=
"#Recs">technical report development process</a>, and through an <a href=
"acreview.html#ACAppeal">appeal process</a> for the Advisory Committee.</p>
<p>The other sections of the Process Document:</p>
<li>set forth <a href="policies.html#Policies">policies</a> for participation
in W3C groups,</li>
<li>establish two permanent groups within W3C: the <a href=
"organization.html#TAG">Technical Architecture Group (TAG)</a>, to help resolve
Consortium-wide technical issues; and the <a href=
"organization.html#AB">Advisory Board (AB)</a>, to help resolve Consortium-wide
non-technical issues, and to manage the <a href=
"processdoc.html#GAProcess">evolution of the W3C process</a>, and</li>
<li>describe other interactions between the <a href=
"organization.html#Members">Members</a> (as represented by the <a href=
"organization.html#AC">W3C Advisory Committee</a>), the Team, and the general
<div class="noprint">
<div class="navbar"><map name="navbar-bottom" title="Navigation Bar" id=
<p>[<a accesskey="n" rel="Next" href="organization.html">next chapter</a>]
&nbsp; [<a accesskey="c" rel="Contents" href="cover.html#toc">contents</a>]</p>