W3C home > Mailing lists > Public > uri@w3.org > October 2012

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>
Date: Mon, 22 Oct 2012 15:11:38 -0700
Message-ID: <CAHBU6isuainUDbAMPTjGJ3rQEE8Ru22ufMKDNDHWxbGLk4T8pg@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>, mnot@mnot.net
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

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
Received on Monday, 22 October 2012 22:12:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:16 UTC