Spec updates for url-encoded submission and adjust-dateTime-to-timezone

Please review the changes made to the XForms 1.1 editor's draft [1] that 
have resulted from action items related to the effect of empty elements on 
url encoded submissions and the function needed for proper dateTime 
addition.

[1] http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html

=========================
Regarding submission, Blake recently submitted an action item result 
changing urlencoded submission so that empty elements are included in the 
serialization.
His write-up also accounted for relevant nodes, which the prior text did 
not.  I slightly amended that part because XForms 1.1 now has a relevant 
attribute on submission.  I also changed the way serialization was 
described to use the string value notion from XPath 1.0, which we are now 
also using for form controls and elsewhere.  Please review the changes 
[2].

[2] 
http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html#serialize-urlencode

Blake also pointed out that he thought the same rules should apply to 
multipart/form-data, so I applied similar wording there.
However, I also found several other errors, which I fixed in the editor's 
draft.  Please review them [3].

[3] 
http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html#serialize-form-data

Specifically, the errors included 

i) referencing RFC 2387 instead of RFC 2388, 
ii) inadequately describing that the content is binary for parts created 
for elements of types associated with upload (e.g. base 64 decode, hex 
decode, or URI resolved), 
iii) failing to describe how the content is obtained for parts created for 
elements of types not associated with upload (i.e. by computing the string 
value)
iv) seeming to omit xsd:anyURI from the list of types associated with 
upload
=========================

=========================
The adjust-dateTime-to-timezone() function has been added [4], and it is 
in accord with the single parameter version of the function in XPath 2.0 
with the single exception that it does not generate a run-time error if 
the input parameter is not a legal lexical dateTime (as generating such an 
error is inconsistent with our decisions for numerous other functions).

The desired dateTime math examples are now also shown in that function as 
well as in local-dateTime() and seconds-to-dateTime() to maximize 
discoverability of the technique.  Generally, the attempt to account for 
this capability with extra boolean parameters to seconds-to-dateTime() and 
seconds-from-dateTime() was rolled back, but the additional examples for 
the functions in this area were not removed but rather amended.

It is now clear to the reader how to use a single expression to compute 2 
days from today and 2 hours from now, both in the local timezone.

[4] 
http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html#fn-adjust-dateTime-to-timezone

========================

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