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

Ted Hardie <ted.ietf@gmail.com> Mon, 03 May 2010 23:22 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 7C86E28C343 for <uri-review@core3.amsl.com>; Mon, 3 May 2010 16:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.217
X-Spam-Level:
X-Spam-Status: No, score=0.217 tagged_above=-999 required=5 tests=[AWL=-0.384, BAYES_50=0.001, 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 SN85kwKVJSTw for <uri-review@core3.amsl.com>; Mon, 3 May 2010 16:22:29 -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 A5FA028C339 for <uri-review@ietf.org>; Mon, 3 May 2010 16:22:24 -0700 (PDT)
Received: by vws11 with SMTP id 11so641723vws.31 for <uri-review@ietf.org>; Mon, 03 May 2010 16:22:07 -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=oot/GkVvT52iIS047D0Rlrh4ziwQg/b6oyeKHhnzo+Q=; b=OY5KzwEi7ODRiJ5N6OsK1e9sHbDs5fAfpvd0oREwq6JkAgTUnZCQPqeJhJqgnQI5Kg C4T3uH8s2ROVrSZgAy9FcMlDrt8cheWMpA5XozIKRRRn2nJaiQ7/oqxrCgtSZNweyDzo RWpPxnCTsr/Uq4z5IrCszRHuW8WYAbYOpUOr4=
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=LjQCMWprXWU8Z4i7/8X1QSK3mwTd21htNmfk6K90RShxyMPOrfV1BnteJR76v7ONNo 8Xe+ZTuAeN0raT3okKefAo1I1yv32xICxccibx6nExn8Xz3Dozps3bCFKb1mV9g4CbBp N1ihVMnsWmw+qAfXE6t9io8+Ed3gNZ3MOmEKw=
MIME-Version: 1.0
Received: by 10.220.107.105 with SMTP id a41mr2131447vcp.179.1272928921715; Mon, 03 May 2010 16:22:01 -0700 (PDT)
Received: by 10.220.48.168 with HTTP; Mon, 3 May 2010 16:22:01 -0700 (PDT)
In-Reply-To: <C804A79E.1FC1C%weibel@oclc.org>
References: <k2p6e04e83a1005031554g217a9c1coe3b1fcb193ccbe82@mail.gmail.com> <C804A79E.1FC1C%weibel@oclc.org>
Date: Mon, 03 May 2010 16:22:01 -0700
Message-ID: <u2h6e04e83a1005031622z655fdb13s401a0ef1e6738b97@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Stu Weibel <weibel@oclc.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: uri-review@ietf.org, Library of Congress Ray Denenberg <rden@loc.gov>
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:22:31 -0000

On Mon, May 3, 2010 at 4:17 PM, Stu Weibel <weibel@oclc.org> wrote:
> 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
>

It is an inherent property?  No.  Is it a property that those requesting
to manage namespaces under the urn scheme sign up for?  Yes.
If you don't want that property, flagging your identifier with something
that will indicate that property is a bad idea.

In other words, I think we agree.

regards,

Ted
>
> 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
>>
>
>
>