I got a note from Eric Bruchez reminding me to comment that XForms 1.1 will also make available submission response header information in the xforms-submit-done event context, which helps complete the story about ATOM.
Yesterday was also a really good day in which we worked out some challenging issues related to the XForms
type model item property.
One reason this was important was for ensuring that we had a proper answer for the last technical question about XForms basic. We confirmed it was not an issue for basic, so you can expect to see basic progress through the rest of the W3C process RSN (real soon now).
We also came to agreement on the meaning of the
type MIP in two interesting scenarios. When an element has an attribute but only simple content, technically it is still a complexType according to W3C schema. So, what happens when
type refers to a simpleType? Also, is a form author allowed to refer to a complexType with simpleContent using XForms type, and if so, does it validate the node or just the content?
And the answers are... the
type MIP applies only to the validation of the string-value of nodes that have no element children, i.e. it only validates content and only when the content is character data. If a simpleType is used on an element with an attribute, that's OK because the simpleType will only be used to validate the element's content. And if a complexType with simpleContent is applied to an element node, only the element content will be validated according to the underlying simpleType. This means that if the attribute on the element node is invalid according to the complexType, the element itself would not be flagged as invalid.
This is a reasaonably nice synchronization of what a user can modify via user interface bindings, what a calculate can modify, and what the type MIP actually validates.[Read More]