W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > March 2007

RE: Query parameter separator value

From: Jonathan Marsh <jonathan@wso2.com>
Date: Fri, 16 Mar 2007 16:02:55 -0700
To: "'Youenn Fablet'" <youenn.fablet@crf.canon.fr>
Cc: <public-ws-desc-comments@w3.org>
Message-ID: <00c301c7681f$3cbd1cd0$b6375670$@com>

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

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

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] 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
Received on Friday, 16 March 2007 23:03:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:06 UTC