XForms

From Wikipedia, the free encyclopedia

For other uses, see XForms (disambiguation).

XForms is an XML format for the specification of a data processing model for XML data and user interface(s) for the XML data, such as web forms. XForms was designed to be the next generation of HTML / XHTML forms, but is generic enough that it can also be used in a standalone manner or with presentation languages other than XHTML to describe a user interface and a set of common data manipulation tasks.

XForms, much like XHTML 2.0 which is currently under development as of November 2006 and within which XForms will be embedded, differs from previous versions of XHTML. Because of this there is a learning curve for developers, but because XForms in general provides a large time savings for the development of enterprise quality web forms, it can be an attractive alternative for many uses.

XForms 1.0 (Second Edition) was made an official W3C Recommendation on 14th March 2006. An indispensable list of errata to the 1.0 specification is available, fully incorporated into the main specification as of the Second Edition. XForms 1.1, which introduces a number of improvements, is in progress as a W3C Working Draft as of November 2006.

1 Differences from HTML forms
2 Software support
3 Implementation technologies compared
4 XForms for Mobile Devices
- 4.1 Benefits
- 4.2 Mobile Implementations
5 References
6 External links

[edit] Differences from HTML forms

Unlike the original HTML forms, the creators of XForms have used a Model-View-Controller approach. The "model" consists of one or more XForms models describing form data, constraints upon that data, and submissions. The "view" describes what controls appear in the form, how they are grouped together, and what data they are bound to. CSS can be used to describe a form's appearance.

An XForms document can be as simple as an HTML form (by only specifying the submission element in the model section, and placing the controls in the body), but XForms includes many advanced features. For example, new data can be requested and used to update the form while it is running, much like using XmlHttpRequest/AJAX except without scripting. The form author can validate user data against XML schema data types, require certain data, disable input controls or change sections of the form depending on circumstances, enforce particular relationships between data, input variable length arrays of data, output calculated values derived from form data, prefill entries using an XML document, respond to actions in real time (versus at submission time), and modify the style of each control depending on the device they are displayed on (browser versus mobile versus text only, etc.). There is often no need for any scripting with languages such as JavaScript.

Like legacy forms, XForms can use various non-XML submission protocols (multipart/form-data, application/x-www-form-urlencoded), but a new feature is that XForms can send data to a server in XML format. XML documents can also be used to prefill data in the form. Because XML is a standard, many tools exist that can chop and modify data upon submission, unlike the case with legacy forms where in general the data needs to be parsed and manipulated on a case by case basis. XForms is itself an XML dialect, and therefore can create and be created from other XML documents using XSLT. Using transformations, XForms can be automatically created from XML Schemas, and XForms can be converted to legacy XHTML forms: this is basically how server side XForms work today.

[edit] Software support

At the time of this writing, no widely used web browser supports XForms natively. However, various browser plugins and client-side extensions exist. The following lists some client-side implementations:

The Firefox XForms extension [1] is part of the Mozilla Project, and is compatible with releases of FireFox and Mozilla, and is built with nightly builds on most platforms as well as of version 0.7 (March 2007). Full XForms 1.0 SE support is not complete but covers most of the specification with a notable exception of attribute-based repeating used in HTML tables.

IBM® Workplace Forms™ supports development and deployment of XForms-based pure XML forms. Trial downloads are available of an Eclipse-based visual design environment and a client-side viewer that can run XForms-based forms both in the web browser and as a standalone desktop application.

formsPlayer extends Internet Explorer 6+ to include not only support for the full XForms standard, but also provides DOM 2 Events, DOM 3 XPath, XML Events and the DOM 3 Implementation Registry. Note that the plug-in had some problems with the Microsoft Eolas IE ActiveX update, which has been resolved by a compatibility patch from Microsoft [2].

FormFaces is a pure JavaScript processor. This means that XForms+HTML can be sent directly to the browser where JavaScript translates XForms controls into regular HTML form controls and processes the bindings directly within the browser. FormFaces is compatible with browsers that implement XHTML 1.0, ECMAScript-262 3rd Edition, and DOM Level 2 which includes Internet Explorer, Netscape, Mozilla, Firefox, Opera, Konqueror, Safari, and NetFront.

Convex is another client-side solution for IE6. It uses a hidden Java applet and is available as open source from the Chiba project. It uses the same engine as the server-side solution (see below) but offering the experience of a local implementation.

The following implementations are pure client-side implementations that do not reside in a web browser:

IBM Workplace Forms supports the use of XForms-based pure XML forms within a web browser but also as a standalone application.

OpenOffice.org versions 2.0 and greater support XForms [3].

X-Smiles is a client-side Java implementation (open source license). X-Smiles supports XForms along with a lot of current XML languages, such as XHTML, CSS, and SVG.

DENG is a lightweight XML Browser Engine that compiles XForms into Flash. DENG has with support for CSS-3 and XForms.

PicoForms has a client-side Java browser implementation supporting XForms. They have demonstration versions of their processor with support for XHTML, CSS, XML Events, and XForms for J2ME-compatible mobile devices.

XForms can also be used today through various server-side technologies which convert XForms to HTML forms and other widgets (typically based on Ajax technology) on the fly and transparently to users. Implementations include:

Chiba (open source license)

Orbeon Forms (open source license)

The following implementations provide a server-side compiler that produces HTML and JavaScript from XHTML/XForms documents:

IBM Workplace Forms WebForm Server supports development and deployment of XForms-based pure XML forms with a zero footprint on the client-side by transforming to HTML and JavaScript and AJAX calls to facilitate dynamic behaviors described by the XForms-based document.

AJAXForms transforms XHTML/XForms to HTML with Javascript (open source license)

[edit] Implementation technologies compared

FormFaces, AJAXForms, Chiba and Orbeon Forms are based on Ajax technology. The amount of server-side and client-side processing varies across these implementations. For example, FormFaces provides 100% XForms client-side processing and data model updates via pure Ajax processing on the XForms standard. The others use server-side Java XForms processing transcoding to Ajax markup prior to delivering the content to the browser. Both techniques can work across browser. Each implementation is significantly different with respect to dependencies, scalability, performance, licensing, maturity, network traffic, offline capability, and cross browser compatibility. System architects should evaluate these constraints against their need to determine potential risks and objectives.

Plugins like FormsPlayer and other client-side technology can have some benefits as well: because they integrate themselves into the browser, they will work with existing server architectures, can be more responsive, require fewer server fetches. They can also present themselves in more user-friendly ways (i.e. controls that do not already exist in the browser, like sliding scales, can be added to a page), although the advent of JavaScript widgets is currently offsetting that benefit.

The tradeoff between server-side and client plug-in solutions is where the software is maintained; either each client must install the required plug-in, or the server architecture must change to accommodate the XForms transcoder engine language technology. It is in theory possible to mix both of these solutions, for instance testing the browser for a client-side XForms implementation and serving native XForms in that case, and defaulting to a server solution in other cases.

FormFaces provides a "zero software" solution on either the client or server: no new software needs to be installed on the client and the solution can be used in conjunction with any server-side architecture. This is possible because FormFaces is written 100% in Ajax. The tradeoff is that compared to other solutions, more JavaScript code is initially downloaded to the client (JavaScript can be cached on the client), and XML Schema validation is not yet supported.

All XForms implementations share the ability to integrate with Web 2.0 APIs such as Google Maps, Yahoo Traffic Alerts, Kiko Calendar, and Skype Voice Service.

[edit] XForms for Mobile Devices

[edit] Benefits

XForms provides specific benefits when used on mobile devices:

User interfaces using XForms require fewer round trips with the server and are in that sense more self contained than user interfaces using HTML 4 forms.
Capabilities of mobile devices vary greatly; consequently the amount of the work involved in generating different user interfaces for different devices is of particular concern in the mobile world. XForms has been designed from the ground up to allow forms to be described independently of the device, which reduces the amount of work required to target multiple devices.
XForms reduces the need for JavaScript, which is particularly interesting as JavaScript support varies greatly on mobile devices and cannot be widely relied on it.

[edit] Mobile Implementations

Despite the benefits of XForms for mobile devices, XForms on mobile devices is still an emerging technology at best. Jon S. von Tetzchner, CEO of Opera, producers of the leading browser for mobile devices, says his company is currently considering support for XForms but that in his mind Webforms 2.0 makes more sense on the client side. So far, IBM, Oracle and FormFaces have produced significant initiatives:

PicoForms Micro Edition Browser supports XForms and runs on cell phones supporting MIDP 2.0 and CLDC 1.x. It also supports PDAs including Palm and Pocket PCs.
IBM Forms for Mobile Devices is an implementation of XForms that run on Palm-powered devices and shows how XForms can be used to create form-based enterprise applications running on mobile devices. This package has been released by IBM on alphaWorks, their site showcasing emerging technologies.
Oracle Wireless Client has released a preview of their Wireless Client in March 2004. Despite its name, the preview contains no software that run on a mobile device. Instead, it is delivered in the form of a plug-in for Internet Explorer, hence maybe the "preview" in the name. The plug-in run XForms client-side, just like the browser would if it supported XForms natively.
FormFaces Mobile Solution is a 100% JavaScript implementation targeted to run within NetFront browser (any ECMA-262 3rd Edition, and DOM Level 2 compatible browser) which supports many OS deployments including Palm and Pocket PC mobile devices.

[edit] References

Wikibooks has a book on the topic of

XForms

T. V. Raman (2004). XForms: XML Powered Web Forms. Boston: Addison-Wesley. ISBN 0-321-15499-1.
Dubinko, Micah (2003). XForms Essentials. Sebastopol, CA; Farnham: O'Reilly & Associates. ISBN 0-596-00369-2. (text available under the GNU Free Documentation License)