IETF Logo Mail Archive

Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Julian Reschke <julian.reschke@gmx.de> Wed, 31 May 2017 06:01 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 D6686129B5E for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 23:01:57 -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 YiFYRwigN-5V for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 23:01:56 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 C4CE71294EE for <xml2rfc@ietf.org>; Tue, 30 May 2017 23:01:55 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.66.246]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MZxch-1dTtLa1h6t-00Lk6f; Wed, 31 May 2017 08:01:21 +0200
To: John R Levine <johnl@taugh.com>, Henrik Levkowetz <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
References: <20170530211633.65372.qmail@ary.lan> <592E00D4.6070206@levkowetz.com> <alpine.OSX.2.21.1705301949420.56985@ary.qy>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <ce470bca-4611-8503-9f70-0e3760299c57@gmx.de>
Date: Wed, 31 May 2017 08:01:20 +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.1705301949420.56985@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Ws+VkdX0sSziJOUHSBF8ZWyaaGKKEXYlpumZZq9GIBEiRfPYOSh z8KMQ92hgUTZxPbVSc/E0GeHufUdSWX7MYKxpRYsYsrpR0To/FA8jzsVqiNHB6pNeG8DcEd naINJRbf/8Q+dOXNz4lmIt3rrVfhXi+yWO6jcc3ZRwo5WS53jPZeJR7msdZ9wwSM9y9Hch5 anTJnNePkAESjBGIsLSwQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:mKuF0KICfe4=:Pb8bEmU1jxr9XpN8AOAbRq ReviIfriMabooSQN98xEq9aC9ci4wzpCcWFsRuz/+GNCeTofhP0MWagZq61Vc8uxoH1FA859s eZttbgfszNe/C3levHtF0KJQPSgDBWBVTX9IDNkUGagDxuOCsV9/LH5W58Hi15ZPkLX3S2+ez mV2OONrjJjqDx9VUm4mxtAEt8+b3cWX7xh9qrBLFUxsIRcngpOQAkLj+l2NaUcfZ0PJxOYfYF d4fOWIv6CYdE4dvFkJM1ukvlpUOXlZwGO0zuYhtXHpS8SokGvzcmgyK0lqHV/IuIDtnD8qeYy 5dkWfQN6eBWLrdCX7zccclMMQwVevc6DjxQjTxiwhZIqT4e/30ZycYahRcgRG4JSjV7YczKG4 BIc7iTKeOcOauKlj5BF2Z4Wa+o9QoG3T22a7A30EK8DMcVEJCx5SbDqRHvpZH/0Rpj6BvJTRi /b9ZYOjpbP5GED2oFpPwpT4VJ+sFnFCii+ujSoz2eoHceCsgWHZkGrcZF6tMwFypnBD5ow5/+ lkS3p2MdAnrsMZa5PgQuzy2v95+bG+awhBwUSoEc0G9PeWtHlbHcFEq0Kj5hhsH1YUQj1nCPC iyOSrXiFYiua+gJJTnTGUpxaUuYl7+T27QnMwgO0OYaC6cgTA2JtlWSFB2gZ208dmgVKCPqBb ZLJMKsvLa7bMCTZsAkKmi+pBPybQfbVZuyG9re6vQpmZHsk5t0zgzvvSoHgsov7GdrlrXGOCj mSj7UzML6HjzK/76vzU+8kxtXGcWubj/Y8qoDbCIRwMxcz0BO8fBWDqYypaKn6/PsO0UucBde zEmR5i1
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/_E8n8ZskBkxHlHVLgz7JuSo9BFA>
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: Wed, 31 May 2017 06:01:58 -0000

On 2017-05-31 01:50, John R Levine wrote:
>> However, please note that this is not a lookup resource which encourages
>> on-the-fly lookups and caching.  It requires you to download the whole
>> corpus information every time you need an update ...
> 
> Sure, but I expect it's obvious how you'd cache a copy locally for 
> lookups.  Downloading it once a day would be plenty.
> ...

So if it's obvious, why do we have published RFCs with broken DOIs? This 
is something that could have been avoided if the formatter had done a 
sanity check.

Best regards, Julian

v2.23.0 | Report a Bug | By Email