[rfc-i] DOIs redux
johnl at taugh.com (John Levine) Fri, 26 August 2016 01:52 UTC
From: johnl at taugh.com (John Levine)
Date: 26 Aug 2016 01:52:09 -0000
Subject: [rfc-i] DOIs redux
In-Reply-To: <dba655c3-d1fc-3220-ea23-e7474b05ae7b@gmail.com>
Message-ID: <20160826015209.40064.qmail@ary.lan>
>So, I think the instructions to authors need to state this. I have a lot >more faith in the authors' already knowing the DOI for a reference than I >have in an automated lookup. Certainly, when I look for a reference using >almost any of the standard tools, the DOI almost always shows up. But there's >then a human in the loop to validate the result. I suspect that just sticking >this on a wish list for automation in xml2rfc masks a significant amount of work. 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. As others have noted, this is not very hard to do, an http request to retrieve the data and some munging to turn it from their flavor of XML into ours. In the spot checking I've done, the DOI data for the kinds of articles we're likely to cite, such as ones published by the ACM and IEEE, is quite good. R's, John
- [rfc-i] DOIs redux Brian E Carpenter
- [rfc-i] DOIs redux HANSEN, TONY L
- [rfc-i] DOIs redux Brian E Carpenter
- [rfc-i] DOIs redux Heather Flanagan RFC Series Editor
- [rfc-i] DOIs redux Brian E Carpenter
- [rfc-i] DOIs redux Martin J. Dürst
- [rfc-i] DOIs redux Brian E Carpenter
- [rfc-i] DOIs redux John Levine
- [rfc-i] DOIs redux Paul Kyzivat
- [rfc-i] DOIs redux Eggert, Lars
- [rfc-i] DOIs redux HANSEN, TONY L
- [rfc-i] DOIs redux Eggert, Lars
- [rfc-i] DOIs redux Andrew G. Malis
- [rfc-i] DOIs redux Brian E Carpenter