This chapter is currently under development and discussion in the XForms Working Group, and does not yet represent consensus.

One possibility is a record set control which allows users to add and delete records, where all of the records satisfy the same XForms Model.

This chapter sets out a core set of datatypes that all XForms Processors are expected to support. The XForms Model chapter describes the different ways that an XForms Model can be specified. For the purposes of this chapter, the most important distinction is "simple syntax" (defined by XForms) versus "Schema Syntax" (defined in [XSchema-1] and [XSchema-2]).

This chapter sets out a core set of datatypes that all XForms Processors support. The XForms Model chapter describes the different ways that an XForms Model can be represented.

The XForms namespace has the URI: http://www.w3.org/2002/01/xforms. Any future Working Drafts are expected to use a different identifier, though a final identifier will be allocated before XForms becomes a W3C Recommendation.

This is an optional library that supports a variety of common financial calculations for interest rates, monthly payments etc.

Binding is the glue that connects the separate pieces of XForms--the XForms Model, instance data, and form controls. The binding is independent of the user interface language used.

Binding is the glue that connects the separate pieces of XForms -- the XForms Model, instance data, and form controls. The binding is independent of the language used in the XForms Model (Schema or simple syntax) and also independent of the user interface language used.

XForms are an application of XML [XML 1.0], and have been designed for use within other XML vocabularies, in particular XHTML [XHTML 1.0]. This chapter discusses some of the high-level features of XForms that allow this specification to be used with other document types

Forms are an important part of the Web, and they continue to be the primary means of interactivity used by many Web sites. Web applications and eCommerce solutions have sparked the demand for better Web forms with richer interactions.

Forms are an important part of the Web, and they continue to be the primary means of interactivity used by many Web sites. Web applications and eCommerce solutions have sparked the demand for better Web forms with richer interactions. XForms are the response to this demand--extended analysis, followed by the creation of a new platform-independent markup language for online interaction between a XForms Processor and a remote entity.

W3C's XForms Recommendation is implemented in X-Smiles. It uses the the "http://www.w3.org/2002/xforms" - namespace. XForms can be embedded in XHTML, XSL FO, SMIL and SVG documents in X-Smiles.

Since their inception in 1993, HTML forms have come to form the underpinnings of user interaction on the World Wide Web (WWW).

We conclude this chapter with a summary of XForms features and highlight the consequent benefits over using traditional HTML forms for developing Web applications.

This section details how various aspects of the XForms architecture can be leveraged in meeting the accessibility design principles covered in Section 11.2.

The XForms specification is an application of XML [XML 1.0], and has been designed for use within other XML vocabularies, in particular XHTML [XHTML 1.0].

The widespread adoption of XML as the common means of exchanging structured information on the Internet has made XML an ideal choice for connecting disparate information technologies.

The previous sections have described the various XForms user interface controls for collecting data from the user. Data collection apart, user interface controls are used to trigger specific actions. In traditional visual interfaces, such controls manifest themselves as buttons.

XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three parts—XForms model, instance data, and user interface—it separates presentation from content, allows reuse, gives strong typing—reducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting.

We conclude this book with an overview of XForms features that ensure that Web applications are accessible to users with different needs and abilities.