[rfc-i] DOIs redux

[tony at att.com (HANSEN, TONY L)]

Thank you Lars and John. I agree fully that making it easy to generate these references is a great idea. However, I think a better method than modifying xml2rfc is to create a bibxml tool to generate the references.

Doing a dig on http://dx.doi.org/${doi} with the header "Accept: application/citeproc+json" appears to generate a nicely formatted JSON reference object. From reading what Carsten Borman has written elsewhere, the data may not be as regular as we want, but it's a good start.

My thoughts are to have http://xml2rfc.ietf.org/public/rfc/bibxml-doi/reference-DOI.${doi}.xml do the dig and conversion (keeping a local cache so multiple requests don't overwhelm dx.doi.org).

	Tony

On 8/26/16, 4:54 AM, "rfc-interest on behalf of Eggert, Lars" <rfc-interest-bounces at rfc-editor.org on behalf of lars at netapp.com> wrote:

    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.