Re: [Uri-review] New icon URI scheme vs new URN namespace

Eran Hammer-Lahav <eran@hueniverse.com> Mon, 03 May 2010 23:11 UTC

Return-Path: <eran@hueniverse.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 A78E13A6B20 for <uri-review@core3.amsl.com>; Mon, 3 May 2010 16:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.485
X-Spam-Level:
X-Spam-Status: No, score=-1.485 tagged_above=-999 required=5 tests=[AWL=-0.975, BAYES_05=-1.11, J_CHICKENPOX_47=0.6]
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 cbr7VUeEWvev for <uri-review@core3.amsl.com>; Mon, 3 May 2010 16:11:02 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 8F0EC3A6857 for <uri-review@ietf.org>; Mon, 3 May 2010 16:10:52 -0700 (PDT)
Received: (qmail 24582 invoked from network); 3 May 2010 23:10:38 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 3 May 2010 23:10:37 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Mon, 3 May 2010 16:10:37 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "Ray Denenberg, Library of Congress" <rden@loc.gov>, "uri-review@ietf.org" <uri-review@ietf.org>
Date: Mon, 03 May 2010 16:10:41 -0700
Thread-Topic: [Uri-review] New icon URI scheme vs new URN namespace
Thread-Index: AcrrEyOFBp/V55/iSkuIKtvvvZ7ONAAAeM2A
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723439323D08EB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <r2q743256c51004301042jdcf55b3ey6e83dba78d82f943@mail.gmail.com><1272674619.30704.3371.camel@dbooth-laptop> <90C41DD21FB7C64BB94121FBBC2E723439323D08CD@P3PW5EX1MB01.EX1.SECURESERVER.NET> <093e01caeb13$15002f00$18af938c@lib.loc.gov>
In-Reply-To: <093e01caeb13$15002f00$18af938c@lib.loc.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Uri-review] New icon URI scheme vs new URN namespace
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: Mon, 03 May 2010 23:11:03 -0000

I was referring to the recent discussion on this list about which term should be used (URI vs URL).

We have URIs, and they come in different flavors and colors. When we have a need to identify a new resource, we first look at the existing schemes to see if they are applicable. If not we propose new schemes. URN offers specific benefits and shortcomings. Their name is a shortcoming when it comes to getting the web developers community at large to recognize and use them. This doesn't make them less useful, but it does pose an adoption limitation.

The point I was trying to make it that just because something *can* be implemented as a urn: namespace, doesn't mean it *must* be. At the same time, I think the authors should explain why they think it should/shouldn't be.

EHL

> -----Original Message-----
> From: uri-review-bounces@ietf.org [mailto:uri-review-bounces@ietf.org]
> On Behalf Of Ray Denenberg, Library of Congress
> Sent: Monday, May 03, 2010 3:51 PM
> To: uri-review@ietf.org
> Subject: Re: [Uri-review] New icon URI scheme vs new URN namespace
> 
>  "We are trying to get people to stop making distinctions between URNs,
> URLs, and URIs."
> 
> Could you clarify that sentence.  It seems to suggest that URN, URL, and URI
> all mean the same thing, and I'm sure that's not what you're trying to say.
> 
> --Ray
> 
> ----- Original Message -----
> From: "Eran Hammer-Lahav" <eran@hueniverse.com>
> To: "David Booth" <david@dbooth.org>; "Pierre-Antoine LaFayette"
> <pierre@alumni.utoronto.ca>
> Cc: <uri-review@ietf.org>
> Sent: Monday, May 03, 2010 6:37 PM
> Subject: Re: [Uri-review] New icon URI scheme vs new URN namespace
> 
> 
> >I disagree with making general classifications.
> >
> > URNs suffer a significant lack of public understanding and stigma
> > (regardless whether it is justified or not). We are trying to get people
> > to stop making distinctions between URNs, URLs, and URIs. The decision
> > whether to register a new URI scheme vs. a new URN namespace must not
> be
> > limited to whether it is practical to use a URN. I have a few use cases
> > for a new URI scheme where a urn: prefix will pose a serious adoption
> > problem because of lack of URN understanding (draft pending).
> >
> > As for the icon URI scheme, it is up to the authors to decide if their
> > scheme will suffer or benefit from using the urn: scheme and make their
> > case for it.
> >
> > EHL
> >
> >> -----Original Message-----
> >> From: uri-review-bounces@ietf.org [mailto:uri-review-bounces@ietf.org]
> >> On Behalf Of David Booth
> >> Sent: Friday, April 30, 2010 5:44 PM
> >> To: Pierre-Antoine LaFayette
> >> Cc: uri-review@ietf.org
> >> Subject: Re: [Uri-review] New icon URI scheme vs new URN namespace
> >>
> >> On Fri, 2010-04-30 at 13:42 -0400, Pierre-Antoine LaFayette wrote:
> >> > In my provisional URI scheme registration request with IANA, my
> >> > reviewer noted that it may be preferable to use a URN namespace
> rather
> >> > than create a new URI scheme.
> >> >
> >> >
> >> > E.g.
> >> >
> >> > urn:icon:ext:pdf:small
> >> > urn:icon:mime:text:plain:64
> >> > urn:icon:unknown
> >> >
> >> >
> >> > instead of:
> >> >
> >> >
> >> > icon:.pdf;small
> >> > icon:text:plain;64
> >> > icon:unknown
> >> >
> >> >
> >> > I wanted to run this by the list to see what the general opinion is on
> >> > this matter. What are the advantages/disadvantages and limitations of
> >> > each? I'm not sure which is more appropriate for the icon URI's use
> >> > cases.
> >> >
> >> >
> >> > http://draft-icon-uri-scheme.googlecode.com/hg/draft-lafayette-icon-
> ur
> >> > i-scheme-00.html
> >> >
> >> >
> >> I agree with your reviewer.  IMO, if there isn't a new protocol defined
> >> for it,
> >> there is no need for a new URI scheme.  URNs are intended for exactly
> >> this
> >> kind of thing.
> >>
> >>
> >>
> >> --
> >> David Booth, Ph.D.
> >> Cleveland Clinic (contractor)
> >>
> >> Opinions expressed herein are those of the author and do not necessarily
> >> reflect those of Cleveland Clinic.
> >>
> >> _______________________________________________
> >> Uri-review mailing list
> >> Uri-review@ietf.org
> >> https://www.ietf.org/mailman/listinfo/uri-review
> > _______________________________________________
> > Uri-review mailing list
> > Uri-review@ietf.org
> > https://www.ietf.org/mailman/listinfo/uri-review
> 
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review