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

Ted Hardie <ted.ietf@gmail.com> Mon, 03 May 2010 22:55 UTC

Return-Path: <ted.ietf@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 3D2A23A6B4A for <uri-review@core3.amsl.com>; Mon, 3 May 2010 15:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.154
X-Spam-Level:
X-Spam-Status: No, score=-0.154 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_20=-0.74, 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 Z34MX3vmgsWg for <uri-review@core3.amsl.com>; Mon, 3 May 2010 15:55:12 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id A539E3A68B9 for <uri-review@ietf.org>; Mon, 3 May 2010 15:55:11 -0700 (PDT)
Received: by vws11 with SMTP id 11so618982vws.31 for <uri-review@ietf.org>; Mon, 03 May 2010 15:54:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=txADypKg9rotPa/1zNIUu5jQvWxqXxcYv7pvci1Gi78=; b=GE0PEAaRnvif/lR4J02VniSqdhU2rii+1kEdamer/BOwuJZCbFHM5Ig/Qf3S1OT6nJ ltHiIq5vMC5/qE11JCAxSlLfOCugjpU74avRE7FOHDqYSE1JXQRsvm1QKLAImmFZEblt iKLe63/0BildSqciGD1kShL3vrz/MAIIR+D+A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TM5eHFRQzQbCPDBoxu9Sz2H+67nAmOZPxm6fSDfm+EsZNY8MPK0krKDEEZI/4p6YWB RKVtZhIvvGP5SZ0nO8R8hzsdyNktkkhOsTmaytoCEQIuiOnhzT3Gubhe/lCZQ7vZF5pH P75uYgYUTMn6clTQTh13qUwF4krzfj23e4NVw=
MIME-Version: 1.0
Received: by 10.220.157.197 with SMTP id c5mr10767891vcx.120.1272927285330; Mon, 03 May 2010 15:54:45 -0700 (PDT)
Received: by 10.220.48.168 with HTTP; Mon, 3 May 2010 15:54:45 -0700 (PDT)
In-Reply-To: <093e01caeb13$15002f00$18af938c@lib.loc.gov>
References: <r2q743256c51004301042jdcf55b3ey6e83dba78d82f943@mail.gmail.com> <1272674619.30704.3371.camel@dbooth-laptop> <90C41DD21FB7C64BB94121FBBC2E723439323D08CD@P3PW5EX1MB01.EX1.SECURESERVER.NET> <093e01caeb13$15002f00$18af938c@lib.loc.gov>
Date: Mon, 03 May 2010 15:54:45 -0700
Message-ID: <k2p6e04e83a1005031554g217a9c1coe3b1fcb193ccbe82@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "Ray Denenberg, Library of Congress" <rden@loc.gov>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: uri-review@ietf.org
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 22:55:13 -0000

I would agree to this request and add who "we" is in the sentence.  It
is not the
IETF, obviously, since the IETF recognizes that URNs are a class of URIs
with specific properties (e.g. persistence).

regards,

Ted

On Mon, May 3, 2010 at 3:50 PM, Ray Denenberg, Library of Congress
<rden@loc.gov> wrote:
> "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
>