W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > December 2008

[closed] Re: p:www-form-urldecode clarifications

From: Norman Walsh <ndw@nwalsh.com>
Date: Fri, 12 Dec 2008 11:39:06 -0500
To: public-xml-processing-model-comments@w3.org
Message-ID: <m2ej0dcpqt.fsf@nwalsh.com>
Toman_Vojtech@emc.com writes:

> Section 7.2.7 (p:www-form-urldecode) contains a note that says:
> "If any parameter name occurs more than once in the encoded string, the
> resulting parameter set will contain a c:param for each instance."
> Shouldn't we add something along the lines: "The c:param elements in the
> resulting parameter set appear in the same order as the corresponding
> name/value pairs in the "value" option."?
> The most important consequence of this would be that it would guarantee
> that the output of p:www-form-urldecode would be the same across
> different XProc implementations. Also, in the case of duplicate
> parameters, it would be clear what to do.
> --
> err:XC0037 says that: "I this a dynamic error if the value provided is
> not a properly x-www-form-urlencoded value."
> I think this error could also cover the case where the decoded parameter
> name is not a valid QName (or even stricter, a valid NCName??? - but
> that depends what we say about names that contains a colon).

Per the 11 Dec telcon, the document order of the resulting parameters
is the left-to-right order of the name/value pairs in the encoded string
and it's a dynamic error if the name isn't a valid NCName.

                                        Be seeing you,

Norman Walsh <ndw@nwalsh.com> | Many ideas grow better when
http://nwalsh.com/            | transplanted to another mind than in
                              | the one where they sprang up.--Oliver
                              | Wendell Holmes

Received on Friday, 12 December 2008 16:39:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:28:26 UTC