Last week, a breakaway faction of the World Wide Web Consortium (W3C) said its work on the Web Forms 2.0 specification is nearly done and put out a call for final comments. The splinter group, which includes browser makers Apple Computer, the Mozilla Foundation and Opera Software, calls itself WHAT-WG, or the Web Hypertext Application Technology Working Group.
The move brings a new entry into the race to take forms software to the next level, complicating efforts to create an open standards foundation for emerging Internet applications that could shape the competitive landscape in software development for years to come. It also marks a major new headache for the W3C, whose XForms recommendation, unveiled in 2003, has long been stymied amid resistance from proprietary software makers, especially Microsoft.
"At the moment it's mass confusion," said Dharmesh Mistry, chief technology officer of Newbury, UK-based EdgeIPK, which builds forms-based applications for clients in the financial services industry. "The W3C is saying the answer is XForms. Microsoft is saying it's XAML. Macromedia is saying its Flash MX. And Mozilla is saying it's XUL. If you look at it from the point of view of an organisation, you're not going to say, 'We're going to write our rich Internet applications in one language and the forms in XForms.'"
The battle illustrates chronic fissures in the politics of Web technology development, with substantial consequences for the continued relevance of open standards in electronic forms -- a ubiquitous tool that's used to gather information on the Web and in other digital applications.
Forms based on current Web standards are used in every Google search, every Amazon.com sale, every automated blog entry, every online tax payment, and every Web e-mail log-in.
Now the industry wants more sophisticated forms that can underlie new Internet application platforms, communicating more fluently with back-end databases and customer relationship management systems.
XForms versus Web Forms
Although XForms offers advances over current standards-based HTML forms, some W3C members worry that it faces an uphill battle because it isn't supported by the current generation of Web browsers. That means Web surfers using today's browsers will have to download and install a plug-in to make it work, slowing adoption.
Continued ...
We currently have a lot of government and financial institutions that do not check for new browsers, relying on code written in 2000 or earlier to determine if a browser is compatable. This discriminate against people who have new, current, and superior browsers. It can also be interpreted legally as conspiring with specific browser suppliers to create an illegal monopoly.
We need the courts to decide if that is acceptable (NO!) or if they will also conspire with illegal monopoly browser manufacturers.