Re: [xml2rfc] RFC Bibtex format doi numbering incorrect
Matthew Kerwin <matthew@kerwin.net.au> Mon, 29 May 2017 23:27 UTC
Return-Path: <phluid61@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 B1210129492 for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 16:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level:
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 97l_lGEjwFrc for <xml2rfc@ietfa.amsl.com>; Mon, 29 May 2017 16:27:41 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 0299B129490 for <xml2rfc@ietf.org>; Mon, 29 May 2017 16:27:41 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id p24so47693060ioi.0 for <xml2rfc@ietf.org>; Mon, 29 May 2017 16:27:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=UZWoSqWpLAZvkLEZTy4hkDcMEFzhjykS3RZHggSEt2A=; b=ZubiFFmHWIJAwYeHWUk83iZhGHrwzQ6tCbPblPZJ4CvVI+e3j1lS8VSQvbuukOM3HF BK3R0URsBWdVCuoG098GANXfIgHXV1GGD+dvr2oouKPNE5VVYZFotgWn8yMdtlBOwxIl SUxboppTlKfaK2QEy7JiRBlq9rwoirFqH7w7SZFcFgQ2TT/nFgBDMIqe+4jZA5YEkb2R ORJadR11+MF0+O8+PEnX/cTDeLVQqq4/Pk1gcwMK2B9pnffhDU0BJO2J2rvZ5rMkIctQ UYG3IXLP99dz50E80YirdT2b29aMeBmaf70PToZCcvHz+A9AYLAmxLZjnOX5Rz4/faDH iKlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=UZWoSqWpLAZvkLEZTy4hkDcMEFzhjykS3RZHggSEt2A=; b=VNam/zQaBtUWimOEy+YQ8XgL8e91nCC3q4T8GLadF+ucGMLC85rJmgQXzWk48Gb5i3 fDOBnEl6nHPGqh5hcsuYs/ilwl2DWrrtatv3XV8BvnWvpdI0BxMN7reewCDgxFGmsQUO UUTVDuOYYUWCtMSPdcnihp+uozyzmt18w1aPSD97upqSbVxe2kuN+MkoKDuCwDfcq7fF VSCQI0F9Vfj5oQPQq7ADLS5+X9eb1N+icQ7KZ8KxBFtYgqN7dqLEO9QNvhWbqAdFaND/ /V39CFRQvtiq/JhncxX/Wxy7XFDvolzWc6VkmGrEO7KfgaLW+GVJrgm64fDdGuNLC1Gk VpFQ==
X-Gm-Message-State: AODbwcDK2bkI5iveWQ9e2GrP8GljS49V6LuaPrye1jNhmZQE5fIFiLgf ha9NVcI9BG94z6JmCTda4SX40DGzPAt02n8=
X-Received: by 10.107.147.134 with SMTP id v128mr14633370iod.70.1496100460231; Mon, 29 May 2017 16:27:40 -0700 (PDT)
MIME-Version: 1.0
Sender: phluid61@gmail.com
Received: by 10.107.38.209 with HTTP; Mon, 29 May 2017 16:27:39 -0700 (PDT)
In-Reply-To: <592CA7B2.1070506@levkowetz.com>
References: <20170526165214.45384.qmail@ary.lan> <592C9B8F.2050504@levkowetz.com> <alpine.OSX.2.21.1705291809080.51625@ary.qy> <592CA7B2.1070506@levkowetz.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Tue, 30 May 2017 09:27:39 +1000
X-Google-Sender-Auth: XylluZxXE9llDnlfDhPrtJjKYGw
Message-ID: <CACweHNCJqUg3ejUsH2pwBWP36tD+e7mgrOoHo-q9GO7c5+oKjg@mail.gmail.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Cc: John R Levine <johnl@taugh.com>, xml2rfc@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c055d187b01fd0550b2086a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/vGvWU2WMoK_3PgLqtJ7QCMVnDC8>
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 23:27:43 -0000
On 30 May 2017 at 08:58, Henrik Levkowetz <henrik@levkowetz.com> wrote: > Hi John, > > On 2017-05-30 00:26, John R Levine wrote: > >> 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: > > 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? > > This whole discussion is rather absurd, and I'm a bit disappointed to see it happening. (Not you specifically, Henrik, I'm just replying to the last message in the thread.) The original bug report is legitimate, and should be corrected. I.e. the tool that generated this document: https://datatracker.ietf.org/doc/rfc826/bibtex/ put the wrong value in the 'doi' field. Presumably, that tool attempted to guess the value, rather than fetching it from a reliable source (contrary to RFC 7669, questions of which was published first notwithstanding), and guessed wrong. Speaking as a general programmery type person, but not someone familiar with the tools and resources in question, I would assume that the tool should be able to retrieve the value for 'doi' the same way it was able to retrieve the value for 'title', from the same or a similar source, and if it were changed to do so the bug would be fixed. Please correct me if that assumption is wrong. Now, because I enjoy a good rabbit hole as much as the next person: Henrik, the RFC Editor can define and publish such an algorithmic mapping, of course. If the goal is just to document the way in which they generate DOIs, it's potentially interesting, but not really useful to anyone outside the editors. If, by publishing it, the RFC Editor wishes to make it possible for consumers to correctly "guess" a DOI, then the document would have to update RFC 7669 (with all the process and consensus that that would involve.) Cheers -- Matthew Kerwin http://matthew.kerwin.net.au/
- Re: [xml2rfc] [django-project] RFC Bibtex format … Robert Sparks
- Re: [xml2rfc] [django-project] RFC Bibtex format … Julian Reschke
- Re: [xml2rfc] [django-project] RFC Bibtex format … Robert Sparks
- Re: [xml2rfc] [django-project] RFC Bibtex format … William Atwood
- Re: [xml2rfc] [django-project] RFC Bibtex format … Brian E Carpenter
- Re: [xml2rfc] [django-project] RFC Bibtex format … Stefan Viergutz
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Dale R. Worley
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John R Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John R Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Brian E Carpenter
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John R Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Henrik Levkowetz
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John R Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Henrik Levkowetz
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Matthew Kerwin
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John C Klensin
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Henrik Levkowetz
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Henrik Levkowetz
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John R Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Dale R. Worley
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… HANSEN, TONY L
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… HANSEN, TONY L
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Henrik Levkowetz
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John R Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John R Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… HANSEN, TONY L
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… John Levine
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Sandy Ginoza
- Re: [xml2rfc] RFC Bibtex format doi numbering inc… Julian Reschke