Re: Spec layering: name-value pairs and beyond

On Wed, Mar 10, 2010 at 7:40 AM, RaphaŽl Troncy <raphael.troncy@cwi.nl> wrote:
>> I believe Yves looks at the production rules as generic rules how to
>> create such a URI rather than how to parse such a URI.
>
> I think that Yves has a plan to smoothly integrate and reconcile both views,
> so let's patiently wait he completes his action.
>
>> I think we may need to make two different sections for these two
>> approaches, since when you are creating a URI, you have to UTF-8
>> encode and percent-encode etc, while when you are parsing, you do the
>> opposite (you decode and you would probably not decode UTF-8, and
>> possibly not decode percent-encoding before doing something with it,
>> such as sticking the values in a HTTP header.
>
> Well, remember Silvia that non-ASCII characters will from the URI will be
> decoded and re-encoded in RFC2047 in headers, e.g.:
>
> †Range: track==?utf8?b?Zm9v?=,=?utf8?b?YmFy?= :-)

Scary!

But I do look forward to Yves' spec.

Cheers,
Silvia.

Received on Tuesday, 9 March 2010 22:18:07 UTC