RE: Query parameter separator value

[Jonathan Marsh-2]

Thank you for this comment.  The Working Group recorded this issue as a
CR156 [1].

The WG decided to restrict the values of the query parameter separator with
an assertion and a schema pattern.  This has been incorporated into the
draft at [2].

[1] http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR156
[2]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml#
http-operation-decl-xml

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
 

> -----Original Message-----
> From: www-ws-desc-request@... [mailto:www-ws-desc-request@...] On
> Behalf Of Youenn Fablet
> Sent: Wednesday, February 21, 2007 4:42 AM
> To: www-ws-desc
> Subject: Query parameter separator value
>
>
> Reading the specification, it seems that the only constraint on the
> separator value is to be a xml string of length 1.
> It would therefore be possible to have a separator value that needs to
> be %-encoded in the URL (e.g. queryParameterSeparator="é").
> I do not know whether that was intended but in this case, the query
> string may become ambiguous: if the separator value appears in a
> parameter value, it will be %-encoded exactly like the separator value.
> It might be safer to restrict the separator value range.
>
> In any case, the most sensible values are '&' and ';'. Is there any
> other obvious possibility?
> While '&' is the default value, ';' does not appear AFAIKT neither in
> the spec nor in the primer.
> It might therefore be good to add a statement that tells a word about
> these values, maybe as a SHOULD.
> Regards,
>     Youenn
>