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

John C Klensin <john-ietf@jck.com> Wed, 24 October 2012 11:38 UTC

Return-Path: <john-ietf@jck.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 D1B4D21F8B94 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 04:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level:
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 iSSs5MyAlfTL for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 04:38:58 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4B05D21F8B93 for <ietf@ietf.org>; Wed, 24 Oct 2012 04:38:58 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TQzIM-000CP6-2b; Wed, 24 Oct 2012 07:38:46 -0400
Date: Wed, 24 Oct 2012 07:38:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mark Nottingham <mnot@mnot.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Message-ID: <67FF7890FC3B18EF24B48C89@JcK-HP8200.jck.com>
In-Reply-To: <5087C57A.80607@gmail.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> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <5087C57A.80607@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>, Ian Hickson <ian@hixie.ch>
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 11:38:59 -0000

--On Wednesday, October 24, 2012 11:39 +0100 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> 
> On 23/10/2012 00:32, Mark Nottingham wrote:
> ...
>> The underlying point that people seem to be making is that
>> there's legitimate need for URIs to be a separate concept
>> from "strings that will become URIs." By collapsing them into
>> one thing, you're doing those folks a disservice. Browser
>> implementers may not care, but it's pretty obvious that lots
>> of other people do.
> 
> Thanks for bringing this point out. It was explained to me in
> 1993 by TBL and Robert Cailliau that URLs (the only term used
> then, I think) should never be typed in by a user, and
> preferably never even seen by a user. It's because that
> doctrine was abandoned a year or so later that we have this
> problem today. I think there would be value in a document
> making this clear, as a framework for clearly separating the
> specification of what is allowable as a URI on the wire from
> what is acceptable as a user input string (UIS?).
> 
> UIS to URI conversion may well end up as a heuristic algorithm.

Very useful perspective, IMO.

Seen that way, IRIs might then be considered a different flavor
of UIS.  Less heuristic than some, but not a flavor of URI.

best,
   john