Last Call
The W3C HTML Working Group is processing issues resulting from the Last Call period. Individuals are still welcome to send bug reports against our various documents. The W3C HTML Working Group also invites contributions to the growing HTML test suite, an important instrument for achieving interoperability.
To provide feedback on any of the Last Call Working Drafts, please see the instructions in the status section of each document:
- HTML5
- HTML+RDFa 1.1
- HTML Microdata
- HTML Canvas 2D Context
- Polyglot Markup: HTML-Compatible XHTML Documents
- HTML5: Techniques for providing useful text alternatives
The following working drafts are not a Last Call yet but are deliverables of the HTML Working Group that are also available for review.
Ongoing
At a recent W3C Advisory Committee meeting, there is a session where the HTML WG co-chairs reported to the W3C membership on the Working Group's status and progress.
A Last Call timeline message from the chairs includes details about the timeline for taking the HTML5 spec through Last Call.
Other ongoing activities include:
Bugs filed prior to 2011-08-03 Last Call bug-cutoff date:
- Bugs closed out in the last 30 days (moved to CLOSED or VERIFIED)
- Bugs with editor actions in the last 30 days (moved to RESOLVED)
- Bugs raised in the last 30 days with no editor actions yet (not moved to RESOLVED)
- Bugs raised more than 30 days ago with no editor actions yet (not moved to RESOLVED)
Issues:
Charter
The current HTML working group charter was issued on 7 March 2007. The group is chartered to continue its work through 31 December 2014.
See also W3C Relaunches HTML Activity press release and Architectural vision behind the HTML/XHTML2/Forms Chartering as well as pre-charter discussion such as Reinventing HTML: Update and HTML and Forms Activities Proposals (Call for Review) to W3C Members, and XHTML 2 Working Group Expected to Stop Work End of 2009, W3C to Increase Resources on HTML 5.
Specification
The HTML 5 draft specification was published as a Last Call Working Draft on 25 May 2011, as well as several other updated Working Drafts. The current editor’s draft of the HTML 5 specification is also available.
If you’re interested in tracking changes to the editor’s draft, a variety of mechanisms are available:
Milestones
Please refer to the Last Call timeline for details, but realize that we're a bit behind.
Membership and Participation
The HTML working group encourages active participation from a diverse community, including content authors and content providers, web developers, implementors (of browsers, authoring tools, conformance checkers, etc.) and anyone interested in helping to evolve the HTML language. A full list of participants is available. A number of HTML working-group members answered a background experience and expertise survey.
By charter, we operate primarily by email (see public-html archive), supplemented by web-based surveys, occasional teleconferences and up to two in-person meetings per year.
An issue-tracking task force is appointed by the chairs.
Phone Meetings
Teleconferences are scheduled for Thursdays at 12noon US/Eastern. Media Source and Encrypted Media are scheduled for Tuesdays at 11am US/Eastern. An agenda is due to public-html-wg-announce 24 hours in advance; we make heavy use of tracker's agenda page. Minutes are less formal than those of groups that regularly make binding technical decisions in teleconferences; they can be found on the HTML WG Wiki within a day or two.
See Scribe 101 for conventional W3C idioms and tools for using IRC to record meetings.
Face-to-Face Meetings
So far, we have been meeting once a year, during the W3C Technical Plenary.
- May 3-4, Mountain View, CA (logitics, registration, and agenda)
- TPAC 2011 in Santa Clara, California
- W3C TPAC 2010 in Lyon, France
- W3C TPAC 2009 in Santa Clara, California
- W3C TPAC 2008 (1 and 2) in Mandelieu, France
- first face-to-face meeting at W3C TPAC 2007 in Boston/Cambridge, Massachusetts
IRC
Some participants supplement public-html mailing-list discussions with IRC discussion in the #html-wg channel on irc.w3.org (port 6665 or port 80), with public logs and an informal directory with names and timezones.
Mailing lists
While the primary mailing list for the HTML Working Group is public-html, we're using several other ones for the task forces, announcements, or issue trackings. A full list of all HTML Working Group related mailing lists is available.
How to join
This Working Group operates under the W3C Patent Policy. The goal of this policy is to assure that Recommendations produced under this policy can be implemented on a Royalty-Free (RF) basis.
In order to carry out the Royalty Free policy, joining the HTML Working Group involves more than typical email subscription:
-
If you're affiliated with a
W3C member organization
- Use the form for getting a W3C account
- Have your AC representative nominate you using the form for joining this Working Group.
- Otherwise, the process involves getting an account and filling out a form for copyright, patent, etc. policies.
When you join, you will be subscribed to public-html, the publicly archived mailing-list for the group. Consistent failure to follow the Discussion Guidelines will result in removal from the working group. Please use the tasks survey to let us know a little bit about yourself and which tasks you're most interested to help with.
This process is somewhat new and novel, and the discussion around it led us to develop Frequently Asked Questions (FAQ) about Public Invited Experts in the W3C HTML Working Group. For example: I want to participate as an individual in the HTML Working Group but I work for a W3C Member. Why can't I join as an Invited Expert?
Patent Disclosures
W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent.
Tracker
An issue-tracking task force is appointed by the chairs.
The issue-tracking task force is currently using the W3C Tracker for its work. A summary of the status of each issue is being maintained.
Here are some links to specific parts of the Tracker:
The public-html-wg-issue-tracking@w3.org mailing list is the mailing list for the task force, and is publicly archived.
Decision History
The Working Group has a decision policy, and the Group is currently applying it. That decision policy contains an Enhanced Change Control section that describes how a working-group member can request a revert of a specific change that an editor has made to a specification.
- 2012-07-31: object-content-model
- 2012-07-31: enhance-time
- 2012-07-19: aria-processing
- 2012-07-18: caret-location-api
- 2012-07-17: Add a data element
- 2012-05-09: Reference a W3C version of DOM Parsing and Serialization
- 2012-03-30: accept-file-ext
- 2012-03-30: ua-http-resp-handling
- 2012-03-30: title-alternative
- 2012-03-20: inaccessible-example
- 2012-03-26: coding-example
- 2012-03-20: title-attribute
- 2012-03-20: generic-track-format
- 2012-03-20: validity-stability
- 2012-03-20: footnote-recommendation
- 2012-03-20: av_param
- 2012-03-07: time syntax
- 2012-02-07: ietf-id-wip
- 2011-05-24: 6 Documents proceed to Last Call (objection responses)
- 2011-04-18: Provide detailed instructions and examples for the
alt
andtitle
attributes to all readers of the HTML specification - 2011-04-18: Adopt revised text for the first two paragraphs of the
img
element definition - 2011-04-18: The presence of
aria-labelledby
,role
=presentation
or use of private communications does not, in itself, make missingalt
conforming. The presence ofmeta
name
=generator
,title
, andfigcaption
does make missingalt
conforming - 2011-04-13: Enable all users to distinguish the cells of a table
- 2011-04-11: Modify existing Canvas 2D API caret and focus ring support to drive screen magnification with two specific exclusions (selection of diff)
- 2011-04-08: Consider the inability to play at a given playback rate a hardware limitation and don't expose it via a dedicated API
- 2011-04-08: Define the
u
element as conforming - 2011-04-08: Defer to the Microformats community for cataloging HTML rel values
- 2011-04-05: Drop the
summary
="" attribute (in favor of thearia-describedby
attribute) - 2011-04-02: Add a link to the HTML to platform accessibility API implementation guide
- 2011-03-31: Clarify that
application/octet-stream
should be treated just like any other MIME type - 2011-03-29: The
video
poster
is conceptually part of the media resource itself. Any short text alternative should apply to the resource as a whole, not just the poster image. - 2011-03-29: Move advice about providing
alt
text for "purely decorative images" out of the HTML5 spec - 2011-03-29: Clarify how prefixes work in RDFa, and document that they're an optional feature
- 2011-03-24: Move the acknowledgement of the microdata usability study from the W3C HTML5 spec into the Microdata spec
- 2011-03-24: Reserve the term "conforming HTML5 document" for documents that conform to the HTML5 specification itself (i.e., no applicable specs)
- 2011-03-24: Not to require backslashes to be processed as escapes in
Content-Type
headers inmeta
elements - 2011-03-20: Provide a direct link to the W3C
canvas
2d context spec - 2011-03-19: Allow attributes on
link
anda
elements to have different effects - 2011-03-19: Don't permit
noreferrer
andnofollow
asrel
attribute values onlink
elements - 2011-03-19: Retain
progress
element - 2011-03-19: Make
Content-Language
pragma non-conforming - 2011-03-19: Explain within the HTML5 spec how to translate input strings contained in text/html documents into URIs
- 2011-03-15: Treat
figure
as being equivalent top
oraside
- 2011-03-15: Change the note after "algorithm for extracting an encoding from a Content-Type" to not mention HTTP
- 2011-03-15: Use RFC 135 as the reference for ASCII character set in terms of Unicode code points
- 2011-03-11: replace
<
video
auto
=muted>
with<
video
muted
>
- 2011-03-10: Make
role
="presentation
" on thetable
element conforming - 2011-03-10: Move a
table
example to a separate section - 2011-03-07: Adopt the "Change the title of the WAI-ARIA section of the HTML5 spec and provide advice about ARIA scope" Change Proposal
- 2011-02-28: Adopt the ARIA in HTML5: change some
role
mappings Proposal (with a number of specific exclusions) - 2011-02-28: Drop support for
rel
="" values - 2011-02-22: Retain Common Idioms section
- 2011-02-03: Don't provide an explicit means for others to define custom elements and attributes within HTML markup
- 2010-12-14: Don't add
nonav
attribute, don't add image maps as alternative, keep navigable canvas DOM - 2010-12-14: Don't put a versioning indicator in the
DOCTYPE
- 2010-12-07: Retain
meter
element - 2010-10-13: Retain
srcdoc
attribute - 2010-10-13: Document XML escaping requirements for the
srcdoc
attribute - 2010-08-11: Don't include the
longdesc
attribute in the language (reopened) - 2010-07-20: Keep
hidden
attribute - 2010-06-01: Keep
aside
element - 2010-06-01: Keep
figure
element - 2010-06-01: Remove image-analysis heuristics
- 2010-06-01: Remove Atom conversion
- 2010-03-11: Make
meta
/@
name
="keywords"
conforming - 2010-03-04: Remove
ping
attribute from HTML5 - 2010-03-04: Don't include
profile
attribute on thehead
element - 2010-01-07: Separate Microdata from HTML5 Specification
- 2009-11-19: Adopt Proposed Decision Policy
- 2008-05-27: Release Offline Web Applications intro/tutorial as a W3C Working Group Note
- 2008-01-18: Release HTML5 specification as a W3C First Public Working Draft
- 2007-12-06: Accept requirement for immediate-mode graphics a la canvas element
- 2007-11-16: Release HTML Design Principles as a W3C First Public Working Draft
- 2007-05-09: Adopt HTML5 draft as our specification text for review, use “HTML5” as the name of the spec, confirm Ian Hickson as David Hyatt as the editors of the spec
See also messages from the chairs such as Decision process: Formal Objections and consensus in the W3C process, on consensus and decision-making, proposal to release "HTML 5 differences from HTML 4" does not carry, and the draft of the decision policy.
Beyond HTML5
We try to keep track of request for future enhancements to HTML, including existing known markup extensions: