W3C home > Mailing lists > Public > public-html-comments@w3.org > November 2011

Re: URL parsing in HTML5

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 04 Nov 2011 16:50:07 +0100
Message-ID: <4EB409AF.7070902@gmx.de>
To: Anne van Kesteren <annevk@opera.com>
CC: "public-iri@w3.org" <public-iri@w3.org>, public-html-comments@w3.org, Peter Saint-Andre <stpeter@stpeter.im>, Sam Ruby <rubys@intertwingly.net>, "Paul Cotton (pcotton@microsoft.com)" <pcotton@microsoft.com>, Ian Hickson <ian@hixie.ch>, "Michael(tm) Smith" <mike@w3.org>, Adam Barth <ietf@adambarth.com>, Edward O'Connor <ted@oconnor.cx>
On 2011-11-04 16:34, Anne van Kesteren wrote:
> On Thu, 03 Nov 2011 21:21:50 -0700, Peter Saint-Andre
> <stpeter@stpeter.im> wrote:
>> [...]
> The outcome you sketch will also result in all other W3C specifications
> to be implemented by browsers (and even HTTP if it were to be defined in
> a non-fiction manner) depend on HTML for its definition of URL processing.

Please stop the "fiction" rhetoric. There's also a lot of fiction in 
HTML5 (such as requiring rewriting of \ for all URI schemes), and I 
don't see you arguing about *that*.

I do agree that URIs leak, but that doesn't necessarily mean that we can 
have the same processing requirements everywhere. For instance, there 
are cases where whitespace acts as a delimiter and thus will not be 
accepted as URI character, no matter how much you want it to.

> ...

Best regards, Julian
Received on Friday, 4 November 2011 15:50:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:28 UTC