IETF Logo Mail Archive

Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

"John Levine" <johnl@taugh.com> Sun, 28 May 2017 21:49 UTC

Return-Path: <johnl@taugh.com>
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 17106129494 for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 14:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 pD5JjynSfEwg for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 14:49:52 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F48112941C for <xml2rfc@ietf.org>; Sun, 28 May 2017 14:49:52 -0700 (PDT)
Received: (qmail 9696 invoked from network); 28 May 2017 21:49:51 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 28 May 2017 21:49:51 -0000
Date: Sun, 28 May 2017 21:49:29 -0000
Message-ID: <20170528214929.56669.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: xml2rfc@ietf.org
Cc: julian.reschke@gmx.de
In-Reply-To: <a9e981dc-d452-026a-915b-613a61863809@gmx.de>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/40z02Pxe0Ug74WdTuysvnKHLgJE>
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: Sun, 28 May 2017 21:49:54 -0000

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.

R's,
John

v2.23.0 | Report a Bug | By Email