Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

"John R Levine" <johnl@taugh.com> Mon, 29 May 2017 22:26 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 28314124281 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 15:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=It9I1wcQ; dkim=pass (1536-bit key) header.d=taugh.com header.b=PV0CzkWa
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 4TUeqRDXoTJr for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 15:26:40 -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 95581120046 for <xml2rfc@ietf.org>; Mon, 29 May 2017 15:26:40 -0700 (PDT)
Received: (qmail 51082 invoked from network); 29 May 2017 22:26:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=c788.592ca01f.k1705; bh=4xScW0BAo/js0LBZhwtity9Z1AoZ8sPBSCU19G7YYpE=; b=It9I1wcQiqtY4EFRKl+431M8jGTbHAFAGGE0PDI2OGdNwbFI/17ztV5NHvF/jwVyggFugBm8Gr8vB5vQxD0gaOlA8dcw16J8BVhBdnauW+mpcFyMf1BHbzpCO/IXSuIL6K9TCXhrdOaR9WHDdpmC40T+GTCPsP633duRm75f8P7jTS4QRpAneNI0EAQ+T8QvRQVl4zyU8/dQnpm0NNxThiXtJcJLIKL674QEU/7JX4+p9N0YtxtiUbOyLZB9Z2jk
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=c788.592ca01f.k1705; bh=4xScW0BAo/js0LBZhwtity9Z1AoZ8sPBSCU19G7YYpE=; b=PV0CzkWankWxTYmrZaJFcMtwBIcucPlIRLo9qM/0GdCRGELcsjCVq+n57Zo27abL5be+GntEeE6o4Ymz530IBez6SKIUJAe0ooVYUZZtUXj8KTuTcDOjY6oTckKgCMF45bWESX7N2GKhnObVUHfuZXdE5FWdjtVgg3zvUzL5WV2Kmlrz463Uflw1ogSVWB9jRNWw8pzGLVq9zyps1rp3hvlj6Zw8jamFbag/TDwLGN+QAwvKrRXNzKorcKnqLBj8
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 29 May 2017 22:26:39 -0000
Date: Mon, 29 May 2017 18:26:39 -0400
Message-ID: <alpine.OSX.2.21.1705291809080.51625@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Cc: xml2rfc@ietf.org
In-Reply-To: <592C9B8F.2050504@levkowetz.com>
References: <20170526165214.45384.qmail@ary.lan> <592C9B8F.2050504@levkowetz.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ZwWZCn3nHlxBFnBOE4XHGgHalGM>
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 22:26:42 -0000

> Whatever was used, once you wrote the code, wouldn't it make sense to
> publish where/how lookups should happen?  Has this been done?

Of course.  It's in RFC 7669.

> And no matter how opaque the DOI series identifiers are in general, there's
> still nothing that prevents the RFC Editor from _having_ a defined mapping
> from RFC numbers to DOI and vice versa, if a decision is made that this
> would be helpful, right?

No.  I really, really, wish that people would stop trying to relitigate 
this settled fact.  We had the exact same argument before the IAB 
published RFC 7669 which says:

    DOIs are treated as opaque identifiers.  The DOI suffixes assigned to
    RFCs are currently based on the "doc-id" field of the RFC index in
    XML (rfc-index.xml), but the suffix of future RFCs might be based on
    something else if circumstances change.  Hence, the reliable way to
    find the DOI for an RFC is not to guess, but to look it up in the RFC
    index or on the RFC Editor website <https://www.rfc-editor.org/>.
    RFC references created from entries in the usual bibxml libraries
    will have DOIs included automatically.

Among the reasons not to change it is that RFCs can contain references to 
other kinds of documents, some of those other things also have DOIs, and 
those DOIs always have to be looked up.  I hope we agree that code that 
tried to guess some DOIs while looking up others would be fragile and 
likely to break in obscure ways.

As far as I can tell all of the code around the IETF that handles DOIs 
does it correctly except for Julian's, and by this time he could have 
fixed it with less effort than he's spent arguing that he doesn't want to.

R's,
John