HTML-WG-charter.html 19.2 KB

Raw Blame History Permalink

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
<head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
  <title>HTML Working Group</title>
  <style type="text/css">
      .nowork { display: none }
    </style>
  <link rel="stylesheet" href="http://www.w3.org/2005/10/w3cdoc.css"
  type="text/css" media="screen" />
  <link rel="stylesheet" type="text/css"
  href="http://www.w3.org/Guide/pubrules-style.css" />
  <link rel="stylesheet" type="text/css"
  href="http://www.w3.org/2006/02/charter-style.css" />
</head>

<body>

<div id="template">
<ul id="navbar" style="font-size: .6em">
  <li><a href="#scope">Scope</a></li>
  <li><a href="#deliverables">Deliverables</a></li>
  <li><a href="#coordination">Dependencies</a></li>
  <li><a href="#participation">Participation</a></li>
  <li><a href="#communication">Communication</a></li>
  <li><a href="#decisions">Decision Policy</a></li>
  <li><a href="#patentpolicy">Patent Policy </a></li>
  <li><a href="#about">About this Charter</a></li>
</ul>

<p><a href="http://www.w3.org/"><img alt="W3C" height="48"
src="http://www.w3.org/Icons/w3c_home" width="72" /></a> <a class="domainlogo"
href="http://www.w3.org/Interaction/"><img
src="http://www.w3.org/Icons/interaction" alt="Interaction Domain" /></a> </p>

<h1 id="title">HTML Working Group Charter</h1>

<p class="mission">The <strong>mission</strong> of the HTML Working Group, part
of the <a href="../../MarkUp/Activity">HTML Activity</a>, is to continue the
evolution of HTML (including classic HTML and XML syntaxes). </p>

<div class="noprint">
<p class="join"><a href="http://www.w3.org/2004/01/pp-impl/40318/join">Join the
HTML Working Group</a>.</p>
</div>

<table class="summary-table">
  <tbody>
    <tr id="Duration">
      <th rowspan="1" colspan="1">End date</th>
      <td rowspan="1" colspan="1">31 December 2014</td>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">Confidentiality</th>
      <td rowspan="1" colspan="1">Proceedings are <a
        href="/2005/10/Process-20051014/comm.html#confidentiality-levels">Public</a></td>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">Chair</th>
      <td rowspan="1" colspan="1"><em>Sam Ruby, IBM,<br />
Paul Cotton, Microsoft,<br />
Maciej Stachowiak, Apple</em>
      </td>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">Team Contact<br />
        (FTE %: 45)</th>
      <td rowspan="1" colspan="1"><em>Michael Smith, W3C/Keio</em></td>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">Usual Meeting Schedule</th>
      <td rowspan="1" colspan="1">Teleconferences: up to 1 per week, as needed
        <br />
        Face-to-face: up to 2 per year </td>
    </tr>
  </tbody>
</table>

<div class="scope">
<h2 id="scope">Scope</h2>

<p>This group will maintain and produce incremental revisions to the HTML
specification, which includes the series of specifications previously published
as XHTML version 1. Both XML and 'classic HTML' syntaxes will be produced.</p>

<p>The Group will define conformance and parsing requirements for 'classic
HTML', taking into account legacy implementations; the Group will not assume
that an SGML parser is used for 'classic HTML'.</p>

<p>The Group will monitor implementation of and conformance to the HTML
specification, construct test suites, and from them produce interoperability
reports.</p>

<p>The Group may hold Workshops, Interoperability Meetings, and other events as
required to fulfill its mission.</p>

<p>Data and canvas are reasonable areas of work for the group. On the one hand, they elaborate areas touched on in HTML4. On the other
hand, these elaborations are much deeper than the features of HTML4,
but also they form separate subsystems, and these subsystems have
strong overlaps with other design areas.</p>
<p>It is important that:</p>
<ol style='list-style-type: lower-alpha'>
<li>the design be modular;</li>
<li>the specifications be kept modular;</li>
<li>the communities of expertise of the respective fields (graphics and data) be involved in the design process.</li>
</ol>
</div>

<h3 id="success">Success Criteria</h3>

<div>
<p>The HTML Working Group's work will be considered a success if there are
multiple independent complete and interoperable implementations of its
deliverable that are widely used.</p>
<ul>
  <li>Production of stable documents addressing the work items listed in the <a
    href="#deliverables">Deliverables</a> section.</li>
  <li>Test suites for each deliverable with conformance criteria</li>
  <li>Availability of multiple, independent, interoperable implementations of
    each deliverable with conformance criteria;, as demonstrated by an
    implementation report (summarizing implementation status against the
    relevant test suite) for each testable class of product, including user
    agents</li>
  <li>Availability of authoring tools and validation tools.</li>
  <li>User community and industry adoption of the group deliverables.</li>
</ul>
</div>
</div>

<div>
<h2 id="deliverables">Deliverables</h2>

<h3>New publications and Milestones</h3>

<p>There is a single specification deliverable for the HTML Working Group, the
HTML specification, a platform-neutral and device-independent design with the
following items in scope: </p>
<ul>
  <li>A language evolved from HTML4 for describing the semantics of documents
    and applications on the World Wide Web. This will be a complete
    specification, not a <a
    href="http://www.w3.org/2005/07/13-pubrules-about#delta">delta
    specification</a>.
  </li>
  <li>An extensible, serialized form of such a language, using XML.</li>
  <li>A serialized form of such a language using a defined, non-XML syntax
    compatible with the 'classic HTML' parsers of existing Web browsers.</li>
  <li>Document Object Model (DOM) interfaces providing APIs for such a
  language.</li>
  <li>Forms and common UI widgets such as progress bars, datagrids, menus, and
    other controls.</li>
  <li>APIs for the manipulation of linked media.</li>
  <li>Editing APIs and user-driven WYSIWYG editing features.</li>
</ul>

<p>The following is a non-restrictive list of the
documents that are part of the deliverables of the Working Group:</p>

<ul id='spec_list'>
  <li><a href="http://www.w3.org/TR/html5/">HTML 5</a></li>
  <li><a href="http://www.w3.org/TR/rdfa-in-html/">HTML+RDFa</a></li>
  <li><a href="http://www.w3.org/TR/microdata/">HTML Microdata</a></li>
  <li><a href="http://www.w3.org/TR/2dcontext/">HTML Canvas 2D Context</a></li>
  <li><a href="http://www.w3.org/TR/html-markup/">HTML: The Markup Language</a></li>
  <li><a href="http://www.w3.org/TR/html5-diff/">HTML5 diffs from HTML4</a></li>
  <li><a href="http://www.w3.org/TR/html-polyglot/">Polyglot Markup: HTML-Compatible XHTML Documents</a></li>
  <li><a href='http://www.w3.org/TR/html-alt-techniques/'>HTML5: Techniques for providing useful text alternatives</a></li>
</ul>

<p>The HTML WG is encouraged to provide a mechanism to permit independently
developed vocabularies such as Internationalization Tag Set (ITS), Ruby, and
RDFa to be mixed into HTML documents. Whether this occurs through the
extensibility mechanism of XML, whether it is also allowed in the classic HTML
serialization, and whether it uses the DTD and Schema modularization
techniques, is for the HTML WG to determine.</p>

<p>The following features are expected to be obtained by integrating
deliverables of the <a href="/2006/webapi/">Web APIs Working Group</a>. They
are listed here so that they may be developed in the case where the Web APIs
Working Group is not able to produce the specifications.</p>
<ul>
  <li>Data storage APIs.</li>
  <li>Networking APIs for server-push, asynchronous two-way client-server
    communication, peer-to-peer communication, and client-side cross-domain
    communication.</li>
</ul>

<p>Note that some of the features mentioned above may be obtained by
integrating deliverables of the Web APIs Working Group. </p>

<h3 id="other">Other Deliverables</h3>

<p id="testsuite">The Group will create a comprehensive <em>test suite</em> for
the HTML specification. </p>

<p id="validate">The Group will ensure that<em>validation tools</em> are
available, possibly from third parties, for the HTML specification. Validation
does not mean DTD validation; validation using schemas (such as W3C XML Schema,
RelaxNG, Schematron) and validation which is tolerant of extensions in other
namespaces (for example using NVDL) is encouraged, as well as automated
checking of items from the specification prose.</p>

<p>The Group will monitor, track, and encourage implementation of HTML, both
during Candidate Recommendation and afterwards, to encourage adoption.</p>

<h3>Milestones</h3>

<table class="roadmap" width="80%">
  <caption>Milestones </caption>
  <tfoot>
    <tr>
      <td colspan="6" rowspan="1">Note: The group will document significant
        changes from this initial schedule on the <a
        href="http://www.w3.org/html/wg/">group home page</a>.</td>
    </tr>
  </tfoot>
  <tbody>
    <tr>
      <th rowspan="1" colspan="1">Specification</th>
      <th rowspan="1" colspan="1"><acronym
        title="First Working Draft">FPWD</acronym></th>
      <th rowspan="1" colspan="1"><acronym
        title="Last Call Working Draft">LC</acronym></th>
      <th rowspan="1" colspan="1"><acronym
        title="Canditate Recommendation">CR</acronym></th>
      <th rowspan="1" colspan="1"><acronym
        title="Proposed Recommendation">PR</acronym></th>
      <th rowspan="1" colspan="1"><acronym
      title="Recommendation">Rec</acronym></th>
    </tr>
    <tr>
      <th rowspan="1" colspan="1">HTML5 and <a href='#spec_list'>other deliverables</a></th>
      <td class="WD1" rowspan="1" colspan="1">N/A</td>
      <td class="LC" rowspan="1" colspan="1">2011 Q2</td>
      <td class="CR" rowspan="1" colspan="1">2012 Q2</td>
      <td class="PR" rowspan="1" colspan="1">2014 Q1</td>
      <td class="REC" rowspan="1" colspan="1">2014 Q2</td>
    </tr>
  </tbody>
</table>
</div>

<h2 id="coordination">Dependencies and Liaison</h2>

<p>The following is a list of known dependencies and liaisons with other W3C
groups at the time this charter was written. Liaison with other W3C groups can
take advantage of a broad range of mechanisms such as cross membership, reviews
of drafts produced by other groups, joint meetings etc., and whenever
appropriate, the HTML Working Group will also coordinate with groups not listed
here.</p>

<h3 id="dependencies">Dependencies</h3>
<dl>
  <dt><a href="http://www.w3.org/2006/webapi/">Web APIs Working Group</a></dt>
    <dd>HTML will integrate APIs developed by this Working Group</dd>
  <dt id="forms-tf">Forms Task Force</dt>
    <dd>The HTML WG and the <a
      href="http://www.w3.org/MarkUp/Forms/Group/">Forms Working Group</a> will
      work together in this Task Force to ensure that the new HTML forms and
      the new <dfn>XForms Transitional</dfn> have architectural consistency and
      that document authors can transition between them </dd>
</dl>

<h3 id="liaisons">Liaisons</h3>
<dl>
  <dt><a id="cdf" class="member" name="cdf"
  href="http://www.w3.org/2004/CDF/Group/">Compound Document Formats Working
  Group</a></dt>
    <dd>The HTML Working Group cooperates with this group to ensure that HTML
      can be readily combined with other W3C specifications</dd>
  <dt><a id="css" class="member" name="css"
  href="http://www.w3.org/Style/Group/">Cascading Style Sheets (CSS) Working
  Group</a> and <a id="xsl" class="member" name="xsl"
  href="http://www.w3.org/Style/XSL/Group/">Extensible Stylesheet Language
  (XSL) Working Group</a></dt>
    <dd>The work of the HTML Working Group will be coordinated with these
      groups on presentation issues.</dd>
  <dt><a id="hcg" class="member" name="hcg"
  href="http://www.w3.org/MarkUp/CoordGroup/">Hypertext Coordination
  Group</a></dt>
    <dd>The Hypertext Coordination Group is the primary place for the HTML
      Working Group for coordination with other Working Groups within the W3C.
      The Chair will participate in the regular Hypertext Coordination Group
      meetings and ensure that reviews between Working Groups are planned and
      carried out so as to meet requirements for deliverables and
    deadlines.</dd>
  <dt><a id="i18n" class="member" name="i18n"
  href="http://www.w3.org/International/Group/">Internationalization Working
  Group</a></dt>
    <dd>The HTML Working Group will cooperate with this group to ensure HTML
      provides effective support for internationalization.</dd>
  <dt><a id="tag" class="member" href="/2001/tag">Technical Architecture Group
  (TAG)</a> </dt>
    <dd>The HTML WG will liaise with the TAG, in particular regarding issue <a
      href="http://www.w3.org/2001/tag/issues.html?type=1#TagSoupIntegration-54">TagSoupIntegration-54</a>.</dd>
  <dt><a id="wai" name="wai" href="http://www.w3.org/WAI/">Web Accessibility
  Initiative (WAI)</a></dt>
    <dd>The HTML Working Group will cooperate with the Web Accessibility
      Initiative to ensure that the deliverables will satisfy accessibility
      requirements. Coordination with WAI will be primarily conducted through
      the <a href="http://www.w3.org/WAI/PF/">Protocol and Formats Working
      Group</a>, but direct coordination with other WAI groups, such as <a
      href="http://www.w3.org/WAI/GL/">Web Content Accessibility Guidelines
      Working Group</a> and <a href="http://www.w3.org/WAI/UA/">User Agent
      Accessibility Guidelines Working Group</a>, will also be done when
      appropriate.</dd>
</dl>

<div id="conformance">
<p>Furthermore, HTML Working Group expects to follow these W3C
Recommendations:</p>
<ul>
  <li><a href="/TR/qaframe-spec/">QA Framework: Specification
  Guidelines</a>.</li>
  <li><a href="/TR/charmod/">Character Model for the World Wide Web 1.0:
    Fundamentals</a></li>
  <li><a href="/TR/webarch/">Architecture of the World Wide Web, Volume
  I</a></li>
</ul>
</div>

<h2>Relationship to External Groups</h2>
<dl>
  <dt>Web Hypertext Application Technology Working Group (<a
  href="http://www.whatwg.org/">WHATWG</a>)</dt>
    <dd>The HTML Working Group will actively pursue convergence with WHATWG,
      encouraging open participation within the bounds of the W3C patent policy
      and available resources.</dd>
</dl>

<div class="participation">
<h2 id="participation">Participation</h2>

<p>To be successful, the HTML Working Group is expected to have active
participation of a diverse community for its duration. If fewer than three
implementors (i.e., browser vendors) are participating in the Working Group,
its charter should be re-examined by the W3C. </p>

<p>The co-chairs and specification Editors are expected to contribute one to
two days per week towards the Working Group. There is no minimum requirement
for other Participants. The Team Contact is expected to spend 0.5FTE for the
duration of the Working Group, which will be supplemented by other members of
the W3C team (management, communications, systems support) in order to support
participation by a large community. </p>

<p>W3C Members may join the Working Group using the regular W3C process. </p>

<p>The HTML Working Group also welcomes participation from non-Members. This
may take the form of questions and comments on the mailing list or IRC channel,
for which there is no formal requirement, or technical submissions for
consideration, for which the participant must agree to Royalty-Free licensing
under the W3C Patent Policy. </p>
</div>

<div class="communication">
<h2 id="communication">Communication</h2>

<p>This group primarily conducts its technical work on a Public mailing list <a
href="http://lists.w3.org/Archives/Public/public-html/">public-html</a>. It is
referred to in the rest of this document as <em>the Working Group mailing
list</em>.</p>

<p>The <a href="http://lists.w3.org/Archives/Public/www-html/">www-html</a>
mailing list remains available for general discussion of HTML, including topics
outside the scope of this Working Group.</p>

<p>Information about the group (deliverables, participants, face-to-face
meetings, teleconferences, etc.) will be available from the <a
href="http://www.w3.org/html/wg/">HTML Working Group home page</a>.</p>
</div>

<div class="decisions">
<h2 id="decisions">Decision Policy</h2>

<p>As explained in the Process Document (<a
href="/Consortium/Process/policies#Consensus">section 3.3</a>), this group will
seek to make decisions when there is consensus. We expect that typically, an
editor makes an initial proposal, which is refined in discussion with Working
Group members and other reviewers, and consensus emerges with little formal
decision-making. However, if a decision is necessary for timely progress, but
after due consideration of different opinions, consensus is not achieved, the
Chair should put a question (allowing for remote, asynchronous participation
using, for example, email and/or web-based survey techniques) and record a
decision and any objections, and consider the matter resolved, at least until
new information becomes available. </p>

<p>This charter is written in accordance with <a
href="/Consortium/Process/policies#Votes">Section 3.4, Votes</a> of the W3C
Process Document and includes no voting procedures beyond what the Process
Document requires.</p>
</div>

<div class="patent">
<h2 id="patentpolicy">Patent Policy </h2>

<p>This Working Group operates under the <a
href="/Consortium/Patent-Policy-20040205/">W3C Patent Policy</a> (5 February
2004 Version). To promote the widest adoption of Web standards, W3C seeks to
issue Recommendations that can be implemented, according to this policy, on a
Royalty-Free basis.</p>

<p>For more information about disclosure obligations for this group, please see
the <a href="/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.</p>
</div>

<h2 id="about">About this Charter</h2>

<p>This charter for the HTML Working Group has been created according to <a
href="/Consortium/Process/groups#GAGeneral">section 6.2</a> of the <a
href="/Consortium/Process">Process Document</a>. In the event of a conflict
between this document or the provisions of any charter and the W3C Process, the
W3C Process shall take precedence.</p>

<p>2010-02-26: This charter has been annotated,
as <a href='http://lists.w3.org/Archives/Public/public-html/2010Feb/0871.html'>requested
by the W3C Director</a>.</p>

<p>2011-02-14: Removed old chair names, updated charter end date, list of specifications, and
milestones.</p>

<hr />
<address>
  <a href="http://www.w3.org/People/chris">Chris Lilley</a> &lt;<a
  href="mailto:chris@w3.org">chris@w3.org</a>&gt;, <a
  href="http://www.w3.org/People/Berners-Lee/">Tim Berners-Lee</a> &lt;<a
  href="mailto:timbl@w3.org">timbl@w3.org</a>&gt; <br />
  <span class="revinfo">$Revision: 1.30 $ of $Date: 2011/02/14 13:58:22 $ by $Author: plehegar $</span>
</address>

<p class="copyright"><a rel="Copyright"
href="/Consortium/Legal/ipr-notice#Copyright">Copyright</a>© 2006 <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.</p>
</body>
</html>