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

Tony Hansen tony at att.com
Sat Jul 11 17:22:52 PDT 2015

The ONLY question on the table is the removal of the <format> elements
from within the <reference> element of the */bibxml entries for the
RFCs. These <reference> elements will contain targets to the RFC
meta-info page.

The other bibxml[2-5] directories will remain in place where they are on
xml2rfc.ietf.org. They will be >>unaffected<< by this change.

The plan is tomake the bibxml found at
<http://xml2rfc.ietf.org/public/rfc/bibxml> to be rsync-ed from
www.rfc-editor.org/refs/bibxml <http://www.rfc-editor.org/refs/bibxml>.
The same information would then be available from either location. (If
you want to see what this looks like, note that
www.rfc-editor.org/refs/bibxml <http://www.rfc-editor.org/refs/bibxml>
is being generated today, with the <format> elements. Also, the rsync is
running today as well, but loading today into

    Tony Hansen

On 7/11/15 2:20 AM, Carsten Bormann wrote:
> Hi Alice,
> very interesting.
> I gather this is for RFCs (bibxml) and I-Ds (bibxml3) only?
> Is this a "production" service at this point?
> Background for my question:
> kramdown-rfc2629 automatically selects a bibxml source based on the
> citation tag (as in [RFC4711]).  It would be a simple flip of a switch
> to move this over from xml2rfc.ietf.org to rfc-editor.org.
> Should I flip this switch?  When?
> One more observation:
> I notice that there are some files with (text form) BCP and STD
> references at http://www.rfc-editor.org/refs/ -- is there an intention
> to make these available in XML, too?  Right now, there is no good source
> for BCP and STD citations that can be used automatically [1].
> Grüße, Carsten
> [1] https://github.com/cabo/kramdown-rfc2629/issues/5
> 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/20150711/e271a649/attachment.html>

More information about the rfc-interest mailing list