W3C home > Mailing lists > Public > public-html-xml@w3.org > January 2011

Re: XForms Use Case

From: Kurt Cagle <kurt.cagle@gmail.com>
Date: Wed, 12 Jan 2011 14:24:13 -0500
Message-ID: <AANLkTik0=bxSZ1062pEYrNSzGoZthZ+nHK316HkTO1Xf@mail.gmail.com>
To: "Edward O'Connor" <hober0@gmail.com>
Cc: Michael Kay <mike@saxonica.com>, "public-html-xml@w3.org" <public-html-xml@w3.org>
Edward,

It's not irrelevant because you can use XHTML, it's (most likely)
> irrelevant because the Web platform already has a widely deployed forms
> language: HTML's forms.
>
>
My bed and butter work - first for US National Archives, now (most likely)
for the Library of Congress - is dealing with complex form content with
constraints and dependencies. HTML forms work reasonably well in a lot of
cases, if you're willing to spend a great deal of time and energy writing
Javascript bindings for the various form elements, but once forms get beyond
a certain level of complexity (and it's not very high) such coding can be
very fragile and subject to enormous errors, not all of which are
syntactical.

XForms works well in those environments, in part because you are formally
separating the data model from the presentation from the control
architecture. Combine that with XML data sources (from syndication feeds to
XML Database content), and you can rapidly create very sophisticated
applications that not only maintain data validity but also insures that
complex structures can be created or maintained, something which HTML forms
generally don't do.

I would invite you to take a look at what's actually happening in the XForms
space before blithely dismissing it as irrelevant.

Kurt Cagle
W3C XForms WG
Received on Wednesday, 12 January 2011 19:25:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 January 2011 19:25:16 GMT