The XML Guild

          where you find established XML experts . . .

Table of Contents

In XForms, form controls are abstracted from their particular implementation--moreso than HTML

e.g. <select1> (XForms) as opposed to <input type="radio"> (HTML)

A key benefit of this abstraction is accessibility and usability among a wider range of devices and user agents

Meant to be embedded in XHTML; replaces forms in XHTML 2.0

Minimization of the need for scripting... using declarative specification of XForms Actions tied to XML Events (candidate rec)

labels (marked as such) are *required* for every form control

XForms provides a single, high-level, two-way (round-trip) mapping between instance data (XML) and form controls/layout

Some products (e.g. Authentic) use a custom XML vocabulary (not XForms) to provide a single, high-level, two-way (round-trip) mapping between instance data (XML) and form controls/layout

Other products (e.g. Ektron) use XSLT to provide two one-way mappings:

• XML -> HTML
• Edited HTML -> XML

Still other products (e.g. InfoPath) use an annotated flavor of XSLT to provide...[two mappings? one mapping?] One mapping, or set of "bindings".

Tools to Investigate

coming soon . . .