From e0095fdf9ece092a57746aa4313339b7191f9aff Mon Sep 17 00:00:00 2001 From: Kesara Rathnayake Date: Wed, 25 May 2022 09:09:41 +1200 Subject: [PATCH] test: Remove Python version specific test results (#780) * test: Remove Python version specific test results * test: Use the latest versions of GNU Make and GNU Diffutils --- .github/workflows/checks.yml | 7 +- Makefile | 28 +- .../valid/{docfile.py36.html => docfile.html} | 0 tests/valid/docfile.py37.html | 6403 -------- tests/valid/docfile.py38.html | 6403 -------- ...t.v3.py38.html => draft-miek-test.v3.html} | 2 +- tests/valid/draft-miek-test.v3.py36.html | 1977 --- tests/valid/draft-miek-test.v3.py37.html | 1977 --- ...te.v3.py36.html => draft-template.v3.html} | 2 +- tests/valid/draft-template.v3.py37.html | 922 -- tests/valid/draft-template.v3.py38.html | 922 -- ...v3.py38.html => draft-v3-features.v3.html} | 2 +- tests/valid/draft-v3-features.v3.py36.html | 5295 ------- tests/valid/draft-v3-features.v3.py37.html | 5295 ------- ...elements.v3.py37.html => elements.v3.html} | 2 +- tests/valid/elements.v3.py36.html | 1932 --- tests/valid/elements.v3.py38.html | 1932 --- tests/valid/indexes.pages.text | 12 +- tests/valid/indexes.prepped.xml | 8 +- tests/valid/indexes.text | 6 +- .../{indexes.v3.py37.html => indexes.v3.html} | 10 +- tests/valid/indexes.v3.py36.html | 507 - tests/valid/indexes.v3.py38.html | 507 - tests/valid/manpage.txt | 2 +- .../{no-toc.v3.py36.html => no-toc.v3.html} | 2 +- tests/valid/no-toc.v3.py37.html | 130 - tests/valid/no-toc.v3.py38.html | 130 - .../{rfc6787.v3.py38.html => rfc6787.v3.html} | 2 +- tests/valid/rfc6787.v3.py36.html | 13032 ---------------- tests/valid/rfc6787.v3.py37.html | 13032 ---------------- .../{rfc7911.v3.py37.html => rfc7911.v3.html} | 2 +- tests/valid/rfc7911.v3.py36.html | 546 - tests/valid/rfc7911.v3.py38.html | 546 - tests/valid/sourcecode.pages.text | 14 +- tests/valid/sourcecode.prepped.xml | 6 +- tests/valid/sourcecode.text | 6 +- ...cecode.v3.py37.html => sourcecode.v3.html} | 8 +- tests/valid/sourcecode.v3.py36.html | 290 - tests/valid/sourcecode.v3.py38.html | 290 - 39 files changed, 61 insertions(+), 62128 deletions(-) rename tests/valid/{docfile.py36.html => docfile.html} (100%) delete mode 100644 tests/valid/docfile.py37.html delete mode 100644 tests/valid/docfile.py38.html rename tests/valid/{draft-miek-test.v3.py38.html => draft-miek-test.v3.html} (99%) delete mode 100644 tests/valid/draft-miek-test.v3.py36.html delete mode 100644 tests/valid/draft-miek-test.v3.py37.html rename tests/valid/{draft-template.v3.py36.html => draft-template.v3.html} (99%) delete mode 100644 tests/valid/draft-template.v3.py37.html delete mode 100644 tests/valid/draft-template.v3.py38.html rename tests/valid/{draft-v3-features.v3.py38.html => draft-v3-features.v3.html} (99%) delete mode 100644 tests/valid/draft-v3-features.v3.py36.html delete mode 100644 tests/valid/draft-v3-features.v3.py37.html rename tests/valid/{elements.v3.py37.html => elements.v3.html} (99%) delete mode 100644 tests/valid/elements.v3.py36.html delete mode 100644 tests/valid/elements.v3.py38.html rename tests/valid/{indexes.v3.py37.html => indexes.v3.html} (98%) delete mode 100644 tests/valid/indexes.v3.py36.html delete mode 100644 tests/valid/indexes.v3.py38.html rename tests/valid/{no-toc.v3.py36.html => no-toc.v3.html} (99%) delete mode 100644 tests/valid/no-toc.v3.py37.html delete mode 100644 tests/valid/no-toc.v3.py38.html rename tests/valid/{rfc6787.v3.py38.html => rfc6787.v3.html} (99%) delete mode 100644 tests/valid/rfc6787.v3.py36.html delete mode 100644 tests/valid/rfc6787.v3.py37.html rename tests/valid/{rfc7911.v3.py37.html => rfc7911.v3.html} (99%) delete mode 100644 tests/valid/rfc7911.v3.py36.html delete mode 100644 tests/valid/rfc7911.v3.py38.html rename tests/valid/{sourcecode.v3.py37.html => sourcecode.v3.html} (97%) delete mode 100644 tests/valid/sourcecode.v3.py36.html delete mode 100644 tests/valid/sourcecode.v3.py38.html diff --git a/.github/workflows/checks.yml b/.github/workflows/checks.yml index e7c324b4f..5ef2ac3e9 100644 --- a/.github/workflows/checks.yml +++ b/.github/workflows/checks.yml @@ -147,7 +147,7 @@ jobs: - name: Install dependencies run: | - brew install pango libffi groff + brew install pango libffi groff make diffutils echo "Installing pip + wheel..." python -m pip install --upgrade pip wheel echo "Installing requirements.txt + test dependencies..." @@ -155,13 +155,16 @@ jobs: - name: Generate Valid Tests run: | + echo "/usr/local/opt/make/libexec/gnubin" >> $GITHUB_PATH make yestests || true cp -af tests/out/. tests/valid - name: Test with tox env: PLATFORM: macos-latest - run: tox + run: | + echo "/usr/local/opt/make/libexec/gnubin" >> $GITHUB_PATH + tox # tests-windows: # name: Unit Tests (Windows) diff --git a/Makefile b/Makefile index f6fbae8e2..4c883c27f 100644 --- a/Makefile +++ b/Makefile @@ -29,8 +29,6 @@ legacydate_regex = [ADFJMOS][a-u]* [123]*[0-9], [12][0-9][0-9][0-9]$$ generator_regex = name="generator" libversion_regex = \(pyflakes\|PyYAML\|requests\|setuptools\|six\|Weasyprint\) [0-9]\+\(\.[0-9]\+\)* -py = $(shell python3 -c 'import sys; print("py%s%s" %(sys.version_info.major,sys.version_info.minor))') - rfcxml= \ rfc6787.xml \ rfc7911.xml \ @@ -102,7 +100,7 @@ CHECKOUTPUT= \ %.rng: %.rnc trang $< $@ -%.tests: %.txt.test %.raw.txt.test %.nroff.test %.html.test %.exp.xml.test %.nroff.txt %.v2v3.xml.test %.v3add-xinclude.xml.test %.text.test %.pages.text.test %.v3.$(py).html.test %.prepped.xml.test %.plain.text +%.tests: %.txt.test %.raw.txt.test %.nroff.test %.html.test %.exp.xml.test %.nroff.txt %.v2v3.xml.test %.v3add-xinclude.xml.test %.text.test %.pages.text.test %.v3.html.test %.prepped.xml.test %.plain.text @echo " Diffing .nroff.txt against regular .txt" @doc=$(basename $@); diff -u -I '$(datetime_regex)' -I '$(version_regex)' -I '$(libversion_regex)' -I '$(date_regex)' $$doc.nroff.txt $$doc.txt || { echo 'Diff failed for $$doc.nroff.txt output'; exit 1; } @echo " Checking v3 validity" @@ -128,11 +126,11 @@ tests/out/%.v2v3.xml: tests/input/%.xml install tests/out/%.v3add-xinclude.xml: tests/input/draft-miek-test.v3.xml install @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --v2v3 --add-xinclude $< --out $@" -tests/out/%.prepped.xml: tests/input/%.xml tests/out/%.v3.$(py).html tests/out/%.text install +tests/out/%.prepped.xml: tests/input/%.xml tests/out/%.v3.html tests/out/%.text install @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --out $@ --prep $<" @echo " Checking generation of .html from prepped .xml" - @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --out $(basename $@).$(py).html --html --external-css --external-js --legacy-date-format --no-inline-version $@" 2> /dev/null || { err=$$?; echo "Error output when generating .html from prepped .xml"; exit $$err; } - @diff -u -I '$(datetime_regex)' -I '$(version_regex)' -I '$(date_regex)' -I '$(generator_regex)' -I 'rel="alternate"' tests/out/$(notdir $(basename $(basename $@))).v3.$(py).html $(basename $@).$(py).html || { echo "Diff failed for $(basename $@).$(py).html output (2)"; exit 1; } + @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --out $(basename $@).html --html --external-css --external-js --legacy-date-format --no-inline-version $@" 2> /dev/null || { err=$$?; echo "Error output when generating .html from prepped .xml"; exit $$err; } + @diff -u -I '$(datetime_regex)' -I '$(version_regex)' -I '$(date_regex)' -I '$(generator_regex)' -I 'rel="alternate"' tests/out/$(notdir $(basename $(basename $@))).v3.html $(basename $@).html || { echo "Diff failed for $(basename $@).html output (2)"; exit 1; } @echo " Checking generation of .text from prepped .xml" @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --out $(basename $@).text --text --no-pagination --external-css --external-js --legacy-date-format $@" 2> /dev/null || { err=$$?; echo "Error output when generating .text from prepped .xml"; exit $$err; } @diff -u -I '$(datetime_regex)' -I '$(version_regex)' -I '$(date_regex)' -I '$(generator_regex)' -I 'rel="alternate"' tests/out/$(notdir $(basename $(basename $@))).text $(basename $@).text || { echo "Diff failed for $(basename $@).text output (3)"; exit 1; } @@ -140,7 +138,7 @@ tests/out/%.prepped.xml: tests/input/%.xml tests/out/%.v3.$(py).html tests/out/% tests/out/docfile.xml: @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --doc --out $@" -tests/out/docfile.$(py).html: tests/out/docfile.xml +tests/out/docfile.html: tests/out/docfile.xml @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --html --external-css --external-js --no-inline-version --out $@ $<" tests/out/manpage.txt: @@ -158,7 +156,7 @@ tests/out/%.bom.text: tests/input/%.xml install tests/out/%.wip.text: tests/input/%.xml install @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --text --v3 --strict --id-is-work-in-progress $< --out $@" -tests/out/%.v3.$(py).html: tests/input/%.xml install +tests/out/%.v3.html: tests/input/%.xml install @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --html --v3 --external-css --external-js --strict --legacy-date-format --rfc-reference-base-url https://rfc-editor.org/rfc --id-reference-base-url https://datatracker.ietf.org/doc/html/ --no-inline-version $< --out $@" tests/out/%.pdf: tests/input/%.xml install @@ -190,7 +188,7 @@ tests/out/%.exp.xml: tests/input/%.xml install %.min.js: %.js bin/uglifycall $< -.PRECIOUS: tests/out/%.txt tests/out/%.raw.txt tests/out/%.nroff tests/out/%.nroff.txt tests/out/%.html tests/out/%.txt tests/out/%.exp.xml tests/out/%.v2v3.xml tests/out/%.prepped.xml tests/out/%.text tests/out/%.v3.$(py).html %.prepped.xml %.nroff.txt tests/out/%.plain.txt +.PRECIOUS: tests/out/%.txt tests/out/%.raw.txt tests/out/%.nroff tests/out/%.nroff.txt tests/out/%.html tests/out/%.txt tests/out/%.exp.xml tests/out/%.v2v3.xml tests/out/%.prepped.xml tests/out/%.text tests/out/%.v3.html %.prepped.xml %.nroff.txt tests/out/%.plain.txt # ---------------------------------------------------------------------- @@ -245,25 +243,25 @@ utf8test: cleantmp env/bin/python install @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --base tmp/ --raw --legacy --text --nroff --html --no-inline-version --exp --v2v3 --prep -q tests/input/utf8.xml" @doc=utf8 ; postnrofffix="cat" ; type=utf8; $(CHECKOUTPUT) -v3featuretest: tests/out/draft-v3-features.prepped.xml.test tests/out/draft-v3-features.text.test tests/out/draft-v3-features.v3.$(py).html.test +v3featuretest: tests/out/draft-v3-features.prepped.xml.test tests/out/draft-v3-features.text.test tests/out/draft-v3-features.v3.html.test dateshifttest: cleantmp install @PS4=" " /bin/bash -cx "xml2rfc --skip-config --allow-local-file-access --cache \"$${IETF_TEST_CACHE_PATH}\" --no-network --date 2013-02-01 --legacy --out tmp/draft-miek-test.dateshift.txt --text tests/input/draft-miek-test.xml" @diff -u -I '$(datetime_regex)' -I '$(version_regex)' -I '$(date_regex)' tests/valid/draft-miek-test.dateshift.txt tmp/draft-miek-test.dateshift.txt || { echo "Diff failed for draft-miek-test.dateshift.txt output"; exit 1; } -elementstest: install tests/out/elements.prepped.xml.test tests/out/elements.text.test tests/out/elements.pages.text.test tests/out/elements.v3.$(py).html.test +elementstest: install tests/out/elements.prepped.xml.test tests/out/elements.text.test tests/out/elements.pages.text.test tests/out/elements.v3.html.test -indextest: install tests/out/indexes.prepped.xml.test tests/out/indexes.text.test tests/out/indexes.pages.text.test tests/out/indexes.v3.$(py).html.test +indextest: install tests/out/indexes.prepped.xml.test tests/out/indexes.text.test tests/out/indexes.pages.text.test tests/out/indexes.v3.html.test -sourcecodetest: install tests/out/sourcecode.prepped.xml.test tests/out/sourcecode.text.test tests/out/sourcecode.pages.text.test tests/out/sourcecode.v3.$(py).html.test +sourcecodetest: install tests/out/sourcecode.prepped.xml.test tests/out/sourcecode.text.test tests/out/sourcecode.pages.text.test tests/out/sourcecode.v3.html.test -notoctest: install tests/out/no-toc.prepped.xml.test tests/out/no-toc.text.test tests/out/no-toc.pages.text.test tests/out/no-toc.v3.$(py).html.test +notoctest: install tests/out/no-toc.prepped.xml.test tests/out/no-toc.text.test tests/out/no-toc.pages.text.test tests/out/no-toc.v3.html.test bomtest: tests/out/elements.bom.text.test wiptest: tests/out/elements.wip.text.test -mantest: install cleantmp tests/out/manpage.txt.test tests/out/docfile.$(py).html.test +mantest: install cleantmp tests/out/manpage.txt.test tests/out/docfile.html.test @fgrep -q '***' tests/out/manpage.txt; res="$$?"; if [ "$$res" = "1" ]; then true; else echo "Missing documentation in manpage"; exit 1; fi manupdate: yes mantest diff --git a/tests/valid/docfile.py36.html b/tests/valid/docfile.html similarity index 100% rename from tests/valid/docfile.py36.html rename to tests/valid/docfile.html diff --git a/tests/valid/docfile.py37.html b/tests/valid/docfile.py37.html deleted file mode 100644 index a56eb1f1b..000000000 --- a/tests/valid/docfile.py37.html +++ /dev/null @@ -1,6403 +0,0 @@ - - - - - - -Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.7 - - - - - - - - - - - - - - - - - - - - - - -
Xml2rfc Vocabulary V3 SchemaMay 2022
xml2rfc(1)Informational[Page]
-
-
-
-
Workgroup:
-
xml2rfc(1)
-
Author:
-
-
-
xml2rfc(1)
-
-
-
-
-

Xml2rfc Vocabulary Version 3 Schema
xml2rfc release 3.12.7

-
-

Abstract

-

- This document provides information about the XML schema implemented in this release of xml2rfc, and the individual elements of that schema. The document is generated from the RNG schema file that is part of the xml2rfc distribution, so schema information in this document should always be in sync with the schema in actual use. The textual descriptions depend on manual updates in order to reflect the implementation.

-
-
-
- ▲

-Table of Contents -

- -
-
-
-

-1. Introduction -

-

- Most elements listed in this documentation will have a "Content schema" entry. This shows the permitted content for the element, expressed in RelaxNG Compact Notation [RNC]. For relatively trivial cases such as the ones in this document, the notation is quite straightforward, and resembles simple regular expressions, but with element names as atoms, instead of individual characters as atoms. A trailing '*' indicates zero or more instances; '+' indicates one or more, '?' indicates zero or one. '|' separates choices within a parenthesized group, and ',' separates entries in a sequence.

-

- Some attributes which are valid according to the schema are not listed in this documentation, mostly because they primarily are used by the preptool, and are not useful to document authors.

-

- Elements and attributes that have been introduced after the publication of the original schema version 3 specification, [RFC7991], have been marked with '(New)' in this document.

-

- For an introduction to the v3 schema, with suggestions on how to transition from v2, see [INTRO-TO-V3].

-

- The latest version of this documentation is available in HTML form at https://xml2rfc.ietf.org/xml2rfc-doc.

-

- This documentation applies to xml2rfc version 3.12.7.

-
-
-

-2. Schema Version 3 Elements -

-
-
-

-2.1. <abstract> -

-

- Contains the Abstract of the document. See [RFC7322] for more information on restrictions for the Abstract.

-

This element can be a child element of <front>.

-
-
Content schema:
-
( dl | ol | t | ul )+ -
-
-
-
-
-

-2.1.1. "anchor" Attribute -

-

Document-wide unique identifier for this <abstract> element.

-
-
-
-
-
-
-

-2.2. <address> -

-

- Provides address information for the author.

-

This element can be a child element of <author> and <contact>.

-
-
Content schema:
-
- postal?, phone?, email*, uri? -
-
-
-
-
-
-
-

-2.3. <annotation> -

-

- Provides additional prose augmenting a bibliographic reference. This text is intended to be shown after the rest of the generated reference text.

-

This element can be a child element of <reference>.

-
-
Content schema:
-
( text | bcp14 | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* -
-
-
-
-
-
-
-

-2.4. <area> -

-

- Provides information about the IETF area to which this document relates (currently not used when generating documents).

-

- The value ought to be either the full name or the abbreviation of one of the IETF areas as listed on http://www.ietf.org/iesg/area.html. A list of full names and abbreviations will be kept by the RFC Series Editor.

-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.5. <artset> (New) -

-

- This element allows for the support of multiple artwork formats, in order to provide suitable artwork for different output formats.

-

- When multiple <artwork> instances are provided within one <artset> element, the renderer will try to pick the <artwork> instance which is most appropriate for its current output format from the given alternatives.

-

- If more than one <artwork> element with the same "type" is found within an <artset> element, the renderer could select the first one, or possibly choose between the alternative instances based on the output format and some quality of the alternatives that make one more suitable than the others for that particular format, such as size, aspect ratio, etc.

-

This element can be a child element of <aside>, <blockquote>, <dd>, <figure>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
- artwork+ -
-
-
-
-
-

-2.5.1. "anchor" Attribute -

-

Document-wide unique identifier for this <artset> element.

-
-
-
-
-
-
-

-2.6. <artwork> -

-

- This element allows the inclusion of "artwork" in the document. <artwork> provides full control of horizontal whitespace and line breaks; thus, it is used for a variety of things, such as diagrams ("line art") and protocol unit diagrams. Tab characters (U+0009) inside of this element are prohibited.

-

- Alternatively, the "src" attribute allows referencing an external graphics file, such as a vector drawing in SVG or a bitmap graphic file, using a URI. In this case, the textual content acts as a fallback for output representations that do not support graphics; thus, it ought to contain either (1) a "line art" variant of the graphics or (2) prose that describes the included image in sufficient detail.

-

- In order to include alternative artwork expressions for different output formats, you should provide multiple <artwork> elements enclosed within an <artset>. The text renderer will prefer instances with type="ascii-art", while the HTML and PDF renderers will prefer instances with type="svg".

-

- In the v1 and v2 iterations of the schema, the <artwork> element was also used for source code and formal languages; in v3, this is now done with <sourcecode>.

-

- There are at least five ways to include SVG in artwork in Internet- Drafts:

-
    -
  • -

    Inline, by including all of the SVG in the content of the element, such as:

    -
    -
    <artwork type="svg"><svg xmlns="http://www.w3.org/2000/ svg...">
    -
    -
    • -
  • -

    Inline, but using XInclude (see Appendix B.1), such as:

    -
    -
    <artwork type="svg"><xi:include href=...>
    -
    -
    • -
  • -

    - As a data: URI, such as:

    -
    -
    -<artwork type="svg"
-src="data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww...">
-
    -
    -
    • -
  • -

    As a URI to an external entity, such as:

    -
    -
    <artwork type="svg" src="http://www.example.com/...">
    -
    -
    • -
  • -

    As a local file, such as:

    -
    -
    <artwork type="svg" src="diagram12.svg">
    -
    -
    • -
-

- The use of SVG in Internet-Drafts and RFCs is covered in much more detail in [RFC7996].

-

- The above methods for inclusion of SVG art can also be used for including text artwork, but using a data: URI is probably confusing for text artwork.

-

- Formatters that do pagination should attempt to keep artwork on a single page. This is to prevent artwork that is split across pages from looking like two separate pieces of artwork.

-

- See Section 5 for a description of how to deal with issues of using "&" and "<" characters in artwork.

-

This element can be a child element of <artset>, <aside>, <blockquote>, <dd>, <figure>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
( text* | svg ) -
-
-
-
-
-

-2.6.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-

- Controls whether the artwork appears left justified, centered, or right justified.

-
-
-
-
-

-2.6.2. "alt" Attribute -

-

- Alternative text description of the artwork (which is more than just a summary or caption). When the art comes from the "src" attribute and the format of that artwork supports alternate text, the alternative text comes from the text of the artwork itself, not from this attribute. The contents of this attribute are important to readers who are visually impaired, as well as those reading on devices that cannot show the artwork well, or at all.

-
-
-
-
-

-2.6.3. "anchor" Attribute -

-

Document-wide unique identifier for this <artwork> element.

-
-
- -
-
-

-2.6.5. "name" Attribute -

-

- A filename suitable for the contents (such as for extraction to a local file). This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the artwork). Note that the "name" attribute does not need to be unique for <artwork> elements in a document. If multiple <artwork> elements have the same "name" attribute, a processing tool might assume that the elements are all fragments of a single file, and the tool can collect those fragments for later processing.

-
-
-
-
-

-2.6.6. "src" Attribute -

-

- The URI reference of a graphics file [RFC3986], or the name of a file on the local disk. This can be a "data" URI [RFC2397] that contains the contents of the graphics file. Note that the inclusion of art with the "src" attribute depends on the capabilities of the processing tool reading the XML document. Tools need to be able to handle the file: URI, and they should be able to handle http: and https: URIs as well. The prep tool will be able to handle reading the "src" attribute.

-

- If no URI scheme is given in the attribute, the attribute is considered to be a local filename relative to the current directory. Processing tools must be careful to not accept dangerous values for the filename, particularly those that contain absolute references outside the current directory. Document creators should think hard before using relative URIs due to possible later problems if files move around on the disk. Also, documents should most likely use explicit URI schemes wherever possible.

-

- In some cases, the prep tool may remove the "src" attribute after processing its value. See [RFC7998] for a description of this.

-
-
-
-
-

-2.6.7. "type" Attribute -

-

- Specifies the format of the artwork. The value of this attribute is free text with certain values designated as preferred.

-

- The preferred values for <artwork> types are:

-
    -
  • ascii-art -
    • -
  • binary-art -
    • -
  • svg -
    • -
-

- Values that don't describe the format, such as "call-flow" or "hex-dump" were mentioned in [RFC7991], but are not supported here; they are instead candidates for use with another future attribute to describe the artwork content.

-

- The RFC Series Editor will maintain a complete list of the preferred values on the RFC Editor web site, and that list is expected to be updated over time. Thus, a consumer of v3 XML should not cause a failure when it encounters an unexpected type or no type is specified. The table will also indicate which type of art can appear in plain-text output (for example, type="svg" cannot).

-
-
- -
-
-
-
-

-2.7. <aside> -

-

- This element is a container for content that is semantically less important or tangential to the content that surrounds it.

-

This element can be a child element of <dd> and <section>.

-
-
Content schema:
-
( artset | artwork | blockquote | dl | figure | iref | ol | t | table | ul )* -
-
-
-
-
-

-2.7.1. "anchor" Attribute -

-

Document-wide unique identifier for this <aside> element.

-
-
-
-
-
-
-

-2.8. <author> -

-

- Provides information about a document's author. This is used both for the document itself (at the beginning of the document) and for referenced documents.

-

- The <author> elements contained within the document's <front> element are used to fill the boilerplate and also to generate the "Author's Address" section (see [RFC7322]).

-

- Note that an "author" can also be just an organization (by not specifying any of the "name" attributes, but adding the <organization> child element).

-

- Furthermore, the "role" attribute can be used to mark an author as "editor". This is reflected both on the front page and in the "Author's Address" section, as well as in bibliographic references. Note that this specification does not define a precise meaning for the term "editor".

-

This element can be a child element of <front> and <section>.

-
-
Content schema:
-
- organization?, address? -
-
-
-
-
-

-2.8.1. "anchor" Attribute (New) -

-

Document-wide unique identifier for this <author> element.

-
-
-
-
-

-2.8.2. "asciiFullname" Attribute -

-

- The Latin script equivalent of the author's full name.

-
-
-
-
-

-2.8.3. "asciiInitials" Attribute -

-

- The Latin script equivalent of the author's initials, to be used in conjunction with the separately specified asciiSurname.

-
-
-
-
-

-2.8.4. "asciiSurname" Attribute -

-

- The Latin script equivalent of the author's surname, to be used in conjunction with the separately specified asciiInitials.

-
-
-
-
-

-2.8.5. "fullname" Attribute -

-

- The full name (used in the automatically generated "Author's Address" section). Although this attribute is optional, if one or more of the "asciiFullname", "asciiInitials", or "asciiSurname" attributes does not have values, the "fullname" attribute is required.

-
-
-
-
-

-2.8.6. "initials" Attribute -

-

- An abbreviated variant of the given name(s), to be used in conjunction with the separately specified surname. It usually appears on the front page, in footers, and in references.

-

- Some processors will post-process the value -- for instance, when it only contains a single letter (in which case they might add a trailing dot). Relying on this kind of post-processing can lead to results varying across formatters and thus ought to be avoided.

-
-
-
-
-

-2.8.7. "role" Attribute -

-

- Specifies the role the author had in creating the document.

-
-
-
-
-

-2.8.8. "surname" Attribute -

-

- The author's surname, to be used in conjunction with the separately specified initials. It usually appears on the front page, in footers, and in references.

-
-
-
-
-
-
-

-2.9. <back> -

-

- Contains the "back" part of the document: the references and appendices. In <back>, <section> elements indicate appendices.

-

This element can be a child element of <rfc>.

-
-
Content schema:
-
- displayreference*, references*, section* -
-
-
-
-
-
-
-

-2.10. <bcp14> -

-

- Marks text that are phrases defined in [BCP14] such as "MUST", "SHOULD NOT", and so on. When shown in some of the output representations, the text in this element might be highlighted. The use of this element is optional.

-

- This element is only to be used around the actual phrase from BCP 14, not the full definition of a requirement. For example, it is correct to say "The packet <bcp14>MUST</bcp14> be dropped.", but it is not correct to say "<bcp14>The packet MUST be dropped.</bcp14>".

-

This element can be a child element of <annotation>, <blockquote>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, and <tt>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.11. <blockquote> -

-

- Specifies that a block of text is a quotation.

-

This element can be a child element of <aside>, <li>, and <section>.

-
-
Content schema:
-
( ( artset | artwork | dl | figure | ol | sourcecode | t | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )+ ) -
-
-
-
-
-

-2.11.1. "anchor" Attribute -

-

Document-wide unique identifier for this <blockquote> element.

-
-
-
-
-

-2.11.2. "cite" Attribute -

-

- The source of the citation. This must be a URI. If the "quotedFrom" attribute is given, this URI will be used by processing tools as the link for the text of that attribute.

-
-
-
-
-

-2.11.3. "quotedFrom" Attribute -

-

- Name of person or document the text in this element is quoted from. A formatter should render this as visible text at the end of the quotation.

-
-
-
-
-
-
-

-2.12. <boilerplate> -

-

- Holds the boilerplate text for the document. This element is filled in by the prep tool.

-

- This element contains <section> elements. Every <section> element in this element must have the "numbered" attribute set to "false".

-

This element can be a child element of <front>.

-
-
Content schema:
-
- section+ -
-
-
-
-
-
-
-

-2.13. <br> -

-

- Inserts a forced break. Use sparingly. In most situations, it's better to insert U+200B, ZERO WIDTH SPACE, in order to encourage line breaking at a point where it would otherwise not occur.

-

This element can be a child element of <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <t>, <td>, <th>, <title>, and <tt>.

-
-
Content schema:
-
empty -
-
-
-
-
-
-
-

-2.14. <city> -

-

- Gives the city name in a postal address.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.14.1. "ascii" Attribute -

-

- The ASCII equivalent of the <city> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.15. <cityarea> (New) -

-

- Where postal addresses use city subdivisions, these are mapped to the <cityarea> element. Korean addresses would use this for a city district, for instance. Countries known to use this element are Ascension Island, China, Iran, South Korea, and Thailand.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.15.1. "ascii" Attribute -

-

- The ASCII equivalent of the <cityarea> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.16. <code> -

-

- Gives the postal region code.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.16.1. "ascii" Attribute -

-

- The ASCII equivalent of the <code> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.17. <contact> (New) -

-

- Provides information about contributors. This element can be used inline within a <t>, and will be rendered with name only, similarly to how <author> is rendered in a <reference>, or it can be used as a direct child of <section>, where it will be rendered the same way as an author address block within the "Authors' Addresses" section.

-

- Note that a "contact" can also be just an organization (by not specifying any of the "name" attributes, but adding the <organization> child element).

-

This element can be a child element of <section> and <t>.

-
-
Content schema:
-
- organization?, address? -
-
-
-
-
-

-2.17.1. "anchor" Attribute -

-

Document-wide unique identifier for this <contact> element.

-
-
-
-
-

-2.17.2. "asciiFullname" Attribute -

-

- The Latin script equivalent of the contact's full name.

-
-
-
-
-

-2.17.3. "asciiInitials" Attribute -

-

- The Latin script equivalent of the contact's initials, to be used in conjunction with the separately specified asciiSurname.

-
-
-
-
-

-2.17.4. "asciiSurname" Attribute -

-

- The Latin script equivalent of the contact's surname, to be used in conjunction with the separately specified asciiInitials.

-
-
-
-
-

-2.17.5. "fullname" Attribute -

-

- The full name. Although this attribute is optional, if one or more of the "asciiFullname", "asciiInitials", or "asciiSurname" attributes does not have values, the "fullname" attribute is required.

-
-
-
-
-

-2.17.6. "initials" Attribute -

-

- An abbreviated variant of the given name(s), to be used in conjunction with the separately specified surname.

-
-
-
-
-

-2.17.7. "surname" Attribute -

-

- The contact's surname, to be used in conjunction with the separately specified initials.

-
-
-
-
-
-
-

-2.18. <country> -

-

- Specifies the country name in a postal address. All common and official country names should be recognized; in addition two- and three-letter country codes according to ISO 3166 are recognized.

-

- xml2rfc has a help option which will list all names and country codes it recognizes as valid country names: xml2rfc --country-help .

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.18.1. "ascii" Attribute -

-

- The ASCII equivalent of the <country> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.19. <cref> -

-

- Represents a comment.

-

- Comments can be used in a document while it is work in progress. They might appear either inline and visually highlighted, at the end of the document, or not at all, depending on the formatting tool.

-

This element can be a child element of <annotation>, <blockquote>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, .

-
-
Content schema:
-
( text | br | em | eref | strong | sub | sup | tt | xref )* -
-
-
-
-
-

-2.19.1. "anchor" Attribute -

-

Document-wide unique identifier for this <cref> element.

-
-
-
-
-

-2.19.2. "display" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Suggests whether or not the comment should be displayed by formatting tools. This might be set to "false" if you want to keep a comment in a document after the contents of the comment have already been dealt with.

-
-
-
-
-

-2.19.3. "source" Attribute -

-

- Holds the "source" of a comment, such as the name or the initials of the person who made the comment.

-
-
-
-
-
-
-

-2.20. <date> -

-

- Provides information about the publication date. This element is used for two cases: the boilerplate of the document being produced, and inside bibliographic references that use the <front> element.

-
-
Bibliographic references:
-
-

(New) In order to be able to specify fuzzy dates, such as "2002-2003", "Second quarter 2010", etc., the date element is now permitted to have text content in addition to the "year", "month", and "day" attributes. If there is only text content, it will be rendered as is. If there is both text content and date components, both will be rendered, with the expanded date components in parentheses.

-
-
-
Boilerplate for Internet-Drafts and RFCs:
-
-

This element defines the date of publication for the current document (Internet-Draft or RFC). When producing Internet-Drafts, the prep tool uses this date to compute the expiration date (see [IDGUIDE]). When one or more of "year", "month", or "day" are left out, the prep tool will attempt to use the current system date if the attributes that are present are consistent with that date.

-

In dates in <rfc> elements, the month must be a number or a month in English. The prep tool will silently change text month names to numbers. Similarly, the year must be a four-digit number.

-

When the prep tool is used to create Internet-Drafts, it will warn if the draft has a <date> element in the boilerplate for itself that is more than 3 days away from today. To avoid this problem, authors might simply not include a <date> element in the boilerplate.

-
-
-
-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.20.1. "day" Attribute -

-

- The day of publication.

-
-
-
-
-

-2.20.2. "month" Attribute -

-

- The month of publication.

-
-
-
-
-

-2.20.3. "year" Attribute -

-

- The year of publication.

-
-
-
-
-
-
-

-2.21. <dd> -

-

- The definition part of an entry in a definition list.

-

This element can be a child element of <dl>.

-
-
Content schema:
-
( ( artset | artwork | aside | dl | figure | ol | sourcecode | t | table | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )+ ) -
-
-
-
-
-

-2.21.1. "anchor" Attribute -

-

Document-wide unique identifier for this <dd> element.

-
-
-
-
-
-
-

-2.22. <displayreference> -

-

- This element gives a mapping between the anchor of a reference and a name that will be displayed instead. This allows authors to display more mnemonic anchor names for automatically included references. The mapping in this element only applies to <xref> elements whose format is "default". For example, if the reference uses the anchor "RFC6949", the following would cause that anchor in the body of displayed documents to be "RFC-dev":

-
-
<displayreference target="RFC6949" to="RFC-dev"/>
-
-

- If a reference section is sorted, this element changes the sort order.

-

This element can be a child element of <back>.

-
-
-

-2.22.1. "target" Attribute (Required) -

-

- This attribute must be the name of an anchor in a <reference> or <referencegroup> element.

-
-
-
-
-

-2.22.2. "to" Attribute (Required) -

-

- This attribute is a name that will be displayed as the anchor instead of the anchor that is given in the <reference> element. The string given must start with one of the following characters: 0-9, a-z, or A-Z. The other characters in the string must be 0-9, a-z, A-Z, "-", ".", or "_".

-
-
-
-
-
-
-

-2.23. <dl> -

-

- A definition list. Each entry has a pair of elements: a term (<dt>) and a definition (<dd>). (This is slightly different and simpler than the model used in HTML, which allows for multiple terms for a single definition.)

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
( dt, dd )+ -
-
-
-
-
-

-2.23.1. "anchor" Attribute -

-

Document-wide unique identifier for this <dl> element.

-
-
-
-
-

-2.23.2. "indent" Attribute (New) -

-
-
Default value:
-
"3" -
-
-
-

- Indicates the indentation to be used for the rendering of the second and following lines of the item (the first line starts with the term, and is not indented). The indentation amount is interpreted as characters when rendering plain-text documents, and en-space units when rendering in formats that have richer typographic support such as HTML or PDF. One en-space is assumed to be the length of 0.5 em-space in CSS units.

-
-
-
-
-

-2.23.3. "newline" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- The "newline" attribute defines whether or not the term appears on the same line as the definition. newline="false" indicates that the term is to the left of the definition, while newline="true" indicates that the term will be on a separate line.

-
-
-
-
-

-2.23.4. "spacing" Attribute -

-
-
Possible values:
-
( "normal" | "compact" ) -
-
-
Default value:
-
"normal" -
-
-
-

- Defines whether or not there is a blank line between entries. spacing="normal" indicates a single blank line, while spacing="compact" indicates no blank line between entries.

-
-
-
-
-
-
-

-2.24. <dt> -

-

- The term being defined in a definition list.

-

This element can be a child element of <dl>.

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-

-2.24.1. "anchor" Attribute -

-

Document-wide unique identifier for this <dt> element.

-
-
-
-
-
-
-

-2.25. <em> -

-

- Indicates text that is semantically emphasized. In HTML and PDF rendering, text enclosed within this element will be displayed as italic after processing; in text rendering it will be preceded and folled by an underline character. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | br | cref | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.26. <email> -

-

- Provides an email address.

-

- The value is expected to be the addr-spec defined in Section 2 of [RFC6068].

-

- (New) In [RFC7991], only zero or one instance of this element was permitted in an address. In the current schemal, now multiple email addresses are permitted.

-

This element can be a child element of <address>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.26.1. "ascii" Attribute -

-

- The ASCII equivalent of the author's email address. This is only used if the email address has any internationalized components.

-
-
-
-
-
-
-

-2.27. <eref> -

-

- Represents an "external" link (as specified in the "target" attribute). This is useful for embedding URIs in the body of a document.

-

- If the <eref> element has non-empty text content, the content is used as the displayed text that is linked. Otherwise, the value of the "target" attribute is used as the displayed text.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, .

-
-
Content schema:
-
text -
-
-
-
-
-

-2.27.1. "brackets" Attribute (New) -

-
-
Possible values:
-
( "none" | "angle" ) -
-
-
Default value:
-
"none" -
-
-
-

- Determines the type of brackets that an eref will be rendered with. "angle" will render with angle brackets, and "none" will render with no brackets in HTML and PDF, and with parentheses by the text renderer.

-
-
-
-
-

-2.27.2. "target" Attribute (Required) -

-

- URI of the link target [RFC3986]. This must begin with a scheme name (such as "https://") and thus not be relative to the URL of the current document.

-
-
-
-
-
-
-

-2.28. <extaddr> (New) -

-

- Extra address information. This element can be used for address parts more specific than a street, for instance apartment numbers, suite numbers, building parts, etc.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.28.1. "ascii" Attribute -

-

- The ASCII equivalent of the <extaddr> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.29. <figure> -

-

- Contains a figure with a caption with the figure number. If the element contains a <name> element, the caption will also show that name.

-

This element can be a child element of <aside>, <blockquote>, <dd>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
- name?, iref*, ( artset | artwork | sourcecode )+ -
-
-
-
-
-

-2.29.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-
-
- -
-
-

-2.29.3. "anchor" Attribute -

-

Document-wide unique identifier for this <figure> element.

-
-
- - -
-
-

-2.29.6. "suppress-title" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-
-
-
-
-

-2.29.7. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
- -
-
-
-
-

-2.30. <front> -

-

- Represents the "front matter" metadata (such as author information), the Abstract, and additional notes.

-

- A <front> element may have more than one <seriesInfo> element. Each should contain a "name" attribute with the series name and a "value" attribute with the series number; other uses of <front><seriesInfo> described in [RFC7991] are deprecated.

-

This element can be a child element of <reference> and <rfc>.

-
-
Content schema:
-
- title, seriesInfo*, author+, date?, area*, workgroup*, keyword*, abstract?, note*, boilerplate?, toc? -
-
-
-
-
-
-
-

-2.31. <iref> -

-

- Provides terms for the document's index.

-

- Index entries can be either regular entries (when just the "item" attribute is given) or nested entries (by specifying "subitem" as well), grouped under a regular entry.

-

- Index entries generally refer to the exact place where the <iref> element occurred. An exception is the occurrence as a child element of <section>, in which case the whole section is considered to be relevant for that index entry. In some formats, index entries of this type might be displayed as ranges.

-

- When the prep tool is creating index content, it collects the items in a case-sensitive fashion for both the item and subitem level.

-

This element can be a child element of <annotation>, <aside>, <blockquote>, <dd>, <dt>, <em>, <figure>, <li>, <name>, <section>, <strong>, <sub>, <sup>, <t>, <table>, <td>, <th>, <tt>, .

-
-
Content schema:
-
empty -
-
-
-
-
-

-2.31.1. "item" Attribute (Required) -

-

- The item to include.

-
-
-
-
-

-2.31.2. "primary" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Setting this to "true" declares the occurrence as "primary", which might cause it to be highlighted in the index. There is no restriction on the number of occurrences that can be "primary".

-
-
-
-
-

-2.31.3. "subitem" Attribute -

-

- The subitem to include.

-
-
-
-
-
-
-

-2.32. <keyword> -

-

- Specifies a keyword applicable to the document.

-

- Note that each element should only contain a single keyword; for multiple keywords, the element can simply be repeated.

-

- Keywords are used both in the RFC Index and in the metadata of generated document representations. They are not reflected in the HTML, PDF, or text rendering of the document.

-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.33. <li> -

-

- A list element, used in <ol> and <ul>.

-

This element can be a child element of <ol> and <ul>.

-
-
Content schema:
-
( ( artset | artwork | blockquote | dl | figure | ol | sourcecode | t | table | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )+ ) -
-
-
-
-
-

-2.33.1. "anchor" Attribute -

-

Document-wide unique identifier for this <li> element.

-
-
-
-
- -
-
-

-2.35. <middle> -

-

- Represents the main content of the document.

-

This element can be a child element of <rfc>.

-
-
Content schema:
-
- section+ -
-
-
-
-
-
-
-

-2.36. <name> -

-

- The name of the containing (parent) element, for instance the section name. This name can include inline markup (for example, including references or making some characters use a fixed-width font).

-

This element can be a child element of <figure>, <note>, <references>, <section>, <table>, .

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.37. <note> -

-

- Creates an unnumbered, titled block of text that appears after the Abstract.

-

- It is usually used for additional information to reviewers (Working Group information, mailing list, ...) or for additional publication information such as "IESG Notes".

-

This element can be a child element of <front>.

-
-
Content schema:
-
- name?, ( dl | ol | t | ul )+ -
-
-
-
-
-

-2.37.1. "removeInRFC" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- If set to "true", this note is marked in the prep tool with text indicating that it should be removed before the document is published as an RFC. That text will be "This note is to be removed before publishing as an RFC."

-
-
-
-
-

-2.37.2. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
-
-
-
-
-

-2.38. <ol> -

-

- An ordered list. The labels on the items will be either a number or a letter, depending on the value of the style attribute.

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
- li+ -
-
-
-
-
-

-2.38.1. "anchor" Attribute -

-

Document-wide unique identifier for this <ol> element.

-
-
-
-
-

-2.38.2. "group" Attribute -

-

- When the prep tool sees an <ol> element with a "group" attribute that has already been seen, it continues the numbering of the list from where the previous list with the same group name left off. If an <ol> element has both a "group" attribute and a "start" attribute, the group's numbering is reset to the given start value.

-
-
-
-
-

-2.38.3. "indent" Attribute (New) -

-
-
Possible values:
-
( text | "adaptive" ) -
-
-
Default value:
-
"adaptive" -
-
-
-

- The indentation of the list elements relative to the start of the list item number. With indent='adaptive', the width of the widest list item number will determine the indentation. With a numeric value, that value will be used to determine the amount of indentation. The indentation amount is interpreted as characters when rendering plain-text documents, and en-space units when rendering in formats that have richer typographic support such as HTML or PDF. One en-space is assumed to be the length of 0.5 em-space in CSS units. Only non-negative integer amounts of indentation are supported.

-
-
-
-
-

-2.38.4. "spacing" Attribute -

-
-
Possible values:
-
( "normal" | "compact" ) -
-
-
Default value:
-
"normal" -
-
-
-

- Defines whether or not there is a blank line between entries. spacing="normal" indicates a single blank line, while spacing="compact" indicates no blank line between entries.

-
-
-
-
-

-2.38.5. "start" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The ordinal value at which to start the list. This defaults to "1" and must be an integer of value 0 or greater.

-
-
-
-
-

-2.38.6. "type" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The type of the labels on list items. If the length of the type value is 1, the meaning is the same as it is for HTML:

-
-
a
-
- Lowercase letters (a, b, c, ...) -
-
-
-
-
A
-
- Uppercase letters (A, B, C, ...) -
-
-
-
-
1
-
- Decimal numbers (1, 2, 3, ...) -
-
-
-
-
i
-
- Lowercase Roman numerals (i, ii, iii, ...) -
-
-
-
-
I
-
- Uppercase Roman numerals (I, II, III, ...) -
-
-
-

- For types "a" and "A", after the 26th entry, the numbering starts at "aa"/"AA", then "ab"/"AB", and so on.

-

- If the length of the type value is greater than 1, the value must contain a percent-encoded indicator and other text. The value is a free-form text that allows counter values to be inserted using a "percent-letter" format. For instance, "[REQ%d]" generates labels of the form "[REQ1]", where "%d" inserts the item number as a decimal number.

-

- The following formats are supported:

-
-
%c
-
- Lowercase letters (a, b, c, ...) -
-
-
-
-
%C
-
- Uppercase letters (A, B, C, ...) -
-
-
-
-
%d
-
- Decimal numbers (1, 2, 3, ...) -
-
-
-
-
%i
-
- Lowercase Roman numerals (i, ii, iii, ...) -
-
-
-
-
%I
-
- Uppercase Roman numerals (I, II, III, ...) -
-
-
-
-
%p
-
- The list counter of a list item in a parent list (see more below) -
-
-
-
-
%%
-
- Represents a percent sign -
-
-
-

- Other formats are reserved for future use. Only one percent encoding other than "%%" and "%p" is allowed in a type string.

-

- It is an error for the type string to be empty. For bulleted lists, use the <ul> element. For lists that have neither bullets nor numbers, use the <ul> element with the 'empty="true"' attribute.

-

- '%p' may be used in nested ordered lists, where it represents the item number of the parent list item. This lets you say for instance:

-
-
-<ol>
-  <li>List item one</li>
-  <li>
-    <t>Nested list:</t>
-    <ol type='%p%d'>
-      <li>Sublist item 2.1</li>
-      <li>Sublist item 2.2</li>
-    </ol>
-  </li>
-</ol>
-
-
-

which is rendered as:

-
    -
  1. List item one -
    2. -
  2. -

    Nested list

    -
    -
    2.1
    -
    Sublist item 2.1 -
    -
    -
    2.2
    -
    Sublist item 2.2 -
    -
    -
    -
    3. -
-

- Without the '%p' format specifier, you would have to explicitly insert the counter number of the parent item, which could easily result in mismatched numbering if parent list intems were inserted or removed during document editing.

-
-
-
-
-
-
-

-2.39. <organization> -

-

- Specifies the affiliation [RFC7322] of an author.

-

- This information appears both in the "Author's Address" section and on the front page (see [RFC7322] for more information). If the value is long, an abbreviated variant can be specified in the "abbrev" attribute.

-

This element can be a child element of <author> and <contact>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.39.1. "abbrev" Attribute -

-

- Abbreviated variant of the organization name.

-
-
-
-
-

-2.39.2. "ascii" Attribute -

-

- The ASCII equivalent of the <organization> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-

-2.39.3. "asciiAbbrev" Attribute (New) -

-

- The ASCII equivalent of the abbreviated variant of the organization's name.

-
-
-
-
-

-2.39.4. "showOnFrontPage" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Turns off listing of organization with author name on the first document page.

-
-
-
-
-
-
-

-2.40. <phone> -

-

- Represents a phone number.

-

- The value is expected to be the scheme-specific part of a "tel" URI (and so does not include the prefix "tel:"), using the "global-number-digits" syntax. See Section 3 of [RFC3966] for details.

-

This element can be a child element of <address>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.41. <pobox> (New) -

-

- Represents a post office box number.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.41.1. "ascii" Attribute -

-

- The ASCII equivalent of the <pobox> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.42. <postal> -

-

- Contains optional child elements providing postal information. These elements will be displayed in an order that is specific to formatters. A postal address can contain only a set of <street>, <city>, <region>, <code>, and <country> elements, or only an ordered set of <postalLine> elements, but not both.

-

This element can be a child element of <address>.

-
-
Content schema:
-
( ( city | cityarea | code | country | extaddr | pobox | region | sortingcode | street )* | postalLine+ ) -
-
-
-
-
-
-
-

-2.43. <postalLine> -

-

- Represents one line of a postal address. When more than one <postalLine> is given, the prep tool emits them in the order given.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.43.1. "ascii" Attribute -

-

- The ASCII equivalent of the <postalLine> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.44. <refcontent> -

-

- Text that should appear between the title and the date of a reference. The purpose of this element is to obviate the need for abuse of <seriesInfo> in order to add such text.

-

- For example:

-

- <reference anchor="April1"> <front> <title>On Being A Fool</title> <author initials="K." surname="Phunny" fullname="Knot Phunny"/> <date year="2000" month="April"/> </front> <refcontent>Self-published pamphlet</refcontent> </reference>

-

- would render as:

-

- [April1] Phunny, K., "On Being A Fool", Self-published pamphlet, April 2000.

-

This element can be a child element of <reference>.

-
-
Content schema:
-
( text | bcp14 | em | strong | sub | sup | tt )* -
-
-
-
-
-
-
-

-2.45. <reference> -

-

- Represents a bibliographic reference.

-

This element can be a child element of <referencegroup> and <references>.

-
-
Content schema:
-
- stream?, front, ( annotation | refcontent | seriesInfo )* -
-
-
-
-
-

-2.45.1. "anchor" Attribute (Required) -

-

- Document-wide unique identifier for this <reference>. Usually, this will be used both to "label" the reference in the "References" section and as an identifier in links to this reference entry; but see <displayreference (Section 2.22)> for how to change this.

-
-
-
-
-

-2.45.2. "quote-title" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
-

- Specifies whether or not the title in the reference should be quoted. This can be used to prevent quoting, such as on errata.

-
-
-
-
-

-2.45.3. "target" Attribute -

-

- Holds the URI for the reference.

-
-
-
-
-
-
-

-2.46. <referencegroup> -

-

- Represents a list of bibliographic references that will be represented as a single reference. This is most often used to reference STDs and BCPs, where a single reference (such as "BCP 9") may encompass more than one RFC.

-

This element can be a child element of <references>.

-
-
Content schema:
-
- reference+ -
-
-
-
-
-

-2.46.1. "anchor" Attribute (Required) -

-

- Document-wide unique identifier for this <referencegroup>. Usually, this will be used both to "label" the reference group in the "References" section and as an identifier in links to this reference entry; but see <displayreference (Section 2.22)> for how to change this.

-
-
-
-
-

-2.46.2. "target" Attribute (New) -

-

- (New) Holds an URI for the reference group, analogous to the "target" attribute of <reference>. Useful for a STD which consists of multiple RFCs with their own URLs, but also has its own unique URL.

-
-
-
-
-
-
-

-2.47. <references> -

-

- Contains a set of bibliographic references.

-

- In the early days of the RFC Series, there was only one "References" section per RFC. This convention was later changed to group references into two sets, "Normative" and "Informative", as described in [RFC7322]. This vocabulary supports the split with the <name> child element. In general, the title should be either "Normative References" or "Informative References".

-

- The recommended way to include references to RFCs and Internet-Drafts is to use the standard XML XInclude mechanism. Here is an example:

-
-
-<references>
-<name>Normative References</name>
-<!--RTP-->
-<xi:include href=
-"https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml"/>
-<!--SIP-->
-<xi:include href=
-"https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml"/>
-</references>
-
-
-

This element can be a child element of <back> and <references>.

-
-
Content schema:
-
- name?, ( references+ | ( reference | referencegroup )* ) -
-
-
-
-
-

-2.47.1. "anchor" Attribute -

-

- An optional user-supplied identifier for this set of references.

-
-
-
-
-

-2.47.2. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
-
-
-
-
-

-2.48. <region> -

-

- Provides the region name in a postal address.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.48.1. "ascii" Attribute -

-

- The ASCII equivalent of the <region> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.49. <rfc> -

-

- This is the root element of the xml2rfc vocabulary.

-
-
Content schema:
-
- link*, front, middle, back? -
-
-
-
-
-

-2.49.1. "category" Attribute -

-
-
Possible values:
-
( "std" | "bcp" | "exp" | "info" | "historic" ) -
-
-
-

- Document category

-

- For RFCs, the "category" attribute (Section 2.33.1) determines the "maturity level" (see Section 4 of [RFC2026]). The allowed values are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for "Historic".

-

- For Internet-Drafts, the "category" attribute is not needed; when supplied, it will appear as "Intended Status". Supplying this information can be useful to reviewers.

-
-
-
-
-

-2.49.2. "consensus" Attribute -

-
-
Possible values:
-
( "no" | "yes" | "false" | "true" ) -
-
-
Default value:
-
"false" -
-
-
-

- Affects the generated boilerplate. Note that the values of "no" and "yes" are deprecated and are replaced by "false" and "true".

-

- See [RFC7841] for more information.

-
-
-
-
-

-2.49.3. "docName" Attribute -

-

- Indicates the draft name (including revision number) for a draft, or the draft from which an RFC derived, for an RFC. Used to insert the <link rel="prev" href="..."> element that points to the precursor of the RFC, in accordance with the intentions of Section 5.6.3 of [RFC7998].

-
-
-
-
-

-2.49.4. "indexInclude" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Specifies whether or not a formatter is requested to include an index in generated files. If the source file has no <iref> elements, an index is never generated. This option is useful for generating documents where the source document has <iref> elements but the author no longer wants an index.

-
-
-
-
-

-2.49.5. "ipr" Attribute -

-

- Represents the Intellectual Property status of the document.

-

- If the attribute is set to the empty string: <tt>ipr=''</tt>, it is assumed that this is not a regular IETF/IRTF/IAB/ISE document, and the document header content is reduced. This is considered a feature by a few other standards organisations that have used xml2rfc to format their standards documents.

-
-
-
-
-

-2.49.6. "iprExtract" Attribute -

-

- Identifies a single section within the document for which extraction "as is" is explicitly allowed (only relevant for historic values of the "ipr).

-
-
-
-
-

-2.49.7. "number" Attribute -

-

- Used to determine wheher to produce an RFC or an Internet-Draft.

-
-
-
-
-

-2.49.8. "obsoletes" Attribute -

-

- A comma-separated list of RFC numbers or Internet-Draft names.

-

- The prep tool will parse the attribute value so that incorrect references can be detected.

-
-
-
-
-

-2.49.9. "prepTime" Attribute -

-

- The date that the XML was processed by a prep tool. This is included in the XML file just before it is saved to disk. The value is formatted using the "date-time" format defined in Section 5.6 of [RFC3339]. The "time-offset" should be "Z".

-
-
-
-
-

-2.49.10. "seriesNo" Attribute -

-

- Deprecated; instead, use the "value" in <seriesInfo>.

-
-
-
-
-

-2.49.11. "sortRefs" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Specifies whether or not the prep tool will sort the references in each reference section.

-
-
-
-
-

-2.49.12. "submissionType" Attribute -

-
-
Possible values:
-
( "IETF" | "IAB" | "IRTF" | "independent" ) -
-
-
Default value:
-
"IETF" -
-
-
-

- The document stream, as described in [RFC7841]. (The RFC Series Editor may change the list of allowed values in the future.)

-
-
-
-
-

-2.49.13. "symRefs" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Specifies whether or not a formatter is requested to use symbolic references (such as "RFC2119"). If the value for this is "false", the references come out as numbers (such as "[3]").

-
-
-
-
-

-2.49.14. "tocDepth" Attribute -

-
-
Default value:
-
"3" -
-
-
-

- Specifies the number of levels of headings that a formatter is requested to include in the table of contents.

-
-
-
-
-

-2.49.15. "tocInclude" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Specifies whether or not a formatter is requested to include a table of contents in generated files.

-
-
-
-
-

-2.49.16. "updates" Attribute -

-

- A comma-separated list of RFC numbers or Internet-Draft names.

-

- The prep tool will parse the attribute value so that incorrect references can be detected.

-
-
-
-
-

-2.49.17. "version" Attribute -

-

- Specifies the version of xml2rfc syntax used in this document. The only expected value (for now) is "3".

-
-
-
-
-
-
-

-2.50. <section> -

-

- Represents a section (when inside a <middle> element) or an appendix (when inside a <back> element).

-

- Subsections are created by nesting <section> elements inside <section> elements. Sections are allowed to be empty.

-

This element can be a child element of <back>, <boilerplate>, <middle>, <section>, and <toc>.

-
-
Content schema:
-
- name?, ( artset | artwork | aside | author | blockquote | contact | dl | figure | iref | ol | sourcecode | t | table | ul )*, section* -
-
-
-
-
-

-2.50.1. "anchor" Attribute -

-

Document-wide unique identifier for this <section> element.

-
-
-
-
-

-2.50.2. "numbered" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- If set to "false", the formatter is requested to not display a section number. The prep tool will verify that such a section is not followed by a numbered section in this part of the document. Descendant sections of unnumbered sections are unnumbered by definition. (New) Both top-level <section>s and other <section>s may have numbered='false'.

-
-
-
-
-

-2.50.3. "removeInRFC" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- If set to "true", this section is marked in the prep tool with text indicating that it should be removed before the document is published as an RFC. That text will be "This section is to be removed before publishing as an RFC."

-
-
-
-
-

-2.50.4. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
-
-
-

-2.50.5. "toc" Attribute -

-
-
Possible values:
-
( "include" | "exclude" | "default" ) -
-
-
Default value:
-
"default" -
-
-
-

- Indicates to a formatter whether or not the section is to be included in a table of contents, if such a table of contents is produced. This only takes effect if the level of the section would have appeared in the table of contents based on the "tocDepth" attribute of the <rfc> element, and of course only if the table of contents is being created based on the "tocInclude" attribute of the <rfc> element. If this is set to "exclude", any section below this one will be excluded as well. The "default" value indicates inclusion of the section if it would be included by the tocDepth attribute of the <rfc> element.

-
-
-
-
-
-
-

-2.51. <seriesInfo> -

-

- Specifies the document series in which this document appears, and also specifies an identifier within that series.

-

- A processing tool determines whether it is working on an RFC or an Internet-Draft by inspecting the "name" attribute of a <seriesInfo> element inside the <front> element inside the <rfc> element, looking for "RFC" or "Internet-Draft". (Specifying neither value in any of the <seriesInfo> elements can be useful for producing other types of documents but is out of scope for this specification.)

-

- It is invalid to have multiple <seriesInfo> elements inside the same <front> element containing the same "name" value. Some combinations of <seriesInfo> "name" attribute values make no sense, such as having both <seriesInfo name="rfc"/> and <seriesInfo name="Internet-Draft"/> in the same <front> element.

-

This element can be a child element of <front> and <reference>.

-
-
Content schema:
-
empty -
-
-
-
-
-

-2.51.1. "asciiName" Attribute -

-

- The ASCII equivalent of the name field.

-
-
-
-
-

-2.51.2. "asciiValue" Attribute -

-

- The ASCII equivalent of the value field.

-
-
-
-
-

-2.51.3. "name" Attribute (Required) -

-

- The name of the series. Some values in use by the IETF community are "RFC", "Internet-Draft", and "DOI", but other names such as "ISO", "W3C" for exist for other standardisation organisations.

-
-
- -
-
-

-2.51.5. "stream" Attribute -

-
-
Possible values:
-
( "IETF" | "IAB" | "IRTF" | "independent" ) -
-
-
-

- Deprecated. Use the <stream (Section 2.54)> element instead.

-
-
-
-
-

-2.51.6. "value" Attribute (Required) -

-

- The identifier within the series specified by the "name" attribute.

-

- For BCPs, FYIs, RFCs, and STDs, this is the number within the series.

-

- For Internet-Drafts, it is the full draft name (ending with the two-digit version number).

-

- For DOIs, the value is given, such as "10.17487/rfc1149", as described in [RFC7669].

-

- The name in the value should be the document name without any file extension.

-
-
-
-
-
-
-

-2.52. <sortingcode> (New) -

-

- A sorting code is related to postal codes in that it is used in addresses to allow sorting, for example to route mail to a certain postal centre or to distinguish streets with the same name in two different areas of the same settlement.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.52.1. "ascii" Attribute -

-

- The ASCII equivalent of the <sortingcode> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.53. <sourcecode> -

-

- This element allows the inclusion of source code into the document.

-

- When rendered, source code is always shown in a monospace font. When <sourcecode> is a child of <figure> or <section>, it provides full control of horizontal whitespace and line breaks. When formatted, it is indented relative to the left margin of the enclosing element. It is thus useful for source code and formal languages (such as ABNF [RFC5234] or the RNC notation used in this document). (When <sourcecode> is a child of other elements, it flows with the text that surrounds it.) Tab characters (U+0009) inside of this element are prohibited.

-

- For artwork such as character-based art, diagrams of message layouts, and so on, use the <artwork> element instead.

-

- Output formatters that do pagination will attempt to keep source code on a single page. This is to prevent source code that is split across pages from looking like two separate pieces of code.

-

This element can be a child element of <blockquote>, <dd>, <figure>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.53.1. "anchor" Attribute -

-

Document-wide unique identifier for this <sourcecode> element.

-
-
-
-
-

-2.53.2. "markers" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Indicates whether "<CODE BEGINS>" and "<CODE ENDS>" markers, as introduced by [RFC6087], should be generated when rendering the <sourcecode> element. The alternative is to include these explicitly inside the element, but that would necessitate extra code to strip these, when extracting code from the XML source.

-
-
-
-
-

-2.53.3. "name" Attribute -

-

- A filename suitable for the contents (such as for extraction to a local file). This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code). Note that the "name" attribute does not need to be unique for <sourcecode> elements in a document. If multiple <sourcecode> elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.

-
-
-
-
-

-2.53.4. "src" Attribute -

-

- The URI reference of a source file [RFC3986].

-

- It is an error to have both a "src" attribute and content in the <sourcecode> element.

-
-
-
-
-

-2.53.5. "type" Attribute -

-

- Specifies the type of the source code. The value of this attribute is free text with certain values designated as preferred.

-

- Most of the preferred values for <sourcecode> types are language names, in a wide sense, such as "abnf", "asn.1", "bash", "c++", etc.

-

- The RFC Series Editor maintains a list of the preferred values on the RFC Editor web site at https://www.rfc-editor.org/materials/sourcecode-types.txt, and that list is updated over time. Thus, a consumer of v3 XML should not cause a failure when it encounters an unexpected type or no type is specified.

-
-
-
-
-
-
-

-2.54. <stream> (New) -

-

- Indicates which stream an RFC belongs to.

-

This element can be a child element of <reference>.

-
-
Content schema:
-
( "IETF" | "IAB" | "IRTF" | "independent" )? -
-
-
-
-
-
-
-

-2.55. <street> -

-

- Provides a street address.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.55.1. "ascii" Attribute -

-

- The ASCII equivalent of the <street> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.56. <strong> -

-

- Indicates text that is semantically strong. In HTML and PDF rendering, text enclosed within this element will be displayed as bold after processing; in text rendering it will be preceeded and followed by an asterisk. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.57. <sub> -

-

- Causes the text to be displayed as subscript, approximately half a letter-height lower than normal text, in HTML and PDF rendering. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.58. <sup> -

-

- Causes the text to be displayed as superscript, approximately half a letter-height higher than normal text, in HTML and PDF rendering. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.59. <t> -

-

- Contains a paragraph of text.

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
( text | bcp14 | br | contact | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* -
-
-
-
-
-

-2.59.1. "anchor" Attribute -

-

- Document-wide unique identifier for this paragraph.

-
-
-
-
-

-2.59.2. "hangText" Attribute -

-

- Deprecated. Instead, use <dd> inside of a definition list (<dl>).

-
-
-
-
-

-2.59.3. "indent" Attribute (New) -

-
-
Default value:
-
"0" -
-
-
-

- Indicates any extra amount of indentation to be used when rendering the paragraph of text. The indentation amount is interpreted as characters when rendering plain-text documents, and en-space units when rendering in formats that have richer typographic support such as HTML or PDF. One en-space is assumed to be the length of 0.5 em-space in CSS units. Only non-negative integer amounts of indentation are supported.

-
-
-
-
-

-2.59.4. "keepWithNext" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Acts as a hint to the output formatters that do pagination to do a best-effort attempt to keep the paragraph with the next element, whatever that happens to be. For example, for HTML output @media print CSS might translate this to page-break-after: avoid. For PDF, the paginator could attempt to keep the paragraph with the next element. Note: this attribute is strictly a hint and not always actionable.

-
-
-
-
-

-2.59.5. "keepWithPrevious" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Acts as a hint to the output formatters that do pagination to do a best-effort attempt to keep the paragraph with the previous element, whatever that happens to be. For example, for HTML output @media print CSS might translate this to page-break-before: avoid. For PDF, the paginator could attempt to keep the paragraph with the previous element. Note: this attribute is strictly a hint and not always actionable.

-
-
-
-
-
-
-

-2.60. <table> -

-

- Contains a table with a caption with the table number. If the element contains a <name> element, the caption will also show that name.

-

- Inside the <table> element there is, optionally, a <thead> element to contain the rows that will be the table's heading and, optionally, a <tfoot> element to contain the rows of the table's footer. If the XML is converted to a representation that has page breaks (such as PDFs or printed HTML), the header and footer are meant to appear on each page.

-

This element can be a child element of <aside>, <dd>, <li>, and <section>.

-
-
Content schema:
-
- name?, iref*, thead?, tbody+, tfoot? -
-
-
-
-
-

-2.60.1. "align" Attribute (New) -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"center" -
-
-
-

- Controls whether the table appears left justified, centered, or right justified. The caption will be centered under the table, and the combined table and caption will be aligned according to the "align" attribute.

-
-
-
-
-

-2.60.2. "anchor" Attribute -

-

Document-wide unique identifier for this <table> element.

-
-
-
-
-
-
-

-2.61. <tbody> -

-

- A container for a set of body rows for a table.

-

This element can be a child element of <table>.

-
-
Content schema:
-
- tr+ -
-
-
-
-
-

-2.61.1. "anchor" Attribute -

-

Document-wide unique identifier for this <tbody> element.

-
-
-
-
-
-
-

-2.62. <td> -

-

- A cell in a table row.

-

This element can be a child element of <tr>.

-
-
Content schema:
-
( ( artset | artwork | dl | figure | ol | sourcecode | t | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* ) -
-
-
-
-
-

-2.62.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-

- Controls whether the content of the cell appears left justified, centered, or right justified. Note that "center" or "right" will probably only work well in cells with plain text; any other elements might make the contents render badly.

-
-
-
-
-

-2.62.2. "anchor" Attribute -

-

Document-wide unique identifier for this <td> element.

-
-
-
-
-

-2.62.3. "colspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of columns that the cell is to span. For example, setting "colspan='3'" indicates that the cell occupies the same horizontal space as three cells of a row without any "colspan" attributes.

-
-
-
-
-

-2.62.4. "rowspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of rows that the cell is to span. For example, setting "rowspan='3'" indicates that the cell occupies the same vertical space as three rows.

-
-
-
-
-
-
-

-2.63. <tfoot> -

-

- A container for a set of footer rows for a table.

-

This element can be a child element of <table>.

-
-
Content schema:
-
- tr+ -
-
-
-
-
-

-2.63.1. "anchor" Attribute -

-

Document-wide unique identifier for this <tfoot> element.

-
-
-
-
-
-
-

-2.64. <th> -

-

- A cell in a table row. When rendered, this will normally come out in boldface; other than that, there is no difference between this and the <td> element.

-

This element can be a child element of <tr>.

-
-
Content schema:
-
( ( artset | artwork | dl | figure | ol | sourcecode | t | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* ) -
-
-
-
-
-

-2.64.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-

- Controls whether the content of the cell appears left justified, centered, or right justified. Note that "center" or "right" will probably only work well in cells with plain text; any other elements might make the contents render badly.

-
-
-
-
-

-2.64.2. "anchor" Attribute -

-

Document-wide unique identifier for this <th> element.

-
-
-
-
-

-2.64.3. "colspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of columns that the cell is to span. For example, setting "colspan='3'" indicates that the cell occupies the same horizontal space as three cells of a row without any "colspan" attributes.

-
-
-
-
-

-2.64.4. "rowspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of rows that the cell is to span. For example, setting "rowspan='3'" indicates that the cell occupies the same vertical space as three rows.

-
-
-
-
-
-
-

-2.65. <thead> -

-

- A container for a set of header rows for a table.

-

This element can be a child element of <table>.

-
-
Content schema:
-
- tr+ -
-
-
-
-
-

-2.65.1. "anchor" Attribute -

-

Document-wide unique identifier for this <thead> element.

-
-
-
-
-
-
-

-2.66. <title> -

-

- Represents the document title.

-

- When this element appears in the <front> element of the current document, the title might also appear in page headers or footers. If it is long (~40 characters), the "abbrev" attribute can be used to specify an abbreviated variant.

-

This element can be a child element of <front>.

-
-
Content schema:
-
( text | br )* -
-
-
-
-
-

-2.66.1. "abbrev" Attribute -

-

- Specifies an abbreviated variant of the document title.

-
-
-
-
-

-2.66.2. "ascii" Attribute -

-

- The ASCII equivalent of the <title> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.67. <toc> (New) -

-

- This element contains the Table of Content. The content of the <toc> element is generated by the preptool based on the "tocInclude" and "tocDepth" attributes of the <rfc> element. As a document author, you should not use <toc> directly.

-

This element can be a child element of <front>.

-
-
Content schema:
-
- section* -
-
-
-
-
-
-
-

-2.68. <tr> -

-

- A row of a table.

-

This element can be a child element of <tbody>, <tfoot>, and <thead>.

-
-
Content schema:
-
( td | th )+ -
-
-
-
-
-

-2.68.1. "anchor" Attribute -

-

Document-wide unique identifier for this <tr> element.

-
-
-
-
-
-
-

-2.69. <tt> -

-

- Causes the text to be displayed in a constant-width font. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | xref )* -
-
-
-
-
-
-
-

-2.70. <u> (New) -

-

- In xml2rfc vocabulary version 3, the elements <author>, <organisation>, <street>, <city>, <region>, <code>, <country>, <postalLine>, <email>, <seriesInfo>, and <title> may contain non- ascii characters for the purpose of rendering author names, addresses, and reference titles correctly. They also have an additional "ascii" attribute for the purpose of proper rendering in ascii-only media.

-

- In order to insert Unicode characters in any other context, xml2rfc vocabulary v3 requires that the Unicode string be enclosed within an <u> element. The element will be expanded inline based on the value of a "format" attribute. This provides a generalised means of generating the 6 methods of Unicode renderings listed in [RFC7997], Section 3.4, and also several others found in for instance the RFC Format Tools example rendering of RFC 7700, at https://rfc-format.github.io/draft-iab-rfc-css-bis/sample2-v2.html.

-

This element can be a child element of <annotation>, <blockquote>, <dd>, <li>, <t>, <td>, and <th>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.70.1. "anchor" Attribute -

-

Document-wide unique identifier for this <u> element.

-
-
-
-
-

-2.70.2. "ascii" Attribute -

-

- The ASCII equivalent of the content, to be used if the "ascii" keyword is used in the "format" specification.

-
-
-
-
-

-2.70.3. "format" Attribute -

-
-
Default value:
-
"lit-name-num" -
-
-
-

- The "format" attribute accepts either a simplified format specification, or a full format string with placeholders for the various possible Unicode expansions.

-

- The simplified format consists of dash-separated keywords, where each keyword represents a possible expansion of the Unicode character or string; use for example "<u "lit-num-name">foo</u>" to expand the text to its literal value, code point values, and code point names.

-

- A combination of up to 3 of the following keywords may be used, separated by dashes: "num", "lit", "name", "ascii", "char". The keywords are expanded as follows and combined, with the second and third enclosed in parentheses if present:

-
-
ascii
-
- The value of the 'ascii' attribute on the <u> element -
-
-
char
-
- The literal element text, without quotes -
-
-
lit
-
- The literal element text, enclosed in quotes -
-
-
name
-
- The Unicode name(s) of the element text -
-
-
num
-
- The numeric value(s) of the element text, in U+1234 notation -
-
-
-

- In order to ensure that no specification mistakes can result for rendering methods that cannot render all Unicode code points, "num" MUST always be part of the specified format.

-
-
-
-2.70.3.1. Examples -
-

- Examples:

-
-
-
-
-
format="num-lit":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 ("Δ"). -
-
-
format="num-name":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 (GREEK CAPITAL LETTER DELTA). -
-
-
format="num-lit-name":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 ("Δ", GREEK CAPITAL LETTER DELTA). -
-
-
format="num-name-lit":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 (GREEK CAPITAL LETTER DELTA, "Δ"). -
-
-
format="name-lit-num":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character GREEK CAPITAL LETTER DELTA ("Δ", U+0394). -
-
-
format="lit-name-num":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character "Δ" (GREEK CAPITAL LETTER DELTA, U+0394). -
-
-
-
-
-
-
-
-
-
-
-2.70.3.2. Expansion of <u> multi-codepoint strings -
-

- If the <u> element encloses a sequence of Unicode codepoints, rather than - a single one, the rendering - reflects this. The element

-
-
   <u format="num-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
-
-

- will be expanded to "U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ")".

-

- Unicode characters in document text which are not enclosed in <u> - will be replaced with a question mark (?) and a warning will be issued.

-
-
-
-
-
-2.70.3.3. Non-simplified <u> format specifications -
-

- In order to provide for cases where the simplified format above is insufficient, - without relinquishing the requirement that the number of a code point always must - be rendered, the "format" attribute can also accept a full format string. This - format uses placeholders which consist of any of the key words above enclosed in - curly braces; outside of this, any ascii text is permissible. For example,

-
-
   The <u format="{lit} character ({num})">Δ</u>.
-
-

- will be rendered as

-
-
   The "Δ" character (U+0394).
-
-

- As for the simplified format, "num" MUST always be part of the - specified format in order to ensure that no specification - mistakes can result for rendering methods that cannot render all - Unicode code points,

-
-
-
-
-
-2.70.3.4. Split expansion of <u> elements -
-

- There are cases which cannot be handled with either the simplified or full <u> - format specifications. One is exemplified in Table 1 of the CSS sample document - at https://rfc-format.github.io/draft-iab-rfc-css-bis/sample2-v2.html#s-3. - Rendering this with <u> elements requires that the non-ascii content be rendered - in one place (a table cell in one column) while the expansion is rendered in another - cell in a different column. Provision for this has been made by modifying the expansion - of <u> when it is referenced by an <xref>. This table, with <u> elements - referenced by <xref> instances:

-
-
-   <table>
-     <name>A Sample of Legal Nicknames</name>
-     <thead>
-       <tr>
-          <th>#</th>
-          <th>Nickname</th>
-          <th>Output for comparison</th>
-       </tr>
-     </thead>
-     <tbody>
-       <tr>
-          <td>1</td>
-          <td>&lt;Foo&gt;</td>
-          <td>&lt;foo&gt;</td>
-       </tr>
-       <tr>
-          <td>2</td>
-          <td>&lt;foo&gt;</td>
-          <td>&lt;foo&gt;</td> </tr>
-       <tr>
-          <td>3</td>
-          <td>&lt;Foo Bar&gt;</td>
-          <td>&lt;foo bar&gt;</td>
-       </tr>
-       <tr>
-          <td>4</td>
-          <td>&lt;foo bar&gt;</td>
-          <td>&lt;foo bar&gt;</td>
-       </tr>
-       <tr>
-         <td>5</td>
-         <td>
-            &lt;
-            <u format="name-num" anchor="greek-upper-sigma">Σ</u>
-            &gt;
-         </td>
-         <td> <xref target="greek-upper-sigma" /> </td>
-       </tr>
-       <tr>
-          <td>6</td>
-          <td>
-             &lt;
-             <u format="name-num" anchor="greek-lower-sigma">σ</u>
-             &gt;
-          </td>
-          <td> <xref target="greek-lower-sigma" /> </td>
-       </tr>
-       <tr>
-          <td>7</td>
-          <td>
-             &lt;
-             <u format="name-num" anchor="greek-final-sigma">ς</u>
-             &gt;
-          </td>
-          <td> <xref target="greek-final-sigma" /> </td>
-       </tr>
-       <tr>
-          <td>8</td>
-          <td>
-             &lt;
-             <u format="name-num" anchor="black-chess-king">♚</u>
-             &gt;
-          </td>
-          <td>
-             <xref target="black-chess-king" format="default"/>
-          </td>
-       </tr>
-       <tr>
-          <td>9</td>
-          <td>
-             &lt;Richard
-             <u format="{char}> ({num})" anchor="richard-iv">Ⅳ</u>
-             &gt;
-          </td>
-          <td>&lt;richard iv&gt;</td>
-       </tr>
-     </tbody>
-   </table>
-
-
-
-

- comes out as shown below:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -A Sample of Legal Nicknames -
#NicknameOutput for comparison
1<Foo><foo>
2<foo><foo>
3<Foo Bar><foo bar>
4<foo bar><foo bar>
5<Σ> - GREEK CAPITAL LETTER SIGMA (U+03A3)
6<σ> - GREEK SMALL LETTER SIGMA (U+03C3)
7<ς> - GREEK SMALL LETTER FINAL SIGMA (U+03C2)
8<♚> - BLACK CHESS KING (U+265A) -
9<Richard Ⅳ> (U+2163) -<richard iv>
-
-
-
-
-
-
-
-
-

-2.71. <ul> -

-

- An unordered list. The labels on the items will be symbols picked by the formatter.

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
- li+ -
-
-
-
-
-

-2.71.1. "anchor" Attribute -

-

Document-wide unique identifier for this <ul> element.

-
-
-
-
-

-2.71.2. "bare" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Can only be used with empty="true" (see below). Determines if the blank bullet has an horizontal extension or not. With bare="false", the empty list bullet will still occupy the same space as for empty="false". With empty="true", there will be no bullet at all, i.e., the list items will have no indentation.

-

- Example: an unordered list with bare="true" and empty="true":

-
    -
  • One -
    • -
  • Two -
    • -
-
-
-
-
-

-2.71.3. "empty" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Defines whether or not the list item bullets are empty. empty="true" indicates that a blank (empty) bullet will be shown.

-

- Example: an unordered list with bare="false" and empty="false":

-
    -
  • One -
    • -
  • Two -
    • -
-

- Example: an unordered list with bare="false" and empty="true":

-
    -
  • One -
    • -
  • Two -
    • -
-
-
-
-
-

-2.71.4. "indent" Attribute (New) -

-
-
Default value:
-
"3" -
-
-
-

- The indentation of the list elements relative to the start of the bullet or bullet text.

-
-
-
-
-

-2.71.5. "spacing" Attribute -

-
-
Possible values:
-
( "normal" | "compact" ) -
-
-
Default value:
-
"normal" -
-
-
-

- Defines whether or not there is a blank line between entries. spacing="normal" indicates a single blank line, while spacing="compact" indicates no blank line between entries.

-
-
-
-
-
-
-

-2.72. <uri> -

-

- Contains a web address associated with the author.

-

- The contents should be a valid URI; this most likely will be an "http:" or "https:" URI.

-

This element can be a child element of <address>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.73. <workgroup> -

-

- This element is used to specify the Working Group (IETF) or Research Group (IRTF) from which the document originates, if any. The recommended format is the official name of the Working Group (with some capitalization).

-

- In Internet-Drafts, this is used in the upper left corner of the boilerplate, replacing the "Network Working Group" string. Formatting software can append the words "Working Group" or "Research Group", depending on the "submissionType" property of the <rfc> element (Section 2.48.12).

-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.74. <xref> -

-

- A reference to an anchor in this document. Formatters that have links (such as HTML and PDF) are likely to render <xref> elements as internal hyperlinks. This element is useful for referring to references in the "References" section, to specific sections of the document, to specific figures, and so on.

-

- If the "section" attribute is present, this represents a link to a specific part of a document that appears in a <reference> element. Formatters that have links (such as HTML and PDF) render <xref> elements with "section" attributes as external hyperlinks to the specified part of the reference, creating the link target by combining the base URI from the <reference> element with the "relative" attribute from this element. The "target" attribute is required, and it must be the anchor of a <reference> element.

-

- If the reference is not an RFC or Internet-Draft that is in the v3 format, the element needs to have a "relative" attribute; in this case, the value of the "section" attribute is used to render the text of the external link.

-

- If the "sectino" attribute is present, the rendering will for most cominations of the "format" and "sectionFormat" have two links; one external link to the specific part of the referenced document, and one internal link to the <reference> entry.

-

- The attribute "format" affect the internal link rendering only, and the "sectionFormat" affects the rendering of the external link and its textual relationship to the internal link only.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, .

-
-
Content schema:
-
( text | em | strong | sub | sup | tt )* -
-
-
-
-
-

-2.74.1. "format" Attribute -

-
-
Possible values:
-
( "default" | "title" | "counter" | "none" ) -
-
-
Default value:
-
"default" -
-
-
-

- This attribute signals to formatters what the desired format of the internal link to the relevant <reference> should be.

-
-
"default"
-
-

If the element has no content, the "derivedContent" attribute will contain a text fragment that describes the referenced part completely, such as "XML" for a target that is a <reference>, or "Section 2" or "Table 4" for a target to a non-reference.

-
-
-
"title"
-
-

If the target is a <reference> element, the "derivedContent" attribute will contain the name of the reference, extracted from the <title> child of the <front> child of the reference. Or, if the target element has a <name> child element, the "derivedContent" attribute will contain the text content of that <name> element concatenated with the text content of each descendant node of <name> (that is, stripping out all of the XML markup, leaving only the text). Or, if the target element does not contain a <name> child element, the "derivedContent" attribute will contain the name of the "anchor" attribute of that element with no other adornment.

-
-
-
"counter"
-
-

The "derivedContent" attribute will contain just a counter. This is used for targets that are <section>, <figure>, <table>, or items in an ordered list. Using "format='counter'" where the target is any other type of element is an error.

-
-
-
"none"
-
-

There will be no autogenerated text for the xref. When this value is used, it expected that the <xref> element will have explicit text content.

-
-
-
-
-
-
-
-

-2.74.2. "relative" Attribute (New) -

-

- Specifies a relative reference from the URI in the target reference. This value must include whatever leading character is needed to create the relative reference; typically, this is "#" for HTML documents.

-
-
-
-
-

-2.74.3. "section" Attribute (New) -

-

- Specifies a section of the target reference. If the reference is not an RFC or Internet-Draft in the v3 format, and no "relative" attribute has been provided, it is an error.

-
-
-
-
-

-2.74.4. "sectionFormat" Attribute (New) -

-
-
Possible values:
-
( "of" | "comma" | "parens" | "bare" ) -
-
-
Default value:
-
"of" -
-
-
-

- This attribute is used to signal formatters what the desired format of the external reference should be. Formatters for document types that have linking capability should wrap each part of the displayed text in hyperlinks. If there is content in the <xref> element, that content will be used when rendering the internal link part of the <xref> rendering, but will not affect the external link.

-
-
"of"
-
-

The <xref> element will be displayed as an external link followed by an internal link, separated by the work 'of'. The external link will have as its display text the word "Section" followed by a space and the contents of the "section" attribute. This will be followed by a space, the word "of", another space, and an internal link to the relevant <reference> entry, formatted based on the "format" attribute.

-
-
-
"comma"
-
-

The <xref> element will be displayed as an internal link followed by an external link, separated by a comma. The external link will have as its display text the word "Section" followed by a space and the contents of the "section" attribute. The internal link will point to the relevant <reference> entry, and will be rendered according to the "format" attribute.

-
-
-
"parens"
-
-

The <xref> element will be displayed as an internal link followed by an external link within parentheses. The external link will have as its display text the word "Section" followed by a space and the contents of the "section" attribute. The internal link will point to the relevant <reference> entry, and will be rendered according to the "format" attribute.

-
-
-
"bare"
-
-

The <xref> element will be displayed as an external link, possibly followed by the same link within parentheses. The first external link will have as its display text only contents of the "section" attribute; the second link will be present within parentheses only if the <xref> element has any text content, and will then have the text content as its display text.

-

This value for the "sectionFormat" attribute is useful when it is desired to express for instance "Sections 3.2 and 3.3 of [RFC7997]".

-
-
-
-
-
-
-
-

-2.74.5. "target" Attribute (Required) -

-

- Identifies the document component being referenced. The value needs to match the value of the "anchor" attribute of an element in the document; otherwise, it is an error.

-
-
-
-
-
-
-

-3. Deprecated Elements and Attributes -

-
-

-3.1. Elements from v2 that have been Deprecated -

-

- - The following elements from v2 have been deprecated:

-
    -
  • <c> -
    • -
  • <facsimile> -
    • -
  • <format> -
    • -
  • <list> -
    • -
  • <postamble> -
    • -
  • <preamble> -
    • -
  • <relref> -
    • -
  • <spanx> -
    • -
  • <texttable> -
    • -
  • <ttcol> -
    • -
  • <vspace> -
    • -
-
-
-

-3.2. Attributes from v2 that have been Deprecated -

-

- - The following attributes from v2 have been deprecated. Only - attributes of elements that have not themselves been deprecated - are listed:

-
-
<artwork>:
-
-
    -
  • "height" -
    • -
  • "width" -
    • -
-
-
-
<figure>:
-
-
    -
  • "align" -
    • -
  • "alt" -
    • -
  • "height" -
    • -
  • "src" -
    • -
  • "suppress-title" -
    • -
  • "title" -
    • -
  • "width" -
    • -
-
-
-
<note>:
-
-
    -
  • "title" -
    • -
-
-
-
<references>:
-
-
    -
  • "title" -
    • -
-
-
-
<section>:
-
-
    -
  • "title" -
    • -
-
-
-
<seriesInfo>:
-
-
    -
  • "status" -
    • -
  • "stream" -
    • -
-
-
-
<t>:
-
-
    -
  • "hangText" -
    • -
-
-
-
-
-
-
-

-4. References -

-
-
[BCP14]
-
-
- Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, .
-
- Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, .
-<https://www.rfc-editor.org/bcp/bcp14.txt> -
-
-
[IDGUIDE]
-
-Housley, R., "Guidelines to Authors of Internet-Drafts", , <https://www.ietf.org/id-info/guidelines.html>.
-
-
[INTRO-TO-V3]
-
-Levkowetz, H., "Introduction to xml2rfc Version 3", , <https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html>.
-
-
[LINKRELATIONS]
-
-IANA, "Link Relations", <https://www.iana.org/assignments/link-relations/link-relations.xhtml>.
-
-
[RFC2026]
-
-Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, , <https://www.rfc-editor.org/info/rfc2026>.
-
-
[RFC2397]
-
-Masinter, L., "The "data" URL scheme", RFC 2397, DOI 10.17487/RFC2397, , <https://www.rfc-editor.org/info/rfc2397>.
-
-
[RFC3339]
-
-Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, , <https://www.rfc-editor.org/info/rfc3339>.
-
-
[RFC3966]
-
-Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, DOI 10.17487/RFC3966, , <https://www.rfc-editor.org/info/rfc3966>.
-
-
[RFC3986]
-
-Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, , <https://www.rfc-editor.org/info/rfc3986>.
-
-
[RFC5234]
-
-Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, , <https://www.rfc-editor.org/info/rfc5234>.
-
-
[RFC6068]
-
-Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, DOI 10.17487/RFC6068, , <https://www.rfc-editor.org/info/rfc6068>.
-
-
[RFC6087]
-
-Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, , <https://www.rfc-editor.org/info/rfc6087>.
-
-
[RFC7322]
-
-Flanagan, H. and S. Ginoza, "RFC Style Guide", RFC 7322, DOI 10.17487/RFC7322, , <https://www.rfc-editor.org/info/rfc7322>.
-
-
[RFC7669]
-
-Levine, J., "Assigning Digital Object Identifiers to RFCs", RFC 7669, DOI 10.17487/RFC7669, , <https://www.rfc-editor.org/info/rfc7669>.
-
-
[RFC7841]
-
-Halpern, J., Ed., Daigle, L., Ed., and O. Kolkman, Ed., "RFC Streams, Headers, and Boilerplates", RFC 7841, DOI 10.17487/RFC7841, , <https://www.rfc-editor.org/info/rfc7841>.
-
-
[RFC7991]
-
-Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, DOI 10.17487/RFC7991, , <https://www.rfc-editor.org/info/rfc7991>.
-
-
[RFC7996]
-
-Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
-
-
[RFC7997]
-
-Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
-
-
[RFC7998]
-
-Hoffman, P. and J. Hildebrand, ""xml2rfc" Version 3 Preparation Tool Description", RFC 7998, DOI 10.17487/RFC7998, , <https://www.rfc-editor.org/info/rfc7998>.
-
-
[RNC]
-
-Clark, J., "RELAX NG Compact Syntax", <https://www.oasis-open.org/committees/relax-ng/compact-20021121.html>.
-
-
-
-
-

-Appendix A. RELAX NG Schema -

-
-
<CODE BEGINS> file "v3.rnc"
-
-
-namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
-
-# xml2rfc Version 3 grammar
-
-rfc =
-  element rfc {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute number { text }?,
-    [ a:defaultValue = "" ] attribute obsoletes { text }?,
-    [ a:defaultValue = "" ] attribute updates { text }?,
-    attribute category {
-      "std" | "bcp" | "exp" | "info" | "historic"
-    }?,
-    attribute mode { text }?,
-    [ a:defaultValue = "false" ]
-    attribute consensus { "no" | "yes" | "false" | "true" }?,
-    attribute seriesNo { text }?,
-    attribute ipr { text }?,
-    attribute iprExtract { xsd:IDREF }?,
-    [ a:defaultValue = "IETF" ]
-    attribute submissionType {
-      "IETF" | "IAB" | "IRTF" | "independent"
-    }?,
-    attribute docName { text }?,
-    [ a:defaultValue = "false" ]
-    attribute sortRefs { "true" | "false" }?,
-    [ a:defaultValue = "true" ]
-    attribute symRefs { "true" | "false" }?,
-    [ a:defaultValue = "true" ]
-    attribute tocInclude { "true" | "false" }?,
-    [ a:defaultValue = "3" ] attribute tocDepth { text }?,
-    attribute prepTime { text }?,
-    [ a:defaultValue = "true" ]
-    attribute indexInclude { "true" | "false" }?,
-    attribute version { text }?,
-    [ a:defaultValue = "Common,Latin" ] attribute scripts { text }?,
-    attribute expiresDate { text }?,
-    link*,
-    front,
-    middle,
-    back?
-  }
-
-link =
-  element link {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute href { text },
-    attribute rel { text }?
-  }
-
-front =
-  element front {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    title,
-    seriesInfo*,
-    author+,
-    date?,
-    area*,
-    workgroup*,
-    keyword*,
-    abstract?,
-    note*,
-    boilerplate?,
-    toc?
-  }
-
-title =
-  element title {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute abbrev { text }?,
-    attribute ascii { text }?,
-    (text | br)*
-  }
-
-author =
-  element author {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute initials { text }?,
-    attribute asciiInitials { text }?,
-    attribute surname { text }?,
-    attribute asciiSurname { text }?,
-    attribute fullname { text }?,
-    attribute role { "editor" }?,
-    attribute asciiFullname { text }?,
-    organization?,
-    address?
-  }
-
-contact =
-  element contact {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute initials { text }?,
-    attribute asciiInitials { text }?,
-    attribute surname { text }?,
-    attribute asciiSurname { text }?,
-    attribute fullname { text }?,
-    attribute asciiFullname { text }?,
-    organization?,
-    address?
-  }
-
-organization =
-  element organization {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute abbrev { text }?,
-    attribute ascii { text }?,
-    attribute asciiAbbrev { text }?,
-    [ a:defaultValue = "true" ]
-    attribute showOnFrontPage { "true" | "false" }?,
-    text
-  }
-
-address =
-  element address {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    postal?,
-    phone?,
-    facsimile?,
-    email*,
-    uri?
-  }
-
-postal =
-  element postal {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (( city | cityarea | code | country | extaddr | pobox | region
-       | sortingcode | street)*
-     | postalLine+)
-  }
-
-extaddr =
-  element extaddr {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-pobox =
-  element pobox {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-street =
-  element street {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-cityarea =
-  element cityarea {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-city =
-  element city {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-region =
-  element region {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-code =
-  element code {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-sortingcode =
-  element sortingcode {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-country =
-  element country {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-postalLine =
-  element postalLine {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-phone =
-  element phone {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-facsimile =
-  element facsimile {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-email =
-  element email {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-uri =
-  element uri {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-date =
-  element date {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute day { text }?,
-    attribute month { text }?,
-    attribute year { text }?,
-    text
-  }
-
-area =
-  element area {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-workgroup =
-  element workgroup {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-keyword =
-  element keyword {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-abstract =
-  element abstract {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (dl | ol | t | ul)+
-  }
-
-note =
-  element note {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute title { text }?,
-    attribute pn { xsd:ID }?,
-    [ a:defaultValue = "false" ]
-    attribute removeInRFC { "true" | "false" }?,
-    name?,
-    (dl | ol | t | ul)+
-  }
-
-boilerplate =
-  element boilerplate {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    section+
-  }
-
-toc =
-  element toc {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    section*
-  }
-
-middle =
-  element middle {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    section+
-  }
-
-section =
-  element section {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute title { text }?,
-    [ a:defaultValue = "true" ]
-    attribute numbered { "true" | "false" }?,
-    [ a:defaultValue = "default" ]
-    attribute toc { "include" | "exclude" | "default" }?,
-    [ a:defaultValue = "false" ]
-    attribute removeInRFC { "true" | "false" }?,
-    name?,
-    (artset
-     | artwork
-     | aside
-     | author
-     | blockquote
-     | contact
-     | dl
-     | figure
-     | iref
-     | ol
-     | sourcecode
-     | t
-     | table
-     | texttable
-     | ul)*,
-    section*
-  }
-
-name =
-  element name {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute slugifiedName { xsd:ID }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-br =
-  element br {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    empty
-  }
-
-t =
-  element t {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute hangText { text }?,
-    [ a:defaultValue = "0" ]
-    attribute indent { text }?,
-    [ a:defaultValue = "false" ]
-    attribute keepWithNext { "true" | "false" }?,
-    [ a:defaultValue = "false" ]
-    attribute keepWithPrevious { "true" | "false" }?,
-    (text
-     | bcp14
-     | br
-     | contact
-     | cref
-     | em
-     | eref
-     | iref
-     | \list
-     | relref
-     | spanx
-     | strong
-     | sub
-     | sup
-     | tt
-     | u
-     | vspace
-     | xref)*
-  }
-
-aside =
-  element aside {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (artset
-     | artwork
-     | blockquote
-     | dl
-     | figure
-     | iref
-     | ol
-     | t
-     | table
-     | ul)*
-
-  }
-
-blockquote =
-  element blockquote {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute cite { text }?,
-    attribute quotedFrom { text }?,
-    ((artset | artwork | dl | figure | ol | sourcecode | t | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)+)
-  }
-
-\list =
-  element list {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "empty" ] attribute style { text }?,
-    attribute hangIndent { text }?,
-    attribute counter { text }?,
-    attribute pn { xsd:ID }?,
-    t+
-  }
-
-ol =
-  element ol {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "1" ] attribute type { text }?,
-    [ a:defaultValue = "1" ] attribute start { text }?,
-    attribute group { text }?,
-    [ a:defaultValue = "normal" ]
-    attribute spacing { "normal" | "compact" }?,
-    [ a:defaultValue = "adaptive" ]
-    attribute indent { text | "adaptive" }?,
-    attribute pn { xsd:ID }?,
-    li+
-  }
-
-ul =
-  element ul {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "normal" ]
-    attribute spacing { "normal" | "compact" }?,
-    ([ a:defaultValue = "false" ]
-     attribute empty { "true" | "false" },
-     [ a:defaultValue = "false" ]
-     attribute bare { "true" | "false" }?)?,
-    [ a:defaultValue = "3" ]
-     attribute indent { text }?,
-     attribute pn { xsd:ID }?,
-    li+
-  }
-
-li =
-  element li {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute derivedCounter { text }?,
-    attribute pn { xsd:ID }?,
-    (( artset
-       | artwork
-       | blockquote
-       | dl
-       | figure
-       | ol
-       | sourcecode
-       | t
-       | table
-       | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)+)
-  }
-
-dl =
-  element dl {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "normal" ]
-    attribute spacing { "normal" | "compact" }?,
-    [ a:defaultValue = "false" ]
-    attribute newline { "true" | "false" }?,
-    [ a:defaultValue = "3" ]
-    attribute indent { text }?,
-    attribute pn { xsd:ID }?,
-    (dt, dd)+
-  }
-
-dt =
-  element dt {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-dd =
-  element dd {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (( artset
-       | artwork
-       | aside
-       | dl
-       | figure
-       | ol
-       | sourcecode
-       | t
-       | table
-       | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)+)
-  }
-
-xref =
-  element xref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { xsd:IDREF },
-    [ a:defaultValue = "false" ]
-    attribute pageno { "true" | "false" }?,
-    [ a:defaultValue = "default" ]
-    attribute format { "default" | "title" | "counter" | "none" }?,
-    attribute derivedContent { text }?,
-    [ a:defaultValue = "of" ]
-    attribute sectionFormat { "of" | "comma" | "parens" | "bare" }?,
-    attribute section { text }?,
-    attribute relative { text }?,
-    attribute derivedLink { text }?,
-    (text | em | strong | sub | sup | tt)*
-  }
-
-relref =
-  element relref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { xsd:IDREF },
-    [ a:defaultValue = "of" ]
-    attribute displayFormat { "of" | "comma" | "parens" | "bare" }?,
-    attribute derivedContent { text }?,
-    attribute section { text },
-    attribute relative { text }?,
-    attribute derivedLink { text }?,
-    text
-  }
-
-eref =
-  element eref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "none" ]
-    attribute brackets { "none" | "angle" }?,
-    attribute target { text },
-    text
-  }
-
-iref =
-  element iref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute item { text },
-    [ a:defaultValue = "" ] attribute subitem { text }?,
-    [ a:defaultValue = "false" ]
-    attribute primary { "true" | "false" }?,
-    attribute pn { xsd:ID }?,
-    empty
-  }
-
-cref =
-  element cref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute source { text }?,
-    [ a:defaultValue = "true" ]
-    attribute display { "true" | "false" }?,
-    (text
-     | br
-     | em
-     | eref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-tt =
-  element tt {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | xref)*
-  }
-
-strong =
-  element strong {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-em =
-  element em {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-sub =
-  element sub {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-sup =
-  element sup {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-spanx =
-  element spanx {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "preserve" ]
-    attribute xml:space { "default" | "preserve" }?,
-    [ a:defaultValue = "emph" ] attribute style { text }?,
-    text
-  }
-
-vspace =
-  element vspace {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "0" ] attribute blankLines { text }?,
-    empty
-  }
-
-figure =
-  element figure {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    [ a:defaultValue = "" ] attribute title { text }?,
-    [ a:defaultValue = "false" ]
-    attribute suppress-title { "true" | "false" }?,
-    attribute src { text }?,
-    attribute originalSrc { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    [ a:defaultValue = "" ] attribute alt { text }?,
-    [ a:defaultValue = "" ] attribute width { text }?,
-    [ a:defaultValue = "" ] attribute height { text }?,
-    name?,
-    iref*,
-    preamble?,
-    (artset | artwork | sourcecode)+,
-    postamble?
-  }
-
-table =
-  element table {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "center" ]
-    attribute align { "left" | "center" | "right" }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    name?,
-    iref*,
-    thead?,
-    tbody+,
-    tfoot?
-  }
-
-preamble =
-  element preamble {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | spanx
-     | strong
-     | sub
-     | sup
-     | tt
-     | u
-     | xref)*
-  }
-
-artset =
-  element artset {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    artwork+
-  }
-
-
-artwork =
-  element artwork {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute xml:space { text }?,
-    [ a:defaultValue = "" ] attribute name { text }?,
-    [ a:defaultValue = "" ] attribute type { text }?,
-    attribute src { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    [ a:defaultValue = "" ] attribute alt { text }?,
-    [ a:defaultValue = "" ] attribute width { text }?,
-    [ a:defaultValue = "" ] attribute height { text }?,
-    attribute originalSrc { text }?,
-    (text* | svg)
-  }
-include "SVG-1.2-RFC.rnc"
-
-sourcecode =
-  element sourcecode {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    [ a:defaultValue = "" ] attribute name { text }?,
-    [ a:defaultValue = "" ] attribute type { text }?,
-    [ a:defaultValue = "false" ]
-    attribute markers { "true" | "false" }?,
-    attribute src { text }?,
-    attribute originalSrc { text }?,
-    text
-  }
-
-thead =
-  element thead {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    tr+
-  }
-
-tbody =
-  element tbody {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    tr+
-  }
-
-tfoot =
-  element tfoot {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    tr+
-  }
-
-tr =
-  element tr {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    (td | th)+
-  }
-
-td =
-  element td {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "1" ] attribute colspan { text }?,
-    [ a:defaultValue = "1" ] attribute rowspan { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    ((artset | artwork | dl | figure | ol | sourcecode | t | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)*)
-  }
-
-th =
-  element th {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "1" ] attribute colspan { text }?,
-    [ a:defaultValue = "1" ] attribute rowspan { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    ((artset | artwork | dl | figure | ol | sourcecode | t | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)*)
-  }
-
-postamble =
-  element postamble {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text | cref | eref | iref | spanx | xref)*
-  }
-
-texttable =
-  element texttable {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "" ] attribute title { text }?,
-    [ a:defaultValue = "false" ]
-    attribute suppress-title { "true" | "false" }?,
-    [ a:defaultValue = "center" ]
-    attribute align { "left" | "center" | "right" }?,
-    [ a:defaultValue = "full" ]
-    attribute style { "all" | "none" | "headers" | "full" }?,
-    name?,
-    preamble?,
-    ttcol+,
-    c*,
-    postamble?
-  }
-
-ttcol =
-  element ttcol {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute width { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    (cref | eref | iref | xref | text)*
-  }
-
-c =
-  element c {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text | cref | eref | iref | spanx | xref)*
-  }
-
-bcp14 =
-  element bcp14 {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-back =
-  element back {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    displayreference*,
-    references*,
-    section*
-  }
-
-displayreference =
-  element displayreference {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { xsd:IDREF },
-    attribute to { text }
-  }
-
-references =
-  element references {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute pn { xsd:ID }?,
-    attribute anchor { xsd:ID }?,
-    attribute title { text }?,
-    name?,
-    (references+ | (reference | referencegroup)*)
-  }
-
-reference =
-  element reference {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID },
-    attribute derivedAnchor { text }?,
-    attribute target { text }?,
-    [ a:defaultValue = "true" ]
-    attribute quoteTitle { "true" | "false" }?,
-    attribute quote-title { "true" | "false" }?,
-    stream?,
-    front,
-    (annotation | format | refcontent | seriesInfo)*
-  }
-
-stream =
-  element stream {
-    ( "IETF" | "IAB" | "IRTF" | "independent" )?
-}
-
-referencegroup =
-  element referencegroup {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID },
-    attribute derivedAnchor { text }?,
-    attribute target { text }?,
-    reference+
-  }
-
-seriesInfo =
-  element seriesInfo {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute name { text },
-    attribute value { text },
-    attribute asciiName { text }?,
-    attribute asciiValue { text }?,
-    attribute status { text }?,
-    attribute stream { "IETF" | "IAB" | "IRTF" | "independent" }?,
-    empty
-  }
-
-format =
-  element format {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { text }?,
-    attribute type { text },
-    attribute octets { text }?,
-    empty
-  }
-
-annotation =
-  element annotation {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | spanx
-     | strong
-     | sub
-     | sup
-     | tt
-     | u
-     | xref)*
-  }
-
-refcontent =
-  element refcontent {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text | bcp14 | em | strong | sub | sup | tt)*
-  }
-
-u =
-  element u {
-    attribute anchor { xsd:ID }?,
-    attribute ascii { text }?,
-    [ a:defaultValue = "lit-name-num" ]
-    attribute format { text }?,
-    attribute pn { xsd:ID }?,
-    text
-  }
-
-start |= rfc
-
-
-<CODE ENDS>
-
-
-
-

-Appendix B. xml2rfc Command-line Options -

-

- The following command-line options are available. Long options may be shortened to the shortest substring that still makes the option string unique, when given on the command line. In config files, the full long option string must be used.

-
-

-B.1. Positional arguments -

-
-
source
-
Input XML file to render to one or more of the available formats. -
-
-
-
-
-

-B.2. Documentation options -

-

- Some options to generate built-in documentation. - The group has 8 options.

-
-
-
---help, -h
-
-
-

- Show a help message and exit.

-
-
-
-
---docfile
-
-
-

- Generate a documentation XML file ready for formatting.

-

- The --docfile and --manpage switches takes input from 5 places:

-
    -
  • The v3.rng file distributed as part of the xml2rfc package, which is also used to validate and process v3 XML input. -
    • -
  • A rfc7991.rng file distributed as part of the xml2rfc package, which holds the schema defined in [RFC7991]. This is used in determining elements and attributes that are new in the current v3.rng schema, compared to the RFC7991 schema. -
    • -
  • Lists of deprecated elements and attributes, which are part of the xml2rfc source. -
    • -
  • A YAML file doc.yaml that contains XML snippets with descriptions of elements, attributes, attribute values, and switches, from the same directory as doc.xml. -
    • -
  • An XML template file doc.xml, by default taken from the templates directory of the xml2rfc package (but this can be changed with the --templates-dir switch). The 4 preceding sources provide content that is used to expand the template file when generating the --⁠docfile and --⁠manpage output. -
    • -
-
-
-
-
---manpage
-
-
-

- Show paged text documentation.

-

- Generates on-the-fly paged text documentation for the v3 schema elements and attributes from the v3 RelaxNG schema file which is part of the xml2rfc distribution, and YAML and XML files that provide the text content and formatting. See the --docfile switch for more details.

-
-
-
-
---country-help
-
-
-

- Show the recognized <country> strings.

-
-
-
-
---pdf-help
-
-
-

- Show pdf generation requirements.

-
-
-
-
---template-dir
-
-
-

- Directory to pull the doc.xml and doc.yaml templates from. The default is the "templates" directory of the xml2rfc package.

-

- This is used to find the templates used by the --⁠docfile and --⁠manpage commands and for legacy .html template and .dtd files.

-

- A consequence of being able to specify a different template directory than the default is that it's possible to use the --⁠docfile command to generate additional documentation XML files based on the current V3 grammar file. The default template and snippets file does not include documentation for deprecated elements and attributes, for instance; but if it is desired to generate such documentation from the distributed V3 RelaxNg schema, it should be straightforward. The templating system used is Jinja2; the snippens file is YAML with extra support for some escape sequences: '\ <' and '\ >'.

-
-
-
-
---values
-
-
-

- Show option values and from where they come.

-

- This shows (in order):

-
    -
  • Command line arguments -
    • -
  • Config file settings, per config file -
    • -
  • Default values -
    • -
  • Config file search path -
    • -
-
-
-
-
---version, -V
-
-
-

- Display the version number and exit.

-

- With the --verbose switch, the versions of the external python modules used will also be shown.

-
-
-
-
-
-

-B.3. Format selection -

-

- One or more of the following output formats may be specified. The default is --text. The destination filename will be based on the input filename, unless --out=FILE or --basename=BASE is used. - The group has 10 options.

-
-
-
---text
-
-
-

- Outputs formatted text to file, with proper page breaks.

-
-
-
-
---html
-
-
-

- Outputs formatted HTML to file.

-
-
-
-
---nroff
-
-
-

- Outputs formatted nroff to file (only v2 input).

-
-
-
-
---pdf
-
-
-

- Outputs formatted PDF to file.

-
-
-
-
---raw
-
-
-

- Outputs formatted text to file, unpaginated (only v2 input).

-
-
-
-
---expand
-
-
-

- Outputs XML to file with all references expanded.

-
-
-
-
---v2v3
-
-
-

- Convert vocabulary version 2 XML to version 3.

-
-
-
-
---preptool
-
-
-

- Run preptool on the input.

-
-
-
-
---unprep
-
-
-

- Reduce prepped xml to unprepped.

-
-
-
-
---info
-
-
-

- Generate a JSON file with anchor to section lookup information.

-
-
-
-
-
-

-B.4. Generic Switch Options -

-
-
-
---clear-cache, -C
-
-
-

- Purge the cache and exit.

-
-
-
-
---debug
-
-
-

- Show debugging output.

-
-
-
-
---no-network, -N
-
-
-

- Don't use the network to resolve references.

-
-
-
-
---no-org-info, -O
-
-
-

- Don't show author orgainzation info on page one (legacy only).

-
-
-
-
---quiet, -q
-
-
-

- Don't print anything while working.

-
-
-
-
---skip-config-files
-
-
-

- Ignore config file settings.

-

- Use this to ignore values in config files, even if there are config files in the search path. Somewhat ironically, this option can itself be set in a config file, and cause all other config file settings to be ignored.

-
-
-
-
---allow-local-file-access
-
-
-

- Allow local file system references.

-
-
-
-
---remove-pis, -r
-
-
-

- Remove XML processing instructions.

-
-
-
-
---utf8, -u
-
-
-

- Generate utf8 output.

-
-
-
-
---verbose, -v
-
-
-

- Print extra information.

-
-
-
-
-
-

-B.5. Generic Options with Values -

-
-
-
---basename, -b = NAME
-
-
-

- Specify the base name for output files.

-
-
-
-
---cache, -c = PATH
-
-
-

- Specify a primary cache directory to write to; default: try [ /var/cache/xml2rfc, ~/.cache/xml2rfc ].

-
-
-
-
---config-file = FILE
-
-
-

- Specify a configuration file.

-

- This argument can be repeated, to read multiple explicitly specified config files. They will be read after any config files found in 'standard' locations have been read. Run xml2rfc --values to see the default search path for config files.

-
-
-
-
---dtd, -d = DTDFILE
-
-
-

- Specify an alternate dtd file.

-

- This option can be negated with --no-dtd.

-
-
-
-
---date, -D = DATE
-
-
-

- Run as if the date is DATE (format: yyyy-mm-dd). Default: Today's date.

-
-
-
-
---filename, -f = FILE
-
-
-

- Deprecated. The same as -o.

-
-
-
-
---indent, -i = INDENT
-
-
-

- With some v3 formatters: Indentation to use when pretty-printing XML.

-
-
-
-
---out, -o = FILE
-
-
-

- Specify an explicit output filename.

-
-
-
-
---path, -p = PATH
-
-
-

- Specify the directory path for output files.

-
-
-
-
---silence, -s = STRING
-
-
-

- Silence any warning beginning with the given string.

-

- Specifies a string prefix or a regular expression to match against warning messages. Any warning message that matches is silenced. Example:

-
-
xml2rfc --silence='The document date' draft-foo-bar.xml
-
-

- This will not show any message about the document date being too far from the current date. The option can be repeated with different prefix strings or regular expressions in order to silence multiple warning messages.

-

- Alternatively, instead of indicating this on the command line, an xml2rfc-specific PI (processing instruction) is available for use in XML input files. This will have the same effect as the example above, except when processing prepped drafts; running the preptool on a file will strip XML PIs before writing the prepped file:

-
-
<?v3xml2rfc silence="The document date" ?>
-
-
-
-
-
-
-

-B.6. Generic Format Options -

-
-
-
---v3
-
-
-

- With --text and --html: use the v3 formatter, rather than the legacy one.

-

- This is the default. With both v2 schema and v3 schema XML input files, use the v3 output formatters. Input with deprecated v2 elements will be converted to v3 on the fly. This means some loss of functionality and exact control of the output, due to the intermediary conversion step.

-
-
-
-
---v2, --legacy
-
-
-

- With --text and --html: use the legacy output formatters, rather than the v3 ones.

-

- Invokes the legacy (schema v2) validator and output formatters, instead of the default schema v3 output formatters. This can only be used with pure v2 input files.

-
-
-
-
---id-is-work-in-progress
-
-
-

- In references, refer to Internet-Drafts as "Work in Progress".

-
-
-
-
-
-

-B.7. Text Format Options -

-
-
-
---no-headers
-
-
-

- Calculate page breaks, and emit form feeds and page top spacing, but omit headers and footers from the paginated format.

-
-
-
-
---legacy-list-symbols
-
-
-

- Use the legacy list bullet symbols, rather than the new ones.

-
-
-
-
---legacy-date-format
-
-
-

- Use the legacy date format, rather than the new one.

-

- This option can be negated with --no-legacy-date-format.

-
-
-
-
---list-symbols = 4*CHAR
-
-
-

- Use the characters given as list bullet symbols.

-
-
-
-
---BOM, --bom
-
-
-

- Add a BOM (unicode byte order mark) to the start of text files.

-
-
-
-
---pagination, --paginate
-
-
-

- Do pagination.

-

- By default, drafts are paginated, but not RFCs. Use this switch if you want to force pagination of all text output.

-

- This option can be negated with --no-pagination.

-
-
-
-
---table-hyphen-breaks
-
-
-

- More easily do line breaks after hyphens in table cells to give a more compact table.

-
-
-
-
---table-borders
-
-
-


Default value: full

-

- The style of table borders to use for text output; one of full/light/minimal.

-

- Examples (these will only have visible differences in text mode):

-
-
"full":
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 2
ABC
a b c
aa ba ca
ab bb cb
AA BB CC
aaa bba cca
aab bbb ccb
-
-
-
-
-
"light":
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 3
ABC
a b c
aa ba ca
ab bb cb
AA BB CC
aaa bba cca
aab bbb ccb
-
-
-
-
-
"minimal":
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 4
ABC
a b c
aa ba ca
ab bb cb
AA BB CC
aaa bba cca
aab bbb ccb
-
-
-
-
-
-
-
-
-

-B.8. Html Format Options -

-
-
-
---css = FILE
-
-
-

- Use the given CSS file instead of the builtin.

-
-
-
-
---external-css
-
-
-

- Place css in external files.

-

- This option can be negated with --no-external-css.

-
-
-
-
---external-js
-
-
-

- Place js in external files.

-

- This option can be negated with --no-external-js.

-
-
-
-
---rfc-base-url
-
-
-


Default value: https://www.rfc-editor.org/rfc/

-

- Base URL for RFC links.

-
-
-
-
---id-base-url
-
-
-


Default value: https://datatracker.ietf.org/doc/html/

-

- Base URL for Internet-Draft links.

-
-
-
-
---rfc-reference-base-url
-
-
-


Default value: https://rfc-editor.org/rfc/

-

- Base URL for RFC reference targets, replacing the target="..." value given in the reference entry.

-
-
-
-
---id-reference-base-url
-
-
-


Default value: https://datatracker.ietf.org/doc/html/

-

- Base URL for I-D reference targets.

-
-
-
-
---metadata-js-url
-
-
-


Default value: metadata.min.js

-

- URL for the metadata script.

-
-
-
-
-
-

-B.9. V2-V3 Converter Options -

-
-
-
---add-xinclude
-
-
-

- Replace reference elements with RFC and Internet-Draft seriesInfo with the appropriate XInclude element.

-
-
-
-
---draft-revs, --draft-revisions
-
-
-

- Reference explicit draft revisions when inserting XIncludes for draft references.

-
-
-
-
---strict
-
-
-

- Be strict about stripping some deprecated attributes.

-
-
-
-
-
-

-B.10. Preptool Options -

-
-
-
---accept-prepped
-
-
-

- Accept already prepped input.

-
-
-
-
-
-
-

-Appendix C. xml2rfc Configuration Files -

-

- Most options have built-in defaults, and the command-line switches above can be used to override those. Additionally, xml2rfc will look for config files in some standard file locations. The option --⁠values will show the places xml2rfc will look for config files on your system (among other information). Any settings in config files will override the program defaults, but will in turn be overridden by command-line options.

-

- The config files are expected to contain lines with option value assignments. Lines with '#' as the first character are considered comments. Here is an example:

-
-
-# ----
-legacy-date-format = true
-add-xinclude = true
-external-js = false
-# ----
-
-
-

- The complete long option names must be used in configuration files; abbreviations will not be recognised (in contrast with how abbreviations are handled during command-line option processing).

-
-
-

-Appendix D. xml2rfc Documentation Template Variables -

-

- - The following variables are available for use in an xml2rfc - manpage Jinja2 template, as of xml2rfc version 3.12.7:

-
-
{{ bare_latin_tags }}:
-
-
-
{{ descriptions }}:
-
The descriptions read from the doc.yaml file -
-
-
{{ element_tags }}:
-
A list of all the element tags in the XML schema -
-
-
{{ elements }}:
-
A list of dictionaries, each with information about one schema element: {"attributes": ..., "children": ..., "deprecated": ..., "deprecated_attributes": ..., "description": ..., "new": ..., "parents": ..., "rnc": ..., "tag": ..., } -
-
-
{{ options }}:
-
A list of dictionaries describing the command-line options -
-
-
{{ schema }}:
-
The full RelaxNG Compact representation of the schema in text form -
-
-
{{ toc_depth }}:
-
ToC depth setting; 1 when running --man, 2 otherwise -
-
-
{{ v3_element_tags }}:
-
A list of v3 element tags, excluding deprecated tags -
-
-
{{ version }}:
-
The xml2rfc version number -
-
-
-
-
-
-

-Author's Address -

-
-
xml2rfc(1)
-
-
-
- - - diff --git a/tests/valid/docfile.py38.html b/tests/valid/docfile.py38.html deleted file mode 100644 index a56eb1f1b..000000000 --- a/tests/valid/docfile.py38.html +++ /dev/null @@ -1,6403 +0,0 @@ - - - - - - -Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.7 - - - - - - - - - - - - - - - - - - - - - - -
Xml2rfc Vocabulary V3 SchemaMay 2022
xml2rfc(1)Informational[Page]
-
-
-
-
Workgroup:
-
xml2rfc(1)
-
Author:
-
-
-
xml2rfc(1)
-
-
-
-
-

Xml2rfc Vocabulary Version 3 Schema
xml2rfc release 3.12.7

-
-

Abstract

-

- This document provides information about the XML schema implemented in this release of xml2rfc, and the individual elements of that schema. The document is generated from the RNG schema file that is part of the xml2rfc distribution, so schema information in this document should always be in sync with the schema in actual use. The textual descriptions depend on manual updates in order to reflect the implementation.

-
-
-
- ▲

-Table of Contents -

- -
-
-
-

-1. Introduction -

-

- Most elements listed in this documentation will have a "Content schema" entry. This shows the permitted content for the element, expressed in RelaxNG Compact Notation [RNC]. For relatively trivial cases such as the ones in this document, the notation is quite straightforward, and resembles simple regular expressions, but with element names as atoms, instead of individual characters as atoms. A trailing '*' indicates zero or more instances; '+' indicates one or more, '?' indicates zero or one. '|' separates choices within a parenthesized group, and ',' separates entries in a sequence.

-

- Some attributes which are valid according to the schema are not listed in this documentation, mostly because they primarily are used by the preptool, and are not useful to document authors.

-

- Elements and attributes that have been introduced after the publication of the original schema version 3 specification, [RFC7991], have been marked with '(New)' in this document.

-

- For an introduction to the v3 schema, with suggestions on how to transition from v2, see [INTRO-TO-V3].

-

- The latest version of this documentation is available in HTML form at https://xml2rfc.ietf.org/xml2rfc-doc.

-

- This documentation applies to xml2rfc version 3.12.7.

-
-
-

-2. Schema Version 3 Elements -

-
-
-

-2.1. <abstract> -

-

- Contains the Abstract of the document. See [RFC7322] for more information on restrictions for the Abstract.

-

This element can be a child element of <front>.

-
-
Content schema:
-
( dl | ol | t | ul )+ -
-
-
-
-
-

-2.1.1. "anchor" Attribute -

-

Document-wide unique identifier for this <abstract> element.

-
-
-
-
-
-
-

-2.2. <address> -

-

- Provides address information for the author.

-

This element can be a child element of <author> and <contact>.

-
-
Content schema:
-
- postal?, phone?, email*, uri? -
-
-
-
-
-
-
-

-2.3. <annotation> -

-

- Provides additional prose augmenting a bibliographic reference. This text is intended to be shown after the rest of the generated reference text.

-

This element can be a child element of <reference>.

-
-
Content schema:
-
( text | bcp14 | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* -
-
-
-
-
-
-
-

-2.4. <area> -

-

- Provides information about the IETF area to which this document relates (currently not used when generating documents).

-

- The value ought to be either the full name or the abbreviation of one of the IETF areas as listed on http://www.ietf.org/iesg/area.html. A list of full names and abbreviations will be kept by the RFC Series Editor.

-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.5. <artset> (New) -

-

- This element allows for the support of multiple artwork formats, in order to provide suitable artwork for different output formats.

-

- When multiple <artwork> instances are provided within one <artset> element, the renderer will try to pick the <artwork> instance which is most appropriate for its current output format from the given alternatives.

-

- If more than one <artwork> element with the same "type" is found within an <artset> element, the renderer could select the first one, or possibly choose between the alternative instances based on the output format and some quality of the alternatives that make one more suitable than the others for that particular format, such as size, aspect ratio, etc.

-

This element can be a child element of <aside>, <blockquote>, <dd>, <figure>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
- artwork+ -
-
-
-
-
-

-2.5.1. "anchor" Attribute -

-

Document-wide unique identifier for this <artset> element.

-
-
-
-
-
-
-

-2.6. <artwork> -

-

- This element allows the inclusion of "artwork" in the document. <artwork> provides full control of horizontal whitespace and line breaks; thus, it is used for a variety of things, such as diagrams ("line art") and protocol unit diagrams. Tab characters (U+0009) inside of this element are prohibited.

-

- Alternatively, the "src" attribute allows referencing an external graphics file, such as a vector drawing in SVG or a bitmap graphic file, using a URI. In this case, the textual content acts as a fallback for output representations that do not support graphics; thus, it ought to contain either (1) a "line art" variant of the graphics or (2) prose that describes the included image in sufficient detail.

-

- In order to include alternative artwork expressions for different output formats, you should provide multiple <artwork> elements enclosed within an <artset>. The text renderer will prefer instances with type="ascii-art", while the HTML and PDF renderers will prefer instances with type="svg".

-

- In the v1 and v2 iterations of the schema, the <artwork> element was also used for source code and formal languages; in v3, this is now done with <sourcecode>.

-

- There are at least five ways to include SVG in artwork in Internet- Drafts:

-
    -
  • -

    Inline, by including all of the SVG in the content of the element, such as:

    -
    -
    <artwork type="svg"><svg xmlns="http://www.w3.org/2000/ svg...">
    -
    -
    • -
  • -

    Inline, but using XInclude (see Appendix B.1), such as:

    -
    -
    <artwork type="svg"><xi:include href=...>
    -
    -
    • -
  • -

    - As a data: URI, such as:

    -
    -
    -<artwork type="svg"
-src="data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww...">
-
    -
    -
    • -
  • -

    As a URI to an external entity, such as:

    -
    -
    <artwork type="svg" src="http://www.example.com/...">
    -
    -
    • -
  • -

    As a local file, such as:

    -
    -
    <artwork type="svg" src="diagram12.svg">
    -
    -
    • -
-

- The use of SVG in Internet-Drafts and RFCs is covered in much more detail in [RFC7996].

-

- The above methods for inclusion of SVG art can also be used for including text artwork, but using a data: URI is probably confusing for text artwork.

-

- Formatters that do pagination should attempt to keep artwork on a single page. This is to prevent artwork that is split across pages from looking like two separate pieces of artwork.

-

- See Section 5 for a description of how to deal with issues of using "&" and "<" characters in artwork.

-

This element can be a child element of <artset>, <aside>, <blockquote>, <dd>, <figure>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
( text* | svg ) -
-
-
-
-
-

-2.6.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-

- Controls whether the artwork appears left justified, centered, or right justified.

-
-
-
-
-

-2.6.2. "alt" Attribute -

-

- Alternative text description of the artwork (which is more than just a summary or caption). When the art comes from the "src" attribute and the format of that artwork supports alternate text, the alternative text comes from the text of the artwork itself, not from this attribute. The contents of this attribute are important to readers who are visually impaired, as well as those reading on devices that cannot show the artwork well, or at all.

-
-
-
-
-

-2.6.3. "anchor" Attribute -

-

Document-wide unique identifier for this <artwork> element.

-
-
- -
-
-

-2.6.5. "name" Attribute -

-

- A filename suitable for the contents (such as for extraction to a local file). This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the artwork). Note that the "name" attribute does not need to be unique for <artwork> elements in a document. If multiple <artwork> elements have the same "name" attribute, a processing tool might assume that the elements are all fragments of a single file, and the tool can collect those fragments for later processing.

-
-
-
-
-

-2.6.6. "src" Attribute -

-

- The URI reference of a graphics file [RFC3986], or the name of a file on the local disk. This can be a "data" URI [RFC2397] that contains the contents of the graphics file. Note that the inclusion of art with the "src" attribute depends on the capabilities of the processing tool reading the XML document. Tools need to be able to handle the file: URI, and they should be able to handle http: and https: URIs as well. The prep tool will be able to handle reading the "src" attribute.

-

- If no URI scheme is given in the attribute, the attribute is considered to be a local filename relative to the current directory. Processing tools must be careful to not accept dangerous values for the filename, particularly those that contain absolute references outside the current directory. Document creators should think hard before using relative URIs due to possible later problems if files move around on the disk. Also, documents should most likely use explicit URI schemes wherever possible.

-

- In some cases, the prep tool may remove the "src" attribute after processing its value. See [RFC7998] for a description of this.

-
-
-
-
-

-2.6.7. "type" Attribute -

-

- Specifies the format of the artwork. The value of this attribute is free text with certain values designated as preferred.

-

- The preferred values for <artwork> types are:

-
    -
  • ascii-art -
    • -
  • binary-art -
    • -
  • svg -
    • -
-

- Values that don't describe the format, such as "call-flow" or "hex-dump" were mentioned in [RFC7991], but are not supported here; they are instead candidates for use with another future attribute to describe the artwork content.

-

- The RFC Series Editor will maintain a complete list of the preferred values on the RFC Editor web site, and that list is expected to be updated over time. Thus, a consumer of v3 XML should not cause a failure when it encounters an unexpected type or no type is specified. The table will also indicate which type of art can appear in plain-text output (for example, type="svg" cannot).

-
-
- -
-
-
-
-

-2.7. <aside> -

-

- This element is a container for content that is semantically less important or tangential to the content that surrounds it.

-

This element can be a child element of <dd> and <section>.

-
-
Content schema:
-
( artset | artwork | blockquote | dl | figure | iref | ol | t | table | ul )* -
-
-
-
-
-

-2.7.1. "anchor" Attribute -

-

Document-wide unique identifier for this <aside> element.

-
-
-
-
-
-
-

-2.8. <author> -

-

- Provides information about a document's author. This is used both for the document itself (at the beginning of the document) and for referenced documents.

-

- The <author> elements contained within the document's <front> element are used to fill the boilerplate and also to generate the "Author's Address" section (see [RFC7322]).

-

- Note that an "author" can also be just an organization (by not specifying any of the "name" attributes, but adding the <organization> child element).

-

- Furthermore, the "role" attribute can be used to mark an author as "editor". This is reflected both on the front page and in the "Author's Address" section, as well as in bibliographic references. Note that this specification does not define a precise meaning for the term "editor".

-

This element can be a child element of <front> and <section>.

-
-
Content schema:
-
- organization?, address? -
-
-
-
-
-

-2.8.1. "anchor" Attribute (New) -

-

Document-wide unique identifier for this <author> element.

-
-
-
-
-

-2.8.2. "asciiFullname" Attribute -

-

- The Latin script equivalent of the author's full name.

-
-
-
-
-

-2.8.3. "asciiInitials" Attribute -

-

- The Latin script equivalent of the author's initials, to be used in conjunction with the separately specified asciiSurname.

-
-
-
-
-

-2.8.4. "asciiSurname" Attribute -

-

- The Latin script equivalent of the author's surname, to be used in conjunction with the separately specified asciiInitials.

-
-
-
-
-

-2.8.5. "fullname" Attribute -

-

- The full name (used in the automatically generated "Author's Address" section). Although this attribute is optional, if one or more of the "asciiFullname", "asciiInitials", or "asciiSurname" attributes does not have values, the "fullname" attribute is required.

-
-
-
-
-

-2.8.6. "initials" Attribute -

-

- An abbreviated variant of the given name(s), to be used in conjunction with the separately specified surname. It usually appears on the front page, in footers, and in references.

-

- Some processors will post-process the value -- for instance, when it only contains a single letter (in which case they might add a trailing dot). Relying on this kind of post-processing can lead to results varying across formatters and thus ought to be avoided.

-
-
-
-
-

-2.8.7. "role" Attribute -

-

- Specifies the role the author had in creating the document.

-
-
-
-
-

-2.8.8. "surname" Attribute -

-

- The author's surname, to be used in conjunction with the separately specified initials. It usually appears on the front page, in footers, and in references.

-
-
-
-
-
-
-

-2.9. <back> -

-

- Contains the "back" part of the document: the references and appendices. In <back>, <section> elements indicate appendices.

-

This element can be a child element of <rfc>.

-
-
Content schema:
-
- displayreference*, references*, section* -
-
-
-
-
-
-
-

-2.10. <bcp14> -

-

- Marks text that are phrases defined in [BCP14] such as "MUST", "SHOULD NOT", and so on. When shown in some of the output representations, the text in this element might be highlighted. The use of this element is optional.

-

- This element is only to be used around the actual phrase from BCP 14, not the full definition of a requirement. For example, it is correct to say "The packet <bcp14>MUST</bcp14> be dropped.", but it is not correct to say "<bcp14>The packet MUST be dropped.</bcp14>".

-

This element can be a child element of <annotation>, <blockquote>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, and <tt>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.11. <blockquote> -

-

- Specifies that a block of text is a quotation.

-

This element can be a child element of <aside>, <li>, and <section>.

-
-
Content schema:
-
( ( artset | artwork | dl | figure | ol | sourcecode | t | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )+ ) -
-
-
-
-
-

-2.11.1. "anchor" Attribute -

-

Document-wide unique identifier for this <blockquote> element.

-
-
-
-
-

-2.11.2. "cite" Attribute -

-

- The source of the citation. This must be a URI. If the "quotedFrom" attribute is given, this URI will be used by processing tools as the link for the text of that attribute.

-
-
-
-
-

-2.11.3. "quotedFrom" Attribute -

-

- Name of person or document the text in this element is quoted from. A formatter should render this as visible text at the end of the quotation.

-
-
-
-
-
-
-

-2.12. <boilerplate> -

-

- Holds the boilerplate text for the document. This element is filled in by the prep tool.

-

- This element contains <section> elements. Every <section> element in this element must have the "numbered" attribute set to "false".

-

This element can be a child element of <front>.

-
-
Content schema:
-
- section+ -
-
-
-
-
-
-
-

-2.13. <br> -

-

- Inserts a forced break. Use sparingly. In most situations, it's better to insert U+200B, ZERO WIDTH SPACE, in order to encourage line breaking at a point where it would otherwise not occur.

-

This element can be a child element of <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <t>, <td>, <th>, <title>, and <tt>.

-
-
Content schema:
-
empty -
-
-
-
-
-
-
-

-2.14. <city> -

-

- Gives the city name in a postal address.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.14.1. "ascii" Attribute -

-

- The ASCII equivalent of the <city> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.15. <cityarea> (New) -

-

- Where postal addresses use city subdivisions, these are mapped to the <cityarea> element. Korean addresses would use this for a city district, for instance. Countries known to use this element are Ascension Island, China, Iran, South Korea, and Thailand.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.15.1. "ascii" Attribute -

-

- The ASCII equivalent of the <cityarea> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.16. <code> -

-

- Gives the postal region code.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.16.1. "ascii" Attribute -

-

- The ASCII equivalent of the <code> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.17. <contact> (New) -

-

- Provides information about contributors. This element can be used inline within a <t>, and will be rendered with name only, similarly to how <author> is rendered in a <reference>, or it can be used as a direct child of <section>, where it will be rendered the same way as an author address block within the "Authors' Addresses" section.

-

- Note that a "contact" can also be just an organization (by not specifying any of the "name" attributes, but adding the <organization> child element).

-

This element can be a child element of <section> and <t>.

-
-
Content schema:
-
- organization?, address? -
-
-
-
-
-

-2.17.1. "anchor" Attribute -

-

Document-wide unique identifier for this <contact> element.

-
-
-
-
-

-2.17.2. "asciiFullname" Attribute -

-

- The Latin script equivalent of the contact's full name.

-
-
-
-
-

-2.17.3. "asciiInitials" Attribute -

-

- The Latin script equivalent of the contact's initials, to be used in conjunction with the separately specified asciiSurname.

-
-
-
-
-

-2.17.4. "asciiSurname" Attribute -

-

- The Latin script equivalent of the contact's surname, to be used in conjunction with the separately specified asciiInitials.

-
-
-
-
-

-2.17.5. "fullname" Attribute -

-

- The full name. Although this attribute is optional, if one or more of the "asciiFullname", "asciiInitials", or "asciiSurname" attributes does not have values, the "fullname" attribute is required.

-
-
-
-
-

-2.17.6. "initials" Attribute -

-

- An abbreviated variant of the given name(s), to be used in conjunction with the separately specified surname.

-
-
-
-
-

-2.17.7. "surname" Attribute -

-

- The contact's surname, to be used in conjunction with the separately specified initials.

-
-
-
-
-
-
-

-2.18. <country> -

-

- Specifies the country name in a postal address. All common and official country names should be recognized; in addition two- and three-letter country codes according to ISO 3166 are recognized.

-

- xml2rfc has a help option which will list all names and country codes it recognizes as valid country names: xml2rfc --country-help .

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.18.1. "ascii" Attribute -

-

- The ASCII equivalent of the <country> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.19. <cref> -

-

- Represents a comment.

-

- Comments can be used in a document while it is work in progress. They might appear either inline and visually highlighted, at the end of the document, or not at all, depending on the formatting tool.

-

This element can be a child element of <annotation>, <blockquote>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, .

-
-
Content schema:
-
( text | br | em | eref | strong | sub | sup | tt | xref )* -
-
-
-
-
-

-2.19.1. "anchor" Attribute -

-

Document-wide unique identifier for this <cref> element.

-
-
-
-
-

-2.19.2. "display" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Suggests whether or not the comment should be displayed by formatting tools. This might be set to "false" if you want to keep a comment in a document after the contents of the comment have already been dealt with.

-
-
-
-
-

-2.19.3. "source" Attribute -

-

- Holds the "source" of a comment, such as the name or the initials of the person who made the comment.

-
-
-
-
-
-
-

-2.20. <date> -

-

- Provides information about the publication date. This element is used for two cases: the boilerplate of the document being produced, and inside bibliographic references that use the <front> element.

-
-
Bibliographic references:
-
-

(New) In order to be able to specify fuzzy dates, such as "2002-2003", "Second quarter 2010", etc., the date element is now permitted to have text content in addition to the "year", "month", and "day" attributes. If there is only text content, it will be rendered as is. If there is both text content and date components, both will be rendered, with the expanded date components in parentheses.

-
-
-
Boilerplate for Internet-Drafts and RFCs:
-
-

This element defines the date of publication for the current document (Internet-Draft or RFC). When producing Internet-Drafts, the prep tool uses this date to compute the expiration date (see [IDGUIDE]). When one or more of "year", "month", or "day" are left out, the prep tool will attempt to use the current system date if the attributes that are present are consistent with that date.

-

In dates in <rfc> elements, the month must be a number or a month in English. The prep tool will silently change text month names to numbers. Similarly, the year must be a four-digit number.

-

When the prep tool is used to create Internet-Drafts, it will warn if the draft has a <date> element in the boilerplate for itself that is more than 3 days away from today. To avoid this problem, authors might simply not include a <date> element in the boilerplate.

-
-
-
-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.20.1. "day" Attribute -

-

- The day of publication.

-
-
-
-
-

-2.20.2. "month" Attribute -

-

- The month of publication.

-
-
-
-
-

-2.20.3. "year" Attribute -

-

- The year of publication.

-
-
-
-
-
-
-

-2.21. <dd> -

-

- The definition part of an entry in a definition list.

-

This element can be a child element of <dl>.

-
-
Content schema:
-
( ( artset | artwork | aside | dl | figure | ol | sourcecode | t | table | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )+ ) -
-
-
-
-
-

-2.21.1. "anchor" Attribute -

-

Document-wide unique identifier for this <dd> element.

-
-
-
-
-
-
-

-2.22. <displayreference> -

-

- This element gives a mapping between the anchor of a reference and a name that will be displayed instead. This allows authors to display more mnemonic anchor names for automatically included references. The mapping in this element only applies to <xref> elements whose format is "default". For example, if the reference uses the anchor "RFC6949", the following would cause that anchor in the body of displayed documents to be "RFC-dev":

-
-
<displayreference target="RFC6949" to="RFC-dev"/>
-
-

- If a reference section is sorted, this element changes the sort order.

-

This element can be a child element of <back>.

-
-
-

-2.22.1. "target" Attribute (Required) -

-

- This attribute must be the name of an anchor in a <reference> or <referencegroup> element.

-
-
-
-
-

-2.22.2. "to" Attribute (Required) -

-

- This attribute is a name that will be displayed as the anchor instead of the anchor that is given in the <reference> element. The string given must start with one of the following characters: 0-9, a-z, or A-Z. The other characters in the string must be 0-9, a-z, A-Z, "-", ".", or "_".

-
-
-
-
-
-
-

-2.23. <dl> -

-

- A definition list. Each entry has a pair of elements: a term (<dt>) and a definition (<dd>). (This is slightly different and simpler than the model used in HTML, which allows for multiple terms for a single definition.)

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
( dt, dd )+ -
-
-
-
-
-

-2.23.1. "anchor" Attribute -

-

Document-wide unique identifier for this <dl> element.

-
-
-
-
-

-2.23.2. "indent" Attribute (New) -

-
-
Default value:
-
"3" -
-
-
-

- Indicates the indentation to be used for the rendering of the second and following lines of the item (the first line starts with the term, and is not indented). The indentation amount is interpreted as characters when rendering plain-text documents, and en-space units when rendering in formats that have richer typographic support such as HTML or PDF. One en-space is assumed to be the length of 0.5 em-space in CSS units.

-
-
-
-
-

-2.23.3. "newline" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- The "newline" attribute defines whether or not the term appears on the same line as the definition. newline="false" indicates that the term is to the left of the definition, while newline="true" indicates that the term will be on a separate line.

-
-
-
-
-

-2.23.4. "spacing" Attribute -

-
-
Possible values:
-
( "normal" | "compact" ) -
-
-
Default value:
-
"normal" -
-
-
-

- Defines whether or not there is a blank line between entries. spacing="normal" indicates a single blank line, while spacing="compact" indicates no blank line between entries.

-
-
-
-
-
-
-

-2.24. <dt> -

-

- The term being defined in a definition list.

-

This element can be a child element of <dl>.

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-

-2.24.1. "anchor" Attribute -

-

Document-wide unique identifier for this <dt> element.

-
-
-
-
-
-
-

-2.25. <em> -

-

- Indicates text that is semantically emphasized. In HTML and PDF rendering, text enclosed within this element will be displayed as italic after processing; in text rendering it will be preceded and folled by an underline character. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | br | cref | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.26. <email> -

-

- Provides an email address.

-

- The value is expected to be the addr-spec defined in Section 2 of [RFC6068].

-

- (New) In [RFC7991], only zero or one instance of this element was permitted in an address. In the current schemal, now multiple email addresses are permitted.

-

This element can be a child element of <address>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.26.1. "ascii" Attribute -

-

- The ASCII equivalent of the author's email address. This is only used if the email address has any internationalized components.

-
-
-
-
-
-
-

-2.27. <eref> -

-

- Represents an "external" link (as specified in the "target" attribute). This is useful for embedding URIs in the body of a document.

-

- If the <eref> element has non-empty text content, the content is used as the displayed text that is linked. Otherwise, the value of the "target" attribute is used as the displayed text.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, .

-
-
Content schema:
-
text -
-
-
-
-
-

-2.27.1. "brackets" Attribute (New) -

-
-
Possible values:
-
( "none" | "angle" ) -
-
-
Default value:
-
"none" -
-
-
-

- Determines the type of brackets that an eref will be rendered with. "angle" will render with angle brackets, and "none" will render with no brackets in HTML and PDF, and with parentheses by the text renderer.

-
-
-
-
-

-2.27.2. "target" Attribute (Required) -

-

- URI of the link target [RFC3986]. This must begin with a scheme name (such as "https://") and thus not be relative to the URL of the current document.

-
-
-
-
-
-
-

-2.28. <extaddr> (New) -

-

- Extra address information. This element can be used for address parts more specific than a street, for instance apartment numbers, suite numbers, building parts, etc.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.28.1. "ascii" Attribute -

-

- The ASCII equivalent of the <extaddr> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.29. <figure> -

-

- Contains a figure with a caption with the figure number. If the element contains a <name> element, the caption will also show that name.

-

This element can be a child element of <aside>, <blockquote>, <dd>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
- name?, iref*, ( artset | artwork | sourcecode )+ -
-
-
-
-
-

-2.29.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-
-
- -
-
-

-2.29.3. "anchor" Attribute -

-

Document-wide unique identifier for this <figure> element.

-
-
- - -
-
-

-2.29.6. "suppress-title" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-
-
-
-
-

-2.29.7. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
- -
-
-
-
-

-2.30. <front> -

-

- Represents the "front matter" metadata (such as author information), the Abstract, and additional notes.

-

- A <front> element may have more than one <seriesInfo> element. Each should contain a "name" attribute with the series name and a "value" attribute with the series number; other uses of <front><seriesInfo> described in [RFC7991] are deprecated.

-

This element can be a child element of <reference> and <rfc>.

-
-
Content schema:
-
- title, seriesInfo*, author+, date?, area*, workgroup*, keyword*, abstract?, note*, boilerplate?, toc? -
-
-
-
-
-
-
-

-2.31. <iref> -

-

- Provides terms for the document's index.

-

- Index entries can be either regular entries (when just the "item" attribute is given) or nested entries (by specifying "subitem" as well), grouped under a regular entry.

-

- Index entries generally refer to the exact place where the <iref> element occurred. An exception is the occurrence as a child element of <section>, in which case the whole section is considered to be relevant for that index entry. In some formats, index entries of this type might be displayed as ranges.

-

- When the prep tool is creating index content, it collects the items in a case-sensitive fashion for both the item and subitem level.

-

This element can be a child element of <annotation>, <aside>, <blockquote>, <dd>, <dt>, <em>, <figure>, <li>, <name>, <section>, <strong>, <sub>, <sup>, <t>, <table>, <td>, <th>, <tt>, .

-
-
Content schema:
-
empty -
-
-
-
-
-

-2.31.1. "item" Attribute (Required) -

-

- The item to include.

-
-
-
-
-

-2.31.2. "primary" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Setting this to "true" declares the occurrence as "primary", which might cause it to be highlighted in the index. There is no restriction on the number of occurrences that can be "primary".

-
-
-
-
-

-2.31.3. "subitem" Attribute -

-

- The subitem to include.

-
-
-
-
-
-
-

-2.32. <keyword> -

-

- Specifies a keyword applicable to the document.

-

- Note that each element should only contain a single keyword; for multiple keywords, the element can simply be repeated.

-

- Keywords are used both in the RFC Index and in the metadata of generated document representations. They are not reflected in the HTML, PDF, or text rendering of the document.

-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.33. <li> -

-

- A list element, used in <ol> and <ul>.

-

This element can be a child element of <ol> and <ul>.

-
-
Content schema:
-
( ( artset | artwork | blockquote | dl | figure | ol | sourcecode | t | table | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )+ ) -
-
-
-
-
-

-2.33.1. "anchor" Attribute -

-

Document-wide unique identifier for this <li> element.

-
-
-
-
- -
-
-

-2.35. <middle> -

-

- Represents the main content of the document.

-

This element can be a child element of <rfc>.

-
-
Content schema:
-
- section+ -
-
-
-
-
-
-
-

-2.36. <name> -

-

- The name of the containing (parent) element, for instance the section name. This name can include inline markup (for example, including references or making some characters use a fixed-width font).

-

This element can be a child element of <figure>, <note>, <references>, <section>, <table>, .

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.37. <note> -

-

- Creates an unnumbered, titled block of text that appears after the Abstract.

-

- It is usually used for additional information to reviewers (Working Group information, mailing list, ...) or for additional publication information such as "IESG Notes".

-

This element can be a child element of <front>.

-
-
Content schema:
-
- name?, ( dl | ol | t | ul )+ -
-
-
-
-
-

-2.37.1. "removeInRFC" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- If set to "true", this note is marked in the prep tool with text indicating that it should be removed before the document is published as an RFC. That text will be "This note is to be removed before publishing as an RFC."

-
-
-
-
-

-2.37.2. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
-
-
-
-
-

-2.38. <ol> -

-

- An ordered list. The labels on the items will be either a number or a letter, depending on the value of the style attribute.

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
- li+ -
-
-
-
-
-

-2.38.1. "anchor" Attribute -

-

Document-wide unique identifier for this <ol> element.

-
-
-
-
-

-2.38.2. "group" Attribute -

-

- When the prep tool sees an <ol> element with a "group" attribute that has already been seen, it continues the numbering of the list from where the previous list with the same group name left off. If an <ol> element has both a "group" attribute and a "start" attribute, the group's numbering is reset to the given start value.

-
-
-
-
-

-2.38.3. "indent" Attribute (New) -

-
-
Possible values:
-
( text | "adaptive" ) -
-
-
Default value:
-
"adaptive" -
-
-
-

- The indentation of the list elements relative to the start of the list item number. With indent='adaptive', the width of the widest list item number will determine the indentation. With a numeric value, that value will be used to determine the amount of indentation. The indentation amount is interpreted as characters when rendering plain-text documents, and en-space units when rendering in formats that have richer typographic support such as HTML or PDF. One en-space is assumed to be the length of 0.5 em-space in CSS units. Only non-negative integer amounts of indentation are supported.

-
-
-
-
-

-2.38.4. "spacing" Attribute -

-
-
Possible values:
-
( "normal" | "compact" ) -
-
-
Default value:
-
"normal" -
-
-
-

- Defines whether or not there is a blank line between entries. spacing="normal" indicates a single blank line, while spacing="compact" indicates no blank line between entries.

-
-
-
-
-

-2.38.5. "start" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The ordinal value at which to start the list. This defaults to "1" and must be an integer of value 0 or greater.

-
-
-
-
-

-2.38.6. "type" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The type of the labels on list items. If the length of the type value is 1, the meaning is the same as it is for HTML:

-
-
a
-
- Lowercase letters (a, b, c, ...) -
-
-
-
-
A
-
- Uppercase letters (A, B, C, ...) -
-
-
-
-
1
-
- Decimal numbers (1, 2, 3, ...) -
-
-
-
-
i
-
- Lowercase Roman numerals (i, ii, iii, ...) -
-
-
-
-
I
-
- Uppercase Roman numerals (I, II, III, ...) -
-
-
-

- For types "a" and "A", after the 26th entry, the numbering starts at "aa"/"AA", then "ab"/"AB", and so on.

-

- If the length of the type value is greater than 1, the value must contain a percent-encoded indicator and other text. The value is a free-form text that allows counter values to be inserted using a "percent-letter" format. For instance, "[REQ%d]" generates labels of the form "[REQ1]", where "%d" inserts the item number as a decimal number.

-

- The following formats are supported:

-
-
%c
-
- Lowercase letters (a, b, c, ...) -
-
-
-
-
%C
-
- Uppercase letters (A, B, C, ...) -
-
-
-
-
%d
-
- Decimal numbers (1, 2, 3, ...) -
-
-
-
-
%i
-
- Lowercase Roman numerals (i, ii, iii, ...) -
-
-
-
-
%I
-
- Uppercase Roman numerals (I, II, III, ...) -
-
-
-
-
%p
-
- The list counter of a list item in a parent list (see more below) -
-
-
-
-
%%
-
- Represents a percent sign -
-
-
-

- Other formats are reserved for future use. Only one percent encoding other than "%%" and "%p" is allowed in a type string.

-

- It is an error for the type string to be empty. For bulleted lists, use the <ul> element. For lists that have neither bullets nor numbers, use the <ul> element with the 'empty="true"' attribute.

-

- '%p' may be used in nested ordered lists, where it represents the item number of the parent list item. This lets you say for instance:

-
-
-<ol>
-  <li>List item one</li>
-  <li>
-    <t>Nested list:</t>
-    <ol type='%p%d'>
-      <li>Sublist item 2.1</li>
-      <li>Sublist item 2.2</li>
-    </ol>
-  </li>
-</ol>
-
-
-

which is rendered as:

-
    -
  1. List item one -
    2. -
  2. -

    Nested list

    -
    -
    2.1
    -
    Sublist item 2.1 -
    -
    -
    2.2
    -
    Sublist item 2.2 -
    -
    -
    -
    3. -
-

- Without the '%p' format specifier, you would have to explicitly insert the counter number of the parent item, which could easily result in mismatched numbering if parent list intems were inserted or removed during document editing.

-
-
-
-
-
-
-

-2.39. <organization> -

-

- Specifies the affiliation [RFC7322] of an author.

-

- This information appears both in the "Author's Address" section and on the front page (see [RFC7322] for more information). If the value is long, an abbreviated variant can be specified in the "abbrev" attribute.

-

This element can be a child element of <author> and <contact>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.39.1. "abbrev" Attribute -

-

- Abbreviated variant of the organization name.

-
-
-
-
-

-2.39.2. "ascii" Attribute -

-

- The ASCII equivalent of the <organization> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-

-2.39.3. "asciiAbbrev" Attribute (New) -

-

- The ASCII equivalent of the abbreviated variant of the organization's name.

-
-
-
-
-

-2.39.4. "showOnFrontPage" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Turns off listing of organization with author name on the first document page.

-
-
-
-
-
-
-

-2.40. <phone> -

-

- Represents a phone number.

-

- The value is expected to be the scheme-specific part of a "tel" URI (and so does not include the prefix "tel:"), using the "global-number-digits" syntax. See Section 3 of [RFC3966] for details.

-

This element can be a child element of <address>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.41. <pobox> (New) -

-

- Represents a post office box number.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.41.1. "ascii" Attribute -

-

- The ASCII equivalent of the <pobox> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.42. <postal> -

-

- Contains optional child elements providing postal information. These elements will be displayed in an order that is specific to formatters. A postal address can contain only a set of <street>, <city>, <region>, <code>, and <country> elements, or only an ordered set of <postalLine> elements, but not both.

-

This element can be a child element of <address>.

-
-
Content schema:
-
( ( city | cityarea | code | country | extaddr | pobox | region | sortingcode | street )* | postalLine+ ) -
-
-
-
-
-
-
-

-2.43. <postalLine> -

-

- Represents one line of a postal address. When more than one <postalLine> is given, the prep tool emits them in the order given.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.43.1. "ascii" Attribute -

-

- The ASCII equivalent of the <postalLine> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.44. <refcontent> -

-

- Text that should appear between the title and the date of a reference. The purpose of this element is to obviate the need for abuse of <seriesInfo> in order to add such text.

-

- For example:

-

- <reference anchor="April1"> <front> <title>On Being A Fool</title> <author initials="K." surname="Phunny" fullname="Knot Phunny"/> <date year="2000" month="April"/> </front> <refcontent>Self-published pamphlet</refcontent> </reference>

-

- would render as:

-

- [April1] Phunny, K., "On Being A Fool", Self-published pamphlet, April 2000.

-

This element can be a child element of <reference>.

-
-
Content schema:
-
( text | bcp14 | em | strong | sub | sup | tt )* -
-
-
-
-
-
-
-

-2.45. <reference> -

-

- Represents a bibliographic reference.

-

This element can be a child element of <referencegroup> and <references>.

-
-
Content schema:
-
- stream?, front, ( annotation | refcontent | seriesInfo )* -
-
-
-
-
-

-2.45.1. "anchor" Attribute (Required) -

-

- Document-wide unique identifier for this <reference>. Usually, this will be used both to "label" the reference in the "References" section and as an identifier in links to this reference entry; but see <displayreference (Section 2.22)> for how to change this.

-
-
-
-
-

-2.45.2. "quote-title" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
-

- Specifies whether or not the title in the reference should be quoted. This can be used to prevent quoting, such as on errata.

-
-
-
-
-

-2.45.3. "target" Attribute -

-

- Holds the URI for the reference.

-
-
-
-
-
-
-

-2.46. <referencegroup> -

-

- Represents a list of bibliographic references that will be represented as a single reference. This is most often used to reference STDs and BCPs, where a single reference (such as "BCP 9") may encompass more than one RFC.

-

This element can be a child element of <references>.

-
-
Content schema:
-
- reference+ -
-
-
-
-
-

-2.46.1. "anchor" Attribute (Required) -

-

- Document-wide unique identifier for this <referencegroup>. Usually, this will be used both to "label" the reference group in the "References" section and as an identifier in links to this reference entry; but see <displayreference (Section 2.22)> for how to change this.

-
-
-
-
-

-2.46.2. "target" Attribute (New) -

-

- (New) Holds an URI for the reference group, analogous to the "target" attribute of <reference>. Useful for a STD which consists of multiple RFCs with their own URLs, but also has its own unique URL.

-
-
-
-
-
-
-

-2.47. <references> -

-

- Contains a set of bibliographic references.

-

- In the early days of the RFC Series, there was only one "References" section per RFC. This convention was later changed to group references into two sets, "Normative" and "Informative", as described in [RFC7322]. This vocabulary supports the split with the <name> child element. In general, the title should be either "Normative References" or "Informative References".

-

- The recommended way to include references to RFCs and Internet-Drafts is to use the standard XML XInclude mechanism. Here is an example:

-
-
-<references>
-<name>Normative References</name>
-<!--RTP-->
-<xi:include href=
-"https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3550.xml"/>
-<!--SIP-->
-<xi:include href=
-"https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3261.xml"/>
-</references>
-
-
-

This element can be a child element of <back> and <references>.

-
-
Content schema:
-
- name?, ( references+ | ( reference | referencegroup )* ) -
-
-
-
-
-

-2.47.1. "anchor" Attribute -

-

- An optional user-supplied identifier for this set of references.

-
-
-
-
-

-2.47.2. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
-
-
-
-
-

-2.48. <region> -

-

- Provides the region name in a postal address.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.48.1. "ascii" Attribute -

-

- The ASCII equivalent of the <region> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.49. <rfc> -

-

- This is the root element of the xml2rfc vocabulary.

-
-
Content schema:
-
- link*, front, middle, back? -
-
-
-
-
-

-2.49.1. "category" Attribute -

-
-
Possible values:
-
( "std" | "bcp" | "exp" | "info" | "historic" ) -
-
-
-

- Document category

-

- For RFCs, the "category" attribute (Section 2.33.1) determines the "maturity level" (see Section 4 of [RFC2026]). The allowed values are "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for "Historic".

-

- For Internet-Drafts, the "category" attribute is not needed; when supplied, it will appear as "Intended Status". Supplying this information can be useful to reviewers.

-
-
-
-
-

-2.49.2. "consensus" Attribute -

-
-
Possible values:
-
( "no" | "yes" | "false" | "true" ) -
-
-
Default value:
-
"false" -
-
-
-

- Affects the generated boilerplate. Note that the values of "no" and "yes" are deprecated and are replaced by "false" and "true".

-

- See [RFC7841] for more information.

-
-
-
-
-

-2.49.3. "docName" Attribute -

-

- Indicates the draft name (including revision number) for a draft, or the draft from which an RFC derived, for an RFC. Used to insert the <link rel="prev" href="..."> element that points to the precursor of the RFC, in accordance with the intentions of Section 5.6.3 of [RFC7998].

-
-
-
-
-

-2.49.4. "indexInclude" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Specifies whether or not a formatter is requested to include an index in generated files. If the source file has no <iref> elements, an index is never generated. This option is useful for generating documents where the source document has <iref> elements but the author no longer wants an index.

-
-
-
-
-

-2.49.5. "ipr" Attribute -

-

- Represents the Intellectual Property status of the document.

-

- If the attribute is set to the empty string: <tt>ipr=''</tt>, it is assumed that this is not a regular IETF/IRTF/IAB/ISE document, and the document header content is reduced. This is considered a feature by a few other standards organisations that have used xml2rfc to format their standards documents.

-
-
-
-
-

-2.49.6. "iprExtract" Attribute -

-

- Identifies a single section within the document for which extraction "as is" is explicitly allowed (only relevant for historic values of the "ipr).

-
-
-
-
-

-2.49.7. "number" Attribute -

-

- Used to determine wheher to produce an RFC or an Internet-Draft.

-
-
-
-
-

-2.49.8. "obsoletes" Attribute -

-

- A comma-separated list of RFC numbers or Internet-Draft names.

-

- The prep tool will parse the attribute value so that incorrect references can be detected.

-
-
-
-
-

-2.49.9. "prepTime" Attribute -

-

- The date that the XML was processed by a prep tool. This is included in the XML file just before it is saved to disk. The value is formatted using the "date-time" format defined in Section 5.6 of [RFC3339]. The "time-offset" should be "Z".

-
-
-
-
-

-2.49.10. "seriesNo" Attribute -

-

- Deprecated; instead, use the "value" in <seriesInfo>.

-
-
-
-
-

-2.49.11. "sortRefs" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Specifies whether or not the prep tool will sort the references in each reference section.

-
-
-
-
-

-2.49.12. "submissionType" Attribute -

-
-
Possible values:
-
( "IETF" | "IAB" | "IRTF" | "independent" ) -
-
-
Default value:
-
"IETF" -
-
-
-

- The document stream, as described in [RFC7841]. (The RFC Series Editor may change the list of allowed values in the future.)

-
-
-
-
-

-2.49.13. "symRefs" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Specifies whether or not a formatter is requested to use symbolic references (such as "RFC2119"). If the value for this is "false", the references come out as numbers (such as "[3]").

-
-
-
-
-

-2.49.14. "tocDepth" Attribute -

-
-
Default value:
-
"3" -
-
-
-

- Specifies the number of levels of headings that a formatter is requested to include in the table of contents.

-
-
-
-
-

-2.49.15. "tocInclude" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- Specifies whether or not a formatter is requested to include a table of contents in generated files.

-
-
-
-
-

-2.49.16. "updates" Attribute -

-

- A comma-separated list of RFC numbers or Internet-Draft names.

-

- The prep tool will parse the attribute value so that incorrect references can be detected.

-
-
-
-
-

-2.49.17. "version" Attribute -

-

- Specifies the version of xml2rfc syntax used in this document. The only expected value (for now) is "3".

-
-
-
-
-
-
-

-2.50. <section> -

-

- Represents a section (when inside a <middle> element) or an appendix (when inside a <back> element).

-

- Subsections are created by nesting <section> elements inside <section> elements. Sections are allowed to be empty.

-

This element can be a child element of <back>, <boilerplate>, <middle>, <section>, and <toc>.

-
-
Content schema:
-
- name?, ( artset | artwork | aside | author | blockquote | contact | dl | figure | iref | ol | sourcecode | t | table | ul )*, section* -
-
-
-
-
-

-2.50.1. "anchor" Attribute -

-

Document-wide unique identifier for this <section> element.

-
-
-
-
-

-2.50.2. "numbered" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"true" -
-
-
-

- If set to "false", the formatter is requested to not display a section number. The prep tool will verify that such a section is not followed by a numbered section in this part of the document. Descendant sections of unnumbered sections are unnumbered by definition. (New) Both top-level <section>s and other <section>s may have numbered='false'.

-
-
-
-
-

-2.50.3. "removeInRFC" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- If set to "true", this section is marked in the prep tool with text indicating that it should be removed before the document is published as an RFC. That text will be "This section is to be removed before publishing as an RFC."

-
-
-
-
-

-2.50.4. "title" Attribute -

-

Deprecated. Use the <name> element instead.

-
-
-
-
-

-2.50.5. "toc" Attribute -

-
-
Possible values:
-
( "include" | "exclude" | "default" ) -
-
-
Default value:
-
"default" -
-
-
-

- Indicates to a formatter whether or not the section is to be included in a table of contents, if such a table of contents is produced. This only takes effect if the level of the section would have appeared in the table of contents based on the "tocDepth" attribute of the <rfc> element, and of course only if the table of contents is being created based on the "tocInclude" attribute of the <rfc> element. If this is set to "exclude", any section below this one will be excluded as well. The "default" value indicates inclusion of the section if it would be included by the tocDepth attribute of the <rfc> element.

-
-
-
-
-
-
-

-2.51. <seriesInfo> -

-

- Specifies the document series in which this document appears, and also specifies an identifier within that series.

-

- A processing tool determines whether it is working on an RFC or an Internet-Draft by inspecting the "name" attribute of a <seriesInfo> element inside the <front> element inside the <rfc> element, looking for "RFC" or "Internet-Draft". (Specifying neither value in any of the <seriesInfo> elements can be useful for producing other types of documents but is out of scope for this specification.)

-

- It is invalid to have multiple <seriesInfo> elements inside the same <front> element containing the same "name" value. Some combinations of <seriesInfo> "name" attribute values make no sense, such as having both <seriesInfo name="rfc"/> and <seriesInfo name="Internet-Draft"/> in the same <front> element.

-

This element can be a child element of <front> and <reference>.

-
-
Content schema:
-
empty -
-
-
-
-
-

-2.51.1. "asciiName" Attribute -

-

- The ASCII equivalent of the name field.

-
-
-
-
-

-2.51.2. "asciiValue" Attribute -

-

- The ASCII equivalent of the value field.

-
-
-
-
-

-2.51.3. "name" Attribute (Required) -

-

- The name of the series. Some values in use by the IETF community are "RFC", "Internet-Draft", and "DOI", but other names such as "ISO", "W3C" for exist for other standardisation organisations.

-
-
- -
-
-

-2.51.5. "stream" Attribute -

-
-
Possible values:
-
( "IETF" | "IAB" | "IRTF" | "independent" ) -
-
-
-

- Deprecated. Use the <stream (Section 2.54)> element instead.

-
-
-
-
-

-2.51.6. "value" Attribute (Required) -

-

- The identifier within the series specified by the "name" attribute.

-

- For BCPs, FYIs, RFCs, and STDs, this is the number within the series.

-

- For Internet-Drafts, it is the full draft name (ending with the two-digit version number).

-

- For DOIs, the value is given, such as "10.17487/rfc1149", as described in [RFC7669].

-

- The name in the value should be the document name without any file extension.

-
-
-
-
-
-
-

-2.52. <sortingcode> (New) -

-

- A sorting code is related to postal codes in that it is used in addresses to allow sorting, for example to route mail to a certain postal centre or to distinguish streets with the same name in two different areas of the same settlement.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.52.1. "ascii" Attribute -

-

- The ASCII equivalent of the <sortingcode> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.53. <sourcecode> -

-

- This element allows the inclusion of source code into the document.

-

- When rendered, source code is always shown in a monospace font. When <sourcecode> is a child of <figure> or <section>, it provides full control of horizontal whitespace and line breaks. When formatted, it is indented relative to the left margin of the enclosing element. It is thus useful for source code and formal languages (such as ABNF [RFC5234] or the RNC notation used in this document). (When <sourcecode> is a child of other elements, it flows with the text that surrounds it.) Tab characters (U+0009) inside of this element are prohibited.

-

- For artwork such as character-based art, diagrams of message layouts, and so on, use the <artwork> element instead.

-

- Output formatters that do pagination will attempt to keep source code on a single page. This is to prevent source code that is split across pages from looking like two separate pieces of code.

-

This element can be a child element of <blockquote>, <dd>, <figure>, <li>, <section>, <td>, and <th>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.53.1. "anchor" Attribute -

-

Document-wide unique identifier for this <sourcecode> element.

-
-
-
-
-

-2.53.2. "markers" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Indicates whether "<CODE BEGINS>" and "<CODE ENDS>" markers, as introduced by [RFC6087], should be generated when rendering the <sourcecode> element. The alternative is to include these explicitly inside the element, but that would necessitate extra code to strip these, when extracting code from the XML source.

-
-
-
-
-

-2.53.3. "name" Attribute -

-

- A filename suitable for the contents (such as for extraction to a local file). This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code). Note that the "name" attribute does not need to be unique for <sourcecode> elements in a document. If multiple <sourcecode> elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.

-
-
-
-
-

-2.53.4. "src" Attribute -

-

- The URI reference of a source file [RFC3986].

-

- It is an error to have both a "src" attribute and content in the <sourcecode> element.

-
-
-
-
-

-2.53.5. "type" Attribute -

-

- Specifies the type of the source code. The value of this attribute is free text with certain values designated as preferred.

-

- Most of the preferred values for <sourcecode> types are language names, in a wide sense, such as "abnf", "asn.1", "bash", "c++", etc.

-

- The RFC Series Editor maintains a list of the preferred values on the RFC Editor web site at https://www.rfc-editor.org/materials/sourcecode-types.txt, and that list is updated over time. Thus, a consumer of v3 XML should not cause a failure when it encounters an unexpected type or no type is specified.

-
-
-
-
-
-
-

-2.54. <stream> (New) -

-

- Indicates which stream an RFC belongs to.

-

This element can be a child element of <reference>.

-
-
Content schema:
-
( "IETF" | "IAB" | "IRTF" | "independent" )? -
-
-
-
-
-
-
-

-2.55. <street> -

-

- Provides a street address.

-

This element can be a child element of <postal>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.55.1. "ascii" Attribute -

-

- The ASCII equivalent of the <street> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.56. <strong> -

-

- Indicates text that is semantically strong. In HTML and PDF rendering, text enclosed within this element will be displayed as bold after processing; in text rendering it will be preceeded and followed by an asterisk. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.57. <sub> -

-

- Causes the text to be displayed as subscript, approximately half a letter-height lower than normal text, in HTML and PDF rendering. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.58. <sup> -

-

- Causes the text to be displayed as superscript, approximately half a letter-height higher than normal text, in HTML and PDF rendering. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | cref | em | eref | iref | strong | sub | sup | tt | xref )* -
-
-
-
-
-
-
-

-2.59. <t> -

-

- Contains a paragraph of text.

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
( text | bcp14 | br | contact | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* -
-
-
-
-
-

-2.59.1. "anchor" Attribute -

-

- Document-wide unique identifier for this paragraph.

-
-
-
-
-

-2.59.2. "hangText" Attribute -

-

- Deprecated. Instead, use <dd> inside of a definition list (<dl>).

-
-
-
-
-

-2.59.3. "indent" Attribute (New) -

-
-
Default value:
-
"0" -
-
-
-

- Indicates any extra amount of indentation to be used when rendering the paragraph of text. The indentation amount is interpreted as characters when rendering plain-text documents, and en-space units when rendering in formats that have richer typographic support such as HTML or PDF. One en-space is assumed to be the length of 0.5 em-space in CSS units. Only non-negative integer amounts of indentation are supported.

-
-
-
-
-

-2.59.4. "keepWithNext" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Acts as a hint to the output formatters that do pagination to do a best-effort attempt to keep the paragraph with the next element, whatever that happens to be. For example, for HTML output @media print CSS might translate this to page-break-after: avoid. For PDF, the paginator could attempt to keep the paragraph with the next element. Note: this attribute is strictly a hint and not always actionable.

-
-
-
-
-

-2.59.5. "keepWithPrevious" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Acts as a hint to the output formatters that do pagination to do a best-effort attempt to keep the paragraph with the previous element, whatever that happens to be. For example, for HTML output @media print CSS might translate this to page-break-before: avoid. For PDF, the paginator could attempt to keep the paragraph with the previous element. Note: this attribute is strictly a hint and not always actionable.

-
-
-
-
-
-
-

-2.60. <table> -

-

- Contains a table with a caption with the table number. If the element contains a <name> element, the caption will also show that name.

-

- Inside the <table> element there is, optionally, a <thead> element to contain the rows that will be the table's heading and, optionally, a <tfoot> element to contain the rows of the table's footer. If the XML is converted to a representation that has page breaks (such as PDFs or printed HTML), the header and footer are meant to appear on each page.

-

This element can be a child element of <aside>, <dd>, <li>, and <section>.

-
-
Content schema:
-
- name?, iref*, thead?, tbody+, tfoot? -
-
-
-
-
-

-2.60.1. "align" Attribute (New) -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"center" -
-
-
-

- Controls whether the table appears left justified, centered, or right justified. The caption will be centered under the table, and the combined table and caption will be aligned according to the "align" attribute.

-
-
-
-
-

-2.60.2. "anchor" Attribute -

-

Document-wide unique identifier for this <table> element.

-
-
-
-
-
-
-

-2.61. <tbody> -

-

- A container for a set of body rows for a table.

-

This element can be a child element of <table>.

-
-
Content schema:
-
- tr+ -
-
-
-
-
-

-2.61.1. "anchor" Attribute -

-

Document-wide unique identifier for this <tbody> element.

-
-
-
-
-
-
-

-2.62. <td> -

-

- A cell in a table row.

-

This element can be a child element of <tr>.

-
-
Content schema:
-
( ( artset | artwork | dl | figure | ol | sourcecode | t | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* ) -
-
-
-
-
-

-2.62.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-

- Controls whether the content of the cell appears left justified, centered, or right justified. Note that "center" or "right" will probably only work well in cells with plain text; any other elements might make the contents render badly.

-
-
-
-
-

-2.62.2. "anchor" Attribute -

-

Document-wide unique identifier for this <td> element.

-
-
-
-
-

-2.62.3. "colspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of columns that the cell is to span. For example, setting "colspan='3'" indicates that the cell occupies the same horizontal space as three cells of a row without any "colspan" attributes.

-
-
-
-
-

-2.62.4. "rowspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of rows that the cell is to span. For example, setting "rowspan='3'" indicates that the cell occupies the same vertical space as three rows.

-
-
-
-
-
-
-

-2.63. <tfoot> -

-

- A container for a set of footer rows for a table.

-

This element can be a child element of <table>.

-
-
Content schema:
-
- tr+ -
-
-
-
-
-

-2.63.1. "anchor" Attribute -

-

Document-wide unique identifier for this <tfoot> element.

-
-
-
-
-
-
-

-2.64. <th> -

-

- A cell in a table row. When rendered, this will normally come out in boldface; other than that, there is no difference between this and the <td> element.

-

This element can be a child element of <tr>.

-
-
Content schema:
-
( ( artset | artwork | dl | figure | ol | sourcecode | t | ul )+ | ( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | tt | u | xref )* ) -
-
-
-
-
-

-2.64.1. "align" Attribute -

-
-
Possible values:
-
( "left" | "center" | "right" ) -
-
-
Default value:
-
"left" -
-
-
-

- Controls whether the content of the cell appears left justified, centered, or right justified. Note that "center" or "right" will probably only work well in cells with plain text; any other elements might make the contents render badly.

-
-
-
-
-

-2.64.2. "anchor" Attribute -

-

Document-wide unique identifier for this <th> element.

-
-
-
-
-

-2.64.3. "colspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of columns that the cell is to span. For example, setting "colspan='3'" indicates that the cell occupies the same horizontal space as three cells of a row without any "colspan" attributes.

-
-
-
-
-

-2.64.4. "rowspan" Attribute -

-
-
Default value:
-
"1" -
-
-
-

- The number of rows that the cell is to span. For example, setting "rowspan='3'" indicates that the cell occupies the same vertical space as three rows.

-
-
-
-
-
-
-

-2.65. <thead> -

-

- A container for a set of header rows for a table.

-

This element can be a child element of <table>.

-
-
Content schema:
-
- tr+ -
-
-
-
-
-

-2.65.1. "anchor" Attribute -

-

Document-wide unique identifier for this <thead> element.

-
-
-
-
-
-
-

-2.66. <title> -

-

- Represents the document title.

-

- When this element appears in the <front> element of the current document, the title might also appear in page headers or footers. If it is long (~40 characters), the "abbrev" attribute can be used to specify an abbreviated variant.

-

This element can be a child element of <front>.

-
-
Content schema:
-
( text | br )* -
-
-
-
-
-

-2.66.1. "abbrev" Attribute -

-

- Specifies an abbreviated variant of the document title.

-
-
-
-
-

-2.66.2. "ascii" Attribute -

-

- The ASCII equivalent of the <title> content. - This element may have non-ASCII Latin script content without specifying - an ASCII equivalent, but for other non-ASCII content an ASCII equivalent - is required.

-
-
-
-
-
-
-

-2.67. <toc> (New) -

-

- This element contains the Table of Content. The content of the <toc> element is generated by the preptool based on the "tocInclude" and "tocDepth" attributes of the <rfc> element. As a document author, you should not use <toc> directly.

-

This element can be a child element of <front>.

-
-
Content schema:
-
- section* -
-
-
-
-
-
-
-

-2.68. <tr> -

-

- A row of a table.

-

This element can be a child element of <tbody>, <tfoot>, and <thead>.

-
-
Content schema:
-
( td | th )+ -
-
-
-
-
-

-2.68.1. "anchor" Attribute -

-

Document-wide unique identifier for this <tr> element.

-
-
-
-
-
-
-

-2.69. <tt> -

-

- Causes the text to be displayed in a constant-width font. This element can be combined with other character formatting elements, and the formatting will be additive.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <refcontent>, <strong>, <sub>, <sup>, <t>, <td>, <th>, and <xref>.

-
-
Content schema:
-
( text | bcp14 | br | cref | em | eref | iref | strong | sub | sup | xref )* -
-
-
-
-
-
-
-

-2.70. <u> (New) -

-

- In xml2rfc vocabulary version 3, the elements <author>, <organisation>, <street>, <city>, <region>, <code>, <country>, <postalLine>, <email>, <seriesInfo>, and <title> may contain non- ascii characters for the purpose of rendering author names, addresses, and reference titles correctly. They also have an additional "ascii" attribute for the purpose of proper rendering in ascii-only media.

-

- In order to insert Unicode characters in any other context, xml2rfc vocabulary v3 requires that the Unicode string be enclosed within an <u> element. The element will be expanded inline based on the value of a "format" attribute. This provides a generalised means of generating the 6 methods of Unicode renderings listed in [RFC7997], Section 3.4, and also several others found in for instance the RFC Format Tools example rendering of RFC 7700, at https://rfc-format.github.io/draft-iab-rfc-css-bis/sample2-v2.html.

-

This element can be a child element of <annotation>, <blockquote>, <dd>, <li>, <t>, <td>, and <th>.

-
-
Content schema:
-
text -
-
-
-
-
-

-2.70.1. "anchor" Attribute -

-

Document-wide unique identifier for this <u> element.

-
-
-
-
-

-2.70.2. "ascii" Attribute -

-

- The ASCII equivalent of the content, to be used if the "ascii" keyword is used in the "format" specification.

-
-
-
-
-

-2.70.3. "format" Attribute -

-
-
Default value:
-
"lit-name-num" -
-
-
-

- The "format" attribute accepts either a simplified format specification, or a full format string with placeholders for the various possible Unicode expansions.

-

- The simplified format consists of dash-separated keywords, where each keyword represents a possible expansion of the Unicode character or string; use for example "<u "lit-num-name">foo</u>" to expand the text to its literal value, code point values, and code point names.

-

- A combination of up to 3 of the following keywords may be used, separated by dashes: "num", "lit", "name", "ascii", "char". The keywords are expanded as follows and combined, with the second and third enclosed in parentheses if present:

-
-
ascii
-
- The value of the 'ascii' attribute on the <u> element -
-
-
char
-
- The literal element text, without quotes -
-
-
lit
-
- The literal element text, enclosed in quotes -
-
-
name
-
- The Unicode name(s) of the element text -
-
-
num
-
- The numeric value(s) of the element text, in U+1234 notation -
-
-
-

- In order to ensure that no specification mistakes can result for rendering methods that cannot render all Unicode code points, "num" MUST always be part of the specified format.

-
-
-
-2.70.3.1. Examples -
-

- Examples:

-
-
-
-
-
format="num-lit":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 ("Δ"). -
-
-
format="num-name":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 (GREEK CAPITAL LETTER DELTA). -
-
-
format="num-lit-name":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 ("Δ", GREEK CAPITAL LETTER DELTA). -
-
-
format="num-name-lit":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character U+0394 (GREEK CAPITAL LETTER DELTA, "Δ"). -
-
-
format="name-lit-num":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character GREEK CAPITAL LETTER DELTA ("Δ", U+0394). -
-
-
format="lit-name-num":
-
- Temperature changes in the Temperature Control Protocol are - indicated by the character "Δ" (GREEK CAPITAL LETTER DELTA, U+0394). -
-
-
-
-
-
-
-
-
-
-
-2.70.3.2. Expansion of <u> multi-codepoint strings -
-

- If the <u> element encloses a sequence of Unicode codepoints, rather than - a single one, the rendering - reflects this. The element

-
-
   <u format="num-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
-
-

- will be expanded to "U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ")".

-

- Unicode characters in document text which are not enclosed in <u> - will be replaced with a question mark (?) and a warning will be issued.

-
-
-
-
-
-2.70.3.3. Non-simplified <u> format specifications -
-

- In order to provide for cases where the simplified format above is insufficient, - without relinquishing the requirement that the number of a code point always must - be rendered, the "format" attribute can also accept a full format string. This - format uses placeholders which consist of any of the key words above enclosed in - curly braces; outside of this, any ascii text is permissible. For example,

-
-
   The <u format="{lit} character ({num})">Δ</u>.
-
-

- will be rendered as

-
-
   The "Δ" character (U+0394).
-
-

- As for the simplified format, "num" MUST always be part of the - specified format in order to ensure that no specification - mistakes can result for rendering methods that cannot render all - Unicode code points,

-
-
-
-
-
-2.70.3.4. Split expansion of <u> elements -
-

- There are cases which cannot be handled with either the simplified or full <u> - format specifications. One is exemplified in Table 1 of the CSS sample document - at https://rfc-format.github.io/draft-iab-rfc-css-bis/sample2-v2.html#s-3. - Rendering this with <u> elements requires that the non-ascii content be rendered - in one place (a table cell in one column) while the expansion is rendered in another - cell in a different column. Provision for this has been made by modifying the expansion - of <u> when it is referenced by an <xref>. This table, with <u> elements - referenced by <xref> instances:

-
-
-   <table>
-     <name>A Sample of Legal Nicknames</name>
-     <thead>
-       <tr>
-          <th>#</th>
-          <th>Nickname</th>
-          <th>Output for comparison</th>
-       </tr>
-     </thead>
-     <tbody>
-       <tr>
-          <td>1</td>
-          <td>&lt;Foo&gt;</td>
-          <td>&lt;foo&gt;</td>
-       </tr>
-       <tr>
-          <td>2</td>
-          <td>&lt;foo&gt;</td>
-          <td>&lt;foo&gt;</td> </tr>
-       <tr>
-          <td>3</td>
-          <td>&lt;Foo Bar&gt;</td>
-          <td>&lt;foo bar&gt;</td>
-       </tr>
-       <tr>
-          <td>4</td>
-          <td>&lt;foo bar&gt;</td>
-          <td>&lt;foo bar&gt;</td>
-       </tr>
-       <tr>
-         <td>5</td>
-         <td>
-            &lt;
-            <u format="name-num" anchor="greek-upper-sigma">Σ</u>
-            &gt;
-         </td>
-         <td> <xref target="greek-upper-sigma" /> </td>
-       </tr>
-       <tr>
-          <td>6</td>
-          <td>
-             &lt;
-             <u format="name-num" anchor="greek-lower-sigma">σ</u>
-             &gt;
-          </td>
-          <td> <xref target="greek-lower-sigma" /> </td>
-       </tr>
-       <tr>
-          <td>7</td>
-          <td>
-             &lt;
-             <u format="name-num" anchor="greek-final-sigma">ς</u>
-             &gt;
-          </td>
-          <td> <xref target="greek-final-sigma" /> </td>
-       </tr>
-       <tr>
-          <td>8</td>
-          <td>
-             &lt;
-             <u format="name-num" anchor="black-chess-king">♚</u>
-             &gt;
-          </td>
-          <td>
-             <xref target="black-chess-king" format="default"/>
-          </td>
-       </tr>
-       <tr>
-          <td>9</td>
-          <td>
-             &lt;Richard
-             <u format="{char}> ({num})" anchor="richard-iv">Ⅳ</u>
-             &gt;
-          </td>
-          <td>&lt;richard iv&gt;</td>
-       </tr>
-     </tbody>
-   </table>
-
-
-
-

- comes out as shown below:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -A Sample of Legal Nicknames -
#NicknameOutput for comparison
1<Foo><foo>
2<foo><foo>
3<Foo Bar><foo bar>
4<foo bar><foo bar>
5<Σ> - GREEK CAPITAL LETTER SIGMA (U+03A3)
6<σ> - GREEK SMALL LETTER SIGMA (U+03C3)
7<ς> - GREEK SMALL LETTER FINAL SIGMA (U+03C2)
8<♚> - BLACK CHESS KING (U+265A) -
9<Richard Ⅳ> (U+2163) -<richard iv>
-
-
-
-
-
-
-
-
-

-2.71. <ul> -

-

- An unordered list. The labels on the items will be symbols picked by the formatter.

-

This element can be a child element of <abstract>, <aside>, <blockquote>, <dd>, <li>, <note>, <section>, <td>, and <th>.

-
-
Content schema:
-
- li+ -
-
-
-
-
-

-2.71.1. "anchor" Attribute -

-

Document-wide unique identifier for this <ul> element.

-
-
-
-
-

-2.71.2. "bare" Attribute (New) -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Can only be used with empty="true" (see below). Determines if the blank bullet has an horizontal extension or not. With bare="false", the empty list bullet will still occupy the same space as for empty="false". With empty="true", there will be no bullet at all, i.e., the list items will have no indentation.

-

- Example: an unordered list with bare="true" and empty="true":

-
    -
  • One -
    • -
  • Two -
    • -
-
-
-
-
-

-2.71.3. "empty" Attribute -

-
-
Possible values:
-
( "true" | "false" ) -
-
-
Default value:
-
"false" -
-
-
-

- Defines whether or not the list item bullets are empty. empty="true" indicates that a blank (empty) bullet will be shown.

-

- Example: an unordered list with bare="false" and empty="false":

-
    -
  • One -
    • -
  • Two -
    • -
-

- Example: an unordered list with bare="false" and empty="true":

-
    -
  • One -
    • -
  • Two -
    • -
-
-
-
-
-

-2.71.4. "indent" Attribute (New) -

-
-
Default value:
-
"3" -
-
-
-

- The indentation of the list elements relative to the start of the bullet or bullet text.

-
-
-
-
-

-2.71.5. "spacing" Attribute -

-
-
Possible values:
-
( "normal" | "compact" ) -
-
-
Default value:
-
"normal" -
-
-
-

- Defines whether or not there is a blank line between entries. spacing="normal" indicates a single blank line, while spacing="compact" indicates no blank line between entries.

-
-
-
-
-
-
-

-2.72. <uri> -

-

- Contains a web address associated with the author.

-

- The contents should be a valid URI; this most likely will be an "http:" or "https:" URI.

-

This element can be a child element of <address>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.73. <workgroup> -

-

- This element is used to specify the Working Group (IETF) or Research Group (IRTF) from which the document originates, if any. The recommended format is the official name of the Working Group (with some capitalization).

-

- In Internet-Drafts, this is used in the upper left corner of the boilerplate, replacing the "Network Working Group" string. Formatting software can append the words "Working Group" or "Research Group", depending on the "submissionType" property of the <rfc> element (Section 2.48.12).

-

This element can be a child element of <front>.

-
-
Content schema:
-
text -
-
-
-
-
-
-
-

-2.74. <xref> -

-

- A reference to an anchor in this document. Formatters that have links (such as HTML and PDF) are likely to render <xref> elements as internal hyperlinks. This element is useful for referring to references in the "References" section, to specific sections of the document, to specific figures, and so on.

-

- If the "section" attribute is present, this represents a link to a specific part of a document that appears in a <reference> element. Formatters that have links (such as HTML and PDF) render <xref> elements with "section" attributes as external hyperlinks to the specified part of the reference, creating the link target by combining the base URI from the <reference> element with the "relative" attribute from this element. The "target" attribute is required, and it must be the anchor of a <reference> element.

-

- If the reference is not an RFC or Internet-Draft that is in the v3 format, the element needs to have a "relative" attribute; in this case, the value of the "section" attribute is used to render the text of the external link.

-

- If the "sectino" attribute is present, the rendering will for most cominations of the "format" and "sectionFormat" have two links; one external link to the specific part of the referenced document, and one internal link to the <reference> entry.

-

- The attribute "format" affect the internal link rendering only, and the "sectionFormat" affects the rendering of the external link and its textual relationship to the internal link only.

-

This element can be a child element of <annotation>, <blockquote>, <cref>, <dd>, <dt>, <em>, <li>, <name>, <strong>, <sub>, <sup>, <t>, <td>, <th>, <tt>, .

-
-
Content schema:
-
( text | em | strong | sub | sup | tt )* -
-
-
-
-
-

-2.74.1. "format" Attribute -

-
-
Possible values:
-
( "default" | "title" | "counter" | "none" ) -
-
-
Default value:
-
"default" -
-
-
-

- This attribute signals to formatters what the desired format of the internal link to the relevant <reference> should be.

-
-
"default"
-
-

If the element has no content, the "derivedContent" attribute will contain a text fragment that describes the referenced part completely, such as "XML" for a target that is a <reference>, or "Section 2" or "Table 4" for a target to a non-reference.

-
-
-
"title"
-
-

If the target is a <reference> element, the "derivedContent" attribute will contain the name of the reference, extracted from the <title> child of the <front> child of the reference. Or, if the target element has a <name> child element, the "derivedContent" attribute will contain the text content of that <name> element concatenated with the text content of each descendant node of <name> (that is, stripping out all of the XML markup, leaving only the text). Or, if the target element does not contain a <name> child element, the "derivedContent" attribute will contain the name of the "anchor" attribute of that element with no other adornment.

-
-
-
"counter"
-
-

The "derivedContent" attribute will contain just a counter. This is used for targets that are <section>, <figure>, <table>, or items in an ordered list. Using "format='counter'" where the target is any other type of element is an error.

-
-
-
"none"
-
-

There will be no autogenerated text for the xref. When this value is used, it expected that the <xref> element will have explicit text content.

-
-
-
-
-
-
-
-

-2.74.2. "relative" Attribute (New) -

-

- Specifies a relative reference from the URI in the target reference. This value must include whatever leading character is needed to create the relative reference; typically, this is "#" for HTML documents.

-
-
-
-
-

-2.74.3. "section" Attribute (New) -

-

- Specifies a section of the target reference. If the reference is not an RFC or Internet-Draft in the v3 format, and no "relative" attribute has been provided, it is an error.

-
-
-
-
-

-2.74.4. "sectionFormat" Attribute (New) -

-
-
Possible values:
-
( "of" | "comma" | "parens" | "bare" ) -
-
-
Default value:
-
"of" -
-
-
-

- This attribute is used to signal formatters what the desired format of the external reference should be. Formatters for document types that have linking capability should wrap each part of the displayed text in hyperlinks. If there is content in the <xref> element, that content will be used when rendering the internal link part of the <xref> rendering, but will not affect the external link.

-
-
"of"
-
-

The <xref> element will be displayed as an external link followed by an internal link, separated by the work 'of'. The external link will have as its display text the word "Section" followed by a space and the contents of the "section" attribute. This will be followed by a space, the word "of", another space, and an internal link to the relevant <reference> entry, formatted based on the "format" attribute.

-
-
-
"comma"
-
-

The <xref> element will be displayed as an internal link followed by an external link, separated by a comma. The external link will have as its display text the word "Section" followed by a space and the contents of the "section" attribute. The internal link will point to the relevant <reference> entry, and will be rendered according to the "format" attribute.

-
-
-
"parens"
-
-

The <xref> element will be displayed as an internal link followed by an external link within parentheses. The external link will have as its display text the word "Section" followed by a space and the contents of the "section" attribute. The internal link will point to the relevant <reference> entry, and will be rendered according to the "format" attribute.

-
-
-
"bare"
-
-

The <xref> element will be displayed as an external link, possibly followed by the same link within parentheses. The first external link will have as its display text only contents of the "section" attribute; the second link will be present within parentheses only if the <xref> element has any text content, and will then have the text content as its display text.

-

This value for the "sectionFormat" attribute is useful when it is desired to express for instance "Sections 3.2 and 3.3 of [RFC7997]".

-
-
-
-
-
-
-
-

-2.74.5. "target" Attribute (Required) -

-

- Identifies the document component being referenced. The value needs to match the value of the "anchor" attribute of an element in the document; otherwise, it is an error.

-
-
-
-
-
-
-

-3. Deprecated Elements and Attributes -

-
-

-3.1. Elements from v2 that have been Deprecated -

-

- - The following elements from v2 have been deprecated:

-
    -
  • <c> -
    • -
  • <facsimile> -
    • -
  • <format> -
    • -
  • <list> -
    • -
  • <postamble> -
    • -
  • <preamble> -
    • -
  • <relref> -
    • -
  • <spanx> -
    • -
  • <texttable> -
    • -
  • <ttcol> -
    • -
  • <vspace> -
    • -
-
-
-

-3.2. Attributes from v2 that have been Deprecated -

-

- - The following attributes from v2 have been deprecated. Only - attributes of elements that have not themselves been deprecated - are listed:

-
-
<artwork>:
-
-
    -
  • "height" -
    • -
  • "width" -
    • -
-
-
-
<figure>:
-
-
    -
  • "align" -
    • -
  • "alt" -
    • -
  • "height" -
    • -
  • "src" -
    • -
  • "suppress-title" -
    • -
  • "title" -
    • -
  • "width" -
    • -
-
-
-
<note>:
-
-
    -
  • "title" -
    • -
-
-
-
<references>:
-
-
    -
  • "title" -
    • -
-
-
-
<section>:
-
-
    -
  • "title" -
    • -
-
-
-
<seriesInfo>:
-
-
    -
  • "status" -
    • -
  • "stream" -
    • -
-
-
-
<t>:
-
-
    -
  • "hangText" -
    • -
-
-
-
-
-
-
-

-4. References -

-
-
[BCP14]
-
-
- Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, .
-
- Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, .
-<https://www.rfc-editor.org/bcp/bcp14.txt> -
-
-
[IDGUIDE]
-
-Housley, R., "Guidelines to Authors of Internet-Drafts", , <https://www.ietf.org/id-info/guidelines.html>.
-
-
[INTRO-TO-V3]
-
-Levkowetz, H., "Introduction to xml2rfc Version 3", , <https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html>.
-
-
[LINKRELATIONS]
-
-IANA, "Link Relations", <https://www.iana.org/assignments/link-relations/link-relations.xhtml>.
-
-
[RFC2026]
-
-Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, , <https://www.rfc-editor.org/info/rfc2026>.
-
-
[RFC2397]
-
-Masinter, L., "The "data" URL scheme", RFC 2397, DOI 10.17487/RFC2397, , <https://www.rfc-editor.org/info/rfc2397>.
-
-
[RFC3339]
-
-Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, , <https://www.rfc-editor.org/info/rfc3339>.
-
-
[RFC3966]
-
-Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, DOI 10.17487/RFC3966, , <https://www.rfc-editor.org/info/rfc3966>.
-
-
[RFC3986]
-
-Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, , <https://www.rfc-editor.org/info/rfc3986>.
-
-
[RFC5234]
-
-Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, , <https://www.rfc-editor.org/info/rfc5234>.
-
-
[RFC6068]
-
-Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, DOI 10.17487/RFC6068, , <https://www.rfc-editor.org/info/rfc6068>.
-
-
[RFC6087]
-
-Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, , <https://www.rfc-editor.org/info/rfc6087>.
-
-
[RFC7322]
-
-Flanagan, H. and S. Ginoza, "RFC Style Guide", RFC 7322, DOI 10.17487/RFC7322, , <https://www.rfc-editor.org/info/rfc7322>.
-
-
[RFC7669]
-
-Levine, J., "Assigning Digital Object Identifiers to RFCs", RFC 7669, DOI 10.17487/RFC7669, , <https://www.rfc-editor.org/info/rfc7669>.
-
-
[RFC7841]
-
-Halpern, J., Ed., Daigle, L., Ed., and O. Kolkman, Ed., "RFC Streams, Headers, and Boilerplates", RFC 7841, DOI 10.17487/RFC7841, , <https://www.rfc-editor.org/info/rfc7841>.
-
-
[RFC7991]
-
-Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, DOI 10.17487/RFC7991, , <https://www.rfc-editor.org/info/rfc7991>.
-
-
[RFC7996]
-
-Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
-
-
[RFC7997]
-
-Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
-
-
[RFC7998]
-
-Hoffman, P. and J. Hildebrand, ""xml2rfc" Version 3 Preparation Tool Description", RFC 7998, DOI 10.17487/RFC7998, , <https://www.rfc-editor.org/info/rfc7998>.
-
-
[RNC]
-
-Clark, J., "RELAX NG Compact Syntax", <https://www.oasis-open.org/committees/relax-ng/compact-20021121.html>.
-
-
-
-
-

-Appendix A. RELAX NG Schema -

-
-
<CODE BEGINS> file "v3.rnc"
-
-
-namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
-
-# xml2rfc Version 3 grammar
-
-rfc =
-  element rfc {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute number { text }?,
-    [ a:defaultValue = "" ] attribute obsoletes { text }?,
-    [ a:defaultValue = "" ] attribute updates { text }?,
-    attribute category {
-      "std" | "bcp" | "exp" | "info" | "historic"
-    }?,
-    attribute mode { text }?,
-    [ a:defaultValue = "false" ]
-    attribute consensus { "no" | "yes" | "false" | "true" }?,
-    attribute seriesNo { text }?,
-    attribute ipr { text }?,
-    attribute iprExtract { xsd:IDREF }?,
-    [ a:defaultValue = "IETF" ]
-    attribute submissionType {
-      "IETF" | "IAB" | "IRTF" | "independent"
-    }?,
-    attribute docName { text }?,
-    [ a:defaultValue = "false" ]
-    attribute sortRefs { "true" | "false" }?,
-    [ a:defaultValue = "true" ]
-    attribute symRefs { "true" | "false" }?,
-    [ a:defaultValue = "true" ]
-    attribute tocInclude { "true" | "false" }?,
-    [ a:defaultValue = "3" ] attribute tocDepth { text }?,
-    attribute prepTime { text }?,
-    [ a:defaultValue = "true" ]
-    attribute indexInclude { "true" | "false" }?,
-    attribute version { text }?,
-    [ a:defaultValue = "Common,Latin" ] attribute scripts { text }?,
-    attribute expiresDate { text }?,
-    link*,
-    front,
-    middle,
-    back?
-  }
-
-link =
-  element link {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute href { text },
-    attribute rel { text }?
-  }
-
-front =
-  element front {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    title,
-    seriesInfo*,
-    author+,
-    date?,
-    area*,
-    workgroup*,
-    keyword*,
-    abstract?,
-    note*,
-    boilerplate?,
-    toc?
-  }
-
-title =
-  element title {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute abbrev { text }?,
-    attribute ascii { text }?,
-    (text | br)*
-  }
-
-author =
-  element author {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute initials { text }?,
-    attribute asciiInitials { text }?,
-    attribute surname { text }?,
-    attribute asciiSurname { text }?,
-    attribute fullname { text }?,
-    attribute role { "editor" }?,
-    attribute asciiFullname { text }?,
-    organization?,
-    address?
-  }
-
-contact =
-  element contact {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute initials { text }?,
-    attribute asciiInitials { text }?,
-    attribute surname { text }?,
-    attribute asciiSurname { text }?,
-    attribute fullname { text }?,
-    attribute asciiFullname { text }?,
-    organization?,
-    address?
-  }
-
-organization =
-  element organization {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute abbrev { text }?,
-    attribute ascii { text }?,
-    attribute asciiAbbrev { text }?,
-    [ a:defaultValue = "true" ]
-    attribute showOnFrontPage { "true" | "false" }?,
-    text
-  }
-
-address =
-  element address {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    postal?,
-    phone?,
-    facsimile?,
-    email*,
-    uri?
-  }
-
-postal =
-  element postal {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (( city | cityarea | code | country | extaddr | pobox | region
-       | sortingcode | street)*
-     | postalLine+)
-  }
-
-extaddr =
-  element extaddr {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-pobox =
-  element pobox {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-street =
-  element street {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-cityarea =
-  element cityarea {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-city =
-  element city {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-region =
-  element region {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-code =
-  element code {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-sortingcode =
-  element sortingcode {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-country =
-  element country {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-postalLine =
-  element postalLine {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-phone =
-  element phone {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-facsimile =
-  element facsimile {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-email =
-  element email {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute ascii { text }?,
-    text
-  }
-
-uri =
-  element uri {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-date =
-  element date {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute day { text }?,
-    attribute month { text }?,
-    attribute year { text }?,
-    text
-  }
-
-area =
-  element area {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-workgroup =
-  element workgroup {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-keyword =
-  element keyword {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-abstract =
-  element abstract {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (dl | ol | t | ul)+
-  }
-
-note =
-  element note {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute title { text }?,
-    attribute pn { xsd:ID }?,
-    [ a:defaultValue = "false" ]
-    attribute removeInRFC { "true" | "false" }?,
-    name?,
-    (dl | ol | t | ul)+
-  }
-
-boilerplate =
-  element boilerplate {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    section+
-  }
-
-toc =
-  element toc {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    section*
-  }
-
-middle =
-  element middle {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    section+
-  }
-
-section =
-  element section {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute title { text }?,
-    [ a:defaultValue = "true" ]
-    attribute numbered { "true" | "false" }?,
-    [ a:defaultValue = "default" ]
-    attribute toc { "include" | "exclude" | "default" }?,
-    [ a:defaultValue = "false" ]
-    attribute removeInRFC { "true" | "false" }?,
-    name?,
-    (artset
-     | artwork
-     | aside
-     | author
-     | blockquote
-     | contact
-     | dl
-     | figure
-     | iref
-     | ol
-     | sourcecode
-     | t
-     | table
-     | texttable
-     | ul)*,
-    section*
-  }
-
-name =
-  element name {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute slugifiedName { xsd:ID }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-br =
-  element br {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    empty
-  }
-
-t =
-  element t {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute hangText { text }?,
-    [ a:defaultValue = "0" ]
-    attribute indent { text }?,
-    [ a:defaultValue = "false" ]
-    attribute keepWithNext { "true" | "false" }?,
-    [ a:defaultValue = "false" ]
-    attribute keepWithPrevious { "true" | "false" }?,
-    (text
-     | bcp14
-     | br
-     | contact
-     | cref
-     | em
-     | eref
-     | iref
-     | \list
-     | relref
-     | spanx
-     | strong
-     | sub
-     | sup
-     | tt
-     | u
-     | vspace
-     | xref)*
-  }
-
-aside =
-  element aside {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (artset
-     | artwork
-     | blockquote
-     | dl
-     | figure
-     | iref
-     | ol
-     | t
-     | table
-     | ul)*
-
-  }
-
-blockquote =
-  element blockquote {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute cite { text }?,
-    attribute quotedFrom { text }?,
-    ((artset | artwork | dl | figure | ol | sourcecode | t | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)+)
-  }
-
-\list =
-  element list {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "empty" ] attribute style { text }?,
-    attribute hangIndent { text }?,
-    attribute counter { text }?,
-    attribute pn { xsd:ID }?,
-    t+
-  }
-
-ol =
-  element ol {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "1" ] attribute type { text }?,
-    [ a:defaultValue = "1" ] attribute start { text }?,
-    attribute group { text }?,
-    [ a:defaultValue = "normal" ]
-    attribute spacing { "normal" | "compact" }?,
-    [ a:defaultValue = "adaptive" ]
-    attribute indent { text | "adaptive" }?,
-    attribute pn { xsd:ID }?,
-    li+
-  }
-
-ul =
-  element ul {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "normal" ]
-    attribute spacing { "normal" | "compact" }?,
-    ([ a:defaultValue = "false" ]
-     attribute empty { "true" | "false" },
-     [ a:defaultValue = "false" ]
-     attribute bare { "true" | "false" }?)?,
-    [ a:defaultValue = "3" ]
-     attribute indent { text }?,
-     attribute pn { xsd:ID }?,
-    li+
-  }
-
-li =
-  element li {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute derivedCounter { text }?,
-    attribute pn { xsd:ID }?,
-    (( artset
-       | artwork
-       | blockquote
-       | dl
-       | figure
-       | ol
-       | sourcecode
-       | t
-       | table
-       | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)+)
-  }
-
-dl =
-  element dl {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "normal" ]
-    attribute spacing { "normal" | "compact" }?,
-    [ a:defaultValue = "false" ]
-    attribute newline { "true" | "false" }?,
-    [ a:defaultValue = "3" ]
-    attribute indent { text }?,
-    attribute pn { xsd:ID }?,
-    (dt, dd)+
-  }
-
-dt =
-  element dt {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-dd =
-  element dd {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    (( artset
-       | artwork
-       | aside
-       | dl
-       | figure
-       | ol
-       | sourcecode
-       | t
-       | table
-       | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)+)
-  }
-
-xref =
-  element xref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { xsd:IDREF },
-    [ a:defaultValue = "false" ]
-    attribute pageno { "true" | "false" }?,
-    [ a:defaultValue = "default" ]
-    attribute format { "default" | "title" | "counter" | "none" }?,
-    attribute derivedContent { text }?,
-    [ a:defaultValue = "of" ]
-    attribute sectionFormat { "of" | "comma" | "parens" | "bare" }?,
-    attribute section { text }?,
-    attribute relative { text }?,
-    attribute derivedLink { text }?,
-    (text | em | strong | sub | sup | tt)*
-  }
-
-relref =
-  element relref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { xsd:IDREF },
-    [ a:defaultValue = "of" ]
-    attribute displayFormat { "of" | "comma" | "parens" | "bare" }?,
-    attribute derivedContent { text }?,
-    attribute section { text },
-    attribute relative { text }?,
-    attribute derivedLink { text }?,
-    text
-  }
-
-eref =
-  element eref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "none" ]
-    attribute brackets { "none" | "angle" }?,
-    attribute target { text },
-    text
-  }
-
-iref =
-  element iref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute item { text },
-    [ a:defaultValue = "" ] attribute subitem { text }?,
-    [ a:defaultValue = "false" ]
-    attribute primary { "true" | "false" }?,
-    attribute pn { xsd:ID }?,
-    empty
-  }
-
-cref =
-  element cref {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute source { text }?,
-    [ a:defaultValue = "true" ]
-    attribute display { "true" | "false" }?,
-    (text
-     | br
-     | em
-     | eref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-tt =
-  element tt {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | xref)*
-  }
-
-strong =
-  element strong {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-em =
-  element em {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | br
-     | cref
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-sub =
-  element sub {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-sup =
-  element sup {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | strong
-     | sub
-     | sup
-     | tt
-     | xref)*
-  }
-
-spanx =
-  element spanx {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "preserve" ]
-    attribute xml:space { "default" | "preserve" }?,
-    [ a:defaultValue = "emph" ] attribute style { text }?,
-    text
-  }
-
-vspace =
-  element vspace {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "0" ] attribute blankLines { text }?,
-    empty
-  }
-
-figure =
-  element figure {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    [ a:defaultValue = "" ] attribute title { text }?,
-    [ a:defaultValue = "false" ]
-    attribute suppress-title { "true" | "false" }?,
-    attribute src { text }?,
-    attribute originalSrc { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    [ a:defaultValue = "" ] attribute alt { text }?,
-    [ a:defaultValue = "" ] attribute width { text }?,
-    [ a:defaultValue = "" ] attribute height { text }?,
-    name?,
-    iref*,
-    preamble?,
-    (artset | artwork | sourcecode)+,
-    postamble?
-  }
-
-table =
-  element table {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    [ a:defaultValue = "center" ]
-    attribute align { "left" | "center" | "right" }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    name?,
-    iref*,
-    thead?,
-    tbody+,
-    tfoot?
-  }
-
-preamble =
-  element preamble {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | spanx
-     | strong
-     | sub
-     | sup
-     | tt
-     | u
-     | xref)*
-  }
-
-artset =
-  element artset {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    artwork+
-  }
-
-
-artwork =
-  element artwork {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    attribute xml:space { text }?,
-    [ a:defaultValue = "" ] attribute name { text }?,
-    [ a:defaultValue = "" ] attribute type { text }?,
-    attribute src { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    [ a:defaultValue = "" ] attribute alt { text }?,
-    [ a:defaultValue = "" ] attribute width { text }?,
-    [ a:defaultValue = "" ] attribute height { text }?,
-    attribute originalSrc { text }?,
-    (text* | svg)
-  }
-include "SVG-1.2-RFC.rnc"
-
-sourcecode =
-  element sourcecode {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    attribute pn { xsd:ID }?,
-    [ a:defaultValue = "" ] attribute name { text }?,
-    [ a:defaultValue = "" ] attribute type { text }?,
-    [ a:defaultValue = "false" ]
-    attribute markers { "true" | "false" }?,
-    attribute src { text }?,
-    attribute originalSrc { text }?,
-    text
-  }
-
-thead =
-  element thead {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    tr+
-  }
-
-tbody =
-  element tbody {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    tr+
-  }
-
-tfoot =
-  element tfoot {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    tr+
-  }
-
-tr =
-  element tr {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    (td | th)+
-  }
-
-td =
-  element td {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "1" ] attribute colspan { text }?,
-    [ a:defaultValue = "1" ] attribute rowspan { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    ((artset | artwork | dl | figure | ol | sourcecode | t | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)*)
-  }
-
-th =
-  element th {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "1" ] attribute colspan { text }?,
-    [ a:defaultValue = "1" ] attribute rowspan { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    ((artset | artwork | dl | figure | ol | sourcecode | t | ul)+
-     | (text
-        | bcp14
-        | br
-        | cref
-        | em
-        | eref
-        | iref
-        | relref
-        | strong
-        | sub
-        | sup
-        | tt
-        | u
-        | xref)*)
-  }
-
-postamble =
-  element postamble {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text | cref | eref | iref | spanx | xref)*
-  }
-
-texttable =
-  element texttable {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID }?,
-    [ a:defaultValue = "" ] attribute title { text }?,
-    [ a:defaultValue = "false" ]
-    attribute suppress-title { "true" | "false" }?,
-    [ a:defaultValue = "center" ]
-    attribute align { "left" | "center" | "right" }?,
-    [ a:defaultValue = "full" ]
-    attribute style { "all" | "none" | "headers" | "full" }?,
-    name?,
-    preamble?,
-    ttcol+,
-    c*,
-    postamble?
-  }
-
-ttcol =
-  element ttcol {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute width { text }?,
-    [ a:defaultValue = "left" ]
-    attribute align { "left" | "center" | "right" }?,
-    (cref | eref | iref | xref | text)*
-  }
-
-c =
-  element c {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text | cref | eref | iref | spanx | xref)*
-  }
-
-bcp14 =
-  element bcp14 {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    text
-  }
-
-back =
-  element back {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    displayreference*,
-    references*,
-    section*
-  }
-
-displayreference =
-  element displayreference {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { xsd:IDREF },
-    attribute to { text }
-  }
-
-references =
-  element references {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute pn { xsd:ID }?,
-    attribute anchor { xsd:ID }?,
-    attribute title { text }?,
-    name?,
-    (references+ | (reference | referencegroup)*)
-  }
-
-reference =
-  element reference {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID },
-    attribute derivedAnchor { text }?,
-    attribute target { text }?,
-    [ a:defaultValue = "true" ]
-    attribute quoteTitle { "true" | "false" }?,
-    attribute quote-title { "true" | "false" }?,
-    stream?,
-    front,
-    (annotation | format | refcontent | seriesInfo)*
-  }
-
-stream =
-  element stream {
-    ( "IETF" | "IAB" | "IRTF" | "independent" )?
-}
-
-referencegroup =
-  element referencegroup {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute anchor { xsd:ID },
-    attribute derivedAnchor { text }?,
-    attribute target { text }?,
-    reference+
-  }
-
-seriesInfo =
-  element seriesInfo {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute name { text },
-    attribute value { text },
-    attribute asciiName { text }?,
-    attribute asciiValue { text }?,
-    attribute status { text }?,
-    attribute stream { "IETF" | "IAB" | "IRTF" | "independent" }?,
-    empty
-  }
-
-format =
-  element format {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    attribute target { text }?,
-    attribute type { text },
-    attribute octets { text }?,
-    empty
-  }
-
-annotation =
-  element annotation {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text
-     | bcp14
-     | cref
-     | em
-     | eref
-     | iref
-     | relref
-     | spanx
-     | strong
-     | sub
-     | sup
-     | tt
-     | u
-     | xref)*
-  }
-
-refcontent =
-  element refcontent {
-    attribute xml:base { text }?,
-    attribute xml:lang { text }?,
-    (text | bcp14 | em | strong | sub | sup | tt)*
-  }
-
-u =
-  element u {
-    attribute anchor { xsd:ID }?,
-    attribute ascii { text }?,
-    [ a:defaultValue = "lit-name-num" ]
-    attribute format { text }?,
-    attribute pn { xsd:ID }?,
-    text
-  }
-
-start |= rfc
-
-
-<CODE ENDS>
-
-
-
-

-Appendix B. xml2rfc Command-line Options -

-

- The following command-line options are available. Long options may be shortened to the shortest substring that still makes the option string unique, when given on the command line. In config files, the full long option string must be used.

-
-

-B.1. Positional arguments -

-
-
source
-
Input XML file to render to one or more of the available formats. -
-
-
-
-
-

-B.2. Documentation options -

-

- Some options to generate built-in documentation. - The group has 8 options.

-
-
-
---help, -h
-
-
-

- Show a help message and exit.

-
-
-
-
---docfile
-
-
-

- Generate a documentation XML file ready for formatting.

-

- The --docfile and --manpage switches takes input from 5 places:

-
    -
  • The v3.rng file distributed as part of the xml2rfc package, which is also used to validate and process v3 XML input. -
    • -
  • A rfc7991.rng file distributed as part of the xml2rfc package, which holds the schema defined in [RFC7991]. This is used in determining elements and attributes that are new in the current v3.rng schema, compared to the RFC7991 schema. -
    • -
  • Lists of deprecated elements and attributes, which are part of the xml2rfc source. -
    • -
  • A YAML file doc.yaml that contains XML snippets with descriptions of elements, attributes, attribute values, and switches, from the same directory as doc.xml. -
    • -
  • An XML template file doc.xml, by default taken from the templates directory of the xml2rfc package (but this can be changed with the --templates-dir switch). The 4 preceding sources provide content that is used to expand the template file when generating the --⁠docfile and --⁠manpage output. -
    • -
-
-
-
-
---manpage
-
-
-

- Show paged text documentation.

-

- Generates on-the-fly paged text documentation for the v3 schema elements and attributes from the v3 RelaxNG schema file which is part of the xml2rfc distribution, and YAML and XML files that provide the text content and formatting. See the --docfile switch for more details.

-
-
-
-
---country-help
-
-
-

- Show the recognized <country> strings.

-
-
-
-
---pdf-help
-
-
-

- Show pdf generation requirements.

-
-
-
-
---template-dir
-
-
-

- Directory to pull the doc.xml and doc.yaml templates from. The default is the "templates" directory of the xml2rfc package.

-

- This is used to find the templates used by the --⁠docfile and --⁠manpage commands and for legacy .html template and .dtd files.

-

- A consequence of being able to specify a different template directory than the default is that it's possible to use the --⁠docfile command to generate additional documentation XML files based on the current V3 grammar file. The default template and snippets file does not include documentation for deprecated elements and attributes, for instance; but if it is desired to generate such documentation from the distributed V3 RelaxNg schema, it should be straightforward. The templating system used is Jinja2; the snippens file is YAML with extra support for some escape sequences: '\ <' and '\ >'.

-
-
-
-
---values
-
-
-

- Show option values and from where they come.

-

- This shows (in order):

-
    -
  • Command line arguments -
    • -
  • Config file settings, per config file -
    • -
  • Default values -
    • -
  • Config file search path -
    • -
-
-
-
-
---version, -V
-
-
-

- Display the version number and exit.

-

- With the --verbose switch, the versions of the external python modules used will also be shown.

-
-
-
-
-
-

-B.3. Format selection -

-

- One or more of the following output formats may be specified. The default is --text. The destination filename will be based on the input filename, unless --out=FILE or --basename=BASE is used. - The group has 10 options.

-
-
-
---text
-
-
-

- Outputs formatted text to file, with proper page breaks.

-
-
-
-
---html
-
-
-

- Outputs formatted HTML to file.

-
-
-
-
---nroff
-
-
-

- Outputs formatted nroff to file (only v2 input).

-
-
-
-
---pdf
-
-
-

- Outputs formatted PDF to file.

-
-
-
-
---raw
-
-
-

- Outputs formatted text to file, unpaginated (only v2 input).

-
-
-
-
---expand
-
-
-

- Outputs XML to file with all references expanded.

-
-
-
-
---v2v3
-
-
-

- Convert vocabulary version 2 XML to version 3.

-
-
-
-
---preptool
-
-
-

- Run preptool on the input.

-
-
-
-
---unprep
-
-
-

- Reduce prepped xml to unprepped.

-
-
-
-
---info
-
-
-

- Generate a JSON file with anchor to section lookup information.

-
-
-
-
-
-

-B.4. Generic Switch Options -

-
-
-
---clear-cache, -C
-
-
-

- Purge the cache and exit.

-
-
-
-
---debug
-
-
-

- Show debugging output.

-
-
-
-
---no-network, -N
-
-
-

- Don't use the network to resolve references.

-
-
-
-
---no-org-info, -O
-
-
-

- Don't show author orgainzation info on page one (legacy only).

-
-
-
-
---quiet, -q
-
-
-

- Don't print anything while working.

-
-
-
-
---skip-config-files
-
-
-

- Ignore config file settings.

-

- Use this to ignore values in config files, even if there are config files in the search path. Somewhat ironically, this option can itself be set in a config file, and cause all other config file settings to be ignored.

-
-
-
-
---allow-local-file-access
-
-
-

- Allow local file system references.

-
-
-
-
---remove-pis, -r
-
-
-

- Remove XML processing instructions.

-
-
-
-
---utf8, -u
-
-
-

- Generate utf8 output.

-
-
-
-
---verbose, -v
-
-
-

- Print extra information.

-
-
-
-
-
-

-B.5. Generic Options with Values -

-
-
-
---basename, -b = NAME
-
-
-

- Specify the base name for output files.

-
-
-
-
---cache, -c = PATH
-
-
-

- Specify a primary cache directory to write to; default: try [ /var/cache/xml2rfc, ~/.cache/xml2rfc ].

-
-
-
-
---config-file = FILE
-
-
-

- Specify a configuration file.

-

- This argument can be repeated, to read multiple explicitly specified config files. They will be read after any config files found in 'standard' locations have been read. Run xml2rfc --values to see the default search path for config files.

-
-
-
-
---dtd, -d = DTDFILE
-
-
-

- Specify an alternate dtd file.

-

- This option can be negated with --no-dtd.

-
-
-
-
---date, -D = DATE
-
-
-

- Run as if the date is DATE (format: yyyy-mm-dd). Default: Today's date.

-
-
-
-
---filename, -f = FILE
-
-
-

- Deprecated. The same as -o.

-
-
-
-
---indent, -i = INDENT
-
-
-

- With some v3 formatters: Indentation to use when pretty-printing XML.

-
-
-
-
---out, -o = FILE
-
-
-

- Specify an explicit output filename.

-
-
-
-
---path, -p = PATH
-
-
-

- Specify the directory path for output files.

-
-
-
-
---silence, -s = STRING
-
-
-

- Silence any warning beginning with the given string.

-

- Specifies a string prefix or a regular expression to match against warning messages. Any warning message that matches is silenced. Example:

-
-
xml2rfc --silence='The document date' draft-foo-bar.xml
-
-

- This will not show any message about the document date being too far from the current date. The option can be repeated with different prefix strings or regular expressions in order to silence multiple warning messages.

-

- Alternatively, instead of indicating this on the command line, an xml2rfc-specific PI (processing instruction) is available for use in XML input files. This will have the same effect as the example above, except when processing prepped drafts; running the preptool on a file will strip XML PIs before writing the prepped file:

-
-
<?v3xml2rfc silence="The document date" ?>
-
-
-
-
-
-
-

-B.6. Generic Format Options -

-
-
-
---v3
-
-
-

- With --text and --html: use the v3 formatter, rather than the legacy one.

-

- This is the default. With both v2 schema and v3 schema XML input files, use the v3 output formatters. Input with deprecated v2 elements will be converted to v3 on the fly. This means some loss of functionality and exact control of the output, due to the intermediary conversion step.

-
-
-
-
---v2, --legacy
-
-
-

- With --text and --html: use the legacy output formatters, rather than the v3 ones.

-

- Invokes the legacy (schema v2) validator and output formatters, instead of the default schema v3 output formatters. This can only be used with pure v2 input files.

-
-
-
-
---id-is-work-in-progress
-
-
-

- In references, refer to Internet-Drafts as "Work in Progress".

-
-
-
-
-
-

-B.7. Text Format Options -

-
-
-
---no-headers
-
-
-

- Calculate page breaks, and emit form feeds and page top spacing, but omit headers and footers from the paginated format.

-
-
-
-
---legacy-list-symbols
-
-
-

- Use the legacy list bullet symbols, rather than the new ones.

-
-
-
-
---legacy-date-format
-
-
-

- Use the legacy date format, rather than the new one.

-

- This option can be negated with --no-legacy-date-format.

-
-
-
-
---list-symbols = 4*CHAR
-
-
-

- Use the characters given as list bullet symbols.

-
-
-
-
---BOM, --bom
-
-
-

- Add a BOM (unicode byte order mark) to the start of text files.

-
-
-
-
---pagination, --paginate
-
-
-

- Do pagination.

-

- By default, drafts are paginated, but not RFCs. Use this switch if you want to force pagination of all text output.

-

- This option can be negated with --no-pagination.

-
-
-
-
---table-hyphen-breaks
-
-
-

- More easily do line breaks after hyphens in table cells to give a more compact table.

-
-
-
-
---table-borders
-
-
-


Default value: full

-

- The style of table borders to use for text output; one of full/light/minimal.

-

- Examples (these will only have visible differences in text mode):

-
-
"full":
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 2
ABC
a b c
aa ba ca
ab bb cb
AA BB CC
aaa bba cca
aab bbb ccb
-
-
-
-
-
"light":
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 3
ABC
a b c
aa ba ca
ab bb cb
AA BB CC
aaa bba cca
aab bbb ccb
-
-
-
-
-
"minimal":
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 4
ABC
a b c
aa ba ca
ab bb cb
AA BB CC
aaa bba cca
aab bbb ccb
-
-
-
-
-
-
-
-
-

-B.8. Html Format Options -

-
-
-
---css = FILE
-
-
-

- Use the given CSS file instead of the builtin.

-
-
-
-
---external-css
-
-
-

- Place css in external files.

-

- This option can be negated with --no-external-css.

-
-
-
-
---external-js
-
-
-

- Place js in external files.

-

- This option can be negated with --no-external-js.

-
-
-
-
---rfc-base-url
-
-
-


Default value: https://www.rfc-editor.org/rfc/

-

- Base URL for RFC links.

-
-
-
-
---id-base-url
-
-
-


Default value: https://datatracker.ietf.org/doc/html/

-

- Base URL for Internet-Draft links.

-
-
-
-
---rfc-reference-base-url
-
-
-


Default value: https://rfc-editor.org/rfc/

-

- Base URL for RFC reference targets, replacing the target="..." value given in the reference entry.

-
-
-
-
---id-reference-base-url
-
-
-


Default value: https://datatracker.ietf.org/doc/html/

-

- Base URL for I-D reference targets.

-
-
-
-
---metadata-js-url
-
-
-


Default value: metadata.min.js

-

- URL for the metadata script.

-
-
-
-
-
-

-B.9. V2-V3 Converter Options -

-
-
-
---add-xinclude
-
-
-

- Replace reference elements with RFC and Internet-Draft seriesInfo with the appropriate XInclude element.

-
-
-
-
---draft-revs, --draft-revisions
-
-
-

- Reference explicit draft revisions when inserting XIncludes for draft references.

-
-
-
-
---strict
-
-
-

- Be strict about stripping some deprecated attributes.

-
-
-
-
-
-

-B.10. Preptool Options -

-
-
-
---accept-prepped
-
-
-

- Accept already prepped input.

-
-
-
-
-
-
-

-Appendix C. xml2rfc Configuration Files -

-

- Most options have built-in defaults, and the command-line switches above can be used to override those. Additionally, xml2rfc will look for config files in some standard file locations. The option --⁠values will show the places xml2rfc will look for config files on your system (among other information). Any settings in config files will override the program defaults, but will in turn be overridden by command-line options.

-

- The config files are expected to contain lines with option value assignments. Lines with '#' as the first character are considered comments. Here is an example:

-
-
-# ----
-legacy-date-format = true
-add-xinclude = true
-external-js = false
-# ----
-
-
-

- The complete long option names must be used in configuration files; abbreviations will not be recognised (in contrast with how abbreviations are handled during command-line option processing).

-
-
-

-Appendix D. xml2rfc Documentation Template Variables -

-

- - The following variables are available for use in an xml2rfc - manpage Jinja2 template, as of xml2rfc version 3.12.7:

-
-
{{ bare_latin_tags }}:
-
-
-
{{ descriptions }}:
-
The descriptions read from the doc.yaml file -
-
-
{{ element_tags }}:
-
A list of all the element tags in the XML schema -
-
-
{{ elements }}:
-
A list of dictionaries, each with information about one schema element: {"attributes": ..., "children": ..., "deprecated": ..., "deprecated_attributes": ..., "description": ..., "new": ..., "parents": ..., "rnc": ..., "tag": ..., } -
-
-
{{ options }}:
-
A list of dictionaries describing the command-line options -
-
-
{{ schema }}:
-
The full RelaxNG Compact representation of the schema in text form -
-
-
{{ toc_depth }}:
-
ToC depth setting; 1 when running --man, 2 otherwise -
-
-
{{ v3_element_tags }}:
-
A list of v3 element tags, excluding deprecated tags -
-
-
{{ version }}:
-
The xml2rfc version number -
-
-
-
-
-
-

-Author's Address -

-
-
xml2rfc(1)
-
-
-
- - - diff --git a/tests/valid/draft-miek-test.v3.py38.html b/tests/valid/draft-miek-test.v3.html similarity index 99% rename from tests/valid/draft-miek-test.v3.py38.html rename to tests/valid/draft-miek-test.v3.html index 2f6a3ddc7..504c4f439 100644 --- a/tests/valid/draft-miek-test.v3.py38.html +++ b/tests/valid/draft-miek-test.v3.html @@ -16,7 +16,7 @@ This version is adapted to work with "xml2rfc" version 2.x. ' name="description"> - + diff --git a/tests/valid/draft-miek-test.v3.py36.html b/tests/valid/draft-miek-test.v3.py36.html deleted file mode 100644 index 2f6a3ddc7..000000000 --- a/tests/valid/draft-miek-test.v3.py36.html +++ /dev/null @@ -1,1977 +0,0 @@ - - - - - - -Writing I-Ds and RFCs using Pandoc and xml2rfc 2.x - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-DraftPandoc2rfc Version 2January 2013
GiebenExpires July 5, 2013[Page]
-
-
-
-
Workgroup:
-
RFC Beautification Working Group
-
Internet-Draft:
-
draft-gieben-writing-rfcs-pandoc-02
-
Published:
-
- -
-
Intended Status:
-
Informational
-
Expires:
-
-
Author:
-
-
-
R. Gieben
-
Google
-
-
-
-
-

Writing I-Ds and RFCs using Pandoc and xml2rfc 2.x

-
-

Abstract

-

- This memo presents a technique for using Pandoc syntax as a source - format for documents in the Internet-Drafts (I-Ds) and Request for - Comments (RFC) series.

-

- This version is adapted to work with "xml2rfc" version 2.x.

-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at http://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on July 5, 2013.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-
-

-1. Introduction -

-

- This document presents a technique for using Pandoc syntax as a - source format for documents in the Internet-Drafts (I-Ds) and - Request for Comments (RFC) series.

-

- This version is adapted to work with - xml2rfc version 2.x.

-

- Pandoc is an "almost plain text" format and therefor particularly - well suited for editing RFC-like documents.

-
    -
  • - Note: this document is typeset in Pandoc and does not render - completely correct when reading it on github. -
    • -
-
-
-
-
-

-2. Pandoc to RFC -

-
    -
  • - Pandoc2rfc -- designed to do the right thing, until it doesn't. -
    • -
-

- When writing [RFC4641] - we directly wrote the XML. Needless to say it was tedious even thought - the XML of xml2rfc - is very "light". The - latest version of xml2rfc version 2 can be found here.

-

- During the last few years people have been developing markup - languages that are very easy to remember and type. These languages - have become known as - almost plain - text-markup languages. One of the first was the - Markdown - syntax. One that was developed later and incorporates Markdown and - a number of extensions is - Pandoc. The - power of Pandoc also comes from the fact that it can be translated - to numerous output formats, including, but not limited to: HTML, - (plain) Markdown and - docbook XML.

-

- So using Pandoc for writing RFCs seems like a sane choice. As - xml2rfc uses XML, - the easiest way would be to create - docbook - XML and transform that using XSLT. Pandoc2rfc does just that. The - conversions are, in some way amusing, as we start off with - (almost) plain text, use elaborate XML and end up with plain text - again.

-
-
-
-
-+-------------------+   pandoc   +---------+
-| ALMOST PLAIN TEXT |   ------>  | DOCBOOK |
-+-------------------+            +---------+
-              |                       |
-non-existent  |                       | xsltproc
-  faster way  |                       |
-              v                       v
-      +------------+    xml2rfc  +---------+
-      | PLAIN TEXT |  <--------  | XML2RFC |
-      +------------+             +---------+
-
-
-
Figure 1: -Attempt to justify Pandoc2rfc. -
-
-

- The XML generated (the output after the - xsltproc step in - Figure 1) - is suitable for inclusion in either the - middle or - back section of - an RFC. The simplest way is to create a template XML file and - include the appropriate XML:

-
-
-
-
-<?xml version='1.0' ?>
-<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' [
-<!ENTITY pandocMiddle PUBLIC '' 'middle.xml'>
-<!ENTITY pandocBack   PUBLIC '' 'back.xml'>
-]>
-
-<rfc ipr='trust200902' docName='draft-gieben-pandoc-rfcs-02'>
- <front>
-    <title>Writing I-Ds and RFCs using Pandoc v2</title>
-</front>
-
-<middle>
-    &pandocMiddle;
-</middle>
-
-<back>
-    &pandocBack;
-</back>
-
-</rfc>
-
-
-
Figure 2: -A minimal template.xml. -
-
-

- See the Makefile for an example of this. In this case you need to - edit 3 documents:

-
    -
  1. - middle.pdc - contains the main body of text; -
    2. -
  2. - back.pdc - holds appendices and references; -
    3. -
  3. - template.xml (probably a fairly static file). -
    4. -
-

- The draft - (draft.txt) you - are reading now, is automatically created when you call - make. The - homepage of Pandoc2rfc is - this github - repository.

-
-
-

-2.1. Dependencies -

-

- It needs xsltproc - and pandoc to be - installed. See the - Pandoc - user manual for the details on how to type in Pandoc style. - And of course xml2rfc - version two.

-

- When using Pandoc2rfc consider adding the following sentence to - an Acknowledgements section:

-
-
- This document was produced using the Pandoc2rfc tool.
-
-
-
-
-
-
-
-
-

-3. Starting a new project -

-

- When starting a new project with - pandoc2rfc you'll - need to copy the following files:

-
    -
  • - Makefile -
    • -
  • - transform.xslt -
    • -
  • -

    - And the above mentioned files:

    -
      -
    • - middle.pdc -
      • -
    • - back.pdc -
      • -
    • - template.xml -
      • -
    -
    • -
-

- After that you can start editing.

-
-
-
-
-

-4. Supported Features -

- -
-
-
-
-

-5. Unsupported Features -

-
    -
  • - Lists inside a table (xml2rfc doesn't handle this); -
    • -
  • - Pandoc markup in the caption for figures/artwork. Pandoc markup for table captions is supported; -
    • -
  • - crefs: for comments (no input syntax available), use HTML comments: <!-- ... -->; -
    • -
-
-
-
-
-

-6. Acknowledgements -

-

- The following people have helped to make Pandoc2rfc what it is today: Benno Overeinder, Erlend Hamnaberg, Matthijs Mekking, Trygve Laugstoel.

-

- This document was prepared using Pandoc2rfc.

-
-
-
-
-

-7. Pandoc Constructs -

-

- So, what syntax do you need to use to get the correct output? Well, it is - just Pandoc. The best introduction - to the Pandoc style is given in this - README from Pandoc itself.

-

- For convenience we list the most important ones in the following sections.

-
-
-

-7.1. Paragraph -

-

- Paragraphs are separated with an empty line.

-
-
-
-
-

-7.2. Section -

-

- Just use the normal sectioning commands available in Pandoc, for instance:

-
-
-# Section1 One
-Bla
-
-
-

- Converts to: <section title="Section1 - One" anchor="section1-one"> If you have another section that is also - named "Section1 One", that anchor will be called "section1-one-1", but - only when the sections are in - the same source file!

-

- Referencing the section is done with see - [](#section1-one), as in see Section 7.2.

-
-
-
-
-

-7.3. List Styles -

-

- A good number of styles are supported.

-
-
-

-7.3.1. Symbol -

-
-
-A symbol list.
-
-* Item one;
-* Item two.
-
-
-

- Converts to <list style="symbol">:

-
    -
  • - Item one; -
    • -
  • - Item two. -
    • -
-
-
-
-
-

-7.3.2. Number -

-
-
-A numbered list.
-
-1. Item one;
-1. Item two.
-
-
-

- Converts to <list style="numbers">:

-
    -
  1. - Item one; -
    2. -
  2. - Item two. -
    3. -
-
-
-
-
-

-7.3.3. Empty -

-

- Using the default list markers from Pandoc:

-
-
-A list using the default list markers.
-
-#. Item one;
-#. Item two.
-
-
-

- Converts to <list style="empty">:

-
    -
  • - Item one; -
    • -
  • - Item two. -
    • -
-
-
-
-
-

-7.3.4. Roman -

-

- Use the supported Pandoc syntax:

-
-
-ii. Item one;
-ii. Item two.
-
-
-

- Converts to <list style="format %i.">:

-
-
i.
-
- Item one; -
-
-
ii.
-
- Item two. -
-
-
-

- If you use uppercase Roman numerals, they convert to a different style:

-
-
-II. Item one;
-II. Item two.
-
-
-

- Yields <list style="format (%d) ">:

-
-
(1)
-
- Item one; -
-
-
(2)
-
- Item two. -
-
-
-
-
-
-
-

-7.3.5. Letter -

-

- A numbered list.

-
-
-a.  Item one;
-b.  Item two.
-
-
-

- Converts to <list style="letters">:

-
    -
  1. - Item one; -
    2. -
  2. - Item two. -
    3. -
-

- Uppercasing the letters works too (note two spaces after the letter.

-
-
-A.  Item one;
-B.  Item two.
-
-
-

- Becomes:

-
-
A.
-
- Item one; -
-
-
B.
-
- Item two. -
-
-
-
-
-
-
-

-7.3.6. Hanging -

-

- This is more like a description list, so we need to use:

-
-
-First item that needs clarification:
-
-:   Explanation one
-More stuff, because item is difficult to explain.
-* item1
-* item2
-
-Second item that needs clarification:
-
-:   Explanation two
-
-
-

- Converts to: <list style="hanging"> and <t hangText="First item that...">

-

- If you want a newline after the hangTexts, search for the string OPTION in transform.xsl and uncomment it.

-
-
-
-
-
-
-

-7.4. Figure/Artwork -

-

- Indent the paragraph with 4 spaces.

-
-
-Like this
-
-
-

- Converts to: - <figure><artwork> ... - Note that xml2rfc - supports a caption with - <artwork>. Pandoc does not - support this, but Pandoc2rfc does. If you add a - @Figure: some text as the last - line, the artwork gets a title - attribute with the text after - @Figure:. It will also be - possible to reference the artwork. If a caption is supplied the artwork will be - centered. If a caption is needed but the figure should not be centered use - @figure:\.

-
-
-

-7.4.1. References -

-

- The reference anchor attribute will be: fig: - + first 10 (normalized) characters from the caption. - Where normalized means:

-
    -
  • - Take the first 10 characters of the caption (i.e. this is the text - after the string - @Figure:); -
    • -
  • - Spaces and single quotes (') are translated to a minus - -; -
    • -
  • - Uppercase letters translated to lowercase. -
    • -
-

- So the first artwork with a caption will get - fig:a-minimal- - as a reference. See for instance - Figure 2.

-

- This anchoring is completely handled from within the - xslt. - Note that duplicate anchors are an XML validation error which will make - xml2rfc fail.

-
-
-
-
-
-
-

-7.5. Block Quote -

-

- Any paragraph like:

-
-
-> quoted text
-
-
-

- Converts to: <t><list style="empty"> ... - paragraph, making it indented.

-
-
-
-
-

-7.6. References -

-
-
-

-7.6.1. External -

-

- Any reference like:

-
-
-[Click here](URI)
-
-
-

- Converts to: <ulink target="URI">Click here ...

-
-
-
-
-

-7.6.2. Internal -

-

- Any reference like:

-
-
-[Click here](#localid)
-
-
-

- Converts to: <link target="localid">Click here ...

-

- For referring to RFCs (for which you manually need add the reference source in - the template, with an external XML entity), you can just use:

-
-
-[](#RFC2119)
-
-
-

- And it does the right thing. Referencing sections is done with:

-
-
-See [](#pandoc-constructs)
-
-
-

- The word 'Section' is inserted automatically: ... see - Section 7 - ... For referencing figures/artworks see - Section 7.4. - For referencing tables see Section 7.8.

-
-
-
-
-
-
-

-7.7. Spanx Styles -

-

- The verb style can be selected with back-tics: - `text` - Converts to: - <spanx style="verb"> ...

-

- And the emphasis style with asterisks: - *text* - or underscores: _text_ - Converts to: <spanx style="emph"> ...

-

- And the emphasis style with double asterisks: - **text** - Converts to: <spanx style="strong"> ...

-
-
-
-
-

-7.8. Tables -

-

- A table can be entered as:

-
-
-
-
-  Right     Left     Center     Default
-  -------   ------ ----------   -------
-       12     12        12        12
-      123     123       123       123
-        1     1         1         1
-
-  Table: A caption describing the table.
-
-
-
Figure 3: -A caption describing the figure describing the table. -
-
-

- Is translated to <texttable> - element in xml2rfc. - You can choose multiple styles as input, but they all are converted to the same style (plain - <texttable>) table in - xml2rfc. The column alignment - is copied over to the generated XML.

-
-
-

-7.8.1. References -

-

- The caption is always - translated to a title - attribute. If a table has a caption, it will - also get a reference. - The reference anchor attribute will be: - tab- - + first 10 (normalized) characters from the caption. - Where normalized means:

-
    -
  • - Take the first 10 characters of the caption (i.e. this is the text - after the string - Table:); -
    • -
  • - Spaces and single quotes (') are translated to a minus - -; -
    • -
  • - Uppercase letters translated to lowercase. -
    • -
-

- So the first table with a caption will get - tab-a-caption- - for reference use. See for instance

-

- This anchoring is completely handled from within the - xslt. - Note that duplicate anchors are an XML validation error which will make - xml2rfc fail.

-
-
-
-
-
-
-

-7.9. Indexes -

-

- The footnote syntax of Pandoc is slightly abused to support an index. Footnotes are entered in two steps, you have a marker in the text, and later you give actual footnote text. Like this:

-
-
-[^1]
-
-[^1]: footnote text
-
-
-

- We re-use this syntax for the <iref> tag. The above text translates to:

-
-
-<iref item="footnote text"/>
-
-
-

- Sub items are also supported. Use an exclamation mark (!) to separate them:

-
-
-[^1]: item!sub item
-
-
-
-
-
-
-
-
-

-8. Usage guidelines -

-
-
-

-8.1. Working with multiple files -

-

- As an author you will probably break up a draft in multiple files, each dealing - with a subject or section. When doing so sections with the same title will clash - with each other. Pandoc can deal with this situation, but only if the different - sections are in the same file or - processed in the same Pandoc run. Concatenating the different section files - before processing them is a solution to this problem. You can, for instance, - amend the Makefile and add - something like this:

-
-
-allsections.pdc: section.pdc.1 section.pdc.2 section.pdc.3
-        cat $@ > allsections.pdc
-
-
-

- And then process allsection.pdc in the normal way.

-
-
-
-
-

-8.2. Setting the title -

-

- If you use double quotes in the documents title in the - docName attribute, like:

-
-
-<rfc ipr="trust200902" docName="draft-gieben-writing-rfcs-pandoc-02">
-
-
-

- The Makefile will pick this up automatically and make a symbolic link:

-
-
-draft-gieben-writing-rfcs-pandoc-00.txt -> draft.txt
-
-
-

- This makes uploading the file to the i-d tracker a bit easier.

-
-
-
-
-

-8.3. Uploading the XML/txt -

-

- The draft.xml target will - generate an XML file with all XML included, so you can upload just one file to - the I-D tracker.

-
-
-
-
-

-8.4. VIM syntax highlighting -

-

- If you are a VIM user you might be interested in a syntax highlighting file (see - [VIM]) that slightly lightens up - your reading experience while viewing a draft.txt from VIM.

-
-
-
-
-
-
-

-9. Security Considerations -

-

- This document raises no security issues.

-
-
-
-
-

-10. IANA Considerations -

-

- This document has no actions for IANA.

-
-
-
-

-11. References -

-
-

-11.1. Informative References -

-
-
[VIM]
-
-Gieben, R., "VIM syntax file for RFCs and I-Ds", , <http://github.com/miekg/rfc>.
-
-
-
-
-

-11.2. Normative References -

-
-
[RFC2119]
-
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, , <ftp://ftp.isi.edu/in-notes/rfc2119.txt>.
-
-
[RFC4641]
-
-Kolkman, O. and R. Gieben, "DNSSEC Operational Practices", RFC 4641, , <http://www.rfc-editor.org/rfc/rfc4641.txt>.
-
-
-
-
-
-
-

-Appendix A. Tests -

-

- This appendix consists out of a few tests that should all render to proper - xml2rfc XML.

- -
-
-

-A.2. Markup in heading -

-

- This is discarded by xml2rfc.

-
-
-
-
-

-A.3. Blockquote -

-
    -
  • - This is a blockquote, how does it look? -
    • -
-
-
-
-
-

-A.4. Verbatim code blocks -

-
-
-A verbatim code block
-jkasjksajassjasjsajsajkas
-
-
-
-
-
-
-

-A.5. Reference Tests -

-

- Refer to RFC 2119 [RFC2119] if you will. Or maybe you want to inspect Figure 2 in Section 2 again. Or you might want to Click here.

-
-
-
-
-

-A.6. Spanx Tests -

-
    -
  • - underscores: underscores -
    • -
  • - asterisks: asterisks -
    • -
  • - double asterisks: double asterisks -
    • -
  • - backticks: backticks -
    • -
-
-
-
-
-

-A.7. List Tests -

-
    -
  1. - First we do -
    2. -
  2. -

    - And then

    -
      -
    • - item 1 -
      • -
    • - item 2 -
      • -
    -
    3. -
-

- And the other around.

-
    -
  • - First we do -
    • -
  • -

    - Then

    -
      -
    1. - Something -
      2. -
    2. - Another thing -
      3. -
    -
    • -
-

- Description lists:

-
-
Item to explain:
-
It works because of herbs. -
-
-
Another item to explain:
-
-

More explaining.

-

Multiple paragraphs in such a list.

-
-
-
-

- lists in description lists.

-
-
Item to explain:
-
-

It works because of

-
    -
  1. - One -
    2. -
  2. - Two -
    3. -
-
-
-
Another item to explain:
-
More explaining -
-
-
Item to explain:
-
-

It works because of

-
    -
  1. - One1 -
    2. -
  2. -

    - Two1

    -
      -
    • - Itemize list -
      • -
    • - Another item -
      • -
    -
    3. -
-
-
-
Another item to explain again:
-
More explaining -
-
-
-

- list with description lists.

-
    -
  1. -

    - More

    -
    -
    Item to explain:
    -
    Explanation ... -
    -
    -
    Item to explain:
    -
    Another explanation ... -
    -
    -
    -
    2. -
  2. - Go'bye -
    3. -
-

- Multiple paragraphs in a list.

-
    -
  1. -

    - This is the first bullet point and it needs multiple paragraphs...

    -

    ... to be explained properly.

    -
    2. -
  2. - This is the next bullet. New paragraphs should be indented with 4 four spaces. -
    3. -
  3. -

    - Another item with some artwork, indented by 8 spaces.

    -
    -
    -Artwork
-
    -
    -
    4. -
  4. - Final item. -
    5. -
-

- xml2rfc does not allow this, so the second paragraph is faked with a

-
-
-<vspace blankLines='1'>
-
-
-

- Ordered lists.

-
    -
  1. - First item -
    2. -
  2. - Second item -
    3. -
-

- A lowercase roman list:

-
-
i.
-
- Item 1 -
-
-
ii.
-
- Item 2 -
-
-
-

- An uppercase roman list.

-
-
(1)
-
- Item1 -
-
-
(2)
-
- Item2 -
-
-
(3)
-
- Item 3 -
-
-
-

- And default list markers.

-

- Some surrounding text, to make it look better.

-
    -
  • - First item. Use lot of text to get a real paragraphs sense. - First item. Use lot of text to get a real paragraphs sense. - First item. Use lot of text to get a real paragraphs sense. - First item. Use lot of text to get a real paragraphs sense. -
    • -
  • - Second item. So this is the second para in your list. Enjoy; -
    • -
  • - Another item. -
    • -
-

- Text at the end.

-

- Lowercase letters list.

-
    -
  1. - First item -
    2. -
  2. - Second item -
    3. -
-

- Uppercase letters list.

-
-
A.
-
- First item -
-
-
B.
-
- Second item -
-
-
-

-

-

- And artwork in a description list.

-
-
Item1:
-
-

- Tell something about it. Tell something about it. Tell something about - it. Tell something about it. Tell something about it. Tell something about it.

-
-
-miek.nl.    IN  NS  a.miek.nl.
-a.miek.nl.  IN  A   192.0.2.1    ; <- this is glue
-
-
-

- Tell some more about it. Tell some more about it. Tell some more about it.

-
-
-
Item2:
-
Another description -
-
-
-

- List with a sublist with a paragraph above the sublist

-
    -
  1. - First Item -
    2. -
  2. - Second item -
    3. -
  3. -

    - Third item

    -

    A paragraph that comes first

    -
      -
    1. - But what do you know -
      2. -
    2. - This is another list -
      3. -
    -
    4. -
-
-
-
-
-

-A.8. Table Tests -

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -Demonstration of simple table - syntax. -
Right Left Center Default
12 12 12 12
123 123 123 123
1 1 1 1
-
-
- - - - - - - - - - - - - - - - - - - - - - - - -
-Table 2: -Here's the caption. It, too, may span multiple lines. This is a - multiline table. This is verbatim text. -
Centered Header Default Aligned Right Aligned Left Aligned
First row 12.0 Example of a row that spans multiple lines.
Second row 5.0 Here's another one. Note the blank line between rows.
-
-

-

-
- - - - - - - - - - - - - - - - - - - - - -
-Table 3: -Sample grid table. -
Fruit Price Advantages
Bananas $1.34 built-in wrapper
Oranges $2.10 cures scurvy
-
-

- Grid tables without a caption

- - - - - - - - - - - - - - - - - - - - - -
Table 4
Fruit Price Advantages
Bananas $1.34 built-in wrapper
Oranges $2.10 cures scurvy
-

- This table has no caption, and therefor no reference. But you can refer to some of the other tables, with for instance:

-
-
-See [](#tab-here-s-the)
-
-
-

- Which will become "See Table 2".

-

-

-

- We should also be able to refer to the table numbers directly, to say things like - 'Look at Tables - 1, - 2 - and 3.'

-
-
-
-
-

-A.9. Numbered examples -

-

- This is another example:

-
    -
  1. - Another bla bla.. -
    2. -
-

- as (1) shows...

-
-
-
-
-

-A.10. Figure tests -

-
-
-
-
-This is a figure
-This is a figure
-This is a figure
-This is a figure
-
-
-
Figure 4: -This is the caption, with text in `typewriter`. Which isnt converted to a <spanx> style, because this is copied as-is. -
-
-

- And how a figure that is not centered, do to using figure and not Figure.

-
-
-
-
-This is a figure
-This is a figure
-
-
-
Figure 5: -A non centered figure. -
-
-

- Test the use of @title:

-
-
-This is a figure with a title
-This is a figure with a title
-@title: and here it is: a title, don't mess it up *
-
-
-
-
-
-
-

-A.11. Verse tests -

-

- This is a verse text This is another line

-
-
-
-
-
-

-Index -

-
-

- L - T

-
- -
-
-
-

-Author's Address -

-
-
R. (Miek) Gieben
-
Google
-
123 Buckingham Palace Road
-
London
-
SW1W 9SH
-
United Kingdom
- -
-URI: -http://miek.nl/ -
-
-
-
- - - diff --git a/tests/valid/draft-miek-test.v3.py37.html b/tests/valid/draft-miek-test.v3.py37.html deleted file mode 100644 index 2f6a3ddc7..000000000 --- a/tests/valid/draft-miek-test.v3.py37.html +++ /dev/null @@ -1,1977 +0,0 @@ - - - - - - -Writing I-Ds and RFCs using Pandoc and xml2rfc 2.x - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-DraftPandoc2rfc Version 2January 2013
GiebenExpires July 5, 2013[Page]
-
-
-
-
Workgroup:
-
RFC Beautification Working Group
-
Internet-Draft:
-
draft-gieben-writing-rfcs-pandoc-02
-
Published:
-
- -
-
Intended Status:
-
Informational
-
Expires:
-
-
Author:
-
-
-
R. Gieben
-
Google
-
-
-
-
-

Writing I-Ds and RFCs using Pandoc and xml2rfc 2.x

-
-

Abstract

-

- This memo presents a technique for using Pandoc syntax as a source - format for documents in the Internet-Drafts (I-Ds) and Request for - Comments (RFC) series.

-

- This version is adapted to work with "xml2rfc" version 2.x.

-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at http://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on July 5, 2013.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-
-

-1. Introduction -

-

- This document presents a technique for using Pandoc syntax as a - source format for documents in the Internet-Drafts (I-Ds) and - Request for Comments (RFC) series.

-

- This version is adapted to work with - xml2rfc version 2.x.

-

- Pandoc is an "almost plain text" format and therefor particularly - well suited for editing RFC-like documents.

-
    -
  • - Note: this document is typeset in Pandoc and does not render - completely correct when reading it on github. -
    • -
-
-
-
-
-

-2. Pandoc to RFC -

-
    -
  • - Pandoc2rfc -- designed to do the right thing, until it doesn't. -
    • -
-

- When writing [RFC4641] - we directly wrote the XML. Needless to say it was tedious even thought - the XML of xml2rfc - is very "light". The - latest version of xml2rfc version 2 can be found here.

-

- During the last few years people have been developing markup - languages that are very easy to remember and type. These languages - have become known as - almost plain - text-markup languages. One of the first was the - Markdown - syntax. One that was developed later and incorporates Markdown and - a number of extensions is - Pandoc. The - power of Pandoc also comes from the fact that it can be translated - to numerous output formats, including, but not limited to: HTML, - (plain) Markdown and - docbook XML.

-

- So using Pandoc for writing RFCs seems like a sane choice. As - xml2rfc uses XML, - the easiest way would be to create - docbook - XML and transform that using XSLT. Pandoc2rfc does just that. The - conversions are, in some way amusing, as we start off with - (almost) plain text, use elaborate XML and end up with plain text - again.

-
-
-
-
-+-------------------+   pandoc   +---------+
-| ALMOST PLAIN TEXT |   ------>  | DOCBOOK |
-+-------------------+            +---------+
-              |                       |
-non-existent  |                       | xsltproc
-  faster way  |                       |
-              v                       v
-      +------------+    xml2rfc  +---------+
-      | PLAIN TEXT |  <--------  | XML2RFC |
-      +------------+             +---------+
-
-
-
Figure 1: -Attempt to justify Pandoc2rfc. -
-
-

- The XML generated (the output after the - xsltproc step in - Figure 1) - is suitable for inclusion in either the - middle or - back section of - an RFC. The simplest way is to create a template XML file and - include the appropriate XML:

-
-
-
-
-<?xml version='1.0' ?>
-<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' [
-<!ENTITY pandocMiddle PUBLIC '' 'middle.xml'>
-<!ENTITY pandocBack   PUBLIC '' 'back.xml'>
-]>
-
-<rfc ipr='trust200902' docName='draft-gieben-pandoc-rfcs-02'>
- <front>
-    <title>Writing I-Ds and RFCs using Pandoc v2</title>
-</front>
-
-<middle>
-    &pandocMiddle;
-</middle>
-
-<back>
-    &pandocBack;
-</back>
-
-</rfc>
-
-
-
Figure 2: -A minimal template.xml. -
-
-

- See the Makefile for an example of this. In this case you need to - edit 3 documents:

-
    -
  1. - middle.pdc - contains the main body of text; -
    2. -
  2. - back.pdc - holds appendices and references; -
    3. -
  3. - template.xml (probably a fairly static file). -
    4. -
-

- The draft - (draft.txt) you - are reading now, is automatically created when you call - make. The - homepage of Pandoc2rfc is - this github - repository.

-
-
-

-2.1. Dependencies -

-

- It needs xsltproc - and pandoc to be - installed. See the - Pandoc - user manual for the details on how to type in Pandoc style. - And of course xml2rfc - version two.

-

- When using Pandoc2rfc consider adding the following sentence to - an Acknowledgements section:

-
-
- This document was produced using the Pandoc2rfc tool.
-
-
-
-
-
-
-
-
-

-3. Starting a new project -

-

- When starting a new project with - pandoc2rfc you'll - need to copy the following files:

-
    -
  • - Makefile -
    • -
  • - transform.xslt -
    • -
  • -

    - And the above mentioned files:

    -
      -
    • - middle.pdc -
      • -
    • - back.pdc -
      • -
    • - template.xml -
      • -
    -
    • -
-

- After that you can start editing.

-
-
-
-
-

-4. Supported Features -

- -
-
-
-
-

-5. Unsupported Features -

-
    -
  • - Lists inside a table (xml2rfc doesn't handle this); -
    • -
  • - Pandoc markup in the caption for figures/artwork. Pandoc markup for table captions is supported; -
    • -
  • - crefs: for comments (no input syntax available), use HTML comments: <!-- ... -->; -
    • -
-
-
-
-
-

-6. Acknowledgements -

-

- The following people have helped to make Pandoc2rfc what it is today: Benno Overeinder, Erlend Hamnaberg, Matthijs Mekking, Trygve Laugstoel.

-

- This document was prepared using Pandoc2rfc.

-
-
-
-
-

-7. Pandoc Constructs -

-

- So, what syntax do you need to use to get the correct output? Well, it is - just Pandoc. The best introduction - to the Pandoc style is given in this - README from Pandoc itself.

-

- For convenience we list the most important ones in the following sections.

-
-
-

-7.1. Paragraph -

-

- Paragraphs are separated with an empty line.

-
-
-
-
-

-7.2. Section -

-

- Just use the normal sectioning commands available in Pandoc, for instance:

-
-
-# Section1 One
-Bla
-
-
-

- Converts to: <section title="Section1 - One" anchor="section1-one"> If you have another section that is also - named "Section1 One", that anchor will be called "section1-one-1", but - only when the sections are in - the same source file!

-

- Referencing the section is done with see - [](#section1-one), as in see Section 7.2.

-
-
-
-
-

-7.3. List Styles -

-

- A good number of styles are supported.

-
-
-

-7.3.1. Symbol -

-
-
-A symbol list.
-
-* Item one;
-* Item two.
-
-
-

- Converts to <list style="symbol">:

-
    -
  • - Item one; -
    • -
  • - Item two. -
    • -
-
-
-
-
-

-7.3.2. Number -

-
-
-A numbered list.
-
-1. Item one;
-1. Item two.
-
-
-

- Converts to <list style="numbers">:

-
    -
  1. - Item one; -
    2. -
  2. - Item two. -
    3. -
-
-
-
-
-

-7.3.3. Empty -

-

- Using the default list markers from Pandoc:

-
-
-A list using the default list markers.
-
-#. Item one;
-#. Item two.
-
-
-

- Converts to <list style="empty">:

-
    -
  • - Item one; -
    • -
  • - Item two. -
    • -
-
-
-
-
-

-7.3.4. Roman -

-

- Use the supported Pandoc syntax:

-
-
-ii. Item one;
-ii. Item two.
-
-
-

- Converts to <list style="format %i.">:

-
-
i.
-
- Item one; -
-
-
ii.
-
- Item two. -
-
-
-

- If you use uppercase Roman numerals, they convert to a different style:

-
-
-II. Item one;
-II. Item two.
-
-
-

- Yields <list style="format (%d) ">:

-
-
(1)
-
- Item one; -
-
-
(2)
-
- Item two. -
-
-
-
-
-
-
-

-7.3.5. Letter -

-

- A numbered list.

-
-
-a.  Item one;
-b.  Item two.
-
-
-

- Converts to <list style="letters">:

-
    -
  1. - Item one; -
    2. -
  2. - Item two. -
    3. -
-

- Uppercasing the letters works too (note two spaces after the letter.

-
-
-A.  Item one;
-B.  Item two.
-
-
-

- Becomes:

-
-
A.
-
- Item one; -
-
-
B.
-
- Item two. -
-
-
-
-
-
-
-

-7.3.6. Hanging -

-

- This is more like a description list, so we need to use:

-
-
-First item that needs clarification:
-
-:   Explanation one
-More stuff, because item is difficult to explain.
-* item1
-* item2
-
-Second item that needs clarification:
-
-:   Explanation two
-
-
-

- Converts to: <list style="hanging"> and <t hangText="First item that...">

-

- If you want a newline after the hangTexts, search for the string OPTION in transform.xsl and uncomment it.

-
-
-
-
-
-
-

-7.4. Figure/Artwork -

-

- Indent the paragraph with 4 spaces.

-
-
-Like this
-
-
-

- Converts to: - <figure><artwork> ... - Note that xml2rfc - supports a caption with - <artwork>. Pandoc does not - support this, but Pandoc2rfc does. If you add a - @Figure: some text as the last - line, the artwork gets a title - attribute with the text after - @Figure:. It will also be - possible to reference the artwork. If a caption is supplied the artwork will be - centered. If a caption is needed but the figure should not be centered use - @figure:\.

-
-
-

-7.4.1. References -

-

- The reference anchor attribute will be: fig: - + first 10 (normalized) characters from the caption. - Where normalized means:

-
    -
  • - Take the first 10 characters of the caption (i.e. this is the text - after the string - @Figure:); -
    • -
  • - Spaces and single quotes (') are translated to a minus - -; -
    • -
  • - Uppercase letters translated to lowercase. -
    • -
-

- So the first artwork with a caption will get - fig:a-minimal- - as a reference. See for instance - Figure 2.

-

- This anchoring is completely handled from within the - xslt. - Note that duplicate anchors are an XML validation error which will make - xml2rfc fail.

-
-
-
-
-
-
-

-7.5. Block Quote -

-

- Any paragraph like:

-
-
-> quoted text
-
-
-

- Converts to: <t><list style="empty"> ... - paragraph, making it indented.

-
-
-
-
-

-7.6. References -

-
-
-

-7.6.1. External -

-

- Any reference like:

-
-
-[Click here](URI)
-
-
-

- Converts to: <ulink target="URI">Click here ...

-
-
-
-
-

-7.6.2. Internal -

-

- Any reference like:

-
-
-[Click here](#localid)
-
-
-

- Converts to: <link target="localid">Click here ...

-

- For referring to RFCs (for which you manually need add the reference source in - the template, with an external XML entity), you can just use:

-
-
-[](#RFC2119)
-
-
-

- And it does the right thing. Referencing sections is done with:

-
-
-See [](#pandoc-constructs)
-
-
-

- The word 'Section' is inserted automatically: ... see - Section 7 - ... For referencing figures/artworks see - Section 7.4. - For referencing tables see Section 7.8.

-
-
-
-
-
-
-

-7.7. Spanx Styles -

-

- The verb style can be selected with back-tics: - `text` - Converts to: - <spanx style="verb"> ...

-

- And the emphasis style with asterisks: - *text* - or underscores: _text_ - Converts to: <spanx style="emph"> ...

-

- And the emphasis style with double asterisks: - **text** - Converts to: <spanx style="strong"> ...

-
-
-
-
-

-7.8. Tables -

-

- A table can be entered as:

-
-
-
-
-  Right     Left     Center     Default
-  -------   ------ ----------   -------
-       12     12        12        12
-      123     123       123       123
-        1     1         1         1
-
-  Table: A caption describing the table.
-
-
-
Figure 3: -A caption describing the figure describing the table. -
-
-

- Is translated to <texttable> - element in xml2rfc. - You can choose multiple styles as input, but they all are converted to the same style (plain - <texttable>) table in - xml2rfc. The column alignment - is copied over to the generated XML.

-
-
-

-7.8.1. References -

-

- The caption is always - translated to a title - attribute. If a table has a caption, it will - also get a reference. - The reference anchor attribute will be: - tab- - + first 10 (normalized) characters from the caption. - Where normalized means:

-
    -
  • - Take the first 10 characters of the caption (i.e. this is the text - after the string - Table:); -
    • -
  • - Spaces and single quotes (') are translated to a minus - -; -
    • -
  • - Uppercase letters translated to lowercase. -
    • -
-

- So the first table with a caption will get - tab-a-caption- - for reference use. See for instance

-

- This anchoring is completely handled from within the - xslt. - Note that duplicate anchors are an XML validation error which will make - xml2rfc fail.

-
-
-
-
-
-
-

-7.9. Indexes -

-

- The footnote syntax of Pandoc is slightly abused to support an index. Footnotes are entered in two steps, you have a marker in the text, and later you give actual footnote text. Like this:

-
-
-[^1]
-
-[^1]: footnote text
-
-
-

- We re-use this syntax for the <iref> tag. The above text translates to:

-
-
-<iref item="footnote text"/>
-
-
-

- Sub items are also supported. Use an exclamation mark (!) to separate them:

-
-
-[^1]: item!sub item
-
-
-
-
-
-
-
-
-

-8. Usage guidelines -

-
-
-

-8.1. Working with multiple files -

-

- As an author you will probably break up a draft in multiple files, each dealing - with a subject or section. When doing so sections with the same title will clash - with each other. Pandoc can deal with this situation, but only if the different - sections are in the same file or - processed in the same Pandoc run. Concatenating the different section files - before processing them is a solution to this problem. You can, for instance, - amend the Makefile and add - something like this:

-
-
-allsections.pdc: section.pdc.1 section.pdc.2 section.pdc.3
-        cat $@ > allsections.pdc
-
-
-

- And then process allsection.pdc in the normal way.

-
-
-
-
-

-8.2. Setting the title -

-

- If you use double quotes in the documents title in the - docName attribute, like:

-
-
-<rfc ipr="trust200902" docName="draft-gieben-writing-rfcs-pandoc-02">
-
-
-

- The Makefile will pick this up automatically and make a symbolic link:

-
-
-draft-gieben-writing-rfcs-pandoc-00.txt -> draft.txt
-
-
-

- This makes uploading the file to the i-d tracker a bit easier.

-
-
-
-
-

-8.3. Uploading the XML/txt -

-

- The draft.xml target will - generate an XML file with all XML included, so you can upload just one file to - the I-D tracker.

-
-
-
-
-

-8.4. VIM syntax highlighting -

-

- If you are a VIM user you might be interested in a syntax highlighting file (see - [VIM]) that slightly lightens up - your reading experience while viewing a draft.txt from VIM.

-
-
-
-
-
-
-

-9. Security Considerations -

-

- This document raises no security issues.

-
-
-
-
-

-10. IANA Considerations -

-

- This document has no actions for IANA.

-
-
-
-

-11. References -

-
-

-11.1. Informative References -

-
-
[VIM]
-
-Gieben, R., "VIM syntax file for RFCs and I-Ds", , <http://github.com/miekg/rfc>.
-
-
-
-
-

-11.2. Normative References -

-
-
[RFC2119]
-
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, , <ftp://ftp.isi.edu/in-notes/rfc2119.txt>.
-
-
[RFC4641]
-
-Kolkman, O. and R. Gieben, "DNSSEC Operational Practices", RFC 4641, , <http://www.rfc-editor.org/rfc/rfc4641.txt>.
-
-
-
-
-
-
-

-Appendix A. Tests -

-

- This appendix consists out of a few tests that should all render to proper - xml2rfc XML.

- -
-
-

-A.2. Markup in heading -

-

- This is discarded by xml2rfc.

-
-
-
-
-

-A.3. Blockquote -

-
    -
  • - This is a blockquote, how does it look? -
    • -
-
-
-
-
-

-A.4. Verbatim code blocks -

-
-
-A verbatim code block
-jkasjksajassjasjsajsajkas
-
-
-
-
-
-
-

-A.5. Reference Tests -

-

- Refer to RFC 2119 [RFC2119] if you will. Or maybe you want to inspect Figure 2 in Section 2 again. Or you might want to Click here.

-
-
-
-
-

-A.6. Spanx Tests -

-
    -
  • - underscores: underscores -
    • -
  • - asterisks: asterisks -
    • -
  • - double asterisks: double asterisks -
    • -
  • - backticks: backticks -
    • -
-
-
-
-
-

-A.7. List Tests -

-
    -
  1. - First we do -
    2. -
  2. -

    - And then

    -
      -
    • - item 1 -
      • -
    • - item 2 -
      • -
    -
    3. -
-

- And the other around.

-
    -
  • - First we do -
    • -
  • -

    - Then

    -
      -
    1. - Something -
      2. -
    2. - Another thing -
      3. -
    -
    • -
-

- Description lists:

-
-
Item to explain:
-
It works because of herbs. -
-
-
Another item to explain:
-
-

More explaining.

-

Multiple paragraphs in such a list.

-
-
-
-

- lists in description lists.

-
-
Item to explain:
-
-

It works because of

-
    -
  1. - One -
    2. -
  2. - Two -
    3. -
-
-
-
Another item to explain:
-
More explaining -
-
-
Item to explain:
-
-

It works because of

-
    -
  1. - One1 -
    2. -
  2. -

    - Two1

    -
      -
    • - Itemize list -
      • -
    • - Another item -
      • -
    -
    3. -
-
-
-
Another item to explain again:
-
More explaining -
-
-
-

- list with description lists.

-
    -
  1. -

    - More

    -
    -
    Item to explain:
    -
    Explanation ... -
    -
    -
    Item to explain:
    -
    Another explanation ... -
    -
    -
    -
    2. -
  2. - Go'bye -
    3. -
-

- Multiple paragraphs in a list.

-
    -
  1. -

    - This is the first bullet point and it needs multiple paragraphs...

    -

    ... to be explained properly.

    -
    2. -
  2. - This is the next bullet. New paragraphs should be indented with 4 four spaces. -
    3. -
  3. -

    - Another item with some artwork, indented by 8 spaces.

    -
    -
    -Artwork
-
    -
    -
    4. -
  4. - Final item. -
    5. -
-

- xml2rfc does not allow this, so the second paragraph is faked with a

-
-
-<vspace blankLines='1'>
-
-
-

- Ordered lists.

-
    -
  1. - First item -
    2. -
  2. - Second item -
    3. -
-

- A lowercase roman list:

-
-
i.
-
- Item 1 -
-
-
ii.
-
- Item 2 -
-
-
-

- An uppercase roman list.

-
-
(1)
-
- Item1 -
-
-
(2)
-
- Item2 -
-
-
(3)
-
- Item 3 -
-
-
-

- And default list markers.

-

- Some surrounding text, to make it look better.

-
    -
  • - First item. Use lot of text to get a real paragraphs sense. - First item. Use lot of text to get a real paragraphs sense. - First item. Use lot of text to get a real paragraphs sense. - First item. Use lot of text to get a real paragraphs sense. -
    • -
  • - Second item. So this is the second para in your list. Enjoy; -
    • -
  • - Another item. -
    • -
-

- Text at the end.

-

- Lowercase letters list.

-
    -
  1. - First item -
    2. -
  2. - Second item -
    3. -
-

- Uppercase letters list.

-
-
A.
-
- First item -
-
-
B.
-
- Second item -
-
-
-

-

-

- And artwork in a description list.

-
-
Item1:
-
-

- Tell something about it. Tell something about it. Tell something about - it. Tell something about it. Tell something about it. Tell something about it.

-
-
-miek.nl.    IN  NS  a.miek.nl.
-a.miek.nl.  IN  A   192.0.2.1    ; <- this is glue
-
-
-

- Tell some more about it. Tell some more about it. Tell some more about it.

-
-
-
Item2:
-
Another description -
-
-
-

- List with a sublist with a paragraph above the sublist

-
    -
  1. - First Item -
    2. -
  2. - Second item -
    3. -
  3. -

    - Third item

    -

    A paragraph that comes first

    -
      -
    1. - But what do you know -
      2. -
    2. - This is another list -
      3. -
    -
    4. -
-
-
-
-
-

-A.8. Table Tests -

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -Demonstration of simple table - syntax. -
Right Left Center Default
12 12 12 12
123 123 123 123
1 1 1 1
-
-
- - - - - - - - - - - - - - - - - - - - - - - - -
-Table 2: -Here's the caption. It, too, may span multiple lines. This is a - multiline table. This is verbatim text. -
Centered Header Default Aligned Right Aligned Left Aligned
First row 12.0 Example of a row that spans multiple lines.
Second row 5.0 Here's another one. Note the blank line between rows.
-
-

-

-
- - - - - - - - - - - - - - - - - - - - - -
-Table 3: -Sample grid table. -
Fruit Price Advantages
Bananas $1.34 built-in wrapper
Oranges $2.10 cures scurvy
-
-

- Grid tables without a caption

- - - - - - - - - - - - - - - - - - - - - -
Table 4
Fruit Price Advantages
Bananas $1.34 built-in wrapper
Oranges $2.10 cures scurvy
-

- This table has no caption, and therefor no reference. But you can refer to some of the other tables, with for instance:

-
-
-See [](#tab-here-s-the)
-
-
-

- Which will become "See Table 2".

-

-

-

- We should also be able to refer to the table numbers directly, to say things like - 'Look at Tables - 1, - 2 - and 3.'

-
-
-
-
-

-A.9. Numbered examples -

-

- This is another example:

-
    -
  1. - Another bla bla.. -
    2. -
-

- as (1) shows...

-
-
-
-
-

-A.10. Figure tests -

-
-
-
-
-This is a figure
-This is a figure
-This is a figure
-This is a figure
-
-
-
Figure 4: -This is the caption, with text in `typewriter`. Which isnt converted to a <spanx> style, because this is copied as-is. -
-
-

- And how a figure that is not centered, do to using figure and not Figure.

-
-
-
-
-This is a figure
-This is a figure
-
-
-
Figure 5: -A non centered figure. -
-
-

- Test the use of @title:

-
-
-This is a figure with a title
-This is a figure with a title
-@title: and here it is: a title, don't mess it up *
-
-
-
-
-
-
-

-A.11. Verse tests -

-

- This is a verse text This is another line

-
-
-
-
-
-

-Index -

-
-

- L - T

-
- -
-
-
-

-Author's Address -

-
-
R. (Miek) Gieben
-
Google
-
123 Buckingham Palace Road
-
London
-
SW1W 9SH
-
United Kingdom
- -
-URI: -http://miek.nl/ -
-
-
-
- - - diff --git a/tests/valid/draft-template.v3.py36.html b/tests/valid/draft-template.v3.html similarity index 99% rename from tests/valid/draft-template.v3.py36.html rename to tests/valid/draft-template.v3.html index b0b6fa9d1..a33eb4adc 100644 --- a/tests/valid/draft-template.v3.py36.html +++ b/tests/valid/draft-template.v3.html @@ -11,7 +11,7 @@ Insert an abstract: MANDATORY. This template is for creating an Internet Draft. " name="description"> - + diff --git a/tests/valid/draft-template.v3.py37.html b/tests/valid/draft-template.v3.py37.html deleted file mode 100644 index b0b6fa9d1..000000000 --- a/tests/valid/draft-template.v3.py37.html +++ /dev/null @@ -1,922 +0,0 @@ - - - - - - -Put Your Internet Draft Title Here - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-DraftAbbreviated TitleMarch 2009
Davies & ZhaoExpires September 2, 2009[Page]
-
-
-
-
Workgroup:
-
Internet Engineering Task Force
-
Internet-Draft:
-
draft-ietf-xml2rfc-template-05
-
Published:
-
- -
-
Intended Status:
-
Informational
-
Expires:
-
-
Authors:
-
-
-
E.B. Davies, Ed. -
-
Folly Consulting
-
-
-
Q. Zhao
-
Huawei Technology
-
-
-
-
-

Put Your Internet Draft Title Here

-
-

Abstract

-

Insert an abstract: MANDATORY. This template is for creating an - Internet Draft.

-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at http://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on September 2, 2009.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-

-1. Introduction -

-

The original specification of xml2rfc format is in RFC 2629 [RFC2629].

-
-

-1.1. Requirements Language -

-

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this - document are to be interpreted as described in RFC 2119 [RFC2119].

-
-
-
-
-

-2. Simple List -

-

List styles: 'empty', 'symbols', 'letters', 'numbers', 'hanging', - 'format'.

-
    -
  • First bullet -
    • -
  • Second bullet -
    • -
-

You can write text here as well.

-
-
-
-

-3. Figures -

-

Figures should not exceed 69 characters wide to allow for the indent - of sections.

-

Preamble text - can be omitted or empty.

-
-
-
-
- - - - - -
-
-
Figure 1
-
-

Cross-references allowed in pre- and postamble. [min_ref].

-

The CDATA means you don't need to escape meta-characters (especially - < (&lt;) and & (&amp;)) but is not essential. - Figures may also have a title attribute but it won't be displayed unless - there is also an anchor. White space, both horizontal and vertical, is - significant in figures even if you don't use CDATA.

-
-
-

-4. Subsections and Tables -

-
-

-4.1. A Subsection -

-

By default 3 levels of nesting show in table of contents but that - can be adjusted with the value of the "tocdepth" processing - instruction.

-
-
-

-4.2. Tables -

-

.. are very similar to figures:

-

Tables use ttcol to define column headers and widths. - Every cell then has a "c" element for its content.

-
- - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -A Very Simple Table -
ttcol #1ttcol #2
c #1c #2
c #3c #4
c #5c #6
-
-

which is a very simple example.

-
-
-
-
-

-5. More about Lists -

-

Lists with 'hanging labels': the list item is indented the amount of - the hangIndent:

-
-
short
-
With a label shorter than the hangIndent. -
-
-
fantastically long label
-
With a label longer than the - hangIndent. -
-
-
vspace_trick
-
Forces the new - item to start on a new line. -
-
-
-

Simulating more than one paragraph in a list item using - <vspace>:

-
    -
  1. First, a short item. -
    2. -
  2. -

    Second, a longer list item.

    -

    And - something that looks like a separate pararaph..

    -
    3. -
-

Simple indented paragraph using the "empty" style:

-
    -
  • The quick, brown fox jumped over the lazy dog and lived to fool - many another hunter in the great wood in the west. -
    • -
-
-

-5.1. Numbering Lists across Lists and Sections -

-

Numbering items continuously although they are in separate - <list> elements, maybe in separate sections using the "format" - style and a "counter" variable.

-

First list:

-
-
R1
-
#1 -
-
-
R2
-
#2 -
-
-
R3
-
#3 -
-
-
-

Specify the indent explicitly so that all the items line up - nicely.

-

Second list:

-
-
R4
-
#4 -
-
-
R5
-
#5 -
-
-
R6
-
#6 -
-
-
-
-
-

-5.2. Where the List Numbering Continues -

-

List continues here.

-

Third list:

-
-
R7
-
#7 -
-
-
R8
-
#8 -
-
-
R9
-
#9 -
-
-
R10
-
#10 -
-
-
-

The end of the list.

-
-
-

-5.3. nested lists -

-

Simulating more than one paragraph in a list item using - <vspace>:

-
    -
  1. First, a short item. -
    2. -
  2. -

    Second, a longer list item.

    -

    And - something that looks like a separate paragraph.

    -
    3. -
  3. -

    and a sublist, also with letters

    -
      -
    1. first subitem -
      2. -
    2. second subitem -
      3. -
    3. -

      and a sub-sublist, also with letters

      -
        -
      1. first sub-subitem -
        2. -
      2. second sub-subitem -
        3. -
      -
      4. -
    -
    4. -
-
-
-

-5.4. List Formats -

-

many formats

-
-
a
-
first %c-item -
-
-
b
-
more %c-items -
-
-
-
-
A
-
first %C-item -
-
-
B
-
more %C-items -
-
-
-
-
1
-
first %d-item. -
-
-
2
-
more %d-items. -
-
-
-
-
i
-
first %i-item -
-
-
ii
-
more %i-items -
-
-
iii
-
more %i-items -
-
-
iv
-
more %i-items -
-
-
v
-
more %i-items -
-
-
vi
-
more %i-items -
-
-
vii
-
more %i-items -
-
-
viii
-
more %i-items -
-
-
ix
-
more %i-items -
-
-
-
-
I
-
first %I-item -
-
-
II
-
more %I-items -
-
-
III
-
more %I-items -
-
-
IV
-
more %I-items -
-
-
V
-
more %I-items -
-
-
VI
-
more %I-items -
-
-
VII
-
more %I-items -
-
-
VIII
-
more %I-items -
-
-
IX
-
more %I-items -
-
-
-
-
1
-
first %o-item -
-
-
2
-
more %o-items -
-
-
3
-
more %o-items -
-
-
4
-
more %o-items -
-
-
5
-
more %o-items -
-
-
6
-
more %o-items -
-
-
7
-
more %o-items -
-
-
10
-
more %o-items -
-
-
11
-
more %o-items -
-
-
-
-
1
-
first %x-item -
-
-
2
-
more %x-items -
-
-
3
-
more %x-items -
-
-
4
-
more %x-items -
-
-
5
-
more %x-items -
-
-
6
-
more %x-items -
-
-
7
-
more %x-items -
-
-
8
-
more %x-items -
-
-
9
-
more %x-items -
-
-
a
-
more %x-items -
-
-
b
-
more %x-items -
-
-
c
-
more %x-items -
-
-
d
-
more %x-items -
-
-
e
-
more %x-items -
-
-
f
-
more %x-items -
-
-
10
-
more %x-items -
-
-
11
-
more %x-items -
-
-
-
-
1
-
first %X-item -
-
-
2
-
more %X-items -
-
-
3
-
more %X-items -
-
-
4
-
more %X-items -
-
-
5
-
more %X-items -
-
-
6
-
more %X-items -
-
-
7
-
more %X-items -
-
-
8
-
more %X-items -
-
-
9
-
more %X-items -
-
-
A
-
more %X-items -
-
-
B
-
more %X-items -
-
-
C
-
more %X-items -
-
-
D
-
more %X-items -
-
-
E
-
more %X-items -
-
-
F
-
more %X-items -
-
-
10
-
more %X-items -
-
-
11
-
more %X-items -
-
-
-
-
-
-
-
-

-6. Example of Code or MIB Module To Be Extracted -

-

The <artwork> element has a number of extra attributes - that can be used to substitute a more aesthetically pleasing rendition - into HTML output while continuing to use the ASCII art version in the - text and nroff outputs (see the xml2rfc README for details). It also - has a "type" attribute. This is currently ignored except in the case - 'type="abnf"'. In this case the "artwork" is expected to contain a - piece of valid Augmented Backus-Naur Format (ABNF) grammar. This will - be syntax checked by xml2rfc and any errors will cause a fatal error - if the "strict" processing instruction is set to "yes". The ABNF will - also be colorized in HTML output to highlight the syntactic - components. Checking of additional "types" may be provided in future - versions of xml2rfc.

-
-
<CODE BEGINS> file "example.c"
-
-
-/**** an example C program */
-
-#include <stdio.h>
-
-void
-main(int argc, char *argv[])
-{
-    int i;
-
-    printf("program arguments are:\n");
-    for (i = 0; i < argc; i++) {
-        printf("%d: \"%s\"\n", i, argv[i]);
-    }
-
-    exit(0);
-} /* main */
-
-/* end of file */
-
-
-<CODE ENDS>
-
-
-
-
-
-

-7. Acknowledgements -

-

This template was derived from an initial version written by Pekka - Savola and contributed by him to the xml2rfc project.

-

- This document is part of a plan to make xml2rfc indispensable [DOMINATION]. - This document may be shared as needed [SHARING]. If necessary, appeal to [JUPITER].

-
-
-
-
-

-8. IANA Considerations -

-

This memo includes no request to IANA.

-

All drafts are required to have an IANA considerations section (see - the update of - RFC 2434 [I-D.narten-iana-considerations-rfc2434bis] for a guide). If the draft does not require IANA to do - anything, the section contains an explicit statement that this is the - case (as above). If there are no requirements for IANA, the section will - be removed during conversion into an RFC by the RFC Editor.

-
-
-
-
-

-9. Security Considerations -

-

All drafts are required to have a security considerations section. - See RFC 3552 [RFC3552] for a guide.

-
-
-
-

-10. References -

-
-

-10.1. Normative References -

-
-
[min_ref]
-
-authSurName, authInitials., "Minimal Reference", .
-
-
[RFC2119]
-
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
-
-
-
-
-

-10.2. Informative References -

-
-
[DOMINATION]
-
-Mad Dominators, Inc., "Ultimate Plan for Taking Over the World", , <http://www.example.com/dominator.html>.
-
-
[I-D.narten-iana-considerations-rfc2434bis]
-
-Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", Work in Progress, Internet-Draft, draft-narten-iana-considerations-rfc2434bis-09, , <https://www.ietf.org/archive/id/draft-narten-iana-considerations-rfc2434bis-09.txt>.
-
-
[JUPITER]
-
-Singh, A., Ong, J., Agarwal, A., Anderson, G., Armistead, A., Bannon, R., Boving, S., Desai, G., Felderman, B., Germano, P., Kanagala, A., Liu, H., Provost, J., Simmons, J., Tanda, E., Wanderer, J., Hölzle, U., Stuart, S., and A. Vahdat, "Jupiter rising: a decade of clos topologies and centralized control in Google's datacenter network", Communications of the ACM Vol. 59, pp. 88-97, DOI 10.1145/2975159, , <https://doi.org/10.1145/2975159>.
-
-
[RFC2629]
-
-Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, , <https://www.rfc-editor.org/info/rfc2629>.
-
-
[RFC3552]
-
-Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/info/rfc3552>.
-
-
[SHARING]
-
-Sesame Street, "I Learned to Share in Kindergarten", , <http://www.example.com/sharing.html>.
-
-
-
-
-
-
-

-Appendix A. Additional Stuff -

-

This becomes an Appendix.

-
-
-
-
-

-Contributors -

-

This becomes an unnumbered section

-
-
-
-
-

-Authors' Addresses -

-
-
Elwyn Davies (editor)
-
Folly Consulting
-
Soham
-
United Kingdom
-
-Phone: -+44 7889 488 335 -
- -
-
-
Quintin Zhao
-
Huawei Technology
-
125 Nagog Technology Park
-
-Acton, MA 01719 -
-
United States of America
- -
-
-
- - - diff --git a/tests/valid/draft-template.v3.py38.html b/tests/valid/draft-template.v3.py38.html deleted file mode 100644 index b0b6fa9d1..000000000 --- a/tests/valid/draft-template.v3.py38.html +++ /dev/null @@ -1,922 +0,0 @@ - - - - - - -Put Your Internet Draft Title Here - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-DraftAbbreviated TitleMarch 2009
Davies & ZhaoExpires September 2, 2009[Page]
-
-
-
-
Workgroup:
-
Internet Engineering Task Force
-
Internet-Draft:
-
draft-ietf-xml2rfc-template-05
-
Published:
-
- -
-
Intended Status:
-
Informational
-
Expires:
-
-
Authors:
-
-
-
E.B. Davies, Ed. -
-
Folly Consulting
-
-
-
Q. Zhao
-
Huawei Technology
-
-
-
-
-

Put Your Internet Draft Title Here

-
-

Abstract

-

Insert an abstract: MANDATORY. This template is for creating an - Internet Draft.

-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at http://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on September 2, 2009.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-

-1. Introduction -

-

The original specification of xml2rfc format is in RFC 2629 [RFC2629].

-
-

-1.1. Requirements Language -

-

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this - document are to be interpreted as described in RFC 2119 [RFC2119].

-
-
-
-
-

-2. Simple List -

-

List styles: 'empty', 'symbols', 'letters', 'numbers', 'hanging', - 'format'.

-
    -
  • First bullet -
    • -
  • Second bullet -
    • -
-

You can write text here as well.

-
-
-
-

-3. Figures -

-

Figures should not exceed 69 characters wide to allow for the indent - of sections.

-

Preamble text - can be omitted or empty.

-
-
-
-
- - - - - -
-
-
Figure 1
-
-

Cross-references allowed in pre- and postamble. [min_ref].

-

The CDATA means you don't need to escape meta-characters (especially - < (&lt;) and & (&amp;)) but is not essential. - Figures may also have a title attribute but it won't be displayed unless - there is also an anchor. White space, both horizontal and vertical, is - significant in figures even if you don't use CDATA.

-
-
-

-4. Subsections and Tables -

-
-

-4.1. A Subsection -

-

By default 3 levels of nesting show in table of contents but that - can be adjusted with the value of the "tocdepth" processing - instruction.

-
-
-

-4.2. Tables -

-

.. are very similar to figures:

-

Tables use ttcol to define column headers and widths. - Every cell then has a "c" element for its content.

-
- - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -A Very Simple Table -
ttcol #1ttcol #2
c #1c #2
c #3c #4
c #5c #6
-
-

which is a very simple example.

-
-
-
-
-

-5. More about Lists -

-

Lists with 'hanging labels': the list item is indented the amount of - the hangIndent:

-
-
short
-
With a label shorter than the hangIndent. -
-
-
fantastically long label
-
With a label longer than the - hangIndent. -
-
-
vspace_trick
-
Forces the new - item to start on a new line. -
-
-
-

Simulating more than one paragraph in a list item using - <vspace>:

-
    -
  1. First, a short item. -
    2. -
  2. -

    Second, a longer list item.

    -

    And - something that looks like a separate pararaph..

    -
    3. -
-

Simple indented paragraph using the "empty" style:

-
    -
  • The quick, brown fox jumped over the lazy dog and lived to fool - many another hunter in the great wood in the west. -
    • -
-
-

-5.1. Numbering Lists across Lists and Sections -

-

Numbering items continuously although they are in separate - <list> elements, maybe in separate sections using the "format" - style and a "counter" variable.

-

First list:

-
-
R1
-
#1 -
-
-
R2
-
#2 -
-
-
R3
-
#3 -
-
-
-

Specify the indent explicitly so that all the items line up - nicely.

-

Second list:

-
-
R4
-
#4 -
-
-
R5
-
#5 -
-
-
R6
-
#6 -
-
-
-
-
-

-5.2. Where the List Numbering Continues -

-

List continues here.

-

Third list:

-
-
R7
-
#7 -
-
-
R8
-
#8 -
-
-
R9
-
#9 -
-
-
R10
-
#10 -
-
-
-

The end of the list.

-
-
-

-5.3. nested lists -

-

Simulating more than one paragraph in a list item using - <vspace>:

-
    -
  1. First, a short item. -
    2. -
  2. -

    Second, a longer list item.

    -

    And - something that looks like a separate paragraph.

    -
    3. -
  3. -

    and a sublist, also with letters

    -
      -
    1. first subitem -
      2. -
    2. second subitem -
      3. -
    3. -

      and a sub-sublist, also with letters

      -
        -
      1. first sub-subitem -
        2. -
      2. second sub-subitem -
        3. -
      -
      4. -
    -
    4. -
-
-
-

-5.4. List Formats -

-

many formats

-
-
a
-
first %c-item -
-
-
b
-
more %c-items -
-
-
-
-
A
-
first %C-item -
-
-
B
-
more %C-items -
-
-
-
-
1
-
first %d-item. -
-
-
2
-
more %d-items. -
-
-
-
-
i
-
first %i-item -
-
-
ii
-
more %i-items -
-
-
iii
-
more %i-items -
-
-
iv
-
more %i-items -
-
-
v
-
more %i-items -
-
-
vi
-
more %i-items -
-
-
vii
-
more %i-items -
-
-
viii
-
more %i-items -
-
-
ix
-
more %i-items -
-
-
-
-
I
-
first %I-item -
-
-
II
-
more %I-items -
-
-
III
-
more %I-items -
-
-
IV
-
more %I-items -
-
-
V
-
more %I-items -
-
-
VI
-
more %I-items -
-
-
VII
-
more %I-items -
-
-
VIII
-
more %I-items -
-
-
IX
-
more %I-items -
-
-
-
-
1
-
first %o-item -
-
-
2
-
more %o-items -
-
-
3
-
more %o-items -
-
-
4
-
more %o-items -
-
-
5
-
more %o-items -
-
-
6
-
more %o-items -
-
-
7
-
more %o-items -
-
-
10
-
more %o-items -
-
-
11
-
more %o-items -
-
-
-
-
1
-
first %x-item -
-
-
2
-
more %x-items -
-
-
3
-
more %x-items -
-
-
4
-
more %x-items -
-
-
5
-
more %x-items -
-
-
6
-
more %x-items -
-
-
7
-
more %x-items -
-
-
8
-
more %x-items -
-
-
9
-
more %x-items -
-
-
a
-
more %x-items -
-
-
b
-
more %x-items -
-
-
c
-
more %x-items -
-
-
d
-
more %x-items -
-
-
e
-
more %x-items -
-
-
f
-
more %x-items -
-
-
10
-
more %x-items -
-
-
11
-
more %x-items -
-
-
-
-
1
-
first %X-item -
-
-
2
-
more %X-items -
-
-
3
-
more %X-items -
-
-
4
-
more %X-items -
-
-
5
-
more %X-items -
-
-
6
-
more %X-items -
-
-
7
-
more %X-items -
-
-
8
-
more %X-items -
-
-
9
-
more %X-items -
-
-
A
-
more %X-items -
-
-
B
-
more %X-items -
-
-
C
-
more %X-items -
-
-
D
-
more %X-items -
-
-
E
-
more %X-items -
-
-
F
-
more %X-items -
-
-
10
-
more %X-items -
-
-
11
-
more %X-items -
-
-
-
-
-
-
-
-

-6. Example of Code or MIB Module To Be Extracted -

-

The <artwork> element has a number of extra attributes - that can be used to substitute a more aesthetically pleasing rendition - into HTML output while continuing to use the ASCII art version in the - text and nroff outputs (see the xml2rfc README for details). It also - has a "type" attribute. This is currently ignored except in the case - 'type="abnf"'. In this case the "artwork" is expected to contain a - piece of valid Augmented Backus-Naur Format (ABNF) grammar. This will - be syntax checked by xml2rfc and any errors will cause a fatal error - if the "strict" processing instruction is set to "yes". The ABNF will - also be colorized in HTML output to highlight the syntactic - components. Checking of additional "types" may be provided in future - versions of xml2rfc.

-
-
<CODE BEGINS> file "example.c"
-
-
-/**** an example C program */
-
-#include <stdio.h>
-
-void
-main(int argc, char *argv[])
-{
-    int i;
-
-    printf("program arguments are:\n");
-    for (i = 0; i < argc; i++) {
-        printf("%d: \"%s\"\n", i, argv[i]);
-    }
-
-    exit(0);
-} /* main */
-
-/* end of file */
-
-
-<CODE ENDS>
-
-
-
-
-
-

-7. Acknowledgements -

-

This template was derived from an initial version written by Pekka - Savola and contributed by him to the xml2rfc project.

-

- This document is part of a plan to make xml2rfc indispensable [DOMINATION]. - This document may be shared as needed [SHARING]. If necessary, appeal to [JUPITER].

-
-
-
-
-

-8. IANA Considerations -

-

This memo includes no request to IANA.

-

All drafts are required to have an IANA considerations section (see - the update of - RFC 2434 [I-D.narten-iana-considerations-rfc2434bis] for a guide). If the draft does not require IANA to do - anything, the section contains an explicit statement that this is the - case (as above). If there are no requirements for IANA, the section will - be removed during conversion into an RFC by the RFC Editor.

-
-
-
-
-

-9. Security Considerations -

-

All drafts are required to have a security considerations section. - See RFC 3552 [RFC3552] for a guide.

-
-
-
-

-10. References -

-
-

-10.1. Normative References -

-
-
[min_ref]
-
-authSurName, authInitials., "Minimal Reference", .
-
-
[RFC2119]
-
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
-
-
-
-
-

-10.2. Informative References -

-
-
[DOMINATION]
-
-Mad Dominators, Inc., "Ultimate Plan for Taking Over the World", , <http://www.example.com/dominator.html>.
-
-
[I-D.narten-iana-considerations-rfc2434bis]
-
-Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", Work in Progress, Internet-Draft, draft-narten-iana-considerations-rfc2434bis-09, , <https://www.ietf.org/archive/id/draft-narten-iana-considerations-rfc2434bis-09.txt>.
-
-
[JUPITER]
-
-Singh, A., Ong, J., Agarwal, A., Anderson, G., Armistead, A., Bannon, R., Boving, S., Desai, G., Felderman, B., Germano, P., Kanagala, A., Liu, H., Provost, J., Simmons, J., Tanda, E., Wanderer, J., Hölzle, U., Stuart, S., and A. Vahdat, "Jupiter rising: a decade of clos topologies and centralized control in Google's datacenter network", Communications of the ACM Vol. 59, pp. 88-97, DOI 10.1145/2975159, , <https://doi.org/10.1145/2975159>.
-
-
[RFC2629]
-
-Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, , <https://www.rfc-editor.org/info/rfc2629>.
-
-
[RFC3552]
-
-Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, , <https://www.rfc-editor.org/info/rfc3552>.
-
-
[SHARING]
-
-Sesame Street, "I Learned to Share in Kindergarten", , <http://www.example.com/sharing.html>.
-
-
-
-
-
-
-

-Appendix A. Additional Stuff -

-

This becomes an Appendix.

-
-
-
-
-

-Contributors -

-

This becomes an unnumbered section

-
-
-
-
-

-Authors' Addresses -

-
-
Elwyn Davies (editor)
-
Folly Consulting
-
Soham
-
United Kingdom
-
-Phone: -+44 7889 488 335 -
- -
-
-
Quintin Zhao
-
Huawei Technology
-
125 Nagog Technology Park
-
-Acton, MA 01719 -
-
United States of America
- -
-
-
- - - diff --git a/tests/valid/draft-v3-features.v3.py38.html b/tests/valid/draft-v3-features.v3.html similarity index 99% rename from tests/valid/draft-v3-features.v3.py38.html rename to tests/valid/draft-v3-features.v3.html index 23a2f81b4..9a3b4be3c 100644 --- a/tests/valid/draft-v3-features.v3.py38.html +++ b/tests/valid/draft-v3-features.v3.html @@ -13,7 +13,7 @@ This document tests features introduced in xml2rfc v3 vocabulary. " name="description"> - + diff --git a/tests/valid/draft-v3-features.v3.py36.html b/tests/valid/draft-v3-features.v3.py36.html deleted file mode 100644 index 23a2f81b4..000000000 --- a/tests/valid/draft-v3-features.v3.py36.html +++ /dev/null @@ -1,5295 +0,0 @@ - - - - - - -xml2rfc V3 Feature Tests - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-Draftxml2rfc V3 Feature TestsApril 2017
Reschke, et al.Expires October 17, 2017[Page]
-
-
-
-
Workgroup:
-
Network Working Group
-
Internet-Draft:
-
draft-v3-features
-
Published:
-
- -
-
Intended Status:
-
Experimental
-
Expires:
-
-
Authors:
-
-
-
J. Reschke, Ed. -
-
-
-
-Πυθαγόρας ὁ Σάμιος (P. O. Samos)
-
-Εργαστήριο γεωμετρία (Geometry Labs)
-
-
-
A. Bergström
-
-
-
-
-

xml2rfc V3 Feature Tests

-
-

Abstract

-

- This document tests features introduced in xml2rfc v3 vocabulary.

-
-
-

-Note to Readers -

-

This note is to be removed before publishing as an RFC.

-

- Something important about this document.

-
-
-

This note is to be removed before publishing as an RFC.

-

- Something else important, this time with no <name>.

-
-
-

This note is to be removed before publishing as an RFC.

-

The warning in this note should not be doubled.

-
-
-

-Another Note -

-

This note is to be removed before publishing as an RFC.

-

The warning in this note should not be doubled either.

-
-
-

-Yet Another Note -

-

This note is to be removed before publishing as an RFC.

-

The removeInRFC warning is only ever the first paragraph, so if a paragraph like this:

-

This note is to be removed before publishing as an RFC.

-

appears but is not the first paragraph, the warning should be added again.

-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at http://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on October 17, 2017.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-

-1. Text Styles -

- -
-

-1.1. em/strong -

-

- This is emphasized. This is strong. - This is both. - So is this.

-
-
-

-1.2. tt -

-

- This is monospaced. Standard 78: [STD78].

-
-
-

-1.3. bcp14 -

-

- This is a BCP14 MUST.

-
-
-

-1.4. sup/sub -

-

- This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is subscript. - This is superscript. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text.

-
-
-
-

-2. Section Titles -

- - - - -
-
-

-2.4. Test: Comment -

-

- cref - Text after comment

-

More text after comment

-
-
-
-
-

-3. Renaming References -

- -

- Test: [0REFTEST].

-
-
-
-

-4. Lists -

-
-

-4.1. Definition Lists -

-

newline=default/spacing=default

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=true/spacing=default

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=false/spacing=default

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=default/spacing=compact

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=false/spacing=compact

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=true/spacing=compact

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

markup

-
-
-
Term1
-
-
Description1. Description1. Description1. Description1. -
-
-
-

multi-paragraph

-
-
Term1
-
-

Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1.

-

Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2.

-
-
-
-

nested list

-
-
Term1
-
-

Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1.

-
-
Term1b
-
Description 1b. -
-
-
-
-
-
Term2
-
-
-
Term2b
-
Description 2b. -
-
-
-
-
-
-
-
-

-4.2. Ordered Lists -

-
    -
  1. -
    One -
    -
    2. -
  2. Two 2 -
    3. -
  3. Three 3 -
    4. -
-

- List item 1 is "One".

-
    -
  1. -
    -

    The quick brown fox jumps over the lazy dog.

    -

    The quick brown fox jumps over the lazy dog.

    -
    -
    2. -
-

- List item 4 is the list above.

-
-
    -
  1. list 1 / item 1 -
    2. -
  2. list 1 / item 2 -
    3. -
-
-

The items below should continue ordering from above.

-
-
    -
  1. list 1 / item 3 -
    2. -
  2. list 1 / item 4 -
    3. -
-
-

The items below should be numbered starting with 17.

-
-
    -
  1. list 1 / item 17 -
    2. -
  2. list 1 / item 18 -
    3. -
-
-

The items below should be numbered starting with 19.

-
-
    -
  1. list 1 / item 19 -
    2. -
  2. list 1 / item 20 -
    3. -
-
-
-

-4.2.1. Styles -

-

1

-
    -
  1. 1 -
    2. -
  2. 2 -
    3. -
  3. -
    3 (check: 3) -
    -
    4. -
-

a

-
    -
  1. a -
    2. -
  2. b -
    3. -
  3. -
    c (check: c) -
    -
    4. -
-

A

-
    -
  1. A -
    2. -
  2. B -
    3. -
  3. -
    C (check: C) -
    -
    4. -
-

i

-
    -
  1. i -
    2. -
  2. ii -
    3. -
  3. -
    iii (check: iii) -
    -
    4. -
-

I

-
    -
  1. I -
    2. -
  2. II -
    3. -
  3. -
    III (check: III) -
    -
    4. -
-

REC%d

-
-
REC1
-
REC1 -
-
-
REC2
-
REC2 -
-
-
REC3
-
-
REC3 (check: REC3) -
-
-
-
-

REC%c with start=5

-
-
RECe
-
e -
-
-
RECf
-
f -
-
-
RECg
-
-
g (check: RECg) -
-
-
-
-

REC%i grouped

-
-
RECi
-
i -
-
-
-

REC%i grouped, continued

-
-
RECii
-
-
ii (check: RECii) -
-
-
-
-
-
-
-

-4.3. Unordered Lists -

-
    -
  • One -
    • -
  • Two 2 -
    • -
  • Three 3 -
    • -
-
-
-

-4.4. Unordered Lists (multi-paragraph / nested) -

-
    -
  • -

    The quick brown fox jumps over the lazy dog.

    -

    - The quick brown fox jumps over the lazy dog.

    -
    • -
  • -

    Two 2

    -
    • -
  • -

    Three 3

    -
    • -
  • -

    sub list

    - -
    • -
-
-
-

-4.5. Unordered Lists (empty=true) -

- -
-
-

-4.6. Referring to list items -

-

(default) see Section 4.1.

-

(counter) see Section 4.1.

-

(title) see listitem.

-

(default, TEXTCONTENT) see TEXTCONTENT (Section 4.1).

-

(counter, TEXTCONTENT) see TEXTCONTENT (4.1).

-

(title, TEXTCONTENT) see TEXTCONTENT (listitem).

-
-
-
-
-

-5. <blockquote> -

-
-

- Let's cite:

-
-
-
-
-

- "The quick brown fox jumps over the lazy dog" is an English-language pangram - a phrase that contains all of the letters of the alphabet. It is used to show fonts and to test typewriters and computer keyboards, and in other applications involving all of the letters in the English alphabet. Owing to its brevity and coherence, it has become widely known.

-
-
-
    -
  1. one -
    2. -
  2. two -
    3. -
-
-

- The parts above have anchors (Section 5, Paragraph 2.1 and Section 5, Paragraph 2.2), but this one does not.

-
-
-

without block content:

-
-
- "The quick brown fox jumps over the lazy dog" is an English-language pangram - a phrase that contains all of the letters of the alphabet. It is used to show fonts and to test typewriters and computer keyboards, and in other applications involving all of the letters in the English alphabet. Owing to its brevity and coherence, it has become widely known. -
-
-

with "quotedFrom":

-
-
- 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.— Abraham Lincoln -
-
-
-
-

-6. <aside> -

-
- -
-
-
-

-7. <sourcecode> -

-

Text before...

-
-
ABC
-
-

Text after...

-

Inside figure

-
-
DEF
-
-

ABNF

-
-
-foo = bar
-
-
-
-
-

-8. SVG -

-
-

-8.1. inline (with @alt attribute) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.2. inline (left) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.3. inline (centered) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.4. inline (right) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.5. included (type svg) -

-
-
- - (external file) - - - - -
-
-
- - (external file with internal ascii art) - - - - -
-
-
Figure 1: -References of [RFC7991] -
-
-

- This paragraph has the anchor 'Section 8.5, Paragraph 2' - which will be in conflict with an id attribute in the included SVG.

-
-
-
-
-

-9. <figure>/<name> -

-
-
-
ABC
-
-
Figure 2: -<figure>/<name> -
-
-
-

-10. Tables -

-
-

-10.1. Bare Table (unnamed, no anchor, with iref) -

- - - - - - - - - - - - - - - -
Table 1
Column 1Column 2
Value 1Value 2
-
-
-

-10.2. Bare Table (unnamed, with anchor, not referenced) -

-
- - - - - - - - - - - - - - -
Table 2
Column 1Column 2
Value 1Value 2
-
-
-
-

-10.3. Bare Table (unnamed, with anchor, referenced) -

-
- - - - - - - - - - - - - - -
Table 3
Column 1Column 2
Value 1Value 2
-
-

- See Table 3.

-
-
-

-10.4. Named Table -

- - - - - - - - - - - - - - -
-Table 4: -Table Name -
Column 1Column 2
Value 1Value 2
-
-
-

-10.5. Aligned Table 1 -

- - - - - - - - - - - - - - - - -
Table 5
Column 1Column 2Column 3
123
-
-
-

-10.6. Colspan 1 -

- - - - - - - - - - - - - - - -
Table 6
Column 1Column 2Column 3
12 and 3
-
-
-

-10.7. Rowspan 1 -

- - - - - - - - - - - - - - - - - - - - -
Table 7
Column 1Column 2Column 3
12 and 53
46
-
-
-

-10.8. References -

-
- - - - - - - - - - - - - - -
Table 8
Column 1Column 2
12
-
-
-
-

-10.9. Markup in Table Cells -

-
- - - - - - - - - - - - - - -
Table 9
Column 1Line 1
Line 2
The quick brown fox jumps over the lazy OPTIONAL dog. Table 9 https://en.wikipedia.org/wiki/The_quick_brown_fox_jumps_over_the_lazy_dog comment - -

- Paragraph 1

-

- Paragraph 2

-
-
Source code
-
-
    -
  1. Ordered List -
    2. -
-
    -
  • Unordered List -
    • -
-
-
Definition
-
List -
-
-
-
-
-
-
-

-10.10. Examples from existing RFCs -

-
-

-10.10.1. RFC 7541 -

-

- (<tfoot> added for testing purposes)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 10
symcode as bits
aligned to MSB 		code
as hex
aligned
to LSB		len
in
bits
- ( 0) - - |11111111|11000 - - 1ff8 - - [13] -
- ( 1) - - |11111111|11111111|1011000 - - 7fffd8 - - [23] -
- ( 2) - - |11111111|11111111|11111110|0010 - - fffffe2 - - [28] -
- ( 3) - - |11111111|11111111|11111110|0011 - - fffffe3 - - [28] -
- ( 4) - - |11111111|11111111|11111110|0100 - - fffffe4 - - [28] -
- ( 5) - - |11111111|11111111|11111110|0101 - - fffffe5 - - [28] -
- ( 6) - - |11111111|11111111|11111110|0110 - - fffffe6 - - [28] -
- ( 7) - - |11111111|11111111|11111110|0111 - - fffffe7 - - [28] -
- ( 8) - - |11111111|11111111|11111110|1000 - - fffffe8 - - [28] -
- ( 9) - - |11111111|11111111|11101010 - - ffffea - - [24] -
- ( 10) - - |11111111|11111111|11111111|111100 3 - - 3ffffffc - - [30] -
- ( 11) - - |11111111|11111111|11111110|1001 - - fffffe9 - - [28] -
- ( 12) - - |11111111|11111111|11111110|1010 - - fffffea - - [28] -
- ( 13) - - |11111111|11111111|11111111|111101 3 - - 3ffffffd - - [30] -
- ( 14) - - |11111111|11111111|11111110|1011 - - fffffeb - - [28] -
- ( 15) - - |11111111|11111111|11111110|1100 - - fffffec - - [28] -
- ( 16) - - |11111111|11111111|11111110|1101 - - fffffed - - [28] -
- ( 17) - - |11111111|11111111|11111110|1110 - - fffffee - - [28] -
- ( 18) - - |11111111|11111111|11111110|1111 - - fffffef - - [28] -
- ( 19) - - |11111111|11111111|11111111|0000 - - ffffff0 - - [28] -
- ( 20) - - |11111111|11111111|11111111|0001 - - ffffff1 - - [28] -
- ( 21) - - |11111111|11111111|11111111|0010 - - ffffff2 - - [28] -
- ( 22) - - |11111111|11111111|11111111|111110 3 - - 3ffffffe - - [30] -
- ( 23) - - |11111111|11111111|11111111|0011 - - ffffff3 - - [28] -
- ( 24) - - |11111111|11111111|11111111|0100 - - ffffff4 - - [28] -
- ( 25) - - |11111111|11111111|11111111|0101 - - ffffff5 - - [28] -
- ( 26) - - |11111111|11111111|11111111|0110 - - ffffff6 - - [28] -
- ( 27) - - |11111111|11111111|11111111|0111 - - ffffff7 - - [28] -
- ( 28) - - |11111111|11111111|11111111|1000 - - ffffff8 - - [28] -
- ( 29) - - |11111111|11111111|11111111|1001 - - ffffff9 - - [28] -
- ( 30) - - |11111111|11111111|11111111|1010 - - ffffffa - - [28] -
- ( 31) - - |11111111|11111111|11111111|1011 - - ffffffb - - [28] -
- ' ' ( 32) - - |010100 - - 14 - - [ 6] -
- '!' ( 33) - - |11111110|00 - - 3f8 - - [10] -
- '"' ( 34) - - |11111110|01 - - 3f9 - - [10] -
- '#' ( 35) - - |11111111|1010 - - ffa - - [12] -
- '$' ( 36) - - |11111111|11001 - - 1ff9 - - [13] -
- '%' ( 37) - - |010101 - - 15 - - [ 6] -
- '&' ( 38) - - |11111000 - - f8 - - [ 8] -
- ''' ( 39) - - |11111111|010 - - 7fa - - [11] -
- '(' ( 40) - - |11111110|10 - - 3fa - - [10] -
- ')' ( 41) - - |11111110|11 - - 3fb - - [10] -
- '*' ( 42) - - |11111001 - - f9 - - [ 8] -
- '+' ( 43) - - |11111111|011 - - 7fb - - [11] -
- ',' ( 44) - - |11111010 - - fa - - [ 8] -
- '-' ( 45) - - |010110 - - 16 - - [ 6] -
- '.' ( 46) - - |010111 - - 17 - - [ 6] -
- '/' ( 47) - - |011000 - - 18 - - [ 6] -
- '0' ( 48) - - |00000 - - 0 - - [ 5] -
- '1' ( 49) - - |00001 - - 1 - - [ 5] -
- '2' ( 50) - - |00010 - - 2 - - [ 5] -
- '3' ( 51) - - |011001 - - 19 - - [ 6] -
- '4' ( 52) - - |011010 - - 1a - - [ 6] -
- '5' ( 53) - - |011011 - - 1b - - [ 6] -
- '6' ( 54) - - |011100 - - 1c - - [ 6] -
- '7' ( 55) - - |011101 - - 1d - - [ 6] -
- '8' ( 56) - - |011110 - - 1e - - [ 6] -
- '9' ( 57) - - |011111 - - 1f - - [ 6] -
- ':' ( 58) - - |1011100 - - 5c - - [ 7] -
- ';' ( 59) - - |11111011 - - fb - - [ 8] -
- '<' ( 60) - - |11111111|1111100 - - 7ffc - - [15] -
- '=' ( 61) - - |100000 - - 20 - - [ 6] -
- '>' ( 62) - - |11111111|1011 - - ffb - - [12] -
- '?' ( 63) - - |11111111|00 - - 3fc - - [10] -
- '@' ( 64) - - |11111111|11010 - - 1ffa - - [13] -
- 'A' ( 65) - - |100001 - - 21 - - [ 6] -
- 'B' ( 66) - - |1011101 - - 5d - - [ 7] -
- 'C' ( 67) - - |1011110 - - 5e - - [ 7] -
- 'D' ( 68) - - |1011111 - - 5f - - [ 7] -
- 'E' ( 69) - - |1100000 - - 60 - - [ 7] -
- 'F' ( 70) - - |1100001 - - 61 - - [ 7] -
- 'G' ( 71) - - |1100010 - - 62 - - [ 7] -
- 'H' ( 72) - - |1100011 - - 63 - - [ 7] -
- 'I' ( 73) - - |1100100 - - 64 - - [ 7] -
- 'J' ( 74) - - |1100101 - - 65 - - [ 7] -
- 'K' ( 75) - - |1100110 - - 66 - - [ 7] -
- 'L' ( 76) - - |1100111 - - 67 - - [ 7] -
- 'M' ( 77) - - |1101000 - - 68 - - [ 7] -
- 'N' ( 78) - - |1101001 - - 69 - - [ 7] -
- 'O' ( 79) - - |1101010 - - 6a - - [ 7] -
- 'P' ( 80) - - |1101011 - - 6b - - [ 7] -
- 'Q' ( 81) - - |1101100 - - 6c - - [ 7] -
- 'R' ( 82) - - |1101101 - - 6d - - [ 7] -
- 'S' ( 83) - - |1101110 - - 6e - - [ 7] -
- 'T' ( 84) - - |1101111 - - 6f - - [ 7] -
- 'U' ( 85) - - |1110000 - - 70 - - [ 7] -
- 'V' ( 86) - - |1110001 - - 71 - - [ 7] -
- 'W' ( 87) - - |1110010 - - 72 - - [ 7] -
- 'X' ( 88) - - |11111100 - - fc - - [ 8] -
- 'Y' ( 89) - - |1110011 - - 73 - - [ 7] -
- 'Z' ( 90) - - |11111101 - - fd - - [ 8] -
- '[' ( 91) - - |11111111|11011 - - 1ffb - - [13] -
- '' ( 92) - - 11111111|11111110|000 - - 7fff0 - - 19] -
- ']' ( 93) - - |11111111|11100 - - 1ffc - - [13] -
- '^' ( 94) - - |11111111|111100 - - 3ffc - - [14] -
- '_' ( 95) - - |100010 - - 22 - - [ 6] -
- '`' ( 96) - - |11111111|1111101 - - 7ffd - - [15] -
- 'a' ( 97) - - |00011 - - 3 - - [ 5] -
- 'b' ( 98) - - |100011 - - 23 - - [ 6] -
- 'c' ( 99) - - |00100 - - 4 - - [ 5] -
- 'd' (100) - - |100100 - - 24 - - [ 6] -
- 'e' (101) - - |00101 - - 5 - - [ 5] -
- 'f' (102) - - |100101 - - 25 - - [ 6] -
- 'g' (103) - - |100110 - - 26 - - [ 6] -
- 'h' (104) - - |100111 - - 27 - - [ 6] -
- 'i' (105) - - |00110 - - 6 - - [ 5] -
- 'j' (106) - - |1110100 - - 74 - - [ 7] -
- 'k' (107) - - |1110101 - - 75 - - [ 7] -
- 'l' (108) - - |101000 - - 28 - - [ 6] -
- 'm' (109) - - |101001 - - 29 - - [ 6] -
- 'n' (110) - - |101010 - - 2a - - [ 6] -
- 'o' (111) - - |00111 - - 7 - - [ 5] -
- 'p' (112) - - |101011 - - 2b - - [ 6] -
- 'q' (113) - - |1110110 - - 76 - - [ 7] -
- 'r' (114) - - |101100 - - 2c - - [ 6] -
- 's' (115) - - |01000 - - 8 - - [ 5] -
- 't' (116) - - |01001 - - 9 - - [ 5] -
- 'u' (117) - - |101101 - - 2d - - [ 6] -
- 'v' (118) - - |1110111 - - 77 - - [ 7] -
- 'w' (119) - - |1111000 - - 78 - - [ 7] -
- 'x' (120) - - |1111001 - - 79 - - [ 7] -
- 'y' (121) - - |1111010 - - 7a - - [ 7] -
- 'z' (122) - - |1111011 - - 7b - - [ 7] -
- '{' (123) - - |11111111|1111110 - - 7ffe - - [15] -
- '|' (124) - - |11111111|100 - - 7fc - - [11] -
- '}' (125) - - |11111111|111101 - - 3ffd - - [14] -
- '~' (126) - - |11111111|11101 - - 1ffd - - [13] -
- (127) - - |11111111|11111111|11111111|1100 - - ffffffc - - [28] -
- (128) - - |11111111|11111110|0110 - - fffe6 - - [20] -
- (129) - - |11111111|11111111|010010 - - 3fffd2 - - [22] -
- (130) - - |11111111|11111110|0111 - - fffe7 - - [20] -
- (131) - - |11111111|11111110|1000 - - fffe8 - - [20] -
- (132) - - |11111111|11111111|010011 - - 3fffd3 - - [22] -
- (133) - - |11111111|11111111|010100 - - 3fffd4 - - [22] -
- (134) - - |11111111|11111111|010101 - - 3fffd5 - - [22] -
- (135) - - |11111111|11111111|1011001 - - 7fffd9 - - [23] -
- (136) - - |11111111|11111111|010110 - - 3fffd6 - - [22] -
- (137) - - |11111111|11111111|1011010 - - 7fffda - - [23] -
- (138) - - |11111111|11111111|1011011 - - 7fffdb - - [23] -
- (139) - - |11111111|11111111|1011100 - - 7fffdc - - [23] -
- (140) - - |11111111|11111111|1011101 - - 7fffdd - - [23] -
- (141) - - |11111111|11111111|1011110 - - 7fffde - - [23] -
- (142) - - |11111111|11111111|11101011 - - ffffeb - - [24] -
- (143) - - |11111111|11111111|1011111 - - 7fffdf - - [23] -
- (144) - - |11111111|11111111|11101100 - - ffffec - - [24] -
- (145) - - |11111111|11111111|11101101 - - ffffed - - [24] -
- (146) - - |11111111|11111111|010111 - - 3fffd7 - - [22] -
- (147) - - |11111111|11111111|1100000 - - 7fffe0 - - [23] -
- (148) - - |11111111|11111111|11101110 - - ffffee - - [24] -
- (149) - - |11111111|11111111|1100001 - - 7fffe1 - - [23] -
- (150) - - |11111111|11111111|1100010 - - 7fffe2 - - [23] -
- (151) - - |11111111|11111111|1100011 - - 7fffe3 - - [23] -
- (152) - - |11111111|11111111|1100100 - - 7fffe4 - - [23] -
- (153) - - |11111111|11111110|11100 - - 1fffdc - - [21] -
- (154) - - |11111111|11111111|011000 - - 3fffd8 - - [22] -
- (155) - - |11111111|11111111|1100101 - - 7fffe5 - - [23] -
- (156) - - |11111111|11111111|011001 - - 3fffd9 - - [22] -
- (157) - - |11111111|11111111|1100110 - - 7fffe6 - - [23] -
- (158) - - |11111111|11111111|1100111 - - 7fffe7 - - [23] -
- (159) - - |11111111|11111111|11101111 - - ffffef - - [24] -
- (160) - - |11111111|11111111|011010 - - 3fffda - - [22] -
- (161) - - |11111111|11111110|11101 - - 1fffdd - - [21] -
- (162) - - |11111111|11111110|1001 - - fffe9 - - [20] -
- (163) - - |11111111|11111111|011011 - - 3fffdb - - [22] -
- (164) - - |11111111|11111111|011100 - - 3fffdc - - [22] -
- (165) - - |11111111|11111111|1101000 - - 7fffe8 - - [23] -
- (166) - - |11111111|11111111|1101001 - - 7fffe9 - - [23] -
- (167) - - |11111111|11111110|11110 - - 1fffde - - [21] -
- (168) - - |11111111|11111111|1101010 - - 7fffea - - [23] -
- (169) - - |11111111|11111111|011101 - - 3fffdd - - [22] -
- (170) - - |11111111|11111111|011110 - - 3fffde - - [22] -
- (171) - - |11111111|11111111|11110000 - - fffff0 - - [24] -
- (172) - - |11111111|11111110|11111 - - 1fffdf - - [21] -
- (173) - - |11111111|11111111|011111 - - 3fffdf - - [22] -
- (174) - - |11111111|11111111|1101011 - - 7fffeb - - [23] -
- (175) - - |11111111|11111111|1101100 - - 7fffec - - [23] -
- (176) - - |11111111|11111111|00000 - - 1fffe0 - - [21] -
- (177) - - |11111111|11111111|00001 - - 1fffe1 - - [21] -
- (178) - - |11111111|11111111|100000 - - 3fffe0 - - [22] -
- (179) - - |11111111|11111111|00010 - - 1fffe2 - - [21] -
- (180) - - |11111111|11111111|1101101 - - 7fffed - - [23] -
- (181) - - |11111111|11111111|100001 - - 3fffe1 - - [22] -
- (182) - - |11111111|11111111|1101110 - - 7fffee - - [23] -
- (183) - - |11111111|11111111|1101111 - - 7fffef - - [23] -
- (184) - - |11111111|11111110|1010 - - fffea - - [20] -
- (185) - - |11111111|11111111|100010 - - 3fffe2 - - [22] -
- (186) - - |11111111|11111111|100011 - - 3fffe3 - - [22] -
- (187) - - |11111111|11111111|100100 - - 3fffe4 - - [22] -
- (188) - - |11111111|11111111|1110000 - - 7ffff0 - - [23] -
- (189) - - |11111111|11111111|100101 - - 3fffe5 - - [22] -
- (190) - - |11111111|11111111|100110 - - 3fffe6 - - [22] -
- (191) - - |11111111|11111111|1110001 - - 7ffff1 - - [23] -
- (192) - - |11111111|11111111|11111000|00 - - 3ffffe0 - - [26] -
- (193) - - |11111111|11111111|11111000|01 - - 3ffffe1 - - [26] -
- (194) - - |11111111|11111110|1011 - - fffeb - - [20] -
- (195) - - |11111111|11111110|001 - - 7fff1 - - [19] -
- (196) - - |11111111|11111111|100111 - - 3fffe7 - - [22] -
- (197) - - |11111111|11111111|1110010 - - 7ffff2 - - [23] -
- (198) - - |11111111|11111111|101000 - - 3fffe8 - - [22] -
- (199) - - |11111111|11111111|11110110|0 - - 1ffffec - - [25] -
- (200) - - |11111111|11111111|11111000|10 - - 3ffffe2 - - [26] -
- (201) - - |11111111|11111111|11111000|11 - - 3ffffe3 - - [26] -
- (202) - - |11111111|11111111|11111001|00 - - 3ffffe4 - - [26] -
- (203) - - |11111111|11111111|11111011|110 - - 7ffffde - - [27] -
- (204) - - |11111111|11111111|11111011|111 - - 7ffffdf - - [27] -
- (205) - - |11111111|11111111|11111001|01 - - 3ffffe5 - - [26] -
- (206) - - |11111111|11111111|11110001 - - fffff1 - - [24] -
- (207) - - |11111111|11111111|11110110|1 - - 1ffffed - - [25] -
- (208) - - |11111111|11111110|010 - - 7fff2 - - [19] -
- (209) - - |11111111|11111111|00011 - - 1fffe3 - - [21] -
- (210) - - |11111111|11111111|11111001|10 - - 3ffffe6 - - [26] -
- (211) - - |11111111|11111111|11111100|000 - - 7ffffe0 - - [27] -
- (212) - - |11111111|11111111|11111100|001 - - 7ffffe1 - - [27] -
- (213) - - |11111111|11111111|11111001|11 - - 3ffffe7 - - [26] -
- (214) - - |11111111|11111111|11111100|010 - - 7ffffe2 - - [27] -
- (215) - - |11111111|11111111|11110010 - - fffff2 - - [24] -
- (216) - - |11111111|11111111|00100 - - 1fffe4 - - [21] -
- (217) - - |11111111|11111111|00101 - - 1fffe5 - - [21] -
- (218) - - |11111111|11111111|11111010|00 - - 3ffffe8 - - [26] -
- (219) - - |11111111|11111111|11111010|01 - - 3ffffe9 - - [26] -
- (220) - - |11111111|11111111|11111111|1101 - - ffffffd - - [28] -
- (221) - - |11111111|11111111|11111100|011 - - 7ffffe3 - - [27] -
- (222) - - |11111111|11111111|11111100|100 - - 7ffffe4 - - [27] -
- (223) - - |11111111|11111111|11111100|101 - - 7ffffe5 - - [27] -
- (224) - - |11111111|11111110|1100 - - fffec - - [20] -
- (225) - - |11111111|11111111|11110011 - - fffff3 - - [24] -
- (226) - - |11111111|11111110|1101 - - fffed - - [20] -
- (227) - - |11111111|11111111|00110 - - 1fffe6 - - [21] -
- (228) - - |11111111|11111111|101001 - - 3fffe9 - - [22] -
- (229) - - |11111111|11111111|00111 - - 1fffe7 - - [21] -
- (230) - - |11111111|11111111|01000 - - 1fffe8 - - [21] -
- (231) - - |11111111|11111111|1110011 - - 7ffff3 - - [23] -
- (232) - - |11111111|11111111|101010 - - 3fffea - - [22] -
- (233) - - |11111111|11111111|101011 - - 3fffeb - - [22] -
- (234) - - |11111111|11111111|11110111|0 - - 1ffffee - - [25] -
- (235) - - |11111111|11111111|11110111|1 - - 1ffffef - - [25] -
- (236) - - |11111111|11111111|11110100 - - fffff4 - - [24] -
- (237) - - |11111111|11111111|11110101 - - fffff5 - - [24] -
- (238) - - |11111111|11111111|11111010|10 - - 3ffffea - - [26] -
- (239) - - |11111111|11111111|1110100 - - 7ffff4 - - [23] -
- (240) - - |11111111|11111111|11111010|11 - - 3ffffeb - - [26] -
- (241) - - |11111111|11111111|11111100|110 - - 7ffffe6 - - [27] -
- (242) - - |11111111|11111111|11111011|00 - - 3ffffec - - [26] -
- (243) - - |11111111|11111111|11111011|01 - - 3ffffed - - [26] -
- (244) - - |11111111|11111111|11111100|111 - - 7ffffe7 - - [27] -
- (245) - - |11111111|11111111|11111101|000 - - 7ffffe8 - - [27] -
- (246) - - |11111111|11111111|11111101|001 - - 7ffffe9 - - [27] -
- (247) - - |11111111|11111111|11111101|010 - - 7ffffea - - [27] -
- (248) - - |11111111|11111111|11111101|011 - - 7ffffeb - - [27] -
- (249) - - |11111111|11111111|11111111|1110 - - ffffffe - - [28] -
- (250) - - |11111111|11111111|11111101|100 - - 7ffffec - - [27] -
- (251) - - |11111111|11111111|11111101|101 - - 7ffffed - - [27] -
- (252) - - |11111111|11111111|11111101|110 - - 7ffffee - - [27] -
- (253) - - |11111111|11111111|11111101|111 - - 7ffffef - - [27] -
- (254) - - |11111111|11111111|11111110|000 - - 7fffff0 - - [27] -
- (255) - - |11111111|11111111|11111011|10 - - 3ffffee - - [26] -
- EOS (256) - - |11111111|11111111|11111111|111111 - - 3fffffff - - [30] -
symcode as bits
aligned to MSB 		code
as hex
aligned
to LSB		len
in
bits
-
-
-
-
-

-11. Section References -

-
-

-11.1. By Section Number -

-

- "of": - See Section 1 of [RFC7991].

-

- "comma": - See [RFC7991], Section 2.2.

-

- "parens": - See [RFC7991] (Appendix A).

-

- "bare": - See B.

-

- (default): - See Section 1 of [RFC7991].

-

- With text content: - See Section 2 of the wonderful Section 2 of RFC 7991 [RFC7991].

-
-
-

-11.2. By Relative URI -

-

- "of": - See Section 1 of [SVG11].

-

- "comma": - See [SVG11], Section 1.

-

- "parens": - See [SVG11] (Section 1).

-

- "bare": - See 1.

-

- (default): - See Section 1 of [SVG11].

-
-
-

-11.3. To "References" -

-

- See Section 12, where the title is "Some References".

-

- See references below (Section 12).

-
-
-

-11.4. To Unnumbered Section -

-

- See Appendix "Contributors", where the title is "Contributors".

-

- See contributors below (Appendix "Contributors").

-
-
-
-
-

-12. Some References -

-
-
[0REFTEST]
-
-Reschke, J., "Reference Test", additional prose goes here, . Due to a <displayreference> element, this should be listed as "[0REFTEST]". -
-
-
[DUP]
-
-Reschke, J., "Reference Duplicate Test", .
-
-
[DUP]
-
-Reschke, J., "Another Reference Duplicate Test", . Oops. -
-
-
[GOST3410]
-
-"Information technology. Cryptographic data security. Signature and verification processes of [electronic] digital signature.", Gosudarstvennyi Standard of Russian Federation, Правительственная комиссия России по стандартам (Government Committee of Russia for Standards), GOST R 34.10-2001, . (In Russian) -
-
-
[RFC7991]
-
-Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, , <https://www.rfc-editor.org/rfc/rfc7991>.
-
-
[RFC7996]
-
-Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
-
-
[STD78]
-
-
- Schoenwaelder, J., "Simple Network Management Protocol (SNMP) Context EngineID Discovery", STD 78, RFC 5343, .
-
- Harrington, D. and J. Schoenwaelder, "Transport Subsystem for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5590, .
-
- Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, .
-
- Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, .
-<https://www.rfc-editor.org/info/std78> -
-
-
[STPETER]
-
-ᏚᎢᎵᎬᎢᎬᏒ Inc. (STPETER Inc.), "ᏚᎢᎵᎬᎢᎬᏒ's document" ("STPETER's document"). A document where the author element specifies just an organization, and both title and organization name have an ASCII equivalent. -
-
-
[SVG11]
-
-Ferraiolo, J., 藤沢, 淳 (Fujisawa, J.), and D. Jackson, "Scalable Vector Graphics (SVG) 1.1 Specification", W3C Recommendation REC-SVG11-20030114, , <http://www.w3.org/TR/2003/REC-SVG11-20030114/>. - Latest version available at - http://www.w3.org/TR/SVG11/. - -
-
-
[UNQUOTED]
-
-Reschke, J., Reference Test, . (The title above should not be quoted) -
-
-
[XML]
-
-Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, , <http://www.w3.org/TR/2008/REC-xml-20081126/>. - Latest version available at - http://www.w3.org/TR/xml. - -
-
-
-
-
-
-

-Appendix A. Change Log -

-

This section is to be removed before publishing as an RFC.

-

- Foo bar.

-

- - - -

-
-
-

-Appendix B. Another Change Log only containing Subsections -

-

This section is to be removed before publishing as an RFC.

-
-

-B.1. Test -

-

Foo

-
-
-
-

-Appendix C. Test removeInRFC duplication -

-

This section is to be removed before publishing as an RFC.

-

The above note should NOT appear twice.

-
-
-

-Appendix D. Test removeInRFC duplication again -

-

This section is to be removed before publishing as an RFC.

-

Since it is not the first paragraph in the source XML,

-

This section is to be removed before publishing as an RFC.

-

should appear twice this time.

-
-
-

-Appendix E. Test removeInRFC without name -

-

This section is to be removed before publishing as an RFC.

-
-

-E.1. section as first child -

-

The warning should still appear.

-
-
-
-
-

-Contributors -

-

- Foo bar.

-
-
-
-

-Index -

-
-

- $ - % - [ - \ - B - M - R - T

-
- -
-
-
-

-Authors' Addresses -

-
-
Julian Reschke (editor)
-
line 1
line 2
line 3
-
-
-
-
Pythagoras of Samos
-
Geometry Labs
-
-831 03 Pythagoreio -
-
Greece
-
-
Additional contact information:
-
-
Πυθαγόρας ὁ Σάμιος
-
Εργαστήριο γεωμετρία
-
-831 03 Πυθαγόρειο -
-
Ελλάδα
-
-
-
-
Armin Bergström
-
-
-
- - - diff --git a/tests/valid/draft-v3-features.v3.py37.html b/tests/valid/draft-v3-features.v3.py37.html deleted file mode 100644 index 23a2f81b4..000000000 --- a/tests/valid/draft-v3-features.v3.py37.html +++ /dev/null @@ -1,5295 +0,0 @@ - - - - - - -xml2rfc V3 Feature Tests - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-Draftxml2rfc V3 Feature TestsApril 2017
Reschke, et al.Expires October 17, 2017[Page]
-
-
-
-
Workgroup:
-
Network Working Group
-
Internet-Draft:
-
draft-v3-features
-
Published:
-
- -
-
Intended Status:
-
Experimental
-
Expires:
-
-
Authors:
-
-
-
J. Reschke, Ed. -
-
-
-
-Πυθαγόρας ὁ Σάμιος (P. O. Samos)
-
-Εργαστήριο γεωμετρία (Geometry Labs)
-
-
-
A. Bergström
-
-
-
-
-

xml2rfc V3 Feature Tests

-
-

Abstract

-

- This document tests features introduced in xml2rfc v3 vocabulary.

-
-
-

-Note to Readers -

-

This note is to be removed before publishing as an RFC.

-

- Something important about this document.

-
-
-

This note is to be removed before publishing as an RFC.

-

- Something else important, this time with no <name>.

-
-
-

This note is to be removed before publishing as an RFC.

-

The warning in this note should not be doubled.

-
-
-

-Another Note -

-

This note is to be removed before publishing as an RFC.

-

The warning in this note should not be doubled either.

-
-
-

-Yet Another Note -

-

This note is to be removed before publishing as an RFC.

-

The removeInRFC warning is only ever the first paragraph, so if a paragraph like this:

-

This note is to be removed before publishing as an RFC.

-

appears but is not the first paragraph, the warning should be added again.

-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at http://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on October 17, 2017.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-

-1. Text Styles -

- -
-

-1.1. em/strong -

-

- This is emphasized. This is strong. - This is both. - So is this.

-
-
-

-1.2. tt -

-

- This is monospaced. Standard 78: [STD78].

-
-
-

-1.3. bcp14 -

-

- This is a BCP14 MUST.

-
-
-

-1.4. sup/sub -

-

- This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is subscript. - This is superscript. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text. - This is regular text.

-
-
-
-

-2. Section Titles -

- - - - -
-
-

-2.4. Test: Comment -

-

- cref - Text after comment

-

More text after comment

-
-
-
-
-

-3. Renaming References -

- -

- Test: [0REFTEST].

-
-
-
-

-4. Lists -

-
-

-4.1. Definition Lists -

-

newline=default/spacing=default

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=true/spacing=default

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=false/spacing=default

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=default/spacing=compact

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=false/spacing=compact

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

newline=true/spacing=compact

-
-
Term1
-
Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. -
-
-
Term2
-
Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. -
-
-
-

markup

-
-
-
Term1
-
-
Description1. Description1. Description1. Description1. -
-
-
-

multi-paragraph

-
-
Term1
-
-

Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1.

-

Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2. Description2.

-
-
-
-

nested list

-
-
Term1
-
-

Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1. Description1.

-
-
Term1b
-
Description 1b. -
-
-
-
-
-
Term2
-
-
-
Term2b
-
Description 2b. -
-
-
-
-
-
-
-
-

-4.2. Ordered Lists -

-
    -
  1. -
    One -
    -
    2. -
  2. Two 2 -
    3. -
  3. Three 3 -
    4. -
-

- List item 1 is "One".

-
    -
  1. -
    -

    The quick brown fox jumps over the lazy dog.

    -

    The quick brown fox jumps over the lazy dog.

    -
    -
    2. -
-

- List item 4 is the list above.

-
-
    -
  1. list 1 / item 1 -
    2. -
  2. list 1 / item 2 -
    3. -
-
-

The items below should continue ordering from above.

-
-
    -
  1. list 1 / item 3 -
    2. -
  2. list 1 / item 4 -
    3. -
-
-

The items below should be numbered starting with 17.

-
-
    -
  1. list 1 / item 17 -
    2. -
  2. list 1 / item 18 -
    3. -
-
-

The items below should be numbered starting with 19.

-
-
    -
  1. list 1 / item 19 -
    2. -
  2. list 1 / item 20 -
    3. -
-
-
-

-4.2.1. Styles -

-

1

-
    -
  1. 1 -
    2. -
  2. 2 -
    3. -
  3. -
    3 (check: 3) -
    -
    4. -
-

a

-
    -
  1. a -
    2. -
  2. b -
    3. -
  3. -
    c (check: c) -
    -
    4. -
-

A

-
    -
  1. A -
    2. -
  2. B -
    3. -
  3. -
    C (check: C) -
    -
    4. -
-

i

-
    -
  1. i -
    2. -
  2. ii -
    3. -
  3. -
    iii (check: iii) -
    -
    4. -
-

I

-
    -
  1. I -
    2. -
  2. II -
    3. -
  3. -
    III (check: III) -
    -
    4. -
-

REC%d

-
-
REC1
-
REC1 -
-
-
REC2
-
REC2 -
-
-
REC3
-
-
REC3 (check: REC3) -
-
-
-
-

REC%c with start=5

-
-
RECe
-
e -
-
-
RECf
-
f -
-
-
RECg
-
-
g (check: RECg) -
-
-
-
-

REC%i grouped

-
-
RECi
-
i -
-
-
-

REC%i grouped, continued

-
-
RECii
-
-
ii (check: RECii) -
-
-
-
-
-
-
-

-4.3. Unordered Lists -

-
    -
  • One -
    • -
  • Two 2 -
    • -
  • Three 3 -
    • -
-
-
-

-4.4. Unordered Lists (multi-paragraph / nested) -

-
    -
  • -

    The quick brown fox jumps over the lazy dog.

    -

    - The quick brown fox jumps over the lazy dog.

    -
    • -
  • -

    Two 2

    -
    • -
  • -

    Three 3

    -
    • -
  • -

    sub list

    - -
    • -
-
-
-

-4.5. Unordered Lists (empty=true) -

- -
-
-

-4.6. Referring to list items -

-

(default) see Section 4.1.

-

(counter) see Section 4.1.

-

(title) see listitem.

-

(default, TEXTCONTENT) see TEXTCONTENT (Section 4.1).

-

(counter, TEXTCONTENT) see TEXTCONTENT (4.1).

-

(title, TEXTCONTENT) see TEXTCONTENT (listitem).

-
-
-
-
-

-5. <blockquote> -

-
-

- Let's cite:

-
-
-
-
-

- "The quick brown fox jumps over the lazy dog" is an English-language pangram - a phrase that contains all of the letters of the alphabet. It is used to show fonts and to test typewriters and computer keyboards, and in other applications involving all of the letters in the English alphabet. Owing to its brevity and coherence, it has become widely known.

-
-
-
    -
  1. one -
    2. -
  2. two -
    3. -
-
-

- The parts above have anchors (Section 5, Paragraph 2.1 and Section 5, Paragraph 2.2), but this one does not.

-
-
-

without block content:

-
-
- "The quick brown fox jumps over the lazy dog" is an English-language pangram - a phrase that contains all of the letters of the alphabet. It is used to show fonts and to test typewriters and computer keyboards, and in other applications involving all of the letters in the English alphabet. Owing to its brevity and coherence, it has become widely known. -
-
-

with "quotedFrom":

-
-
- 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.— Abraham Lincoln -
-
-
-
-

-6. <aside> -

-
- -
-
-
-

-7. <sourcecode> -

-

Text before...

-
-
ABC
-
-

Text after...

-

Inside figure

-
-
DEF
-
-

ABNF

-
-
-foo = bar
-
-
-
-
-

-8. SVG -

-
-

-8.1. inline (with @alt attribute) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.2. inline (left) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.3. inline (centered) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.4. inline (right) -

-

Text before...

-
- - - - - -
-

Text after...

-
-
-

-8.5. included (type svg) -

-
-
- - (external file) - - - - -
-
-
- - (external file with internal ascii art) - - - - -
-
-
Figure 1: -References of [RFC7991] -
-
-

- This paragraph has the anchor 'Section 8.5, Paragraph 2' - which will be in conflict with an id attribute in the included SVG.

-
-
-
-
-

-9. <figure>/<name> -

-
-
-
ABC
-
-
Figure 2: -<figure>/<name> -
-
-
-

-10. Tables -

-
-

-10.1. Bare Table (unnamed, no anchor, with iref) -

- - - - - - - - - - - - - - - -
Table 1
Column 1Column 2
Value 1Value 2
-
-
-

-10.2. Bare Table (unnamed, with anchor, not referenced) -

-
- - - - - - - - - - - - - - -
Table 2
Column 1Column 2
Value 1Value 2
-
-
-
-

-10.3. Bare Table (unnamed, with anchor, referenced) -

-
- - - - - - - - - - - - - - -
Table 3
Column 1Column 2
Value 1Value 2
-
-

- See Table 3.

-
-
-

-10.4. Named Table -

- - - - - - - - - - - - - - -
-Table 4: -Table Name -
Column 1Column 2
Value 1Value 2
-
-
-

-10.5. Aligned Table 1 -

- - - - - - - - - - - - - - - - -
Table 5
Column 1Column 2Column 3
123
-
-
-

-10.6. Colspan 1 -

- - - - - - - - - - - - - - - -
Table 6
Column 1Column 2Column 3
12 and 3
-
-
-

-10.7. Rowspan 1 -

- - - - - - - - - - - - - - - - - - - - -
Table 7
Column 1Column 2Column 3
12 and 53
46
-
-
-

-10.8. References -

-
- - - - - - - - - - - - - - -
Table 8
Column 1Column 2
12
-
-
-
-

-10.9. Markup in Table Cells -

-
- - - - - - - - - - - - - - -
Table 9
Column 1Line 1
Line 2
The quick brown fox jumps over the lazy OPTIONAL dog. Table 9 https://en.wikipedia.org/wiki/The_quick_brown_fox_jumps_over_the_lazy_dog comment - -

- Paragraph 1

-

- Paragraph 2

-
-
Source code
-
-
    -
  1. Ordered List -
    2. -
-
    -
  • Unordered List -
    • -
-
-
Definition
-
List -
-
-
-
-
-
-
-

-10.10. Examples from existing RFCs -

-
-

-10.10.1. RFC 7541 -

-

- (<tfoot> added for testing purposes)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 10
symcode as bits
aligned to MSB 		code
as hex
aligned
to LSB		len
in
bits
- ( 0) - - |11111111|11000 - - 1ff8 - - [13] -
- ( 1) - - |11111111|11111111|1011000 - - 7fffd8 - - [23] -
- ( 2) - - |11111111|11111111|11111110|0010 - - fffffe2 - - [28] -
- ( 3) - - |11111111|11111111|11111110|0011 - - fffffe3 - - [28] -
- ( 4) - - |11111111|11111111|11111110|0100 - - fffffe4 - - [28] -
- ( 5) - - |11111111|11111111|11111110|0101 - - fffffe5 - - [28] -
- ( 6) - - |11111111|11111111|11111110|0110 - - fffffe6 - - [28] -
- ( 7) - - |11111111|11111111|11111110|0111 - - fffffe7 - - [28] -
- ( 8) - - |11111111|11111111|11111110|1000 - - fffffe8 - - [28] -
- ( 9) - - |11111111|11111111|11101010 - - ffffea - - [24] -
- ( 10) - - |11111111|11111111|11111111|111100 3 - - 3ffffffc - - [30] -
- ( 11) - - |11111111|11111111|11111110|1001 - - fffffe9 - - [28] -
- ( 12) - - |11111111|11111111|11111110|1010 - - fffffea - - [28] -
- ( 13) - - |11111111|11111111|11111111|111101 3 - - 3ffffffd - - [30] -
- ( 14) - - |11111111|11111111|11111110|1011 - - fffffeb - - [28] -
- ( 15) - - |11111111|11111111|11111110|1100 - - fffffec - - [28] -
- ( 16) - - |11111111|11111111|11111110|1101 - - fffffed - - [28] -
- ( 17) - - |11111111|11111111|11111110|1110 - - fffffee - - [28] -
- ( 18) - - |11111111|11111111|11111110|1111 - - fffffef - - [28] -
- ( 19) - - |11111111|11111111|11111111|0000 - - ffffff0 - - [28] -
- ( 20) - - |11111111|11111111|11111111|0001 - - ffffff1 - - [28] -
- ( 21) - - |11111111|11111111|11111111|0010 - - ffffff2 - - [28] -
- ( 22) - - |11111111|11111111|11111111|111110 3 - - 3ffffffe - - [30] -
- ( 23) - - |11111111|11111111|11111111|0011 - - ffffff3 - - [28] -
- ( 24) - - |11111111|11111111|11111111|0100 - - ffffff4 - - [28] -
- ( 25) - - |11111111|11111111|11111111|0101 - - ffffff5 - - [28] -
- ( 26) - - |11111111|11111111|11111111|0110 - - ffffff6 - - [28] -
- ( 27) - - |11111111|11111111|11111111|0111 - - ffffff7 - - [28] -
- ( 28) - - |11111111|11111111|11111111|1000 - - ffffff8 - - [28] -
- ( 29) - - |11111111|11111111|11111111|1001 - - ffffff9 - - [28] -
- ( 30) - - |11111111|11111111|11111111|1010 - - ffffffa - - [28] -
- ( 31) - - |11111111|11111111|11111111|1011 - - ffffffb - - [28] -
- ' ' ( 32) - - |010100 - - 14 - - [ 6] -
- '!' ( 33) - - |11111110|00 - - 3f8 - - [10] -
- '"' ( 34) - - |11111110|01 - - 3f9 - - [10] -
- '#' ( 35) - - |11111111|1010 - - ffa - - [12] -
- '$' ( 36) - - |11111111|11001 - - 1ff9 - - [13] -
- '%' ( 37) - - |010101 - - 15 - - [ 6] -
- '&' ( 38) - - |11111000 - - f8 - - [ 8] -
- ''' ( 39) - - |11111111|010 - - 7fa - - [11] -
- '(' ( 40) - - |11111110|10 - - 3fa - - [10] -
- ')' ( 41) - - |11111110|11 - - 3fb - - [10] -
- '*' ( 42) - - |11111001 - - f9 - - [ 8] -
- '+' ( 43) - - |11111111|011 - - 7fb - - [11] -
- ',' ( 44) - - |11111010 - - fa - - [ 8] -
- '-' ( 45) - - |010110 - - 16 - - [ 6] -
- '.' ( 46) - - |010111 - - 17 - - [ 6] -
- '/' ( 47) - - |011000 - - 18 - - [ 6] -
- '0' ( 48) - - |00000 - - 0 - - [ 5] -
- '1' ( 49) - - |00001 - - 1 - - [ 5] -
- '2' ( 50) - - |00010 - - 2 - - [ 5] -
- '3' ( 51) - - |011001 - - 19 - - [ 6] -
- '4' ( 52) - - |011010 - - 1a - - [ 6] -
- '5' ( 53) - - |011011 - - 1b - - [ 6] -
- '6' ( 54) - - |011100 - - 1c - - [ 6] -
- '7' ( 55) - - |011101 - - 1d - - [ 6] -
- '8' ( 56) - - |011110 - - 1e - - [ 6] -
- '9' ( 57) - - |011111 - - 1f - - [ 6] -
- ':' ( 58) - - |1011100 - - 5c - - [ 7] -
- ';' ( 59) - - |11111011 - - fb - - [ 8] -
- '<' ( 60) - - |11111111|1111100 - - 7ffc - - [15] -
- '=' ( 61) - - |100000 - - 20 - - [ 6] -
- '>' ( 62) - - |11111111|1011 - - ffb - - [12] -
- '?' ( 63) - - |11111111|00 - - 3fc - - [10] -
- '@' ( 64) - - |11111111|11010 - - 1ffa - - [13] -
- 'A' ( 65) - - |100001 - - 21 - - [ 6] -
- 'B' ( 66) - - |1011101 - - 5d - - [ 7] -
- 'C' ( 67) - - |1011110 - - 5e - - [ 7] -
- 'D' ( 68) - - |1011111 - - 5f - - [ 7] -
- 'E' ( 69) - - |1100000 - - 60 - - [ 7] -
- 'F' ( 70) - - |1100001 - - 61 - - [ 7] -
- 'G' ( 71) - - |1100010 - - 62 - - [ 7] -
- 'H' ( 72) - - |1100011 - - 63 - - [ 7] -
- 'I' ( 73) - - |1100100 - - 64 - - [ 7] -
- 'J' ( 74) - - |1100101 - - 65 - - [ 7] -
- 'K' ( 75) - - |1100110 - - 66 - - [ 7] -
- 'L' ( 76) - - |1100111 - - 67 - - [ 7] -
- 'M' ( 77) - - |1101000 - - 68 - - [ 7] -
- 'N' ( 78) - - |1101001 - - 69 - - [ 7] -
- 'O' ( 79) - - |1101010 - - 6a - - [ 7] -
- 'P' ( 80) - - |1101011 - - 6b - - [ 7] -
- 'Q' ( 81) - - |1101100 - - 6c - - [ 7] -
- 'R' ( 82) - - |1101101 - - 6d - - [ 7] -
- 'S' ( 83) - - |1101110 - - 6e - - [ 7] -
- 'T' ( 84) - - |1101111 - - 6f - - [ 7] -
- 'U' ( 85) - - |1110000 - - 70 - - [ 7] -
- 'V' ( 86) - - |1110001 - - 71 - - [ 7] -
- 'W' ( 87) - - |1110010 - - 72 - - [ 7] -
- 'X' ( 88) - - |11111100 - - fc - - [ 8] -
- 'Y' ( 89) - - |1110011 - - 73 - - [ 7] -
- 'Z' ( 90) - - |11111101 - - fd - - [ 8] -
- '[' ( 91) - - |11111111|11011 - - 1ffb - - [13] -
- '' ( 92) - - 11111111|11111110|000 - - 7fff0 - - 19] -
- ']' ( 93) - - |11111111|11100 - - 1ffc - - [13] -
- '^' ( 94) - - |11111111|111100 - - 3ffc - - [14] -
- '_' ( 95) - - |100010 - - 22 - - [ 6] -
- '`' ( 96) - - |11111111|1111101 - - 7ffd - - [15] -
- 'a' ( 97) - - |00011 - - 3 - - [ 5] -
- 'b' ( 98) - - |100011 - - 23 - - [ 6] -
- 'c' ( 99) - - |00100 - - 4 - - [ 5] -
- 'd' (100) - - |100100 - - 24 - - [ 6] -
- 'e' (101) - - |00101 - - 5 - - [ 5] -
- 'f' (102) - - |100101 - - 25 - - [ 6] -
- 'g' (103) - - |100110 - - 26 - - [ 6] -
- 'h' (104) - - |100111 - - 27 - - [ 6] -
- 'i' (105) - - |00110 - - 6 - - [ 5] -
- 'j' (106) - - |1110100 - - 74 - - [ 7] -
- 'k' (107) - - |1110101 - - 75 - - [ 7] -
- 'l' (108) - - |101000 - - 28 - - [ 6] -
- 'm' (109) - - |101001 - - 29 - - [ 6] -
- 'n' (110) - - |101010 - - 2a - - [ 6] -
- 'o' (111) - - |00111 - - 7 - - [ 5] -
- 'p' (112) - - |101011 - - 2b - - [ 6] -
- 'q' (113) - - |1110110 - - 76 - - [ 7] -
- 'r' (114) - - |101100 - - 2c - - [ 6] -
- 's' (115) - - |01000 - - 8 - - [ 5] -
- 't' (116) - - |01001 - - 9 - - [ 5] -
- 'u' (117) - - |101101 - - 2d - - [ 6] -
- 'v' (118) - - |1110111 - - 77 - - [ 7] -
- 'w' (119) - - |1111000 - - 78 - - [ 7] -
- 'x' (120) - - |1111001 - - 79 - - [ 7] -
- 'y' (121) - - |1111010 - - 7a - - [ 7] -
- 'z' (122) - - |1111011 - - 7b - - [ 7] -
- '{' (123) - - |11111111|1111110 - - 7ffe - - [15] -
- '|' (124) - - |11111111|100 - - 7fc - - [11] -
- '}' (125) - - |11111111|111101 - - 3ffd - - [14] -
- '~' (126) - - |11111111|11101 - - 1ffd - - [13] -
- (127) - - |11111111|11111111|11111111|1100 - - ffffffc - - [28] -
- (128) - - |11111111|11111110|0110 - - fffe6 - - [20] -
- (129) - - |11111111|11111111|010010 - - 3fffd2 - - [22] -
- (130) - - |11111111|11111110|0111 - - fffe7 - - [20] -
- (131) - - |11111111|11111110|1000 - - fffe8 - - [20] -
- (132) - - |11111111|11111111|010011 - - 3fffd3 - - [22] -
- (133) - - |11111111|11111111|010100 - - 3fffd4 - - [22] -
- (134) - - |11111111|11111111|010101 - - 3fffd5 - - [22] -
- (135) - - |11111111|11111111|1011001 - - 7fffd9 - - [23] -
- (136) - - |11111111|11111111|010110 - - 3fffd6 - - [22] -
- (137) - - |11111111|11111111|1011010 - - 7fffda - - [23] -
- (138) - - |11111111|11111111|1011011 - - 7fffdb - - [23] -
- (139) - - |11111111|11111111|1011100 - - 7fffdc - - [23] -
- (140) - - |11111111|11111111|1011101 - - 7fffdd - - [23] -
- (141) - - |11111111|11111111|1011110 - - 7fffde - - [23] -
- (142) - - |11111111|11111111|11101011 - - ffffeb - - [24] -
- (143) - - |11111111|11111111|1011111 - - 7fffdf - - [23] -
- (144) - - |11111111|11111111|11101100 - - ffffec - - [24] -
- (145) - - |11111111|11111111|11101101 - - ffffed - - [24] -
- (146) - - |11111111|11111111|010111 - - 3fffd7 - - [22] -
- (147) - - |11111111|11111111|1100000 - - 7fffe0 - - [23] -
- (148) - - |11111111|11111111|11101110 - - ffffee - - [24] -
- (149) - - |11111111|11111111|1100001 - - 7fffe1 - - [23] -
- (150) - - |11111111|11111111|1100010 - - 7fffe2 - - [23] -
- (151) - - |11111111|11111111|1100011 - - 7fffe3 - - [23] -
- (152) - - |11111111|11111111|1100100 - - 7fffe4 - - [23] -
- (153) - - |11111111|11111110|11100 - - 1fffdc - - [21] -
- (154) - - |11111111|11111111|011000 - - 3fffd8 - - [22] -
- (155) - - |11111111|11111111|1100101 - - 7fffe5 - - [23] -
- (156) - - |11111111|11111111|011001 - - 3fffd9 - - [22] -
- (157) - - |11111111|11111111|1100110 - - 7fffe6 - - [23] -
- (158) - - |11111111|11111111|1100111 - - 7fffe7 - - [23] -
- (159) - - |11111111|11111111|11101111 - - ffffef - - [24] -
- (160) - - |11111111|11111111|011010 - - 3fffda - - [22] -
- (161) - - |11111111|11111110|11101 - - 1fffdd - - [21] -
- (162) - - |11111111|11111110|1001 - - fffe9 - - [20] -
- (163) - - |11111111|11111111|011011 - - 3fffdb - - [22] -
- (164) - - |11111111|11111111|011100 - - 3fffdc - - [22] -
- (165) - - |11111111|11111111|1101000 - - 7fffe8 - - [23] -
- (166) - - |11111111|11111111|1101001 - - 7fffe9 - - [23] -
- (167) - - |11111111|11111110|11110 - - 1fffde - - [21] -
- (168) - - |11111111|11111111|1101010 - - 7fffea - - [23] -
- (169) - - |11111111|11111111|011101 - - 3fffdd - - [22] -
- (170) - - |11111111|11111111|011110 - - 3fffde - - [22] -
- (171) - - |11111111|11111111|11110000 - - fffff0 - - [24] -
- (172) - - |11111111|11111110|11111 - - 1fffdf - - [21] -
- (173) - - |11111111|11111111|011111 - - 3fffdf - - [22] -
- (174) - - |11111111|11111111|1101011 - - 7fffeb - - [23] -
- (175) - - |11111111|11111111|1101100 - - 7fffec - - [23] -
- (176) - - |11111111|11111111|00000 - - 1fffe0 - - [21] -
- (177) - - |11111111|11111111|00001 - - 1fffe1 - - [21] -
- (178) - - |11111111|11111111|100000 - - 3fffe0 - - [22] -
- (179) - - |11111111|11111111|00010 - - 1fffe2 - - [21] -
- (180) - - |11111111|11111111|1101101 - - 7fffed - - [23] -
- (181) - - |11111111|11111111|100001 - - 3fffe1 - - [22] -
- (182) - - |11111111|11111111|1101110 - - 7fffee - - [23] -
- (183) - - |11111111|11111111|1101111 - - 7fffef - - [23] -
- (184) - - |11111111|11111110|1010 - - fffea - - [20] -
- (185) - - |11111111|11111111|100010 - - 3fffe2 - - [22] -
- (186) - - |11111111|11111111|100011 - - 3fffe3 - - [22] -
- (187) - - |11111111|11111111|100100 - - 3fffe4 - - [22] -
- (188) - - |11111111|11111111|1110000 - - 7ffff0 - - [23] -
- (189) - - |11111111|11111111|100101 - - 3fffe5 - - [22] -
- (190) - - |11111111|11111111|100110 - - 3fffe6 - - [22] -
- (191) - - |11111111|11111111|1110001 - - 7ffff1 - - [23] -
- (192) - - |11111111|11111111|11111000|00 - - 3ffffe0 - - [26] -
- (193) - - |11111111|11111111|11111000|01 - - 3ffffe1 - - [26] -
- (194) - - |11111111|11111110|1011 - - fffeb - - [20] -
- (195) - - |11111111|11111110|001 - - 7fff1 - - [19] -
- (196) - - |11111111|11111111|100111 - - 3fffe7 - - [22] -
- (197) - - |11111111|11111111|1110010 - - 7ffff2 - - [23] -
- (198) - - |11111111|11111111|101000 - - 3fffe8 - - [22] -
- (199) - - |11111111|11111111|11110110|0 - - 1ffffec - - [25] -
- (200) - - |11111111|11111111|11111000|10 - - 3ffffe2 - - [26] -
- (201) - - |11111111|11111111|11111000|11 - - 3ffffe3 - - [26] -
- (202) - - |11111111|11111111|11111001|00 - - 3ffffe4 - - [26] -
- (203) - - |11111111|11111111|11111011|110 - - 7ffffde - - [27] -
- (204) - - |11111111|11111111|11111011|111 - - 7ffffdf - - [27] -
- (205) - - |11111111|11111111|11111001|01 - - 3ffffe5 - - [26] -
- (206) - - |11111111|11111111|11110001 - - fffff1 - - [24] -
- (207) - - |11111111|11111111|11110110|1 - - 1ffffed - - [25] -
- (208) - - |11111111|11111110|010 - - 7fff2 - - [19] -
- (209) - - |11111111|11111111|00011 - - 1fffe3 - - [21] -
- (210) - - |11111111|11111111|11111001|10 - - 3ffffe6 - - [26] -
- (211) - - |11111111|11111111|11111100|000 - - 7ffffe0 - - [27] -
- (212) - - |11111111|11111111|11111100|001 - - 7ffffe1 - - [27] -
- (213) - - |11111111|11111111|11111001|11 - - 3ffffe7 - - [26] -
- (214) - - |11111111|11111111|11111100|010 - - 7ffffe2 - - [27] -
- (215) - - |11111111|11111111|11110010 - - fffff2 - - [24] -
- (216) - - |11111111|11111111|00100 - - 1fffe4 - - [21] -
- (217) - - |11111111|11111111|00101 - - 1fffe5 - - [21] -
- (218) - - |11111111|11111111|11111010|00 - - 3ffffe8 - - [26] -
- (219) - - |11111111|11111111|11111010|01 - - 3ffffe9 - - [26] -
- (220) - - |11111111|11111111|11111111|1101 - - ffffffd - - [28] -
- (221) - - |11111111|11111111|11111100|011 - - 7ffffe3 - - [27] -
- (222) - - |11111111|11111111|11111100|100 - - 7ffffe4 - - [27] -
- (223) - - |11111111|11111111|11111100|101 - - 7ffffe5 - - [27] -
- (224) - - |11111111|11111110|1100 - - fffec - - [20] -
- (225) - - |11111111|11111111|11110011 - - fffff3 - - [24] -
- (226) - - |11111111|11111110|1101 - - fffed - - [20] -
- (227) - - |11111111|11111111|00110 - - 1fffe6 - - [21] -
- (228) - - |11111111|11111111|101001 - - 3fffe9 - - [22] -
- (229) - - |11111111|11111111|00111 - - 1fffe7 - - [21] -
- (230) - - |11111111|11111111|01000 - - 1fffe8 - - [21] -
- (231) - - |11111111|11111111|1110011 - - 7ffff3 - - [23] -
- (232) - - |11111111|11111111|101010 - - 3fffea - - [22] -
- (233) - - |11111111|11111111|101011 - - 3fffeb - - [22] -
- (234) - - |11111111|11111111|11110111|0 - - 1ffffee - - [25] -
- (235) - - |11111111|11111111|11110111|1 - - 1ffffef - - [25] -
- (236) - - |11111111|11111111|11110100 - - fffff4 - - [24] -
- (237) - - |11111111|11111111|11110101 - - fffff5 - - [24] -
- (238) - - |11111111|11111111|11111010|10 - - 3ffffea - - [26] -
- (239) - - |11111111|11111111|1110100 - - 7ffff4 - - [23] -
- (240) - - |11111111|11111111|11111010|11 - - 3ffffeb - - [26] -
- (241) - - |11111111|11111111|11111100|110 - - 7ffffe6 - - [27] -
- (242) - - |11111111|11111111|11111011|00 - - 3ffffec - - [26] -
- (243) - - |11111111|11111111|11111011|01 - - 3ffffed - - [26] -
- (244) - - |11111111|11111111|11111100|111 - - 7ffffe7 - - [27] -
- (245) - - |11111111|11111111|11111101|000 - - 7ffffe8 - - [27] -
- (246) - - |11111111|11111111|11111101|001 - - 7ffffe9 - - [27] -
- (247) - - |11111111|11111111|11111101|010 - - 7ffffea - - [27] -
- (248) - - |11111111|11111111|11111101|011 - - 7ffffeb - - [27] -
- (249) - - |11111111|11111111|11111111|1110 - - ffffffe - - [28] -
- (250) - - |11111111|11111111|11111101|100 - - 7ffffec - - [27] -
- (251) - - |11111111|11111111|11111101|101 - - 7ffffed - - [27] -
- (252) - - |11111111|11111111|11111101|110 - - 7ffffee - - [27] -
- (253) - - |11111111|11111111|11111101|111 - - 7ffffef - - [27] -
- (254) - - |11111111|11111111|11111110|000 - - 7fffff0 - - [27] -
- (255) - - |11111111|11111111|11111011|10 - - 3ffffee - - [26] -
- EOS (256) - - |11111111|11111111|11111111|111111 - - 3fffffff - - [30] -
symcode as bits
aligned to MSB 		code
as hex
aligned
to LSB		len
in
bits
-
-
-
-
-

-11. Section References -

-
-

-11.1. By Section Number -

-

- "of": - See Section 1 of [RFC7991].

-

- "comma": - See [RFC7991], Section 2.2.

-

- "parens": - See [RFC7991] (Appendix A).

-

- "bare": - See B.

-

- (default): - See Section 1 of [RFC7991].

-

- With text content: - See Section 2 of the wonderful Section 2 of RFC 7991 [RFC7991].

-
-
-

-11.2. By Relative URI -

-

- "of": - See Section 1 of [SVG11].

-

- "comma": - See [SVG11], Section 1.

-

- "parens": - See [SVG11] (Section 1).

-

- "bare": - See 1.

-

- (default): - See Section 1 of [SVG11].

-
-
-

-11.3. To "References" -

-

- See Section 12, where the title is "Some References".

-

- See references below (Section 12).

-
-
-

-11.4. To Unnumbered Section -

-

- See Appendix "Contributors", where the title is "Contributors".

-

- See contributors below (Appendix "Contributors").

-
-
-
-
-

-12. Some References -

-
-
[0REFTEST]
-
-Reschke, J., "Reference Test", additional prose goes here, . Due to a <displayreference> element, this should be listed as "[0REFTEST]". -
-
-
[DUP]
-
-Reschke, J., "Reference Duplicate Test", .
-
-
[DUP]
-
-Reschke, J., "Another Reference Duplicate Test", . Oops. -
-
-
[GOST3410]
-
-"Information technology. Cryptographic data security. Signature and verification processes of [electronic] digital signature.", Gosudarstvennyi Standard of Russian Federation, Правительственная комиссия России по стандартам (Government Committee of Russia for Standards), GOST R 34.10-2001, . (In Russian) -
-
-
[RFC7991]
-
-Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", RFC 7991, , <https://www.rfc-editor.org/rfc/rfc7991>.
-
-
[RFC7996]
-
-Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, , <https://www.rfc-editor.org/info/rfc7996>.
-
-
[STD78]
-
-
- Schoenwaelder, J., "Simple Network Management Protocol (SNMP) Context EngineID Discovery", STD 78, RFC 5343, .
-
- Harrington, D. and J. Schoenwaelder, "Transport Subsystem for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5590, .
-
- Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, .
-
- Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, .
-<https://www.rfc-editor.org/info/std78> -
-
-
[STPETER]
-
-ᏚᎢᎵᎬᎢᎬᏒ Inc. (STPETER Inc.), "ᏚᎢᎵᎬᎢᎬᏒ's document" ("STPETER's document"). A document where the author element specifies just an organization, and both title and organization name have an ASCII equivalent. -
-
-
[SVG11]
-
-Ferraiolo, J., 藤沢, 淳 (Fujisawa, J.), and D. Jackson, "Scalable Vector Graphics (SVG) 1.1 Specification", W3C Recommendation REC-SVG11-20030114, , <http://www.w3.org/TR/2003/REC-SVG11-20030114/>. - Latest version available at - http://www.w3.org/TR/SVG11/. - -
-
-
[UNQUOTED]
-
-Reschke, J., Reference Test, . (The title above should not be quoted) -
-
-
[XML]
-
-Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, , <http://www.w3.org/TR/2008/REC-xml-20081126/>. - Latest version available at - http://www.w3.org/TR/xml. - -
-
-
-
-
-
-

-Appendix A. Change Log -

-

This section is to be removed before publishing as an RFC.

-

- Foo bar.

-

- - - -

-
-
-

-Appendix B. Another Change Log only containing Subsections -

-

This section is to be removed before publishing as an RFC.

-
-

-B.1. Test -

-

Foo

-
-
-
-

-Appendix C. Test removeInRFC duplication -

-

This section is to be removed before publishing as an RFC.

-

The above note should NOT appear twice.

-
-
-

-Appendix D. Test removeInRFC duplication again -

-

This section is to be removed before publishing as an RFC.

-

Since it is not the first paragraph in the source XML,

-

This section is to be removed before publishing as an RFC.

-

should appear twice this time.

-
-
-

-Appendix E. Test removeInRFC without name -

-

This section is to be removed before publishing as an RFC.

-
-

-E.1. section as first child -

-

The warning should still appear.

-
-
-
-
-

-Contributors -

-

- Foo bar.

-
-
-
-

-Index -

-
-

- $ - % - [ - \ - B - M - R - T

-
- -
-
-
-

-Authors' Addresses -

-
-
Julian Reschke (editor)
-
line 1
line 2
line 3
-
-
-
-
Pythagoras of Samos
-
Geometry Labs
-
-831 03 Pythagoreio -
-
Greece
-
-
Additional contact information:
-
-
Πυθαγόρας ὁ Σάμιος
-
Εργαστήριο γεωμετρία
-
-831 03 Πυθαγόρειο -
-
Ελλάδα
-
-
-
-
Armin Bergström
-
-
-
- - - diff --git a/tests/valid/elements.v3.py37.html b/tests/valid/elements.v3.html similarity index 99% rename from tests/valid/elements.v3.py37.html rename to tests/valid/elements.v3.html index 9a0dccc14..a706e49f3 100644 --- a/tests/valid/elements.v3.py37.html +++ b/tests/valid/elements.v3.html @@ -15,7 +15,7 @@ - + diff --git a/tests/valid/elements.v3.py36.html b/tests/valid/elements.v3.py36.html deleted file mode 100644 index 9a0dccc14..000000000 --- a/tests/valid/elements.v3.py36.html +++ /dev/null @@ -1,1932 +0,0 @@ - - - - - - -Xml2rfc Vocabulary V3 Elements Combined Test File - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-DraftXml2rfc Vocabulary V3 ElementsJuly 2018
Author, et al.Expires January 13, 2019[Page]
-
-
-
-
Workgroup:
-
Network Working Group
-
Obsoletes:
-
-1234, 5678, 9012, 3456, 7890 (if approved)
-
Published:
-
- -
-
Intended Status:
-
Informational
-
Expires:
-
-
Authors:
-
-
-
A. Author
-
-
-
-רוני אבן (R. Even)
-
-וואווי (Huawei)
-
-
-
-田中花子 様 (H. Tanaka)
-
-
-
N. Org
-
-
-
B. Aventure
-
Université de Liège
-
-
-
International Association for Cryptologic Research
-
-
-
A. Lindgren
-
-
-
-
-

Xml2rfc Vocabulary V3 Elements
Combined Test File

-
-
-

Abstract

-

This is the abstract.

-
-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at https://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on January 13, 2019.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-

-1. RFC 2119 key words -

- -

- The key words "MUST", "MUST NOT", - "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", - "RECOMMENDED", "NOT RECOMMENDED", "MAY", - and "OPTIONAL" in this document are to be interpreted as described in - BCP 14 [RFC2119] [RFC8174] when, and only when, they - appear in all capitals, as shown here.

-
-
-

-2. Citations -

-

- - This section contains a bunch of citations, in order to test citation formats and also - - in order to refer to each of the entries in - the Section 18.

-

Citations of References:

- -

Citations of References with explicit text:

- -

Citations of multiple Sections in References, using sectionFormat="bare":

- -

Citations of multiple Sections in References, using text and sectionFormat="bare":

- -

References to Abstract, with explicit text:

- -

References to Abstract:

- -

References to Sections, with explicit text:

- -

References to Sections:

- -

References to Appendix:

- -

References to Comments:

- -

This comment is to be cited.

-

- These references should be present: - [RFC5652] - [RFC2634] - [RFC5035] - [RFC2045] - [RFC2046] - [RFC2047] - [RFC2049] - [RFC4289] - [RFC6838]

-
-
-
-

-3. Unordered list with sub-elements -

-
    -
  • -
    - Unordered list, first bullet. [MUST], [MUST NOT] -
    -
    • -
  • - Unordered list, second bullet. Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici. -
    • -
  • -

    - Unordered list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

    -
    -
    -        Unordered list, third bullet, second element:
-        +-------------------------------------------+
-        |                                           |
-        |                  Artwork                  |
-        |                                           |
-        +-------------------------------------------+
-
    -
    -
    -
    Unordered list, third bullet, third element: Definition list, element dt.
    -
    -
    Element dd. Indent 16. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
    -
    -
    -
    -
    Unordered list, third bullet, third element: Definition list, element dt.
    -
    -
    Element dd. Indent 16. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
    -
    -
    -
    -
    -
    -Unordered list, third bullet, fourth element:
-                    Figure
-                        Figure
-                           Figure
-
    -
    -
    Figure 1: -Some figure name -
    -
    -
    REQ1:
    -
    -
    Unordered list, third bullet, fifth element: Ordered list, element li. Text only. Indent="8" -
    -
    -
    -
    REQ2:
    -
    -

    - Unordered list, third bullet, fifth element: Ordered list, element t. Indent="8". Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

    -
    -
    REQ2:1
    -
    Sublist with '%p' parent counter element in the list counter, item one -
    -
    -
    REQ2:2
    -
    Item two. -
    -
    -
    REQ2:3
    -
    Item three. -
    -
    -
    -
    -
    -
    -
    -
    <CODE BEGINS> file "sample.py"
-
-                  # Unordered list, third bullet, sixth element
-                  A = 1; # Non-ASCII comment: €
-
-<CODE ENDS>
    -
    -
      -
    • Unordered list, third bullet, seventh element: Unordered list, element li. Text only. -
      • -
    • -

      - Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem.

      -
      • -
    -

    - Unordered list, third bullet, eight and ninth element: Text and SVG Artwork:

    -
    -
    - - - - - -
    -
    -
    • -
  • -

    Artset include with <xi:include>

    -
    - - - - - -
    -
    • -
-
-
-
-

-4. Ordered list with sub-elements -

-
    -
  1. - Ordered list, first bullet. Indent="6". -
    2. -
  2. - Ordered list, second bullet. Indent="6". Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici. -
    3. -
-
    -
  1. -

    - Ordered list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

    -
    -
    -        Ordered list, third bullet, second element:
-        +-------------------------------------------+
-        |                                           |
-        |                  Artwork                  |
-        |                                           |
-        +-------------------------------------------+
-
    -
    -
    -
    Ordered list, third bullet, third element: Definition list, element dt.
    -
    -
    Element dd. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
    -
    -
    -
    -
    -
    -Ordered list, third bullet, fourth element:
-                    Figure
-                        Figure
-                           Figure
-
    -
    -
    Figure 2: -Some figure name -
    -
      -
    1. Ordered list, third bullet, fifth element: Ordered list, element li. Text only. -
      2. -
    2. -

      - Ordered list, third bullet, fifth element: Ordered list, element t. Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

      -
      3. -
    -
    -
    -                  # Ordered list, third bullet, sixth element
-                  A = 1;
-
    -
    -
      -
    • Ordered list, third bullet, seventh element: Unordered list, element li. Text only. -
      • -
    • -

      - Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. - See Appendix A, Section 3.1 of [I-D.levkowetz-xml2rfc-v3-implementation-notes] - and also Appendix A.1 of Key Words Case Ambiguity [RFC8174] / - Key Words Case Ambiguity [RFC8174], Appendix A.1 / - Key Words Case Ambiguity [RFC8174] (Appendix A.1).

      -
      • -
    -
    2. -
  2. -
    -
    4.1
    -
    Sublist with '%p' parent counter element in the list counter, item one -
    -
    -
    4.2
    -
    Item two. -
    -
    -
    4.3
    -
    Item three. -
    -
    -
    -
    3. -
-
-
-

-5. Definition list with sub-elements -

-
-
-
Term 1
-
-
-
- Definition list, first bullet. -
-
-
-
Term 2
-
- Definition list, second bullet. Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici. -
-
-
Term 3
-
-

- Definition list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

-
-
-        Definition list, third bullet, second element:
-        +-------------------------------------------+
-        |                                           |
-        |                  Artwork                  |
-        |                                           |
-        +-------------------------------------------+
-
-
-
-
Definition list, third bullet, third element: Definition list, element dt.
-
-
Element dd. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
-
-
-
-
-
-Definition list, third bullet, fourth element:
-                    Figure
-                        Figure
-                           Figure
-
-
-
Figure 3: -Some figure name -
-
    -
  1. Definition list, third bullet, fifth element: Ordered list, element li. Text only. -
    2. -
  2. -

    - Definition list, third bullet, fifth element: Ordered list, element t. Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

    -
      -
    • UL within OL within DL, item one -
      • -
    • UL within OL within DL, item two -
      • -
    -
      -
    • UL within OL within DL, empty="true"; item one -
      • -
    • UL within OL within DL, empty="true"; item two -
      • -
    -
      -
    • UL within OL within DL, bare="true"; item one -
      • -
    • UL within OL within DL, bare="true"; item two -
      • -
    -
    3. -
-
-
-                  # Definition list, third bullet, sixth element
-                  A = 1;
-
-
-
    -
  • Definition list, third bullet, seventh element: Unordered list, element li. Text only. -
    • -
  • -

    - Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem.

    -
    • -
-

Definition list, third bullet, eight element, t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

-

Definition list, third bullet, ninth element, t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

-
-
-
-
-
-

-6. Table -

-
-
-      +-----+-----+-----------+
-      |     |     |           |
-      +-----+-----+-----+-----+
-      |     |     |     |     |
-      +=====+=====+=====+=====+
-      |     |     |     |     |
-      +-----+-----+-----+-----+
-      |     |                 |
-      +     +-----+-----+-----+
-      |     |     |     |     |
-      +     +     +-----+-----+
-      |     |     |           |
-      +-----+     +-----+-----+
-      |     |     |     |     |
-      +=====+=====+=====+=====+
-      |     |     |     |     |
-      +-----+-----+-----+-----+
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -Header, footer, colspan and rowspan
Default alignment -
ABC D
1234
Long text in a single cellb1c1d1
Long text in a 3-cell column.
Quid igitur est? Inquit; audire enim cupio, quid non probes eius, a quo dissentias.		Long text in a 3-cell row.
Quid enim est a Cyrenaicisque melius liberiusque defenditur, tamen eius modi tempora incidunt, ut labore et dolore disputandum putant.
Another 3-cell column.c3d3
x
a5c5d5
aabbccdd
- - - - - - - - - - - - -
-Table 2: -Aligned left -
OneTwo
AlphaBeta
- - - - - - - - - - - - -
-Table 3: -Aligned center -
OneTwo
AlphaBeta
- - - - - - - - - - - - -
-Table 4: -Aligned right -
OneTwo
AlphaBeta
-

- A really tight table where left padding cannot be applied as it would throw - the left-alignment of the text off.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 5
MethodDefinitionptypepropertyValueStatusVersion
dnswlRFC 8904dnszone -

DNSWL publicly accessible query root domain

-		active1
dnswlRFC 8904policyip -

type A response received (or a quoted, - comma-separated list thereof)

-		active1
dnswlRFC 8904policytxttype TXT query responseactive1
dnswlRFC 8904dnssecone of "yes" for DNSSEC authenticated data, "no" for - not signed, or "na" for not applicableactive1
-
-
-

-7. Unicode Literals -

-
-

-7.1. Single Characters -

-
-
Expansion "num":
-
-

Example XML:

-
-
Use the character
-  <u format="num">Δ</u>.
-
-

expands to:

-

- Use the character U+0394.

-
-
-
Expansion "name":
-
-

Example XML:

-
-
Use the character <u format="name-num">Δ</u>.
-
-

expands to:

-

- Use the character GREEK CAPITAL LETTER DELTA (U+0394).

-
-
-
Expansion "num-lit":
-
-

Example XML:

-
-
Use the character <u format="num-lit">Δ</u>.
-
-

expands to:

-

- Use the character U+0394 ("Δ").

-
-
-
Expansion "num-name":
-
-

Example XML:

-
-
Use the <u format="{num} character ({name})">Δ</u>.
-
-

expands to:

-

- Use the U+0394 character (GREEK CAPITAL LETTER DELTA).

-
    -
  • Tab: U+0009 (U+0009) -
    • -
  • Char(128): U+0080 (U+0080) -
    • -
-
-
-
Expansion "num-lit-name":
-
-

Example XML:

-
-
Use the character <u format="num-lit-name">Δ</u>.
-
-

expands to:

-

- Use the character U+0394 ("Δ", GREEK CAPITAL LETTER DELTA).

-
-
-
Expansion "num-name-lit":
-
-

Example XML:

-
-
Use the character <u format="num-name-lit">Δ</u>.
-
-

expands to:

-

- Use the character U+0394 (GREEK CAPITAL LETTER DELTA, "Δ").

-
-
-
Expansion "ascii-lit-num":
-
-

Example XML:

-
-
Use the character
-  <u ascii="Delta" format="ascii-lit-num" ascii="Delta">Δ</u>.
-
-

expands to:

-

- Use the character "Delta" ("Δ", U+0394).

-
-
-
Expansion "lit-name-num":
-
-

Example XML:

-
-
Use the <u format="{lit} character ({name}, {num})">Δ</u>.
-
-

expands to:

-

- Use the "Δ" character (GREEK CAPITAL LETTER DELTA, U+0394)

-
-
-
Expansion "lit-num":
-
-

Example XML:

-
-
Use the <u format="{lit} character ({num})">Δ</u>.
-
-

expands to:

-

- Use the "Δ" character (U+0394).

-
-
-
-
-
-

-7.2. Character Strings -

-
-
Expansion "num-lit":
-
-

Example XML:

-
-
For example, the characters
-  <u ascii="STPETER" format="num-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ") from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "num-name":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="num-name">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "num-lit-name":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="num-lit-name">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ", CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "num-name-lit":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="num-name-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV, "ᏚᎢᎵᎬᎢᎬᏒ") from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "ascii-lit-num":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="ascii-lit-num">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters "STPETER" ("ᏚᎢᎵᎬᎢᎬᏒ", U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "lit-name-num":
-
-

Example XML:

-
-
-For example, the
-  <u ascii="STPETER" format="{lit}
-     characters ({name}, {num})">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the "ᏚᎢᎵᎬᎢᎬᏒ" characters (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV, U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "lit-num":
-
-

Example XML:

-
-
-For example, the
-  <u ascii="STPETER" format="{lit} characters ({num})">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the "ᏚᎢᎵᎬᎢᎬᏒ" characters (U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
-
-
-
-

-8. Irregular date specifications -

-

- - You can now use date ranges like "2002-2003" (See [DATE-RANGE]) and - fuzzy dates such as "Spring 1814" (See [FUZZY-DATE]) by omitting - the year/month/day attributes of <date>, and instead provide text content.

-
-
-
-

-9. Aside, Word Joiner, and Break -

- -

- - Regular: Nam ut tortor ut dui fermentum viverra. Quisque sed aliquam enim. Pellentesque - vestibulum risus sed ligula eleifend commodo. Sed vel lacus id mauris dapibus - lobortis. Suspendisse quis pellentesque nisl, vitae pulvinar felis. Ut at hendrerit - odio. Morbi non sem non ligula posuere ultrices.

- - - - -
-
Definition list with aside in <dd>
-
- -
-
-
-
-
-
-

-10. Section title test 1 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-

-11. Section level h2 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-

-11.1. Section level h3 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-

-11.1.1. Section level h4 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-11.1.1.1. Section level h5 -
-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-11.1.1.1.1. Section level h6 -
-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-
-
-
-
-

-12. Eref brackets -

- -
-
-

-13. Sourcecode indentation -

-

Source code as-is:

-
-
-while true ; do
-    case "$1" in
-        -h| --help)     usage; exit;;   # Show this help
-        -v| --verbose)  VERBOSE=1;;     # Be more talkative
-        -V| --version)  version; exit;; # Show program version
-        --)             shift; break;;
-    esac
-    shift
-done
-
-
-

Source code within a figure:

-
-
-
-for opt, value in opts:
-    if   opt in ["-h", "--help"]: # Output this help, then exit
-        print __doc__ % locals()
-        sys.exit(1)
-    elif opt in ["-v", "--version"]: # Output version information
-        print program, version
-        sys.exit(0)
-    elif opt in ["-V", "--verbose"]: # Output version information
-        opt_verbose = True
-
-
-
Figure 4: -Sourcecode within figure -
-
-
-

-14. Tables inside lists -

-
-
Step 1:
-
-
-

(This example is excerpted from pre-RFC8677) Indent="9"

-

- At nSFF1, the following nNLM is assumed:

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 6: -nNLM at nSFF1 -
SPISINext Hop(s)Transport Encapsulation (TE)
10255192.0.2.1VXLAN-gpe
10254198.51.100.10GRE
10253www.example.comHTTP
10252www.example2.comHTTP
40251198.51.100.15GRE
5020001:23:45:67:89:ab Ethernet
15212Null (end of path)None
-
-
-
-
-
-
-
-
This is an arbitrary term:
-
-
-

And this is some text with a table.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 7
Head 1Head 2 - Head 3 -
Cell A1Cell A2 - Cell A3 -
Cell B1Cell B2 - Cell B3 -
Cell C1Cell C2 - Cell C3 -
Head 10Head 20 - Head 30 -
Cell A10Cell A20 - Cell A30 -
Cell B10Empty Cell:
-
-
-
-
-
-

-15. Wide artwork -

-
-
-0        1         2         3         4         5         6         7
-123456789012345678901234567890123456789012345678901234567890123456789012
-
-
-
-
-

-16. Sup and sub -

-
-
Sup
-
Text with superscript2 -
-
-
Sup
-
Simple superscript expressions: x-1 y+3.0 z3.2a -
-
-
Sup
-
More simple superscript expressions: x1.2 yn0 -
-
-
Sup
-
Parenthetical expressions in superscript: x(n+1) y-(k-1) z(_c) -
-
-
Sup
-
Compound superscript expressions: xx+y y_c za.0 -
-
-
Sup
-
One word superscript or two words superscript -
-
-
Sup
-
Text with sub inside superscriptx2 -
-
-
Sub
-
Text with subscript2 -
-
-
Sub
-
Simple subscript expressions: x-1 y+3.0 z3.2a -
-
-
Sub
-
More simple subscript expressions: x1.2 yn0 -
-
-
Sub
-
Parenthetical expressions in subscript: x(n+1) y-(k-1) z(_c) -
-
-
Sub
-
Compound subscript expressions: xx+y y_c za.0 -
-
-
Sub
-
One word subscript or two words subscript -
-
-
Sub
-
Text with super inside subscriptx2 -
-
-
-
-
-

-Unnumbered section -

-

- - Regular paragraph. Lorem ipsum dolor sit amet, consectetur - adipiscing elit. Ut pharetra neque vulputate dolor elementum - sodales. Maecenas maximus elit sit amet pretium facilisis. Vivamus - pulvinar, quam nec eleifend ultricies, nisi elit rhoncus risus, in - commodo mi leo in lorem.

-

- - Indented paragraph. Indent="5". Aenean ornare elit at urna molestie - fermentum. Donec erat purus, vestibulum in venenatis tempor, - feugiat nec neque. Fusce luctus sem neque, id venenatis turpis - vulputate nec. Nulla tincidunt pretium ex fringilla posuere. Cras - quis massa neque.

-
    -
  1. Indent="5". Lorem ipsum dolor sit amet, consectetur - adipiscing elit. Ut pharetra neque vulputate dolor elementum - sodales. -
    2. -
  2. Item 2 -
    3. -
- -
-
-
-

-References -

-
-

-Normative References -

-
-
[RFC2119]
-
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
-
-
[RFC7997]
-
-Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", IAB, RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
-
-
[RFC8174]
-
-Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
-
-
-
-
-

-Informative References -

-
-
-

-CMS References -

-
-
[I-D.levkowetz-xml2rfc-v3-implementation-notes]
-
-Levkowetz, H., "Implementation notes for RFC7991,", Work in Progress, Internet-Draft, draft-levkowetz-xml2rfc-v3-implementation-notes-13, , <https://datatracker.ietf.org/doc/html/draft-levkowetz-xml2rfc-v3-implementation-notes-13>.
-
-
[RFC5083]
-
-Housley, R., "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type", RFC 5083, DOI 10.17487/RFC5083, , <https://www.rfc-editor.org/info/rfc5083>.
-
-
[RFC5652]
-
-Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, DOI 10.17487/RFC5652, , <https://www.rfc-editor.org/info/rfc5652>.
-
-
-
-
-
-
-

-ESS References -

-
-
[RFC2634]
-
-Hoffman, P., Ed., "Enhanced Security Services for S/MIME", RFC 2634, DOI 10.17487/RFC2634, , <https://www.rfc-editor.org/info/rfc2634>.
-
-
[RFC5035]
-
-Schaad, J., "Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility", RFC 5035, DOI 10.17487/RFC5035, , <https://www.rfc-editor.org/info/rfc5035>.
-
-
-
-
-
-
-

-MIME-SPEC References -

-
-
[RFC2045]
-
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, , <https://www.rfc-editor.org/info/rfc2045>.
-
-
[RFC2046]
-
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, , <https://www.rfc-editor.org/info/rfc2046>.
-
-
[RFC2047]
-
-Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, DOI 10.17487/RFC2047, , <https://www.rfc-editor.org/info/rfc2047>.
-
-
[RFC2049]
-
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049, DOI 10.17487/RFC2049, , <https://www.rfc-editor.org/info/rfc2049>.
-
-
[RFC4289]
-
-Freed, N. and J. Klensin, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 4289, DOI 10.17487/RFC4289, , <https://www.rfc-editor.org/info/rfc4289>.
-
-
[RFC6838]
-
-Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, , <https://www.rfc-editor.org/info/rfc6838>.
-
-
-
-
-
-

-Other References -

-
-
[AUTHORS]
-
-Πυθαγόρας ὁ Σάμιος (Samos, P. O.), Doe, J., Bergström, A., and J. Doe, "Lots of authors", RFC 7539, DOI 10.17487/RFC7539, , <https://www.rfc-editor.org/rfc/rfc7539>.
-
-
[DATE-RANGE]
-
-Moe, J., "Document with date range", 2002-2003.
-
-
[FUZZY-DATE]
-
-Mae, J., "Document with fuzzy date", Second quarter 2010.
-
-
[GEDICHTE]
-
-Heine, H., "Dreiunddreißig Gedichte", .
-
-
[NO-DATE]
-
-Mae, N., "Document — with no date", Advances in Cryptology - AACC Edition pp. 235-265.
-
-
[REPUBLIC]
-
-Πλάτων (Plato), "Πολιτεία" ("The Republic"), 375 BC.
-
-
[RFC0952]
-
-Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet host table specification", RFC 952, DOI 10.17487/RFC0952, , <https://www.rfc-editor.org/info/rfc952>.
-
-
-
-
-
-
-
-
-

-Appendix A. Some Back Matter -

-

- - Fusce viverra ipsum tempor finibus pharetra. Vestibulum fermentum - porta neque et maximus. Aliquam tristique nibh in neque aliquam - pharetra. Sed sapien felis, efficitur at finibus et, porttitor non - quam. Nulla a ultrices nibh, ac commodo lacus. Integer vitae lorem ut - sapien venenatis maximus. Morbi ut faucibus nunc, vitae pretium - lorem. Aliquam sit amet tortor ut turpis dapibus ullamcorper. Proin - at ligula nec magna molestie eleifend:
- トヨタ 自動車 株式会社 (Toyota Jidōsha KK). - - This is a long comment line which extends well beyond the 72-character page width.

-
-

-A.1. Contributors -

-

We'd like to thank these contributors:

-
-
-
Roni Even
-
Huawei
-
David Hamelech 14
-
-Tel Aviv 64953 -
-
Israel
-
-
Additional contact information:
-
-
רוני אבן
-
וואווי
-
דוד המלך 14
-
-תל אביב 64953 -
-
ישראל
-
-
-

- Reviews and helpful comments have also been received from - ანა კიკაბიძე (Ana Kikabidze).

-
-
-

-A.2. Arbitrarysuperscript in section title -

-

Arbitrary text

-
-
-
-
-
-

-Authors' Addresses -

-
-
An Author
-
ElfTools
-
Midtskogveien 18
-
-2020 Skedsmokorset -
-
Norway
- -
-
-
-
Roni Even
-
Huawei
-
David Hamelech 14
-
-Tel Aviv 64953 -
-
Israel
- -
-
Additional contact information:
-
-
רוני אבן
-
וואווי
-
דוד המלך 14
-
-תל אביב 64953 -
-
ישראל
-
-
-
-
-
Hanako Tanaka
-
3-kai B-goshitsu
-
-4-3-2 Hakusan, Bunkyo-ku, Tokyo -
-
112-0001
-
Japan
- -
-
Additional contact information:
-
-
田中花子 様
-
日本
-
〒112-0001 -
-
東京都
-
文京区 白山4丁目3番2号
-
3階B号室
-
-
-
-
No Org
-
Tokyo
-
112-0001
-
Japan
- -
-
-
Bon Aventure
-
Université de Liège
-
Place du 20 Août 7
-
-4000 Liège -
-
Belgium
-
-
-
International Association for Cryptologic Research
-
-
-
A. Lindgren
-
Mellangården
-
Sevedstorp 125
-
Mariannelund
-
Sweden
-
-
-
- - - diff --git a/tests/valid/elements.v3.py38.html b/tests/valid/elements.v3.py38.html deleted file mode 100644 index 9a0dccc14..000000000 --- a/tests/valid/elements.v3.py38.html +++ /dev/null @@ -1,1932 +0,0 @@ - - - - - - -Xml2rfc Vocabulary V3 Elements Combined Test File - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Internet-DraftXml2rfc Vocabulary V3 ElementsJuly 2018
Author, et al.Expires January 13, 2019[Page]
-
-
-
-
Workgroup:
-
Network Working Group
-
Obsoletes:
-
-1234, 5678, 9012, 3456, 7890 (if approved)
-
Published:
-
- -
-
Intended Status:
-
Informational
-
Expires:
-
-
Authors:
-
-
-
A. Author
-
-
-
-רוני אבן (R. Even)
-
-וואווי (Huawei)
-
-
-
-田中花子 様 (H. Tanaka)
-
-
-
N. Org
-
-
-
B. Aventure
-
Université de Liège
-
-
-
International Association for Cryptologic Research
-
-
-
A. Lindgren
-
-
-
-
-

Xml2rfc Vocabulary V3 Elements
Combined Test File

-
-
-

Abstract

-

This is the abstract.

-
-
-
-
-

-Status of This Memo -

-

- This Internet-Draft is submitted in full conformance with the - provisions of BCP 78 and BCP 79.

-

- Internet-Drafts are working documents of the Internet Engineering Task - Force (IETF). Note that other groups may also distribute working - documents as Internet-Drafts. The list of current Internet-Drafts is - at https://datatracker.ietf.org/drafts/current/.

-

- Internet-Drafts are draft documents valid for a maximum of six months - and may be updated, replaced, or obsoleted by other documents at any - time. It is inappropriate to use Internet-Drafts as reference - material or to cite them other than as "work in progress."

-

- This Internet-Draft will expire on January 13, 2019.

-
-
- -
-
- ▲

-Table of Contents -

- -
-
-
-

-1. RFC 2119 key words -

- -

- The key words "MUST", "MUST NOT", - "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", - "RECOMMENDED", "NOT RECOMMENDED", "MAY", - and "OPTIONAL" in this document are to be interpreted as described in - BCP 14 [RFC2119] [RFC8174] when, and only when, they - appear in all capitals, as shown here.

-
-
-

-2. Citations -

-

- - This section contains a bunch of citations, in order to test citation formats and also - - in order to refer to each of the entries in - the Section 18.

-

Citations of References:

- -

Citations of References with explicit text:

- -

Citations of multiple Sections in References, using sectionFormat="bare":

- -

Citations of multiple Sections in References, using text and sectionFormat="bare":

- -

References to Abstract, with explicit text:

- -

References to Abstract:

- -

References to Sections, with explicit text:

- -

References to Sections:

- -

References to Appendix:

- -

References to Comments:

- -

This comment is to be cited.

-

- These references should be present: - [RFC5652] - [RFC2634] - [RFC5035] - [RFC2045] - [RFC2046] - [RFC2047] - [RFC2049] - [RFC4289] - [RFC6838]

-
-
-
-

-3. Unordered list with sub-elements -

-
    -
  • -
    - Unordered list, first bullet. [MUST], [MUST NOT] -
    -
    • -
  • - Unordered list, second bullet. Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici. -
    • -
  • -

    - Unordered list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

    -
    -
    -        Unordered list, third bullet, second element:
-        +-------------------------------------------+
-        |                                           |
-        |                  Artwork                  |
-        |                                           |
-        +-------------------------------------------+
-
    -
    -
    -
    Unordered list, third bullet, third element: Definition list, element dt.
    -
    -
    Element dd. Indent 16. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
    -
    -
    -
    -
    Unordered list, third bullet, third element: Definition list, element dt.
    -
    -
    Element dd. Indent 16. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
    -
    -
    -
    -
    -
    -Unordered list, third bullet, fourth element:
-                    Figure
-                        Figure
-                           Figure
-
    -
    -
    Figure 1: -Some figure name -
    -
    -
    REQ1:
    -
    -
    Unordered list, third bullet, fifth element: Ordered list, element li. Text only. Indent="8" -
    -
    -
    -
    REQ2:
    -
    -

    - Unordered list, third bullet, fifth element: Ordered list, element t. Indent="8". Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

    -
    -
    REQ2:1
    -
    Sublist with '%p' parent counter element in the list counter, item one -
    -
    -
    REQ2:2
    -
    Item two. -
    -
    -
    REQ2:3
    -
    Item three. -
    -
    -
    -
    -
    -
    -
    -
    <CODE BEGINS> file "sample.py"
-
-                  # Unordered list, third bullet, sixth element
-                  A = 1; # Non-ASCII comment: €
-
-<CODE ENDS>
    -
    -
      -
    • Unordered list, third bullet, seventh element: Unordered list, element li. Text only. -
      • -
    • -

      - Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem.

      -
      • -
    -

    - Unordered list, third bullet, eight and ninth element: Text and SVG Artwork:

    -
    -
    - - - - - -
    -
    -
    • -
  • -

    Artset include with <xi:include>

    -
    - - - - - -
    -
    • -
-
-
-
-

-4. Ordered list with sub-elements -

-
    -
  1. - Ordered list, first bullet. Indent="6". -
    2. -
  2. - Ordered list, second bullet. Indent="6". Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici. -
    3. -
-
    -
  1. -

    - Ordered list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

    -
    -
    -        Ordered list, third bullet, second element:
-        +-------------------------------------------+
-        |                                           |
-        |                  Artwork                  |
-        |                                           |
-        +-------------------------------------------+
-
    -
    -
    -
    Ordered list, third bullet, third element: Definition list, element dt.
    -
    -
    Element dd. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
    -
    -
    -
    -
    -
    -Ordered list, third bullet, fourth element:
-                    Figure
-                        Figure
-                           Figure
-
    -
    -
    Figure 2: -Some figure name -
    -
      -
    1. Ordered list, third bullet, fifth element: Ordered list, element li. Text only. -
      2. -
    2. -

      - Ordered list, third bullet, fifth element: Ordered list, element t. Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

      -
      3. -
    -
    -
    -                  # Ordered list, third bullet, sixth element
-                  A = 1;
-
    -
    -
      -
    • Ordered list, third bullet, seventh element: Unordered list, element li. Text only. -
      • -
    • -

      - Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. - See Appendix A, Section 3.1 of [I-D.levkowetz-xml2rfc-v3-implementation-notes] - and also Appendix A.1 of Key Words Case Ambiguity [RFC8174] / - Key Words Case Ambiguity [RFC8174], Appendix A.1 / - Key Words Case Ambiguity [RFC8174] (Appendix A.1).

      -
      • -
    -
    2. -
  2. -
    -
    4.1
    -
    Sublist with '%p' parent counter element in the list counter, item one -
    -
    -
    4.2
    -
    Item two. -
    -
    -
    4.3
    -
    Item three. -
    -
    -
    -
    3. -
-
-
-

-5. Definition list with sub-elements -

-
-
-
Term 1
-
-
-
- Definition list, first bullet. -
-
-
-
Term 2
-
- Definition list, second bullet. Text only. Octavio fuit, cum illam severitatem in eo non arbitrantur. erunt etiam, et ii quidem eruditi Graecis litteris, contemnentes Latinas, qui se plane Graecum dici velit, ut a Scaevola est praetore salutatus Athenis Albucius. In physicis plurimum posuit. ea scientia et verborum vis et natura orationis et consequentium repugnantiumve ratio potest perspici. -
-
-
Term 3
-
-

- Definition list, third bullet, element t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

-
-
-        Definition list, third bullet, second element:
-        +-------------------------------------------+
-        |                                           |
-        |                  Artwork                  |
-        |                                           |
-        +-------------------------------------------+
-
-
-
-
Definition list, third bullet, third element: Definition list, element dt.
-
-
Element dd. Nisi mihi Phaedrum, inquam, tu mentitum aut Zenonem misisti. -
-
-
-
-
-
-Definition list, third bullet, fourth element:
-                    Figure
-                        Figure
-                           Figure
-
-
-
Figure 3: -Some figure name -
-
    -
  1. Definition list, third bullet, fifth element: Ordered list, element li. Text only. -
    2. -
  2. -

    - Definition list, third bullet, fifth element: Ordered list, element t. Nam cum ad me de virtute misisti. Quae est enim contra Cyrenaicos satis acute, nihil ad iucunde vivendum reperiri posse, quod coniunctione tali sit aptius. Quae etsi mihi nullo modo nec divelli nec distrahi possint, sic de iustitia iudicandum est, quae non modo non impediri rationem amicitiae, si summum bonum diceret, primum in eo essent.

    -
      -
    • UL within OL within DL, item one -
      • -
    • UL within OL within DL, item two -
      • -
    -
      -
    • UL within OL within DL, empty="true"; item one -
      • -
    • UL within OL within DL, empty="true"; item two -
      • -
    -
      -
    • UL within OL within DL, bare="true"; item one -
      • -
    • UL within OL within DL, bare="true"; item two -
      • -
    -
    3. -
-
-
-                  # Definition list, third bullet, sixth element
-                  A = 1;
-
-
-
    -
  • Definition list, third bullet, seventh element: Unordered list, element li. Text only. -
    • -
  • -

    - Element t. Atque ut odia, invidiae, despicationes adversantur voluptatibus, sic amicitiae non posse iucunde vivi, nisi sapienter, honeste iusteque vivatur, nec sapienter, honeste, iuste, nisi iucunde. Democritea dicit perpauca mutans, sed ita, ut ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem.

    -
    • -
-

Definition list, third bullet, eight element, t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

-

Definition list, third bullet, ninth element, t. Quid? si nos non interpretum fungimur munere, sed tuemur ea, quae audiebamus, conferebamus, neque erat umquam controversia, quid ego intellegerem, sed quid probarem. Extremum autem esse bonorum eum voluptate vivere. Sic faciam igitur, inquit: unam rem explicabo, eamque maximam, de physicis alias, et quidem locis pluribus.

-
-
-
-
-
-

-6. Table -

-
-
-      +-----+-----+-----------+
-      |     |     |           |
-      +-----+-----+-----+-----+
-      |     |     |     |     |
-      +=====+=====+=====+=====+
-      |     |     |     |     |
-      +-----+-----+-----+-----+
-      |     |                 |
-      +     +-----+-----+-----+
-      |     |     |     |     |
-      +     +     +-----+-----+
-      |     |     |           |
-      +-----+     +-----+-----+
-      |     |     |     |     |
-      +=====+=====+=====+=====+
-      |     |     |     |     |
-      +-----+-----+-----+-----+
-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 1: -Header, footer, colspan and rowspan
Default alignment -
ABC D
1234
Long text in a single cellb1c1d1
Long text in a 3-cell column.
Quid igitur est? Inquit; audire enim cupio, quid non probes eius, a quo dissentias.		Long text in a 3-cell row.
Quid enim est a Cyrenaicisque melius liberiusque defenditur, tamen eius modi tempora incidunt, ut labore et dolore disputandum putant.
Another 3-cell column.c3d3
x
a5c5d5
aabbccdd
- - - - - - - - - - - - -
-Table 2: -Aligned left -
OneTwo
AlphaBeta
- - - - - - - - - - - - -
-Table 3: -Aligned center -
OneTwo
AlphaBeta
- - - - - - - - - - - - -
-Table 4: -Aligned right -
OneTwo
AlphaBeta
-

- A really tight table where left padding cannot be applied as it would throw - the left-alignment of the text off.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 5
MethodDefinitionptypepropertyValueStatusVersion
dnswlRFC 8904dnszone -

DNSWL publicly accessible query root domain

-		active1
dnswlRFC 8904policyip -

type A response received (or a quoted, - comma-separated list thereof)

-		active1
dnswlRFC 8904policytxttype TXT query responseactive1
dnswlRFC 8904dnssecone of "yes" for DNSSEC authenticated data, "no" for - not signed, or "na" for not applicableactive1
-
-
-

-7. Unicode Literals -

-
-

-7.1. Single Characters -

-
-
Expansion "num":
-
-

Example XML:

-
-
Use the character
-  <u format="num">Δ</u>.
-
-

expands to:

-

- Use the character U+0394.

-
-
-
Expansion "name":
-
-

Example XML:

-
-
Use the character <u format="name-num">Δ</u>.
-
-

expands to:

-

- Use the character GREEK CAPITAL LETTER DELTA (U+0394).

-
-
-
Expansion "num-lit":
-
-

Example XML:

-
-
Use the character <u format="num-lit">Δ</u>.
-
-

expands to:

-

- Use the character U+0394 ("Δ").

-
-
-
Expansion "num-name":
-
-

Example XML:

-
-
Use the <u format="{num} character ({name})">Δ</u>.
-
-

expands to:

-

- Use the U+0394 character (GREEK CAPITAL LETTER DELTA).

-
    -
  • Tab: U+0009 (U+0009) -
    • -
  • Char(128): U+0080 (U+0080) -
    • -
-
-
-
Expansion "num-lit-name":
-
-

Example XML:

-
-
Use the character <u format="num-lit-name">Δ</u>.
-
-

expands to:

-

- Use the character U+0394 ("Δ", GREEK CAPITAL LETTER DELTA).

-
-
-
Expansion "num-name-lit":
-
-

Example XML:

-
-
Use the character <u format="num-name-lit">Δ</u>.
-
-

expands to:

-

- Use the character U+0394 (GREEK CAPITAL LETTER DELTA, "Δ").

-
-
-
Expansion "ascii-lit-num":
-
-

Example XML:

-
-
Use the character
-  <u ascii="Delta" format="ascii-lit-num" ascii="Delta">Δ</u>.
-
-

expands to:

-

- Use the character "Delta" ("Δ", U+0394).

-
-
-
Expansion "lit-name-num":
-
-

Example XML:

-
-
Use the <u format="{lit} character ({name}, {num})">Δ</u>.
-
-

expands to:

-

- Use the "Δ" character (GREEK CAPITAL LETTER DELTA, U+0394)

-
-
-
Expansion "lit-num":
-
-

Example XML:

-
-
Use the <u format="{lit} character ({num})">Δ</u>.
-
-

expands to:

-

- Use the "Δ" character (U+0394).

-
-
-
-
-
-

-7.2. Character Strings -

-
-
Expansion "num-lit":
-
-

Example XML:

-
-
For example, the characters
-  <u ascii="STPETER" format="num-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ") from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "num-name":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="num-name">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "num-lit-name":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="num-lit-name">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 ("ᏚᎢᎵᎬᎢᎬᏒ", CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "num-name-lit":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="num-name-lit">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2 (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV, "ᏚᎢᎵᎬᎢᎬᏒ") from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "ascii-lit-num":
-
-

Example XML:

-
-
-For example, the characters
-  <u ascii="STPETER" format="ascii-lit-num">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the characters "STPETER" ("ᏚᎢᎵᎬᎢᎬᏒ", U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "lit-name-num":
-
-

Example XML:

-
-
-For example, the
-  <u ascii="STPETER" format="{lit}
-     characters ({name}, {num})">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the "ᏚᎢᎵᎬᎢᎬᏒ" characters (CHEROKEE LETTER DU, CHEROKEE LETTER I, CHEROKEE LETTER LI, CHEROKEE LETTER GV, CHEROKEE LETTER I, CHEROKEE LETTER GV, CHEROKEE LETTER SV, U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
Expansion "lit-num":
-
-

Example XML:

-
-
-For example, the
-  <u ascii="STPETER" format="{lit} characters ({num})">ᏚᎢᎵᎬᎢᎬᏒ</u>
-from the Cherokee block look similar to the ASCII characters
-"STPETER".
-
-

expands to:

-

- For example, the "ᏚᎢᎵᎬᎢᎬᏒ" characters (U+13DA U+13A2 U+13B5 U+13AC U+13A2 U+13AC U+13D2) from the Cherokee block look similar to the ASCII characters "STPETER".

-
-
-
-
-
-
-

-8. Irregular date specifications -

-

- - You can now use date ranges like "2002-2003" (See [DATE-RANGE]) and - fuzzy dates such as "Spring 1814" (See [FUZZY-DATE]) by omitting - the year/month/day attributes of <date>, and instead provide text content.

-
-
-
-

-9. Aside, Word Joiner, and Break -

- -

- - Regular: Nam ut tortor ut dui fermentum viverra. Quisque sed aliquam enim. Pellentesque - vestibulum risus sed ligula eleifend commodo. Sed vel lacus id mauris dapibus - lobortis. Suspendisse quis pellentesque nisl, vitae pulvinar felis. Ut at hendrerit - odio. Morbi non sem non ligula posuere ultrices.

- - - - -
-
Definition list with aside in <dd>
-
- -
-
-
-
-
-
-

-10. Section title test 1 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-

-11. Section level h2 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-

-11.1. Section level h3 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-

-11.1.1. Section level h4 -

-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-11.1.1.1. Section level h5 -
-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-11.1.1.1.1. Section level h6 -
-

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

-
-
-
-
-
-
-

-12. Eref brackets -

- -
-
-

-13. Sourcecode indentation -

-

Source code as-is:

-
-
-while true ; do
-    case "$1" in
-        -h| --help)     usage; exit;;   # Show this help
-        -v| --verbose)  VERBOSE=1;;     # Be more talkative
-        -V| --version)  version; exit;; # Show program version
-        --)             shift; break;;
-    esac
-    shift
-done
-
-
-

Source code within a figure:

-
-
-
-for opt, value in opts:
-    if   opt in ["-h", "--help"]: # Output this help, then exit
-        print __doc__ % locals()
-        sys.exit(1)
-    elif opt in ["-v", "--version"]: # Output version information
-        print program, version
-        sys.exit(0)
-    elif opt in ["-V", "--verbose"]: # Output version information
-        opt_verbose = True
-
-
-
Figure 4: -Sourcecode within figure -
-
-
-

-14. Tables inside lists -

-
-
Step 1:
-
-
-

(This example is excerpted from pre-RFC8677) Indent="9"

-

- At nSFF1, the following nNLM is assumed:

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-Table 6: -nNLM at nSFF1 -
SPISINext Hop(s)Transport Encapsulation (TE)
10255192.0.2.1VXLAN-gpe
10254198.51.100.10GRE
10253www.example.comHTTP
10252www.example2.comHTTP
40251198.51.100.15GRE
5020001:23:45:67:89:ab Ethernet
15212Null (end of path)None
-
-
-
-
-
-
-
-
This is an arbitrary term:
-
-
-

And this is some text with a table.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table 7
Head 1Head 2 - Head 3 -
Cell A1Cell A2 - Cell A3 -
Cell B1Cell B2 - Cell B3 -
Cell C1Cell C2 - Cell C3 -
Head 10Head 20 - Head 30 -
Cell A10Cell A20 - Cell A30 -
Cell B10Empty Cell:
-
-
-
-
-
-

-15. Wide artwork -

-
-
-0        1         2         3         4         5         6         7
-123456789012345678901234567890123456789012345678901234567890123456789012
-
-
-
-
-

-16. Sup and sub -

-
-
Sup
-
Text with superscript2 -
-
-
Sup
-
Simple superscript expressions: x-1 y+3.0 z3.2a -
-
-
Sup
-
More simple superscript expressions: x1.2 yn0 -
-
-
Sup
-
Parenthetical expressions in superscript: x(n+1) y-(k-1) z(_c) -
-
-
Sup
-
Compound superscript expressions: xx+y y_c za.0 -
-
-
Sup
-
One word superscript or two words superscript -
-
-
Sup
-
Text with sub inside superscriptx2 -
-
-
Sub
-
Text with subscript2 -
-
-
Sub
-
Simple subscript expressions: x-1 y+3.0 z3.2a -
-
-
Sub
-
More simple subscript expressions: x1.2 yn0 -
-
-
Sub
-
Parenthetical expressions in subscript: x(n+1) y-(k-1) z(_c) -
-
-
Sub
-
Compound subscript expressions: xx+y y_c za.0 -
-
-
Sub
-
One word subscript or two words subscript -
-
-
Sub
-
Text with super inside subscriptx2 -
-
-
-
-
-

-Unnumbered section -

-

- - Regular paragraph. Lorem ipsum dolor sit amet, consectetur - adipiscing elit. Ut pharetra neque vulputate dolor elementum - sodales. Maecenas maximus elit sit amet pretium facilisis. Vivamus - pulvinar, quam nec eleifend ultricies, nisi elit rhoncus risus, in - commodo mi leo in lorem.

-

- - Indented paragraph. Indent="5". Aenean ornare elit at urna molestie - fermentum. Donec erat purus, vestibulum in venenatis tempor, - feugiat nec neque. Fusce luctus sem neque, id venenatis turpis - vulputate nec. Nulla tincidunt pretium ex fringilla posuere. Cras - quis massa neque.

-
    -
  1. Indent="5". Lorem ipsum dolor sit amet, consectetur - adipiscing elit. Ut pharetra neque vulputate dolor elementum - sodales. -
    2. -
  2. Item 2 -
    3. -
- -
-
-
-

-References -

-
-

-Normative References -

-
-
[RFC2119]
-
-Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
-
-
[RFC7997]
-
-Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", IAB, RFC 7997, DOI 10.17487/RFC7997, , <https://www.rfc-editor.org/info/rfc7997>.
-
-
[RFC8174]
-
-Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.
-
-
-
-
-

-Informative References -

-
-
-

-CMS References -

-
-
[I-D.levkowetz-xml2rfc-v3-implementation-notes]
-
-Levkowetz, H., "Implementation notes for RFC7991,", Work in Progress, Internet-Draft, draft-levkowetz-xml2rfc-v3-implementation-notes-13, , <https://datatracker.ietf.org/doc/html/draft-levkowetz-xml2rfc-v3-implementation-notes-13>.
-
-
[RFC5083]
-
-Housley, R., "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type", RFC 5083, DOI 10.17487/RFC5083, , <https://www.rfc-editor.org/info/rfc5083>.
-
-
[RFC5652]
-
-Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, DOI 10.17487/RFC5652, , <https://www.rfc-editor.org/info/rfc5652>.
-
-
-
-
-
-
-

-ESS References -

-
-
[RFC2634]
-
-Hoffman, P., Ed., "Enhanced Security Services for S/MIME", RFC 2634, DOI 10.17487/RFC2634, , <https://www.rfc-editor.org/info/rfc2634>.
-
-
[RFC5035]
-
-Schaad, J., "Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility", RFC 5035, DOI 10.17487/RFC5035, , <https://www.rfc-editor.org/info/rfc5035>.
-
-
-
-
-
-
-

-MIME-SPEC References -

-
-
[RFC2045]
-
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, , <https://www.rfc-editor.org/info/rfc2045>.
-
-
[RFC2046]
-
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, , <https://www.rfc-editor.org/info/rfc2046>.
-
-
[RFC2047]
-
-Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, DOI 10.17487/RFC2047, , <https://www.rfc-editor.org/info/rfc2047>.
-
-
[RFC2049]
-
-Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC 2049, DOI 10.17487/RFC2049, , <https://www.rfc-editor.org/info/rfc2049>.
-
-
[RFC4289]
-
-Freed, N. and J. Klensin, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 4289, DOI 10.17487/RFC4289, , <https://www.rfc-editor.org/info/rfc4289>.
-
-
[RFC6838]
-
-Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, , <https://www.rfc-editor.org/info/rfc6838>.
-
-
-
-
-
-

-Other References -

-
-
[AUTHORS]
-
-Πυθαγόρας ὁ Σάμιος (Samos, P. O.), Doe, J., Bergström, A., and J. Doe, "Lots of authors", RFC 7539, DOI 10.17487/RFC7539, , <https://www.rfc-editor.org/rfc/rfc7539>.
-
-
[DATE-RANGE]
-
-Moe, J., "Document with date range", 2002-2003.
-
-
[FUZZY-DATE]
-
-Mae, J., "Document with fuzzy date", Second quarter 2010.
-
-
[GEDICHTE]
-
-Heine, H., "Dreiunddreißig Gedichte", .
-
-
[NO-DATE]
-
-Mae, N., "Document — with no date", Advances in Cryptology - AACC Edition pp. 235-265.
-
-
[REPUBLIC]
-
-Πλάτων (Plato), "Πολιτεία" ("The Republic"), 375 BC.
-
-
[RFC0952]
-
-Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet host table specification", RFC 952, DOI 10.17487/RFC0952, , <https://www.rfc-editor.org/info/rfc952>.
-
-
-
-
-
-
-
-
-

-Appendix A. Some Back Matter -

-

- - Fusce viverra ipsum tempor finibus pharetra. Vestibulum fermentum - porta neque et maximus. Aliquam tristique nibh in neque aliquam - pharetra. Sed sapien felis, efficitur at finibus et, porttitor non - quam. Nulla a ultrices nibh, ac commodo lacus. Integer vitae lorem ut - sapien venenatis maximus. Morbi ut faucibus nunc, vitae pretium - lorem. Aliquam sit amet tortor ut turpis dapibus ullamcorper. Proin - at ligula nec magna molestie eleifend:
- トヨタ 自動車 株式会社 (Toyota Jidōsha KK). - - This is a long comment line which extends well beyond the 72-character page width.

-
-

-A.1. Contributors -

-

We'd like to thank these contributors:

-
-
-
Roni Even
-
Huawei
-
David Hamelech 14
-
-Tel Aviv 64953 -
-
Israel
-
-
Additional contact information:
-
-
רוני אבן
-
וואווי
-
דוד המלך 14
-
-תל אביב 64953 -
-
ישראל
-
-
-

- Reviews and helpful comments have also been received from - ანა კიკაბიძე (Ana Kikabidze).

-
-
-

-A.2. Arbitrarysuperscript in section title -

-

Arbitrary text

-
-
-
-
-
-

-Authors' Addresses -

-
-
An Author
-
ElfTools
-
Midtskogveien 18
-
-2020 Skedsmokorset -
-
Norway
- -
-
-
-
Roni Even
-
Huawei
-
David Hamelech 14
-
-Tel Aviv 64953 -
-
Israel
- -
-
Additional contact information:
-
-
רוני אבן
-
וואווי
-
דוד המלך 14
-
-תל אביב 64953 -
-
ישראל
-
-
-
-
-
Hanako Tanaka
-
3-kai B-goshitsu
-
-4-3-2 Hakusan, Bunkyo-ku, Tokyo -
-
112-0001
-
Japan
- -
-
Additional contact information:
-
-
田中花子 様
-
日本
-
〒112-0001 -
-
東京都
-
文京区 白山4丁目3番2号
-
3階B号室
-
-
-
-
No Org
-
Tokyo
-
112-0001
-
Japan
- -
-
-
Bon Aventure
-
Université de Liège
-
Place du 20 Août 7
-
-4000 Liège -
-
Belgium
-
-
-
International Association for Cryptologic Research
-
-
-
A. Lindgren
-
Mellangården
-
Sevedstorp 125
-
Mariannelund
-
Sweden
-
-
-
- - - diff --git a/tests/valid/indexes.pages.text b/tests/valid/indexes.pages.text index 6cca78c76..011a90a2f 100644 --- a/tests/valid/indexes.pages.text +++ b/tests/valid/indexes.pages.text @@ -3,9 +3,9 @@ Network Working Group H. Person, Ed. -Internet-Draft May 16, 2022 +Internet-Draft May 23, 2022 Intended status: Experimental -Expires: November 17, 2022 +Expires: November 24, 2022 xml2rfc index tests @@ -26,7 +26,7 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on November 17, 2022. + This Internet-Draft will expire on November 24, 2022. Copyright Notice @@ -53,7 +53,7 @@ Table of Contents -Person Expires November 17, 2022 [Page 1] +Person Expires November 24, 2022 [Page 1] Internet-Draft xml2rfc index tests May 2022 @@ -109,7 +109,7 @@ Index -Person Expires November 17, 2022 [Page 2] +Person Expires November 24, 2022 [Page 2] Internet-Draft xml2rfc index tests May 2022 @@ -165,4 +165,4 @@ Author's Address -Person Expires November 17, 2022 [Page 3] +Person Expires November 24, 2022 [Page 3] diff --git a/tests/valid/indexes.prepped.xml b/tests/valid/indexes.prepped.xml index dc719ec18..93d532f16 100644 --- a/tests/valid/indexes.prepped.xml +++ b/tests/valid/indexes.prepped.xml @@ -1,6 +1,6 @@ - - + + @@ -20,7 +20,7 @@ - +
Status of This Memo @@ -41,7 +41,7 @@ material or to cite them other than as "work in progress." - This Internet-Draft will expire on 17 November 2022. + This Internet-Draft will expire on 24 November 2022.
diff --git a/tests/valid/indexes.text b/tests/valid/indexes.text index 05eda8226..ba4db24b8 100644 --- a/tests/valid/indexes.text +++ b/tests/valid/indexes.text @@ -3,9 +3,9 @@ Network Working Group H. Person, Ed. -Internet-Draft May 16, 2022 +Internet-Draft May 23, 2022 Intended status: Experimental -Expires: November 17, 2022 +Expires: November 24, 2022 xml2rfc index tests @@ -26,7 +26,7 @@ Status of This Memo time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on November 17, 2022. + This Internet-Draft will expire on November 24, 2022. Copyright Notice diff --git a/tests/valid/indexes.v3.py37.html b/tests/valid/indexes.v3.html similarity index 98% rename from tests/valid/indexes.v3.py37.html rename to tests/valid/indexes.v3.html index 1ab5d3a19..f12868525 100644 --- a/tests/valid/indexes.v3.py37.html +++ b/tests/valid/indexes.v3.html @@ -6,7 +6,7 @@ xml2rfc index tests - + @@ -23,7 +23,7 @@ Person -Expires November 17, 2022 +Expires November 24, 2022 [Page] @@ -36,12 +36,12 @@
indexes-00
Published:
- +
Intended Status:
Experimental
Expires:
-
+
Author:
@@ -71,7 +71,7 @@

time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

- This Internet-Draft will expire on November 17, 2022.

+ This Internet-Draft will expire on November 24, 2022.