View source for XForms 1.1 First Edition Errata

'''XForms 1.1 First Edition Errata'''

This document provides a group editable area for preparing the technical content of the errata for [http://www.w3.org/TR/2009/REC-xforms-20091020/ XForms 1.1 First Edition].  Eventually, this content will be used to prepare an updated version of the [http://www.w3.org/2009/10/REC-xforms-20091020-errata.html 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: <span style="background-color:yellow">added text</span>, <del style="background-color:red">deleted text</del>, <span style="background-color:lightgreen">changed text</span>.

----

==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.

'''''Specification Changes'''''

''<u>Section 5.1</u>''

XForms supports all XML Schema 1.0 datatypes except for <del style="background-color:red">xsd:duration,</del> xsd:ENTITY, xsd:ENTITIES, and xsd:NOTATION.

...

'''Note:'''

The built-in datatype xsd:duration <span style="background-color:lightgreen">does not support a total ordering. Form authors are encouraged to use</span> xforms:dayTimeDuration or xforms:yearMonthDuration <span style="background-color:lightgreen">instead</span>.

''<u>Section 5.2.1</u>''

Built-in primitive types (in the XForms namespace):

dateTime <br />
time <br />
date <br />
<span style="background-color:yellow">duration</span>  <br />
gYearMonth  <br />
...

----

==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 <u>UI Common</u> elements such as help, hint, alert and XForms actions immediately after the label and before <u>List UI Common</u> content. Due to support in known XForms processors, the specification and the XForms 1.1 Schema are amended to reflect this common authoring practice.

'''''Specification Changes'''''

''<u>Section 8.1</u>''

''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, <span style="background-color:yellow">(UI Common)*, </span>(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).

'''''Specification Changes'''''

''<u>Section 13</u>''

...(including those associated by<del style="background-color:red">t</del> 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).

'''''Specification Changes'''''

''<u>Section 10.3</u>''

...xforms:action ev:event="DOMActivate<span style="background-color:yellow">"</span>...

----

==Erratum 5: Remove Unreferenced Citation==

The informative XForms Basic is not referenced anywhere in the specification, so it is being removed.

'''''Specification Changes'''''

''<u>Appendix A.2 Informative References</u>''

<del style="background-color:red">'''XForms Basic'''</del>

<del style="background-color:red">XForms Basic Profile, Micah Dubinko, T. V. Raman, 2003. W3C Candidate Recommendation available at: http://www.w3.org/TR/2003/CR-xforms-basic-20031014/.</del>

==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,

'''''Specification Changes'''''

''<u>Abstract</u>''

... such as <span style="background-color:lightgreen">[[http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]], [[http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1-html/OpenDocument-v1.1.html ODF]] or [[http://www.w3.org/TR/2003/REC-SVG11-20030114/ SVG]]</span> ...

==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.

'''''Specification Changes'''''

''<u>Section 12.1</u>''

Individual XForms fragments <span style="background-color:lightgreen">are expected to</span> be schema-valid according to the Schema for XForms...

==Erratum 8: Disambiguation of case Element==

Since both the <u>switch</u> element and the <u>toggle</u> element have a child <u>case</u> element, a community member requested a forward reference from the <u>switch</u> <u>case</u> to the <u>toggle</u> element for disambiguation.

'''''Specification Changes'''''

''<u>Section 9.2.2</u>''

... The attribute selected determines the initial selected state. <span style="background-color:yellow">The selected ''case'' can be changed with the [http://www.w3.org/TR/xforms11/#action-toggle toggle] action, which uses a ''case'' attribute or a [http://www.w3.org/TR/xforms11/#action-toggle-case case] child element to make an ID reference to the ''case'' of the ''switch'' to select.</span>

==Erratum 9: Items with empty/spaces values selectable in select1==

The <u>select</u> 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 <u>select1</u>, 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 <u>select</u> element has no similar need since an empty value can be restored by deselecting all items.  Therefore, the difference in behavior between <u>select</u> and <u>select1</u> is warranted to allow both elements to achieve the same effect.

'''''Specification Changes'''''

''<u>Section 8.1.11</u>''

For both closed and open selections, any selection item with a storage value which is empty or which contains only white space characters <del style="background-color:red">must remain deselected</del> <span style="background-color:yellow">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.</span>

==Erratum 10: Typo in load action description==

The <u>load</u> element can have a <u>resource</u> child element, not a <u>name</u> child element.  The subsection link is correct on the word <u>name</u>, but it should say <u>resource</u>.

'''''Specification Changes'''''

''<u>Section 10.14</u>''

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 <span style="background-color:lightgreen">[http://www.w3.org/TR/xforms11/#action-load-resource resource]</span> child element.

==Erratum 11: Typo in dispatch action description==

Fix typo.

'''''Specification Changes'''''

''<u>Section 10.8</u>''

... <del style="background-color:red">chlid</del> <span style="background-color:yellow">child</span> element.

==Erratum 12: Typos in insert and delete action attribute descriptions==

Fix typos.

'''''Specification Changes'''''

''<u>Section 10</u> (content model table, attribute descriptions)''

<u>insert</u> ... context (node XPath Express<span style="background-color:yellow">i</span>on) ... origin (nodeset XPath Express<span style="background-color:yellow">i</span>on)

<u>delete</u> ... context (node XPath Express<span style="background-color:yellow">i</span>on) ...

==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.

'''''Specification Changes'''''

''<u>Section 7.9.8</u> function description''

This function adjusts a legal lexical <code>xsd:dateTime</code> received as the parameter to the local time zone<span style="background-color:yellow"> for the user</span> of the implementation, and returns the result. <span style="background-color:yellow">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.</span> "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 <code>xsd:dateTime</code>. 

''<u>Section 7.9.8</u> first example''

returns <code>2007-10-07T02:22:00-07:00</code> in the Pacific time zone since daylight savings time applies<span style="background-color:yellow"> to the date <code>2007-10-02</code> in the Pacific time zone</span>.

''<u>Section 7.9.8</u> second example''

returns <code>2007-10-02T14:26:43-07:00</code> in the Pacific time zone since daylight savings time applies<span style="background-color:yellow"> to the date <code>2007-10-02</code> in the Pacific time zone</span>.

''<u>Section 7.9.8</u> third example''

Computes two hours from now, returning the result in the local time zone. For example, if <code>now()</code> returns <code>2007-10-02T21:26:43Z</code> and the local date and time is <code>2007-10-02T14:26:43-07:00</code><span style="background-color:yellow"> in the Pacific time zone</span>, then the above expression returns <code>2007-10-02T16:26:43-07:00</code>

''<u>Section 7.9.8</u> add new last example below''


<div class="exampleInner">

<span style="background-color:yellow"> adjust-dateTime-to-timezone(seconds-to-dateTime(seconds-from-dateTime('2007-10-02T14:26:43-07:00') + 61*86400))</span>

</div>

<span style="background-color:yellow">Returns <code>2007-12-02T13:26:43-08:00</code>, which is the date and time two months (61 days) from the date <code>2007-10-02T14:26:43-07:00</code> 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 <code>13</code>, not <code>14</code> and the timezone offset is <code>-08:00</code>, not <code>-07:00</code>.
</span>

==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 [http://lists.w3.org/Archives/Public/www-forms/2011Jan/0001.html found] that a slightly stricter definition is needed to avoid excessive circular dependencies.

'''''Specification Changes'''''

''<u>Section 7.3</u> implement stricter definition for computed expressions''

If an XPath expression <span style="background-color:yellow">other than a [http://www.w3.org/TR/2009/REC-xforms-20091020/#def-computed-expression computed expression]</span> references an instance node, then the expression <del style="background-color:red">result</del> is '''dependent''' on the instance node.  <span style="background-color:yellow">If a [http://www.w3.org/TR/2009/REC-xforms-20091020/#def-computed-expression computed expression] references an instance node and uses its character content (rather than just referencing for navigation), then the [http://www.w3.org/TR/2009/REC-xforms-20091020/#def-computed-expression computed expression] is '''dependent''' on the instance node.</span> 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 [http://www.w3.org/TR/2009/REC-xforms-20091020/#evt-recalculate 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.

''<u>Section 7.3</u> remove note''

<del style="background-color:red">'''Note:'''</del>

<del style="background-color:red">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.</del>