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

"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 24 October 2012 01:59 UTC

Return-Path: <James.H.Manger@team.telstra.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 18C0011E8146 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 18:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.929
X-Spam-Level:
X-Spam-Status: No, score=-0.929 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 4K1GnNmhx6P1 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 18:59:10 -0700 (PDT)
Received: from ipxcno.tcif.telstra.com.au (ipxcno.tcif.telstra.com.au [203.35.82.208]) by ietfa.amsl.com (Postfix) with ESMTP id 3042C11E80E9 for <ietf@ietf.org>; Tue, 23 Oct 2012 18:59:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,638,1344175200"; d="scan'208";a="98037678"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipocni.tcif.telstra.com.au with ESMTP; 24 Oct 2012 12:59:08 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6874"; a="96043639"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipccni.tcif.telstra.com.au with ESMTP; 24 Oct 2012 12:59:08 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Wed, 24 Oct 2012 12:59:07 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Ian Hickson <ian@hixie.ch>, Christophe Lauret <clauret@weborganic.com>
Date: Wed, 24 Oct 2012 12:59:05 +1100
Subject: RE: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Thread-Topic: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Thread-Index: Ac2xeWY/aSNY/ig4Q1OIdv9rcNd7qgADHwyA
Message-ID: <255B9BB34FB7D647A506DC292726F6E114FE01A829@WSMSG3153V.srv.dir.telstra.com>
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> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Anne van Kesteren <annevk@annevk.nl>, Ted Hardie <ted.ietf@gmail.com>, Jan Algermissen <jan.algermissen@nordsc.com>, 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, 24 Oct 2012 01:59:11 -0000

> From: Ian Hickson [mailto:ian@hixie.ch]
> I think we can agree that the error handling should be, at the option
> of the software developer, either to handle the input as defined by the
> spec's algorithms, or to abort and not handle the input at all.

Currently, I don't think url.spec.whatwg.org distinguishes between strings that are
valid URLs and strings that can be interpreted as URLs by applying its standardised error handling. Consequently, error handling cannot be at the option of the software developer as you cannot tell which bits are error handling.

This might be why some are unhappy with url.spec.whatwg.org.

url.spec.whatwg.org does have separate "Writing" and "Parsing" sections. Perhaps the implicit idea is that any output of the "Writing" section is a valid URL (that all URL-processing software should handle). The "Parsing" section accepts more strings than can be created by the "Writing" section. The difference is the error handling. It's OK for a software developer not to parse this difference if it makes its parser simpler, safer, or that is the way its parser works today.


--
James Manger