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

Stu Weibel <weibel@oclc.org> Mon, 03 May 2010 23:17 UTC

Return-Path: <weibel@oclc.org>
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 1548628C2BD for <uri-review@core3.amsl.com>; Mon, 3 May 2010 16:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.064
X-Spam-Level: ***
X-Spam-Status: No, score=3.064 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_47=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
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 5-Yz8dxFC7Rg for <uri-review@core3.amsl.com>; Mon, 3 May 2010 16:17:53 -0700 (PDT)
Received: from mshieldserver1.oclc.org (mshieldserver1.oclc.org [132.174.29.209]) by core3.amsl.com (Postfix) with SMTP id 9D3B33A6B62 for <uri-review@ietf.org>; Mon, 3 May 2010 16:17:52 -0700 (PDT)
Received: From OAEXCH4SERVER.oa.oclc.org ([132.174.29.227]) by mshieldserver1.oclc.org (WebShield SMTP v4.5 MR3) id 1272928655874; Mon, 3 May 2010 19:17:35 -0400
Received: from 132.174.105.36 ([132.174.105.36]) by OAEXCH4SERVER.oa.oclc.org ([132.174.29.214]) via Exchange Front-End Server owa2.oclc.org ([132.174.29.192]) with Microsoft Exchange Server HTTP-DAV ; Mon, 3 May 2010 23:17:34 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 03 May 2010 16:17:34 -0700
From: Stu Weibel <weibel@oclc.org>
To: Ted Hardie <ted.ietf@gmail.com>, Library of Congress Ray Denenberg <rden@loc.gov>
Message-ID: <C804A79E.1FC1C%weibel@oclc.org>
Thread-Topic: [Uri-review] New icon URI scheme vs new URN namespace
Thread-Index: AcrrFs+0hjeDwpns+EqkSxZYmuBNvA==
In-Reply-To: <k2p6e04e83a1005031554g217a9c1coe3b1fcb193ccbe82@mail.gmail.com>
Mime-version: 1.0
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 23:17:54 -0000

At the risk of dredging up the corpses of old arguments, I would suggest
that URNs do NOT have a property of persistence.  They are intended to be
managed as persistent identifiers, and are structured so as to make that
more straightforward, but identifier persistence has little to do with the
the identifier per se.  Rather, it has to do solely with the commitment of
organizations that adopt the responsibility for managing such identifiers
(and their enabling infrastructure) persistently.  The technology can make
that harder or easier, but assures nothing.  There is no intrinsic
persistence property.

stu


On 5/3/10 3:54 PM, "Ted Hardie" <ted.ietf@gmail.com> wrote:

> 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
>> 
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>