Re: [Uri-review] [uri-review] Review Request for Icon URI Scheme

Joseph Holsten <joseph@josephholsten.com> Fri, 09 April 2010 11:55 UTC

Return-Path: <josephholsten@gmail.com>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC0373A6948 for <uri-review@core3.amsl.com>; Fri, 9 Apr 2010 04:55:08 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PX1aQ3IEQ+Bn for <uri-review@core3.amsl.com>; Fri, 9 Apr 2010 04:55:07 -0700 (PDT)
Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by core3.amsl.com (Postfix) with ESMTP id BD4383A6998 for <uri-review@ietf.org>; Fri, 9 Apr 2010 04:55:07 -0700 (PDT)
Received: by qyk11 with SMTP id 11so2517754qyk.13 for <uri-review@ietf.org>; Fri, 09 Apr 2010 04:55:01 -0700 (PDT)
Received: by 10.224.5.72 with SMTP id 8mr620534qau.96.1270814100861; Fri, 09 Apr 2010 04:55:00 -0700 (PDT)
Received: from [192.168.1.103] (ip70-189-108-199.ok.ok.cox.net [70.189.108.199]) by mx.google.com with ESMTPS id 22sm686980qyk.14.2010.04.09.04.55.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 09 Apr 2010 04:55:00 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Joseph Holsten <joseph@josephholsten.com>
In-Reply-To: <1270811172.29423.261.camel@ophelia2.g5n.co.uk>
Date: Fri, 09 Apr 2010 06:54:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C710E8B7-333B-4D69-8AF2-8D78285D2967@josephholsten.com>
References: <m2v743256c51004050812w2a5a95f2y57104ee6aafa0be6@mail.gmail.com> <1270811172.29423.261.camel@ophelia2.g5n.co.uk>
To: Toby Inkster <mail@tobyinkster.co.uk>
X-Mailer: Apple Mail (2.1077)
Cc: uri-review@ietf.org
Subject: Re: [Uri-review] [uri-review] Review Request for Icon URI Scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2010 11:55:08 -0000

On Apr 9, 2010, at 6:06 AM, Toby Inkster wrote:
> On Mon, 2010-04-05 at 11:12 -0400, Pierre-Antoine LaFayette wrote:
>> I've put together a draft document for an icon URI scheme, used for
>> displaying platform specific icons in web pages, that I would like to
>> get some feedback on.
> 
> This seems to have pretty poor fallback behaviour in existing user
> agents. It would seem advantageous to reuse the existing HTTP scheme.
> 
> Rather than, have a URI of say:
> 
> 	<icon:image/jpeg;32>
> 
> Instead use:
> 
> 	<http://icons.example.net/image/jpeg;32>
> 
> Where icons.example.net is a domain name registered to someone
> shepherding this idea.

As you are recommending it, would you care to host this magic HTTP resource? Of course, we'd want to standardize on your host, as it would be needlessly complicated if every browser group used their own host.

Implementors tend to know where to look when they encounter an unknown URI scheme. Your idea has terrific fallback behaviour, but I'm not sure how best to inform developers that HTTP URIs with a host of icons.example.net. are okay to treat magically. Perhaps a HEAD request could say "More-Magic: icon"?

Also, congrats on the most useful variant of "Let's solve this URI scheme idea with HTTP URIs" that I've encountered this year.
--
http://josephholsten.com