Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Julian Reschke <julian.reschke@gmx.de> Mon, 29 May 2017 05:49 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 D17FC126DFB for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 22:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level:
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, 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 a9msTX6jMdDc for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 22:49:25 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 12F7B12009C for <xml2rfc@ietf.org>; Sun, 28 May 2017 22:49:24 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.121.164]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LxxKu-1e2aeN1qHE-015I9P; Mon, 29 May 2017 07:49:07 +0200
To: John Levine <johnl@taugh.com>, xml2rfc@ietf.org
References: <20170528214929.56669.qmail@ary.lan>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <038e5bd1-726c-599d-38cf-a65b7385856b@gmx.de>
Date: Mon, 29 May 2017 07:49:06 +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: <20170528214929.56669.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Sht2CcQzNSkkuz/8dxwpeSJv5FQ3pW7fVzY97RkRYlvlhyanzwY JM74QBRGZ8JzOG6FU/lVsr+0tmuAndCC5ILnCX6RJFHORIbd3kKEhsvwvI8KkyP3w+q1oLX 5q//VRZSGmoVvEWDIITRecnH5C/n8X4Lwt02CipQzG85Hk+nJJx2cfTpd4xQqCoOvANpkcw 39DljK0mg6I6SG2s1Pyyg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:TiRyVKpZc48=:IFKpbwI1t0thGbrRb6wUy7 liExRsFibNgYzmKXUuHBfnA5d77pgi2ebvLxZet3MFy/DarxXKJyae556KZDpdMcORgqf3zfZ QhCnRGoaAGImMZSIfsosIGkauHtZCwfluXGqvzCBqVQlyX4aqm7ie0QgH7VzRnqSNLmQGsOoW z1SqCiiuab/DaLy7JXMuZ6R2j+3OvGVu02I0+VVjb8Aso58vRn9dqy7+0aJ6Xi5Vcw7OEz0oY nBoyQFLSmCQWjo4bGSOpnra6gZNSCDFrmu7DmEGlV+e+x6bPSSLkCVS5AxKxyoOEipwO2+cKN +Clo8NYtC3hCbI5pznrf6sSR1mhDeURAf+ku6bKNH8fWb5FNxmAbAyzVbagnt7zE6QV5LFmcC BltHCXECAqv+Cb7FLvbAiTJliPsOS/1ydC4XyamfE1WMILOTLsYHeWgXmw6kk+W9BMzynzYNb 6A289Rf4BFmk2q6H8K0cOQTeihvprOuZiHVmvoVJ6/OMx+0vc6Cm9boIwSJhjZ2H7PRqYFg1W IsWVUgf7Dbjlsb0p/1w2eejwDDIzRfZtBH+0Sau3FRbGmUlDLUnH771NgfljpSywa3FE1yL2A h6BogLK16rYbpC3pUFbm5lZ0D2zsHPMSvOcujBvba6AMpElXb1tBGKgWlYCUbP98qlV63EE2Q QicxLsXApFx5bhyjsU/iNs2nrPA0GbKdpz6+1QwDcdvg8a+kwVS18TXbkIXUYXk/N9xcHYGyj ws0BZSCAB1Pbs3x1FahbkUZgcokIx5SCPTwRAxM1HtpgPqVH0qjuC/7V7/Bn7j0J2ZVrSjg/1 KjSVcnR
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/SDbuD8rZMXio7xIsKEbdWV0NCFk>
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: Mon, 29 May 2017 05:49:27 -0000

On 2017-05-28 23:49, John Levine wrote:
> In article <a9e981dc-d452-026a-915b-613a61863809@gmx.de> you write:
>> On 2017-05-28 17:04, John R Levine wrote:
>>> It's easier to parse stuff out of rfc-index.xml in the same directory.
>>> Yes, Julian, there is a doi field.
>>
>> Which makes something that should be easy hard.
> 
> I'm sorry, but this is getting ridiculous.
> 
> Let's say I have a a document with a reference RFC7511 and run it
> through xml2rfc.  Somehow, it will turn that reference into strings
> like "Scenic Routing for IPv6" and "April 1, 2015".  Where do those
> strings come from?
> 
> Wherever they come from, that's where the DOIs come from because
> they're all stored in the same place.  Looking up DOIs is not
> negotiable -- the rules about DOIs are fixed, and not only for the
> IETF.  Please just fix the code.  It's hard to believe that looking up
> one more field from the place where you look up a dozen already would
> be hard.
> ...

I'm not looking them up at all. I maintain an XML2RFC processor which is 
capable of

a) inserting DOIs when they are missing, and
b) checking RFC DOIs when they are present.

Neither should require an access to an external database.

Best regards, Julian