W3C home > Mailing lists > Public > public-forms@w3.org > February 2009

separator default for urlencoded-post versus application/x-www-form-urlencoded

From: John Boyer <boyerj@ca.ibm.com>
Date: Sat, 28 Feb 2009 10:35:09 -0800
To: public-forms@w3.org
Message-ID: <OF8B7E81C0.75E5E4EE-ON8825756B.0064B528-8825756B.006607F2@ca.ibm.com>
The section for form-urlencoded submission [1] indicates that it uses the 
separator character specified by the submission element.

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

The default for the separator attribute specified at the beginning of 
Section 11 [2] is semicolon rather than ampersand.

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

Why is this?

Either the default should be ampersand, or possibly it was meant to be 
used only on a urlencoded-post? 

Or possibly the default was meant to be semi-colon for urlencoded-post and 
ampersand otherwise?  For method="get" is there ever a reason to have a 
separator other than ampersand?

This default setting appears ever since the attribute was added way back 
in 2002 [3], but the attribute appeared in the same working draft as did 
the urlencoded-post.

[3] http://www.w3.org/TR/2002/WD-xforms-20020821/

John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
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
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
Received on Saturday, 28 February 2009 18:35:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:50 UTC