[rfc-i] DOIs redux

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

From: lars at netapp.com (Eggert, Lars)
Date: Fri, 26 Aug 2016 13:40:02 +0000
Subject: [rfc-i] DOIs redux
In-Reply-To: <C516CE6A-94B0-4DED-BC88-7B119A6DFC82@att.com>
References: <20160826015209.40064.qmail@ary.lan> <BA9E304D-0431-42DF-8206-6BD8459B6594@netapp.com> <C516CE6A-94B0-4DED-BC88-7B119A6DFC82@att.com>
Message-ID: <E1FE28FC-95A4-4090-A7A6-A3CB2F6CEA78@netapp.com>

Hi,

On 2016-08-26, at 15:32, HANSEN, TONY L <tony at att.com> wrote:
> 
> 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).

that'd work, too.

Lars
-------------- 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/cfecd2ef/attachment.asc>