- From: Raphaël Troncy <raphael.troncy@cwi.nl>
- Date: Tue, 09 Mar 2010 21:40:42 +0100
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- CC: Philip Jägenstedt <philipj@opera.com>, Media Fragment <public-media-fragment@w3.org>
> 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?= :-) Raphaël -- Raphaël Troncy EURECOM, Multimedia Communications Department 2229, route des Crêtes, 06560 Sophia Antipolis, France. e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com Tel: +33 (0)4 - 9300 8242 Fax: +33 (0)4 - 9000 8200 Web: http://www.eurecom.fr/~troncy/
Received on Tuesday, 9 March 2010 20:50:38 UTC