- From: Raphaël Troncy <raphael.troncy@eurecom.fr>
- Date: Wed, 30 Jun 2010 11:56:39 +0200
- To: Yves Lafon <ylafon@w3.org>
- CC: Jack Jansen <Jack.Jansen@cwi.nl>, Philip Jägenstedt <philipj@opera.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Media Fragment <public-media-fragment@w3.org>
> the URI RFC makes it quite clear where percent encoding is allowed and > where it is not. For example, h%74%54p://www.example.com/ is _not_ > htTp://www.example.com/ > > Also, do you want 'NpT' to be equivalent to 'nPT' and 'npt' ? > To me, if you are escaping something, there is good reason for that, if > you do it in 'npt' you probably mean that you don't want it to be > processed as 'npt' directly. The grammar allows pct-encoding in track > names and ids. Does it mean you don't want to have pct-encoding for x-prefix? Does the URI RFC tells you that you cannot have pct-encoding anywhere you want into the fragment part? If yes, where? 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 Wednesday, 30 June 2010 09:58:39 UTC