Network Working Group P. Hoffman
Internet-Draft VPN Consortium
Obsoletes: 2629 (if approved) September 29, 2014
Intended status: Informational
Expires: April 2, 2015
The 'XML2RFC' version 3 Vocabulary
draft-hoffman-xml2rfc-11
Abstract
This document defines the "XML2RFC" version 3 vocabulary; an XML-
based language used for writing RFCs and Internet-Drafts. It is
heavily derived from the version 2 vocabulary that is also under
discussion. This document obsoletes the v2 grammar described in RFC
2629 and its expected followup, draft-reschke-xml2rfc.
Editorial Note (To be removed by RFC Editor)
Discussion of this draft takes place on the rfc-interest mailing list
(rfc-interest@rfc-editor.org), which has its home page at
<https://www.rfc-editor.org/mailman/listinfo/rfc-interest>.
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 April 2, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
Hoffman Expires April 2, 2015 [Page 1]
Internet-Draft XML2RFCv3 September 2014
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. Design Criteria for the Changes in v3 . . . . . . . . . . 5
1.2. Differences from v2 to v3 . . . . . . . . . . . . . . . . 6
1.2.1. New Elements in v3 . . . . . . . . . . . . . . . . . 6
1.2.2. New Attributes for Existing Elements . . . . . . . . 7
1.2.3. Elements and Attributes Deprecated from v2 . . . . . 7
1.2.4. Additional Changes from v2 . . . . . . . . . . . . . 8
1.3. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 9
2. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1. <abstract> . . . . . . . . . . . . . . . . . . . . . . . 10
2.2. <address> . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3. <annotation> . . . . . . . . . . . . . . . . . . . . . . 10
2.4. <area> . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5. <artwork> . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6. <aside> . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7. <author> . . . . . . . . . . . . . . . . . . . . . . . . 15
2.8. <b> . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9. <back> . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.10. <bcp14> . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.11. <blockquote> . . . . . . . . . . . . . . . . . . . . . . 18
2.12. <city> . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.13. <code> . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.14. <country> . . . . . . . . . . . . . . . . . . . . . . . . 20
2.15. <cref> . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.16. <date> . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.17. <dd> . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.18. <displayreference> . . . . . . . . . . . . . . . . . . . 23
2.19. <dl> . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.20. <dt> . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.21. <em> . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.22. <email> . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.23. <eref> . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.24. <figure> . . . . . . . . . . . . . . . . . . . . . . . . 27
2.25. <front> . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.26. <i> . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.27. <iref> . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.28. <keyword> . . . . . . . . . . . . . . . . . . . . . . . . 31
2.29. <li> . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Hoffman Expires April 2, 2015 [Page 2]
Internet-Draft XML2RFCv3 September 2014
2.30. <link> . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.31. <middle> . . . . . . . . . . . . . . . . . . . . . . . . 34
2.32. <name> . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.33. <note> . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.34. <ol> . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.35. <organization> . . . . . . . . . . . . . . . . . . . . . 37
2.36. <phone> . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.37. <postal> . . . . . . . . . . . . . . . . . . . . . . . . 37
2.38. <postalLine> . . . . . . . . . . . . . . . . . . . . . . 38
2.39. <refcontent> . . . . . . . . . . . . . . . . . . . . . . 38
2.40. <reference> . . . . . . . . . . . . . . . . . . . . . . . 40
2.41. <referencegroup> . . . . . . . . . . . . . . . . . . . . 40
2.42. <references> . . . . . . . . . . . . . . . . . . . . . . 41
2.43. <region> . . . . . . . . . . . . . . . . . . . . . . . . 41
2.44. <rfc> . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.45. <section> . . . . . . . . . . . . . . . . . . . . . . . . 46
2.46. <seriesInfo> . . . . . . . . . . . . . . . . . . . . . . 48
2.47. <sourcecode> . . . . . . . . . . . . . . . . . . . . . . 49
2.48. <street> . . . . . . . . . . . . . . . . . . . . . . . . 51
2.49. <strong> . . . . . . . . . . . . . . . . . . . . . . . . 52
2.50. <sub> . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.51. <sup> . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.52. <t> . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.53. <table> . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.54. <tbody> . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.55. <td> . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.56. <tfoot> . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.57. <th> . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.58. <thead> . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.59. <title> . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.60. <tr> . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.61. <tt> . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.62. <ul> . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.63. <uri> . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.64. <workgroup> . . . . . . . . . . . . . . . . . . . . . . . 63
2.65. <xref> . . . . . . . . . . . . . . . . . . . . . . . . . 63
3. Elements from v2 That Have Been Deprecated . . . . . . . . . 66
3.1. <c> . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.2. <facsimile> . . . . . . . . . . . . . . . . . . . . . . . 67
3.3. <format> . . . . . . . . . . . . . . . . . . . . . . . . 67
3.4. <list> . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.5. <postamble> . . . . . . . . . . . . . . . . . . . . . . . 68
3.6. <preamble> . . . . . . . . . . . . . . . . . . . . . . . 69
3.7. <spanx> . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.8. <texttable> . . . . . . . . . . . . . . . . . . . . . . . 71
3.9. <ttcol> . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.10. <vspace> . . . . . . . . . . . . . . . . . . . . . . . . 73
4. Internationalization Considerations . . . . . . . . . . . . . 73
Hoffman Expires April 2, 2015 [Page 3]
Internet-Draft XML2RFCv3 September 2014
5. Security Considerations . . . . . . . . . . . . . . . . . . . 73
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 73
6.1. Internet Media Type Registration . . . . . . . . . . . . 74
6.2. Link Relation Registration . . . . . . . . . . . . . . . 75
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 75
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 76
8.1. Normative References . . . . . . . . . . . . . . . . . . 76
8.2. Informative References . . . . . . . . . . . . . . . . . 76
Appendix A. Front Page Generation . . . . . . . . . . . . . . . 78
A.1. The /rfc/@category Attribute . . . . . . . . . . . . . . 78
A.2. The /rfc/@ipr Attribute . . . . . . . . . . . . . . . . . 78
A.2.1. Current Values: '*trust200902' . . . . . . . . . . . 79
A.2.2. Historic Values . . . . . . . . . . . . . . . . . . . 80
Appendix B. The v3 Format and Processors . . . . . . . . . . . . 81
B.1. Including External Text . . . . . . . . . . . . . . . . . 82
B.2. Anchors and IDs . . . . . . . . . . . . . . . . . . . . . 83
B.2.1. Overlapping Values . . . . . . . . . . . . . . . . . 84
Appendix C. Relax NG Schema . . . . . . . . . . . . . . . . . . 85
Appendix D. Schema Differences from v2 . . . . . . . . . . . . . 100
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Hoffman Expires April 2, 2015 [Page 4]
Internet-Draft XML2RFCv3 September 2014
1. Introduction
This document describes version 3 ("v3") of the "XML2RFC" vocabulary;
an XML-based language ('Extensible Markup Language', [XML]) used for
writing RFCs ([RFC7322]) and Internet-Drafts ([IDGUIDE]).
This document obsoletes the version ("v2") vocabulary [XML2RFCv2],
which contains the extended language definition. That document in
turn obsoletes the original version ("v1") [RFC2629]. This document
directly copies the material from [XML2RFCv2] where possible; as that
document makes its way toward RFC publication, this document will
incorporate as many of the changes as possible.
The v3 format will be used as part of the new RFC series described in
[RFC6949]. The new format will be handled by one or more new
processors for checking the XML and converting it to other
representations. Features of the expected processors are described
in Appendix B.
Note that the vocabulary contains certain constructs that might not
be used when generating of the final text; however, they can provide
useful data for other uses (such as index generation, populating a
keyword database, or syntax checks).
In this document, the term "format" is used when describing types of
documents, primarily XML and HTML. The term "representation" is used
when talking about a specific instatiation of a format, such as an
XML document or an HTML document that was created by an XML document.
The following two sections are a hopefully-complete list of all the
technical changes between [XML2RFCv2] and this document, as well as
the design criteria for those changes.
1.1. Design Criteria for the Changes in v3
The design criteria of the changes from v2 to v3 are:
o The intention is that starting and editing a v3 document will be
easier than for a v2 document.
o There will be good v2-to-v3 conversion tools for when an author
wants to change versions.
o There are no current plans to make v3 XML the required submission
representation for drafts or RFCs. That might happen eventually,
but it is likely to be years away.
There is a desire to keep as much of the v2 grammar as makes sense
Hoffman Expires April 2, 2015 [Page 5]
Internet-Draft XML2RFCv3 September 2014
within the above design criteria and not to make gratuitous changes
to the v2 grammar. Another way to say this is "we would rather
encourage backward compatibility but not be constrained by it".
Still, the goal of starting and editing a v3 document being easier
than for a v2 document is more important than backwards compatibility
with v2, given the latter two design criteria.
v3 is upwards compatible with v2, meaning that a v2 document is meant
to be a valid v3 document as well. However, some features of v2 are
deprecated in v3 in favor of new elements. Deprecated features are
listed in Section 1.2.3, and are described in [XML2RFCv2].
1.2. Differences from v2 to v3
The format changes in v3 are listed in the following subsections.
1.2.1. New Elements in v3
o Add <dl>, <ul>, and <ol> as new ways to make lists. This is a
significant change from v2 in that the child under these elements
is <li>, not <t>. <li> has a model of either containing one or
more <t> elements, or containing the flowing text normally found
in <t>. These lists are children of <section>s instead of <t>.
o Add <strong>, <b>, <em>, <i>, <tt>, <sub>, and <sup> for character
formatting.
o Add <aside> for incidental text that will be indented when
displayed.
o Add <sourcecode> to differentiate from <artwork>.
o Add <table>, <thead>, <tbody>, <tfoot>, <tr>, <td>, and <th> to
give table functionality like that in HTML.
o Add <blockquote> to indicate a quotation as in a paragraph-like
format.
o Add <name> to sections, notes, figures, and texttables to allow
character formatting (fixed-width font) in their titles, and to
allow references.
o Add <postalLine>, free text that represents one line of the
address.
o Add <displayreference> to allow display of more mneumonic anchor
names for automatically-included references.
Hoffman Expires April 2, 2015 [Page 6]
Internet-Draft XML2RFCv3 September 2014
o Add <refcontent> to allow better control of text in a reference.
o Add <referencegroup> to allow referemcing multi-RFC documents such
as STDs and BCPs.
o Add <link> to point to a resource related to the RFC.
1.2.2. New Attributes for Existing Elements
o Add "sortRefs", "symRefs", "tocDepth", and "tocInclude" attributes
to <rfc> to cover processor instructions (PIs) that were in v2
that are still needed in the grammar.
o Add "ascii" attributes to <author>, <email>, <organization>,
<street>, <city>, <region> and <code>. This allows an author to
specify their information in their native scripts as the primary
entry and still allow the ASCII-equivalent values to appear in the
processed documents.
o Add "xml:lang" attribute to <artwork>, <postal>, and <author>.
This is sometimes useful for renderers which display different
fonts for ideographic characters used in China and Japan.
o Add the "section", "relative", and "sectionFormat" attributes to
<xref>.
o Add the "numbered" and "removeinrfc" attributes to <section>.
o Add "boilerplateText", "figureNumber", "tableNumber", and
"sectionNumber" attributes to <rfc>, <figure>, <table>, and
<section>, respectively.
o Add "partNumber" to <artwork>, <artwork>, <aside>, <blockquote>,
<li>, <sourcecode>, and <t> to hold automatically generated
numbers for items in a section that don't have their own numbering
(namely figures and tables).
1.2.3. Elements and Attributes Deprecated from v2
Deprecated elements and attributes are legacy vocabulary from v2 that
are supported for input to v3 processors. They are likely to be
removed from those processors in the future. Instead of being listed
in Section 2, they are listed in in Section 3. See Appendix B for
more information on processors and how they will handle deprecated
features.
Hoffman Expires April 2, 2015 [Page 7]
Internet-Draft XML2RFCv3 September 2014
o Deprecate <list> in favor of <dl>, <ul>, and <ol>.
o Deprecate <spanx>; replace it with <strong>, <b>, <em>, <i>, and
<tt>.
o Deprecate <vspace> because the major use for it, creating pseudo-
paragraph-breaks in lists, is now handled properly.
o Deprecate <texttable>, <ttcol>, and <c>; replace them with the new
table elements (<table> and the elements that can be contained
within it).
o Deprecate <facsimile> because it is rarely used and is not
actually useful; <email> is a much more useful way to get in touch
with authors.
o Deprecate <format> because it is not useful and has caused
surprise for authors in the past. If the goal is to provide a
single URI (Uniform Resource Identifier) for a reference, use the
"target" attribute on <reference> instead.
o Deprecate <preamble> and <postamble> in favor of simply using <t>.
This also deprecates the "align" attribute in <figure>.
o Deprecate the "title" attribute in <section>, <note>, <figure>,
and <texttable> in favor of the new <name>.
o Deprecate the "alt", and "src" attributes in <figure> because they
overlap with the attributes in <artwork>.
o Deprecate the "xml:space" attribute in <artwork> because there was
only one useful value. Deprecate "height" and "width" attribute
in both <artwork> and <figure> because they are not needed for the
new output formats.
o Deprecate the "pageno" attribute in <xref> because it was unused
in v2. Deprecate the "none" and "title" values for the "format"
attribute in <xref> because the former makes no sense semantically
and the latter because it has unpredictable output.
1.2.4. Additional Changes from v2
o Allow non-ASCII characters in the format; the characters that are
actually allowed will be determined by the RFC Editor.
o Allow <artwork> and <sourcecode> to be used on their own in
<section> (no longer confine them to a figure).
Hoffman Expires April 2, 2015 [Page 8]
Internet-Draft XML2RFCv3 September 2014
o Give more specifics of handling the "type" attribute in <artwork>.
o In <address>, allow the sub-elements to be in any order.
o Allow <strong>, <b>, <em>, <i>, <tt>, <eref>, and <xref> in
<cref>.
o Allow the sub-elements inside a <reference> to be in any order.
o Turned off the auto-generation of anchors in <cref> because there
is no use case for them that cannot be achieved in other ways.
o Allow more than one <artwork>, or more than one <sourcecode>, in
<figure>.
o In <front>, make <date> optional.
o In <postal>, allow the sub-elements to be in any order. Also
allow the inclusion of the new <postalLine> instead of the older
elements.
o In <section>, restricted the names of the anchors that can be used
on some types of sections.
o <t> now only contains non-block elements, so it no longer contains
<figure> elements.
o Do not generate the grammar from a DTD, but instead get it
directly from the Relax Next Generation (RNG) grammar [RNG].
1.3. Syntax Notation
The XML vocabulary here is defined in prose, based on the Relax NG
schema ([RNC]) contained in Appendix C (specified in Relax NG Compact
Notation, "RNC").
Note that the schema can be used for automated validity checks, but
certain constraints are only described in prose (example: the
conditionally required presence of the "abbrev" attribute).
2. Elements
The sections below describe all elements and their attributes.
Note that attributes not labeled "mandatory" are optional.
Many elements have an optional "anchor" attribute. In all cases, the
value of the "anchor" attribute needs to be a valid XML "Name"
Hoffman Expires April 2, 2015 [Page 9]
Internet-Draft XML2RFCv3 September 2014
(Section 2.3 of [XML]). In short, it is a text string with no spaces
or colons; hyphens, periods, and underscores are allowed; some
characters cannot be in the first position (such as digits, hypen, or
period). Anchors are described in more detail in Appendix B.2.
Except inside <artwork> and <sourcecode>, horizontal whitespace and
linebreaks are collapsed into a single whitespace, and leading and
trailing whitespace are trimmed off.
2.1. <abstract>
Contains the abstract of the document. See [RFC7322] for more
information on restrictions for the abstract.
This element appears as a child element of: <front> (Section 2.25).
Content model:
One or more <t> elements (Section 2.52)
2.2. <address>
Provides address information for the author.
This element appears as a child element of: <author> (Section 2.7).
Content model:
In any order:
o <email> elements (Section 2.22)
o <facsimile> elements (Section 3.2)
o <phone> elements (Section 2.36)
o <postal> elements (Section 2.37)
o <uri> elements (Section 2.63)
2.3. <annotation>
Provides additional prose augmenting a bibliographical reference.
This element appears as a child element of: <reference>
(Section 2.40).
Content model:
Hoffman Expires April 2, 2015 [Page 10]
Internet-Draft XML2RFCv3 September 2014
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <spanx> elements (Section 3.7)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.3.1. 'ascii' attribute
The ASCII equivalent of the annotation.
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>.
The list at the time that this document is being published is:
"Applications", "app", "General", "gen", "Internet", "int",
"Operations and Management", "ops", "Real-time Applications and
Infrastructure", "rai", "Routing", "rtg", "Security", "sec",
"Transport", "tsv".
This element appears as a child element of: <front> (Section 2.25).
Hoffman Expires April 2, 2015 [Page 11]
Internet-Draft XML2RFCv3 September 2014
Content model: only text content.
2.5. <artwork>
This element allows the inclusion of "artwork" into the document.
<artwork> provides full control of horizontal whitespace and line
breaks, and thus is used for a variety of things, such as:
o diagrams ("line art"),
o complex tables, or
o protocol unit diagrams.
Alternatively, the "src" attribute allows referencing an external
graphics file, such as a bitmap or a vector drawing, using a URI. In
this case, the textual content acts as fallback for output
representations that do not support graphics, and thus ought to
contain either a "line art" variant of the graphics, or otherwise
prose that describes the included image in sufficient detail.
If the artwork includes either "&" or "<" characters, or the string
"]]>" those characters need to be encoded using escaping or CDATA
block(s); see <sourcecode> for a fuller description of these
solutions.
In [XML2RFCv2], the <artwork> element was also used for source code
and formal languages; in v3, this is now done with <sourcecode>.
There are at least four ways to include SVG in artwork in Internet
Drafts:
o Inline, by including all of the SVG in the content of the element
(such as "<artwork type="svg"><svg xmlns...">")
o Inline, but using XInclude (see Appendix B.1 (such as "<artwork
type="svg"><xi:include href=...")
o As a data: URI (such as "<artwork type="svg" src="data:image/
svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3...">")
o As a URI to an external entity (such as "<artwork type="svg"
src="http://www.example.com/...">")
This element appears as a child element of: <aside> (Section 2.6),
<blockquote> (Section 2.11), <dd> (Section 2.17), <figure>
(Section 2.24), <li> (Section 2.29), <section> (Section 2.45), <td>
Hoffman Expires April 2, 2015 [Page 12]
Internet-Draft XML2RFCv3 September 2014
(Section 2.55), and <th> (Section 2.57).
Content model:
Text
2.5.1. 'align' attribute
Controls whether the artwork appears left justified (default),
centered, or right justified.
Allowed values:
o "left" (default)
o "center"
o "right"
2.5.2. 'alt' attribute
Alternative text description of the artwork (not just the caption).
This is only used with artwork that is text-based; when the art comes
from the "src" attribute, the alternative text comes from the text of
the artwork itself.
2.5.3. 'anchor' attribute
Document-wide unique identifier for this artwork.
2.5.4. 'height' attribute
Deprecated.
2.5.5. 'name' attribute
A filename suitable for the contents (such as for extraction to a
local file).
This attribute generally isn't used for document generation, but it
can be helpful for other kinds of tools (such as automated syntax
checkers which work by extracting the artwork).
2.5.6. 'partNumber' attribute
The number for this artwork within the section. The numbering is
shared with other elements of a section. This is described in more
detail in Appendix B.2.
Hoffman Expires April 2, 2015 [Page 13]
Internet-Draft XML2RFCv3 September 2014
2.5.7. 'src' attribute
The URI reference of a graphics file ([RFC3986]).
Note that this can be a "data" URI ([RFC2397]).
2.5.8. 'type' attribute
Specifies the type of the artwork. The value of this attribute is
free text with certain values designated as preferred. A private
processor (as described in Appendix B) might add type-specific
formatting to artwork with the preferred values. If a processor
encounters a value for "type" that is not one of the preferred
values, it can issue a warning but should still use the artwork as if
it had no "type" attribute.
The preferred values for <artwork> types are:
o ascii-art
o call-flow
o hex-dump
o svg
The RFC Editor will maintain a complete list of the preferred values
on its 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.
2.5.9. 'width' attribute
Deprecated.
2.5.10. 'xml:lang' attribute
Allows specification of the language used. This is sometimes useful
for renderers which display different fonts for ideographic
characters used in China and Japan.
2.5.11. 'xml:space' attribute
Deprecated.
Hoffman Expires April 2, 2015 [Page 14]
Internet-Draft XML2RFCv3 September 2014
2.6. <aside>
This element is a container for content that is semantically less
important or tangential to the content that surrounds it. The
elements inside this container are indented from both margins when
displayed.
This element appears as a child element of: <section> (Section 2.45).
Content model:
In any order:
o <artwork> elements (Section 2.5)
o <figure> elements (Section 2.24)
o <iref> elements (Section 2.27)
o <sourcecode> elements (Section 2.47)
o <t> elements (Section 2.52)
o <texttable> elements (Section 3.8)
2.6.1. 'anchor' attribute
Document-wide unique identifier for this aside.
2.6.2. 'partNumber' attribute
The number for this aside within the section. The numbering is
shared with other elements of a section. This is described in more
detail in Appendix B.2.
2.7. <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 (inside of <reference>).
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).
Hoffman Expires April 2, 2015 [Page 15]
Internet-Draft XML2RFCv3 September 2014
Furthermore, the "role" attribute can be used to mark an author as
"editor". This is reflected both on the front page and in
bibliographical references. Note that this specification does not
define a precise meaning for the term "editor".
See Section "Authors vs. Contributors" of [RFCPOLICY] for more
information.
This element appears as a child element of: <front> (Section 2.25).
Content model:
In this order:
1. One optional <organization> element (Section 2.35)
2. One optional <address> element (Section 2.2)
2.7.1. 'ascii' attribute
The ASCII equivalent of the author's full name.
2.7.2. 'fullname' attribute
The full name (used in the automatically generated "Author's Address"
section).
2.7.3. 'initials' attribute
Author initials (used on the front page and in references).
The value contains one or more initials, each followed by a period.
Initials should be provided as a whitespace separated list of pairs
of a letter and a dot.
2.7.4. 'role' attribute
Specifies the role the author had in creating the document.
Allowed values:
o "editor"
2.7.5. 'surname' attribute
The author's surname (used on the front page and in references).
Hoffman Expires April 2, 2015 [Page 16]
Internet-Draft XML2RFCv3 September 2014
2.7.6. 'xml:lang' attribute
Allows specification of the language used. This is sometimes useful
for renderers which display different fonts for CJK characters.
2.8. <b>
Causes the text to be displayed in bold. It is almost always a
better idea to use the <strong> element instead. This element can be
combined with other character formatting elements, and the formatting
will be additive.
This element appears as a child element of: <annotation>
(Section 2.3), <blockquote> (Section 2.11), <c> (Section 3.1), <cref>
(Section 2.15), <dd> (Section 2.17), <dt> (Section 2.20), <em>
(Section 2.21), <i> (Section 2.26), <li> (Section 2.29), <postamble>
(Section 3.5), <preamble> (Section 3.6), <refcontent> (Section 2.39),
<sub> (Section 2.50), <sup> (Section 2.51), <t> (Section 2.52), <td>
(Section 2.55), <th> (Section 2.57), and <tt> (Section 2.61).
Content model:
In any order:
o Text
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
Hoffman Expires April 2, 2015 [Page 17]
Internet-Draft XML2RFCv3 September 2014
2.9. <back>
Contains the "back" part of the document: the references and
appendices. In <back>, <section> elements indicate appendices.
This element appears as a child element of: <rfc> (Section 2.44).
Content model:
In this order:
1. Optional <displayreference> elements (Section 2.18)
2. Optional <references> elements (Section 2.42)
3. Optional <section> elements (Section 2.45)
2.10. <bcp14>
Marks text that are phrases defined in BCP 14 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 not
correct to say "<bcp14>The packet MUST be dropped.</bcp14>".
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <blockquote> (Section 2.11), <c>
(Section 3.1), <dd> (Section 2.17), <dt> (Section 2.20), <em>
(Section 2.21), <i> (Section 2.26), <li> (Section 2.29), <postamble>
(Section 3.5), <preamble> (Section 3.6), <refcontent> (Section 2.39),
<strong> (Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51),
<t> (Section 2.52), <td> (Section 2.55), <th> (Section 2.57), and
<tt> (Section 2.61).
Content model: only text content.
2.11. <blockquote>
Specifies a block of text is a quotation. The "cite" attribute is
required, and must be a URI.
This element appears as a child element of: <section> (Section 2.45).
Content model:
Hoffman Expires April 2, 2015 [Page 18]
Internet-Draft XML2RFCv3 September 2014
In any order:
o Text
o <artwork> elements (Section 2.5)
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <em> elements (Section 2.21)
o <figure> elements (Section 2.24)
o <i> elements (Section 2.26)
o <sourcecode> elements (Section 2.47)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
2.11.1. 'anchor' attribute
Document-wide unique identifier for this quotation.
2.11.2. 'cite' attribute (mandatory)
The source of the citation. This must be a URI.
2.11.3. 'partNumber' attribute
The number for this blockquote within the section. The numbering is
shared with other elements of a section. This is described in more
detail in Appendix B.2.
2.12. <city>
Gives the city name in a postal address.
This element appears as a child element of: <postal> (Section 2.37).
Content model: only text content.
Hoffman Expires April 2, 2015 [Page 19]
Internet-Draft XML2RFCv3 September 2014
2.12.1. 'ascii' attribute
The ASCII equivalent of the city name.
2.13. <code>
Gives the postal region code.
This element appears as a child element of: <postal> (Section 2.37).
Content model: only text content.
2.13.1. 'ascii' attribute
The ASCII equivalent of the postal code.
2.14. <country>
Gives the country in a postal address.
This element appears as a child element of: <postal> (Section 2.37).
Content model: only text content.
2.15. <cref>
Represents a comment.
Comments can be used in a document while it is work-in-progress.
They usually appear either inline and visually highlighted, at the
end of the document (depending on file representation and settings of
the processor), or not at all (when generating an RFC).
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <c> (Section 3.1), <dd>
(Section 2.17), <dt> (Section 2.20), <em> (Section 2.21), <i>
(Section 2.26), <li> (Section 2.29), <name> (Section 2.32),
<postamble> (Section 3.5), <preamble> (Section 3.6), <strong>
(Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51), <t>
(Section 2.52), <td> (Section 2.55), <th> (Section 2.57), <tt>
(Section 2.61), and <ttcol> (Section 3.9).
Content model:
In any order:
o Text
Hoffman Expires April 2, 2015 [Page 20]
Internet-Draft XML2RFCv3 September 2014
o <b> elements (Section 2.8)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.15.1. 'anchor' attribute
Document-wide unique identifier for this comment.
2.15.2. 'source' attribute
Holds the "source" of a comment, such as the name or the initials of
the person who made the comment.
2.16. <date>
Provides information about the publication date.
Note that this element is used both for the boilerplate of the
document being produced, and also inside bibliographic references
that use the <front> element.
In the boilerplate case, it defines the date of publication for the
current document (Internet Draft or RFC). When producing Internet-
Drafts, the Draft Processor uses this date to compute the expiration
date (see [IDGUIDE]). When one or more of "year", "month", or "day"
are left out, the processor will attempt to use the current system
date if the attributes that are present are consisten with that date.
Also in the first case, that month names, if given, need to match the
full English month name: "January", "February", "March", "April",
"May, "June", "July", "August", "September", "October", "November",
or "December".
In the case of bibliographic references, the date information can
Hoffman Expires April 2, 2015 [Page 21]
Internet-Draft XML2RFCv3 September 2014
have prose text for the month or year. For example, vague dates
(year="ca. 2000"), date ranges (year="2012-2013"), non-specific
months (month="Second quarter") and so on, are allowed.
This element appears as a child element of: <front> (Section 2.25).
Content model: this element does not have any contents.
2.16.1. 'day' attribute
Day of publication; this is a number.
2.16.2. 'month' attribute
Month of publication; this is the English name of the month.
2.16.3. 'year' attribute
Year of publication.
2.17. <dd>
The definition part of an entry in a definition list.
This element appears as a child element of: <dl> (Section 2.19).
Content model:
Either:
One or more <t> elements (Section 2.52)
Or:
In any order, but at least one of:
* Text
* <artwork> elements (Section 2.5)
* <b> elements (Section 2.8)
* <bcp14> elements (Section 2.10)
* <cref> elements (Section 2.15)
* <dl> elements (Section 2.19)
Hoffman Expires April 2, 2015 [Page 22]
Internet-Draft XML2RFCv3 September 2014
* <em> elements (Section 2.21)
* <eref> elements (Section 2.23)
* <figure> elements (Section 2.24)
* <i> elements (Section 2.26)
* <iref> elements (Section 2.27)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.47)
* <strong> elements (Section 2.49)
* <sub> elements (Section 2.50)
* <sup> elements (Section 2.51)
* <tt> elements (Section 2.61)
* <ul> elements (Section 2.62)
* <xref> elements (Section 2.65)
2.18. <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 mneumonic anchor names for automatically-included references.
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 from="RFC6449" to="RFC-dev"/>
This element appears as a child element of: <back> (Section 2.9).
Content model: this element does not have any contents.
2.18.1. 'from' attribute (mandatory)
This attribute must be the name of an anchor in a <reference>
element.
Hoffman Expires April 2, 2015 [Page 23]
Internet-Draft XML2RFCv3 September 2014
2.18.2. 'to' attribute (mandatory)
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, A-Z.
The other characters in the string must be 0-9, a-z, A-Z, "-", ".",
and "_".
2.19. <dl>
A definition list. Each entry has a pair of elements: a term (<dt>)
and a definition (<dd>).
This element appears as a child element of: <dd> (Section 2.17), <li>
(Section 2.29), <section> (Section 2.45), <td> (Section 2.55), and
<th> (Section 2.57).
Content model:
One or more sequences of:
1. One <dt> element
2. One <dd> element
2.19.1. 'hanging' attribute
The hanging attribute defines whether or not the term appears on the
same line as the definition. hanging="false" indicates that the term
is to the left of the definition, while hanging="true" indicates that
the term will be on a separate line.
Allowed values:
o "false" (default)
o "true"
2.19.2. 'spacing' attribute
Defines whether or not there is a blank line between entries.
spacing="normal" indicates a single blank line, while
spacing="compact" indicates no space between.
Allowed values:
o "normal" (default)
Hoffman Expires April 2, 2015 [Page 24]
Internet-Draft XML2RFCv3 September 2014
o "compact"
2.20. <dt>
The term being defined in a definition list.
This element appears as a child element of: <dl> (Section 2.19).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.21. <em>
Indicates text that is semantically empahsized. This element will be
displayed as italic after processing. This element has the same
effects as <i>.
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <blockquote> (Section 2.11), <c>
(Section 3.1), <cref> (Section 2.15), <dd> (Section 2.17), <dt>
(Section 2.20), <li> (Section 2.29), <postamble> (Section 3.5),
Hoffman Expires April 2, 2015 [Page 25]
Internet-Draft XML2RFCv3 September 2014
<preamble> (Section 3.6), <refcontent> (Section 2.39), <strong>
(Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51), <t>
(Section 2.52), <td> (Section 2.55), <th> (Section 2.57), and <tt>
(Section 2.61).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <eref> elements (Section 2.23)
o <iref> elements (Section 2.27)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.22. <email>
Provides an email address.
The value is expected to be the scheme-specific part of a "mailto"
URI (so does not include the prefix "mailto:"). See Section 2 of
[RFC6068] for details.
This element appears as a child element of: <address> (Section 2.2).
Content model: only text content.
2.22.1. 'ascii' attribute
The ASCII equivalent of the author's email address. This is only
used if the email address has one or two internationalized
components.
Hoffman Expires April 2, 2015 [Page 26]
Internet-Draft XML2RFCv3 September 2014
2.23. <eref>
Represents an "external" link (as specified in the "target"
attribute). This can be used for creating linked references, such as
in HTML output.
If the element has text content, that content will be used.
Otherwise, the value of the target attribute will be inserted in
angle brackets ([RFC3986], Appendix C).
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <c> (Section 3.1), <cref>
(Section 2.15), <dd> (Section 2.17), <dt> (Section 2.20), <em>
(Section 2.21), <i> (Section 2.26), <li> (Section 2.29), <name>
(Section 2.32), <postamble> (Section 3.5), <preamble> (Section 3.6),
<strong> (Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51),
<t> (Section 2.52), <td> (Section 2.55), <th> (Section 2.57), <tt>
(Section 2.61), and <ttcol> (Section 3.9).
Content model: only text content.
2.23.1. 'target' attribute (mandatory)
URI of the link target (see Section 3 of [RFC3986]).
2.24. <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 appears as a child element of: <aside> (Section 2.6),
<blockquote> (Section 2.11), <dd> (Section 2.17), <li>
(Section 2.29), <section> (Section 2.45), <td> (Section 2.55), and
<th> (Section 2.57).
Content model:
In this order:
1. One optional <name> element (Section 2.32)
2. Optional <iref> elements (Section 2.27)
3. One optional <preamble> element (Section 3.6)
4. In any order, but at least one of:
Hoffman Expires April 2, 2015 [Page 27]
Internet-Draft XML2RFCv3 September 2014
* <artwork> elements (Section 2.5)
* <sourcecode> elements (Section 2.47)
5. One optional <postamble> element (Section 3.5)
2.24.1. 'align' attribute
Deprecated.
Note: does not affect title or <artwork> alignment.
Allowed values:
o "left" (default)
o "center"
o "right"
2.24.2. 'alt' attribute
Deprecated. If the goal is to provide a single URI for a reference,
use the "target" attribute on <reference> instead.
2.24.3. 'anchor' attribute
Document-wide unique identifier for this figure.
2.24.4. 'figureNumber' attribute
The number for this figure. This attribute and its value are
automatically generated by the RFC Processor. If the value already
exists when the RFC Processor is run, it is replaced.
2.24.5. 'height' attribute
Deprecated.
2.24.6. 'src' attribute
Deprecated.
2.24.7. 'suppress-title' attribute
Deprecated. Figures always now get captions.
Allowed values:
Hoffman Expires April 2, 2015 [Page 28]
Internet-Draft XML2RFCv3 September 2014
o "true"
o "false" (default)
2.24.8. 'title' attribute
Deprecated. Use <name> instead.
2.24.9. 'width' attribute
Deprecated.
2.25. <front>
Represent the "front matter": metadata (such as author information),
abstract, and additional notes.
This element appears as a child element of: <reference>
(Section 2.40), and <rfc> (Section 2.44).
Content model:
In this order:
1. One <title> element (Section 2.59)
2. One or more <author> elements (Section 2.7)
3. One optional <date> element (Section 2.16)
4. Optional <area> elements (Section 2.4)
5. Optional <workgroup> elements (Section 2.64)
6. Optional <keyword> elements (Section 2.28)
7. One optional <abstract> element (Section 2.1)
8. Optional <note> elements (Section 2.33)
2.26. <i>
Causes the text to be displayed in italic. It is almost always a
better idea to use the <em> element instead.
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <blockquote> (Section 2.11), <c>
(Section 3.1), <cref> (Section 2.15), <dd> (Section 2.17), <dt>
Hoffman Expires April 2, 2015 [Page 29]
Internet-Draft XML2RFCv3 September 2014
(Section 2.20), <li> (Section 2.29), <postamble> (Section 3.5),
<preamble> (Section 3.6), <refcontent> (Section 2.39), <strong>
(Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51), <t>
(Section 2.52), <td> (Section 2.55), <th> (Section 2.57), and <tt>
(Section 2.61).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <eref> elements (Section 2.23)
o <iref> elements (Section 2.27)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.27. <iref>
Provides terms for the document's index.
Index entries can be either single items (when just the "item"
attribute is given) or nested items (by specifying "subitem" as
well).
This element appears as a child element of: <annotation>
(Section 2.3), <aside> (Section 2.6), <b> (Section 2.8), <c>
(Section 3.1), <dd> (Section 2.17), <dt> (Section 2.20), <em>
(Section 2.21), <figure> (Section 2.24), <i> (Section 2.26), <li>
(Section 2.29), <name> (Section 2.32), <postamble> (Section 3.5),
<preamble> (Section 3.6), <section> (Section 2.45), <strong>
(Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51), <t>
(Section 2.52), <table> (Section 2.53), <td> (Section 2.55), <th>
Hoffman Expires April 2, 2015 [Page 30]
Internet-Draft XML2RFCv3 September 2014
(Section 2.57), <tt> (Section 2.61), and <ttcol> (Section 3.9).
Content model: this element does not have any contents.
2.27.1. 'item' attribute (mandatory)
The item to include.
2.27.2. 'primary' attribute
Setting this to "true" declares the occurrence as "primary", which
might cause it to be highlighted in the index.
Allowed values:
o "true"
o "false" (default)
2.27.3. 'subitem' attribute
The subitem to include.
2.28. <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.
This element appears as a child element of: <front> (Section 2.25).
Content model: only text content.
2.29. <li>
A list element, used in <ol> and <ul>.
This element appears as a child element of: <ol> (Section 2.34), and
<ul> (Section 2.62).
Content model:
Either:
Hoffman Expires April 2, 2015 [Page 31]
Internet-Draft XML2RFCv3 September 2014
One or more <t> elements (Section 2.52)
Or:
In any order, but at least one of:
* Text
* <artwork> elements (Section 2.5)
* <b> elements (Section 2.8)
* <bcp14> elements (Section 2.10)
* <cref> elements (Section 2.15)
* <dl> elements (Section 2.19)
* <em> elements (Section 2.21)
* <eref> elements (Section 2.23)
* <figure> elements (Section 2.24)
* <i> elements (Section 2.26)
* <iref> elements (Section 2.27)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.47)
* <strong> elements (Section 2.49)
* <sub> elements (Section 2.50)
* <sup> elements (Section 2.51)
* <tt> elements (Section 2.61)
* <ul> elements (Section 2.62)
* <xref> elements (Section 2.65)
Hoffman Expires April 2, 2015 [Page 32]
Internet-Draft XML2RFCv3 September 2014
2.29.1. 'anchor' attribute
Document-wide unique identifier for this list item.
2.29.2. 'partNumber' attribute
The number for this list item within the section. The numbering is
shared with other elements of a section. This is described in more
detail in Appendix B.2.
2.30. <link>
A link to an external document that is related to the RFC.
The following are the supported types of external documents that can
be pointed to in a <link> element:
o The current ISSN for the RFC Series. The value for the "rel"
attribute is "isPartOf". The link should use the form
"urn:issn:".
o The DOI for this document. The value for the "rel" attribute is
"describedBy". The link should use the form "doi:".
o The Internet Draft that was submitted to the RFC Editor to become
the published RFC. The value for the "rel" attribute is
"convertedFrom". The link should be to an IETF-controlled web
site that retains copies of Internet Drafts.
o A representation of the document offered by the document author.
The value for the "rel" attribute is "alternate". The link can be
to a personally-run web site.
The RFC Processor needs to check the values for <link> before an RFC
is published. The Draft Processor might remove some <link> elements
during the draft submission process.
This element appears as a child element of: <rfc> (Section 2.44).
Content model: this element does not have any contents.
2.30.1. 'href' attribute (mandatory)
The URI of the external document.
Hoffman Expires April 2, 2015 [Page 33]
Internet-Draft XML2RFCv3 September 2014
2.30.2. 'rel' attribute
The relationship of the external document to this one. The
relationships are taken from Link Relations registry maintained by
IANA [LINKRELATIONS].
2.31. <middle>
Represents the main content of the document.
This element appears as a child element of: <rfc> (Section 2.44).
Content model:
One or more <section> elements (Section 2.45)
2.32. <name>
The name of the section, note, figure, or texttable. This name can
have flow markup such as to make some characters use a fixed-width
font, or to include references.
This element appears as a child element of: <figure> (Section 2.24),
<note> (Section 2.33), <section> (Section 2.45), <table>
(Section 2.53), and <texttable> (Section 3.8).
Content model:
In any order:
o Text
o <cref> elements (Section 2.15)
o <eref> elements (Section 2.23)
o <iref> elements (Section 2.27)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.32.1. 'slugifiedName' attribute
This attribute is filled in by a processor with a "slugified" version
of the text in the element. This attribute can be used in the output
formats for elements that have both names and numbers.
Hoffman Expires April 2, 2015 [Page 34]
Internet-Draft XML2RFCv3 September 2014
2.33. <note>
Creates an unnumbered section 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 appears as a child element of: <front> (Section 2.25).
Content model:
In this order:
1. One optional <name> element (Section 2.32)
2. One or more <t> elements (Section 2.52)
2.33.1. 'title' attribute
Deprecated. Use <name> instead.
2.34. <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 appears as a child element of: <dd> (Section 2.17), <li>
(Section 2.29), <section> (Section 2.45), <t> (Section 2.52), <td>
(Section 2.55), and <th> (Section 2.57).
Content model:
One or more <li> elements (Section 2.29)
2.34.1. 'group' attribute
When a processor sees an <ol> element with a "group" attribute that
has already been seen, the processor 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" and "start" attribute, the
group's numbering is reset to the given start value.
2.34.2. 'spacing' attribute
Defines whether or not there is a blank line between entries.
spacing="normal" indicates a single blank line, while
spacing="compact" indicates no space between.
Hoffman Expires April 2, 2015 [Page 35]
Internet-Draft XML2RFCv3 September 2014
Allowed values:
o "normal" (default)
o "compact"
2.34.3. 'start' attribute
The ordinal value to start the list at. This defaults to "1", and
must be an integer of 0 or greater.
2.34.4. 'style' attribute
The style of the labels on list items. If the length of the style
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 style "a" and "A", after the 26th entry, the numbering starts at
"aa"/"AA", then "ab"/"AB", and so on.
If the length of the style 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 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, ...)
Hoffman Expires April 2, 2015 [Page 36]
Internet-Draft XML2RFCv3 September 2014
%I Uppercase Roman numerals (I, II, III, ...)
%% Represents a percent sign
Other formats are reserved for future use.
It is an error for the style string to be empty, and processors will
reject documents with an element that has such a style. If the
intention is to have a list that is indented without bullets or
numbers, use <ul> with the 'empty="true"' attribute instead.
2.35. <organization>
Specifies the affiliation of an author.
This information appears in both 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 appears as a child element of: <author> (Section 2.7).
Content model: only text content.
2.35.1. 'abbrev' attribute
Abbreviated variant.
2.35.2. 'ascii' attribute
The ASCII equivalent of the organization's name.
2.36. <phone>
Represents a phone number.
The value is expected to be the scheme-specific part of a "tel" URI
(so does not include the prefix "tel:"), using the "global numbers"
syntax. See Section 3 of [RFC3966] for details.
This element appears as a child element of: <address> (Section 2.2).
Content model: only text content.
2.37. <postal>
Contains optional child elements providing postal information. These
elements will be displayed in an order that is processor-specific. A
Hoffman Expires April 2, 2015 [Page 37]
Internet-Draft XML2RFCv3 September 2014
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 appears as a child element of: <address> (Section 2.2).
Content model:
Either:
In any order:
* <city> elements (Section 2.12)
* <code> elements (Section 2.13)
* <country> elements (Section 2.14)
* <region> elements (Section 2.43)
* <street> elements (Section 2.48)
Or:
One or more <postalLine> elements (Section 2.38)
2.37.1. 'xml:lang' attribute
Allows specification of the language used. This is sometimes useful
for renderers which display different fonts for CJK characters.
2.38. <postalLine>
Represents one line of a postal address. When more than one
<postalLine> is given, the processor emits them in the order given.
This element appears as a child element of: <postal> (Section 2.37).
Content model: only text content.
2.38.1. 'ascii' attribute
The ASCII equivalent of the text in the address line.
2.39. <refcontent>
Text that should appear between the title and the date of a
reference. The purpose of this element is to prevent the need to
Hoffman Expires April 2, 2015 [Page 38]
Internet-Draft XML2RFCv3 September 2014
abuse <seriesInfo> to get such text in a reference.
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 appears as a child element of: <reference>
(Section 2.40).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <em> elements (Section 2.21)
o <i> elements (Section 2.26)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
2.39.1. 'ascii' attribute
The ASCII equivalent of the added text.
Hoffman Expires April 2, 2015 [Page 39]
Internet-Draft XML2RFCv3 September 2014
2.40. <reference>
Represents a bibliographical reference.
This element appears as a child element of: <referencegroup>
(Section 2.41), and <references> (Section 2.42).
Content model:
In this order:
1. One <front> element (Section 2.25)
2. In any order:
* <annotation> elements (Section 2.3)
* <format> elements (Section 3.3)
* <refcontent> elements (Section 2.39)
* <seriesInfo> elements (Section 2.46)
2.40.1. 'anchor' attribute (mandatory)
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.
2.40.2. 'target' attribute
Holds the URI for the reference.
Note that depending on the <seriesInfo> element, a URI might not be
needed, nor desirable, as it can be automatically generated (for
instance, for RFCs).
2.41. <referencegroup>
Represents a list of bibliographic references that will be
represented as a single reference. This is most often used for
references in the STD and BCP series, where a single reference (such
as "BCP 9") encompasses more than one RFC.
Content model:
One or more <reference> elements (Section 2.40)
Hoffman Expires April 2, 2015 [Page 40]
Internet-Draft XML2RFCv3 September 2014
2.41.1. 'anchor' attribute (mandatory)
Document-wide unique identifier for this reference group. 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.
2.42. <references>
Contains a set of bibliographical 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 "title"
attribute.
By default, the order of references is significant. Processors,
however, can be instructed to sort them based on their anchor names.
This element appears as a child element of: <back> (Section 2.9).
Content model:
One or more <reference> elements (Section 2.40)
2.42.1. 'title' attribute
Provides the title for the References section (defaulting to
"References").
In general, the title should be either "Normative References" or
"Informative References".
2.43. <region>
Provides the region name in a postal address.
This element appears as a child element of: <postal> (Section 2.37).
Content model: only text content.
2.43.1. 'ascii' attribute
The ASCII equivalent of the region name.
Hoffman Expires April 2, 2015 [Page 41]
Internet-Draft XML2RFCv3 September 2014
2.44. <rfc>
This is the root element of the xml2rfc vocabulary.
Processors distinguish between RFC mode ("number" attribute being
present) and Internet-Draft mode ("docName" attribute being present):
it is invalid to specify both. Setting neither "number" nor
"docName" can be useful for producing other types of document but is
out-of-scope for this specification.
Content model:
In this order:
1. One optional <link> element (Section 2.30)
2. One <front> element (Section 2.25)
3. One <middle> element (Section 2.31)
4. One optional <back> element (Section 2.9)
2.44.1. 'boilerplateText' attribute
The full boilerplate text for this document. This attribute and its
value are automatically generated by the RFC Processor, and are
ignored by other processors. If the value already exists when the
RFC Processor is run, it is replaced.
2.44.2. 'category' attribute
Document category (see Appendix A.1).
Allowed values:
o "std"
o "bcp"
o "info"
o "exp"
o "historic"
Hoffman Expires April 2, 2015 [Page 42]
Internet-Draft XML2RFCv3 September 2014
2.44.3. 'consensus' attribute
Affects the generated boilerplate.
See [RFC5741] for more information.
Allowed values:
o "no"
o "yes"
2.44.4. 'docName' attribute
Specifies the name or the Internet Draft or private document. A
private document is one whose representation is not meant to be an
Internet Draft or RFC. If the value for this attribute starts with
the string "draft-", a processor treats the input as an Internet
Draft; if the value starts with any other string, a processor treats
this as a private document. The name in the value should be the
document name without any file extension. That is, the value for
this attribute should be "draft-ietf-somewg-someprotocol-07", not
"draft-ietf-somewg-someprotocol-07.txt".
A processor should give an error if both the "docName" and "number"
attributes are given in the <rfc> element.
2.44.5. 'ipr' attribute
Represents the Intellectual Property status of the document. See
Appendix A.2 for details.
Allowed values:
o "full2026"
o "noDerivativeWorks2026"
o "none"
o "full3667"
o "noModification3667"
o "noDerivatives3667"
o "full3978"
Hoffman Expires April 2, 2015 [Page 43]
Internet-Draft XML2RFCv3 September 2014
o "noModification3978"
o "noDerivatives3978"
o "trust200811"
o "noModificationTrust200811"
o "noDerivativesTrust200811"
o "trust200902"
o "noModificationTrust200902"
o "noDerivativesTrust200902"
o "pre5378Trust200902"
2.44.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" attribute).
2.44.7. 'number' attribute
The number of the RFC to be produced by a processor.
A processor should give an error if both the "docName" and "number"
attributes are given in the <rfc> element.
2.44.8. 'obsoletes' attribute
A comma-separated list of RFC numbers or Internet-Draft names.
Processors ought to parse the attribute value, so that incorrect
references can be detected and, depending on output representation,
hyperlinks can be generated. Also, the value ought to be reformatted
to insert whitespace after each comma if not already present.
2.44.9. 'seriesNo' attribute
When producing a document within document series (such as "STD"): the
number within that series.
Hoffman Expires April 2, 2015 [Page 44]
Internet-Draft XML2RFCv3 September 2014
2.44.10. 'sortRefs' attribute
Specifies whether or not a processor will sort the references in each
reference section.
Allowed values:
o "yes"
o "no" (default)
2.44.11. 'submissionType' attribute
The document stream.
See Section 2 of [RFC5741] for details.
Allowed values:
o "IETF" (default)
o "IAB"
o "IRTF"
o "independent"
2.44.12. 'symRefs' attribute
Specifies whether or not a processor will use symbolic references
(such as "[RFC2119]"). If the value for this is "no", the references
come out as numbers (such as "[3]").
Allowed values:
o "yes" (default)
o "no"
2.44.13. 'tocDepth' attribute
Specifies number of levels of heading for a processor to include in
the table of contents; the default is "3".
2.44.14. 'tocInclude' attribute
Specifies whether or not a processor will include a table of contents
in generated files.
Hoffman Expires April 2, 2015 [Page 45]
Internet-Draft XML2RFCv3 September 2014
Allowed values:
o "yes" (default)
o "no"
2.44.15. 'updates' attribute
A comma-separated list of RFC numbers or Internet-Draft names.
Processors ought to parse the attribute value, so that incorrect
references can be detected and, depending on output representation,
hyperlinks can be generated. Also, the value ought to be reformatted
to insert whitespace after each comma if not already present.
2.44.16. 'xml:lang' attribute
The natural language used in the document (defaults to "en").
See Section 2.12 of [XML] for more information.
2.45. <section>
Represents a section (when inside a <middle> element) or an appendix
(when inside a <back> element).
Sub-sections are created by nesting <section> elements inside
<section> elements. Sections are allowed to be empty.
This element appears as a child element of: <back> (Section 2.9),
<middle> (Section 2.31), and <section> (Section 2.45).
Content model:
In this order:
1. One optional <name> element (Section 2.32)
2. In any order:
* <artwork> elements (Section 2.5)
* <aside> elements (Section 2.6)
* <blockquote> elements (Section 2.11)
* <dl> elements (Section 2.19)
Hoffman Expires April 2, 2015 [Page 46]
Internet-Draft XML2RFCv3 September 2014
* <figure> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.47)
* <t> elements (Section 2.52)
* <table> elements (Section 2.53)
* <texttable> elements (Section 3.8)
* <ul> elements (Section 2.62)
3. Optional <section> elements (Section 2.45)
2.45.1. 'anchor' attribute
Document-wide unique identifier for this section.
2.45.2. 'numbered' attribute
If set to "no", this section does not get a section number.
Processors will verify that such a section is not followed by a
numbered section in a part, and will verify that the section is a
top-level section.
Allowed values:
o "yes" (default)
o "no"
2.45.3. 'removeInRFC' attribute
If set to "yes", this section is marked in the processor with text
indicating that it should be removed before the document is published
as an RFC.
Allowed values:
o "yes"
o "no" (default)
Hoffman Expires April 2, 2015 [Page 47]
Internet-Draft XML2RFCv3 September 2014
2.45.4. 'sectionNumber' attribute
The number for this section, if one is generated by the processor.
This attribute and its value are automatically generated by the RFC
Processor, and are ignored by other processors. If the value already
exists when the RFC Processor is run, it is replaced.
2.45.5. 'title' attribute
Deprecated. Use <name> instead.
2.45.6. 'toc' attribute
Indicates to a processor whether or not the section is to be included
in the table of contents. 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 to include the section if it would be included by the
tocDepth attribute of the <rfc> element.
Allowed values:
o "include"
o "exclude"
o "default" (default)
2.46. <seriesInfo>
Specifies the document series in which this document appears, and
also specifies an identifier within that series.
This element appears as a child element of: <reference>
(Section 2.40).
Content model: this element does not have any contents.
2.46.1. 'asciiname' attribute
The ASCII equivalent of the name field.
Hoffman Expires April 2, 2015 [Page 48]
Internet-Draft XML2RFCv3 September 2014
2.46.2. 'asciivalue' attribute
The ASCII equivalent of the value field.
2.46.3. 'name' attribute (mandatory)
The name of the series.
The following names trigger specific processing (such as for auto-
generating links, and adding descriptions such as "work in
progress"): "BCP", "FYI", "Internet-Draft", "RFC", and "STD".
2.46.4. 'value' attribute (mandatory)
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).
2.47. <sourcecode>
This element allows the inclusion of sourcecode into the document.
<sourcecode> provides full control of horizontal whitespace and line
breaks. It is thus useful for source code and formal languages (such
as ABNF or the RNC notation used in this document).
For artwork such as character-based art, diagrams of message layouts,
and so on, use the <artwork> element instead.
A common problem authors have with <sourcecode> is that the XML
processor returns errors if the text in the artwork contains either
the "&" or "<" character, or the string "]]>". To avoid these
problems, the "&" and "<" characters may be escaped using the strings
"&" and "<", respectively; the "]]>" string can be represented
as "]]>". Alternatively, they may be surrounded in a CDATA
structure: "<![CDATA[]]>". For example:
Hoffman Expires April 2, 2015 [Page 49]
Internet-Draft XML2RFCv3 September 2014
Desired output:
allowed-chars = "." | "," | "&" | "<" | ">" | "|"
Using escaping:
<sourcecode>
allowed-chars = "." | "," | "&" | "<" | ">" | "|"
</sourcecode>
Using CDATA:
<sourcecode>
<![CDATA[ allowed-chars = "." | "," | "&" | "<" | ">" | "|"]]>
</sourcecode>
Using CDATA is not a panacea, but it does help prevent having to use
escapes in places where using using escapes can cause other problems,
such as difficulty of inclusion from other documents.
This element appears as a child element of: <aside> (Section 2.6),
<blockquote> (Section 2.11), <dd> (Section 2.17), <figure>
(Section 2.24), <li> (Section 2.29), <section> (Section 2.45), <td>
(Section 2.55), and <th> (Section 2.57).
Content model: only text content.
2.47.1. 'anchor' attribute
Document-wide unique identifier for this sourcecode.
2.47.2. 'name' attribute
A filename suitable for the contents (such as for extraction to a
local file). This attribute generally isn't used for document
generation, but it can be helpful for other kinds of tools (such as
automated syntax checkers which work by extracting the source code).
2.47.3. 'partNumber' attribute
The number for this sourceode within the section. The numbering is
shared with other elements of a section. This is described in more
detail in Appendix B.2.
2.47.4. 'type' attribute
Specifies the type of the sourcecode. The value of this attribute is
free text with certain values designated as preferred. A private
processor (as described in Appendix B) might add type-specific
formatting to sourcecode with the preferred values. If a processor
encounters a value for "type" that is not one of the preferred
Hoffman Expires April 2, 2015 [Page 50]
Internet-Draft XML2RFCv3 September 2014
values, it can issue a warning but should still use the artwork as if
it had no "type" attribute.
The preferred values for <sourcecode> types are:
o abnf
o asn.1
o bash
o c++
o c
o cbor
o dtd
o java
o javascript
o json
o mib
o perl
o pseudocode
o python
o rnc
o xml
The RFC Editor will maintain a complete list of the preferred values
on its 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.
2.48. <street>
Provides a street address.
This element appears as a child element of: <postal> (Section 2.37).
Hoffman Expires April 2, 2015 [Page 51]
Internet-Draft XML2RFCv3 September 2014
Content model: only text content.
2.48.1. 'ascii' attribute
The ASCII equivalent of the street address.
2.49. <strong>
Indicates text that is semantically strong. This element will be
displayed as bold after processing. This element has the same
effects as <b>. This element can be combined with other character
formatting elements, and the formatting will be additive.
This element appears as a child element of: <annotation>
(Section 2.3), <blockquote> (Section 2.11), <c> (Section 3.1), <cref>
(Section 2.15), <dd> (Section 2.17), <dt> (Section 2.20), <em>
(Section 2.21), <i> (Section 2.26), <li> (Section 2.29), <postamble>
(Section 3.5), <preamble> (Section 3.6), <refcontent> (Section 2.39),
<sub> (Section 2.50), <sup> (Section 2.51), <t> (Section 2.52), <td>
(Section 2.55), <th> (Section 2.57), and <tt> (Section 2.61).
Content model:
In any order:
o Text
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
Hoffman Expires April 2, 2015 [Page 52]
Internet-Draft XML2RFCv3 September 2014
2.50. <sub>
Causes the text to be displayed as subscript, approximately half a
letter-height lower than normal text. This element can be combined
with other character formatting elements, and the formatting will be
additive.
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <blockquote> (Section 2.11), <c>
(Section 3.1), <cref> (Section 2.15), <dd> (Section 2.17), <dt>
(Section 2.20), <em> (Section 2.21), <i> (Section 2.26), <li>
(Section 2.29), <postamble> (Section 3.5), <preamble> (Section 3.6),
<refcontent> (Section 2.39), <strong> (Section 2.49), <t>
(Section 2.52), <td> (Section 2.55), <th> (Section 2.57), and <tt>
(Section 2.61).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <strong> elements (Section 2.49)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.51. <sup>
Causes the text to be displayed as superscript, approximately half a
letter-height higher than normal text. This element can be combined
with other character formatting elements, and the formatting will be
additive.
Hoffman Expires April 2, 2015 [Page 53]
Internet-Draft XML2RFCv3 September 2014
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <blockquote> (Section 2.11), <c>
(Section 3.1), <cref> (Section 2.15), <dd> (Section 2.17), <dt>
(Section 2.20), <em> (Section 2.21), <i> (Section 2.26), <li>
(Section 2.29), <postamble> (Section 3.5), <preamble> (Section 3.6),
<refcontent> (Section 2.39), <strong> (Section 2.49), <t>
(Section 2.52), <td> (Section 2.55), <th> (Section 2.57), and <tt>
(Section 2.61).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <strong> elements (Section 2.49)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
2.52. <t>
Contains a paragraph of text.
This element appears as a child element of: <abstract> (Section 2.1),
<aside> (Section 2.6), <dd> (Section 2.17), <li> (Section 2.29),
<list> (Section 3.4), <note> (Section 2.33), <section>
(Section 2.45), <td> (Section 2.55), and <th> (Section 2.57).
Content model:
In any order:
Hoffman Expires April 2, 2015 [Page 54]
Internet-Draft XML2RFCv3 September 2014
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <list> elements (Section 3.4)
o <ol> elements (Section 2.34)
o <spanx> elements (Section 3.7)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <vspace> elements (Section 3.10)
o <xref> elements (Section 2.65)
2.52.1. 'anchor' attribute
Document-wide unique identifier for this paragraph.
2.52.2. 'hangText' attribute
Deprecated. Instead use <dd> inside of a definition list (<dl>).
2.52.3. 'partNumber' attribute
The number for this paragraph within the section. The numbering is
shared with other elements of a section. This is described in more
detail in Appendix B.2.
Hoffman Expires April 2, 2015 [Page 55]
Internet-Draft XML2RFCv3 September 2014
2.53. <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.
Insde the <table> element is optionlly 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 appears as a child element of: <section> (Section 2.45).
Content model:
In this order:
1. One optional <name> element (Section 2.32)
2. Optional <iref> elements (Section 2.27)
3. One optional <thead> element (Section 2.58)
4. One or more <tbody> elements (Section 2.54)
5. One optional <tfoot> element (Section 2.56)
2.53.1. 'anchor' attribute
Document-wide unique identifier for this table.
2.53.2. 'tableNumber' attribute
The number for this table. This attribute and its value are
automatically generated by the RFC Processor. If the value already
exists when the RFC Processor is run, it is replaced.
2.54. <tbody>
A container for a set of body rows for a table.
This element appears as a child element of: <table> (Section 2.53).
Content model:
One or more <tr> elements (Section 2.60)
Hoffman Expires April 2, 2015 [Page 56]
Internet-Draft XML2RFCv3 September 2014
2.55. <td>
A cell in a table row.
This element appears as a child element of: <tr> (Section 2.60).
Content model:
Either:
One or more <t> elements (Section 2.52)
Or:
In any order, but at least one of:
* Text
* <artwork> elements (Section 2.5)
* <b> elements (Section 2.8)
* <bcp14> elements (Section 2.10)
* <cref> elements (Section 2.15)
* <dl> elements (Section 2.19)
* <em> elements (Section 2.21)
* <eref> elements (Section 2.23)
* <figure> elements (Section 2.24)
* <i> elements (Section 2.26)
* <iref> elements (Section 2.27)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.47)
* <strong> elements (Section 2.49)
* <sub> elements (Section 2.50)
* <sup> elements (Section 2.51)
Hoffman Expires April 2, 2015 [Page 57]
Internet-Draft XML2RFCv3 September 2014
* <tt> elements (Section 2.61)
* <ul> elements (Section 2.62)
* <xref> elements (Section 2.65)
2.55.1. 'border' attribute
The width of the border for this cell. The default is 0, meaning no
border.
2.55.2. 'colspan' attribute
The number of columns that the cell to span. For example, setting
"colspan='3'" indicates that the cell occupies the same horizontal
space as three cells in the row above or below this one.
2.55.3. 'rowspan' attribute
The number of rows that the cell to span. For example, setting
"rowspan='3'" indicates that the cell occupies the same vertical
space as three rows.
2.56. <tfoot>
A container for a set of footer rows for a table.
This element appears as a child element of: <table> (Section 2.53).
Content model:
One or more <tr> elements (Section 2.60)
2.57. <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 appears as a child element of: <tr> (Section 2.60).
Content model:
Either:
One or more <t> elements (Section 2.52)
Or:
Hoffman Expires April 2, 2015 [Page 58]
Internet-Draft XML2RFCv3 September 2014
In any order, but at least one of:
* Text
* <artwork> elements (Section 2.5)
* <b> elements (Section 2.8)
* <bcp14> elements (Section 2.10)
* <cref> elements (Section 2.15)
* <dl> elements (Section 2.19)
* <em> elements (Section 2.21)
* <eref> elements (Section 2.23)
* <figure> elements (Section 2.24)
* <i> elements (Section 2.26)
* <iref> elements (Section 2.27)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.47)
* <strong> elements (Section 2.49)
* <sub> elements (Section 2.50)
* <sup> elements (Section 2.51)
* <tt> elements (Section 2.61)
* <ul> elements (Section 2.62)
* <xref> elements (Section 2.65)
2.57.1. 'border' attribute
The width of the border for this cell. The default is 0, meaning no
border.
Hoffman Expires April 2, 2015 [Page 59]
Internet-Draft XML2RFCv3 September 2014
2.57.2. 'colspan' attribute
The number of columns that the cell to span. For example, setting
"colspan='3'" indicates that the cell occupies the same horizontal
space as three cells in the row above or below this one.
2.57.3. 'rowspan' attribute
The number of rows that the cell to span. For example, setting
"rowspan='3'" indicates that the cell occupies the same vertical
space as three rows.
2.58. <thead>
A container for a set of header rows for a table.
This element appears as a child element of: <table> (Section 2.53).
Content model:
One or more <tr> elements (Section 2.60)
2.59. <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 is used to
specify an abbreviated variant.
This element appears as a child element of: <front> (Section 2.25).
Content model: only text content.
2.59.1. 'abbrev' attribute
Specifies an abbreviated variant of the document title.
2.59.2. 'ascii' attribute
The ASCII equivalent of the title.
2.60. <tr>
A row of a table.
This element appears as a child element of: <tbody> (Section 2.54),
Hoffman Expires April 2, 2015 [Page 60]
Internet-Draft XML2RFCv3 September 2014
<tfoot> (Section 2.56), and <thead> (Section 2.58).
Content model:
One or more sequences of:
1. One <td> element
2. One <th> element
2.60.1. 'border' attribute
The width of the border for this row. The default is 0, meaning no
border. If the cells in this row also have "border" attributes,
those values override this value for those cells.
2.61. <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 appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <blockquote> (Section 2.11), <c>
(Section 3.1), <cref> (Section 2.15), <dd> (Section 2.17), <dt>
(Section 2.20), <em> (Section 2.21), <i> (Section 2.26), <li>
(Section 2.29), <name> (Section 2.32), <postamble> (Section 3.5),
<preamble> (Section 3.6), <refcontent> (Section 2.39), <strong>
(Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51), <t>
(Section 2.52), <td> (Section 2.55), and <th> (Section 2.57).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
Hoffman Expires April 2, 2015 [Page 61]
Internet-Draft XML2RFCv3 September 2014
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <xref> elements (Section 2.65)
2.62. <ul>
An unordered list. The labels on the items will be symbols picked by
the processor.
This element appears as a child element of: <dd> (Section 2.17), <li>
(Section 2.29), <section> (Section 2.45), <td> (Section 2.55), and
<th> (Section 2.57).
Content model:
One or more <li> elements (Section 2.29)
2.62.1. 'empty' attribute
Defines whether or not the label is empty. empty="true" indicates
that no label be shown.
Allowed values:
o "false" (default)
o "true"
2.62.2. 'spacing' attribute
Defines whether or not there is a blank line between entries.
spacing="normal" indicates a single blank line, while
spacing="compact" indicates no space between.
Allowed values:
o "normal" (default)
o "compact"
Hoffman Expires April 2, 2015 [Page 62]
Internet-Draft XML2RFCv3 September 2014
2.63. <uri>
Contains a web address associated with the author.
The contents should be a valid URI (see Section 3 of [RFC3986]).
This element appears as a child element of: <address> (Section 2.2).
Content model: only text content.
2.64. <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 on the <rfc>
element (Section 2.44.11).
This element appears as a child element of: <front> (Section 2.25).
Content model: only text content.
2.65. <xref>
Inserts a reference to a different part of a document.
The generated text depends on whether the <xref> is empty (in which
case the processor will try to generate a meaningful text fragment),
and the nature of the referenced document part. [[anchor6: Need to
say more about the processor output if the element is empty and if it
has text.]]
Any element that allows the "anchor" attribute can be referenced;
however, there are restrictions with respect to the text content
being generated. For instance, a <t> can be a reference target,
however, because paragraphs are not (visibly) numbered, the author
will have to make sure that the prose is sufficient for a reader to
understand what is being referred to.
This element appears as a child element of: <annotation>
(Section 2.3), <b> (Section 2.8), <c> (Section 3.1), <cref>
(Section 2.15), <dd> (Section 2.17), <dt> (Section 2.20), <em>
(Section 2.21), <i> (Section 2.26), <li> (Section 2.29), <name>
Hoffman Expires April 2, 2015 [Page 63]
Internet-Draft XML2RFCv3 September 2014
(Section 2.32), <postamble> (Section 3.5), <preamble> (Section 3.6),
<strong> (Section 2.49), <sub> (Section 2.50), <sup> (Section 2.51),
<t> (Section 2.52), <td> (Section 2.55), <th> (Section 2.57), <tt>
(Section 2.61), and <ttcol> (Section 3.9).
Content model: only text content.
2.65.1. 'format' attribute
This attribute is used to control the format of the generated
reference text.
"counter"
Inserts just a counter; this is used for the number of a section,
figure, or table. For example:
<section anchor="overview">Protocol Overview</section>
. . .
See Section <xref target="overview" format="counter"/>
for an overview.
might generate
See Section 1.7 for an overview.
"default"
Inserts a text fragment that describes the referenced part
completely, such as "Section 2" or "Table 4" for internal links,
or "[XML]" for links to references. For example:
<section anchor="overview">Protocol Overview</section>
. . .
See <xref target="overview"/> for an overview.
might generate
See Section 1.7 for an overview.
"none"
There will be no auto-generated text. This is useful for creating
a link that will appear in the processed text.
"title"
Hoffman Expires April 2, 2015 [Page 64]
Internet-Draft XML2RFCv3 September 2014
Inserts a title for the referenced element (usually obtained from
the referenced element's "title" attribute; some processors also
use the <title> child element or a <reference> target).
Allowed values:
o "counter"
o "title"
o "none"
o "default" (default)
2.65.2. 'pageno' attribute
Deprecated.
Allowed values:
o "true"
o "false" (default)
2.65.3. 'relative' attribute
Specifies a relative reference from the main target. [[anchor7: Need
more description here about how this will be rendered by a
processor.]]
2.65.4. 'section' attribute
Specifies a section for the generated reference. For example,
See <xref section="2.3" target="RFC6949"/> for more information.
would generate
See Section 2.3 of [RFC6949] for more information.
2.65.5. 'sectionFormat' attribute
The format that the section reference will be displayed in. The
acceptable values are:
o "of" (default)
Hoffman Expires April 2, 2015 [Page 65]
Internet-Draft XML2RFCv3 September 2014
o "comma"
o "parens"
For example:
See <xref target="RFC6949" section="2.3" sectionFormat="of"/>
for more information.
See <xref target="RFC6949" section="2.4" sectionFormat="comma"/>
for more information.
See <xref target="RFC6949" section="2.5" sectionFormat="parens"/>
for more information.
would generate
See Section 2.3 of [RFC6949] for more information.
See [RFC6949], Section 2.4 for more information.
See [RFC6949] (Section 2.5) for more information.
2.65.6. 'target' attribute (mandatory)
Identifies the document component being referenced.
The value needs to match the value of the "anchor" attribute of
another element in the document.
3. Elements from v2 That Have Been Deprecated
This section lists the elements from v2 that have been deprecated.
Note that some elements in v3 have attributes from v2 that are
deprecated; those are not listed here.
3.1. <c>
Deprecated. Instead, use <tr>, <td>, and <th>.
This element appears as a child element of: <texttable>
(Section 3.8).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
Hoffman Expires April 2, 2015 [Page 66]
Internet-Draft XML2RFCv3 September 2014
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <spanx> elements (Section 3.7)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
3.2. <facsimile>
Deprecated. The <email> element is a much more useful way to get in
touch with authors.
This element appears as a child element of: <address> (Section 2.2).
Content model: only text content.
3.3. <format>
Deprecated. If the goal is to provide a single URI for a reference,
use the "target" attribute on <reference> instead.
This element appears as a child element of: <reference>
(Section 2.40).
Content model: this element does not have any contents.
3.3.1. 'octets' attribute
Deprecated.
Hoffman Expires April 2, 2015 [Page 67]
Internet-Draft XML2RFCv3 September 2014
3.3.2. 'target' attribute
Deprecated.
3.3.3. 'type' attribute (mandatory)
Deprecated.
3.4. <list>
Deprecated. Instead, use <dl> for list/@style "hanging"; <ul> for
list/@style "empty" or "symbols"; and <ol> for list/@style "letters",
"numbers", "counter", or "format".
This element appears as a child element of: <t> (Section 2.52).
Content model:
One or more <t> elements (Section 2.52)
3.4.1. 'counter' attribute
Deprecated. The functionality of this attribute has been replaced
with <ol>/@start.
3.4.2. 'hangIndent' attribute
Deprecated. Use <dl> instead.
3.4.3. 'style' attribute
Deprecated.
3.5. <postamble>
Deprecated. Instead, use a regular paragraph after the figure or
table.
This element appears as a child element of: <figure> (Section 2.24),
and <texttable> (Section 3.8).
Content model:
In any order:
o Text
Hoffman Expires April 2, 2015 [Page 68]
Internet-Draft XML2RFCv3 September 2014
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <spanx> elements (Section 3.7)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
3.6. <preamble>
Deprecated. Instead, use a regular paragraph before the figure or
table.
This element appears as a child element of: <figure> (Section 2.24),
and <texttable> (Section 3.8).
Content model:
In any order:
o Text
o <b> elements (Section 2.8)
o <bcp14> elements (Section 2.10)
o <cref> elements (Section 2.15)
o <em> elements (Section 2.21)
Hoffman Expires April 2, 2015 [Page 69]
Internet-Draft XML2RFCv3 September 2014
o <eref> elements (Section 2.23)
o <i> elements (Section 2.26)
o <iref> elements (Section 2.27)
o <spanx> elements (Section 3.7)
o <strong> elements (Section 2.49)
o <sub> elements (Section 2.50)
o <sup> elements (Section 2.51)
o <tt> elements (Section 2.61)
o <xref> elements (Section 2.65)
3.7. <spanx>
Deprecated.
This element appears as a child element of: <annotation>
(Section 2.3), <c> (Section 3.1), <postamble> (Section 3.5),
<preamble> (Section 3.6), and <t> (Section 2.52).
Content model: only text content.
3.7.1. 'style' attribute
Deprecated. Instead of <spanx style="emph">, use <b> instead of
<spanx style="strong">, use <i>; instead of <spanx style="verg">, use
<tt>.
3.7.2. 'xml:space' attribute
Deprecated.
Allowed values:
o "default"
o "preserve" (default)
Hoffman Expires April 2, 2015 [Page 70]
Internet-Draft XML2RFCv3 September 2014
3.8. <texttable>
Deprecated. Use <table> instead.
This element appears as a child element of: <aside> (Section 2.6),
and <section> (Section 2.45).
Content model:
In this order:
1. One optional <name> element (Section 2.32)
2. One optional <preamble> element (Section 3.6)
3. One or more <ttcol> elements (Section 3.9)
4. Optional <c> elements (Section 3.1)
5. One optional <postamble> element (Section 3.5)
3.8.1. 'align' attribute
Deprecated
Allowed values:
o "left"
o "center" (default)
o "right"
3.8.2. 'anchor' attribute
Deprecated
3.8.3. 'style' attribute
Deprecated.
3.8.4. 'suppress-title' attribute
Deprecated.
Allowed values:
Hoffman Expires April 2, 2015 [Page 71]
Internet-Draft XML2RFCv3 September 2014
o "true"
o "false" (default)
3.8.5. 'title' attribute
Deprecated.
3.9. <ttcol>
Deprecated. Instead, use <tr>, <td>, and <th>.
This element appears as a child element of: <texttable>
(Section 3.8).
Content model:
In any order:
o <cref> elements (Section 2.15)
o <eref> elements (Section 2.23)
o <iref> elements (Section 2.27)
o <xref> elements (Section 2.65)
o Text
3.9.1. 'align' attribute
Deprecated.
Allowed values:
o "left" (default)
o "center"
o "right"
3.9.2. 'width' attribute
Deprecated.
Hoffman Expires April 2, 2015 [Page 72]
Internet-Draft XML2RFCv3 September 2014
3.10. <vspace>
Deprecated. In earlier versions of this format, <vspace> was often
used to get an extra blank line in a list element; in the v3
vocabulary, that can be done instead by using multiple <t> elements
inside the <li> element. Other uses have no direct replacement.
This element appears as a child element of: <t> (Section 2.52).
Content model: this element does not have any contents.
3.10.1. 'blankLines' attribute
Deprecated.
4. Internationalization Considerations
This format is based on [XML], thus does not have any issues
representing arbitrary Unicode [UNICODE] characters in text content.
The RFC Editor may restrict some of the characters that can be used
in a particular RFC; the rules for such restrictions are covered in
[NONASCII].
5. Security Considerations
The "name" attribute on the <artwork> element (Section 2.5.5) can be
used to derive a filename for saving to a local file system.
Trusting this kind of information without pre-processing is a known
security risk; see Section 4.3 of [RFC6266] for more information.
The "type" attribute of the <artwork> and <sourcecode> elements is
meant to encourage processors to automatically extract known types of
content from an RFC or Internet Draft. While extraction is probably
safe, those processors might also think that they could further
process the extracted content such as by rendering artwork or
executing code. Doing so without first sanity-checking the extracted
content is clearly a terrible idea from a security perspective. More
generally, a processor that is reading RFCs or Internet Drafts needs
to be suspicious of any content that it intends to post-process.
All security considerations related to XML processing are relevant as
well (see Section 7 of [RFC3470]).
6. IANA Considerations
Hoffman Expires April 2, 2015 [Page 73]
Internet-Draft XML2RFCv3 September 2014
6.1. Internet Media Type Registration
IANA maintains the registry of Internet media types [BCP13] at
<http://www.iana.org/assignments/media-types>.
This document updates the specification for the Internet media type
"application/rfc+xml" from the one in [XML2RFCv2]. The following is
to be registered with IANA.
Type name: application
Subtype name: rfc+xml
Required parameters: There are no required parameters.
Optional parameters: "charset": This parameter has identical
semantics as the charset parameter of the "application/xml" media
type specified in Section 9.1 of [RFC7303].
Encoding considerations: Identical to those of "application/xml" as
described in Section 9.1 of [RFC7303].
Security considerations: As defined in Section 5. In addition, as
this media type uses the "+xml" convention, it inherits the
security considerations described in Section 10 of [RFC7303].
Interoperability considerations: N/A
Published specification: This specification.
Applications that use this media type: Applications that transform
xml2rfc to output representations such as plain text or HTML, plus
additional analysis tools.
Fragment identifier considerations: The "anchor" attribute is used
for assigning document-wide unique identifiers that can be used as
shorthand pointers, as described in Section 2.8 of [XPOINTER].
Additional information:
Deprecated alias names for this type: None.
Magic number(s): As specified for "application/xml" in Section
9.1 of [RFC7303].
Hoffman Expires April 2, 2015 [Page 74]
Internet-Draft XML2RFCv3 September 2014
File extension(s): .xml or .rfcxml when disambiguation from other
XML files is needed
Macintosh file type code(s): TEXT
Person & email address to contact for further information: See
Authors Section.
Intended usage: COMMON
Restrictions on usage: N/A
Author: See Authors Section.
Change controller: RFC Series Editor (rse@rfc-editor.org)
6.2. Link Relation Registration
The following is a proposed addition to [LINKRELATIONS].
Relation Name: convertedFrom
Description: The document linked to was later converted to the
document that contains this link relation. For example, an RFC can
have a link to the Internet Draft that became the RFC; in that case,
the link relation would be "convertedFrom".
Reference: This document.
Notes: This relation is different than "predecessor-version" in that
"predecessor-version" is for items in a version control system. It
is also different that "previous" in that this relation is used for
converted resources, not those that are part of a sequence of
resources.
Application Data: none
7. Acknowledgments
Thanks to everybody who reviewed this document and provided feedback
and/or specification text. Thanks especially go to Julian Reschke
for editing [XML2RFCv2] and those who provided feedback on that
document.
We also thank Marshall T. Rose for both the original design and the
reference implementation of the "xml2rfc" processor.
8. References
Hoffman Expires April 2, 2015 [Page 75]
Internet-Draft XML2RFCv3 September 2014
8.1. Normative References
[XML] Maler, E., Yergeau, F., Paoli, J., Sperberg-McQueen,
M., and T. Bray, "Extensible Markup Language (XML)
1.0 (Fifth Edition)", W3C Recommendation REC-xml-
20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126/>.
Latest version available at
<http://www.w3.org/TR/xml>.
[XML2RFCv2] Reschke, J., "The 'XML2RFC' version 2 Vocabulary",
draft-reschke-xml2rfc (work in progress), 2014.
8.2. Informative References
[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13,
RFC 6838, January 2013.
[IDGUIDE] Housley, R., "Guidelines to Authors of Internet-
Drafts",
<http://www.ietf.org/id-info/guidelines.html>.
[LINKRELATIONS] IANA, "Link Relations", <http://www.iana.org/
assignments/link-relations/link-relations.xhtml>.
[NONASCII] Flanagan, H., "The Use of Non-ASCII Characters in
RFCs", draft-flanagan-nonascii (work in progress),
2014.
[RFC2026] Bradner, S., "The Internet Standards Process --
Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397,
August 1998.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML",
RFC 2629, June 1999.
[RFC3470] Hollenbeck, S., Rose, M., and L. Masinter,
"Guidelines for the Use of Extensible Markup
Language (XML) within IETF Protocols", BCP 70,
RFC 3470, January 2003.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone
Numbers", RFC 3966, December 2004.
Hoffman Expires April 2, 2015 [Page 76]
Internet-Draft XML2RFCv3 September 2014
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,
"Uniform Resource Identifier (URI): Generic Syntax",
STD 66, RFC 3986, January 2005.
[RFC5741] Daigle, L. and O. Kolkman, "RFC Streams, Headers,
and Boilerplates", RFC 5741, December 2009.
[RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The
'mailto' URI Scheme", RFC 6068, October 2010.
[RFC6266] Reschke, J., "Use of the Content-Disposition Header
Field in the Hypertext Transfer Protocol (HTTP)",
RFC 6266, June 2011.
[RFC6949] Flanagan, H. and N. Brownlee, "RFC Series Format
Requirements and Future Development", RFC 6949,
May 2013.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types",
RFC 7303, July 2014.
[RFC7322] Heather, H. and S. Ginoza, "RFC Style Guide",
RFC 7322, September 2014.
[RFCPOLICY] RFC Editor, "RFC Editorial Guidelines and
Procedures",
<http://www.rfc-editor.org/policy.html>.
[RNC] Clark, J., "RELAX NG Compact Syntax", OASIS ,
November 2002, <http://www.oasis-open.org/
committees/relax-ng/compact-20021121.html>.
[RNG] ISO/IEC, "Information Technology - Document Schema
Definition Languages (DSDL) - Part 2: Regular-
Grammar-Based Validation - RELAX NG. Second
Edition.", ISO/IEC 19757-2:2008(E), December 2008.
A useful source of RNG-related information is
<http://relaxng.org/>.
[TLP2.0] IETF Trust, "Legal Provisions Relating to IETF
Documents", February 2009, <http://trustee.ietf.org/
license-info/IETF-TLP-2.htm>.
[TLP3.0] IETF Trust, "Legal Provisions Relating to IETF
Documents", September 2009, <http://
trustee.ietf.org/license-info/IETF-TLP-3.htm>.
Hoffman Expires April 2, 2015 [Page 77]
Internet-Draft XML2RFCv3 September 2014
[TLP4.0] IETF Trust, "Legal Provisions Relating to IETF
Documents", December 2009, <http://trustee.ietf.org/
license-info/IETF-TLP-4.htm>.
[UNICODE] The Unicode Consortium, "The Unicode Standard,
Version 6.3.0", September 2013,
<http://www.unicode.org/versions/Unicode6.3.0/>.
[XInclude] Marsh, J., Orchard, D., and D. Veillard, "XML
Inclusions (XInclude) Version 1.0 (Second Edition)",
W3C Recommendation REC-xinclude-20061115,
November 2006, <http://www.w3.org/TR/xinclude/>.
Latest version available at
<http://www.w3.org/TR/xinclude/>.
[XPOINTER] Grosso, P., Maler, E., Marsh, J., and N. Walsh,
"XPointer Framework", W3C Recommendation REC-xptr-
framework-20030325, March 2003, <http://www.w3.org/
TR/2003/REC-xptr-framework-20030325/>.
Latest version available at
<http://www.w3.org/TR/xptr-framework/>.
Appendix A. Front Page Generation
A.1. The /rfc/@category Attribute
For RFCs, the category 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, but will
appear on the front page as "Intended Status". Supplying this
information can be useful to reviewers.
A.2. The /rfc/@ipr Attribute
This attribute value can take a long list of values, each of which
describes an IPR policy for the document. This attribute's values
are not the result of a grand plan, but remain simply for historic
reasons. Of these values, only a few are currently in use; all
others are supported by the various tools for backwards compatibility
with old source files.
Hoffman Expires April 2, 2015 [Page 78]
Internet-Draft XML2RFCv3 September 2014
Note: some variations of the boilerplate are selected based on the
document's date; therefore it is important to specify the "year",
"month" and "day" attributes of the <date> element when archiving
the XML source of an Internet-Draft on the day of submission.
Disclaimer: THIS ONLY PROVIDES IMPLEMENTATION INFORMATION. IF YOU
NEED LEGAL ADVICE, PLEASE CONTACT A LAWYER. For further information,
refer to <http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf>.
For the current "Status Of This Memo" text, the submissionType
attribute determines whether a statement about "Code Components" is
inserted (which is the case for the value "IETF", which is the
default). Other values, such as "independent", suppress this part of
the text.
A.2.1. Current Values: '*trust200902'
The name for these values refers to the "IETF TRUST Legal Provisions
Relating to IETF Documents", sometimes simply called the "TLP, that
went into effect on February 15, 2009 ([TLP2.0]). Updates to this
document were published on September 12, 2009 ([TLP3.0]) and on
December 28, 2009 ([TLP4.0]), modifying the license for code
components (see <http://trustee.ietf.org/license-info/> for further
information). The actual text is located in Section 6 ("Text To Be
Included in IETF Documents") of these documents.
The tools will automatically produce the "correct" text depending on
the document's date information (see above):
+----------+--------------------------------+
| TLP | starting with publication date |
+----------+--------------------------------+
| [TLP3.0] | 2009-11-01 |
| [TLP4.0] | 2010-04-01 |
+----------+--------------------------------+
A.2.1.1. trust200902
This should be the default, unless one of the more specific
'*trust200902' values is a better fit. It produces the text in
Sections 6.a and 6.b of the TLP.
A.2.1.2. noModificationTrust200902
This produces additional text from Section 6.c.i of the TLP:
Hoffman Expires April 2, 2015 [Page 79]
Internet-Draft XML2RFCv3 September 2014
This document may not be modified, and derivative works of it may
not be created, except to format it for publication as an RFC or
to translate it into languages other than English.
Note: this clause is incompatible with RFCs that are published on
the Standards Track.
A.2.1.3. noDerivativesTrust200902
This produces the additional text from Section 6.c.ii of the TLP:
This document may not be modified, and derivative works of it may
not be created, and it may not be published except as an Internet-
Draft.
Note: this clause is incompatible with RFCs.
A.2.1.4. pre5378Trust200902
This produces the additional text from Section 6.c.iii of the TLP,
frequently called the "pre-5378 escape clause":
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s)
controlling the copyright in such materials, this document may not
be modified outside the IETF Standards Process, and derivative
works of it may not be created outside the IETF Standards Process,
except to format it for publication as an RFC or to translate it
into languages other than English.
See Section 4 of
<http://trustee.ietf.org/docs/IETF-Copyright-FAQ.pdf> for further
information about when to use this value.
Note: this text appears under "Copyright Notice", unless the
document was published before November 2009, in which case it
appears under "Status Of This Memo".
A.2.2. Historic Values
A.2.2.1. Historic Values: '*trust200811'
The attribute values "trust200811", "noModificationTrust200811" and
"noDerivativesTrust200811" are similar to their "trust200902"
Hoffman Expires April 2, 2015 [Page 80]
Internet-Draft XML2RFCv3 September 2014
counterparts, except that they use text specified in <http://
trustee.ietf.org/license-info/archive/
IETF-Trust-License-Policy_11-10-08.pdf>.
A.2.2.2. Historic Values: '*3978'
The attribute values "full3978", "noModification3978" and
"noDerivatives3978" are similar to their counterparts above, except
that they use text specified in RFC 3978 (March 2005).
A.2.2.3. Historic Values: '*3667'
The attribute values "full3667", "noModification3667" and
"noDerivatives3667" are similar to their counterparts above, except
that they use text specified in RFC 3667 (February 2004).
A.2.2.4. Historic Values: '*2026'
The attribute values "full2026" and "noDerivativeWorks2026" are
similar to their counterparts above, except that they use text
specified in RFC 2026 (October 1996).
The special value "none" was also used back then, and denied the IETF
any rights beyond publication as Internet-Draft.
Appendix B. The v3 Format and Processors
This section describes topics that are specific to processors. Note
that there is some discussion of processors in the main body of the
document as well. For example, some elements have descriptions of
how a processor might create output from the element.
A processor has multiple roles. The processor checks whether or not
the input is valid XML; it also checks whether or not the input XML
matches this format. It may have one or more outputs, depending on
the way that it is invoked. It might convert the XML to different
XML, or to a different representation such as HTML or plain text, or
do no conversion at all. It also might give diagnostic warnings
about how to improve the input.
In v2, the grammar was specified as a DTD. In v3, the grammar is
specified only as Relax Next Generation (RNG). This means that
processors need to work from the RNG, not from a DTD. Some of the
features of the v3 grammar cannot be specified as a DTD.
This section differentiates between three types of processors:
Hoffman Expires April 2, 2015 [Page 81]
Internet-Draft XML2RFCv3 September 2014
o RFC Processor -- The processor used by the RFC Editor to process
the input from one of the RFC streams, and to process XML produced
during the RFC editing process.
o Draft Processor -- The processor used by the Internet Draft
submission tool.
o Private Processors -- There may be processors that are meant to
run on the computers of authors. These processors may be used to
produce interim versions of the non-canonical representations so
that authors can see how their XML might later be rendered; to
create documents in representations different than those supported
by the RFC Editor; to possibly create documents that are not meant
to be Internet Drafts or RFCs; and to convert XML that has
external information into XML that has that external information
included.
[[anchor13: There needs to be more focus on processors before this
document is complete. In specific, does this document get to say
what the Draft Processor gets to do? Should this document say even
less about Private Processors?]]
It is expected that a single piece of software will be used for both
the RFC Processor and the Draft Processor, with different application
settings to differentiate between them. It is also expected that the
same software could be used as a Private Processor; others might
create Private Processors independently, or using parts of, the
software used by the RFC Editor.
The RFC Processor and Draft Processor must have clear error
reporting, giving more context than just a line number. For example,
the error messages will differentiate between errors in XML and those
from the v3 format.
It is expected that both the RFC Processor and the Draft Processor
will have options to produce different types of output. For example,
they might have a "convert XML to XML" option that expands the XML
entities in the output.
B.1. Including External Text
All XML processors for v3 are expected to support XInclude
[XInclude]. XInclude specifies a processing model and syntax for
general purpose inclusion of information that is either on the
Internet or local to the user's computer.
In the v3 syntax, XInclude is expressed as the <xi:include> element.
To use this element, you need to include the "xi" namespace in the
Hoffman Expires April 2, 2015 [Page 82]
Internet-Draft XML2RFCv3 September 2014
<rfc> element; that is, you need to specify
xmlns:xi="http://www.w3.org/2001/XInclude"
as one of the attributes in the <rfc> element.
The most common way to use <xi:include> is to pull in references that
are already formed as XML. Currently, this can be done from
xml2rfc.tools.ietf.org, but later is expected to be from the RFC
Editor. For example, if a document has three normative references,
all RFCs, the document might contain:
<references>
<xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/
bibxml/reference.RFC.2119.xml"/>
<xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/
bibxml/reference.RFC.4869.xml"/>
<xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/
bibxml/reference.RFC.7169.xml"/>
</references>
<xi:include> can be used anywhere an XML element could be used (but
not where free text is used). For example, if three Internet Drafts
are all including a particular paragraph or section verbatim, that
text can be kept either in a file or somewhere on the web, and be
included with <xi:include>. An example of pulling something from the
local disk would be:
<x:include href="file://home/chris/ietf/drafts/commontext.xml"/>
In general, XInclude should be used instead of ENTITY references and
XML Processor Instructions (PIs) that allow external inclusions.
[[anchor14: Need to think a bit more about using xi:include to
replace src= for artwork or sourcecode.]]
B.2. Anchors and IDs
People writing and reading Internet Drafts and RFCs often want to
make reference to specific locations in those documents. In the case
of RFC authors, it is common to want to reference another part of
their document, such as "see Section 3.2 of this document". Readers,
on the other hand, want to reference part of documents that they
didn't write, such as "see Section 3.2 of RFC 6949". The XML
vocabulary in this document attempts to support both sets of people.
Authors can leave anchors in a document that can later be used for
references with the "anchor" attribute. Anchors can be included in
Hoffman Expires April 2, 2015 [Page 83]
Internet-Draft XML2RFCv3 September 2014
the following elements: <artwork>, <aside>, <blockquote>, <cref>,
<figure>, <li>, <reference>, <referencegroup>, <section>,
<sourcecode>, <t>, and <table>. The author can then refer to that
anchor in the "target" attribute of the <xref> element.
Readers can refer to any element that has an "anchor" attribute by
that attribute. Note, however, that most of the time, elements won't
have anchors. In the common case, the reader wants to refer to an
element that does not have an "anchor" attribute, but that element
has "partNumber" attribute.
Processors add the "partNumber" attribute to many elements during
processing. This attribute and its value are automatically generated
by the processor if the attribute is not there; if the attribute is
already there, the processor may replace the value.
B.2.1. Overlapping Values
In the HTML representation of this XML vocabulary, both anchors and
partNumber attributes will be used in the "id" attributes of
elements. Thus, there can be no overlap between the names entered in
"anchor" attributes, the values in the "figureNumber", "tableNumber",
and "sectionNumber" attributes, in "slugifiedName" attributes, and
those that are generated for the "partNumber" attributes. Also,
there are some values for the "anchor" values that are reserved for
sections, and those sections can only have those anchor values.
The following rules prevent this overlap:
o "figureNumber" always has the format "f-nnn", where "nnn" is the
figure number. For example, this would be "f-5" for Figure 5.
o "tableNumber" always has the format "t-nnn", where "nnn" is the
figure number. For example, this would be "t-5" for Table 5.
o "sectionNumber" always has the format "s-nnn", where "nnn" is the
section number. For example, this would be "s-2.1.3" for Section
2.1.3.
o "partNumber" always has the format "p-nnn-mmm", where "nnn" is the
section number and "mmm" is the relative position in the section.
For example, this would be "p-2.1.3-7" for the seventh part number
in Section 2.1.3.
o "slugifiedName" always has the format "n-ttt", where "ttt" is the
text of the name after slugification. For example, this would be
"n-protocol-overview" for the name "Protocol Overview". The
actual conversions done in slugification will be specified at a
Hoffman Expires April 2, 2015 [Page 84]
Internet-Draft XML2RFCv3 September 2014
later time..
o Anchors must never overlap with any of the above. The easiest way
to assure that is to not pick an anchor name that starts with a
single letter followed by a hyphen. If an anchor does overlap
with one of the types of names above, the processor will reject
the document.
Appendix C. Relax NG Schema
The following is the RelaxNG schema for the v3 format.
namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
rfc =
element rfc {
attribute number { text }?,
[ a:defaultValue = "" ] attribute obsoletes { text }?,
[ a:defaultValue = "" ] attribute updates { text }?,
attribute category { "std" | "bcp" | "info" | "exp" | "historic"
}?,
attribute consensus { "no" | "yes" }?,
attribute seriesNo { text }?,
attribute ipr {
"full2026"
| "noDerivativeWorks2026"
| "none"
| "full3667"
| "noModification3667"
| "noDerivatives3667"
| "full3978"
| "noModification3978"
| "noDerivatives3978"
| "trust200811"
| "noModificationTrust200811"
| "noDerivativesTrust200811"
| "trust200902"
| "noModificationTrust200902"
| "noDerivativesTrust200902"
| "pre5378Trust200902"
}?,
attribute iprExtract { xsd:IDREF }?,
[ a:defaultValue = "IETF" ]
attribute submissionType {
"IETF" | "IAB" | "IRTF" | "independent"
}?,
attribute docName { text }?,
Hoffman Expires April 2, 2015 [Page 85]
Internet-Draft XML2RFCv3 September 2014
[ a:defaultValue = "en" ] attribute xml:lang { text }?,
[ a:defaultValue = "no" ] attribute sortRefs { "yes" | "no" }?,
[ a:defaultValue = "yes" ] attribute symRefs { "yes" | "no" }?,
[ a:defaultValue = "yes" ] attribute tocInclude { "yes" | "no"
}?,
[ a:defaultValue = "3" ] attribute tocDepth { text }?,
attribute boilerplateText { text }?,
link?,
front,
middle,
back?
}
link =
element link {
attribute href { text },
attribute rel { text }?
}
front =
element front {
title, author+, date?, area*, workgroup*, keyword*, abstract?,
note*
}
title =
element title {
attribute abbrev { text }?,
attribute ascii { text }?,
text
}
author =
element author {
attribute initials { text }?,
attribute surname { text }?,
attribute fullname { text }?,
attribute role { "editor" }?,
[ a:defaultValue = "en" ] attribute xml:lang { text }?,
attribute ascii { text }?,
organization?,
address?
}
organization =
element organization {
attribute abbrev { text }?,
attribute ascii { text }?,
text
}
address =
element address { (email | facsimile | phone | postal | uri)* }
postal =
Hoffman Expires April 2, 2015 [Page 86]
Internet-Draft XML2RFCv3 September 2014
element postal {
[ a:defaultValue = "en" ] attribute xml:lang { text }?,
((city | code | country | region | street)* | postalLine+)
}
street =
element street {
attribute ascii { text }?,
text
}
city =
element city {
attribute ascii { text }?,
text
}
region =
element region {
attribute ascii { text }?,
text
}
code =
element code {
attribute ascii { text }?,
text
}
country = element country { text }
postalLine =
element postalLine {
attribute ascii { text }?,
text
}
phone = element phone { text }
facsimile = element facsimile { text }
email =
element email {
attribute ascii { text }?,
text
}
uri = element uri { text }
date =
element date {
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
area = element area { text }
workgroup = element workgroup { text }
keyword = element keyword { text }
Hoffman Expires April 2, 2015 [Page 87]
Internet-Draft XML2RFCv3 September 2014
abstract = element abstract { t+ }
note =
element note {
attribute title { text }?,
name?,
t+
}
middle = element middle { section+ }
section =
element section {
attribute anchor { xsd:ID }?,
attribute title { text }?,
[ a:defaultValue = "yes" ] attribute numbered { "yes" | "no" }?,
[ a:defaultValue = "default" ]
attribute toc { "include" | "exclude" | "default" }?,
[ a:defaultValue = "no" ] attribute removeInRFC { "yes" | "no"
}?,
attribute sectionNumber { text }?,
name?,
(artwork
| aside
| blockquote
| dl
| figure
| iref
| ol
| sourcecode
| t
| table
| texttable
| ul)*,
section*
}
name =
element name {
attribute slugifiedName { text }?,
(text | cref | eref | iref | tt | xref)*
}
t =
element t {
attribute anchor { xsd:ID }?,
attribute hangText { text }?,
attribute partNumber { text }?,
(text
| b
| bcp14
| cref
| em
Hoffman Expires April 2, 2015 [Page 88]
Internet-Draft XML2RFCv3 September 2014
| eref
| i
| iref
| \list
| ol
| spanx
| strong
| sub
| sup
| tt
| vspace
| xref)*
}
aside =
element aside {
attribute anchor { xsd:ID }?,
attribute partNumber { text }?,
(artwork | figure | iref | sourcecode | t | texttable)*
}
blockquote =
element blockquote {
attribute anchor { xsd:ID }?,
attribute partNumber { text }?,
attribute cite { text },
(text
| artwork
| b
| bcp14
| em
| figure
| i
| sourcecode
| strong
| sub
| sup
| tt)*
}
\list =
element list {
[ a:defaultValue = "empty" ] attribute style { text }?,
attribute hangIndent { text }?,
attribute counter { text }?,
t+
}
ol =
element ol {
[ a:defaultValue = "1" ] attribute style { text }?,
[ a:defaultValue = "1" ] attribute start { text }?,
Hoffman Expires April 2, 2015 [Page 89]
Internet-Draft XML2RFCv3 September 2014
attribute group { text }?,
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
li+
}
ul =
element ul {
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
[ a:defaultValue = "false" ] attribute empty { "false" | "true"
}?,
li+
}
li =
element li {
attribute anchor { xsd:ID }?,
attribute partNumber { text }?,
(t+
| (text
| artwork
| b
| bcp14
| cref
| dl
| em
| eref
| figure
| i
| iref
| ol
| sourcecode
| strong
| sub
| sup
| tt
| ul
| xref)+)
}
dl =
element dl {
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
[ a:defaultValue = "false" ]
attribute hanging { "false" | "true" }?,
(dt, dd)+
}
dt =
element dt {
Hoffman Expires April 2, 2015 [Page 90]
Internet-Draft XML2RFCv3 September 2014
(text
| b
| bcp14
| cref
| em
| eref
| i
| iref
| strong
| sub
| sup
| tt
| xref)*
}
dd =
element dd {
t+
| (text
| artwork
| b
| bcp14
| cref
| dl
| em
| eref
| figure
| i
| iref
| ol
| sourcecode
| strong
| sub
| sup
| tt
| ul
| xref)+
}
xref =
element xref {
attribute target { xsd:IDREF },
[ a:defaultValue = "false" ] attribute pageno { "true" | "false"
}?,
[ a:defaultValue = "default" ]
attribute format { "counter" | "title" | "none" | "default" }?,
(attribute section { text },
attribute relative { text }?,
attribute sectionFormat { text }?)?,
text
Hoffman Expires April 2, 2015 [Page 91]
Internet-Draft XML2RFCv3 September 2014
}
eref =
element eref {
attribute target { text },
text
}
iref =
element iref {
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
empty
}
cref =
element cref {
attribute anchor { xsd:ID }?,
attribute source { text }?,
(text | b | em | eref | i | strong | sub | sup | tt | xref)*
}
tt =
element tt {
(text
| b
| bcp14
| cref
| em
| eref
| i
| iref
| strong
| sub
| sup
| xref)*
}
b =
element b {
(text
| bcp14
| cref
| em
| eref
| i
| iref
| sub
| sup
| tt
| xref)*
Hoffman Expires April 2, 2015 [Page 92]
Internet-Draft XML2RFCv3 September 2014
}
strong =
element strong {
(text
| bcp14
| cref
| em
| eref
| i
| iref
| sub
| sup
| tt
| xref)*
}
i =
element i {
(text
| b
| bcp14
| cref
| eref
| iref
| strong
| sub
| sup
| tt
| xref)*
}
em =
element em {
(text
| b
| bcp14
| cref
| eref
| iref
| strong
| sub
| sup
| tt
| xref)*
}
sub =
element sub {
(text
| b
| bcp14
Hoffman Expires April 2, 2015 [Page 93]
Internet-Draft XML2RFCv3 September 2014
| cref
| em
| eref
| i
| iref
| strong
| tt
| xref)*
}
sup =
element sup {
(text
| b
| bcp14
| cref
| em
| eref
| i
| iref
| strong
| tt
| xref)*
}
spanx =
element spanx {
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
text
}
vspace =
element vspace {
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
figure =
element figure {
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
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 figureNumber { text }?,
Hoffman Expires April 2, 2015 [Page 94]
Internet-Draft XML2RFCv3 September 2014
name?,
iref*,
preamble?,
(artwork | sourcecode)+,
postamble?
}
table =
element table {
attribute anchor { xsd:ID }?,
attribute tableNumber { text }?,
name?,
iref*,
thead?,
tbody+,
tfoot?
}
preamble =
element preamble {
(text
| b
| bcp14
| cref
| em
| eref
| i
| iref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
artwork =
element artwork {
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 }?,
[ a:defaultValue = "en" ] attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute partNumber { text }?,
text*
Hoffman Expires April 2, 2015 [Page 95]
Internet-Draft XML2RFCv3 September 2014
}
sourcecode =
element sourcecode {
[ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "" ] attribute type { text }?,
attribute anchor { xsd:ID }?,
attribute partNumber { text }?,
text
}
thead = element thead { tr+ }
tbody = element tbody { tr+ }
tfoot = element tfoot { tr+ }
tr =
element tr {
[ a:defaultValue = "0" ] attribute border { text }?,
(td, th)+
}
td =
element td {
[ a:defaultValue = "0" ] attribute border { text }?,
[ a:defaultValue = "0" ] attribute colspan { text }?,
[ a:defaultValue = "0" ] attribute rowspan { text }?,
(t+
| (text
| artwork
| b
| bcp14
| cref
| dl
| em
| eref
| figure
| i
| iref
| ol
| sourcecode
| strong
| sub
| sup
| tt
| ul
| xref)+)
}
th =
element th {
[ a:defaultValue = "0" ] attribute border { text }?,
[ a:defaultValue = "0" ] attribute colspan { text }?,
[ a:defaultValue = "0" ] attribute rowspan { text }?,
Hoffman Expires April 2, 2015 [Page 96]
Internet-Draft XML2RFCv3 September 2014
(t+
| (text
| artwork
| b
| bcp14
| cref
| dl
| em
| eref
| figure
| i
| iref
| ol
| sourcecode
| strong
| sub
| sup
| tt
| ul
| xref)+)
}
postamble =
element postamble {
(text
| b
| bcp14
| cref
| em
| eref
| i
| iref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
texttable =
element texttable {
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" }?,
Hoffman Expires April 2, 2015 [Page 97]
Internet-Draft XML2RFCv3 September 2014
name?,
preamble?,
ttcol+,
c*,
postamble?
}
ttcol =
element ttcol {
attribute width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
(cref | eref | iref | xref | text)*
}
c =
element c {
(text
| b
| bcp14
| cref
| em
| eref
| i
| iref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
bcp14 = element bcp14 { text }
back = element back { displayreference*, references*, section* }
displayreference =
element displayreference {
attribute from { text },
attribute to { text }
}
references =
element references {
[ a:defaultValue = "References" ] attribute title { text }?,
reference+
}
reference =
element reference {
attribute anchor { xsd:ID },
attribute target { text }?,
front,
(annotation | format | refcontent | seriesInfo)*
Hoffman Expires April 2, 2015 [Page 98]
Internet-Draft XML2RFCv3 September 2014
}
referencegroup =
element referencegroup {
attribute anchor { xsd:ID },
reference+
}
seriesInfo =
element seriesInfo {
attribute name { text },
attribute value { text },
attribute asciiname { text }?,
attribute asciivalue { text }?,
empty
}
format =
element format {
attribute target { text }?,
attribute type { text },
attribute octets { text }?,
empty
}
annotation =
element annotation {
attribute ascii { text }?,
(text
| b
| bcp14
| cref
| em
| eref
| i
| iref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
refcontent =
element refcontent {
attribute ascii { text }?,
(text | b | bcp14 | em | i | strong | sub | sup | tt)*
}
start = rfc
Hoffman Expires April 2, 2015 [Page 99]
Internet-Draft XML2RFCv3 September 2014
Appendix D. Schema Differences from v2
The following is a non-normative comparison of the v3 format to the
v2 format. A "-" indicates lines removed from the v2 schema, and a
"+" indicates lines added to the v3 schema.
namespace a =
"http://relaxng.org/ns/compatibility/annotations/1.0"
rfc =
element rfc {
attribute number { text }?,
[ a:defaultValue = "" ] attribute obsoletes { text }?,
[ a:defaultValue = "" ] attribute updates { text }?,
attribute category { "std" | "bcp" | "info" | "exp" |
"historic" }?,
attribute consensus { "no" | "yes" }?,
attribute seriesNo { text }?,
attribute ipr {
"full2026"
| "noDerivativeWorks2026"
| "none"
| "full3667"
| "noModification3667"
| "noDerivatives3667"
| "full3978"
| "noModification3978"
| "noDerivatives3978"
| "trust200811"
| "noModificationTrust200811"
| "noDerivativesTrust200811"
| "trust200902"
| "noModificationTrust200902"
| "noDerivativesTrust200902"
| "pre5378Trust200902"
}?,
attribute iprExtract { xsd:IDREF }?,
[ a:defaultValue = "IETF" ]
attribute submissionType {
"IETF" | "IAB" | "IRTF" | "independent"
}?,
attribute docName { text }?,
[ a:defaultValue = "en" ] attribute xml:lang { text }?,
+ [ a:defaultValue = "no" ] attribute sortRefs { "yes" | "no"
+ }?,
+ [ a:defaultValue = "yes" ] attribute symRefs { "yes" | "no"
+ }?,
Hoffman Expires April 2, 2015 [Page 100]
Internet-Draft XML2RFCv3 September 2014
+ [ a:defaultValue = "yes" ] attribute tocInclude { "yes" |
+ "no" }?,
+ [ a:defaultValue = "3" ] attribute tocDepth { text }?,
+ attribute boilerplateText { text }?,
+ link?,
front,
middle,
back?
}
+ link =
+ element link {
+ attribute href { text },
+ attribute rel { text }?
+ }
front =
element front {
- title, author+, date, area*, workgroup*, keyword*, abstract?,
- note*
+ title, author+, date?, area*, workgroup*, keyword*,
+ abstract?, note*
}
title =
element title {
attribute abbrev { text }?,
+ attribute ascii { text }?,
text
}
author =
element author {
attribute initials { text }?,
attribute surname { text }?,
attribute fullname { text }?,
attribute role { "editor" }?,
+ [ a:defaultValue = "en" ] attribute xml:lang { text }?,
+ attribute ascii { text }?,
organization?,
address?
}
organization =
element organization {
attribute abbrev { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ address =
+ element address { (email | facsimile | phone | postal | uri)* }
+ postal =
+ element postal {
Hoffman Expires April 2, 2015 [Page 101]
Internet-Draft XML2RFCv3 September 2014
+ [ a:defaultValue = "en" ] attribute xml:lang { text }?,
+ ((city | code | country | region | street)* | postalLine+)
+ }
+ street =
+ element street {
+ attribute ascii { text }?,
+ text
+ }
+ city =
+ element city {
+ attribute ascii { text }?,
+ text
+ }
+ region =
+ element region {
+ attribute ascii { text }?,
+ text
+ }
+ code =
+ element code {
+ attribute ascii { text }?,
text
}
- address = element address { postal?, phone?, facsimile?, email?,
- uri? }
- postal = element postal { street+, (city | region | code |
- country)* }
- street = element street { text }
- city = element city { text }
- region = element region { text }
- code = element code { text }
country = element country { text }
+ postalLine =
+ element postalLine {
+ attribute ascii { text }?,
+ text
+ }
phone = element phone { text }
facsimile = element facsimile { text }
- email = element email { text }
+ email =
+ element email {
+ attribute ascii { text }?,
+ text
+ }
uri = element uri { text }
date =
element date {
Hoffman Expires April 2, 2015 [Page 102]
Internet-Draft XML2RFCv3 September 2014
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
area = element area { text }
workgroup = element workgroup { text }
keyword = element keyword { text }
abstract = element abstract { t+ }
note =
element note {
- attribute title { text },
+ attribute title { text }?,
+ name?,
t+
}
middle = element middle { section+ }
section =
element section {
attribute anchor { xsd:ID }?,
- attribute title { text },
+ attribute title { text }?,
+ [ a:defaultValue = "yes" ] attribute numbered { "yes" | "no"
+ }?,
[ a:defaultValue = "default" ]
attribute toc { "include" | "exclude" | "default" }?,
- (t | figure | texttable | iref)*,
+ [ a:defaultValue = "no" ] attribute removeInRFC { "yes" |
+ "no" }?,
+ attribute sectionNumber { text }?,
+ name?,
+ (artwork
+ | aside
+ | blockquote
+ | dl
+ | figure
+ | iref
+ | ol
+ | sourcecode
+ | t
+ | table
+ | texttable
+ | ul)*,
section*
}
+ name =
+ element name {
+ attribute slugifiedName { text }?,
Hoffman Expires April 2, 2015 [Page 103]
Internet-Draft XML2RFCv3 September 2014
+ (text | cref | eref | iref | tt | xref)*
+ }
t =
element t {
attribute anchor { xsd:ID }?,
attribute hangText { text }?,
+ attribute partNumber { text }?,
(text
- | \list
- | figure
- | xref
+ | b
+ | bcp14
+ | cref
+ | em
| eref
+ | i
| iref
- | cref
+ | \list
+ | ol
| spanx
- | vspace)*
+ | strong
+ | sub
+ | sup
+ | tt
+ | vspace
+ | xref)*
+ }
+ aside =
+ element aside {
+ attribute anchor { xsd:ID }?,
+ attribute partNumber { text }?,
+ (artwork | figure | iref | sourcecode | t | texttable)*
+ }
+ blockquote =
+ element blockquote {
+ attribute anchor { xsd:ID }?,
+ attribute partNumber { text }?,
+ attribute cite { text },
+ (text
+ | artwork
+ | b
+ | bcp14
+ | em
+ | figure
+ | i
Hoffman Expires April 2, 2015 [Page 104]
Internet-Draft XML2RFCv3 September 2014
+ | sourcecode
+ | strong
+ | sub
+ | sup
+ | tt)*
}
\list =
element list {
- attribute style { text }?,
+ [ a:defaultValue = "empty" ] attribute style { text }?,
attribute hangIndent { text }?,
attribute counter { text }?,
t+
}
+ ol =
+ element ol {
+ [ a:defaultValue = "1" ] attribute style { text }?,
+ [ a:defaultValue = "1" ] attribute start { text }?,
+ attribute group { text }?,
+ [ a:defaultValue = "normal" ]
+ attribute spacing { "normal" | "compact" }?,
+ li+
+ }
+ ul =
+ element ul {
+ [ a:defaultValue = "normal" ]
+ attribute spacing { "normal" | "compact" }?,
+ [ a:defaultValue = "false" ] attribute empty { "false" |
+ "true" }?,
+ li+
+ }
+ li =
+ element li {
+ attribute anchor { xsd:ID }?,
+ attribute partNumber { text }?,
+ (t+
+ | (text
+ | artwork
+ | b
+ | bcp14
+ | cref
+ | dl
+ | em
+ | eref
+ | figure
+ | i
+ | iref
+ | ol
Hoffman Expires April 2, 2015 [Page 105]
Internet-Draft XML2RFCv3 September 2014
+ | sourcecode
+ | strong
+ | sub
+ | sup
+ | tt
+ | ul
+ | xref)+)
+ }
+ dl =
+ element dl {
+ [ a:defaultValue = "normal" ]
+ attribute spacing { "normal" | "compact" }?,
+ [ a:defaultValue = "false" ]
+ attribute hanging { "false" | "true" }?,
+ (dt, dd)+
+ }
+ dt =
+ element dt {
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ dd =
+ element dd {
+ t+
+ | (text
+ | artwork
+ | b
+ | bcp14
+ | cref
+ | dl
+ | em
+ | eref
+ | figure
+ | i
+ | iref
+ | ol
+ | sourcecode
Hoffman Expires April 2, 2015 [Page 106]
Internet-Draft XML2RFCv3 September 2014
+ | strong
+ | sub
+ | sup
+ | tt
+ | ul
+ | xref)+
+ }
xref =
element xref {
attribute target { xsd:IDREF },
[ a:defaultValue = "false" ] attribute pageno { "true" |
"false" }?,
[ a:defaultValue = "default" ]
attribute format { "counter" | "title" | "none" | "default"
}?,
+ (attribute section { text },
+ attribute relative { text }?,
+ attribute sectionFormat { text }?)?,
text
}
eref =
element eref {
attribute target { text },
text
}
iref =
element iref {
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
empty
}
cref =
element cref {
attribute anchor { xsd:ID }?,
attribute source { text }?,
- text
+ (text | b | em | eref | i | strong | sub | sup | tt | xref)*
+ }
+ tt =
+ element tt {
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
Hoffman Expires April 2, 2015 [Page 107]
Internet-Draft XML2RFCv3 September 2014
+ | i
+ | iref
+ | strong
+ | sub
+ | sup
+ | xref)*
+ }
+ b =
+ element b {
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ strong =
+ element strong {
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ i =
+ element i {
+ (text
+ | b
+ | bcp14
+ | cref
+ | eref
+ | iref
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
Hoffman Expires April 2, 2015 [Page 108]
Internet-Draft XML2RFCv3 September 2014
+ }
+ em =
+ element em {
+ (text
+ | b
+ | bcp14
+ | cref
+ | eref
+ | iref
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ sub =
+ element sub {
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
+ | strong
+ | tt
+ | xref)*
+ }
+ sup =
+ element sup {
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
+ | strong
+ | tt
+ | xref)*
}
spanx =
element spanx {
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
Hoffman Expires April 2, 2015 [Page 109]
Internet-Draft XML2RFCv3 September 2014
text
}
vspace =
element vspace {
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
figure =
element figure {
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
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 figureNumber { text }?,
+ name?,
iref*,
preamble?,
- artwork,
+ (artwork | sourcecode)+,
postamble?
}
+ table =
+ element table {
+ attribute anchor { xsd:ID }?,
+ attribute tableNumber { text }?,
+ name?,
+ iref*,
+ thead?,
+ tbody+,
+ tfoot?
+ }
preamble =
- element preamble { (text | xref | eref | iref | cref | spanx)* }
+ element preamble {
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
Hoffman Expires April 2, 2015 [Page 110]
Internet-Draft XML2RFCv3 September 2014
+ | spanx
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
artwork =
element artwork {
- [ a:defaultValue = "preserve" ]
- attribute xml:space { "default" | "preserve" }?,
+ 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 }?,
+ [ a:defaultValue = "en" ] attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ attribute partNumber { text }?,
text*
}
+ sourcecode =
+ element sourcecode {
+ [ a:defaultValue = "" ] attribute name { text }?,
+ [ a:defaultValue = "" ] attribute type { text }?,
+ attribute anchor { xsd:ID }?,
+ attribute partNumber { text }?,
+ text
+ }
+ thead = element thead { tr+ }
+ tbody = element tbody { tr+ }
+ tfoot = element tfoot { tr+ }
+ tr =
+ element tr {
+ [ a:defaultValue = "0" ] attribute border { text }?,
+ (td, th)+
+ }
+ td =
+ element td {
+ [ a:defaultValue = "0" ] attribute border { text }?,
+ [ a:defaultValue = "0" ] attribute colspan { text }?,
+ [ a:defaultValue = "0" ] attribute rowspan { text }?,
+ (t+
+ | (text
Hoffman Expires April 2, 2015 [Page 111]
Internet-Draft XML2RFCv3 September 2014
+ | artwork
+ | b
+ | bcp14
+ | cref
+ | dl
+ | em
+ | eref
+ | figure
+ | i
+ | iref
+ | ol
+ | sourcecode
+ | strong
+ | sub
+ | sup
+ | tt
+ | ul
+ | xref)+)
+ }
+ th =
+ element th {
+ [ a:defaultValue = "0" ] attribute border { text }?,
+ [ a:defaultValue = "0" ] attribute colspan { text }?,
+ [ a:defaultValue = "0" ] attribute rowspan { text }?,
+ (t+
+ | (text
+ | artwork
+ | b
+ | bcp14
+ | cref
+ | dl
+ | em
+ | eref
+ | figure
+ | i
+ | iref
+ | ol
+ | sourcecode
+ | strong
+ | sub
+ | sup
+ | tt
+ | ul
+ | xref)+)
+ }
postamble =
- element postamble { (text | xref | eref | iref | cref | spanx)*
+ element postamble {
Hoffman Expires April 2, 2015 [Page 112]
Internet-Draft XML2RFCv3 September 2014
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
+ | spanx
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
}
texttable =
element texttable {
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 width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
- text
+ (cref | eref | iref | xref | text)*
+ }
+ c =
+ element c {
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
Hoffman Expires April 2, 2015 [Page 113]
Internet-Draft XML2RFCv3 September 2014
+ | iref
+ | spanx
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ bcp14 = element bcp14 { text }
+ back = element back { displayreference*, references*, section* }
+ displayreference =
+ element displayreference {
+ attribute from { text },
+ attribute to { text }
}
- c = element c { (text | xref | eref | iref | cref | spanx)* }
- back = element back { references*, section* }
references =
element references {
[ a:defaultValue = "References" ] attribute title { text }?,
reference+
}
reference =
element reference {
attribute anchor { xsd:ID },
attribute target { text }?,
front,
- seriesInfo*,
- format*,
- annotation*
+ (annotation | format | refcontent | seriesInfo)*
+ }
+ referencegroup =
+ element referencegroup {
+ attribute anchor { xsd:ID },
+ reference+
}
seriesInfo =
element seriesInfo {
attribute name { text },
attribute value { text },
+ attribute asciiname { text }?,
+ attribute asciivalue { text }?,
empty
}
format =
element format {
attribute target { text }?,
Hoffman Expires April 2, 2015 [Page 114]
Internet-Draft XML2RFCv3 September 2014
attribute type { text },
attribute octets { text }?,
empty
}
annotation =
- element annotation { (text | xref | eref | iref | cref |
- spanx)* }
+ element annotation {
+ attribute ascii { text }?,
+ (text
+ | b
+ | bcp14
+ | cref
+ | em
+ | eref
+ | i
+ | iref
+ | spanx
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ refcontent =
+ element refcontent {
+ attribute ascii { text }?,
+ (text | b | bcp14 | em | i | strong | sub | sup | tt)*
+ }
start = rfc
Index
A
abbrev attribute
in organization element 37
in title element 60
abstract element 10
inside front 29
address element 10
inside author 16
align attribute
in artwork element 13
in figure element 28
in texttable element 71
in ttcol element 72
alt attribute
Hoffman Expires April 2, 2015 [Page 115]
Internet-Draft XML2RFCv3 September 2014
in artwork element 13
in figure element 28
anchor attribute
in artwork element 13
in aside element 15
in blockquote element 19
in cref element 21
in figure element 28
in li element 33
in reference element 40
in referencegroup element 41
in section element 47
in sourcecode element 50
in t element 55
in table element 56
in texttable element 71
annotation element 10
ascii attribute 11
inside reference 40
application/rfc+xml Media Type 74
area element 11
inside front 29
artwork element 12
align attribute 13
alt attribute 13
anchor attribute 13
height attribute 13
inside aside 15
inside blockquote 19
inside dd 22
inside figure 28
inside li 32
inside section 46
inside td 57
inside th 59
name attribute 13
partNumber attribute 13
src attribute 14
type attribute 14
width attribute 14
xml:lang attribute 14
xml:space attribute 14
ascii attribute
in annotation element 11
in author element 16
in city element 20
in code element 20
in email element 26
Hoffman Expires April 2, 2015 [Page 116]
Internet-Draft XML2RFCv3 September 2014
in organization element 37
in postalLine element 38
in refcontent element 39
in region element 41
in street element 52
in title element 60
asciiname attribute
in seriesInfo element 48
asciivalue attribute
in seriesInfo element 49
aside element 15
anchor attribute 15
inside section 46
partNumber attribute 15
Attributes
abbrev 37, 60
align 13, 28, 71-72
alt 13, 28
anchor 13, 15, 19, 21, 28, 33, 40-41, 47, 50, 55-56, 71
ascii 11, 16, 20, 26, 37-39, 41, 52, 60
asciiname 48
asciivalue 49
blankLines 73
boilerplateText 42
border 58-59, 61
category 42
cite 19
colspan 58, 60
consensus 43
counter 68
day 22
docName 43
empty 62
figureNumber 28
format 64
from 23
fullname 16
group 35
hangIndent 68
hanging 24
hangText 55
height 13, 28
href 33
initials 16
ipr 43
iprExtract 44
item 31
month 22
Hoffman Expires April 2, 2015 [Page 117]
Internet-Draft XML2RFCv3 September 2014
name 13, 49-50
number 44
numbered 47
obsoletes 44
octets 67
pageno 65
partNumber 13, 15, 19, 33, 50, 55
primary 31
rel 34
relative 65
removeInRFC 47
role 16
rowspan 58, 60
section 65
sectionFormat 65
sectionNumber 48
seriesNo 44
slugifiedName 34
sortRefs 45
source 21
spacing 24, 35, 62
src 14, 28
start 36
style 36, 68, 70-71
subitem 31
submissionType 45
suppress-title 28, 71
surname 16
symRefs 45
tableNumber 56
target 27, 40, 66, 68
title 29, 35, 41, 48, 72
to 24
toc 48
tocDepth 45
tocInclude 45
type 14, 50, 68
updates 46
value 49
width 14, 29, 72
xml:lang 14, 17, 38, 46
xml:space 14, 70
year 22
author element 15
ascii attribute 16
fullname attribute 16
initials attribute 16
inside front 29
Hoffman Expires April 2, 2015 [Page 118]
Internet-Draft XML2RFCv3 September 2014
role attribute 16
surname attribute 16
xml:lang attribute 17
B
b element 17
inside annotation 11
inside blockquote 19
inside c 66
inside cref 21
inside dd 22
inside dt 25
inside em 26
inside i 30
inside li 32
inside postamble 69
inside preamble 69
inside refcontent 39
inside sub 53
inside sup 54
inside t 55
inside td 57
inside th 59
inside tt 61
back element 18
inside rfc 42
bcp14 element 18
inside annotation 11
inside b 17
inside blockquote 19
inside c 67
inside dd 22
inside dt 25
inside em 26
inside i 30
inside li 32
inside postamble 69
inside preamble 69
inside refcontent 39
inside strong 52
inside sub 53
inside sup 54
inside t 55
inside td 57
inside th 59
inside tt 61
blankLines attribute
in vspace element 73
Hoffman Expires April 2, 2015 [Page 119]
Internet-Draft XML2RFCv3 September 2014
blockquote element 18
anchor attribute 19
cite attribute 19
inside section 46
partNumber attribute 19
boilerplateText attribute
in rfc element 42
border attribute
in td element 58
in th element 59
in tr element 61
C
c element 66
inside texttable 71
category attribute
in rfc element 42
cite attribute
in blockquote element 19
city element 19
ascii attribute 20
inside postal 38
code element 20
ascii attribute 20
inside postal 38
colspan attribute
in td element 58
in th element 60
consensus attribute
in rfc element 43
counter attribute
in list element 68
country element 20
inside postal 38
cref element 20
anchor attribute 21
inside annotation 11
inside b 17
inside c 67
inside dd 22
inside dt 25
inside em 26
inside i 30
inside li 32
inside name 34
inside postamble 69
inside preamble 69
inside strong 52
Hoffman Expires April 2, 2015 [Page 120]
Internet-Draft XML2RFCv3 September 2014
inside sub 53
inside sup 54
inside t 55
inside td 57
inside th 59
inside tt 61
inside ttcol 72
source attribute 21
D
date element 21
day attribute 22
inside front 29
month attribute 22
year attribute 22
day attribute
in date element 22
dd element 22
inside dl 24
displayreference element 23
from attribute 23
inside back 18
to attribute 24
dl element 24
hanging attribute 24
inside dd 22
inside li 32
inside section 46
inside td 57
inside th 59
spacing attribute 24
docName attribute
in rfc element 43
dt element 25
inside dl 24
E
Elements
abstract 10, 29
address 10, 16
annotation 10, 40
area 11, 29
artwork 12, 15, 19, 22, 28, 32, 46, 57, 59
aside 15, 46
author 15, 29
b 11, 17, 19, 21-22, 25-26, 30, 32, 39, 53-55, 57, 59, 61, 66,
69
back 18, 42
Hoffman Expires April 2, 2015 [Page 121]
Internet-Draft XML2RFCv3 September 2014
bcp14 11, 17-19, 22, 25-26, 30, 32, 39, 52-55, 57, 59, 61, 67,
69
blockquote 18, 46
c 66, 71
city 19, 38
code 20, 38
country 20, 38
cref 11, 17, 20, 22, 25-26, 30, 32, 34, 52-55, 57, 59, 61, 67,
69, 72
date 21, 29
dd 22, 24
displayreference 18, 23
dl 22, 24, 32, 46, 57, 59
dt 24-25
em 11, 17, 19, 21, 23, 25, 32, 39, 52-55, 57, 59, 61, 67, 69
email 10, 26
eref 11, 17, 21, 23, 25-27, 30, 32, 34, 52-55, 57, 59, 61, 67,
69-70, 72
facsimile 10, 67
figure 15, 19, 23, 27, 32, 47, 57, 59
format 40, 67
front 29, 40, 42
i 11, 17, 19, 21, 23, 25, 29, 32, 39, 52-55, 57, 59, 62, 67,
69-70
iref 11, 15, 17, 23, 25-27, 30, 32, 34, 47, 52-57, 59, 62, 67,
69-70, 72
keyword 29, 31
li 31, 35, 62
link 33, 42
list 55, 68
middle 34, 42
name 27, 34-35, 46, 56, 71
note 29, 35
ol 23, 32, 35, 47, 55, 57, 59
organization 16, 37
phone 10, 37
postal 10, 37
postalLine 38
postamble 28, 68, 71
preamble 27, 69, 71
refcontent 38, 40
reference 40-41
referencegroup 40
references 18, 41
region 38, 41
rfc 42
section 18, 34, 46-47
seriesInfo 40, 48
Hoffman Expires April 2, 2015 [Page 122]
Internet-Draft XML2RFCv3 September 2014
sourcecode 15, 19, 23, 28, 32, 47, 49, 57, 59
spanx 11, 55, 67, 69-70
street 38, 51
strong 11, 19, 21, 23, 25-26, 30, 32, 39, 52-55, 57, 59, 62,
67, 69-70
sub 11, 17, 19, 21, 23, 25-26, 30, 32, 39, 52-53, 55, 57, 59,
62, 67, 69-70
sup 11, 17, 19, 21, 23, 25-26, 30, 32, 39, 52-53, 55, 57, 59,
62, 67, 69-70
t 10, 15, 22, 32, 35, 47, 54, 57-58, 68
table 47, 56
tbody 56
td 57, 61
texttable 15, 47, 71
tfoot 56, 58
th 58, 61
thead 56, 60
title 29, 60
tr 56, 58, 60
tt 11, 17, 19, 21, 23, 25-26, 30, 32, 34, 39, 52-55, 58-59,
61, 67, 69-70
ttcol 71-72
ul 23, 32, 47, 58-59, 62
uri 10, 63
vspace 55, 73
workgroup 29, 63
xref 11, 17, 21, 23, 25-26, 30, 32, 34, 52-55, 58-59, 62-63,
67, 69-70, 72
em element 25
inside annotation 11
inside b 17
inside blockquote 19
inside c 67
inside cref 21
inside dd 23
inside dt 25
inside li 32
inside postamble 69
inside preamble 69
inside refcontent 39
inside strong 52
inside sub 53
inside sup 54
inside t 55
inside td 57
inside th 59
inside tt 61
email element 26
Hoffman Expires April 2, 2015 [Page 123]
Internet-Draft XML2RFCv3 September 2014
ascii attribute 26
inside address 10
empty attribute
in ul element 62
eref element 27
inside annotation 11
inside b 17
inside c 67
inside cref 21
inside dd 23
inside dt 25
inside em 26
inside i 30
inside li 32
inside name 34
inside postamble 69
inside preamble 70
inside strong 52
inside sub 53
inside sup 54
inside t 55
inside td 57
inside th 59
inside tt 61
inside ttcol 72
target attribute 27
F
facsimile element 67
inside address 10
figure element 27
align attribute 28
alt attribute 28
anchor attribute 28
figureNumber attribute 28
height attribute 28
inside aside 15
inside blockquote 19
inside dd 23
inside li 32
inside section 47
inside td 57
inside th 59
src attribute 28
suppress-title attribute 28
title attribute 29
width attribute 29
figureNumber attribute
Hoffman Expires April 2, 2015 [Page 124]
Internet-Draft XML2RFCv3 September 2014
in figure element 28
format attribute
in xref element 64
format element 67
inside reference 40
octets attribute 67
target attribute 68
type attribute 68
from attribute
in displayreference element 23
front element 29
inside reference 40
inside rfc 42
fullname attribute
in author element 16
G
group attribute
in ol element 35
H
hangIndent attribute
in list element 68
hanging attribute
in dl element 24
hangText attribute
in t element 55
height attribute
in artwork element 13
in figure element 28
href attribute
in link element 33
I
i element 29
inside annotation 11
inside b 17
inside blockquote 19
inside c 67
inside cref 21
inside dd 23
inside dt 25
inside li 32
inside postamble 69
inside preamble 70
inside refcontent 39
inside strong 52
inside sub 53
Hoffman Expires April 2, 2015 [Page 125]
Internet-Draft XML2RFCv3 September 2014
inside sup 54
inside t 55
inside td 57
inside th 59
inside tt 62
initials attribute
in author element 16
ipr attribute
'*2026' 81
'*3667' 81
'*3978' 81
'*trust200811' 80
'*trust200902' 79
'noDerivativesTrust200902' 80
'noModificationTrust200902' 79
'pre5378Trust200902' 80
'trust200902' 79
in rfc element 43
iprExtract attribute
in rfc element 44
iref element 30
inside annotation 11
inside aside 15
inside b 17
inside c 67
inside dd 23
inside dt 25
inside em 26
inside figure 27
inside i 30
inside li 32
inside name 34
inside postamble 69
inside preamble 70
inside section 47
inside strong 52
inside sub 53
inside sup 54
inside t 55
inside table 56
inside td 57
inside th 59
inside tt 62
inside ttcol 72
item attribute 31
primary attribute 31
subitem attribute 31
item attribute
Hoffman Expires April 2, 2015 [Page 126]
Internet-Draft XML2RFCv3 September 2014
in iref element 31
K
keyword element 31
inside front 29
L
li element 31
anchor attribute 33
inside ol 35
inside ul 62
partNumber attribute 33
link element 33
href attribute 33
inside rfc 42
rel attribute 34
list element 68
counter attribute 68
hangIndent attribute 68
inside t 55
style attribute 68
M
Media Type
application/rfc+xml 74
middle element 34
inside rfc 42
month attribute
in date element 22
N
name attribute
in artwork element 13
in seriesInfo element 49
in sourcecode element 50
name element 34
inside figure 27
inside note 35
inside section 46
inside table 56
inside texttable 71
slugifiedName attribute 34
note element 35
inside front 29
title attribute 35
number attribute
in rfc element 44
numbered attribute
Hoffman Expires April 2, 2015 [Page 127]
Internet-Draft XML2RFCv3 September 2014
in section element 47
O
obsoletes attribute
in rfc element 44
octets attribute
in format element 67
ol element 35
group attribute 35
inside dd 23
inside li 32
inside section 47
inside t 55
inside td 57
inside th 59
spacing attribute 35
start attribute 36
style attribute 36
organization element 37
abbrev attribute 37
ascii attribute 37
inside author 16
P
pageno attribute
in xref element 65
partNumber attribute
in artwork element 13
in aside element 15
in blockquote element 19
in li element 33
in sourcecode element 50
in t element 55
phone element 37
inside address 10
postal element 37
inside address 10
xml:lang attribute 38
postalLine element 38
ascii attribute 38
inside postal 38
postamble element 68
inside figure 28
inside texttable 71
preamble element 69
inside figure 27
inside texttable 71
primary attribute
Hoffman Expires April 2, 2015 [Page 128]
Internet-Draft XML2RFCv3 September 2014
in iref element 31
R
refcontent element 38
ascii attribute 39
inside reference 40
reference element 40
anchor attribute 40
inside referencegroup 40
inside references 41
target attribute 40
referencegroup element 40
anchor attribute 41
references element 41
inside back 18
title attribute 41
region element 41
ascii attribute 41
inside postal 38
rel attribute
in link element 34
relative attribute
in xref element 65
removeInRFC attribute
in section element 47
rfc element 42
boilerplateText attribute 42
category attribute 42
consensus attribute 43
docName attribute 43
ipr attribute 43
iprExtract attribute 44
number attribute 44
obsoletes attribute 44
seriesNo attribute 44
sortRefs attribute 45
submissionType attribute 45
symRefs attribute 45
tocDepth attribute 45
tocInclude attribute 45
updates attribute 46
xml:lang attribute 46
role attribute
in author element 16
rowspan attribute
in td element 58
in th element 60
Hoffman Expires April 2, 2015 [Page 129]
Internet-Draft XML2RFCv3 September 2014
S
section attribute
in xref element 65
section element 46
anchor attribute 47
inside back 18
inside middle 34
inside section 47
numbered attribute 47
removeInRFC attribute 47
sectionNumber attribute 48
title attribute 48
toc attribute 48
sectionFormat attribute
in xref element 65
sectionNumber attribute
in section element 48
seriesInfo element 48
asciiname attribute 48
asciivalue attribute 49
inside reference 40
name attribute 49
value attribute 49
seriesNo attribute
in rfc element 44
slugifiedName attribute
in name element 34
sortRefs attribute
in rfc element 45
source attribute
in cref element 21
sourcecode element 49
anchor attribute 50
inside aside 15
inside blockquote 19
inside dd 23
inside figure 28
inside li 32
inside section 47
inside td 57
inside th 59
name attribute 50
partNumber attribute 50
type attribute 50
spacing attribute
in dl element 24
in ol element 35
in ul element 62
Hoffman Expires April 2, 2015 [Page 130]
Internet-Draft XML2RFCv3 September 2014
spanx element 70
inside annotation 11
inside c 67
inside postamble 69
inside preamble 70
inside t 55
style attribute 70
xml:space attribute 70
src attribute
in artwork element 14
in figure element 28
start attribute
in ol element 36
street element 51
ascii attribute 52
inside postal 38
strong element 52
inside annotation 11
inside blockquote 19
inside c 67
inside cref 21
inside dd 23
inside dt 25
inside em 26
inside i 30
inside li 32
inside postamble 69
inside preamble 70
inside refcontent 39
inside sub 53
inside sup 54
inside t 55
inside td 57
inside th 59
inside tt 62
style attribute
in list element 68
in ol element 36
in spanx element 70
in texttable element 71
sub element 53
inside annotation 11
inside b 17
inside blockquote 19
inside c 67
inside cref 21
inside dd 23
inside dt 25
Hoffman Expires April 2, 2015 [Page 131]
Internet-Draft XML2RFCv3 September 2014
inside em 26
inside i 30
inside li 32
inside postamble 69
inside preamble 70
inside refcontent 39
inside strong 52
inside t 55
inside td 57
inside th 59
inside tt 62
subitem attribute
in iref element 31
submissionType attribute
in rfc element 45
sup element 53
inside annotation 11
inside b 17
inside blockquote 19
inside c 67
inside cref 21
inside dd 23
inside dt 25
inside em 26
inside i 30
inside li 32
inside postamble 69
inside preamble 70
inside refcontent 39
inside strong 52
inside t 55
inside td 57
inside th 59
inside tt 62
suppress-title attribute
in figure element 28
in texttable element 71
surname attribute
in author element 16
symRefs attribute
in rfc element 45
T
t element 54
anchor attribute 55
hangText attribute 55
inside abstract 10
inside aside 15
Hoffman Expires April 2, 2015 [Page 132]
Internet-Draft XML2RFCv3 September 2014
inside dd 22
inside li 32
inside list 68
inside note 35
inside section 47
inside td 57
inside th 58
partNumber attribute 55
table element 56
anchor attribute 56
inside section 47
tableNumber attribute 56
tableNumber attribute
in table element 56
target attribute
in eref element 27
in format element 68
in reference element 40
in xref element 66
tbody element 56
inside table 56
td element 57
border attribute 58
colspan attribute 58
inside tr 61
rowspan attribute 58
texttable element 71
align attribute 71
anchor attribute 71
inside aside 15
inside section 47
style attribute 71
suppress-title attribute 71
title attribute 72
tfoot element 58
inside table 56
th element 58
border attribute 59
colspan attribute 60
inside tr 61
rowspan attribute 60
thead element 60
inside table 56
title attribute
in figure element 29
in note element 35
in references element 41
in section element 48
Hoffman Expires April 2, 2015 [Page 133]
Internet-Draft XML2RFCv3 September 2014
in texttable element 72
title element 60
abbrev attribute 60
ascii attribute 60
inside front 29
to attribute
in displayreference element 24
toc attribute
in section element 48
tocDepth attribute
in rfc element 45
tocInclude attribute
in rfc element 45
tr element 60
border attribute 61
inside tbody 56
inside tfoot 58
inside thead 60
tt element 61
inside annotation 11
inside b 17
inside blockquote 19
inside c 67
inside cref 21
inside dd 23
inside dt 25
inside em 26
inside i 30
inside li 32
inside name 34
inside postamble 69
inside preamble 70
inside refcontent 39
inside strong 52
inside sub 53
inside sup 54
inside t 55
inside td 58
inside th 59
ttcol element 72
align attribute 72
inside texttable 71
width attribute 72
type attribute
in artwork element 14
in format element 68
in sourcecode element 50
Hoffman Expires April 2, 2015 [Page 134]
Internet-Draft XML2RFCv3 September 2014
U
ul element 62
empty attribute 62
inside dd 23
inside li 32
inside section 47
inside td 58
inside th 59
spacing attribute 62
updates attribute
in rfc element 46
uri element 63
inside address 10
V
value attribute
in seriesInfo element 49
vspace element 73
blankLines attribute 73
inside t 55
W
width attribute
in artwork element 14
in figure element 29
in ttcol element 72
workgroup element 63
inside front 29
X
xml:lang attribute
in artwork element 14
in author element 17
in postal element 38
in rfc element 46
xml:space attribute
in artwork element 14
in spanx element 70
xref element 63
format attribute 64
inside annotation 11
inside b 17
inside c 67
inside cref 21
inside dd 23
inside dt 25
inside em 26
inside i 30
Hoffman Expires April 2, 2015 [Page 135]
Internet-Draft XML2RFCv3 September 2014
inside li 32
inside name 34
inside postamble 69
inside preamble 70
inside strong 52
inside sub 53
inside sup 54
inside t 55
inside td 58
inside th 59
inside tt 62
inside ttcol 72
pageno attribute 65
relative attribute 65
section attribute 65
sectionFormat attribute 65
target attribute 66
xref formats
counter 64
default 64
none 64
title 64
Y
year attribute
in date element 22
Author's Address
Paul Hoffman
VPN Consortium
EMail: paul.hoffman@vpnc.org
Hoffman Expires April 2, 2015 [Page 136]