- From: Dan Connolly <connolly@w3.org>
- Date: Wed, 02 May 2007 19:33:59 -0500
- To: John Boyer <boyerj@ca.ibm.com>
- Cc: Dave Raggett <dsr@w3.org>, www-archive@w3.org
On Fri, 2007-04-27 at 10:39 -0700, John Boyer wrote: > > Hi Dan, > > Actually, the original material you posted to me was a cut and paste > from the HTML WG charter, and my response included some of that but I > didn't make up a lot of new words. They were cut and paste wordings > from the Forms WG charter and the vision document, with enough glue > words to make it reasonable. > > So, for example, the verbatim quote you asked for comes from > http://www.w3.org/2007/03/html-forms-vision.html, 3rd option (the > option selected by W3M), third paragraph. This document reflects the > W3M's understanding of what they wrote into the charters. > > The 'enterprise markets' material is lifted from the Forms WG charter, > first sentence (http://www.w3.org/2007/03/forms-charter.html). > > Based on these sources, would you consider continuing to hone and > refine the draft of text I sent earlier? OK, here's what I came up with: Our charter calls for a joint task force with the Forms Working group... The HTML WG and the Forms Working Group will work together in this Task Force to ensure that the new HTML forms and the new XForms Transitional have architectural consistency and that document authors can transition between them -- http://www.w3.org/2007/03/HTML-WG-charter.html The Forms Working group Charter notes: Previous work on XForms 1.0 has found success in the enterprise market -- http://www.w3.org/2007/03/forms-charter.html Meanwhile, the Web Forms 2 specification specifies an extension to the forms features found in HTML4's Forms chapter and the corresponding DOM2 HTML interfaces. HTML4, XHTML1.1, and the DOM are thus extended in a manner that has a clear migration path from existing HTML forms, leveraging the knowledge authors have built up with their experience with HTML so far. An architectural vision document released with the charters elaborates: The charter calls for two equivalent serializations to be developed, corresponding to a single DOM (or infoset, though tag soup cannot be considered to have an infoset currently, while it can have a DOM). This ensures that decisions are not made which would not preclude an XML serialization. It allows the two serializations to be inter-converted automatically. Having new language features, there is an incentive for content authors to use it; and having client-side implementations means that there is the possibility to really use it. -- http://www.w3.org/2007/03/vision.html The HTML WG task survey includes a "forms task force" checkbox; please check it if you'd like to participate. http://www.w3.org/2002/09/wbs/40318/tasks83/ -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Thursday, 3 May 2007 00:34:05 UTC