Re: [urn] DOI URN namespace registration

worley@ariadne.com Sun, 24 May 2020 16:06 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 62F033A0B04 for <urn@ietfa.amsl.com>; Sun, 24 May 2020 09:06:05 -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 A2SuL46q3dII for <urn@ietfa.amsl.com>; Sun, 24 May 2020 09:06:02 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 AE33A3A0B01 for <urn@ietf.org>; Sun, 24 May 2020 09:06:02 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-10v.sys.comcast.net with ESMTP id csydjN2M3320yct8SjUwm9; Sun, 24 May 2020 16:06:00 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1590336360; bh=CWFUln9tBANfMTn3eaFf4bUXoIGZOb4ig1fVayA0HG4=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=QC9s53rDIS0rskMumGREV+AjZNh+jEAYbVMKsTvBo7YWcvjDOJq6A8httZB/uMSVQ z5JH9vS9jVFP0pYmsvSWmT587XPd5Fb2pJ6+tVWCizA5mW15mYYbpK2n9HDlFGuXZT U83m9rsQndLIsh4b7vQHfEDEK/2cmAXn4aW69YkCJO3iH6mxfzmA/dwEBtBsot36RT YQgt+vR5gA4SQwIv1b2K0N9RvW4jBu2t5RvFdpGUfQEzRu0dAGZ1BR1oz+qQjTiMqj UmQcjpG5/8VDXMamaOSEQ8T33t2ULS8OP8ckEL7DFlUm8rEaFaymbMSWAthjSX1GLq r+mhpSxfAqeBA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-12v.sys.comcast.net with ESMTPA id ct8RjHkXxuSuIct8SjtCH3; Sun, 24 May 2020 16:06:00 +0000
X-Xfinity-VMeta: sc=0.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 04OG5xck005101 for <urn@ietf.org>; Sun, 24 May 2020 12:05:59 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 04OG5wZC005098; Sun, 24 May 2020 12:05:58 -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: urn@ietf.org
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 24 May 2020 12:05:58 -0400
Message-ID: <87ftbpl3mh.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/A3ZH8UEw7lmG4sjHEupOoSngtH8>
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: Sun, 24 May 2020 16:06:06 -0000

"Hakala, Juha E" <juha.hakala@helsinki.fi> writes:
> [...] I have been asked to write a namespace registration request for
> DOI, and that may have a major impact on both URN and DOI
> systems. That request needs to be processed promptly.

I was going to ask, As an opening question has consideration been given
to registering DOI as a URI scheme?  My memory is that DOIs are written
in a format that is compatible with URI syntax.

But the Wikipedia page says "Most legal Unicode characters are allowed
in these strings, which are interpreted in a case-insensitive manner."
So DOI syntax is not compatible with URI syntax.  And what "case
insensitive" means in a fully internationalized context is (in my
memory) not well-defined.

So yes, there are going to be some complexities.

Dale