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

Carsten Bormann <cabo@tzi.org> Fri, 15 October 2021 11:18 UTC

Return-Path: <cabo@tzi.org>
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 A0EF73A1324 for <rfc-markdown@ietfa.amsl.com>; Fri, 15 Oct 2021 04:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 P7iiTGpLWlmK for <rfc-markdown@ietfa.amsl.com>; Fri, 15 Oct 2021 04:18:28 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A8003A1171 for <rfc-markdown@ietf.org>; Fri, 15 Oct 2021 04:18:28 -0700 (PDT)
Received: from smtpclient.apple (p5089a8ac.dip0.t-ipconnect.de [80.137.168.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HW3fm36JHz2xdJ; Fri, 15 Oct 2021 13:18:24 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <D69D35CD-CE36-477F-AC9D-FFFC50381C79@eggert.org>
Date: Fri, 15 Oct 2021 13:18:23 +0200
Cc: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E07AC75D-8E78-49B2-BA49-5B1B8515C44A@tzi.org>
References: <57C9F625-F034-467B-A83A-67EF90E18385@eggert.org> <2343E50C-63B4-44F7-96A7-30FF8286DBCF@tzi.org> <D69D35CD-CE36-477F-AC9D-FFFC50381C79@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/mXLnLahdjjkbvsPBrPABZPvdWTA>
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: Fri, 15 Oct 2021 11:18:34 -0000

On 15. Oct 2021, at 12:36, Lars Eggert <lars@eggert.org> wrote:
> 
> I have no idea. The whole DOI thing seems pretty sloppily put together; unfortunately it's what the publishing industry adopted though.

That was easy:

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.

> For example, https://dl.acm.org/doi/10.5555/206746 has a DOI via the ACM that doi.org refuses to resolve. Fun.

That is a different thing, as John Levine explained to me.
Books don’t have DOIs, but ACM uses a DOI-like namespace for books.
(Doesn’t anyone think of the children^W users?)

Grüße, Carsten