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

Tim Bray <tbray@textuality.com> Mon, 22 October 2012 22:11 UTC

Return-Path: <tbray@textuality.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 02E9711E80EA for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 nr0u7FCfXn8u for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:11:39 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5D25F11E80E2 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:11:39 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so3502454obq.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:11:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=hoxEWBClCdiJjME5SzedjPD+3ycSwNWfJljWNJQcBxE=; b=BIeRf6inyrjY7Xq1JaMAhvdMNNCtfBOiEc9cpEudnIK6btRsh742mEwLsoPUkzxcpV tBBFpvBg60mI9fiWa/9UaJJP/Evz2F9punti8DAhpKg8Ani3oP1XaW3emlo4l+WyVlYa fxPuxKGuk/pje8WjfDzZ2fITxjckEDtFa4K5zYsSunnc17n24XwaEbR8GKyYA/zcLGtZ zaEk8wKGCfDv1mjtqEds8IqZAksOCBU2evuWMnT5WchzrVSezrQe4T/gZV26LO76yAGc PbCRv/lY/1D0i0WBN2EPascD/qnLWqF27cf1b2zVXDNC/+LqIu3+c0fJF6fd9VU7Bv6N RlHw==
MIME-Version: 1.0
Received: by 10.182.146.46 with SMTP id sz14mr8201898obb.76.1350943898883; Mon, 22 Oct 2012 15:11:38 -0700 (PDT)
Received: by 10.76.87.136 with HTTP; Mon, 22 Oct 2012 15:11:38 -0700 (PDT)
X-Originating-IP: [2620:0:1000:5e03:8146:c08:57ba:8c50]
In-Reply-To: <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.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>
Date: Mon, 22 Oct 2012 15:11:38 -0700
Message-ID: <CAHBU6isuainUDbAMPTjGJ3rQEE8Ru22ufMKDNDHWxbGLk4T8pg@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Tim Bray <tbray@textuality.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary="f46d0444e92b3454ff04ccad234f"
X-Gm-Message-State: ALoCoQkqV5THtgUcgq5RS4uLS63rxYuYNcJUQlQjKW6vbkf6O+zCZB/cKIT8y49jsDJFSrFN7by5
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.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 22:11:40 -0000

On Mon, Oct 22, 2012 at 2:46 PM, Ian Hickson <ian@hixie.ch> wrote:

> On Mon, 22 Oct 2012, Roy T. Fielding wrote:
>>
>> What you are insisting on defining as a "URL" is the input to the
>> process of making a hypertext reference (the arbitrary string typed into
>> a dialog or placed inside an href/src attribute)
>
> Or placed on a command line to wget(1), or put in an RDFa triple store, or
> in transmitted in an HTTP Location: header, or...

It seems reasonable that someone should write rules for dealing with the
kinds of errors that are observed to occur in links as embedded in resource
representations AKA HTML pages.  It also seems reasonable that WHATWG, who
speak (if I understand correctly) for browser builders, can write those
rules.

The notion that curl, or an HTTP cache manager, or an XML namespace
processor, is going to be routing around errors, strikes me on the face of
it as being wrong.  One of the main uses I put curl to is making sure I
have the URL exactly right before I drop it into chat or whatever.   -T