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

Re: Media Fragments URI parsing: pseudo algorithm code

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Thu, 01 Jul 2010 11:17:54 +0200
To: Yves Lafon <ylafon@w3.org>
Cc: Philip Jägenstedt <philipj@opera.com>, public-media-fragment@w3.org
Message-ID: <lvmo26h7fv362bbost1a2702evjlvl9b75@hive.bjoern.hoehrmann.de>
* Yves Lafon wrote:
>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.

Well, http://www.websitedev.de/temp/rfc3986-check.html.gz tells me (3)
is neither a URI nor a URI-reference so the question does not arise. For
(1) and (2) the answer is scheme-specific. Neither has a bearing on the
case of fragment identifiers as they are scheme-independent and allow
percent-encoding everywhere.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Thursday, 1 July 2010 09:18:25 UTC

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