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

Ian Hickson <ian@hixie.ch> Wed, 17 October 2012 23:57 UTC

Return-Path: <ian@hixie.ch>
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 16DD221F8686 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 16:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 CU7mVxgm79ls for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 16:57:39 -0700 (PDT)
Received: from homiemail-a79.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6A68A21F8691 for <ietf@ietf.org>; Wed, 17 Oct 2012 16:57:39 -0700 (PDT)
Received: from homiemail-a79.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTP id 814E37D4070; Wed, 17 Oct 2012 16:57:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=Gwt0D7KC8IQU85D05avTE0ABZnI=; b=akY RG8RGTLZk+B6dHIvdM6+BSjw2qcwN6PPcsYz8R6invZxiyANmQVNANJzvR/lSTRH SDjBipzNFBRUDhMfqgq1W5QB7aQATmUlRWqIbsKbQSRpoIWgbtDHfa4DJZv7m8Iq tByjFIX5yAL48kiwUznmYTL+VIcw8ELFWEucyznU=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTPSA id 6DF037D406F; Wed, 17 Oct 2012 16:57:35 -0700 (PDT)
Date: Wed, 17 Oct 2012 23:57:38 +0000
From: Ian Hickson <ian@hixie.ch>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <5060A964.5060001@stpeter.im>
Message-ID: <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:04:06 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, 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: Wed, 17 Oct 2012 23:57:40 -0000

On Mon, 24 Sep 2012, Peter Saint-Andre wrote:
>
> It's also not clear to me what the WHATWG HTML Living Standard [1] 
> really means by "willful violation"
> http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#willful-violation

Can you elaborate on how the definition you cite there in the spec is 
unclear? I'm not sure how to make it clearer.


> e.g., is it just an allowance for APIs and browser software to not be 
> completely strict about processing some input for the sake of backward 
> compatibility with existing (messy) web content, or is it an active 
> attempt at redefining core protocols?

The spec seems pretty clear that it's the latter ("conflicting needs have 
led to this specification violating the requirements of these other 
specifications").


> However, it is interesting that the willful violations are not limited 
> to RFC 3986: the spec also mentions willful violations of RFC 2046, RFC 
> 2616, RFC 2781, RFC 5322, EcmaScript, XPath, XSLT, and Unicode. Quite a 
> list...

Yeah. Turns out we (the Web standards community) haven't been doing such a 
great job of making our specificatiosn match reality. :-(

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'