IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Fri, 15 October 2021 10:36 UTC

Return-Path: <lars@eggert.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 9AB7D3A1914 for <rfc-markdown@ietfa.amsl.com>; Fri, 15 Oct 2021 03:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 LbPbUWDKAD_Z for <rfc-markdown@ietfa.amsl.com>; Fri, 15 Oct 2021 03:36:27 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CB673A1912 for <rfc-markdown@ietf.org>; Fri, 15 Oct 2021 03:36:27 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:3120:db61:932b:49a7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 5A6E3600B18; Fri, 15 Oct 2021 13:36:17 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1634294177; bh=h8NhEUOXwempq/J6gqRDBYT/vPJOsVz/zj7MTAnIveY=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=CMdIRhOL2S80LnvCshRIeZX+157i+Z7gQbnQGwvTDMFCz/n8CrOsknpdRhJBIsQtw OZ70IqdPfxKJ+5cJC2NEO7EUyDZSkAeAM8pbA0X+j0V/PXTM5GMYTfmRG11ClJYhAK GQjpqRQpuRAhM2hKoYqb9e/a2AMof3cvuiABYW2U=
From: Lars Eggert <lars@eggert.org>
Message-Id: <D69D35CD-CE36-477F-AC9D-FFFC50381C79@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_68C13FCA-3061-4179-B6D1-0D153101C1C9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Fri, 15 Oct 2021 13:36:15 +0300
In-Reply-To: <2343E50C-63B4-44F7-96A7-30FF8286DBCF@tzi.org>
Cc: rfc-markdown@ietf.org
To: Carsten Bormann <cabo@tzi.org>
References: <57C9F625-F034-467B-A83A-67EF90E18385@eggert.org> <2343E50C-63B4-44F7-96A7-30FF8286DBCF@tzi.org>
X-MailScanner-ID: 5A6E3600B18.A2224
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/wz6L7eJxTp2npBugj9PpDfr_tRA>
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 10:36:33 -0000

Hi,

On 2021-10-15, at 13:04, Carsten Bormann <cabo@tzi.org> wrote:
> Worked around now in 1.5.10.

thanks!

>> Any hints?
> 
> Is there a defined syntax for DOIs?
> (What other weird characters are allowed in there?)

I have no idea. The whole DOI thing seems pretty sloppily put together; unfortunately it's what the publishing industry adopted though.

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

Lars

v2.8.7 | Report a Bug | By Email