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

Re: Media Fragments URI parsing: pseudo algorithm code

From: Yves Lafon <ylafon@w3.org>
Date: Thu, 1 Jul 2010 05:06:33 -0400 (EDT)
To: Bjoern Hoehrmann <derhoermi@gmx.net>
cc: Philip Jägenstedt <philipj@opera.com>, public-media-fragment@w3.org
Message-ID: <alpine.DEB.1.10.1007010505030.30546@wnl.j3.bet>
On Wed, 30 Jun 2010, Bjoern Hoehrmann wrote:

>> The disagreement here is only for which components to decode
>> percent-encoding, RFC3986 will not help us.
> RFC 3986 requires implementations when processing a fragment identifiers
> to treat %74 and "t" the same regardless of where either occurs, as "t"
> is not a reserved character and URIs that differ only in the escaping of
> unreserved characters are defined to be equivalent. So the answer here
> is "all components". You can only have special requirements for reserved
> characters when they occur unescaped.

URI equivalence is an endlees source of fun :)
are http://www.example.com/ (1) and http://www.example.com:80/ (2) and 
h%74ttp:www/example.com/ (3) equivalent ?
From what you say, at least (1) and (3) should be.

Baroula que barouleras, au tiéu toujou t'entourneras.

Received on Thursday, 1 July 2010 09:06:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:45 UTC