W3C home > Mailing lists > Public > uri@w3.org > February 2007

Re: URI and IRI Templating - encoding defaults

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 17 Feb 2007 13:50:41 +1100
Message-Id: <683F8784-400D-4287-A38C-CE83A761D623@mnot.net>
Cc: "Marc Hadley" <Marc.Hadley@sun.com>, "James M Snell" <jasnell@gmail.com>, uri@w3.org
To: Joe Gregorio <joe@bitworking.org>


On 2007/02/17, at 5:48 AM, Joe Gregorio wrote:
>>
>> I agree that embedding encoding information isn't desirable, but  
>> using:
>>
>> >   Characters outside ( iprivate | iunreserved | '@' | ':' | '/' )
>> > are % encoded.
>>
>> as the default encoding rule means that sub-delims ("!" / "$" / "&" /
>> "'" / "(" / ")" / "*" / "+" / "," / ";" / "=") will *always* be
>> encoded when expanded from templates; there won't be any way to have
>> these perfectly legal characters appear in template-generated URIs.
>
> They will appear, it just means that they will be percent-encoded,  
> that is, you
> can't use them as delimiters.

...and some people / formats / schemes want to use them exactly as  
that. That's what they're there for.

> The same is true for all the examples you listed.

Yes, but as soon as someone needs to disambiguate between data and  
delimiter, they'll have a problem.

> True, you can't have template values span multiple components, but
> I thought we had already decided against that use case.

I'm not talking about having templates span multiple components.



--
Mark Nottingham     http://www.mnot.net/
Received on Saturday, 17 February 2007 02:51:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:10 UTC