Re: URI Templates: done or dead?

Mark Nottingham wrote:

> ... 
> 
> 3. Make percent-encoding context-sensitive.
> 
> There are just too many cases where the 'escape everything but 
> unreserved' rule gets in the way; for example, if my template is 
> "http://example.com/user/{email}", I'm going to have percent-encoded @ 
> signs in my URIs whether I like it or not -- even though they're not 
> required to be percent-encoded there. This is a relatively simple thing 
> to do, as long as we also...
> 
> 4. Allow exceptions to percent-encoding.
> 
> We need a syntax that allows characters to be excepted from encoding, 
> even in context. As a straw-man, I suggest preceding the expression with 
> the characters that are excepted, like:
> 
>    http://example.com/{/path}
>    http://example.com/thing{?&=query_args}
> 
> and so forth.
> 
 > ...

Not being able to use unreserved characters as substitution values is 
the biggest issue I have with the current draft.  To make this even 
simpler, I'd suggest a single character prefix on the "expression" to 
indicate not doing ANY percent-encoding; Mark's suggestion limits 
extendability later, and doesn't read easily.

-- 
Patrick Mueller
http://muellerware.org

Received on Tuesday, 16 September 2008 16:17:28 UTC