XForms 1.0 Recommendation Errata

Current specification wording:

value

An XPath expression to be evaluated. The result of the evaluation is rendered by the form control.

Changed specification wording:

value

An XPath expression to be evaluated. The string result of the evaluation is rendered by the form control. If binding attributes are present to select a node, this attribute has no effect. The evaluation context is the same as would be applied to the evaluation of the single node binding. This XPath expression is re-evaluated whenever there is a change in any node to which the expression refers.

Current specification wording, section 4.2:

This section defines the various stages of the initialization phase. The processor begins initialization by dispatching an event xforms-model-construct to each XForms Model in the containing document.

Current specification wording, section 4.2.1:

Dispatched by the containing document processor to bootstrap XForms Processor initialization.

Changed specification wording, section 4.2:

This section defines the various stages of the initialization phase. The processor begins initialization by dispatching an event xforms-model-construct to each XForms Model in the containing document. How the XForms Processor itself is requested to initialise is implementation dependent.

Changed specification wording, section 4.2.1:

Dispatched to each XForms model by the XForms processor.

Current specification wording:

action

Required destination URI for submitting instance data.

Added specification wording (from section 3.2.2, Linking Attributes):

Behavior of relative URIs in links is determined by the host language, although [XML Base] processing is strongly recommended.

Current specification wording (in all the above sections but 10.1.11):

model

Required IDREF of the model to be processed.

Current specification wording, section 10.1.11 (The reset Element):

model

Required selection of instance data for reset, defined in 3.2.3 Single-Node Binding Attributes.

Changed specification wording:

model

Optional XForms Model selector, as defined in 3.2.3 Single-Node Binding Attributes.

Current specification wording:

value

Optional XPath expression to evaluate, with the result stored in the selected instance data node.

Changed specification wording:

value

Optional XPath expression to evaluate, with the result stored in the selected instance data node. The evaluation context for this XPath expression is the result from the Single Node Binding.

Current specification wording:

This action sets focus to the form control identified by attribute control by dispatching an xforms-focus event

Changed specification wording:

This action dispatches an xforms-focus event to the element identified by attribute control

Current specification wording:

The default action for these events results in the following:

focus is given to the target form control if the form control is able to accept focus.

Changed specification wording:

The default action for these events results in the following:

Focus is given to the target form control if the form control is able to accept focus. Setting focus to a repeating structure sets the focus to the repeat item represented by the repeat index.

Current specification wording:

Target: model

Changed specification wording:

Target: submission

Changed specification wording:

The xforms-submit-error is targeted at the submission element.

Current specification wording:

The sign of the result will match the sign of the duration. If no time zone is specified, an implementation default is used. Year and month components, if present, are ignored. Any other input parameter causes a return value of NaN.

Changed specification wording:

The sign of the result will match the sign of the duration. Year and month components, if present, are ignored. Any other input parameter causes a return value of NaN.

Clarify that all data items relevant to the XPath data models are relevant for XForms instances.

Current specification wording:

A node from the instance data is selected, based on attributes on the submission element. The indicated node and all nodes for which it is an ancestor are considered for the remainder of the submit process.

Changed specification wording:

A node from the instance data is selected, based on attributes on the submission element. The indicated node and all nodes for which it is an ancestor are considered for the remainder of the submit process. Any node which is considered not relevant as defined in 6.1.4 is removed.

Current specification wording:

If the parameter string matches none of the above strings, according to a case-insensitive comparison, processing stops with an exception (4.5.4 The xforms-compute-exception Event).

Changed specification wording:

If the parameter string matches none of the above strings, according to a case-insensitive comparison, the return value will be false.

Current specification wording:

show

Optional link behavior specifier.

Changed specification wording:

show

Optional link behavior specifier. If this attribute is missing, a default value of "replace" is assumed.

Current specification wording:

When it is time to recalculate a compute, the XPath expression is evaluated in the context of the instance node whose value or model item property is associated with the compute.

Changed specification wording:

When it is time to recalculate a model item property, the XPath expression is evaluated. The evaluation context is determined from the model binding expression that applied the model item property, as defined for computed expressions in 7.4 Evaluation Context.

Current specification wording:

This action adjusts all selected attributes on the affected cases to reflect the new state, and then performs the following:

Changed specification wording:

This action adjusts all selected states (not the attribute values) on the affected cases to reflect the new state of the switch containing the identified case

Current specification wording:

This element encloses markup to be conditionally rendered. The attribute selected determines the selected state and can be manipulated programmatically via the DOM, or declaratively via XForms Action toggle.

Changed specification wording:

This element encloses markup to be conditionally rendered. The attribute selected determines the initiel selected state.

Current specification wording:

  <xsd:element name="payment">
    <xsd:complexType name="payment">
      <xsd:sequence minOccurs="0" maxOccurs="unbounded">

Changed specification wording:

  <xsd:element name="payment">
    <xsd:complexType>
      <xsd:sequence minOccurs="0" maxOccurs="unbounded">

Current specification wording:

  <xsd:simpleType name="cc">
    <xsd:restriction base="xsd:string">
      <xsd:pattern value="\s*((\d+)[-\s])+([\d]+)\s*" />
    </xsd:restriction>
  </xsd:simpleType>

Changed specification wording:

  <xsd:simpleType name="cc"> 
     <xsd:restriction base="xsd:string"> 
       <xsd:minLength value="12"/> 
       <xsd:maxLength value="19"/> 
       <xsd:pattern value="[0-9]+"/> 
     </xsd:restriction> 
  </xsd:simpleType>

Current specification wording:

Attribute at is evaluated to determine the insertion index – a numerical value that is the index into the node-set. Attribute position specifies whether the new node is inserted before or after this index.

Changed specification wording:

Attribute at is evaluated to determine the insertion index – a numerical value that is the index into the node-set. The attribute at is evaluated with the first node in document order from the node set binding as the context node, the size of the node set binding as the context size and 1 as the context position. Attribute position specifies whether the new node is inserted before or after this index.

Target of events should include <itemset>.Current specification wording:

Target: item or case

Changed specification wording:

Target: item or itemset or case

Current specification wording:

1. All instance data nodes in all instance elements in the model are checked against any specified XML Schema.

Changed specification wording:

Definition: Local relevance is the relevance associated directly from the model item properties and not by inheritance.

1. All instance data nodes in all instance elements in the model are checked against any specified XML Schema and associated XML Schema datatypes by the following rules:

   1. The XML Schema validity of an element is determined by the local relevant attribute, element and text nodes. If the error code list exposed from the PSVI only contain the cvc-attribute.3 code then the element is still considered valid. This means that an invalid attribute value will not make its owner element invalid.

   2. The XML Schema validity of an attribute node is determined by the rules for Attribute Locally Valid as defined in the XML Schema specification.

   3. The XML Schema validity of a text node is defined as the locally validity of its normalized content with respect to the type definition associated from a model bind as defined by String Valid. If the text node has no type associated it is always considered valid.

Current specification wording:

If the string parameter represents a legal lexical xsd:date or xsd:dateTime, the return value is equal to the number of days difference between the specified date or dateTime (normalized to UTC) and 1970-01-01. Hour, minute, and second components are ignored after normalization. Any other input parameter causes a return value of NaN.

Changed specification wording:

If the string parameter represents a legal lexical xsd:date or xsd:dateTime, the return value is equal to the number of days difference between the specified date or dateTime normalized to UTC and 1970-01-01. Hour, minute, and second components are ignored after normalization. Any other input parameter causes a return value of NaN.

Current specification wording:

If the string parameter represents a legal lexical xsd:dateTime, the return value is equal to the number of seconds difference between the specified dateTime (normalized to UTC) and 1970-01-01T00:00:00Z. If no time zone is specified, UTC is used. Any other input string parameter causes a return value of NaN.

Changed specification wording:

If the string parameter represents a legal lexical xsd:dateTime, the return value is equal to the number of seconds difference between the specified dateTime normalized to UTC and 1970-01-01T00:00:00Z. If no time zone is specified UTC is assumed.

Current specification wording:

<select1 ref="@attr" ... />

Changed specification wording:

<select1 ref="@attr" ... >
  <label>...</label>
</select1>

Current specification wording:

<repeat nodeset="/cart/items/item">
  <input ref="." ... /><html:br/>
</repeat>

Changed specification wording:

<repeat nodeset="/cart/items/item">
  <input ref="." ...>
     <label>...</label>
  </input>
  <html:br/>
</repeat>

Added specification wording (before the note):

If, when creating the detached copy by having the instance inline, should fail because of an xml error then processing should halt with an xforms-link-exception. This could e.g. happen if the inline content had two element nodes which would imply creating an XML document with two document elements.

Current specification wording:

3. The index for this repeating structure is initialized to the value of startindex.

Changed specification wording:

3. The index for this repeating structure is initialized to the value of startindex. If the initial startindex is less than 1 it defaults to 1. If the index is greater than the initial node-set then it defaults to the size of the node-set.

Remove the specification wording:

Notice that an inner repeat's index always starts from 1.

Current specification wording:

Under no circumstances may more than a single concurrent submit process be under way for a particular XForms Model.

Changed specification wording:

Under no circumstances may more than a single concurrent submit process be under way for a particular XForms submission.

Current specification wording:

  <message level="modeless" ev:event="xforms-help" ev:propagate="stop>

Changed specification wording:

  <message level="modeless" ev:event="xforms-help" ev:propagate="stop">

Current specification wording:

Content-Type: multipart/form-data; boundary=AaB03x
Content-Length: xxx
        
--AaB03x
Content-Disposition: form-data; name="document"; filename="b.txt"
Content-Type: text/plain; charset=iso-8859-1
This is a file.
It has two lines.
--AaB03x
Content-Disposition: form-data; name="title"
Content-Type: text/plain; charset=iso-8859-1
A File
--AaB03x
Content-Disposition: form-data; name="summary"
Content-Type: text/plain; charset=iso-8859-1
This is my file
file test
--AaB03x--

Changed specification wording:

Content-Type: multipart/form-data; boundary=AaB03x
Content-Length: xxx
        
--AaB03x
Content-Disposition: form-data; name="document"; filename="b.txt"
Content-Type: text/plain; charset=iso-8859-1
This is a file.
It has two lines.
--AaB03x
Content-Disposition: form-data; name="title"
A File
--AaB03x
Content-Disposition: form-data; name="summary"
This is my file
file test
--AaB03x--

Current specification wording:

show

Optional link behavior specifier.

Changed specification wording:

show

Optional link behavior specifier. The default value is replace.

Current specification wording:

appearance

Optional attribute to define an appearance hint.

Changed specification wording:

appearance

Optional attribute to define an appearance hint. If absent, the user agent may freely choose any suitable rendering.

Current specification wording:

...

• For a success response including a body of an XML media type, when the value of the replace attribute on element submission is "instance", the response is parsed as XML and all of the internal instance data corresponding to the submitted instance is replaced with the result, using the same processing as remote instance data retrieved through src, and the xforms-model-construct event is dispatched to element model. Submit processing then concludes after dispatching xforms-submit-done.

Changed specification wording:

...

• For a success response including a body of an XML media type, when the value of the replace attribute on element submission is "instance", the response is parsed as XML and all of the internal instance data corresponding to the submitted instance is replaced with the result. Submit processing then concludes after doing the processing for rebuild, recalculate, revalidate and refresh, bypassing the normal event flow. Submit processing then concludes after dispatching xforms-submit-done.

Remove specification wording:

Section 11.1 says that submission revalidates selected instance data "taking into account only namespace nodes considered for serialization as described at 3.3.3 The submission Element"

Current specification wording:

Required reference to a case section inside the conditional construct.

Changed specification wording:

Required reference to a case element.

Current specification wording:

For a success response including a body of an XML media type...

Changed specification wording:

For a success response including a body of an XML media type (as defined by the content type specifiers in [RFC 3023])...

Current specification wording:

For a success response including a body of a non-XML media type...

Changed specification wording:

For a success response including a body of a non-XML media type (i.e. with a content type not matching any of the specifiers in [RFC 3023])...

Current specification wording:

  <xsd:element name="bind"> [...] <xsd:complexType> [...]
    <xsd:attribute name="maxOccurs" type="xforms:XPathExpression" use="optional" default="INF"/>
    <xsd:attribute name="minOccurs" type="xforms:XPathExpression" use="optional" default="0"/>
  [...] </xsd:complexType> [...] </xsd:element>

The attributes minOccurs and maxOccurs are removed.

Current specification wording:

Function avg returns the arithmetic average of the result of converting the string-values of each node in the argument node-set to a number. The sum is computed with sum(), and divided with div by the value computed with count(). If the parameter is an empty node-set, the return value is NaN.

Changed specification wording:

Function avg returns the arithmetic average of the result of converting the string-values of each node in the argument node-set to a number. The sum is computed with sum(), and divided with div by the value computed with count(). If the parameter is an empty node-set, or if any of the nodes evaluate to NaN, the return value is NaN.

Current specification wording:

 ...
  <bind type="my:nonEmptyString" nodeset="my:first-name"
      p3ptype="user.personname.given"/>

Changed specification wording:

 ...
  <bind type="my:nonEmptyString" nodeset="my:first-name"
      p3ptype="user.name.given"/>

Current specification wording:

1. If the selected index is 0 or less, an xforms-scroll-first event is dispatched and the index is set to 1. If the selected index is greater than the index of the last repeat item, an xforms-scroll-last event is dispatched and the index is set to that of the last item. The indexes for inner nested repeat collections are re-initialized to 1. The implementation data structures for tracking computational dependencies are rebuilt or updated as a result of this action.

Changed specification wording:

1. If the selected index is 0 or less, an xforms-scroll-first event is dispatched and the index is set to 1. If the selected index is greater than the index of the last repeat item, an xforms-scroll-last event is dispatched and the index is set to that of the last item. If the index evaluates to NaN the action has no effect. The indexes for inner nested repeat collections are re-initialized to 1. The implementation data structures for tracking computational dependencies are rebuilt or updated as a result of this action.

Current specification wording:

Element nodes selected for inclusion are encoded as EltName=value{sep}, where = is a literal character, {sep} is the separator character from the separator attribute on submission, EltName represents the element local name, and value represents the contents of the text node. Note that contextual path information is not preserved, nor are namespaces or namespace prefixes. As a result, different elements might serialize to the same name.

GivenName=Ren%C3%A9;

<PersonName title="Mr"> 
  <GivenName>René</GivenName> 
</PersonName>

Changed specification wording:

Element nodes selected for inclusion are encoded as EltName=value, where = is a literal character, EltName represents the element local name, and value represents the contents of the text node. The separator character {sep} from the separator attribute on submission is used between pairs of encoded name/value pairs EltName=value{sep}EltName=value{sep}EltName=value. Note that contextual path information is not preserved, nor are namespaces or namespace prefixes. As a result, different elements might serialize to the same name.

GivenName=Ren%C3%A9

<PersonName title="Mr"> 
  <GivenName>René</GivenName> 
</PersonName>

Current specification wording:

If the specified argument does not identify a repeat, processing stops with an exception (4.5.4 The xforms-compute-exception Event).

Changed specification wording:

If the specified argument does not identify a repeat it returns NaN.

Current specification wording:

Legal Values: Any xsd:QName representing a datatype definition in an XML Schema.

Changed specification wording:

Legal Values: Any xsd:QName representing a datatype definition.