julian.reschke at gmx.de
Sun Feb 28 09:35:13 PST 2016
"A plain-text output for RFCs will continue to be required for the
foreseeable future. The process of converting XML2RFC version 2 (xml2rfc
v2) into text documents is well understood [I-D.iab-xml2rfcv2]. ..."
Should cite RFC 7749.
"Where practical, the original guidance for the structure of a
plain-text RFC has been kept, such as with line lengths, lines per page,
etc. [INS2AUTH] Other publication formats, such as HTML and PDF, will
include additional features that will not be present in the plain text
(e.g., paragraph numbering, typographical emphasis."
"Artwork is defined as anything marked by the XML >artwork< element (see
Section 2.5 of "The 'XML2RFC' version 3 Vocabulary" [I-D.iab-xml2rfc].
Only the 'type=ascii-art' will be rendered within the plain-text format.
This marks figures drawn with ASCII characters."
That doesn't work. There are many other things that could be placed into
<artwork>, and those will have to continue to work in the plain text
The type list in the v3 spec is not exhaustive, but even on that list I
see "call-flow" and "hex-dump" which will have to continue to work.
"... In particular, the formatter will use the "submissionType",
"seriesInfo", "author", "address", "title", "reference",
"referencegroup", and "references" to build the front and back matter of
This list is confusing. Why is front and back matter called out here?
Best regards, Julian
More information about the rfc-interest