Re: [xml2rfc] RFC Bibtex format doi numbering incorrect

worley@ariadne.com (Dale R. Worley) Tue, 30 May 2017 14:13 UTC

Return-Path: <worley@alum.mit.edu>
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 5DE9E128D44 for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 07:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.034
X-Spam-Level:
X-Spam-Status: No, score=-0.034 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 8HOkPiw53gzD for <xml2rfc@ietfa.amsl.com>; Tue, 30 May 2017 07:13:35 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E36A11288B8 for <xml2rfc@ietf.org>; Tue, 30 May 2017 07:13:34 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-09v.sys.comcast.net with SMTP id Fhpudw2XAQe9cFhttda4BR; Tue, 30 May 2017 14:13:33 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-10v.sys.comcast.net with SMTP id FhtsdW0moX2FjFhttd5nIY; Tue, 30 May 2017 14:13:33 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v4UEDV7s003083 for <xml2rfc@ietf.org>; Tue, 30 May 2017 10:13:31 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v4UEDU5S003080; Tue, 30 May 2017 10:13:30 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: xml2rfc@ietf.org
In-Reply-To: <40342552-00c2-ece5-a773-8c7646ebb715@gmx.de> (julian.reschke@gmx.de)
Sender: worley@ariadne.com
Date: Tue, 30 May 2017 10:13:30 -0400
Message-ID: <87zidu301h.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfK1li0y7/7lnMbTeqgjuJf7bw/2DJk/OMVvZ/XRYPTT+YS/mWnHdXr4AkrAhA+YNfJnuKrj4ChmX2hieuqstz7sHkvILbPT43/X91kZzFhBec9cqVeE3 GySxQ40o5CFdFUxA1BJO5emJV5AHvbSmolNU33eg9m6O5TEBSz1bL0yw
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/BVqEsd9dIjEHl-XmInU-e743JQ0>
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 14:13:36 -0000

Julian Reschke <julian.reschke@gmx.de> writes:
> I still don't get why we just define the mapping precisely.

Let us at least state this position correctly.  The word is not
"precisely", since any well-defined mapping between RFCs and DOIs is
"precise", and the mapping defined in rfc-index.txt is well-defined.
The word you want is "algorithmically", and in particular in the sense
that one can predict the DOI that will be assigned to an RFC that does
not yet exist, based on its number.

Henrik Levkowetz <henrik@levkowetz.com> writes:
> 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?

The Editor can publish whatever documentation they want to of their
current processes.  What they can't do is commit themselves to hold to
any particular algorithm for the indefinite future; what they say is not
a contract with the user.  Only the IAB can do that, and it hasn't.

"John R Levine" <johnl@taugh.com> writes:
> The way you validate a DOI is easy: you dereference it.  If the DOI is 
> 10.1234/something, you look up https://dx.doi.org/10.1234/something.  If 
> it's valid, you'll get something back, if it isn't, you won't.  If your 
> query accepts accept application/rdf+xml you will get back the document's 
> bibliographic info in XML.

Heh...  Liking to nit-pick requirement statements, I would revise this
to "you dereference it and verify that the bibliographic information you
obtain matches that of the document you think the DOI is for".

Dale