W3C home > Mailing lists > Public > public-soap-jms@w3.org > October 2010

ISSUE-64 (URI encoding explanatory text too restrictive): Section 3.3.5 refers to encoding of parameters

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 05 Oct 2010 16:16:39 +0000
To: public-soap-jms@w3.org
Message-Id: <E1P3ABz-0003Jg-CN@otto.w3.org>

ISSUE-64 (URI encoding explanatory text too restrictive): Section 3.3.5 refers to encoding of parameters

http://www.w3.org/2002/ws/soapjms/tracker/issues/64

Raised by: Mark Phillips
On product: 

>From email: http://lists.w3.org/Archives/Public/public-soap-jms/2010Sep/0022.html

The discussion on whitespace in the JMS URI has caused a colleague to raise
a minor issue with section 3.3.5 in the Binding spec. with regard to
encoding the URI for use in XML.  The final paragraph in that section
states that:

"The values for parameters in the URI need to be encoded ("%20" for space,
for example) as per normal URI escaping rules, and the resulting URI needs
to be encoded as per normal XML rules ("&amp;" for &) when serialized into
an XML attribute."

The problem with this sentence is that it specifically refers to URI
parameter values, but it is conceivable that other parts of the URI might
contain characters which need encoding, for example parameter names (or the
destination name itself in some variants).

To resolve the issue I propose that we modify the sentence so that ....

"The values for parameters in the URI"

...becomes...

"The characters  in the URI"
Received on Tuesday, 5 October 2010 16:16:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:25 GMT