asciidoctor-rfc 0.8.0 → 0.8.2

data/spec/examples/README.adoc

@@ -38,7 +38,10 @@ output as `eref`, and in the xml2rfc output as angle brackets.
 --
 
 == RFC XML v2
-https://www.ietf.org/archive/id/draft-hoffman-rfcexamples-04.txt
+* https://www.ietf.org/archive/id/draft-hoffman-rfcexamples-04.txt
+* https://github.com/rfc-format:
+** https://github.com/rfc-format/draft-iab-rfc-framework-bis
+** https://github.com/rfc-format/draft-iab-html-rfc-bis
 
 * `hoffmanv2.xml.orig`
 
@@ -52,11 +55,44 @@ and xml2rfc output from XML generated from our asciidoc should be noted:
 `hoffmanv2.xml.adoc`::
 +
 --
-* The source xml has set the `subcompact` document directive; the directive cannot be set
-from Asciidoc.
 * Table preambles and postambles are not supported in Asciidoc.
 --
 
+`https://github.com/rfc-format/draft-iab-html-rfc-bis.xml.adoc`::
++
+--
+* Asciidoc does not permit anchors with dots (e.g. `element.postalLine`)
+* Original uses `section@numbered="no"`; that attribute is supported by xml2rfc v2,
+but not by RFC XML v2 itself.
+* Original applies subcompact processing instruction to a single list;
+restricted processing instructions are not supported by the gem.
+
+* Note that the references in XML need to be well-formed. In the absence of closing tags,
+the gem may switch tag case to lower case, assuming it is dealing with HTML; for example
+
+````
+<abstract>
+<t>This document describes some aspects of the "prep tool" that is expected to be created when the new RFC v3 specification is deployed.</abstract>
+
+</front>
+
+<seriesInfo name='RFC' value='7998' />
+````
+
+is output as
+
+````
+<abstract>
+<t>This document describes some aspects of the "prep tool" that is expected to be created when the new RFC v3 specification is deployed.</abstract>
+
+</front>
+
+<seriesinfo name='RFC' value='7998' />
+````
+
+where the absence of a closing `t` tag results in `seriesInfo` being lowercased as an HTML tag. (!)
+--
+
 == MMark
 https://github.com/miekg/mmark/tree/master/rfc
 
@@ -108,10 +144,10 @@ and definitions (`<vspace blankLines="1"/>`).
 --
 * The MMark has specified an external reference to a specific section by giving the section
 number in text: `Section 4.2 of RFC 2460 [@!RFC2460]`, rendered as
-`Section 4.2 of RFC 2460 <xref target="RFC2460"/>`. The asciidoc takes advantage of
+`Section 4.2 of <xref target="RFC2460"/>`. The asciidoc takes advantage of
 the `relref` construction of external section references, even though `relref` is a v3
 RFC XML feature: `<<RFC2460,4.2 of>>`, which is rendered in v2 RFC XML as
-`<xref target="RFC2460">Section 4.2 of [RFC2460]</xref>`.
+`Section 4.2 of <xref target="RFC2460"/>`.
 --
 
 == Kramdown
@@ -142,7 +178,7 @@ cross-reference, which takes up one more space for the same reference text.
 since the term delimiter itself involves colons:
 `SZX: :: `
 * Note that `**` needs to be escape in Asciidoc as `\\**`, in order not to be misinterpreted
-as formatting. On occasionl, the escaping is ignored, and the exponentiation operator
+as formatting. On occasion, the escaping is ignored, and the exponentiation operator
 has had to be entered as `&#42;&#42;`.
 --
 

data/spec/examples/biblio-insert-v2.adoc

@@ -0,0 +1,29 @@
+= The Holy Hand Grenade of Antioch
+Arthur Pendragon
+:doctype: internet-draft
+:workgroup: silly
+:normative: RFC2119, AsciiDoc
+:biblio-insert: true
+:biblio-dir: refs-v2
+
+[[xyz]]
+== Hello
+Hello
+
+* a <<RFC2119,2.3 of: See internet draft subsection>>
+* b <<I-D.abarth-cake>>
+* c <<xyz,format=counter: xyzzy>>
+* d <<biblio>>
+* e <<AsciiDoc,AsciiDoctor>>
+
+
+[[biblio]]
+=== Biblio
+See biblio
+
+[bibliography]
+== Normative References
+
+[bibliography]
+== Informative References
+

data/spec/examples/biblio-insert-v3.adoc

@@ -0,0 +1,30 @@
+= The Holy Hand Grenade of Antioch
+Arthur Pendragon
+:doctype: internet-draft
+:workgroup: silly
+:normative: RFC2119, AsciiDoc
+:biblio-insert: true
+:biblio-dir: refs-v3
+
+[[xyz]]
+== Hello
+Hello
+
+* a <<RFC2119,2.3 of: See internet draft subsection>>
+* b <<I-D.abarth-cake>>
+* c <<xyz,format=counter: xyzzy>>
+* d <<biblio>>
+* e <<AsciiDoc,AsciiDoctor>>
+* f <<mathrefs>>
+
+
+[[biblio]]
+=== Biblio
+See biblio
+
+[bibliography]
+== Normative References
+
+[bibliography]
+== Informative References
+

data/spec/examples/davies-template-bare-06.adoc

@@ -21,6 +21,7 @@ Elwyn Davies <elwynd@dial.pipex.com>
 :inline-definition-lists: true
 :compact: yes
 :subcompact: no
+:rfc2629xslt: true
 
 [abstract]
 Insert an abstract: MANDATORY. This template is for creating an

data/spec/examples/draft-iab-html-rfc-bis.xml.adoc

@@ -0,0 +1,2300 @@
+= HTML Format for RFCs
+Joe Hildebrand <joe-ietf@cursive.net>; Paul Hoffman <paul.hoffman@icann.org>
+:rfc2629xslt: true
+:toc-include: yes
+:toc-depth: 4
+:sort-refs: yes
+:sym-refs: yes
+:compact: yes
+:subcompact: no
+:consensus: yes
+:ipr: trust200902
+:doctype: rfc
+:submission-type: IAB
+:name: 7992
+:status: informational
+:abbrev: HTML for RFCs
+:forename_initials: J.
+:role: editor
+:organization: Mozilla
+:forename_initials_2: P.
+:organization_2: ICANN
+:revdate: 2016-12
+:keyword: html,css,rfc
+
+In order to meet the evolving needs of the Internet community, the
+canonical format for RFCs is changing from a plain-text, ASCII-only format to an
+XML format that will, in turn, be rendered into several
+publication formats. This document defines the HTML format that will
+be rendered for an RFC or Internet-Draft.
+
+[#introduction]
+== Introduction
+
+As described in <<RFC7990>>, the RFC
+Series is changing. One of those changes includes the RFC Editor
+publishing a non-canonical HTML version of RFCs.
+
+This document describes the HTML format that will be used as one of the
+publication formats for the RFC Series. It defines a strict subset of
+HTML appropriate for RFC Series documents.  The visual layout of the
+document will be defined through a cascading style sheet (CSS)
+<<W3C.REC-CSS2-20110607>>.  The CSS will be included in the
+HTML file but will be described in <<RFC7993>>.
+
+The details (particularly any vocabularies) described in this document
+are expected to change based on experience gained in implementing the
+the new publication toolsets. Revised documents will be published
+capturing those changes as the toolsets are completed. Other implementers
+must not expect those changes to remain backwards compatible with the
+details described in this document.
+
+[#requirements-for-html]
+== Requirements for the HTML Format
+
+This section lists the design requirements used to create the HTML
+format described in this document.  These requirements build on those
+found in <<RFC6949>>. Many of these requirements are
+naturally fulfilled by using the output of the preparation tool
+<<RFC7998>>.
+
+
+* The HTML has to render correctly on a list of browser versions that
+the RFC Editor will keep up to date outside of this document.
+* The format will consist of a subset of HTML deemed to be widely
+implemented   by common browsers at the time the specification is
+created, likely to continue to be widely implemented, and unlikely to
+cause security issues.  This will maximize the chances that future HTML
+renderers (such as new web browsers) will continue to produce readable
+text from the HTML format without the format needing to be changed
+frequently.
+* These requirements are expected to change in the future to reflect the
+expectation that HTML rendering will be required for current versions of
+browsers and platforms, while ideally continuing to render correctly on
+recent versions of those browsers.
+* The HTML documents from the RFC Editor or Internet-Drafts directory
+may be re-rendered from the canonical XML format in
+the future to ensure the ongoing readability of the documents.  The
+intent is that any re-rendering would be due to exceptional
+circumstances rather than for minor annoyances.
+* The HTML must display adequately in at least one text-based browser.
+Some consumers of the RFC Series can only access the documents on
+text-based terminals.
+* The HTML document will be self-contained, without requiring external
+files for images, CSS, JavaScript, or the like.  This will allow
+the HTML file to be moved over various non-HTTP transports (such as
+email, FTP, and rsync) without breakage.
+* JavaScript will be supported on a limited basis.  It will not be
+permitted to overwrite or change any text present in the rendered HTML.
+It may, on a limited basis, add additional text that provides
+post-publication metadata or pointers if warranted.  All such text will
+be clearly marked as additional.
+* The HTML document will allow easy local override of the default CSS
+formatting.  This will allow users who have a different visual style
+that they prefer to make RFCs display with that style without having to
+alter the contents of the HTML document.  This might also be valuable
+for allowing people with specific accessibility needs to use a
+customized CSS.
+* HTML tags in documents will rarely have attributes whose only purpose
+is to affect the rendered styling, and those will only be used if it
+would not be possible to specify that styling in a CSS.  No such attributes are known at this time.
+* Both user-defined and auto-generated anchors must be supported and
+linkable, with user-defined anchors appearing in an "id" attribute.
+Auto-generated anchors will be generated for every heading, paragraph,
+and so on, not just those that do not have user-defined anchors.
+User-defined anchors may, and auto-generated anchors will, appear next to
+paragraphs, figures, tables, blockquotes, and section titles.
+* All sections, subsections, figures, and paragraphs should have stable
+numbered link anchors.  Additionally, anchors expressed in the source
+XML should be exposed as anchors in the HTML output as well.
+* The HTML must make it easy to separate sections along with all of their
+subsections into separate files.  This will make creating EPUB
+documents easier in the future.
+* The HTML produced for Internet-Drafts will differ from that produced
+by the RFC Editor due to differences in the output from the prep tool.
+* The abstract must be marked up or tagged in a way that popular search
+engines will extract it as a summary.
+
+[#accessibility]
+=== Requirements for Accessibility
+
+
+* Normative information must be easily accessible to the following
+consumers:
+** People with impaired vision, including those that use large fonts
+and those that use screen readers
+** People with difficulty distinguishing between colors
+** People who use devices with small screens, such as cell phones
+* Specific instances where goals for accessibility are important in the
+design choices of the format have been called out in the text.
+* Note: designing for these consumers does not preclude the use of
+features they cannot use, but it does require that key semantic data not
+be lost when read using the tools and settings that are required by a given
+constituency.
+
+
+[#html5]
+== HTML Version
+
+The RFC Editor will periodically determine which version of the
+HTML specification will be referenced for tools generating the
+format defined in this document.  The starting version will be that
+defined in <<W3C.REC-html5-20141028>>, commonly known as
+"HTML5".  Although the HTML specification mandates several of the syntax
+and structure rules described in this document, they are called out here
+for emphasis.
+
+[#syntax]
+== HTML Syntax
+
+The processor emitting HTML from the XML source will follow these
+rules:
+
+* The HTML output is encoded as UTF-8, as specified in
+<<RFC3629>>.
+* The document is valid HTML.
+* Double quotes (U+0022 QUOTATION MARK: ") are used to quote attribute
+values unless the HTML specification forbids quoting a particular
+attribute.
+* Each logical line is terminated solely with a \n (U+000A: LINE
+FEED), otherwise known as "Unix-style" line endings.
+* Code points below (U+0020: SPACE) or character entity references
+that generate them (e.g. &amp;#9;), other than (U+000A: LINE FEED)
+may not be used.  Note: this rule explicitly forbids \t (U+0009:
+CHARACTER TABULATION), \f (U+000C: FORM FEED), and \r (U+000D:
+CARRIAGE RETURN) from appearing in the HTML output.
+* Comments in the source XML, if any, will not be copied into
+the HTML.
+* The HTML output will be pretty-printed, using whatever
+consistent rules are deemed best by the developers of the HTML
+production tools.
+
+
+Note: none of these rules affect the rendered output of the HTML, but they 
+are intended to increase the chance that text comparison tools
+(e.g., "diff") that operate on the HTML output are easier to write.
+
+[#common]
+== Common Items
+
+This section lists items that are common across multiple parts of the HTML
+document.
+
+[#ids]
+=== IDs
+
+HTML elements that are generated from XML elements that include
+an "anchor" attribute will use the value of the "anchor" attribute
+as the value of the "id" attribute of the corresponding HTML element.
+The prep tool produces XML with "anchor" attributes in all elements that need them.
+Some HTML constructs (such as
+&lt;section&gt;) will use
+multiple instances of these identifiers.
+
+[#pilcrows]
+=== Pilcrows
+
+Each paragraph, artwork, or sourcecode segment outside of a
+&lt;figure&gt; or &lt;table&gt; element will be appended with a
+space and a "pilcrow" (U+00B6: PILCROW SIGN), otherwise known as a
+"paragraph sign".  For the purposes of clarity in ASCII renderings
+of this document, in this document pilcrows are rendered as
+"&amp;para;".  The pilcrow will be linked to the "id" attribute on the
+XML entity to which it is associated using an &lt;a&gt; element of
+class "pilcrow".  For example:
+
+....
+<p id="s-1.1-1">
+  Some paragraph text. <a class="pilcrow" href="#s-1.1-1">&para;</a>
+</p>
+....
+
+The pilcrow will normally be invisible unless the element it is
+attached to is moused over.  The pilcrow will be surrounded by a
+link that points to the element it is attached to.
+
+Pilcrows are never included inside a &lt;table&gt; or
+&lt;figure&gt; element, since the figure number or table number
+serves as an adequate link target.
+
+Elements that might otherwise contain a pilcrow do not get marked
+with a pilcrow if they contain one or more child elements that are
+marked with a pilcrow. For example:
+
+....
+<blockquote id="s-1.2-1">
+  <p id="s-1.2-2">Four score and seven years ago our fathers brought
+    forth on this continent, a new nation, conceived in Liberty, and
+    dedicated to the proposition that all men are created equal.
+    <a href="#s-1.2-2" class="pilcrow">&para;</a></p>
+  <!-- NO pilcrow here -->
+</blockquote>
+....
+
+[#front-matter]
+== Front Matter
+
+The front matter of the HTML format contains processing information,
+metadata of various types, and styling information that applies to the
+document as a whole.  This section describes HTML that is not
+necessarily a direct transform from the XML format.  For more details
+on each of the tags that generate content in this section,
+see <<elements>>.
+
+[#doctype]
+=== DOCTYPE
+
+The DOCTYPE of the document is "html", which declares that the
+document is compliant with HTML5.  The document will start with
+exactly this string:
+
+....
+<!DOCTYPE html>
+....
+
+[#root-element]
+=== Root Element
+
+The root element of the document is &lt;html&gt;.  This element
+includes a &quot;lang&quot; attribute, whose value is a language tag, as discussed in <<RFC5646>>,
+that describes the natural language of the document.  The
+language tag to be included is "en".  The class of the &lt;html&gt;
+element will be copied verbatim from the XML &lt;rfc&gt; element's
+&lt;front&gt; element's &lt;seriesInfo&gt; element's "name"
+attributes (separated by spaces; see Section 2.47.3 of <<RFC7991>>), allowing CSS to style RFCs and
+Internet-Drafts differently from one another (if needed):
+
+....
+<html lang="en" class="RFC">
+....
+
+[#head-element]
+=== &lt;head&gt; Element
+
+The root &lt;html&gt; will contain a &lt;head&gt; element that
+contains the following elements, as needed.
+
+[#charset-declaration]
+==== Charset Declaration
+
+In order to be correctly processed by browsers that load the HTML
+using a mechanism that does not provide a valid content-type
+or charset (such as from a local file system using a "file:" URL),
+the HTML &lt;head&gt; element contains a &lt;meta&gt; element,
+whose &quot;charset&quot; attribute value is "utf-8":
+
+....
+<meta charset="utf-8">
+....
+
+[#head-title]
+==== Document Title
+
+The contents of the &lt;title&gt; element from the XML source
+will be placed inside an HTML &lt;title&gt; element in the
+header.
+
+[#meta]
+==== Document Metadata
+
+The following &lt;meta&gt; elements will be included:
+
+* author - one each for the each of the "fullname"s and "asciiFullname"s of
+all of the &lt;author&gt;s from the &lt;front&gt; of the XML
+source
+* description - the &lt;abstract&gt; from the XML source
+* generator - the name and version number of the software used
+to create the HTML
+* keywords - comma-separated &lt;keyword&gt;s from the XML
+source
+
+For example:
+
+....
+<meta name="author" content="Joe Hildebrand">
+<meta name="author" content="JOE HILDEBRAND">
+<meta name="author" content="Heather Flanagan">
+<meta name="description" content="This document defines...">
+<meta name="generator" content="xmljade v0.2.4">
+<meta name="keywords" content="html,css,rfc">
+....
+
+Note: the HTML &lt;meta&gt; tag does not contain a closing
+slash.
+
+[#xmlsource]
+==== Link to XML Source
+
+The &lt;head&gt; element contains a &lt;link&gt; tag, with "rel"
+attribute of "alternate", "type" attribute of "application/rfc+xml",
+and "href" attribute pointing to the prepared XML source that was
+used to generate this document.
+
+....
+<link rel="alternate" type="application/rfc+xml" href="source.xml">
+....
+
+[#license]
+==== Link to License
+
+The &lt;head&gt; element contains a &lt;link&gt; tag, with "rel"
+attribute of "license" and "href" attribute pointing to the an
+appropriate copyright license for the document.
+
+....
+<link rel="license" 
+   href="https://trustee.ietf.org/trust-legal-provisions.html">
+....
+
+[#style]
+==== Style
+
+The &lt;head&gt; element contains an embedded CSS in a
+&lt;style&gt; element.  The styles in the style sheet are to be set
+consistently between documents by the RFC Editor, according to the
+best practices of the day.
+
+To ensure consistent formatting, individual style attributes should
+not be used in the main portion of the document.
+
+Different readers of a specification will desire different
+formatting when reading the HTML versions of RFCs.  To facilitate
+this, the &lt;head&gt; element also includes a &lt;link&gt; to a
+style sheet in the same directory as the HTML file, named
+"rfc-local.css". Any formatting in the linked style sheet will
+override the formatting in the included style sheet. For example:
+
+....
+<style>
+  body {}
+  ...
+</style>
+<link rel="stylesheet" type="text/css" href="rfc-local.css">
+....
+
+[#links]
+==== Links
+
+Each &lt;link&gt; element from the XML source is copied into
+the HTML header.  Note: the HTML &lt;link&gt; element does not
+include a closing slash.
+
+[#page-headers-footers]
+=== Page Headers and Footers
+
+In order to simplify printing by HTML renderers that implement
+<<W3C.WD-css3-page-20130314>>, a hidden HTML
+&lt;table&gt; tag of class "ears" is added at the beginning of the HTML &lt;body&gt;
+tag, containing HTML &lt;thead&gt; and &lt;tfoot&gt; tags, each of
+which contains an HTML &lt;tr&gt; tag, which contains three HTML
+&lt;td&gt; tags with class "left", "center", and "right",
+respectively.
+
+The &lt;thead&gt; corresponds to the top of the page, the
+&lt;tfoot&gt; to the bottom.  The string "[Page]" can be used
+as a placeholder for the page number.  In practice, this must
+always be in the &lt;tfoot&gt;'s right &lt;td&gt;, and no control
+of the formatting of the page number is implied.
+
+....
+<table class="ears">
+  <thead>
+    <tr>
+      <td class="left">Internet-Draft</td>
+      <td class="center">HTML RFC</td>
+      <td class="right">March 2016</td>
+    </tr>
+  </thead>
+  <tfoot>
+    <tr>
+      <td class="left">Hildebrand</td>
+      <td class="center">Expires September 2, 2016</td>
+      <td class="right">[Page]</td>
+    </tr>
+  </tfoot>
+</table>
+....
+
+[#document-information]
+=== Document Information
+
+
+Information about the document as a whole will appear as the first child of the
+HTML &lt;body&gt; element, embedded in an HTML &lt;dl&gt; element
+with id="identifiers".  The defined terms in the definition list
+are "Workgroup:", "Series:", "Status:", "Published:", and "Author:"
+or "Authors:" (as appropriate). For example:
+
+....
+<dl id="identifiers">
+  <dt>Workgroup:</dt>
+    <dd class="workgroup">rfc-interest</dd>
+  <dt>Series:</dt>
+    <dd class="series">Internet-Draft</dd>
+  <dt>Status:</dt>
+    <dd class="status">Informational</dd>
+  <dt>Published:</dt>
+    <dd><time datetime="2014-10-25"
+              class="published">2014-10-25</time></dd>
+  <dt>Authors:</dt>
+    <dd class="authors">
+      <div class="author">
+        <span class="initial">J.</span>
+        <span class="surname">Hildebrand</span>
+        (<span class="organization">Cisco Systems, Inc.</span>)
+        <span class="editor">Ed.</span> 
+      </div>
+      <div class="author">
+        <span class="initial">H.</span>
+        <span class="surname">Flanagan</span>
+        (<span class="organization">RFC Editor</span>)
+      </div>
+    </dd>
+</dl>
+....
+
+[#table-of-contents]
+=== Table of Contents
+
+The table of contents will follow the boilerplate if the XML's &lt;rfc&gt;
+element's &quot;tocInclude&quot; attribute has the value "true".  An HTML &lt;h2&gt;
+heading containing the text "Table of Contents" will be followed by a
+&lt;nav&gt; element that contains a &lt;ul&gt; element for each depth
+of the section hierarchy.  Each section will be represented by a
+&lt;li&gt; element containing links by the section number (from the "pn"
+attribute) and by the name (from the "slugifiedName" attribute of the
+&lt;name&gt; child element).  Each &lt;nav&gt;, &lt;ul&gt;, and
+&lt;li&gt; element will have the class "toc".
+
+For example:
+
+....
+<h2 id="toc">Table of Contents</h2>
+<nav class="toc">
+  <ul class="toc">
+    <li class="toc">
+      <a href="s-1">1</a>. <a href="n-introduction">Introduction</a>
+    </li>
+    <ul class="toc">
+      <li class="toc">
+        <a href="s-1.1">1.1</a>. <a href="n-sub-intro">Sub Intro</a>
+      </li>
+...
+....
+
+[#middle]
+== Main Body
+
+The main body of the HTML document is processed according to the rules in
+<<elements>>.
+
+[#back-matter]
+== Back Matter
+
+
+The back matter of the HTML document includes an index (if generated),
+information about the authors, and further information about the
+document itself.
+
+[#index]
+=== Index
+
+The index will be produced as dictated by the RFC Editor's Style
+	Guide <<RFC-STYLE>> if and only if the XML document's &lt;rfc&gt; 
+element has an &quot;indexInclude&quot; attribute with the value "true" and there
+is one or more &lt;iref&gt; elements in the document.
+
+[#index-index]
+==== Index Contents
+
+The index section will start with an &lt;h2&gt; heading containing
+the text "Index", followed by links to each of the lettered
+portions of the index.  Links are not generated for letters that
+do not occur as the first letter of an index item.
+
+For example:
+
+....
+<h2>Index</h2>
+<div class="index">
+  <div class="indexIndex">
+    <a href="#rfc.index.C">C</a>
+    <a href="#rfc.index.P">P</a>
+  </div>
+  ...
+....
+
+[#index-letters]
+==== Index Letters
+
+The index letter is followed by a &lt;ul&gt; tag that contains an
+&lt;li&gt; tag for each first letter represented in the index. This
+&lt;li&gt; tag has the class "indexChar" and contains an &lt;a&gt;
+tag with the id pointed to by the index letter as well as an
+&quot;href&quot; attribute to itself.  The &lt;li&gt; tag also includes a &lt;ul&gt; tag
+that will contain the index items.
+
+For example:
+
+....
+<ul>
+  <li class="indexChar">
+    <a href="#rfc.index.C" id="rfc.index.C">C</a>
+    <ul>
+      <!-- items go here -->
+    </ul>
+  </li>
+  ...
+....
+
+[#index-items]
+==== Index Items
+
+Each index item can have multiple &lt;iref&gt; elements to point to, all
+with the same item attribute.  Each index item is represented by an
+&lt;li&gt; tag of class "indexItem" containing a &lt;span&gt; of class
+"irefItem" for the item text and one of class "irefRefs" for the generated
+references (if there is at least one reference to the item not having
+a subitem).  Each generated reference contains an &lt;a&gt; tag
+containing the section number where the &lt;iref&gt; is found, with
+an "href" attribute pointing to the "irefid" attribute of the &lt;iref&gt; element from the XML document. If the primary
+attribute of the &lt;iref&gt; element has the value "true", the &lt;a&gt; element in the HTML document
+will have the class "indexPrimary". Commas may be used to separate the
+generated references.
+
+For example:
+
+....
+<li class="indexItem">
+  <span class="irefItem">Bullets</span>
+  <span class="irefRefs">
+    <a class="indexPrimary" href="#s-Bullets-1">2</a>,
+    <a href="#s-Bullets-2">2</a>
+  </span>
+  <!-- subitems go here -->
+</li>
+...
+....
+
+[#index-subitems]
+==== Index Subitems
+
+If an index item has at least one subitem, the &lt;li&gt; of
+that item will contain a &lt;ul&gt;, with one &lt;li&gt; for each
+subitem, of class "indexSubItem".  The format for each subitem is 
+similar to that used for items, except the class of the first &lt;span&gt;
+tag is "irefSubItem".
+
+For example:
+
+....
+<ul>
+  <li class="indexSubItem">
+    <span class="irefSubItem">Ordered</span>
+    <span class="irefRefs">
+      <a href="#s-Bullets-Ordered-1">2</a>
+    </span>
+  </li>
+</ul>
+...
+....
+
+[#authors-addresses]
+=== Authors' Addresses Section
+
+At the end of the document, author information will be included
+inside an HTML &lt;section&gt; element whose &quot;id&quot; attribute is
+"author-addresses".  The class names of the constituent HTML tags
+have been chosen to match the class names in <<HCARD>>.
+
+The information for each author will be separated by an HTML
+&lt;hr&gt; element with class "addr".
+
+....
+<section id="author-addresses">
+  <h2>
+    <a class="selfRef" href="#author-addresses">
+      Authors' Addresses
+    </a>
+  </h2>
+  <address class="vcard">
+    <div class="nameRole"><span class="fn">Joe Hildebrand</span>
+      (<span class="role">editor</span>)</div>
+    <div class="org">Cisco Systems, Inc.</div>
+  </address>
+  <hr class="addr">
+  <address class="vcard">
+    <div class="nameRole"><span class="fn">Heather Flanagan</span>
+      (<span class="role">editor</span>)</div>
+    <div class="org">RFC Series Editor</div>
+  </address>
+</section>
+....
+
+[#docInfo]
+=== Document Information
+
+A few bits of metadata about the document that are less
+important to most readers are included after the author information.
+These are gathered together into a &lt;div&gt; of class
+"docInfo".
+
+
+The finalized time is copied from the &lt;rfc&gt; element's
+&quot;prepTime&quot; attribute.  The rendered time is the time that this
+HTML was generated.
+
+For example:
+
+....
+<div class="docInfo">
+  <span class="finalized">
+    Finalized: <time
+    datetime="2015-04-29T18:59:08Z">2015-04-29T18:59:08Z</time>
+  </span>
+  <span class="rendered">
+    Rendered: <time
+    datetime="2015-04-29T18:59:10Z">2015-04-29T18:59:10Z</time>
+  </span>
+</div>
+....
+
+[#elements]
+== Elements
+
+This section describes how each of the XML elements from
+<<RFC7991>> is rendered to HTML.
+Many of the descriptions have examples to clarify how elements will be rendered.
+
+[#element-abstract]
+=== &lt;abstract&gt;
+
+The abstract is rendered in a similar fashion to a &lt;section&gt; with anchor="abstract" and
+&lt;name&gt;Abstract&lt;/name&gt;, but without a section number.
+
+....
+<section id="abstract">
+  <h2><a href="#abstract" class="selfRef">Abstract</a></h2>
+  <p id="s-abstract-1">This document defines...
+    <a href="#s-abstract-1" class="pilcrow">&para;</a>
+  </p>
+</section>
+....
+
+
+[#element-address]
+=== &lt;address&gt;
+
+This element is used in the Authors' Addresses section.
+It is rendered
+as an HTML &lt;address&gt; tag of class "vcard".  If none of the
+descendant XML elements has an "ascii" attribute, the &lt;address&gt;
+HTML tag includes the HTML rendering of each of the descendant
+XML elements.  Otherwise, the &lt;address&gt; HTML tag includes
+an HTML &lt;div&gt; tag of class "ascii" (containing the HTML
+rendering of the ASCII variants of each of the descendant XML
+elements), an HTML &lt;div&gt; tag of class "alternative-contact",
+(containing the text "Alternate contact information:"), and
+an HTML &lt;div&gt; tag of class "non-ascii" (containing the HTML
+rendering of the non-ASCII variants of each of the descendant XML
+elements).
+
+
+Note: the following example shows some ASCII equivalents that are
+the same as their nominal equivalents for clarity; normally, the ASCII
+equivalents would not be included for these cases.
+
+....
+<address class="vcard">
+  <div class="ascii">
+    <div class="nameRole"><span class="fn">Joe Hildebrand</span>
+      (<span class="role">editor</span>)</div>
+    <div class="org">Cisco Systems, Inc.</div>
+  </div>
+  <div class="alternative-contact">
+    Alternate contact information:
+  </div>
+  <div class="non-ascii">
+    <div class="nameRole"><span class="fn">Joe Hildebrand</span>
+      (<span class="role">editor</span>)</div>
+    <div class="org">Cisco Systems, Inc.</div>
+  </div>
+</address>
+....
+
+[#element-annotation]
+=== &lt;annotation&gt;
+
+This element is rendered as the text ", " (a comma and a space)
+followed by a &lt;span&gt; of class "annotation" at the end
+of a &lt;reference&gt; element, the &lt;span&gt;
+containing appropriately transformed elements from the children of
+the &lt;annotation&gt; tag.
+
+....
+ <span class="annotation">Some <em>thing</em>.</span>
+....
+
+[#element-area]
+=== &lt;area&gt;
+
+Not currently rendered to HTML.
+
+[#element-artwork]
+=== &lt;artwork&gt;
+
+Artwork can consist of either inline text or SVG.  If the artwork is
+not inside a &lt;figure&gt; element, a
+<<pilcrows,pilcrow>> is included.  Inside a
+&lt;figure&gt; element, the figure title serves the purpose of the
+pilcrow. If the "align" attribute has the value "right", the CSS class
+"alignRight" will be added. If the "align" attribute has the value
+"center", the CSS class "alignCenter" will be added.
+
+[#element-artwork-text]
+==== Text Artwork
+
+Text artwork is rendered inside an HTML &lt;pre&gt; element, which
+is contained by a &lt;div&gt; element for consistency with SVG
+artwork.  Note that CDATA blocks are not a part of HTML,
+so angle brackets and ampersands (i.e., &lt;, &gt;, and &amp;) must be escaped as &amp;lt;, &amp;gt;,
+and &amp;amp;, respectively.
+
+The &lt;div&gt; element will have CSS classes of "artwork",
+"art-text", and "art-" prepended to the value of the &lt;artwork&gt;
+element's "type" attribute, if it exists.
+
+....
+<div class="artwork art-text art-ascii-art"  id="s-1-2">
+  <pre>
+ ______________
+&lt; hello, world &gt;
+ --------------
+  \   ^__^
+   \  (oo)\_______
+      (__)\       )\/\
+          ||----w |
+          ||     ||
+  </pre>
+  <a class="pilcrow" href="#s-1-2">&para;</a>
+</div>
+....
+
+[#element-artwork-svg]
+==== SVG Artwork
+
+SVG artwork will be included inline.  The SVG is wrapped in a
+&lt;div&gt; element with CSS classes "artwork" and "art-svg".
+
+If the SVG &quot;artwork&quot; element is a child of &lt;figure&gt; and the
+artwork is specified as align="right", an
+empty HTML &lt;span&gt; element is added directly after the
+&lt;svg&gt; element, in order to get right alignment to work correctly
+in HTML rendering engines that do not support the flex-box
+model.
+
+Note: the &quot;alt&quot; attribute of &lt;artwork&gt; is not currently used
+for SVG; instead, the &lt;title&gt; and &lt;desc&gt; tags are used
+in the SVG.
+
+....
+<div class="artwork art-svg" id="s-2-17">
+  <svg width="100" height="100" xmlns="http://www.w3.org/2000/svg">
+    <desc>Alt text here</desc>
+    <circle
+      cx="50" cy="50" r="40"
+      stroke="green" stroke-width="4" fill="yellow" />
+  </svg>
+  <a href="#s-2-17" class="pilcrow">&para;</a>
+</div>
+....
+
+[#element]
+==== Other Artwork
+
+Other artwork will have a &quot;src&quot; attribute that uses the "data" URI scheme
+defined in <<RFC2397>>.  Such artwork is rendered in an
+HTML &lt;img&gt; element.  Note: the HTML &lt;img&gt; element does
+not have a closing slash.
+
+Note: such images are not yet allowed in RFCs
+even though the format supports them.  A limited set of "data:" mediatypes for artwork may be allowed in the
+future.
+
+....
+<div class="artwork art-logo" id="s-2-58">
+  <img alt="IETF logo"
+       src="data:image/gif;charset=utf-8;base64,...">
+  <a class="pilcrow" href="#s-2-58">&para;</a>
+</div>
+....
+
+[#element-aside]
+=== &lt;aside&gt;
+
+This element is rendered as an HTML &lt;aside&gt; element, with
+all child content appropriately transformed.
+
+....
+<aside id="s-2.1-2">
+  <p id="s-2.1-2.1">
+    A little more than kin, and less than kind.
+    <a class="pilcrow" href="#s-2.1-2.1">&para;</a>
+  </p>
+</aside>
+....
+
+[#element-author]
+=== &lt;author&gt;
+
+The &lt;author&gt; element is used in several places in the output.
+Different rendering is used for each.
+
+==== Authors in Document Information
+
+As seen in the <<document-information,format=title>>
+at the beginning of the HTML, each document author is rendered
+as an HTML &lt;div&gt; tag of class "author".
+
+
+Inside the &lt;div class="author"&gt; HTML tag, the author's
+initials and surname (or the fullname, if it exists and the others
+do not) will be rendered in an HTML &lt;div&gt;
+tag of class "author-name". If the &lt;author&gt;
+contains "asciiInitials" and "asciiSurname" attributes, or contains
+as "asciiFullname" attribute, the author's name is rendered twice,
+with the first being the non-ASCII version, wrapped in an HTML
+&lt;span&gt; tag of class "non-ascii", followed by the ASCII
+version wrapped in an HTML &lt;span&gt; tag of class "ascii",
+wrapped in parentheses.  If the &lt;author&gt; has a "role"
+attribute of "editor", the &lt;div class="author-name"&gt; will
+also contain the text ", " (comma, space), followed by an HTML
+&lt;span&gt; tag of class "editor", which contains the text "Ed.".
+
+If the &lt;author&gt; element contains an
+<<element-organization,format=title>>
+element, it is also rendered inside the &lt;div class="author"&gt;
+HTML tag. 
+
+....
+<div class="author">
+  <div class="author-name">
+    H. Flanagan,
+    <span class="editor">Ed.</span></div>
+  <div class="org">Test Org</div>
+</div>
+<div class="author">
+  <div class="author-name">
+    <span class="non-ascii">Hildebrand</span>
+    (<span class="ascii">HILDEBRAND</span>)
+  </div>
+  <div class="org">
+    <span class="non-ascii">Test Org</span>
+    (<span class="ascii">TEST ORG</span>)
+  </div>
+</div>
+....
+
+==== Authors of This Document
+
+As seen in the Authors' Addresses section,
+at the end of the HTML, each document author is rendered into an
+HTML &lt;address&gt; element with the CSS class "vcard".
+
+The HTML &lt;address&gt; element will contain an HTML &lt;div&gt;
+with CSS class "nameRole".  That div will contain an HTML &lt;span&gt;
+element with CSS class "fn" containing the value of the "fullname"
+attribute of the &lt;author&gt; XML element and an HTML &lt;span&gt;
+element with CSS class "role" containing the value of the "role"
+attribute of the &lt;author&gt; XML element (if there is a role).
+Parentheses will surround the &lt;span class="role"&gt;, if it
+exists.
+
+....
+<address class="vcard">
+  <div class="nameRole">
+    <span class="fn">Joe Hildebrand</span>
+    (<span class="role">editor</span>)
+  </div>
+  ...
+....
+
+After the name, the
+<<element-organization,format=title>> and
+<<element-address,format=title>> child elements of
+the author are rendered inside the HTML &lt;address&gt; tag.
+
+When the &lt;author&gt; element, or any of its descendant elements,
+has any attribute that starts with "ascii", all of the author
+information is displayed twice.  The first version is wrapped in
+an HTML &lt;div&gt; tag with class "ascii"; this version prefers
+the ASCII version of information, such as "asciiFullname", but falls
+back on the non-ASCII version if the ASCII version doesn't exist.
+The second version is wrapped in an HTML &lt;div&gt; tag with class
+"non-ascii"; this version prefers the non-ASCII version of
+information, such as "fullname", but falls back on the ASCII
+version if the non-ASCII version does not exist.  Between these
+two HTML &lt;div&gt;s, a third &lt;div&gt; is inserted, with class
+"alternative-contact", containing the text "Alternate contact
+information:".
+
+....
+<address class="vcard">
+  <div class="ascii">
+    <div class="nameRole">
+      <span class="fn">The ASCII name</span>
+    </div>
+  </div>
+  <div class="alternative-contact">
+    Alternate contact information:
+  </div>
+  <div class="non-ascii">
+    <div class="nameRole">
+      <span class="fn">The non-ASCII name</span>
+      (<span class="role">editor</span>)
+    </div>
+  </div>
+</address>
+....
+
+==== Authors of References
+
+In the output generated from a reference element, author tags are
+rendered inside an HTML &lt;span&gt; element with CSS class
+"refAuthor".  See Section 4.8.6.2 of <<RFC7322>> for
+	    guidance on how author names are to appear.
+
+....
+<span class="refAuthor">Flanagan, H.</span> and
+<span class="refAuthor">N. Brownlee</span>
+....
+
+[#element-back]
+=== &lt;back&gt;
+
+If there is exactly one
+<<element-references,format=title>> child, render
+that child in a similar way to a <<element-section,format=title>>.
+If there are more than one
+<<element-references,format=title>> children, render
+as a <<element-section,format=title>> whose name is
+"References", containing a <<element-section,format=title>>
+for each <<element-references,format=title>> child.
+
+After any <<element-references,format=title>> sections,
+render each <<element-section,format=title>> child of
+	  <<element-back,format=title>>
+as an appendix.
+
+....
+<section id="n-references">
+  <h2 id="s-2">
+    <a class="selfRef" href="#s-2">2.</a>
+    <a class="selfRef" href="#n-references">References</a>
+  </h2>
+  <section id="n-normative">
+    <h3 id="s-2.1">
+      <a class="selfRef" href="#s-2.1">2.1.</a>
+      <a class="selfRef" href="#n-normative">Normative</a>
+    </h3>
+    <dl class="reference"></dl>
+  </section>
+  <section id="n-informational">
+    <h3 id="s-2.2">
+      <a class="selfRef" href="#s-2.2">2.2.</a>
+      <a class="selfRef" href="#n-informational">Informational</a>
+    </h3>
+    <dl class="reference"></dl>
+  </section>
+</section>
+<section id="n-unimportant">
+  <h2 id="s-A">
+    <a class="selfRef" href="#s-A">Appendix A.</a>
+    <a class="selfRef" href="#n-unimportant">Unimportant</a>
+  </h2>
+</section>
+....
+
+[#element-bcp14]
+=== &lt;bcp14&gt;
+
+This element marks up words like MUST and SHOULD <<BCP14>> with an HTML
+&lt;span&gt; element with the CSS class "bcp14".
+
+....
+You <span class="bcp14">MUST</span> be joking.
+....
+
+
+[#element-blockquote]
+=== &lt;blockquote&gt;
+
+This element renders in a way similar to the HTML &lt;blockquote&gt;
+element.  If there is a "cite" attribute, it is  copied
+to the HTML "cite" attribute.  If there is a "quoteFrom" attribute,
+it is placed inside a &lt;cite&gt; element at the end of the quote,
+with an &lt;a&gt; element surrounding it (if there is a "cite"
+attribute), linking to the cited URL.
+
+If the &lt;blockquote&gt; does not contain another element that gets a
+<<pilcrows,pilcrow>>, a pilcrow is added.
+
+Note that the "&amp;mdash;" at the beginning of the &lt;cite&gt; element
+should be a proper emdash, which is difficult to show in the
+display of the current format.
+
+....
+<blockquote id="s-1.2-1"
+  cite="http://...">
+  <p id="s-1.2-2">Four score and seven years ago our fathers
+    brought forth on this continent, a new nation, conceived
+    in Liberty, and dedicated to the proposition that all men
+    are created equal.
+    <a href="#s-1.2-2" class="pilcrow">&para;</a>
+  </p>
+  <cite>&mdash; <a href="http://...">Abraham Lincoln</a></cite>
+</blockquote>
+....
+
+[#element-boilerplate]
+=== &lt;boilerplate&gt;
+
+The Status of This Memo and the Copyright statement, together
+	commonly referred to as the document boilerplate, appear after the
+	Abstract. The children of the input &lt;boilerplate&gt; element
+are treated in a similar fashion to unnumbered sections.
+
+....
+<section id="status-of-this-memo">
+  <h2 id="s-boilerplate-1">
+    <a href="#status-of-this-memo" class="selfRef">
+      Status of this Memo</a>
+  </h2>
+  <p id="s-boilerplate-1-1">This Internet-Draft is submitted in full
+    conformance with the provisions of BCP 78 and BCP 79.
+    <a href="#s-boilerplate-1-1" class="pilcrow">&para;</a>
+  </p>
+...
+....
+
+[#element-br]
+=== &lt;br&gt;
+
+This element is directly rendered as its HTML counterpart.  Note:
+in HTML, &lt;br&gt; does not have a closing slash.
+
+[#element-city]
+=== &lt;city&gt;
+
+This element is rendered as a &lt;span&gt; element with CSS
+class "locality".
+
+....
+<span class="locality">Guilford</span>
+....
+
+[#element-code]
+=== &lt;code&gt;
+
+This element is rendered as a &lt;span&gt; element with CSS
+class "postal-code".
+
+....
+<span class="postal-code">GU16 7HF<span>
+....
+
+[#element-country]
+=== &lt;country&gt;
+
+This element is rendered as a &lt;div&gt; element with CSS
+class "country-name".
+
+....
+<div class="country-name">England</div>
+....
+
+[#element-cref]
+=== &lt;cref&gt;
+
+This element is rendered as a &lt;span&gt; element with CSS
+class "cref".  Any anchor is copied to the &quot;id&quot; attribute.  If there is
+a source given, it is contained inside the &quot;cref&quot; &lt;span&gt; element with another
+&lt;span&gt; element of class "crefSource".
+
+....
+<span class="cref" id="crefAnchor">Just a brief comment
+about something that we need to remember later.
+<span class="crefSource">--life</span></span>
+....
+
+[#element-date]
+=== &lt;date&gt;
+
+
+
+This element is rendered as the HTML &lt;time&gt; element.  If the
+"year", "month", or "day" attribute is included on the XML element,
+an appropriate "datetime" element will be generated in HTML.
+
+If this date is a child of the document's &lt;front&gt; element, it
+gets the CSS class "published".
+
+If this date is inside a &lt;reference&gt; element, it gets the
+CSS class "refDate".
+
+....
+<time datetime="2014-10" class="published">October 2014</time>
+....
+
+[#element-dd]
+=== &lt;dd&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-displayreference]
+=== &lt;displayreference&gt;
+
+This element does not affect the HTML output, but it is used in the generation of the 
+<<element-reference,format=title>>,
+<<element-referencegroup,format=title>>,
+<<element-relref,format=title>>, and
+<<element-xref,format=title>> elements.
+
+[#element-dl]
+=== &lt;dl&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+If the hanging attribute is "false", add the "dlParallel" class, else
+add the "dlHanging" class.
+
+If the spacing attribute is "compact", add the "dlCompact" class.
+
+[#element-dt]
+=== &lt;dt&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-em]
+=== &lt;em&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-email]
+=== &lt;email&gt;
+
+
+This element is
+rendered as an HTML &lt;div&gt; containing the string "Email:" and
+an HTML &lt;a&gt; element with the "href" attribute set to the
+equivalent "mailto:" URI, a CSS class of "email", and the contents set
+to the email address.  If this is the version of the address with
+ASCII, the "ascii" attribute is preferred to the element text.
+
+....
+<div>
+  <span>Email:</span>
+  <a class="email" href="mailto:joe@example.com">joe@example.com</a>
+</div>
+....
+
+[#element-eref]
+=== &lt;eref&gt;
+
+This element is rendered as an HTML &lt;a&gt; element, with the "href"
+attribute set to the value of the "target" attribute and the CSS
+class of "eref".
+
+....
+<a href="https://..." class="eref">the text</a>
+....
+
+[#element-figure]
+=== &lt;figure&gt;
+
+This element renders as the HTML &lt;figure&gt; element, containing
+the artwork or sourcecode indicated and an HTML &lt;figcaption&gt;
+element.  The &lt;figcaption&gt; element will contain an &lt;a&gt; element
+around the figure number.  It will also
+contain another &lt;a&gt; element with CSS class "selfRef" around the
+figure name, if a name was given.
+
+....
+<figure id="f-1">
+  ...
+  <figcaption>
+    <a href="#f-1">Figure 1.</a>
+    <a href="#n-it-figures" id="n-it-figures" class="selfRef">
+      It figures
+    </a>
+  </figcaption>
+</figure>
+....
+
+[#element-front]
+=== &lt;front&gt;
+
+See <<document-information,"Document Information">> for information on this element.
+
+[#element-iref]
+=== &lt;iref&gt;
+
+This element is rendered as an empty &lt;&gt; tag of class &quot;iref&quot;, with
+an &quot;id&quot; attribute consisting of the &lt;iref&gt; element's &quot;irefid&quot; attribute:
+
+....
+<span class="iref" id="s-Paragraphs-first-1"/>
+....
+
+[#element-keyword]
+=== &lt;keyword&gt;
+
+Each &lt;keyword&gt; element renders its text into the &lt;meta&gt;
+keywords in the document's header, separated by commas.
+
+....
+<meta name="keywords" content="html,css,rfc">
+....
+
+[#element-li]
+=== &lt;li&gt;
+
+This element is rendered as its HTML counterpart.  However, if there
+is no contained element that has a
+<<pilcrows,pilcrow>> attached, a pilcrow
+is added.
+
+....
+<li id="s-2-7">Item <a href="#s-2-7" class="pilcrow">&para;</a></li>
+....
+
+[#element-link]
+=== &lt;link&gt;
+
+This element is rendered as its HTML counterpart, in the HTML
+header.
+
+[#element-middle]
+=== &lt;middle&gt;
+
+This element does not add any direct output to HTML.
+
+[#element-name]
+=== &lt;name&gt;
+
+This element is never rendered directly; it is only rendered when
+considering a parent element, such as
+<<element-figure,format=title>>,
+<<element-references,format=title>>,
+<<element-section,format=title>>, or
+<<element-table,format=title>>.
+
+[#element-note]
+=== &lt;note&gt;
+
+This element is rendered like a 
+<<element-section,format=title>> element, but without
+a section number and with the CSS class of "note".  If the
+"removeInRFC" attribute is set to "yes", the generated &lt;div&gt; element
+will also include the CSS class "rfcEditorRemove".
+
+
+....
+<section id="s-note-1" class="note rfcEditorRemove">
+  <h2>
+    <a href="#n-editorial-note" class="selfRef">Editorial Note</a>
+  </h2>
+  <p id="s-note-1-1">
+    Discussion of this draft takes place...
+    <a href="#s-note-1-1" class="pilcrow">&para;</a>
+  </p>
+</section>
+....
+
+[#element-ol]
+=== &lt;ol&gt;
+
+The output created from an &lt;ol&gt; element depends upon the &quot;style&quot;
+attribute.
+
+If the &quot;spacing&quot; attribute has the value "compact", a CSS class of
+"olCompact" will be added.
+
+The group attribute is not copied; the input XML should have start
+values added by a prep tool for all grouped &lt;ol&gt; elements.
+
+[#ol-percent-styles]
+==== Percent Styles
+
+If the style attribute includes the character "%", the output is
+a &lt;dl&gt; tag with the class "olPercent".  Each contained &lt;li&gt; element
+is emitted as a &lt;dt&gt;/&lt;dd&gt; pair, with the generated
+label in the &lt;dt&gt; and the contents of the &lt;li&gt; in the
+&lt;dd&gt;.
+
+....
+<dl class="olPercent">
+  <dt>Requirement xviii:</dt>
+  <dd>Wheels on a big rig</dd>
+</dl>
+....
+
+[#ol-standard-styles]
+==== Standard Styles
+
+For all other styles, an &lt;ol&gt; tag is emitted, with any
+&quot;style&quot; attribute turned into the equivalent HTML attribute.
+
+....
+<ol class="compact" type="I" start="18">
+  <li>Wheels on a big rig</li>
+</ol>
+....
+
+[#element-organization]
+=== &lt;organization&gt;
+
+This element is
+rendered as an HTML &lt;div&gt; tag with CSS class "org".
+
+If the element contains the "ascii" attribute, the organization name
+is rendered twice: once with the non-ASCII version wrapped in an
+HTML &lt;span&gt; tag of class "non-ascii" and then as the ASCII version
+wrapped in an HTML &lt;span&gt; tag of class "ascii" wrapped in
+parentheses.
+
+....
+<div class="org">
+  <span class="non-ascii">Test Org</span>
+  (<span class="ascii">TEST ORG</span>)
+</div>
+....
+
+[#element-phone]
+=== &lt;phone&gt;
+
+
+This element is
+rendered as an HTML &lt;div&gt; tag containing the string "Phone:"  (wrapped
+in a span), an HTML &lt;a&gt; tag with CSS class "tel" containing the
+phone number (and an href with a corresponding "tel:" URI), and an
+HTML &lt;span&gt; with CSS class "type" containing the string
+"VOICE".
+
+....
+<div>
+  <span>Phone:</span>
+  <a class="tel" href="tel:+1-720-555-1212">+1-720-555-1212</a>
+  <span class="type">VOICE</span>
+</div>
+....
+
+[#element-postal]
+=== &lt;postal&gt;
+
+This element renders as an HTML &lt;div&gt; with CSS class
+"adr", unless it contains one or more &lt;postalLine&gt; child
+elements; in which case, it renders as an HTML &lt;pre&gt; element with CSS
+class "label".
+
+When there is no &lt;postalLine&gt; child, the following child
+elements are rendered into the HTML:
+
+* Each &lt;street&gt; is rendered
+* A &lt;div&gt; that includes:
+** The rendering of all &lt;city&gt; elements
+** A comma and a space: ", "
+** The rendering of all &lt;region&gt; elements
+** Whitespace
+** The rendering of all &lt;code&gt; elements
+* The rendering of all &lt;country&gt; elements
+
+
+....
+<div class="adr">
+  <div class="street-address">1 Main Street</div>
+  <div class="street-address">Suite 1</div>
+  <div>
+    <span class="city">Denver</span>,
+    <span class="region">CO</span>
+    <span class="postal-code">80212</span>
+  </div>
+  <div class="country-name">United States of America</div>
+</div>
+....
+
+[#element-postalLine]
+=== &lt;postalLine&gt;
+
+This element renders as the text contained by the element, followed
+by a newline.  However, the last &lt;postalLine&gt; in a given
+&lt;postal&gt; element should not be followed by a newline.  For example:
+
+....
+<postal>
+  <postalLine>In care of:</postalLine>
+  <postalLine>Computer Sciences Division</postalLine>
+</postal>
+....
+
+Would be rendered as:
+
+....
+<pre class="label">In care of:
+Computer Sciences Division</pre>
+....
+
+[#element-refcontent]
+=== &lt;refcontent&gt;
+
+This element renders as an HTML &lt;span&gt; with CSS class
+"refContent".
+
+
+....
+<span class="refContent">Self-published pamphlet</span>
+....
+
+[#element-reference]
+=== &lt;reference&gt;
+
+If the parent of this element is not a &lt;referencegroup&gt;, this
+element will render as a &lt;dt&gt; &lt;dd&gt; pair with the
+defined term being the reference "anchor" attribute surrounded by
+square brackets and the definition including the correct set of
+bibliographic information as specified by <<RFC7322>>.
+The &lt;dt&gt; element will have an "id" attribute of the reference
+anchor.
+
+....
+<dl class="reference">
+  <dt id="RFC5646">[RFC5646]</dt>
+  <dd>
+    <span class="refAuthor">Phillips, A.</span>
+    <span>and</span>
+    <span class="refAuthor">M. Davis</span>
+    <span class="refTitle">"Tags for Identifying Languages"</span>,
+    ...
+  </dd>
+</dl>
+....
+
+
+
+If the child of a &lt;referencegroup&gt;, this
+element renders as a &lt;div&gt; of class "refInstance" whose
+"id" attribute is the value of the &lt;source&gt; element's "anchor"
+attribute.
+
+....
+<div class="refInstance" id="RFC5730">
+  ...
+</div>
+....
+
+[#element-referencegroup]
+=== &lt;referencegroup&gt;
+
+A &lt;referencegroup&gt; is translated into a &lt;dt&gt; &lt;dd&gt;
+pair, with the defined term being the referencegroup "anchor"
+attribute surrounded by square brackets, and the definition containing
+the translated output of all of the child &lt;reference&gt;
+elements.
+
+....
+<dt id="STD69">[STD69]</dt>
+<dd>
+  <div class="refInstance" id="RFC5730">
+    <span class="refAuthor">Hollenbeck, S.</span>
+    ...
+  </div>
+  <div class="refInstance" id="RFC5731">
+    <span class="refAuthor">Hollenbeck, S.</span>
+    ...
+  </div>
+  ...
+</dd>
+....
+
+[#element-references]
+=== &lt;references&gt;
+
+If there is at exactly one &lt;references&gt; element, a
+section is added to the document, continuing with the next
+section number after the last top-level &lt;section&gt; in
+&lt;middle&gt;.  The &lt;name&gt; element of the &lt;references&gt;
+element is used as the section name.
+
+
+....
+<section id="n-my-references">
+  <h2 id="s-3">
+    <a href="#s-3" class="selfRef">3.</a>
+    <a href="#n-my-references class="selfRef">My References</a>
+  </h2>
+  ...
+</section>
+....
+
+If there is more than one &lt;references&gt; element, an HTML
+&lt;section&gt; element  is created to contain a subsection for
+each of the &lt;references&gt;.  The section number will be the next
+section number after the last top-level &lt;section&gt; in
+&lt;middle&gt;. The name of this section will
+be "References", and its "id" attribute will be "n-references".
+
+....
+<section id="n-references">
+  <h2 id="s-3">
+    <a href="#s-3" class="selfRef">3.</a>
+    <a href="#n-references" class="selfRef">References</a>
+  </h2>
+  <section id="n-informative-references">
+    <h3 id="s-3.1">
+      <a href="#s-3.1" class="selfRef">3.1.</a>
+      <a href="#n-informative-references" class="selfRef">
+        Informative References</a></h3>
+    <dl class="reference">...
+    </dl>
+  </section>
+  ...
+</section>
+....
+
+[#element-region]
+=== &lt;region&gt;
+
+This element is rendered as a &lt;span&gt; tag with CSS
+class "region".
+
+
+....
+<span class="region">Colorado</span>
+....
+
+[#element-relref]
+=== &lt;relref&gt;
+
+
+This element is rendered as an HTML &lt;a&gt; tag with CSS class
+"relref" and "href" attribute of the "derivedLink" attribute of the
+element. Different values of the "displayFormat" attribute cause
+the text inside that HTML &lt;a&gt; tag to change and cause extra
+text to be generated.  Some values of the "displayFormat"
+attribute also cause another HTML &lt;a&gt; tag to be rendered
+with CSS class "xref" and an "href" of "#" and the "target" attribute
+(modified by any applicable &lt;displayreference&gt; XML element)
+and text inside of the "target" attribute
+(modified by any applicable &lt;displayreference&gt; XML element).
+When used, this &lt;a class='xref'&gt; HTML tag is always surrounded
+by square brackets, for example, "[&lt;a class='xref' href='#foo'&gt;foo&lt;/a&gt;]".
+
+[#element-relref-df-of]
+==== displayFormat='of'
+
+The output is an &lt;a class='relref'&gt; HTML tag, with
+contents of "Section " and the value of the "section" attribute.
+This is followed by the word "of" (surrounded by whitespace). This
+is followed by the &lt;a class='xref'&gt; HTML tag (surrounded by
+square brackets).
+
+For example, with an input of:
+
+....
+See <relref section="2.3" target="RFC9999" displayFormat="of"
+derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"/>
+for an overview.
+....
+
+
+The HTML generated will be:
+
+....
+See <a class="relref"
+href="http://www.rfc-editor.org/info/rfc9999#s-2.3">Section
+2.3</a> of [<a class="xref" href="#RFC9999">RFC9999</a>]
+for an overview.
+....
+
+[#element-relref-df-comma]
+==== displayFormat='comma'
+
+The output is an &lt;a class='xref'&gt; HTML tag (wrapped by
+square brackets), followed by a comma (","), followed by
+whitespace, followed by an &lt;a class='relref'&gt; HTML tag, with
+contents of "Section " and the value of the "section"
+attribute.
+
+For example, with an input of:
+
+....
+See <relref section="2.3" target="RFC9999" displayFormat="comma"
+derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"/>,
+for an overview.
+....
+
+
+The HTML generated will be:
+
+....
+See [<a class="xref" href="#RFC9999">RFC9999</a>], <a class="relref"
+href="http://www.rfc-editor.org/info/rfc9999#s-2.3">Section 2.3</a>,
+for an overview.
+....
+
+[#element-relref-df-parens]
+==== displayFormat='parens'
+
+The output is an &lt;a&gt; element with "href" attribute whose value
+is the value of the "target" attribute prepended by "#", and whose
+content is the value of the "target" attribute; the entire element
+is wrapped in square brackets.  This is followed by  whitespace.
+This is followed by an &lt;a&gt; element whose "href" attribute is
+the value of the "derivedLink" attribute and whose content is the
+value of the "derivedRemoteContent" attribute; the entire element is
+wrapped in  parentheses.
+
+For example, if Section 2.3 of RFC 9999 has the title "Protocol
+Overview", for an input of:
+
+....
+See <relref section="2.3" target="RFC9999" displayFormat="parens"
+derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"
+derivedRemoteContent="Section 2.3"/> for an overview.
+....
+
+
+The HTML generated will be:
+
+....
+See [<a class="relref" href="#RFC9999">RFC9999</a>]
+(<a class="relref"
+href="http://www.rfc-editor.org/info/rfc9999#s-2.3">Section
+2.3</a>) for an overview.
+....
+
+[#element-relref-df-bare]
+==== displayFormat='bare'
+
+The output is an &lt;a&gt; element whose "href" attribute is
+the value of the "derivedLink" attribute and whose content is the
+value of the "derivedRemoteContent" attribute.
+
+For this input:
+
+....
+See <relref section="2.3" target="RFC9999" displayFormat="bare"
+derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"
+derivedRemoteContent="Section 2.3"/> and ...
+....
+
+
+The HTML generated will be:
+
+....
+See <a class="relref"
+href="http://www.rfc-editor.org/info/rfc9999#s-2.3">Section
+2.3</a> and ...
+....
+
+
+[#element-rfc]
+=== &lt;rfc&gt;
+
+Various attributes of this element are represented in different parts of the HTML
+document.
+
+[#element-section]
+=== &lt;section&gt;
+
+This element is rendered as an HTML &lt;section&gt; element,
+containing an appropriate level HTML heading element
+(&lt;h2&gt;-&lt;h6&gt;).  That heading element contains an &lt;a&gt;
+element around the part number (pn), if applicable (for instance,
+&lt;abstract&gt; does not get a section number).  Another &lt;a&gt;
+element is included with the section's name.
+
+....
+<section id="intro">
+  <h2 id="s-1">
+    <a href="#s-1" class="selfRef">1.</a>
+    <a href="#intro" class="selfRef">Introduction</a>
+  </h2>
+  <p id="s-1-1">Paragraph <a href="#s-1-1" class="pilcrow">&para;</a>
+  </p>
+</section>
+....
+
+[#element-seriesInfo]
+=== &lt;seriesInfo&gt;
+
+This element is rendered in an HTML &lt;span&gt; element with CSS
+name "seriesInfo".
+
+....
+<span class="seriesInfo">RFC 5646</span>
+....
+
+[#element-sourcecode]
+=== &lt;sourcecode&gt;
+
+This element is rendered in an HTML &lt;pre&gt; element with a CSS class of
+"sourcecode".  Note that CDATA blocks do not work consistently in
+HTML, so all &lt;, &gt;, and &amp; must be escaped as &amp;lt;,
+&amp;gt;, and &amp;amp;, respectively.  If the input XML has a "type"
+attribute, another CSS class of "lang-" and the type is added.
+
+If the sourcecode is not inside a &lt;figure&gt; element, a
+<<pilcrows,pilcrow>> is included.  Inside a
+&lt;figure&gt; element, the figure title serves the purpose of the
+pilcrow.
+
+....
+<pre class="sourcecode lang-c">
+#include &lt;stdio.h&gt;
+int main(void)
+{
+    printf(&quot;hello, world\n&quot;);
+    return 0;
+}
+</pre>
+....
+
+[#element-street]
+=== &lt;street&gt;
+
+This element renders as an HTML &lt;div&gt; element with CSS class
+"street-address".
+
+....
+<div class="street-address">1899 Wynkoop St, Suite 600</div>
+....
+
+[#element-strong]
+=== &lt;strong&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-sub]
+=== &lt;sub&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-sup]
+=== &lt;sup&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-t]
+=== &lt;t&gt;
+
+This element is rendered as an HTML &lt;p&gt; element.  A
+<<pilcrows,pilcrow>> is included.
+
+....
+<p id="s-1-1">A paragraph.
+  <a href="#s-1-1" class="pilcrow">&para;</a></p>
+....
+
+[#element-table]
+=== &lt;table&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-tbody]
+=== &lt;tbody&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-td]
+=== &lt;td&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-tfoot]
+=== &lt;tfoot&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-th]
+=== &lt;th&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-thead]
+=== &lt;thead&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-title]
+=== &lt;title&gt;
+
+The title of the document appears in a &lt;title&gt; element in the
+&lt;head&gt; element, as described in <<head-title>>.
+
+The title also appears in an &lt;h1&gt; element and follows directly
+after the Document Information.  The &lt;h1&gt; element has an &quot;id&quot;
+attribute with value "title".
+
+....
+<h1 id="title">HyperText Markup Language Request For
+    Comments Format</h1>
+
+....
+
+Inside a reference, the title is rendered as an HTML &lt;span&gt;
+tag with CSS class "refTitle".  The text is surrounded by quotes
+inside the &lt;span&gt;.
+
+....
+<span class="refTitle">"Tags for Identifying Languages"</span>
+....
+
+[#element-tr]
+=== &lt;tr&gt;
+
+This element is directly rendered as its HTML counterpart.
+
+[#element-tt]
+=== &lt;tt&gt;
+
+This element is rendered as an HTML &lt;code&gt; element.
+
+[#element-ul]
+=== &lt;ul&gt;
+
+This element is directly rendered as its HTML counterpart. If the
+"spacing" attribute has the value "compact", a CSS class of "ulCompact"
+will be added. If the "empty" attribute has the value "true", a CSS
+class of "ulEmpty" will be added.
+
+[#element-uri]
+=== &lt;uri&gt;
+
+
+
+This element is
+rendered as an HTML &lt;div&gt; containing the string "URI:" and
+an HTML &lt;a&gt; element with the "href" attribute set to the
+linked URI, CSS class of "url" (note that the value is "url", not "uri" as one might expect), and the contents
+set to the linked URI.
+
+
+....
+<div>URI:
+  <a href="http://www.example.com"
+     class="url">http://www.example.com</a>
+</div>
+....
+
+[#element-workgroup]
+=== &lt;workgroup&gt;
+
+This element does not add any direct output to HTML.
+
+[#element-xref]
+=== &lt;xref&gt;
+
+This element is rendered as an HTML &lt;a&gt; element containing an
+appropriate local link as the "href" attribute.  The value of the
+"href" attribute is taken from the "target" attribute,
+prepended by "#".  The &lt;a&gt; element generated will have
+class "xref".  The contents of the &lt;a&gt; element are
+the value of the "derivedContent" attribute. If the "format"
+attribute has the value "default", and the "target" attribute points
+to a &lt;reference&gt; or &lt;referencegroup&gt; element, then
+the generated &lt;a&gt; element is surrounded by square brackets
+in the output.
+
+....
+<a class="xref" href="#target">Table 2</a>
+....
+
+or
+
+....
+[<a class="xref" href="#RFC1234">RFC1234</a>]
+
+....
+
+[#element-svg]
+=== &lt;svg xmlns='http://www.w3.org/2000/svg'&gt;
+
+This element is rendered as part of the &lt;artwork&gt; element.
+The "xmlns='http://www.w3.org/2000/svg'" namespace declaration should
+be included, and the SVG should be serialized as well-formed XML,
+even for tags that would otherwise not need closing in HTML5.
+
+[#security-considerations]
+== Security Considerations
+
+Since RFCs are sometimes exchanged outside the normal Web sandboxing mechanism
+(such as using the "rsync" program to a mirror site) then loaded from a local file, more care must be taken
+with the HTML than is ordinary on the web. 
+
+[bibliography]
+== Normative References
+++++
+<reference anchor="RFC2397" target="https://www.rfc-editor.org/info/rfc2397">
+<front>
+<title>The "data" URL scheme</title>
+<author initials="L." surname="Masinter" fullname="L. Masinter">
+<organization/>
+</author>
+<date year="1998" month="August"/>
+<abstract>
+<t>
+A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK]
+</t>
+</abstract>
+</front>
+<seriesInfo name="RFC" value="2397"/>
+<seriesInfo name="DOI" value="10.17487/RFC2397"/>
+</reference>
+
+<reference anchor="RFC3629" target="https://www.rfc-editor.org/info/rfc3629">
+<front>
+<title>UTF-8, a transformation format of ISO 10646</title>
+<author initials="F." surname="Yergeau" fullname="F. Yergeau">
+<organization/>
+</author>
+<date year="2003" month="November"/>
+<abstract>
+<t>
+ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.
+</t>
+</abstract>
+</front>
+<seriesInfo name="STD" value="63"/>
+<seriesInfo name="RFC" value="3629"/>
+<seriesInfo name="DOI" value="10.17487/RFC3629"/>
+</reference>
+
+<reference anchor="RFC5646" target="https://www.rfc-editor.org/info/rfc5646">
+<front>
+<title>Tags for Identifying Languages</title>
+<author initials="A." surname="Phillips" fullname="A. Phillips" role="editor">
+<organization/>
+</author>
+<author initials="M." surname="Davis" fullname="M. Davis" role="editor">
+<organization/>
+</author>
+<date year="2009" month="September"/>
+<abstract>
+<t>
+This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
+</t>
+</abstract>
+</front>
+<seriesInfo name="BCP" value="47"/>
+<seriesInfo name="RFC" value="5646"/>
+<seriesInfo name="DOI" value="10.17487/RFC5646"/>
+</reference>
+
+<reference anchor="RFC7322" target="https://www.rfc-editor.org/info/rfc7322">
+<front>
+<title>RFC Style Guide</title>
+<author initials="H." surname="Flanagan" fullname="H. Flanagan">
+<organization/>
+</author>
+<author initials="S." surname="Ginoza" fullname="S. Ginoza">
+<organization/>
+</author>
+<date year="2014" month="September"/>
+<abstract>
+<t>
+This document describes the fundamental and unique style conventions and editorial policies currently in use for the RFC Series. It captures the RFC Editor's basic requirements and offers guidance regarding the style and structure of an RFC. Additional guidance is captured on a website that reflects the experimental nature of that guidance and prepares it for future inclusion in the RFC Style Guide. This document obsoletes RFC 2223, "Instructions to RFC Authors".
+</t>
+</abstract>
+</front>
+<seriesInfo name="RFC" value="7322"/>
+<seriesInfo name="DOI" value="10.17487/RFC7322"/>
+</reference>
+
+<reference  anchor='BCP14' target='http://www.rfc-editor.org/info/bcp14'>
+<front>
+<title>Key words for use in RFCs to Indicate Requirement Levels</title>
+<author initials='S.' surname='Bradner' fullname='S. Bradner'><organization /></author>
+<date year='1997' month='March' />
+<abstract>
+<t>In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t></abstract>
+</front>
+<seriesInfo name='BCP' value='14'/>
+<seriesInfo name='RFC' value='2119'/>
+</reference>
+
+
+<!--&I-D.iab-rfc-css; Companion Document-->
+
+
+<reference anchor='RFC7993' target='http://www.rfc-editor.org/info/rfc7993'>
+<front>
+<title>Cascading Style Sheets (CSS) Requirements for RFCs</title>
+
+<author initials='H' surname='Flanagan' fullname='Heather Flanagan'>
+<organization />
+</author>
+
+<date month='December' year='2016' />
+
+<abstract>
+<t>The HTML format for RFCs, described in [I-D.iab-html-rfc] assigns style guidance to an RFC Editor-defined Cascading Style Sheet (CSS). The embedded, default CSS as included by the RFC Editor is expected to take into account accessibility needs and be built along a responsive design model.  This document describes the requirements for the default CSS used by the RFC Editor.  The class names are based on the classes defined in draft-iab-html-rfc.  Discussion of this draft takes place on the rfc-interest mailing list (rfc-interest@rfc-editor.org), which has its home page at https://www.rfc-editor.org/mailman/listinfo/rfc-interest.</t></abstract>
+
+</front>
+
+<seriesInfo name='RFC' value='7993' />
+<seriesInfo name="DOI" value="10.17487/RFC7993"/>
+
+</reference>
+
+
+<!--&I-D.iab-xml2rfc; Companion Document-->
+
+<reference anchor='RFC7991' target='http://www.rfc-editor.org/info/rfc7991'>
+<front>
+<title>The "xml2rfc" Version 3 Vocabulary</title>
+
+<author initials='P' surname='Hoffman' fullname='Paul E. Hoffman'>
+<organization />
+</author>
+
+<date month='December' year='2016' />
+
+</front>
+
+<seriesInfo name='RFC' value='7991' />
+<seriesInfo name="DOI" value="10.17487/RFC7991"/>
+
+</reference>
+
+
+<!--&W3C.REC-html5-20141028; -->
+
+<reference anchor='W3C.REC-html5-20141028'
+target='http://www.w3.org/TR/2014/REC-html5-20141028'>
+<front>
+<title>HTML5</title>
+
+<author initials='I.' surname='Hickson' fullname='Ian Hickson'>
+<organization />
+</author>
+
+<author initials='R.' surname='Berjon' fullname='Robin Berjon'>
+<organization />
+</author>
+
+<author initials='S.' surname='Faulkner' fullname='Steve Faulkner'>
+<organization />
+</author>
+
+<author initials='T.' surname='Leithead' fullname='Travis Leithead'>
+<organization />
+</author>
+
+<author initials='E.' surname='Navara' fullname='Erika Doyle Navara'>
+<organization />
+</author>
+
+<author initials='T.' surname='O&#039;Connor' fullname='Theresa O&#039;Connor'>
+<organization />
+</author>
+
+<author initials='S.' surname='Pfeiffer' fullname='Silvia Pfeiffer'>
+<organization />
+</author>
+
+<date month='October' day='28' year='2014' />
+</front>
+
+<seriesInfo name='World Wide Web Consortium Recommendation' value='REC-html5-20141028' />
+<format type='HTML' target='http://www.w3.org/TR/2014/REC-html5-20141028' />
+</reference>
+
+
+<reference anchor="W3C.REC-CSS2-20110607" target="http://www.w3.org/TR/2011/REC-CSS2-20110607">
+<front>
+<title>Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification</title>
+<author initials="B." surname="Bos" fullname="Bert Bos">
+<organization/>
+</author>
+<author initials="T." surname="Celik" fullname="Tantek Celik">
+<organization/>
+</author>
+<author initials="I." surname="Hickson" fullname="Ian Hickson">
+<organization/>
+</author>
+<author initials="H." surname="Lie" fullname="Hakon Wium Lie">
+<organization/>
+</author>
+<date month="June" day="7" year="2011"/>
+</front>
+<seriesInfo name="World Wide Web Consortium Recommendation" value="REC-CSS2-20110607"/>
+<format type="HTML" target="http://www.w3.org/TR/2011/REC-CSS2-20110607"/>
+</reference>
+++++
+
+[bibliography]
+== Informative References
+++++
+<reference anchor="RFC-STYLE"
+	   target="https://www.rfc-editor.org/styleguide/">
+<front>
+<title>Style Guide</title>
+<author >
+<organization>RFC Editor</organization>
+</author>
+<date/>
+</front>
+</reference>
+
+
+<reference anchor="W3C.WD-css3-page-20130314" target="http://www.w3.org/TR/2013/WD-css3-page-20130314">
+<front>
+<title>CSS Paged Media Module Level 3</title>
+<author initials="M." surname="Grant" fullname="Melinda Grant">
+<organization/>
+</author>
+<author initials="E." surname="Etemad" fullname="Elika Etemad">
+<organization/>
+</author>
+<author initials="H." surname="Lie" fullname="Hakon Wium Lie">
+<organization/>
+</author>
+<author initials="S." surname="Sapin" fullname="Simon Sapin">
+<organization/>
+</author>
+<date month="March" day="14" year="2013"/>
+</front>
+<seriesInfo name="World Wide Web Consortium WD" value="WD-css3-page-20130314"/>
+<format type="HTML" target="http://www.w3.org/TR/2013/WD-css3-page-20130314"/>
+</reference>
+
+<reference anchor="HCARD" target="http://microformats.org/wiki/hcard">
+<front>
+<title>hCard 1.0</title>
+<author initials="T." surname = "Celik" fullname="Tantek Celik"/>
+<date year="2015"/>
+</front>
+</reference>
+
+
+
+
+<reference anchor="RFC6949" target="https://www.rfc-editor.org/info/rfc6949">
+<front>
+<title>
+RFC Series Format Requirements and Future Development
+</title>
+<author initials="H." surname="Flanagan" fullname="H. Flanagan">
+<organization/>
+</author>
+<author initials="N." surname="Brownlee" fullname="N. Brownlee">
+<organization/>
+</author>
+<date year="2013" month="May"/>
+<abstract>
+<t>
+This document describes the current requirements and requests for enhancements for the format of the canonical version of RFCs. Terms are defined to help clarify exactly which stages of document production are under discussion for format changes. The requirements described in this document will determine what changes will be made to RFC format. This document updates RFC 2223.
+</t>
+</abstract>
+</front>
+<seriesInfo name="RFC" value="6949"/>
+<seriesInfo name="DOI" value="10.17487/RFC6949"/>
+</reference>
+<!--&I-D.iab-rfcv3-preptool; Companion Doc-->
+
+
+
+<reference anchor='RFC7998' target='http://www.rfc-editor.org/info/rfc7998'>
+<front>
+<title>"xml2rfc" Version 3 Preparation Tool Description</title>
+
+<author initials='P' surname='Hoffman' fullname='Paul E. Hoffman'>
+<organization />
+</author>
+
+<author initials='J' surname='Hildebrand' fullname='Joe Hildebrand'>
+<organization />
+</author>
+
+<date month='December' year='2016' />
+
+<abstract>
+<t>This document describes some aspects of the "prep tool" that is expected to be created when the new RFC v3 specification is deployed.</t></abstract>
+
+</front>
+
+<seriesInfo name='RFC' value='7998' />
+<seriesInfo name="DOI" value="10.17487/RFC7998"/>
+
+</reference>
+
+
+<!--&I-D.iab-rfc-framework; Companion doc-->
+
+
+
+<reference anchor='RFC7990' target='http://www.rfc-editor.org/info/rfc7990'>
+<front>
+<title>RFC Format Framework</title>
+
+<author initials='H' surname='Flanagan' fullname='Heather Flanagan'>
+<organization />
+</author>
+
+<date month='December'  year='2016' />
+
+<abstract>
+<t>The canonical format for the RFC Series has been plain-text, ASCII-encoded for several decades.  After extensive community discussion and debate, the RFC Editor will be transitioning to XML as the canonical format using the XML2RFC version 3 vocabulary.  Different publication formats will be rendered from that base document.  These changes are intended to increase the usability of the RFC Series by offering documents that match the needs of a wider variety of stakeholders.  With these changes, however, comes an increase in complexity for authors, consumers, and the publisher of RFCs.  This document serves as the framework that describes the problems being solved and summarizes the many documents that capture the specific requirements for each aspect of the change in format.</t></abstract>
+
+</front>
+
+<seriesInfo name='RFC' value='7990' />
+<seriesInfo name="DOI" value="10.17487/RFC7990"/>
+<format type='TXT'
+target='http://www.ietf.org/internet-drafts/draft-iab-rfc-framework-06.txt' />
+</reference>
+++++
+
+:sectnums!:
+== IAB Members at the Time of Approval
+
+The IAB members at the time this memo was approved were (in alphabetical order):                                                       
+
+[spacing=compact]
+* Jari Arkko
+
+* Ralph Droms
+
+* Ted Hardie
+
+* Joe Hildebrand
+
+* Russ Housley
+
+* Lee Howard
+
+* Erik Nordmark
+
+* Robert Sparks
+
+* Andrew Sullivan
+
+* Dave Thaler
+
+* Martin Thomson
+
+* Brian Trammell
+
+* Suzanne Woolf
+
+[#appendix-a-acknowledgments]
+== Acknowledgments
+
+Heather Flanangan was an early coauthor of this document and helped its formation.
+The authors gratefully acknowledge the contributions of: Patrick Linskey and the
+members of the RFC Format Design Team (Nevil Brownlee (ISE), Tony Hansen,
+Ted Lemon, Julian Reschke, Adam Roach, Alice Russo, Robert Sparks
+	(Tools Team liaison), and
+Dave Thaler).
+