W3C home > Mailing lists > Public > public-media-fragment@w3.org > June 2010

Re: Media Fragments URI parsing: pseudo algorithm code

From: RaphaŽl Troncy <raphael.troncy@eurecom.fr>
Date: Wed, 30 Jun 2010 11:56:39 +0200
Message-ID: <4C2B14D7.1070804@eurecom.fr>
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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:39 GMT