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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 22 October 2012 16:03 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 A273E21F8C68 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 09:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.675
X-Spam-Level:
X-Spam-Status: No, score=-101.675 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, 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 lB4lPWGqLTTn for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 09:03:20 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF6221F8C52 for <ietf@ietf.org>; Mon, 22 Oct 2012 09:03:19 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so992770bkc.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 09:03:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RKzxCWvYl9KhutImF9Uah1UOl+drmMi9d3Ia66tjzrY=; b=DX1KR15us5GI6SE0H2qZmqYa/BMpzvm3HajQwcoENB4UKTasJuxT0TdEM6dPykrC6k 6xoyQ6evo2ke7X06diNGM9OmQrfx5JL84O9+JcfvNG1gisZMKKQyFJgcCagSWcqZgBl5 WYfjlxy/c6UbJSA2yeOGMppB11H8uuVTGxpVLhPIlX5+sjcGGtdhubeaHoJ6YMTVsQyi JlQ65w8e3Be48Bovd6ix22xNE2Gy0LRU5Jab3USzKqnMPblXiyq+st4KAlnib6bi3dUA GK11Bmw8r8LYEReWKpLdpl6hTZP7+fniwo8dRZP3VY5loFrAnSmXwAD5QDwGU7HT/ejo 2gzw==
Received: by 10.204.150.141 with SMTP id y13mr2780533bkv.1.1350921798279; Mon, 22 Oct 2012 09:03:18 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-216-204.as13285.net. [2.102.216.204]) by mx.google.com with ESMTPS id r15sm4081605bkw.9.2012.10.22.09.03.13 (version=SSLv3 cipher=OTHER); Mon, 22 Oct 2012 09:03:14 -0700 (PDT)
Message-ID: <50856E3C.103@gmail.com>
Date: Mon, 22 Oct 2012 17:03:08 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Noah Mendelsohn <nrm@arcanedomain.com>
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>
In-Reply-To: <507F5A7E.6040206@arcanedomain.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, mnot@mnot.net, URI <uri@w3.org>, Ian Hickson <ian@hixie.ch>, 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 16:03:20 -0000

Hi Noah,

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.
It can't be done by reference in a W3C document; it has to be done by value
in an IETF document.

So it seems to me there is an open liaison question here and I'd like to hear
from the IETF/W3C liaison how this will be resolved.

Regards
    Brian