W3C home > Mailing lists > Public > www-ws-desc@w3.org > February 2007

Re: LocationTemplate-1G test

From: Youenn Fablet <youenn.fablet@crf.canon.fr>
Date: Wed, 21 Feb 2007 14:37:18 +0100
To: Jonathan Marsh <jonathan@wso2.com>
Cc: "'keith chapman'" <keithgchapman@gmail.com>, "'www-ws-desc'" <www-ws-desc@w3.org>
Message-id: <45DC4B0E.9000802@crf.canon.fr>

To be sure of the current state of the spec, my current understanding is 
the following:
    - '*' may be let unencoded (in this LocationTemplate-1G example)
    - '*' may also be %-encoded (in this LocationTemplate-1G example)
LocationTemplate-1G servers should both process messages with unencoded 
'*' and %-encoded '*'.
If that is correct, the test framework should (in theory) not flag 
messages with '*' encoded as %xx.
  Youenn

Jonathan Marsh wrote:
> I looked into message 13 there.  The location template in that testcase is: 
>
>    datespace/{year}.html?passphrase={time}{{4(^$@!}}4^@*}}
>
> This testcase test not only that templates are encoded, but that the IRI is
> correctly converted to a URI per RFC3987.  Many characters over #xA0 are
> %-encoded, as well as "<", ">", '"', space, "{", "}", "|", "\", "^", and
> "`".
>
>    datespace/2006.html?passphrase=16:40:00%7B4(%5E$@!%7D4%5E@*%7D
>
> Indeed the "*" should have been omitted from the list of characters encoded
> during this conversion.  I've updated the expected results, putting Canon at
> all green on this testcase.  Axis2 still fails the testcase because it
> doesn't seem to be doing the encoding listed above at all.
>
> Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
>  
>
>   
>> -----Original Message-----
>> From: Youenn Fablet [mailto:youenn.fablet@crf.canon.fr]
>> Sent: Tuesday, February 20, 2007 5:31 AM
>> To: keith chapman
>> Cc: www-ws-desc; Jonathan Marsh
>> Subject: Re: LocationTemplate-1G test
>>
>> Here is canon location template 1G result.
>> There is one red (request 13).
>> It seems that our implementation is not %-encoding the '*' character
>> while the test framework wants it to be %-encoded.
>> As per the current draft, '*' is not in the must-be-encoded set.
>> An application may therefore typically choose to %-encode it or not,
>> right?
>> The test framework should only check that must-be-%-encoded characters
>> are correctly encoded and nothing more.
>> I do not know whether this is easily feasible in the current test
>> framework though.
>>     Youenn
>>
>> keith chapman wrote:
>>     
>>> Hi Jonathan,
>>>
>>> Request 11 shows red due to a mistake in the test framework. You
>>> forgot to add 000Z to one time element...
>>>
>>> Thanks,
>>> Keith.
>>> --
>>> Keith Chapman
>>> WSO2 Inc.
>>> Oxygen for Web Services Developers.
>>> http://wso2.org/
>>>       
>
>
>
>   
Received on Wednesday, 21 February 2007 13:37:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:46 GMT