- From: Mukund Balasubramanian <mukund@cs.stanford.edu>
- Date: Wed, 04 Oct 2000 13:36:34 -0700
- To: Dave Raggett <dsr@w3.org>, "www-forms@w3.org" <www-forms@w3.org>
I think the former option would be more helpful since HTML+JavaScript+DHTML brings with it its own set of problems. Anyways, I have an implementation of the same assuming that the Data Model is based on XML Schema with some annotations and I would Most certainly like to share it... if you are interested. The problem is that most of the intermediate steps lack standardization. For example, instance data is fine as long as there are no errors in the Instance.... But what about an invalid instance being representable as a prefilled form with error messages ? Has anybody thought about such issues.. because I am having to invent my own solutions. Mukund Balasubramanian Dave Raggett wrote: > On Fri, 22 Sep 2000, Simon Brooke wrote: > > > On Fri, 22 Sep 2000, you wrote: > > > Hi Simon > > > > > > ----- Original Message ----- > > > > > > > There is, in effect, no migration path. > > > > > > Afaik they plan to support legacy devices (current browser) using > > > JavaApplet-Technology. > > > > That's what I feared. > > The XForms working group is interested in migration paths, and in > ways to allow existing browsers to work with XForms in some manner. > One approach is for the server to map HTML forms data submitted by > an existing HTML browser, into XML data based upon a data model held > at the server. Another is to compile an XHTML+XForms page into > HTML+JavaScript and to exploit Dynamic HTML. > > Regards, > > -- Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett > tel/fax: +44 122 578 3011 (or 2521) +44 778 532 0444 (mobile) > World Wide Web Consortium (on assignment from HP Labs)
Received on Wednesday, 4 October 2000 04:03:12 UTC