Re: [urn] DOI URN namespace registration

John R Levine <johnl@taugh.com> Mon, 25 May 2020 15:16 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24473A0DAA for <urn@ietfa.amsl.com>; Mon, 25 May 2020 08:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=KvEJeDPc; dkim=pass (1536-bit key) header.d=taugh.com header.b=AF3bZWtO
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dyNsaihSYxkx for <urn@ietfa.amsl.com>; Mon, 25 May 2020 08:16:07 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F1F13A0D83 for <urn@ietf.org>; Mon, 25 May 2020 08:16:05 -0700 (PDT)
Received: (qmail 84688 invoked from network); 25 May 2020 15:16:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=14ac9.5ecbe134.k2005; i=johnl-iecc.com@submit.iecc.com; bh=lbjoG3XSn+DXwwn9RL963w+YQbccD9IVlyPL8y65EaM=; b=KvEJeDPcNXiPAa/pDB9dB48FxgnshBG1A90tmzBG0dH2jivv45RgdoGZH5A/IRis9lJ6hEWDs8u11k7kwFkbSbGuX0YkQsq+lxN2nnC2Gz1feFLt2z3LMVgYYf7ni16CSzUjoLSFfQWzOBvGYepERFmYYQkoZ6IsFR/b6yTgYdF0LyTJCIuG369rpQkZkJp4T4fg4wIiqmxeDQJSWr9+8Jt3WV5qVbHNjWwizVFdLFladI7ix5IT5p+ShuAIDkUv
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=14ac9.5ecbe134.k2005; olt=johnl-iecc.com@submit.iecc.com; bh=lbjoG3XSn+DXwwn9RL963w+YQbccD9IVlyPL8y65EaM=; b=AF3bZWtOkyzau0ALQITC7KV02vgd7dAn69WK3PVjZiktZjHbEfMbJLGY57DauwHwj07d/ow0pnbE8PGRusQwIMt9NcazTnnXLO60XhXDjqlaO/V5eCxewZvUsg1F4UkzDEHq2yooloahkxu1LXfKKLvV8DwSfwN40UeZ4o71fbRvUtW8OYOmFXJPDLoAKFriKFxKrzk7KUlylttSYoIdwFNxou0CegZccYhhJSR8H9iyBltlAfX6jFAC7XG4yuew
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 25 May 2020 15:16:04 -0000
Date: Mon, 25 May 2020 11:16:03 -0400
Message-ID: <alpine.OSX.2.22.407.2005251112490.25546@ary.qy>
From: John R Levine <johnl@taugh.com>
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>
Cc: "urn@ietf.org" <urn@ietf.org>
In-Reply-To: <DB7PR07MB5110EB6820FBF02B27F8485FFAB30@DB7PR07MB5110.eurprd07.prod.outlook.com>
References: <20200524165038.DE61B199447E@ary.qy> (johnl@taugh.com) <875zcklsh9.fsf@hobgoblin.ariadne.com> <DB7PR07MB5110EB6820FBF02B27F8485FFAB30@DB7PR07MB5110.eurprd07.prod.outlook.com>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/x39tLm6tlIQ1M9xAnlcSJYqsmV4>
Subject: Re: [urn] DOI URN namespace registration
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 May 2020 15:16:13 -0000

>> Beyond the case sensitivity thing which I think is a red herring, I
>> would ask why they're asking for a DOI URN rather than a handle URN
>> since they're the same namespace.
>
> Juha: Handle and DOI are different identifier systems although they share the same technical base. DOI system is administered by International DOI Foundation, and they have the mandate to register a URN namespace for DOI (and asked me to help in the process). Handle system and Handle specifications are managed by DONA Foundation, and they have not required registration of a URN namespace for Handles.

Thanks, but that's not what I'm asking.  Is there ever a situation where a 
10.xx/yy DOI and the same 10.xx/yy handle would refer to different 
resources?  I understand that the answer is no.  That's what I mean by the 
same namespace.

As I noted in a previous messages, there are other handles such as the 
ITU's 11.x which resolve as https://doi.org/ URLs, which even more 
strongly suggests they're the same namespace.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly