CR117 Option 2

I'm becoming more intrigued by Youenn's option 2, under the new formulation
"raw path parts, encoded query parts".  I think it will work.  Here's a more
fully developed proposal for it, which is a subset of the proposal for
option 1.

 

Remove the text in 6.7.1.1 that reads:

 

No percent-encoding mechanism, as defined in section 2.1 of RFC 3986, is
performed on the replacement value.

 

Add to the bullet list in 6.7.1.1:

 

*         A template preceded in the {http location} by a "?" or "#"
character, or an uncited parameter, is encoded as follows:  Any character in
the XML value falling outside the range ALPHA | DIGIT | "-" | "." | "_" |
"~" | "!" | "$" | "&" | "'" | "(" | ")" | "*" | "+" | "," | ";" | "=" | ":"
| "@" MUST be %-encoded.  %-encoding MUST be performed using the UTF-8
representation of the character as prescribed by section 6.4 of [IRIs].

 

Add to the bullet list in 6.7.2.2.1:

*         Parameter values falling outside the range ALPHA | DIGIT | "-" |
"." | "_" | "~" | "!" | "$" | "&" | "'" | "(" | ")" | "*" | "+" | "," | ";"
| "=" | ":" | "@" MUST be %-encoded.  %-encoding MUST be performed using the
UTF-8 representation of the character as prescribed by section 6.4 of
[IRIs].

 

 

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