Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

Henrik Levkowetz <henrik@levkowetz.com> Tue, 30 May 2017 01:15 UTC

Return-Path: <henrik@levkowetz.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 6685A129B39 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 18:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 DW_owfiPEfOL for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 18:15:19 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EF0D12717E for <xml2rfc@ietf.org>; Mon, 29 May 2017 18:15:19 -0700 (PDT)
Received: from h-43-30.a357.priv.bahnhof.se ([79.136.43.30]:61110 helo=[192.168.1.120]) by durif.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1dFVkk-0005MW-Qv; Mon, 29 May 2017 18:15:19 -0700
To: John Levine <johnl@taugh.com>, xml2rfc@ietf.org
References: <20170530003331.61349.qmail@ary.lan>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <592CC79E.8080804@levkowetz.com>
Date: Tue, 30 May 2017 03:15:10 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20170530003331.61349.qmail@ary.lan>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="4aU99h1xkOhWFc0cqM5LCUKsUhxLR4mqJ"
X-SA-Exim-Connect-IP: 79.136.43.30
X-SA-Exim-Rcpt-To: xml2rfc@ietf.org, johnl@taugh.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on durif.tools.ietf.org)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/WssoVV3fsL7dYRyjneLOgSAscc4>
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: Tue, 30 May 2017 01:15:20 -0000

Hi John,

On 2017-05-30 02:33, John Levine wrote:
> In article <592CA7B2.1070506@levkowetz.com> you write:
>>So you are saying that even if the RFC-Editor wished to define and publish
>>an algorithmic mapping between RFC numbers and DOI identifiers, they would
>>not be permitted to do so?
> 
> Not unless they could persuade the IAB to change RFC 7669.  Since that would
> be a bad idea, I doubt they would do so.
> 
> What is the problem with looking up DOIs the same way we look up the
> title, abstract, and umpteen other chunks of text in a reference?
> Everyone else in the world does it.  Why are we so bleeping special?

In general, there's no problem in that.  There _is_ a problem in not even being
able to talk about when that might or might not be feasible, and how to handle
such a situation.  There is also a problem that there does not seem to be an
authoritative URL for such lookups.

May I point out that even when you quoted 7669, the quote did not show an easy
way to look up the correct DOI for a given RFC number?  If there's no clearly
publicised resource which lets you programmatically look up the DOI for each or
all RFCs, permitting authoritative information and easy local caching, there's
no wonder if toolmakers starts to think in terms of algorithmic derivation of
the DOIs for RFCs.

I know a few places I could go to get DOI information for RFCs, but should the
knowledge I have about URLs in this space be required?  And how authoritative
are the various resources I might think of?

Personally, I'm going to use my knowledge here to correct the datatracker's
bibtex record, but that doesn't resolve the general issue above.


	Henrik