Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 29 May 2017 20:17 UTC

Return-Path: <brian.e.carpenter@gmail.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 BB5541292F4 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 13:17:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LGHyX7nzfoCR for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 13:17:57 -0700 (PDT)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 350C51205D3 for <xml2rfc@ietf.org>; Mon, 29 May 2017 13:17:57 -0700 (PDT)
Received: by mail-pf0-x244.google.com with SMTP id u26so13253079pfd.2 for <xml2rfc@ietf.org>; Mon, 29 May 2017 13:17:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=NhKzHumZki76u2JC7RzXAFZpE1lWhx2hjp58VDBnwNE=; b=ai/kozP3I2F1zSxI+DztBwDnmKL6MEWhzrbmusy6E4uy8eMGVWIkqwzghC7vX5mMma +/D3EDutwawUVVe+/7/1VNPkYH3SBDGlRhDA54ssbJ2aqX813UxkRTz6otaTeMjBoU1U +G4gCYCRYyPylVN9NnS/d+OoUl7PI7Uz8CVFGPUj3nS+jxDYpExO1vu9JIN+NP9Y/EXt 7rI0rxAJSlI7aw654Px/iUMe/A/RZd1TgllS1B+8ZbnuULEF/SrFrxI9QsC4JFG5pAup UWb2qcGf7ep1KewbU7+qw6jyIqsUqUTK0VATATk4lKU0D9wsMALDE5x2a8wDOXGSug/Z NqPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization:cc :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=NhKzHumZki76u2JC7RzXAFZpE1lWhx2hjp58VDBnwNE=; b=f17M1S5LrdCLCDoCypiALlOc9+GLmFjzX9gWZBfCILjc2t4WAU7N4ZVj//1+cgaKkn ZYbL0x/MUAcNgfhyDVLNYed67ZgIjmvmQom6QyTp3ZbNwvkbaX3tCwR8Idpu0/s8lVXl CSeEU1TXdfJVoP/Cg5fa4I4Q1GDCboBK+dW36q6HiZnx0q5v/vDKvr67jc1rH9yW01EC ooLnVVA51cmfhept/AD39LFA/XndyKk81FFZUDUD5PX9WQI8I1zjLGQa28ACJhOg2U12 dpjFeKfJatVfe3gwi6zznU1ZtbRG6Cnn/FLJENL72xJPBBzMj48fjg6w/8xka98GkRgx tpgQ==
X-Gm-Message-State: AODbwcDDjyrT564PjKEwnahYsfSCTZQY4lTo5CIBFspjm7iIqAWaD5N3 urHII+Brqsgm2A==
X-Received: by 10.84.229.72 with SMTP id d8mr78698040pln.159.1496089076791; Mon, 29 May 2017 13:17:56 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.69.51]) by smtp.gmail.com with ESMTPSA id o89sm19336904pfj.88.2017.05.29.13.17.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 May 2017 13:17:56 -0700 (PDT)
To: Julian Reschke <julian.reschke@gmx.de>
References: <20170528214929.56669.qmail@ary.lan> <038e5bd1-726c-599d-38cf-a65b7385856b@gmx.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Cc: John Levine <johnl@taugh.com>, xml2rfc@ietf.org
Message-ID: <a92f6a44-38cf-3c5a-49c8-676596f14c5f@gmail.com>
Date: Tue, 30 May 2017 08:17:53 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <038e5bd1-726c-599d-38cf-a65b7385856b@gmx.de>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/zYtkdWIM9J2EAG6yxFuLGPtP8ig>
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 20:17:59 -0000

On 29/05/2017 17:49, Julian Reschke wrote:
> 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.

But it must, since the DOIs are arbitrary strings made up by the RFC Editor.
I don't understand your point: wherever you look up other arbitrary
strings, such as the document title, you can look up the DOI string.

I don't see why parsing <doi>10.17487/RFC0001</doi>
is any different from parsing <title>Host Software</title>

Regards
   Brian