Re: [urn] DOI URN namespace registration

worley@ariadne.com Mon, 25 May 2020 01:21 UTC

Return-Path: <worley@alum.mit.edu>
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 B184C3A0A35 for <urn@ietfa.amsl.com>; Sun, 24 May 2020 18:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Level:
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 veJgjgTYfL3U for <urn@ietfa.amsl.com>; Sun, 24 May 2020 18:21:29 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 695973A09D7 for <urn@ietf.org>; Sun, 24 May 2020 18:21:29 -0700 (PDT)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-07v.sys.comcast.net with ESMTP id d1hvjib5NSe0Rd1nzjczIS; Mon, 25 May 2020 01:21:27 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1590369687; bh=EQqE+Uz4hgUAZGbUj5iWtuambSL88tft4prpqLAbQQQ=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=aFN1F/AbvK2pgz/9GsHjevlPWDYSxEh0GXe9F5DhRY3/NpSd10DioPwun9cSvAkCN m8FQNUng73Pbbv81CpZDUrWcmXPNiPGjjABSHrNDBqKN5i690s/OaDRKKX8wRFWL31 RQ2pVLtVzDvadZnCP/7aoUJcB6FNEo/40xnv6lNj0+bXyHbapU+5H+6VAPMfCtesQb OQDik932tO8uz95gEe5u+L87h4h1vAO7BA6wX9p3tsimkJvlDk5yN6ichq9JTmnsaj pbTZLygq4kXkdJ2ru6Kpz//5X+HIK9MU4p/qsfzFJRRGyuee5LYytyU5R7cmmRpWJl V7la9nbT4bsQA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-02v.sys.comcast.net with ESMTPA id d1nvjfYYINezdd1nwjJyNU; Mon, 25 May 2020 01:21:24 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 04P1LMv3003593; Sun, 24 May 2020 21:21:22 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 04P1LMhn003588; Sun, 24 May 2020 21:21:22 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "John Levine" <johnl@taugh.com>
Cc: urn@ietf.org
In-Reply-To: <20200524165038.DE61B199447E@ary.qy> (johnl@taugh.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 24 May 2020 21:21:22 -0400
Message-ID: <875zcklsh9.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/VNL9SZ37C37RNHo-8vBgnZH7Wxg>
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 01:21:31 -0000

"John Levine" <johnl@taugh.com> writes:
> ...
> Given that DOIs are usually resolved by looking up URLs, it is clear
> that in practice they are compatible with URLs because they *are*
> URLs.
> ...

Unless they've retroactively removed non-ASCII characters from being
valid in DOIs, then it's certain that DOIs *aren't* URLs, and quite
possible that nobody has ever properly specified how DOIs are mapped
into URLs for lookup.

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

It certainly seems preferable to solve the general case rather than just
the special case.  But I notice that though I can't remember anything
about "the handle system", my subconscious supplies a frisson when I
read that phrase.

Dale