W3C home > Mailing lists > Public > uri@w3.org > October 2006

Re: Feedback on draft-gregorio-uritemplate-00

From: James M Snell <jasnell@gmail.com>
Date: Thu, 05 Oct 2006 07:57:18 -0700
Message-ID: <45251D4E.4080204@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
CC: uri@w3.org

For a URI template, the only legal values for a template variable name
are in the "reserved" set.  Anything is not allowed.  Applications are
free to treat sequences like %20 as pct-encoded if they wish but that is
not required).  I am working on an IRI templates variation that will
allow non-ascii characters in template variable names and will allow for
 the generation of IRIs.

As for the replacement values, again, they MUST result in a valid URI,
meaning that the application is responsible for proper encoding of the
values so the result is valid.

- James

Julian Reschke wrote:
> James M Snell schrieb:
>> 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.
> 
> OK,
> 
> in that case the examples should be clarified.
> 
> Now, what if I put non-ASCII characters into a variable? Should the spec
> require encoding  la IRI?
> 
> Best regards, Julian
> 
Received on Thursday, 5 October 2006 14:57:39 UTC

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