Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)

Julian Reschke <julian.reschke@gmx.de> Mon, 22 October 2012 19:09 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA5721F8495 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.487
X-Spam-Level:
X-Spam-Status: No, score=-103.487 tagged_above=-999 required=5 tests=[AWL=-0.888, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oiPnONkgEZTv for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:09:32 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 8825221F8480 for <ietf@ietf.org>; Mon, 22 Oct 2012 12:09:31 -0700 (PDT)
Received: (qmail invoked by alias); 22 Oct 2012 18:59:42 -0000
Received: from p5DD95D63.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.93.99] by mail.gmx.net (mp069) with SMTP; 22 Oct 2012 20:59:42 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/2YHd0lWL2uJx/Rv8dsobGgm11W0tZmQji9bdAq6 XVhEYNoWsTUomY
Message-ID: <5085979D.8040104@gmx.de>
Date: Mon, 22 Oct 2012 20:59:41 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Noah Mendelsohn <nrm@arcanedomain.com>, mnot@mnot.net, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 19:09:32 -0000

On 2012-10-22 19:55, Ian Hickson wrote:
> On Mon, 22 Oct 2012, Brian E Carpenter wrote:
>> On 18/10/2012 02:25, Noah Mendelsohn wrote:
>>> On 10/17/2012 7:57 PM, Ian Hickson wrote:
>>>> Yeah. Turns out we (the Web standards community) haven't been doing
>>>> such a great job of making our specificatiosn match reality.:-(
>>>
>>> Um, true... but it's also the case that the implementation community
>>> hasn't over the years been doing as much as might be best to make
>>> reality match the specifications. The new specs we're writing now
>>> would like have been a lot thinner and cleaner if they had.
>>
>> However, I think the concern here is that if certain IETF specs need to
>> be updated to match the real world, that work needs to be done in the
>> IETF.
>
> I couldn't agree more! We've been waiting for four years for the URI
> working group to get their act together and fix the URL mess. Nothing has
> happened. We lost patience and are now doing it ourselves.
> ...

Clarifying: there is no URI Working Group, and as far as I can tell, 
there is no consensus that there is a "mess" to fix related to URIs. 
There *is* indeed a *IRI* Working Group which planned to define things 
that occur in HTML links (including sanitizing whitespace and dealing 
with the problems with non-ASCII characters), and *that* WG indeed 
hasn't delivered yet.

Best regards, Julian