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

Re: Media Fragments URI parsing: pseudo algorithm code

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 30 Jun 2010 22:23:51 +0200
To: Philip Jägenstedt <philipj@opera.com>
Cc: public-media-fragment@w3.org
Message-ID: <h49n261v0qtili75toluug6s62r945rgh5@hive.bjoern.hoehrmann.de>
* Philip Jägenstedt wrote:
>>>> With the current grammar, it is allowed only in track and id  
>>>> productions.
>>>> So it is perfectly compatible with the processing defined in rfc3986  
>>>> and perfectly allows #track=A%20%26%20B&t=10
>>>
>>> No disagreement that we need to define it, thankfully. The disagreement  
>>> is only where to decode percent-encoding.
>>
>> RFC3986 gives the answer, after the URI components are parsed (and we  
>> define here how to split out in components).
>
>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.
-- 
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 Wednesday, 30 June 2010 20:24:21 GMT

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