Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Julian Reschke <julian.reschke@gmx.de> Tue, 30 May 2017 05:45 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24A8128D16 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 22:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.58
X-Spam-Level:
X-Spam-Status: No, score=0.58 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-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 whE6BXnSgUhZ for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 22:45:21 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 E908B120727 for <xml2rfc@ietf.org>; Mon, 29 May 2017 22:45:20 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.66.43]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lm7MT-1dodjF3wqP-00ZcTW; Tue, 30 May 2017 07:44:49 +0200
To: John R Levine <johnl@taugh.com>, Henrik Levkowetz <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
References: <20170526165214.45384.qmail@ary.lan> <592C9B8F.2050504@levkowetz.com> <alpine.OSX.2.21.1705291809080.51625@ary.qy>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <e79db540-0ddf-f8bf-f3c6-7890315fb814@gmx.de>
Date: Tue, 30 May 2017 07:44:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1705291809080.51625@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:99KAR4sJowf4nBj0xEthXIAATVKFIAx2AeqR+sUChCOAmBFyXPN 76jfEZBCn/tWi8IVgPYDKQiX1iuVBEAx8r6i4CqCtWh5fki21mohYVIteSJ2ZMsq5vxN9Kg 3iZTZOE4e0b8mgp4drjHqxV3LIpTMP2tXUmKgMIQsuf/UL4SyJj/U+j/43Dwl+cNQn39WJn BQ7s4OBcN9md9gQz82K7g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:W+hJNoFog94=:NBF9piaH8P4RaVDwtXhONJ hHJrB7nRmI2pQS28SRnZQuZTQ60+yGCaes2gxUUZSA9JxqMfr+/ywebxXUvsPhwuVAE6o5oME 3dPdjTXaGvnsvpUU9Tz8rw8Ajl9g0OG/+I/a/oUrClUhXxPT90N8x5qt+9cigiWbtT3SXfk5q I9abB/jtgJR5oO2HPE7U14uNRiuJKfB8dPtEUw00ExGZiuDtGC0IMke52ggxVpCAnEkbHLwu6 Jh1LxbH3YBBDedfOmgPrTCHA3HxhihogHwKlSNrG8VVrOI1PcGnrmqlOnLFQyJ7b2Nwd0OBav /76E+y2AmIK/uAVfQAzs2jcrF4wNJRWBWndMxQRppFP6KTB8rxl63Hta00TJv5Q0kfUUQmOb9 hoR3a5UPHpPt2ER01b4RwaQh8SqGeadDv70uzy1/nJ/IwGith3X0QCFeAZKHvMl7c+Msm63u4 Ems9o467wrLrFU1MiCsNTk7TexDenyinIb3lO4pFtfDbj54PstB4ImJd5h02HkVBphlXVSkq1 R4vmsazXMEX3vpHh2u5Mo5fKIZ+ZhzcOWmT6TYKUKKo33qQlR/mo9bOYnv7zIDuJXe2X7QA9c U2vqx5W0J4SE0aNcile5y6qlQPPYdMbTGlMYVhA/o8pxt5vxNsFUYZlMBsClyVLQZ0R1O1nlU N6iTxTR/F/W45TcBMXdjhDO9HdiZ3tn6AbCC3gBE44/QoZZEAmsRs+JGKcg+UHMcEt3G3xccr 7rN1E8Lw6HPEopd/Lr4hsWPdcvn4DAwKJhND6ZUMP6+5qNYi6JjTXeiwjbAPpjErJM9vQZh/K s2NOvKl
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/d-OqM9K7Tt0l5uic8JwJLl-Ci9o>
Subject: Re: [xml2rfc] RFC Bibtex format doi numbering incorrect
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 May 2017 05:45:22 -0000

On 2017-05-30 00:26, John R Levine wrote:
> ...
> Among the reasons not to change it is that RFCs can contain references 
> to other kinds of documents, some of those other things also have DOIs, 
> and those DOIs always have to be looked up.  I hope we agree that code 
> that tried to guess some DOIs while looking up others would be fragile 
> and likely to break in obscure ways.
> ...

I did not suggest anything about non-RFC DOIs.

> As far as I can tell all of the code around the IETF that handles DOIs 
> does it correctly except for Julian's, and by this time he could have 
> fixed it with less effort than he's spent arguing that he doesn't want to.

The code we're talking about is *validation* code. It works for all 
published RFCs, and already has helped fixing broken references (when 
someone else copy/pasted a reference entry together).

I could fix this if there was an efficient way to lookup RFC information 
from rfc-editor.org, but that would require:

1) that the information is available per RFC (or set of RFCs), so it's 
not needed to pull the whole database

2) that the information is CORS-enabled, so it can be retrieved as side 
effect of displaying something in a browser

(that request isn't new, FWIW)

Best regards, Julian