AsciiDoc feature support in Metanorma-IETF

These AsciiDoc features are not supported in one or both RFC output formats:

AsciiDoc feature RFC XML v2 RFC XML v3

Quote

Rendered as normal paragraph

Supported

Quote: Non-URL Citations

Ignored

Ignored

Verse

Rendered as normal paragraph

Rendered as Quote

Sidebar

Rendered as normal paragraph

Supported

Index Term: Tertiary

Ignored

Ignored

List: Ordered List numbering decimal, lowergreek

Treated as arabic

Treated as arabic

Callouts

Ignored

Ignored

Adminitions: formatting

Ignored

Supported

Formatting: Floating Title

Rendered as strong paragraph

Rendered as strong paragraph

Formatting: Page Break

Ignored

Ignored

Formatting: Horizontal Rule

Ignored

Ignored

Formatting: Line breaks

Supported

Only supported within table cells

Media: Audio

Ignored

Ignored

Media: Video

Ignored

Ignored

Media: Inline images

Ignored

Ignored

Macro: Keyboard shortcuts

Ignored

Ignored

Macro: Menu selections

Ignored

Ignored

Macro: UI buttons

Ignored

Ignored

Table: Distinction between table body and table footer

No

Supported

Table: Multiple table header rows

No

Supported

Table: Table borders: grid = rows

Rendered as headers

Ignored

Table: Table borders: grid = cols|none

Supported

Ignored

Table: Table borders: frame

Ignored

Ignored

Table: Table cells: rowspan

Ignored

Supported

Table: Table cells: colspan

Ignored

Supported

Table: Table cells: Asciidoctor formatting (blocks within cells)

Ignored

Supported

Table: Table columns: width

Supported

Ignored

The document model of AsciiDoc and RFC XML are different. In particular,

  • AsciiDoc and RFC XML differ in where they allow anchors to be placed: AsciiDoc does not allow anchors within tables and lists, and RFC XML v3 does not permit anchors for the note or abstract elements, while RFC XML v2 uses anchors for much fewer block elements (e.g. artwork, list.)

  • AsciiDoc has a more restrictive block model: it regards elements such as admonitions, lists, and tables as blocks, and does not allow them to be nested within paragraphs.

As a result, it may be necessary to post-edit the RFC XML output if the block model produced does not reflect the intended structure accurately.