[rfc-i] References for non-standards

Paul Hoffman paul.hoffman at vpnc.org
Wed Feb 12 10:18:02 PST 2014


On Feb 12, 2014, at 9:55 AM, Yaron Sheffer <yaronf.ietf at gmail.com> wrote:

> Hi Julian,
> 
> Sorry, I used "XMLbib" instead of "bibxml" (a.k.a. the <reference> format). The Github link has a "tests" directory with a number of test cases, which the Python script converts into <reference> entries. Different bibtex databases are not very consistent, so the results are quite basic - not all bibtex fields appear in the output.
> 
> If you could create a usable conversion service from it, that would be grand.
> 
> And then, what kind of syntax should I use to include one or two such bibtex entries from my draft? Can I do something like:
> 
> <reference src="http://julian.com/convert2ref/url=..."/>

That would not work with the v2 vocabulary because it requires a <front> element, and <front> requires <title>, one or more <author>s, and a <date>. (See <http://tools.ietf.org/html/draft-reschke-xml2rfc-04#section-2.30> and <http://tools.ietf.org/html/draft-reschke-xml2rfc-04#section-2.19>.)

In the current proposal for the v3 format, that would also not be allowed. We could add that, but I would prefer that we don't, and instead require that a full reference like we have now be included in the RFC.

--Paul Hoffman


More information about the rfc-interest mailing list