[rfc-i] DOIs redux

I recently had an RFC that referenced several journal articles, and I
generated the references manually, including the DOIs. In this case it was
no great burden, but I can see for the future that it would be nice to only
have to supply the DOIs and have the rest of the reference generated
automatically.

Cheers,
Andy

On Fri, Aug 26, 2016 at 4:54 AM, Eggert, Lars <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.
>
>
>
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20160826/232aea80/attachment.html>