- From: Youenn Fablet <youenn.fablet@crf.canon.fr>
- Date: Fri, 16 Mar 2007 14:17:54 +0100
- To: Jonathan Marsh <jonathan@wso2.com>
- Cc: "'keith chapman'" <keithgchapman@gmail.com>, www-ws-desc@w3.org
Thanks for the input.
See inline.
Regards,
Youenn
Jonathan Marsh wrote:
> Youenn,
>
> I'm updating the expected results, but there are still a few questionable
> items which I believe are errors on your end, which affect all three test
> cases.
>
> 1) The character #xA3 doesn't seem to be encoded correctly. Per the rules
> in the IRI spec, UTF-8 encoding for characters up to #x7f is trivial, but
> for characters over #x80 it gets more complicated. That's why included a
> character over #x80 ;-). My read is that #xA3 gets percent-escaped
> according to these rules as %C2%A3.
>
Yes, you are right.
I will integrate the whole 1 to 4 bytes UTF8 conversion before doing the
% encoding.
> 2) There is an extra ?, encoded as %3F, following the "path" parameter.
> There isn't supposed to be one in the test data.
>
ok, I will remove the ? at the end of the path parameter value.
> 3) You also encode "=" even though there isn't a MUST or SHOULD requirement
> in the spec to do so. You conform, but it means I'll have to adjust the
> expected value in the test suite to represent the MUSTs + the SHOULDs + "=".
> I'm happy enough to do that, but just thought I'd point it out in case you
> think there's an erratum there.
>
Reading the current html draft, '=' does not appear in any of the
characters lists.
This implies that one must encode it, which may not be the intention.
It seems to me that '=', as a query parameter value character, is not
harmful to the query parsing.
I do not know if '=' has a specific meaning as a path character.
It might however be more coherent to add '=' to the SHOULD list.
> Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
>
Received on Friday, 16 March 2007 13:18:01 UTC