The Web Hypertext Application Technology Working Group

Looking for feedback on HTML5

spacer Wednesday, 8th November 2006

The Web Standards Project, Lachy's Log, Molly.com and 456 Berea Street are collecting feedback on the HTML5 proposal.

If you want to send feedback, but don't want to join the WHATWG mailing list, then please submit comments to one of the above-mentioned posts. Members of the community have comitted to collecting and responding to all the feedback.

What's happening at the WHATWG

Our current main focus is on the Web Applications 1.0 specification, sometimes referred to as "HTML5" or "XHTML5".

Read the spec, send your feedback! We guarantee that all feedback will be responded to before the spec is considered "done".

What is the Web Hypertext Application Technology Working Group?

It is a loose unofficial collaboration of Web browser manufacturers and interested parties who wish to develop new technologies designed to allow authors to write and deploy Applications over the World Wide Web.

The working group mailing list is an open subscription public mailing list and anyone is welcome to contribute.

The focus of this working group is limited to technologies that will need to be directly implemented in Web browsers. It is not the right forum for very domain-specific proposals that would not be suitable for implementation in, for instance, Safari, Firefox, or Opera.

What are "Web Applications"?

The term "Web Application" in this context refers to applications accessed over the World Wide Web by using a Web browser. This group is not attempting to describe APIs for writing high-end sophisticated programs such as office productivity suites, graphics manipulation packages, or 3D games.

Some of the most famous examples of Web applications currently deployed are eBay and Amazon.

Aren't "Web Applications" already possible?

Yes. This working group aims to make their development easier, and hopes to specify new technologies that make it possible to make much prettier and more usable interfaces with less dependence on complex scripts, less dependence on server-generated pages, and a more seamless user experience.

For example, currently HTML forms do not specify a way to specify that a control is a required control that must be filled in before submission: such features have to be scripted explicitly.

What exactly are you working on?

The work is currently split between three specifications.

Web Forms 2.0 is targeted to the common needs of web authors. Advanced widgets like RTF controls, menus and toolbars are the domain of Web Applications 1.0. These drafts are in active development. Web Forms 2 is nearing maturity; proposals are currently being discussed and specified for Web Applications 1.

Web Controls 1.0 is intended to add functionality to Javascript and CSS that aid the creation of custom widgets. However, this will be influenced by the design and implementations of XBL2, and so will not be available in the near future.

Shouldn't this work be done at the W3C or IETF?

Many of the members of this working group are active supporters and members of the W3C and other standardization bodies. Parts of the work have already been submitted to the W3C, and the W3C has continued the work and published one of the WHATWG specifications as a working draft. We intend to work more closely with the W3C in future. The technical work is currently focused on developing the specifications to levels appropriate for the W3C Last Call stage.

Several members of this working group attended The W3C Workshop on Web Applications and Compound Documents. The position paper submitted by Opera and Mozilla represents the fundamental principles upon which the WHAT working group intends to operate.

Queries should be directed either to the mailing list or to Ian Hickson, who is acting as a spokesman for the group.
gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.