- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Tue, 21 Sep 2010 23:35:24 +0200
- To: Amelia A Lewis <alewis@tibco.com>
- Cc: SOAP-JMS <public-soap-jms@w3.org>, uri-review@ietf.org
* Amelia A Lewis wrote:
>So ... isn't this a concern at a higher layer than the URI
>specification layer? The SOAP/JMS specification, for instance, might
>have to deal with encoding issues, but it seems as though the URI spec
>itself cannot.
It is uncommon for names and values to begin or end with white space
characters, but it is common to wrap long identifiers at the delimiters
between them. The concern is that some implementers may undo wrapping
at the wrong layer. To take an example from the draft
jms:jndi:SomeJndiNameForDestination?jndiInitialContextFactory=
com.example.jndi.JndiFactory&priority=3
some implementations might end up treating that the same as
jms:jndi:SomeJndiNameForDestination?jndiInitialContextFactory=
%20com.example.jndi.JndiFactory&priority=3
because that is what wrapping may translate to when moving from one
layer to the other without properly accounting for the wrapping. So
my comment was that it may be a good idea to include a brief note
about the significance of white space in the document, just like it
discusses case-sensitivity, default values, and ordering.
--
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Tuesday, 21 September 2010 21:36:04 UTC