Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Julian Reschke <julian.reschke@gmx.de> Sun, 28 May 2017 21:27 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 D9C32120046 for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 14:27:47 -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 tE5cvHsp_D0q for <xml2rfc@ietfa.amsl.com>; Sun, 28 May 2017 14:27:46 -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 3A19012948E for <xml2rfc@ietf.org>; Sun, 28 May 2017 14:27:45 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.99.52]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MVui8-1dQ58q0S8O-00X5FW; Sun, 28 May 2017 23:27:28 +0200
To: John R Levine <johnl@taugh.com>
Cc: xml2rfc@ietf.org
References: <20170526165214.45384.qmail@ary.lan> <c08be30c-253a-47d6-a9f9-c89741073a8c@gmx.de> <alpine.OSX.2.21.1705281035220.45932@ary.qy>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <e5ce1a28-c6b0-9b7c-5894-2b9567c70b08@gmx.de>
Date: Sun, 28 May 2017 23:27:28 +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.1705281035220.45932@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:2p2li399ffcMP1HjnQUB8DfqLNRsD6iqtHEJoRTcZ+wnAomekTz mDxv+OK92oX5vsxNs6JN61EXuhlfKDmaL5SrI6pLrteLM11JOec6fNw/wKDcbFTGH2THToW zeBlKHSP4m2pyGwiD42uW2UKXAVdfIAtbmYcKI/6Vg8YNtQKQbx0xl/7tBc6ID4RPFU4Eil 4yN6G/ih5Ijm5kl3RB4Fw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:H1hWUOckdqs=:R89s5RxtifnWT57iTFmd9s OA3JUbyQ6IRUp0WsaeYeYx9WmSOSE4oIKRMPb2aFtY6dIIeEtV38mYFAamtxAg7qRydxPaUJy 15EoveZ3dG3a/vYt6RfYofLqalm4AAGCWAjO3pfRTnqgOXtzLqqRpQoiRTkPWo2pDQNalsv7L LcDNF9FnGA2gGTiOSjGMzitukS78s7N/ojyFD4bEIUirz8oKWFJ0CrryhnLAcrdq8IOjDFPXf qrXwIwRGZ+dhLh3yHXRLWm7j1yRQqN94ZvdYg8NeJTyncaKL9lv17umnfS1c/2xeGa5cuU9xJ Y37JB7SIIA4yFrQpdCzR5/JUesysnot+mxGMATO1WqaRYcIaFJpueyEi1WfQKZqhvm6zNLWvg FaTjkyw6dbS/xbx+gftKrQlJA1xkNxe9lUAbzh9wWwPjP0MYximwuXl60IyUjKdmP4kTR4j1m UHTbL73epIPTlKml3gkA5sggU6FRmq6sOp6EKbF28EINuGZn3Fhh/SItYbQkXKjUXRA4e+qw1 zKf0uRyj2TjD3gbiKfdNkGZElYt8CbZ3jy5vjp759bOaZmH0rKNdHpdgnpmxvC62mFtzagaGp zxUbQ0ee3X74Se0E54lutex9uPTRB2lLdJM0pnTRLYqb99qytQ6jSCoc+1NYUmceAdYhnJpIG I4o+ugN6+4tG6kf0g6VcbRBq68OIA6G/17KOlg30IIU0DRJ94zP2oLAr9IAjsJrbRO8muOjeM nbcPW6cYevI+hTd6bFbSQZVz8WWnlDwiOyXxJ/gJZDxN+batlGsm85bATDk1S3rwGuM7gzSxZ 4NP+D6I
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/_X7TEnNT2q5xhCtnVydYGXq4eAc>
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:27:48 -0000

On 2017-05-28 17:00, John R Levine wrote:
>>>  DOIs are opaque identifiers.  The DOI of any RFC is whatever is in the
>>>  DOI field of the RFC Editor's database.  Any code that attempts to
>>>  guess the DOI from the RFC number is broken.
>>
>> Wow. Really? Why not just define the mapping precisely?
> 
> Because we are not the only people in the world who use DOIs, and the
> rule for everyone, not just us, is that they are opaque.  Our
> references are supposed to show the DOI on every document that has
> one, which includes anything published by the IEEE or ACM.  Where do
> you get those?  If you don't, there's another bug report.

What does this have to do with the mapping of RFC numbers to DOIs? I 
don't get it.

>>>  In response to the question of what DOIs of RFCs past RFC9999 will be,
>>>  it doesn't matter.  If your code tries to guess, it is still broken.
>>>  The DOI is whatever the DOI is.  Don't guess, look it up.
>>
>> Where? I thought you just said the database is for internal use only?
> 
> Huh.  This is just a wild guess, but how about looking up the DOI in the 
> same place you get the title, authors, date and abstract.  Or are you 
> saying you compute them from the RFC number, too?

Yes, of course I do.

Best regards, Julian