The latest editor's draft available now contains a number of changes that
were inspired by the edition of the submisson examples.
1) The submission element overview for the method attribute was missing
"multipart-post".
2) The mediatype attribute incorrectly said that the type should be
consistent with application/xml. Now that we have
xforms-submit-serialize, the requirement is that form authors should
ensure that the type is consistent with the actual content being
submitted.
3) The target attribute incorrectly identified its content as a binding
expression (rather than just an XPath) and it did not express the
evaluation context.
4) The xforms-submit-serialize event context property submission-body was
indicated to be a string (text node). We previously decided it was not
worth the effort of making it an element because we could not see anything
wrong with binding to a text node. However, seeing the example caused me
to realize that it was incorrect from the XPath data model perpective. In
XPath 1.0, empty text nodes do not exist. Unfortunately, the
submission-body is specified to be an empty string that is allowed to be
changed by an event handler. So it would not have been unreasonable to
conclude that the ref on the setvalue in the example was bound to an empty
nodeset, which would have prevented the setvalue from running To fix
this, I simply defined the property as returning a node instead.
Cheers,
John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com
Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer