RFC 7991
The "xml2rfc" Version 3 Vocabulary
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. The <author> elements contained within the document's <front> element are used to fill the boilerplate and also to generate the "Author's Address" section (see [RFC7322]). Note that an "author" can also be just an organization (by not specifying any of the "name" attributes, but adding the <organization> child element). Furthermore, the "role" attribute can be used to mark an author as "editor". This is reflected both on the front page and in the "Author's Address" section, as well as in bibliographic references. Note that this specification does not define a precise meaning for the term "editor". This element appears as a child element of <front> (Section 2.26). Content model: In this order: 1. One optional <organization> element (Section 2.35) 2. One optional <address> element (Section 2.2)2.7.1. "asciiFullname" Attribute
The ASCII equivalent of the author's full name.2.7.2. "asciiInitials" Attribute
The ASCII equivalent of the author's initials, to be used in conjunction with the separately specified asciiSurname.2.7.3. "asciiSurname" Attribute
The ASCII equivalent of the author's surname, to be used in conjunction with the separately specified asciiInitials.
2.7.4. "fullname" Attribute
The full name (used in the automatically generated "Author's Address" section). Although this attribute is optional, if one or more of the "asciiFullname", "asciiInitials", or "asciiSurname" attributes have values, the "fullname" attribute is required.2.7.5. "initials" Attribute
An abbreviated variant of the given name(s), to be used in conjunction with the separately specified surname. It usually appears on the front page, in footers, and in references. Some processors will post-process the value -- for instance, when it only contains a single letter (in which case they might add a trailing dot). Relying on this kind of post-processing can lead to results varying across formatters and thus ought to be avoided.2.7.6. "role" Attribute
Specifies the role the author had in creating the document. Allowed value: o "editor"2.7.7. "surname" Attribute
The author's surname, to be used in conjunction with the separately specified initials. It usually appears on the front page, in footers, and in references.2.8. <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.45). Content model: In this order: 1. Optional <displayreference> elements (Section 2.19) 2. Optional <references> elements (Section 2.42) 3. Optional <section> elements (Section 2.46)
2.9. <bcp14>
Marks text that are phrases defined in [BCP14] such as "MUST", "SHOULD NOT", and so on. When shown in some of the output representations, the text in this element might be highlighted. The use of this element is optional. This element is only to be used around the actual phrase from BCP 14, not the full definition of a requirement. For example, it is correct to say "The packet <bcp14>MUST</bcp14> be dropped.", but it is not correct to say "<bcp14>The packet MUST be dropped.</bcp14>". This element appears as a child element of <annotation> (Section 2.3), <blockquote> (Section 2.10), <dd> (Section 2.18), <dt> (Section 2.21), <em> (Section 2.22), <li> (Section 2.29), <preamble> (Section 3.6), <refcontent> (Section 2.39), <strong> (Section 2.50), <sub> (Section 2.51), <sup> (Section 2.52), <t> (Section 2.53), <td> (Section 2.56), <th> (Section 2.58), and <tt> (Section 2.62). Content model: only text content.2.10. <blockquote>
Specifies that a block of text is a quotation. This element appears as a child element of <section> (Section 2.46). Content model: Either: In any order, but at least one of: * <artwork> elements (Section 2.5) * <dl> elements (Section 2.20) * <figure> elements (Section 2.25) * <ol> elements (Section 2.34) * <sourcecode> elements (Section 2.48) * <t> elements (Section 2.53) * <ul> elements (Section 2.63)
Or:
In any order, but at least one of:
* Text
* <bcp14> elements (Section 2.9)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
2.10.1. "anchor" Attribute
Document-wide unique identifier for this quotation.
2.10.2. "cite" Attribute
The source of the citation. This must be a URI. If the "quotedFrom"
attribute is given, this URI will be used by processing tools as the
link for the text of that attribute.
2.10.3. "quotedFrom" Attribute
Name of person or document the text in this element is quoted from.
A formatter should render this as visible text at the end of the
quotation.
2.11. <boilerplate>
Holds the boilerplate text for the document. This element is filled in by the prep tool. This element contains <section> elements. Every <section> element in this element must have the "numbered" attribute set to "false". This element appears as a child element of <front> (Section 2.26). Content model: One or more <section> elements (Section 2.46)2.12. <br>
Indicates that a line break should be inserted in the generated output by a formatting tool. Multiple successive instances of this element are ignored. This element appears as a child element of <td> (Section 2.56) and <th> (Section 2.58). Content model: this element does not have any contents.2.13. <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.2.13.1. "ascii" Attribute
The ASCII equivalent of the city name.2.14. <code>
Gives the postal region code. This element appears as a child element of <postal> (Section 2.37). Content model: only text content.2.14.1. "ascii" Attribute
The ASCII equivalent of the postal code.
2.15. <country>
Gives the country name or code in a postal address. This element appears as a child element of <postal> (Section 2.37). Content model: only text content.2.15.1. "ascii" Attribute
The ASCII equivalent of the country name.2.16. <cref>
Represents a comment. Comments can be used in a document while it is work in progress. They might appear either inline and visually highlighted, at the end of the document, or not at all, depending on the formatting tool. This element appears as a child element of <annotation> (Section 2.3), <blockquote> (Section 2.10), <c> (Section 3.1), <dd> (Section 2.18), <dt> (Section 2.21), <em> (Section 2.22), <li> (Section 2.29), <name> (Section 2.32), <postamble> (Section 3.5), <preamble> (Section 3.6), <strong> (Section 2.50), <sub> (Section 2.51), <sup> (Section 2.52), <t> (Section 2.53), <td> (Section 2.56), <th> (Section 2.58), <tt> (Section 2.62), and <ttcol> (Section 3.9). Content model: In any order: o Text o <em> elements (Section 2.22) o <eref> elements (Section 2.24) o <relref> elements (Section 2.44) o <strong> elements (Section 2.50)
o <sub> elements (Section 2.51) o <sup> elements (Section 2.52) o <tt> elements (Section 2.62) o <xref> elements (Section 2.66)2.16.1. "anchor" Attribute
Document-wide unique identifier for this comment.2.16.2. "display" Attribute
Suggests whether or not the comment should be displayed by formatting tools. This might be set to "false" if you want to keep a comment in a document after the contents of the comment have already been dealt with. Allowed values: o "true" (default) o "false"2.16.3. "source" Attribute
Holds the "source" of a comment, such as the name or the initials of the person who made the comment.2.17. <date>
Provides information about the publication date. This element is used for two cases: the boilerplate of the document being produced, and inside bibliographic references that use the <front> element. Boilerplate for Internet-Drafts and RFCs: This element defines the date of publication for the current document (Internet-Draft or RFC). When producing Internet-Drafts, the prep tool uses this date to compute the expiration date (see [IDGUIDE]). When one or more of "year", "month", or "day" are left out, the prep tool will attempt to use the current system date if the attributes that are present are consistent with that date. In dates in <rfc> elements, the month must be a number or a month in English. The prep tool will silently change text month names to numbers. Similarly, the year must be a four-digit number.
When the prep tool is used to create Internet-Drafts, it will
reject a submitted Internet-Draft that has a <date> element in the
boilerplate for itself that is anything other than today. That
is, the tool will not allow a submitter to specify a date other
than the day of submission. To avoid this problem, authors might
simply not include a <date> element in the boilerplate.
Bibliographic references: In dates in <reference> elements, the date
information can 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.26).
Content model: this element does not have any contents.
2.17.1. "day" Attribute
The day of publication.
2.17.2. "month" Attribute
The month or months of publication.
2.17.3. "year" Attribute
The year or years of publication.
2.18. <dd>
The definition part of an entry in a definition list.
This element appears as a child element of <dl> (Section 2.20).
Content model:
Either:
In any order, but at least one of:
* <artwork> elements (Section 2.5)
* <dl> elements (Section 2.20)
* <figure> elements (Section 2.25)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
Or:
In any order, but at least one of:
* Text
* <bcp14> elements (Section 2.9)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
2.18.1. "anchor" Attribute
Document-wide unique identifier for this definition.
2.19. <displayreference>
This element gives a mapping between the anchor of a reference and a name that will be displayed instead. This allows authors to display more mnemonic anchor names for automatically included references. The mapping in this element only applies to <xref> elements whose format is "default". For example, if the reference uses the anchor "RFC6949", the following would cause that anchor in the body of displayed documents to be "RFC-dev": <displayreference target="RFC6949" to="RFC-dev"/> If a reference section is sorted, this element changes the sort order. It is expected that this element will only be valid in input documents. It will likely be removed by prep tools when preparing a final version after those tools have replaced all of the associated anchors, targets, and "derivedContent" attributes. This element appears as a child element of <back> (Section 2.8). Content model: this element does not have any contents.2.19.1. "target" Attribute (Mandatory)
This attribute must be the name of an anchor in a <reference> or <referencegroup> element.2.19.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, or A-Z. The other characters in the string must be 0-9, a-z, A-Z, "-", ".", or "_".2.20. <dl>
A definition list. Each entry has a pair of elements: a term (<dt>) and a definition (<dd>). (This is slightly different and simpler than the model used in HTML, which allows for multiple terms for a single definition.) This element appears as a child element of <abstract> (Section 2.1), <aside> (Section 2.6), <blockquote> (Section 2.10), <dd> (Section 2.18), <li> (Section 2.29), <note> (Section 2.33), <section> (Section 2.46), <td> (Section 2.56), and <th> (Section 2.58).
Content model: One or more sequences of: 1. One <dt> element 2. One <dd> element2.20.1. "anchor" Attribute
Document-wide unique identifier for the list.2.20.2. "hanging" Attribute
The "hanging" attribute defines whether or not the term appears on the same line as the definition. hanging="true" indicates that the term is to the left of the definition, while hanging="false" indicates that the term will be on a separate line. Allowed values: o "false" o "true" (default)2.20.3. "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"
2.21. <dt>
The term being defined in a definition list. This element appears as a child element of <dl> (Section 2.20). Content model: In any order: o Text o <bcp14> elements (Section 2.9) o <cref> elements (Section 2.16) o <em> elements (Section 2.22) o <eref> elements (Section 2.24) o <iref> elements (Section 2.27) o <relref> elements (Section 2.44) o <strong> elements (Section 2.50) o <sub> elements (Section 2.51) o <sup> elements (Section 2.52) o <tt> elements (Section 2.62) o <xref> elements (Section 2.66)2.21.1. "anchor" Attribute
Document-wide unique identifier for this term.
2.22. <em>
Indicates text that is semantically emphasized. Text enclosed within this element will be displayed as italic after processing. 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.10), <cref> (Section 2.16), <dd> (Section 2.18), <dt> (Section 2.21), <li> (Section 2.29), <preamble> (Section 3.6), <refcontent> (Section 2.39), <strong> (Section 2.50), <sub> (Section 2.51), <sup> (Section 2.52), <t> (Section 2.53), <td> (Section 2.56), <th> (Section 2.58), and <tt> (Section 2.62). Content model: In any order: o Text o <bcp14> elements (Section 2.9) o <cref> elements (Section 2.16) o <eref> elements (Section 2.24) o <iref> elements (Section 2.27) o <relref> elements (Section 2.44) o <strong> elements (Section 2.50) o <sub> elements (Section 2.51) o <sup> elements (Section 2.52) o <tt> elements (Section 2.62) o <xref> elements (Section 2.66)
2.23. <email>
Provides an email address. The value is expected to be the addr-spec defined in Section 2 of [RFC6068]. This element appears as a child element of <address> (Section 2.2). Content model: only text content.2.23.1. "ascii" Attribute
The ASCII equivalent of the author's email address. This is only used if the email address has any internationalized components.2.24. <eref>
Represents an "external" link (as specified in the "target" attribute). This is useful for embedding URIs in the body of a document. If the <eref> element has non-empty text content, formatters should use the content as the displayed text that is linked. Otherwise, the formatter should use the value of the "target" attribute as the displayed text. Formatters will link the displayed text to the value of the "target" attribute in a manner appropriate for the output format. For example, with an input of: This is described at <eref target="http://www.example.com/reports/r12.html"/>. An HTML formatter might generate: This is described at <a href="http://www.example.com/reports/r12.html"> http://www.example.com/reports/r12.html</a>.
With an input of:
This is described
<eref target="http://www.example.com/reports/r12.html">
in this interesting report</eref>.
An HTML formatter might generate:
This is described
<a href="http://www.example.com/reports/r12.html">
in this interesting report</a>.
This element appears as a child element of <annotation>
(Section 2.3), <blockquote> (Section 2.10), <c> (Section 3.1), <cref>
(Section 2.16), <dd> (Section 2.18), <dt> (Section 2.21), <em>
(Section 2.22), <li> (Section 2.29), <name> (Section 2.32),
<postamble> (Section 3.5), <preamble> (Section 3.6), <strong>
(Section 2.50), <sub> (Section 2.51), <sup> (Section 2.52), <t>
(Section 2.53), <td> (Section 2.56), <th> (Section 2.58), <tt>
(Section 2.62), and <ttcol> (Section 3.9).
Content model: only text content.
2.24.1. "target" Attribute (Mandatory)
URI of the link target [RFC3986]. This must begin with a scheme name
(such as "https://") and thus not be relative to the URL of the
current document.
2.25. <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.10), <dd> (Section 2.18), <li>
(Section 2.29), <section> (Section 2.46), <td> (Section 2.56), and
<th> (Section 2.58).
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: * <artwork> elements (Section 2.5) * <sourcecode> elements (Section 2.48) 5. One optional <postamble> element (Section 3.5)2.25.1. "align" Attribute
Deprecated. Note: does not affect title or <artwork> alignment. Allowed values: o "left" (default) o "center" o "right"2.25.2. "alt" Attribute
Deprecated. If the goal is to provide a single URI for a reference, use the "target" attribute in <reference> instead.2.25.3. "anchor" Attribute
Document-wide unique identifier for this figure.2.25.4. "height" Attribute
Deprecated.2.25.5. "src" Attribute
Deprecated.
2.25.6. "suppress-title" Attribute
Deprecated. Allowed values: o "true" o "false" (default)2.25.7. "title" Attribute
Deprecated. Use <name> instead.2.25.8. "width" Attribute
Deprecated.2.26. <front>
Represents the "front matter": metadata (such as author information), the Abstract, and additional notes. A <front> element may have more than one <seriesInfo> element. A <seriesInfo> element determines the document number (for RFCs) or name (for Internet-Drafts). Another <seriesInfo> element determines the "maturity level" (defined in [RFC2026]), using values of "std" for "Standards Track", "bcp" for "BCP", "info" for "Informational", "exp" for "Experimental", and "historic" for "Historic". The "name" attributes of those multiple <seriesInfo> elements interact as described in Section 2.47. This element appears as a child element of <reference> (Section 2.40) and <rfc> (Section 2.45). Content model: In this order: 1. One <title> element (Section 2.60) 2. Optional <seriesInfo> elements (Section 2.47) 3. One or more <author> elements (Section 2.7) 4. One optional <date> element (Section 2.17) 5. Optional <area> elements (Section 2.4)
6. Optional <workgroup> elements (Section 2.65) 7. Optional <keyword> elements (Section 2.28) 8. One optional <abstract> element (Section 2.1) 9. Optional <note> elements (Section 2.33) 10. One optional <boilerplate> element (Section 2.11)2.27. <iref>
Provides terms for the document's index. Index entries can be either regular entries (when just the "item" attribute is given) or nested entries (by specifying "subitem" as well), grouped under a regular entry. Index entries generally refer to the exact place where the <iref> element occurred. An exception is the occurrence as a child element of <section>, in which case the whole section is considered to be relevant for that index entry. In some formats, index entries of this type might be displayed as ranges. When the prep tool is creating index content, it collects the items in a case-sensitive fashion for both the item and subitem level. This element appears as a child element of <annotation> (Section 2.3), <aside> (Section 2.6), <blockquote> (Section 2.10), <c> (Section 3.1), <dd> (Section 2.18), <dt> (Section 2.21), <em> (Section 2.22), <figure> (Section 2.25), <li> (Section 2.29), <postamble> (Section 3.5), <preamble> (Section 3.6), <section> (Section 2.46), <strong> (Section 2.50), <sub> (Section 2.51), <sup> (Section 2.52), <t> (Section 2.53), <table> (Section 2.54), <td> (Section 2.56), <th> (Section 2.58), <tt> (Section 2.62), 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. There is no restriction on the number of occurrences that can be "primary". 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.26). 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.63). Content model: Either: In any order, but at least one of: * <artwork> elements (Section 2.5) * <dl> elements (Section 2.20) * <figure> elements (Section 2.25)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
Or:
In any order, but at least one of:
* Text
* <bcp14> elements (Section 2.9)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
2.29.1. "anchor" Attribute
Document-wide unique identifier for this list item.
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 International Standard Serial Number (ISSN) for the RFC Series. The value for the "rel" attribute is "item". The link should use the form "urn:issn:". o The Digital Object Identifier (DOI) for this document. The value for the "rel" attribute is "describedBy". The link should use the form specified in [RFC7669]; this is expected to change in the future. 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. In RFC production mode, the prep tool needs to check the values for <link> before an RFC is published. In draft production mode, the prep tool might remove some <link> elements during the draft submission process. This element appears as a child element of <rfc> (Section 2.45). Content model: this element does not have any contents.2.30.1. "href" Attribute (Mandatory)
The URI of the external document.2.30.2. "rel" Attribute
The relationship of the external document to this one. The relationships are taken from the "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.45). Content model: One or more <section> elements (Section 2.46)2.32. <name>
The name of the section, note, figure, or texttable. This name can indicate markup of flowing text (for example, including references or making some characters use a fixed-width font). This element appears as a child element of <figure> (Section 2.25), <note> (Section 2.33), <references> (Section 2.42), <section> (Section 2.46), <table> (Section 2.54), and <texttable> (Section 3.8). Content model: In any order: o Text o <cref> elements (Section 2.16) o <eref> elements (Section 2.24) o <relref> elements (Section 2.44) o <tt> elements (Section 2.62) o <xref> elements (Section 2.66)2.33. <note>
Creates an unnumbered, titled block of text that appears after the Abstract. It is usually used for additional information to reviewers (Working Group information, mailing list, ...) or for additional publication information such as "IESG Notes". This element appears as a child element of <front> (Section 2.26).
Content model: In this order: 1. One optional <name> element (Section 2.32) 2. In any order, but at least one of: * <dl> elements (Section 2.20) * <ol> elements (Section 2.34) * <t> elements (Section 2.53) * <ul> elements (Section 2.63)2.33.1. "removeInRFC" Attribute
If set to "true", this note is marked in the prep tool with text indicating that it should be removed before the document is published as an RFC. That text will be "This note is to be removed before publishing as an RFC." Allowed values: o "true" o "false" (default)2.33.2. "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 <abstract> (Section 2.1), <aside> (Section 2.6), <blockquote> (Section 2.10), <dd> (Section 2.18), <li> (Section 2.29), <note> (Section 2.33), <section> (Section 2.46), <td> (Section 2.56), and <th> (Section 2.58). Content model: One or more <li> elements (Section 2.29)
2.34.1. "anchor" Attribute
Document-wide unique identifier for the list.2.34.2. "group" Attribute
When the prep tool sees an <ol> element with a "group" attribute that has already been seen, it continues the numbering of the list from where the previous list with the same group name left off. If an <ol> element has both a "group" attribute and a "start" attribute, the group's numbering is reset to the given start value.2.34.3. "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"2.34.4. "start" Attribute
The ordinal value at which to start the list. This defaults to "1" and must be an integer of 0 or greater.2.34.5. "type" Attribute
The type of the labels on list items. If the length of the type value is 1, the meaning is the same as it is for HTML: a Lowercase letters (a, b, c, ...) A Uppercase letters (A, B, C, ...) 1 Decimal numbers (1, 2, 3, ...) i Lowercase Roman numerals (i, ii, iii, ...) I Uppercase Roman numerals (I, II, III, ...) For types "a" and "A", after the 26th entry, the numbering starts at "aa"/"AA", then "ab"/"AB", and so on.
If the length of the type value is greater than 1, the value must contain a percent-encoded indicator and other text. The value is a free-form text that allows counter values to be inserted using a "percent-letter" format. For instance, "[REQ%d]" generates labels of the form "[REQ1]", where "%d" inserts the item number as a decimal number. The following formats are supported: %c Lowercase letters (a, b, c, ...) %C Uppercase letters (A, B, C, ...) %d Decimal numbers (1, 2, 3, ...) %i Lowercase Roman numerals (i, ii, iii, ...) %I Uppercase Roman numerals (I, II, III, ...) %% Represents a percent sign Other formats are reserved for future use. Only one percent encoding other than "%%" is allowed in a type string. It is an error for the type string to be empty. For bulleted lists, use the <ul> element. For lists that have neither bullets nor numbers, use the <ul> element with the 'empty="true"' attribute. If no type attribute is given, the default type is the same as "type='%d.'".2.35. <organization>
Specifies the affiliation [RFC7322] of an author. This information appears both in the "Author's Address" section and on the front page (see [RFC7322] for more information). If the value is long, an abbreviated variant can be specified in the "abbrev" attribute. This element 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 (and so does not include the prefix "tel:"), using the "global-number-digits" 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 specific to formatters. A postal address can contain only a set of <street>, <city>, <region>, <code>, and <country> elements, or only an ordered set of <postalLine> elements, but not both. This element appears as a child element of <address> (Section 2.2). Content model: Either: In any order: * <city> elements (Section 2.13) * <code> elements (Section 2.14) * <country> elements (Section 2.15) * <region> elements (Section 2.43) * <street> elements (Section 2.49) Or: One or more <postalLine> elements (Section 2.38)
(next page on part 3)
