RE: List discussion issue: Pruning empty nodes on url-encoded submission

I apologize for the distraction during the meeting and for sending both
issues in the same message.
 
- If you submit with method="get", nodes whose string content is empty
get elided, so there's no way to do a GET of 
 http://example.com/query?a=1;b=;c=3
Instead, you get
 http://example.com/query?a=1;c=3 
 
I believe the correct behavior is that the empty item should be
serialized as "name=" but no value.
I believe that only missing or non-relevant b is what should cause the
elision.
 
- In HTML4, empty string content values are still submitted.
 
Attached are examples of a single-parameter query/echo form example in
XHTML+XForms and XHTML1.
 
Leigh.

________________________________

From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
On Behalf Of John Boyer
Sent: Wednesday, May 02, 2007 1:13 PM
To: public-forms@w3.org
Subject: List discussion issue: Pruning empty nodes on url-encoded
submission



Turns out the link in the agenda was correct:
http://lists.w3.org/Archives/Public/www-forms/2007Feb/0077.html 

It is the submit-on-enter example from Leigh, which includes information
from Aaron Reed. 

The email points out two problems, the submit-on-enter problem AND the
problem that empty nodes are pruned on URL encoded submissions, instead
of submitting them as empty values. 

Let's get some discussion going on the list here about what the correct
behavior should be. 

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