headers
Alexey Melnikov | 1 Dec 11:17
Favicon

Re: Request to review sieve URI scheme

Hi Martin,

Martin Duerst wrote:

>I had a look at parts of it. One thing I looked through is whether it's
>clear where (percent-encoded) UTF-8 can be used; that seems to be fine.
>
>It might help the reader if the grammar rules were reordered to
>read top-down. Currently it's top-down first, but then bottom-up.
>  
>
Good point. I've reordered them.

>Another thing I noticed is that characters such as "&" and "="
>are listed as needing percent-encoding. I don't see them being
>used in the syntax, so it wouldn't be necessary to percent-encode
>them. Or are they reserved for future extensions?
>  
>
Yes. I don't have any extensions in mind yet, but I thought it would be 
better to allow for them.

Thank you,
Alexey

>Regards,    Martin.
>
>At 02:56 08/12/01, Alexey Melnikov wrote:
>  
>
(Continue reading)

Permalink | Reply |
headers
Martin Duerst | 1 Dec 11:24

Re: Request to review sieve URI scheme

Hi Alex,

At 19:17 08/12/01, Alexey Melnikov wrote:

>>Another thing I noticed is that characters such as "&" and "="
>>are listed as needing percent-encoding. I don't see them being
>>used in the syntax, so it wouldn't be necessary to percent-encode
>>them. Or are they reserved for future extensions?
>>  
>>
>Yes. I don't have any extensions in mind yet, but I thought it would be better to allow for them.

In that case, I guess it would be better to say so in a note.
The principle in URI escaping is that escaping isn't necessary
in those parts where the character doesn't take a special meaning,
so people familiar with that principle could think that it's not
really necessary to escape these.

Regards,    Martin.

>Thank you,
>Alexey
>
>>Regards,    Martin.
>>
>>At 02:56 08/12/01, Alexey Melnikov wrote:
>>  
>>
>>>Hi,
>>>I am finishing draft-ietf-sieve-managesieve-02.txt which defines the sieve: URI scheme. So I would
(Continue reading)

Permalink | Reply |

Gmane