[rfc-i] XML citation library for RFCs (bibxml)

Tony Hansen tony at att.com
Mon Jul 13 03:32:00 PDT 2015

On 7/12/15 3:46 AM, Eliot Lear wrote:
> Hi Alice,
> This looks like a good idea, and I have no objection to the change. 
> Once suggestion I do have is to release a version of xml2rfc very
> quickly that warns those who keep their own copies of the XML2RFC
> database to update their copies.

For what?

> One related question: can anyone at the RPC comment on how you plan to
> maintain the non-IETF files?  I'm hoping the answer is simply that
> you'll import information that individual authors provide.  For
> instance, I'm currently writing a draft that makes use of IEEE standards
> that you currently don't have.

That's not currently in any plans. The other bibxml are not moving
anywhere else.

For non-RFC and non-Internet-Draft bibxml issues, you can always send an
email to citations at rfc-editor.org. Alice Russo and I both monitor that
mailing list.

    Tony Hansen

> Eliot
> On 7/11/15 1:50 AM, Alice Russo wrote:
>> FYI, the RFC Editor maintains a version of the XML citation library for RFCs ("bibxml") that has been updated to create text output that matches the RFC Style Guide, i.e., each reference includes the URL for the RFC info page and the DOI. (In addition, it includes more accurate data for specific RFCs regarding seriesInfo, role, and when an organization is an author.) It is available via rsync (see https://www.rfc-editor.org/rsync-help.html).
>> Replacing the existing bibxml (available from xml2rfc.ietf.org) with the one from rfc-editor.org is under consideration. For example:
>> (A) http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml
>> (B) http://www.rfc-editor.org/refs/bibxml/reference.RFC.5234.xml
>> One change is removing the format elements. Example of what is removed from (A):
>> <format type="TXT" octets="26359" target="http://www.rfc-editor.org/rfc/rfc5234.txt"/>
>> Rationale: It makes the info page (the target) the entry point. When using xml2rfc v2, the presence of the format element does not have an effect on the text or HTML output.
>> With an eye toward the future, for xml2rfc v3, <format> has been deprecated as described in draft-hoffman-xml2rfc:
>>  o  Deprecate <format> because it is not useful and has caused
>>     surprise for authors in the past.  If the goal is to provide a
>>     single URI (Uniform Resource Identifier) for a reference, use the
>>     "target" attribute on <reference> instead. 
>> Please let us know if you object to this change.
>> Thank you.
>> Alice Russo
>> RFC Production Center
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest at rfc-editor.org
>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
> _______________________________________________
> 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/20150713/ecf752c8/attachment.html>

More information about the rfc-interest mailing list