[rfc-i] DOIs redux

tony at att.com (HANSEN, TONY L) Thu, 25 August 2016 20:51 UTC

From: tony at att.com (HANSEN, TONY L)
Date: Thu, 25 Aug 2016 20:51:38 +0000
Subject: [rfc-i] DOIs redux
In-Reply-To: <8537fa85-475c-ee20-a24f-26f10977980e@gmail.com>
References: <8537fa85-475c-ee20-a24f-26f10977980e@gmail.com>
Message-ID: <F3EDB3EC-902C-479B-8906-99678AC99325@att.com>

There is a portion of the DOI agreement that says we SHOULD include DOIs for other references, when possible.

RFC 7669:

       4.4.  Use of DOIs in RFCs

          The DOI agency requests that documents that are assigned DOIs in turn
          include DOIs when possible when referring to other organizations'
          documents.

It?s a self-preservation issue: the more you make them visible, the more often they get used.

I could see having a real-time bibxml conversion tool. That is, a reference to http://xml2rfc.ietf.org/public/rfc/bibxml-doi/DOI# would reach out to the appropriate place and return the bibxml-formatted reference entry for the given DOI. The tool that Carsten Borman created might be a useful start to this.

But it does require that the DOI database being referenced actually have good data that can be converted.

	Tony Hansen 

On 8/25/16, 4:06 PM, "rfc-interest on behalf of Brian E Carpenter" <rfc-interest-bounces at rfc-editor.org on behalf of brian.e.carpenter at gmail.com> wrote:

    Hi,
    
    There's a ticket open for xml2rfc that starts:
    
    >  Because RFCs now have DOI numbers, the reference sections in RFCs are now
    >  supposed to include DOIs for all references for which they have been
    >  assigned...
    
    I don't see why that follows. Has the RFC Editor actually got a policy on this?
    
    It isn't a trivial requirement to support this automatically in xml2rfc (or
    to insert manually, for that matter).