Web Hypertext Application Technology Working Group Launches Mailing List

Friday June 4th, 2004

Ian Hickson writes: "Some of you may be interested to hear that people from Opera and Mozilla have set up an open mailing list for discussing Web Forms 2 and other new specs that have been discussed in various places over the last few months."

The list is the public forum of the newly-formed Web Hypertext Application Technology Working Group, an organisation made of contributors from several major Web browser development teams. Current invited members are Brendan Eich, David Baron, David Hyatt, Håkon Wium Lie, Ian Hickson, Johnny Stenback and Maciej Stachowiak.

The group is working on specifications for Web Forms 2.0, Web Apps 1.0, Web Controls 1.0 and a CSS object rendering model. This work will be largely done outside of the World Wide Web Consortium, though finalised versions of the specs are expected to be submitted for formal standardisation. While the decision to operate independently of the W3C may be seen as controversial, many feel that formal standards bodies move too slowly to react to proprietary technologies such as Microsoft's forthcoming XAML. In addition, many in the W3C are pushing for Web applications standards based on technologies such as XForms and Scalable Vector Graphics, whereas the members of the WHATWG favour backwards-compatible HTML-based solutions, which they believe would be easier to implement and more likely to be adopted by Web developers.

#30 Re: Disappointing news, IMO

by mlefevre

Monday June 7th, 2004 4:43 AM

You are replying to this message

I think you've missed the point on the SVG stuff. This is about building applications on top of a future version of SVG that isn't finished yet, not just about doing vector graphics - SVG 1.0 support wouldn't enable that anyway. AIUI, the stuff in current drafts of SVG 1.2 isn't compatible with existing concepts, making it pretty much impossible to implement as part of the browser - it'd work more like a Java applet, suitable to run as a plugin or separate app, not as something you'd use in a compound document.

"if and when all the major browsers support it, people can start developing pages using it"

Well that's the big issue. If one of the major browsers doesn't support it (for example, the one with the largest market share which is produced by someone making their own standard), then you're stuffed unless you can grab the market from them before you start.

Hixie's blog entry at <> makes the case in a more direct way than document linked from the article.