[rfc-i] DOIs redux

lars at netapp.com (Eggert, Lars) Fri, 26 August 2016 08:54 UTC

From: lars at netapp.com (Eggert, Lars)
Date: Fri, 26 Aug 2016 08:54:06 +0000
Subject: [rfc-i] DOIs redux
In-Reply-To: <20160826015209.40064.qmail@ary.lan>
References: <20160826015209.40064.qmail@ary.lan>
Message-ID: <BA9E304D-0431-42DF-8206-6BD8459B6594@netapp.com>

Hi,

On 2016-08-26, at 3:52, John Levine <johnl at taugh.com> wrote:
> I suspect it'd be more effective to do it the other way, put a DOI in
> the reference section, it can pull the requisite info out of the
> underlying database.

agree with John, hence my ticket to add that capability to xml2rfc: https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/326

The desire to have this functionality came when draft-irtf-icnrg-evaluation-methodology was processed by the RFC Editor, which contains 90+ references where the majority have DOIs. Sure, we can ask the authors to do the work here and correctly cite them, but without any tool support, that's quite a task. A proposition that lets authors simply cite-by-DOI is much more convincing, IMO. (And the RFC Editor still needs to check all references w/o DOIs, so we do want to make it easy for authors to add them, to reduce that load on the RFC Editor.)

Lars

PS: A quick grep through the RFCs finds 352 that contain SIGCOMM, 153 that contain INFOCOM and 566 that contain ACM, so there are quite a few.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20160826/762b2b88/attachment.asc>