XForms 1.1 First Edition Errata
This document provides a group editable area for preparing the technical content of the errata for XForms 1.1 First Edition. Eventually, this content will be used to prepare an updated version of the XForms 1.1 Errata.
This document is intended to contain errata that the W3C Forms Working Group has resolved to add.
Diff markings are denoted as follows: added text,
deleted text, changed text.
Erratum 1: The xsd:duration and xforms:duration datatypes are supported
The specification states that xsd:duration is not supported in XForms. However, this is not true in practice since an XForms processor inherits the capability from the XML Schema engine, and any capability available from the xsi:type attribute is also available to the XForms type model item property. Moreover, the intention of the xforms:* datatypes is to provide a consistent authoring alternative guaranteed to allow empty string as valid content. This erratum fixes these problems with amendments allowing both xsd:duration and xforms:duration datatypes in XForms processors.
XForms supports all XML Schema 1.0 datatypes except for
xsd:duration, xsd:ENTITY, xsd:ENTITIES, and xsd:NOTATION.
The built-in datatype xsd:duration does not support a total ordering. Form authors are encouraged to use xforms:dayTimeDuration or xforms:yearMonthDuration instead.
Built-in primitive types (in the XForms namespace):
Erratum 2: The UI Common elements can appear before and after List UI Common elements
The specification does not reflect the natural tendency to place UI Common elements such as help, hint, alert and XForms actions immediately after the label and before List UI Common content. Due to support in known XForms processors, the specification and the XForms 1.1 Schema are amended to reflect this common authoring practice.
In the XForms Core Forms Controls Module table, amend the Minimal Content Model column for the rows for the select and select1 controls as follows:
label, (UI Common)*, (List UI Common)+, (UI Common)*
Erratum 3: Typo in Glossary Term
Correct typo in definition of Valid node (http://www.w3.org/TR/xforms11/#def-valid-node).
...(including those associated by
t the type model item property...
Erratum 4: Typo in Example of insert Action
Add missing close quote in example of insert action (http://www.w3.org/TR/xforms11/#action-insert).
Erratum 5: Remove Unreferenced Citation
The informative XForms Basic is not referenced anywhere in the specification, so it is being removed.
Appendix A.2 Informative References
XForms Basic Profile, Micah Dubinko, T. V. Raman, 2003. W3C Candidate Recommendation available at: http://www.w3.org/TR/2003/CR-xforms-basic-20031014/.
Erratum 6: Cite Informative Reference
The specification contains an informative reference to ODF due to a reference in the abstract. The abstract is changed to create reference links to XHTML, ODF and SVG,
Erratum 7: Statement of Conformance to Informative Schema
The specification states that fragments of XForms must conform to the Schema for XForms, but the schema is non-normative, so the sentence is amended to indicate that the fragments are expected to be valid according to the schema.
Individual XForms fragments are expected to be schema-valid according to the Schema for XForms...
Erratum 8: Disambiguation of case Element
Since both the switch element and the toggle element have a child case element, a community member requested a forward reference from the switch case to the toggle element for disambiguation.
... The attribute selected determines the initial selected state. The selected case can be changed with the toggle action, which uses a case attribute or a case child element to make an ID reference to the case of the switch to select.
Erratum 9: Items with empty/spaces values selectable in select1
The select element does not select an item having an empty or a spaces-only value because space separation is used for multiple item selection. Although the same rule is stated for select1, it is inconvenient and implementations do not support it due to the need in forms to allow a single selection item that restores an empty data value. The select element has no similar need since an empty value can be restored by deselecting all items. Therefore, the difference in behavior between select and select1 is warranted to allow both elements to achieve the same effect.
For both closed and open selections, any selection item with a storage value which is empty or which contains only white space characters
must remain deselected is deemed to be selected if the bound data node value exactly matches the storage value of the selection item. Furthermore, selecting a selection item with a storage value which is empty or which contains only white space characters places the storage value into the bound data node value.
Erratum 10: Typo in load action description
The load element can have a resource child element, not a name child element. The subsection link is correct on the word name, but it should say resource.
The URI specifying the link to traverse may be pointed to by the Single Node Binding attributes, if given, or by the resource attribute or the resource child element.
Erratum 11: Typo in dispatch action description
chlid child element.
Erratum 12: Typos in insert and delete action attribute descriptions
Section 10 (content model table, attribute descriptions)
insert ... context (node XPath Expression) ... origin (nodeset XPath Expression)
delete ... context (node XPath Expression) ...
Erratum 13: Clarify timezone adjustment is sensitive to dateTime being adjusted
The function adjust-dateTime-to-timezone() adjusts a given dateTime to the end-user's local timezone. This includes application of a daylight savings time adjustment. It is reasonably clear that the normative examples are expected to produce the return results at all times, not just when the end-user uses the form in the summer. This erratum further clarifies that the daylight savings time adjustment is not according to the current date and time for the end-user but rather whether daylight savings time is locally in effect at the date and time of the input parameter.
Section 7.9.8 function description
This function adjusts a legal lexical
xsd:dateTime received as the parameter to the local time zone for the user of the implementation, and returns the result. The application of daylight savings time is dependent on whether daylight savings time is in effect for the local time zone at the given date and time. "Local" or untimezoned times are presumed to be the time in the local time zone. If the implementation does not have access to time zone information, UTC is used. The result is empty string if the string argument is the empty sequence or not a legal lexical
Section 7.9.8 first example
2007-10-07T02:22:00-07:00 in the Pacific time zone since daylight savings time applies to the date
2007-10-02 in the Pacific time zone.
Section 7.9.8 second example
2007-10-02T14:26:43-07:00 in the Pacific time zone since daylight savings time applies to the date
2007-10-02 in the Pacific time zone.
Section 7.9.8 third example
Computes two hours from now, returning the result in the local time zone. For example, if
2007-10-02T21:26:43Z and the local date and time is
2007-10-02T14:26:43-07:00 in the Pacific time zone, then the above expression returns
Section 7.9.8 add new last example below
adjust-dateTime-to-timezone(seconds-to-dateTime(seconds-from-dateTime('2007-10-02T14:26:43-07:00') + 61*86400))
2007-12-02T13:26:43-08:00, which is the date and time two months (61 days) from the date
2007-10-02T14:26:43-07:00 in the Pacific timezone, adjusting the result for the fact that daylight savings time no longer applies to the resultant date in the Pacific timezone. Note that the hour component is
14 and the timezone offset is
Erratum 14: Dynamic dependencies and computed expressions
The definition of dependency is changed for computed expressions to reflect the current common practice of implementing the recalculation dependency graph algorithm. When the definition of a 'reference' was added to XForms 1.1, it was recognized that a future version of XForms may require a stricter definition for recalculation purposes. It has since been found that a slightly stricter definition is needed to avoid excessive circular dependencies.
Section 7.3 implement stricter definition for computed expressions
If an XPath expression other than a computed expression references an instance node, then the expression
result is dependent on the instance node. If a computed expression references an instance node and uses its character content (rather than just referencing for navigation), then the computed expression is dependent on the instance node. A dependency list for an instance node is the list of XPath expressions of a given category that are dependent upon the instance node. For example, in Section 4.3.2 The xforms-recalculate Event, the dependency list of computed expressions for each instance node helps establish the recalculation order for the computed expressions when the values of instance data nodes are changed.
Section 7.3 remove note
Defining a reference in terms of matching a NodeTest ... Moreover, the excess references created by the definition may cause some recalculation constructs to cease operation due to circular references that would not be created with a stricter definition of a reference. A future version of XForms may use a stricter version of referencing for recalculation and a less strict definition of referencing for the purpose of detecting and performing automatic rebuild operations.