ISSUE-64: Section 3.3.5 refers to encoding of parameters
URI encoding explanatory text too restrictive
Section 3.3.5 refers to encoding of parameters
- Raised by:
- Mark Phillips
- Opened on:
- 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
"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 ("&" 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"
"The characters in the URI"
- Related Actions Items:
- No related actions
- Related emails:
- Completion of ACTION-216 (from M8PHILLI@uk.ibm.com on 2010-10-12)
- Agenda for the 2010-10-12 conference call (from firstname.lastname@example.org on 2010-10-11)
- ISSUE-64 (URI encoding explanatory text too restrictive): Section 3.3.5 refers to encoding of parameters (from email@example.com on 2010-10-05)
Opened as per 2010-10-05 call: http://www.w3.org/2010/10/05-soap-jms-minutes.htmlEric Johnson, 5 Oct 2010, 18:58:34
Accepted proposal as per 2010-10-05 call
Application of resolution accepted as per:
Display change log