- From: James M Snell <jasnell@gmail.com>
- Date: Thu, 05 Oct 2006 07:23:05 -0700
- To: Julian Reschke <julian.reschke@gmx.de>
- CC: uri@w3.org
Hey Julian,
Yeah, this actually came up in our own discussions prior to publishing
the draft. The point that the spec is trying to make is that invalid
characters MUST be percent encoded before performing the replacement so
rather than replacing {a} with the literal "fred barney" you'd replace
it with the literal "fred%20barney". This should ensure that no
additional processing of the URI is necessary after performing the
template expansion.
- James
Julian Reschke wrote:
> [snip]
> However, in
> <http://bitworking.org/projects/URI-Templates/draft-gregorio-uritemplate-00.html#rfc.section.4.3>
> we see:
>
> +++++++++++
> The following are examples of URI Template expansions that are not legal.
>
> Name Value
> ------------------------------------------------------------
> a fred barney
> b %
>
> The following URI Templates are expanded with the given values and do
> not produce legal URIs.
>
> http://example.org/{a}
> http://example.org/fred barney
>
> http://example.org/{b}/
> http://example.org/%/
> +++++++++++
>
> ..although I would have assumed that "http://example.org/{b}/" should
> have been expanded to "http://example.org/%25/" according to Section 4.2...
>
> [snip]
Received on Thursday, 5 October 2006 14:23:29 UTC