IETF Logo Mail Archive

Re: [Rfc-markdown] How to cite this DOI?

John R Levine <johnl@taugh.com> Sat, 16 October 2021 01:53 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B6453A153A for <rfc-markdown@ietfa.amsl.com>; Fri, 15 Oct 2021 18:53:41 -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 (2048-bit key) header.d=iecc.com header.b=nL+yYeUb; dkim=pass (2048-bit key) header.d=taugh.com header.b=ZujypU4w
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 uFKWztWqtxPU for <rfc-markdown@ietfa.amsl.com>; Fri, 15 Oct 2021 18:53:35 -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 64F393A1539 for <rfc-markdown@ietf.org>; Fri, 15 Oct 2021 18:53:35 -0700 (PDT)
Received: (qmail 3055 invoked from network); 16 Oct 2021 01:53:32 -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:content-transfer-encoding; s=bed.616a309c.k2110; bh=wgIJUNrggc+f6rO3Y/Nl9djSIuh5/58R1sXbbr6l+mA=; b=nL+yYeUbuuavs0YJ7q602O/xcqZ2O5bTNKZhCHd1/cCNzr7bLNkSymrqwR6u6eFaKdKbUbT8qQ99kr+vItN1VZnQOFhAl3ahfV5Jg3uG6fP8wlg9b77+/2Fbb01H8qKfAhtHCpKALuQqAFrWqbU8+VgCiOPtchuFOcI8+kcWL3ttFlYP9jur+wuwj8+IL76TalT1zOKlKsu5sUTNlK+PaXhTwz3VuAjPEC0WS2c6iZzSEDCmMO/8vhgiSEMruc6dVnkp18NWFM28L1QNILvx9zHlfo8usPqkGWcJ51RYvn1XTfjr9+4e+W9GZK2o4Cpu4HiKPoOxjHxPA+kg3fHxfA==
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:content-transfer-encoding; s=bed.616a309c.k2110; bh=wgIJUNrggc+f6rO3Y/Nl9djSIuh5/58R1sXbbr6l+mA=; b=ZujypU4wPfDPSyqxxihm26Z1obTqx2hBNy+uSxzU+iDCB71NWGqDrcwSC4ffoyPCr9IAhHwn6ptw1ORJqaRLKksj0LGuC812RhwC2KD+O/bdMy3XnfRe1/4kudlhDYmacDPwQKSJajBuIT1n4d/uugTX9Gdqp3mRK62xwnpt04Sfu5oKKaoS6vrbNnimdQIDNofB+Y/niW+leKAsR+PGmIgbXrFVR9u75c6q6COdGUI1spSQY77nzI6tA5IEDvArfAtN8RNIF7fJsZKEPFCxkSjs1y5v/ziG+BzOIzHfQ/zN2wY1s+6XF6SGvuWdRnIa95VMiWoJAwBAHoeujicw7A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 16 Oct 2021 01:53:32 -0000
Received: by ary.qy (Postfix, from userid 501) id BD0D12A69B0B; Fri, 15 Oct 2021 21:53:31 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 51A172A69AED; Fri, 15 Oct 2021 21:53:31 -0400 (EDT)
Date: 15 Oct 2021 21:53:31 -0400
Message-ID: <3e3d8cbe-49b-69bd-67a-878aabbbae2c@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: rfc-markdown@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <733C184A-8BFD-4EDE-92E6-5B5E4843B811@tzi.org>
References: <20211015210234.A1BA52A66EE4@ary.qy> <733C184A-8BFD-4EDE-92E6-5B5E4843B811@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/X5K_VtN57vKliJ8D13lSR5AjCgM>
Subject: Re: [Rfc-markdown] How to cite this DOI?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2021 01:53:41 -0000

On Sat, 16 Oct 2021, Carsten Bormann wrote:
>>> https://www.doi.org/doi_handbook/2_Numbering.html#2.2.1
>>>
>>>>> The DOI name is case-insensitive and can incorporate any printable characters from the legal graphic characters of Unicode. Further constraints on
>>> character use (e.g. use of language-specific alphanumeric characters) can be defined for an application by the ISO 26324 Registration Authority.
>>>
>>> You can’t make this stuff up.
>>
>> How soon they forget.  DOIs are an instance of the handle system, whose syntax is defined in RFC 3651.  It does indeed allow any UTF-8 encoded
>> Unicode 2.0 character, but since the handle system also had its own retrieval protocol, quoting wasn't a problem.
>
> Does “printable character” include ZWNJ?  If not, how do I get a correct representation of the Auf‌lage (*) of a digital object?
> The term “case-insensitive” doesn’t even mean anything without a locale.
> (Well, you know all this, but I want to remind everyone why this choice just boggles the mind.)

If you believe RFC 3650, handles are UTF-8 encoded Unicode 3.0, but if you 
believe the ABNF in RFC 3651, it is UTF-8 encoded Unicode 2.0.  Either 
way, ZWNJ is allowed so you are in luck.  I'm more interested in what 
happens when my handles contain uncomposed accented characters 
and surrogates.

I have no idea what "printable characters from the legal graphic 
characters of Unicode" means and neither do they since Unicode doesn't 
define printable.

> Parentheses are just fine in a URL (e.g., I use them all the time on cbor.me [1]).
> Everything is wrong about using anything but [-A-Za-z0-9.]+ in the components of a DOI [2]; Elsevier would not have had to do that.

Well, yeah. You'll notice the handles in RFC DOIs currently include the 
letters R, F, C, and digits 0-9.  I considered being more clever but 
decided not to.

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

v2.8.7 | Report a Bug | By Email