The opening paragraphs:
The purpose of XForms is to express the core XML data processing asset used in sophisticated data collection scenarios.To your Humble Editor's eyes, this reads something like this: XForms is a way to fill out an XML document in such a way that the document is valid, including validation by DTD or by Schema.
In fact, it would be better if XForms were called the XML data processing language (XDP or XDPL) because XML is about standardizing data and about 80% of business transactions are based on filling out some kind of form to collect the transactional data.
There's more to it, of course. Selected from the rest of the article:
XForms is all about thinking of the data first and driving outward to how that data gets exposed to applications. Perhaps the most prevalent of such applications are for presenting the data to a human user, though even human users have highly varied capabilities. For example, the desktop user and the PDA user have very different visual capabilities. Of course, this argument extends easily to meeting the far greater accessibility needs of the sight-impaired.
I sometimes get asked whether XForms will next extend itself to standardizing the actual presentation layer. Clearly, from above the answer is no. XForms standardizes the core XML data processing asset, and more work will go into doing a better job of that. The key issue we want is to address interoperability and reusability across applications and user contexts of the data processing behaviors that are fundamental to completing a transaction.
Have you used XForms? Whether you have or have not, what's your understanding of it? Is the specification useful to you?