Re: [urn] URN:DOI namespace registration request

worley@ariadne.com Mon, 18 January 2021 17:11 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 D32E33A0AF3 for <urn@ietfa.amsl.com>; Mon, 18 Jan 2021 09:11:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.985
X-Spam-Level:
X-Spam-Status: No, score=-0.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 ICjL2orJVGuG for <urn@ietfa.amsl.com>; Mon, 18 Jan 2021 09:11:56 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (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 7462F3A0AC5 for <urn@ietf.org>; Mon, 18 Jan 2021 09:11:56 -0800 (PST)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-06v.sys.comcast.net with ESMTP id 1U5GlW9uDsjoS1Y4Jlklii; Mon, 18 Jan 2021 17:11:55 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1610989915; bh=InObH95dFhHI4nMrM/nrBj4VzWs3y8YH5xRsz8kiLYg=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=d1K+yySQMbFSWCodyMZZ3+Rqkceowj8OIWCKPbyNMREi3jrRvsUxa/iQXjgOJZUCa ZkFhbj088FQcaVQoU9hUChwW3w5113e2spXQcgc50PJl1DXR3FkSLLrpmdZX26Kxy3 Yl+SOePziLt9iKSHvwfqp3Lfe6ZsZsfWw5dq9fHsljUY330E51J3FytXrV3A/TqmIQ 1o8qGBSYnUVF2g57aXQHj5+oNt9jA7sVZC6s14uzQVhlab0ZfAl2yoyhRp8XI6jFUH p94gVSJrhppY1OKJris0tL21+cvS8lzXV0oJOUnE+O5jmTv69TbMePsMLOn/tSAY6t 9jzy5OVoDGcGw==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-01v.sys.comcast.net with ESMTPA id 1Y4Gl1EEk7swd1Y4Hl90DT; Mon, 18 Jan 2021 17:11:54 +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 10IHBoSb018586; Mon, 18 Jan 2021 12:11:50 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 10IHBn0O018583; Mon, 18 Jan 2021 12:11:49 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: "Hakala, Juha E" <juha.hakala@helsinki.fi>
Cc: urn@ietf.org, llannom@cnri.reston.va.us, john@jck.com, paul@countyanalytics.com, jonathanmtclark@gmail.com
In-Reply-To: <HE1PR07MB3196DBADE6019EF3794C90ADFA310@HE1PR07MB3196.eurprd07.prod.outlook.com> (juha.hakala@helsinki.fi)
Sender: worley@ariadne.com
Date: Mon, 18 Jan 2021 12:11:49 -0500
Message-ID: <87ft2ygofe.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/aKRBZQMsaSUVhqp-cx0eY-Ng0s8>
Subject: Re: [urn] URN:DOI namespace registration request
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, 18 Jan 2021 17:11:58 -0000

My apologies for not attending to this sooner.

I'm afraid I object to this registration as a matter of principle,
rather than a matter of details.  The inclusion of the DOI space as part
of the URI space should be done through the implementation of the doi
URI scheme -- as has already been proposed -- and the details of that
should be fixed by the DOI Handbook.

Looking at the benefits listed in the proposed registration, they are as
easily obtained by use of doi URIs as they are by doi URNs.

Given the provisional registration of the doi scheme, it appears that
the DOI Foundation intends to establish the details of the scheme.  It
would be unwise for us to establish an entirely parallel defintion as a
namespace, where for sanity's sake, the two definitions would have to be
maintained in exact alignment.

Dale