Internet Architecture Board (IAB) P. Hoffman
Request for Comments: 7991 ICANN
Obsoletes: 7749 December 2016
Category: Informational
ISSN: 2070-1721
Internet Architecture Board (IAB) P. Hoffman
Request for Comments: 7991 ICANN
Obsoletes: 7749 December 2016
Category: Informational
ISSN: 2070-1721
The "xml2rfc" Version 3 Vocabulary
“xml2rfc”版本3词汇表
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 7749.
本文档定义了“xml2rfc”版本3词汇表：一种用于编写RFC和Internet草稿的基于XML的语言。它在很大程度上来源于正在讨论的第2版词汇表。本文档废弃了RFC 7749中描述的v2语法。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Architecture Board (IAB) and represents information that the IAB has deemed valuable to provide for permanent record. It represents the consensus of the Internet Architecture Board (IAB). Documents approved for publication by the IAB are not a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网体系结构委员会（IAB）的产品，代表IAB认为有价值提供永久记录的信息。它代表了互联网体系结构委员会（IAB）的共识。IAB批准发布的文件不适用于任何级别的互联网标准；见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7991.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7991.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction ....................................................5
1.1. Expected Updates to the Specification ......................5
1.2. Design Criteria for the Changes in v3 ......................6
1.3. Differences from v2 to v3 ..................................6
1.3.1. New Elements in v3 ..................................6
1.3.2. New Attributes for Existing Elements ................7
1.3.3. Elements and Attributes Deprecated from v2 ..........8
1.3.4. Additional Changes from v2 ..........................9
1.4. Syntax Notation ...........................................10
2. Elements .......................................................10
2.1. <abstract> ................................................11
2.2. <address> .................................................12
2.3. <annotation> ..............................................12
2.4. <area> ....................................................13
2.5. <artwork> .................................................13
2.6. <aside> ...................................................17
2.7. <author> ..................................................18
2.8. <back> ....................................................19
2.9. <bcp14> ...................................................20
2.10. <blockquote> .............................................20
2.11. <boilerplate> ............................................22
2.12. <br> .....................................................22
2.13. <city> ...................................................22
2.14. <code> ...................................................22
2.15. <country> ................................................23
2.16. <cref> ...................................................23
2.17. <date> ...................................................24
2.18. <dd> .....................................................25
2.19. <displayreference> .......................................27
2.20. <dl> .....................................................27
2.21. <dt> .....................................................29
2.22. <em> .....................................................30
2.23. <email> ..................................................31
2.24. <eref> ...................................................31
2.25. <figure> .................................................32
2.26. <front> ..................................................34
2.27. <iref> ...................................................35
2.28. <keyword> ................................................36
2.29. <li> .....................................................36
2.30. <link> ...................................................38
2.31. <middle> .................................................39
2.32. <name> ...................................................39
2.33. <note> ...................................................39
2.34. <ol> .....................................................40
2.35. <organization> ...........................................42
1. Introduction ....................................................5
1.1. Expected Updates to the Specification ......................5
1.2. Design Criteria for the Changes in v3 ......................6
1.3. Differences from v2 to v3 ..................................6
1.3.1. New Elements in v3 ..................................6
1.3.2. New Attributes for Existing Elements ................7
1.3.3. Elements and Attributes Deprecated from v2 ..........8
1.3.4. Additional Changes from v2 ..........................9
1.4. Syntax Notation ...........................................10
2. Elements .......................................................10
2.1. <abstract> ................................................11
2.2. <address> .................................................12
2.3. <annotation> ..............................................12
2.4. <area> ....................................................13
2.5. <artwork> .................................................13
2.6. <aside> ...................................................17
2.7. <author> ..................................................18
2.8. <back> ....................................................19
2.9. <bcp14> ...................................................20
2.10. <blockquote> .............................................20
2.11. <boilerplate> ............................................22
2.12. <br> .....................................................22
2.13. <city> ...................................................22
2.14. <code> ...................................................22
2.15. <country> ................................................23
2.16. <cref> ...................................................23
2.17. <date> ...................................................24
2.18. <dd> .....................................................25
2.19. <displayreference> .......................................27
2.20. <dl> .....................................................27
2.21. <dt> .....................................................29
2.22. <em> .....................................................30
2.23. <email> ..................................................31
2.24. <eref> ...................................................31
2.25. <figure> .................................................32
2.26. <front> ..................................................34
2.27. <iref> ...................................................35
2.28. <keyword> ................................................36
2.29. <li> .....................................................36
2.30. <link> ...................................................38
2.31. <middle> .................................................39
2.32. <name> ...................................................39
2.33. <note> ...................................................39
2.34. <ol> .....................................................40
2.35. <organization> ...........................................42
2.36. <phone> ..................................................43
2.37. <postal> .................................................43
2.38. <postalLine> .............................................44
2.39. <refcontent> .............................................44
2.40. <reference> ..............................................45
2.41. <referencegroup> .........................................46
2.42. <references> .............................................46
2.43. <region> .................................................47
2.44. <relref> .................................................47
2.45. <rfc> ....................................................51
2.46. <section> ................................................54
2.47. <seriesInfo> .............................................57
2.48. <sourcecode> .............................................59
2.49. <street> .................................................61
2.50. <strong> .................................................61
2.51. <sub> ....................................................62
2.52. <sup> ....................................................63
2.53. <t> ......................................................64
2.54. <table> ..................................................66
2.55. <tbody> ..................................................67
2.56. <td> .....................................................67
2.57. <tfoot> ..................................................69
2.58. <th> .....................................................69
2.59. <thead> ..................................................71
2.60. <title> ..................................................72
2.61. <tr> .....................................................72
2.62. <tt> .....................................................73
2.63. <ul> .....................................................74
2.64. <uri> ....................................................75
2.65. <workgroup> ..............................................75
2.66. <xref> ...................................................75
3. Elements from v2 That Have Been Deprecated .....................78
3.1. <c> .......................................................78
3.2. <facsimile> ...............................................78
3.3. <format> ..................................................79
3.4. <list> ....................................................79
3.5. <postamble> ...............................................80
3.6. <preamble> ................................................81
3.7. <spanx> ...................................................81
3.8. <texttable> ...............................................82
3.9. <ttcol> ...................................................83
3.10. <vspace> .................................................84
4. SVG ............................................................84
5. Use of CDATA Structures and Escaping ...........................85
6. Internationalization Considerations ............................85
7. Security Considerations ........................................85
2.36. <phone> ..................................................43
2.37. <postal> .................................................43
2.38. <postalLine> .............................................44
2.39. <refcontent> .............................................44
2.40. <reference> ..............................................45
2.41. <referencegroup> .........................................46
2.42. <references> .............................................46
2.43. <region> .................................................47
2.44. <relref> .................................................47
2.45. <rfc> ....................................................51
2.46. <section> ................................................54
2.47. <seriesInfo> .............................................57
2.48. <sourcecode> .............................................59
2.49. <street> .................................................61
2.50. <strong> .................................................61
2.51. <sub> ....................................................62
2.52. <sup> ....................................................63
2.53. <t> ......................................................64
2.54. <table> ..................................................66
2.55. <tbody> ..................................................67
2.56. <td> .....................................................67
2.57. <tfoot> ..................................................69
2.58. <th> .....................................................69
2.59. <thead> ..................................................71
2.60. <title> ..................................................72
2.61. <tr> .....................................................72
2.62. <tt> .....................................................73
2.63. <ul> .....................................................74
2.64. <uri> ....................................................75
2.65. <workgroup> ..............................................75
2.66. <xref> ...................................................75
3. Elements from v2 That Have Been Deprecated .....................78
3.1. <c> .......................................................78
3.2. <facsimile> ...............................................78
3.3. <format> ..................................................79
3.4. <list> ....................................................79
3.5. <postamble> ...............................................80
3.6. <preamble> ................................................81
3.7. <spanx> ...................................................81
3.8. <texttable> ...............................................82
3.9. <ttcol> ...................................................83
3.10. <vspace> .................................................84
4. SVG ............................................................84
5. Use of CDATA Structures and Escaping ...........................85
6. Internationalization Considerations ............................85
7. Security Considerations ........................................85
8. IANA Considerations ............................................86
8.1. Internet Media Type Registration ..........................86
8.2. Link Relation Registration ................................87
9. References .....................................................88
9.1. Normative References ......................................88
9.2. Informative References ....................................88
Appendix A. Front-Page ("Boilerplate") Generation .................93
A.1. The "ipr" Attribute ........................................93
A.1.1. Current Values: "*trust200902" .........................93
A.1.2. Historic Values ........................................95
A.2. The "submissionType" Attribute .............................96
A.3. The "consensus" Attribute ..................................97
Appendix B. The v3 Format and Processing Tools ....................98
B.1. Including External Text with XInclude ......................99
B.2. Anchors and IDs ...........................................100
B.2.1. Overlapping Values ....................................100
B.3. Attributes Controlled by the Prep Tool ....................102
Appendix C. RELAX NG Schema ......................................104
Appendix D. Schema Differences from v2 ...........................127
IAB Members at the Time of Approval ..............................151
Acknowledgements .................................................151
Author's Address .................................................151
8. IANA Considerations ............................................86
8.1. Internet Media Type Registration ..........................86
8.2. Link Relation Registration ................................87
9. References .....................................................88
9.1. Normative References ......................................88
9.2. Informative References ....................................88
Appendix A. Front-Page ("Boilerplate") Generation .................93
A.1. The "ipr" Attribute ........................................93
A.1.1. Current Values: "*trust200902" .........................93
A.1.2. Historic Values ........................................95
A.2. The "submissionType" Attribute .............................96
A.3. The "consensus" Attribute ..................................97
Appendix B. The v3 Format and Processing Tools ....................98
B.1. Including External Text with XInclude ......................99
B.2. Anchors and IDs ...........................................100
B.2.1. Overlapping Values ....................................100
B.3. Attributes Controlled by the Prep Tool ....................102
Appendix C. RELAX NG Schema ......................................104
Appendix D. Schema Differences from v2 ...........................127
IAB Members at the Time of Approval ..............................151
Acknowledgements .................................................151
Author's Address .................................................151
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].
本文档描述了“xml2rfc”词汇表的第3版（“v3”）：一种基于XML的语言（“可扩展标记语言”[XML]），用于编写RFC[RFC7322]和Internet草稿[IDGUIDE]。
This document obsoletes the version 2 vocabulary ("v2") [RFC7749], which contains the extended language definition. That document in turn obsoletes the original version ("v1") [RFC2629]. This document directly copies the material from [RFC7749] where possible.
本文档淘汰了包含扩展语言定义的版本2词汇表（“v2”）[RFC7749]。该文件进而淘汰了原始版本（“v1”）[RFC2629]。本文件尽可能直接从[RFC7749]复制材料。
The v3 format will be used as part of the new RFC Series format described in [RFC6949]. The new format will be handled by one or more new tools for preparing the XML and converting it to other representations. Features of the expected tools are described in Appendix B. That section defines some terms used throughout this document, such as "prep tool" and "formatter".
v3格式将用作[RFC6949]中描述的新RFC系列格式的一部分。新格式将由一个或多个新工具处理，用于准备XML并将其转换为其他表示形式。预期工具的功能在附录B中描述。该部分定义了本文档中使用的一些术语，如“准备工具”和“格式化程序”。
Note that the vocabulary contains certain constructs that might not be used when generating 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 instantiation of a format, such as an XML document or an HTML document that was created by an XML document.
在本文档中，术语“格式”用于描述文档类型，主要是XML和HTML。术语“表示”用于讨论格式的特定实例化，例如XML文档或由XML文档创建的HTML文档。
Non-interoperable changes in later versions of this specification are likely based on experience gained in implementing the new publication toolsets. Revised documents will be published capturing those changes as the toolsets are completed. Other implementers must not expect those changes to remain backwards-compatible with the details described in this document.
本规范更高版本中不可互操作的更改可能基于在实现新发布工具集过程中获得的经验。修订后的文档将在工具集完成后发布，以捕获这些更改。其他实施者不得期望这些更改与本文档中描述的细节保持向后兼容。
The design criteria of the changes from v2 to v3 are as follows:
从v2到v3的变更设计标准如下：
o The intention is that starting and editing a v3 document will be easier than for a v2 document.
o 其目的是，启动和编辑v3文档将比启动和编辑v2文档更容易。
o There will be good v2-to-v3 conversion tools for when an author wants to change versions.
o 当作者想要更改版本时，会有很好的v2到v3转换工具。
o There are no current plans to make v3 XML the required submission format for drafts or RFCs. That might happen eventually, but it is likely to be years away.
o 目前没有计划将V3XML作为草稿或RFC所需的提交格式。这最终可能会发生，但很可能还要几年。
There is a desire to keep as much of the v2 grammar as makes sense 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 backwards 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.
人们希望在上述设计标准范围内尽可能多地保留v2语法，而不是对v2语法进行无谓的更改。另一种说法是“我们更愿意鼓励向后兼容，但不受其限制”。不过，考虑到后两个设计标准，启动和编辑v3文档比编辑v2文档更容易的目标比与v2的向后兼容更重要。
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.3.3 and are described in [RFC7749].
v3与v2向上兼容，这意味着v2文档也应该是有效的v3文档。然而，v2的一些特性在v3中被弃用，取而代之的是新元素。第1.3.3节列出了不推荐的功能，并在[RFC7749]中进行了说明。
This is a (hopefully) complete list of all the technical changes between [RFC7749] and this document.
这是[RFC7749]与本文件之间所有技术变更的完整列表（希望如此）。
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 and other lists instead of <t>.
o 添加<dl>、<ul>和<ol>作为制作列表的新方法。与v2相比，这是一个显著的变化，因为这些元素下的子元素是<li>，而不是<t><li>的模型包含一个或多个<t>元素，或者包含通常在<t>中找到的流动文本。这些列表是<section>s和其他列表的子列表，而不是<t>。
o Add <strong>, <em>, <tt>, <sub>, and <sup> for character formatting.
o 为字符格式添加<strong>、<em>、<tt>、<sub>和<sup>。
o Add <aside> for incidental text that will be indented when displayed.
o 为显示时将缩进的附带文本添加<aside>。
o Add <sourcecode> to differentiate from <artwork>.
o 添加<sourcecode>以区别于<artwork>。
o Add <table>, <thead>, <tbody>, <tfoot>, <tr>, <td>, and <th> to give table functionality like that in HTML.
o 添加<table>、<thead>、<tbody>、<tfoot>、<tr>、<td>和<th>以提供类似HTML的表格功能。
o Add <boilerplate> to hold the automatically generated boilerplate text.
o 添加<boilerplate>以保存自动生成的样板文本。
o Add <blockquote> to indicate a quotation as in a paragraph-like format.
o 添加<blockquote>以类似段落的格式指示引用。
o Add <name> to sections, notes, figures, and texttables to allow character formatting (fixed-width font) in their titles and to allow references in the names.
o 将<name>添加到节、注释、数字和文本表中，以允许在标题中使用字符格式（固定宽度字体），并允许在名称中使用引用。
o Add <postalLine>, free text that represents one line of the address.
o 添加<postalLine>，表示一行地址的自由文本。
o Add <displayreference> to allow display of more mnemonic anchor names for automatically included references.
o 添加<displayreference>以允许为自动包含的引用显示更多助记符锚定名称。
o Add <refcontent> to allow better control of text in a reference.
o 添加<refcontent>，以便更好地控制引用中的文本。
o Add <referencegroup> to allow referencing multi-RFC documents such as STDs and BCPs.
o 添加<referencegroup>以允许引用多个RFC文档，如STD和BCP。
o Add <relref> to allow referencing specific sections or anchors in references.
o 添加<relref>以允许引用引用中的特定节或锚定。
o Add <link> to point to a resource related to the RFC.
o 添加<link>指向与RFC相关的资源。
o Add <br> to allow line breaks (but not blank lines) in the generated output for table cells.
o 添加<br>以允许在为表格单元格生成的输出中使用换行符（而不是空行）。
o Add <svg> to allow easy inclusion of SVG drawings in <artwork>.
o 添加<svg>，以便在<artwork>中轻松包含svg图形。
o Add "sortRefs", "symRefs", "tocDepth", and "tocInclude" attributes to <rfc> to cover Processing Instructions (PIs) that were in v2 that are still needed in the grammar. Add "prepTime" to indicate the time that the XML went through a preparation step. Add "version" to indicate the version of xml2rfc vocabulary used in the document. Add "scripts" to indicate which scripts are needed to render the document. Add "expiresDate" when an Internet-Draft expires.
o 将“sortRefs”、“symRefs”、“tocDepth”和“tocclude”属性添加到<rfc>，以涵盖v2中语法中仍然需要的处理指令（pi）。添加“prepTime”以指示XML完成准备步骤的时间。添加“版本”以指示文档中使用的xml2rfc词汇表的版本。添加“脚本”以指示呈现文档需要哪些脚本。在Internet草稿过期时添加“expiresDate”。
o Add "ascii" attributes to <email>, <organization>, <street>, <city>, <region>, <country>, and <code>. Also add "asciiFullname", "asciiInitials", and "asciiSurname" to <author>. 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 将“ascii”属性添加到<email>、<organization>、<street>、<city>、<region>、<country>和<code>。同时在<author>中添加“asciiFullname”、“asciiInitials”和“asciiSurname”。这允许作者在其本机脚本中将其信息指定为主要条目，并且仍然允许在处理的文档中显示ASCII等效值。
o Add "anchor" attributes to many block elements to allow them to be linked with <relref> and <xref>.
o 向许多块元素添加“锚定”属性，以允许它们与<relref>和<xref>链接。
o Add the "section", "relative", and "sectionFormat" attributes to <xref>.
o 将“section”、“relative”和“sectionFormat”属性添加到<xref>。
o Add the "numbered" and "removeInRFC" attributes to <section>.
o 将“编号”和“删除”属性添加到<section>。
o Add the "removeInRFC" attribute to <note>.
o 将“removeInRFC”属性添加到<note>。
o Add "pn" to <artwork>, <aside>, <blockquote>, <boilerplate>, <dt>, <figure>, <iref>, <li>, <references>, <section>, <sourcecode>, <t>, and <table> to hold automatically generated numbers for items in a section that don't have their own numbering (namely figures and tables).
o 将“pn”添加到<artwork>、<Side>、<blockquote>、<boilerplate>、<dt>、<figure>、<iref>、<li>、<references>、<section>、<sourcecode>、<t>和<table>中，以保存节中没有自己编号的项（即图和表）的自动生成的编号。
o Add "display" to <cref> to indicate to tools whether or not to display the comment.
o 将“显示”添加到<cref>以指示工具是否显示注释。
o Add "keepWithNext" and "keepWithPrevious" to <t> as a hint to tools that do pagination that they should try to keep the paragraph with the next/previous element.
o 将“keepWithNext”和“keepWithPrevious”添加到<t>中，作为对分页工具的提示，提示它们应该尝试使用next/previous元素保留段落。
Deprecated elements and attributes are legacy vocabulary from v2 that are supported for input to v3 tools. They are likely to be removed from those tools in the future. Deprecated attributes are still listed in Section 2, and deprecated elements are listed in Section 3. See Appendix B for more information on tools and how they will handle deprecated features.
不推荐使用的元素和属性是v2中的遗留词汇表，支持输入到v3工具。将来可能会从这些工具中删除它们。不推荐使用的属性仍列在第2节中，不推荐使用的元素列在第3节中。有关工具以及如何处理不推荐的功能的更多信息，请参见附录B。
o Deprecate <list> in favor of <dl>, <ul>, and <ol>.
o 反对<list>而赞成<dl>、<ul>和<ol>。
o Deprecate <spanx>; replace it with <strong>, <em>, and <tt>.
o 反对<spanx>；将其替换为<strong>、<em>和<tt>。
o Deprecate <vspace> because the major use for it, creating pseudo-paragraph-breaks in lists, is now handled properly.
o 不推荐使用<vspace>，因为它的主要用途是在列表中创建伪段落分隔符，现在已得到正确处理。
o Deprecate <texttable>, <ttcol>, and <c>; replace them with the new table elements (<table> and the elements that can be contained within it).
o 反对<texttable>、<ttcol>和<c>；将它们替换为新的表元素（<table>和可包含在其中的元素）。
o Deprecate <facsimile> because it is rarely used.
o 不推荐使用<fax>，因为它很少使用。
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 in <reference> instead.
o 不赞成<format>，因为它没有用处，过去曾让作者感到惊讶。如果目标是为引用提供单个URI（统一资源标识符），请使用<reference>中的“target”属性。
o Deprecate <preamble> and <postamble> in favor of simply using <t> before or after the figure. This also deprecates the "align" attribute in <figure>.
o 不赞成使用<preamble>和<postmble>，而赞成在图形之前或之后使用<t>。这也不赞成<figure>中的“align”属性。
o Deprecate the "title" attribute in <section>, <note>, <figure>, <references>, and <texttable> in favor of the new <name>.
o 反对<section>、<note>、<figure>、<references>和<texttable>中的“title”属性，支持新的<name>。
o Deprecate the "alt" and "src" attributes in <figure> because they overlap with the attributes in <artwork>.
o 反对<figure>中的“alt”和“src”属性，因为它们与<artwork>中的属性重叠。
o Deprecate the "xml:space" attribute in <artwork> because there was only one useful value. Deprecate the "height" and "width" attributes in both <artwork> and <figure> because they are not needed for the new output formats.
o 不推荐<artwork>中的“xml:space”属性，因为只有一个有用的值。不推荐<artwork>和<figure>中的“高度”和“宽度”属性，因为新的输出格式不需要它们。
o Deprecate the "pageno" attribute in <xref> because it was unused in v2. Deprecate the "none" values for the "format" attribute in <xref> because it makes no sense semantically.
o 不推荐使用<xref>中的“pageno”属性，因为它在v2中未使用。反对使用<xref>中“format”属性的“none”值，因为它在语义上没有意义。
o Allow non-ASCII characters in the format; the characters that are actually allowed will be determined by the RFC Series Editor.
o 允许格式中包含非ASCII字符；实际允许的字符将由RFC系列编辑器确定。
o Allow <artwork> and <sourcecode> to be used on their own in <section> (no longer confine them to a figure).
o 允许<artwork>和<sourcecode>在<section>中单独使用（不再局限于图形）。
o Give more specifics of handling the "type" attribute in <artwork>.
o 给出处理<artwork>中“type”属性的更多细节。
o Allow <strong>, <em>, <tt>, <eref>, and <xref> in <cref>.
o 在<cref>中允许<strong>、<em>、<tt>、<eref>和<xref>。
o Allow the sub-elements inside a <reference> to be in any order.
o 允许<reference>中的子元素按任意顺序排列。
o Turn off the autogeneration of anchors in <cref> because there is no use case for them that cannot be achieved in other ways.
o 在<cref>中关闭锚的自动生成，因为没有其他方法无法实现的用例。
o Allow more than one <artwork>, or more than one <sourcecode>, in <figure>.
o 在<figure>中允许多个<artwork>，或多个<sourcecode>。
o In <front>, make <date> optional.
o 在<front>中，将<date>设置为可选。
o In <date>, add restrictions to the "date" and "year" attributes when used in the <front> for the document's boilerplate text.
o 在<date>中，为文档样板文本的<front>中使用的“date”和“year”属性添加限制。
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 在<postal>中，允许子元素按任意顺序排列。还允许包含新的<postalLine>，而不是旧的元素。
o In <section>, restrict the names of the anchors that can be used on some types of sections.
o 在<section>中，限制可在某些类型的节上使用的锚的名称。
o Make <seriesInfo> a child of <front>, and deprecated it as a child of <reference>. This also deprecates some of the attributes from <rfc> and moves them into <seriesInfo>.
o 将<serieinfo>设为<front>的子级，并不推荐将其作为<reference>的子级。这也会弃用<rfc>中的某些属性，并将它们移动到<serieinfo>。
o <t> now only contains non-block elements, so it no longer contains <figure> elements.
o <t> 现在只包含非块元素，因此不再包含<figure>元素。
o Do not generate the grammar from a DTD, but instead get it directly from the RELAX Next Generation (RNG) grammar [RNG].
o 不要从DTD生成语法，而是直接从RELAX下一代（RNG）语法[RNG]获取语法。
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)).
这里的XML词汇表是以散文形式定义的，基于附录C中包含的RELAXNG模式[RNC]（在RELAXNG紧凑表示法（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).
请注意，该模式可用于自动有效性检查，但某些约束仅以散文形式描述（例如：有条件地要求存在“abbrev”属性）。
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" (Section 2.3 of [XML]), additionally constrained to US-ASCII characters [USASCII]. Thus, the character repertoire consists of "A-Z", "a-z", "0-9", "_", "-", ".", and ":", where "0-9", ".", and "-" are disallowed as start characters. Anchors are described in more detail in Appendix B.2.
许多元素具有可选的“锚定”属性。在所有情况下，“锚定”属性的值都必须是有效的XML“名称”（XML第2.3节），另外还必须限制为US-ASCII字符[USASCII]。因此，字符集由“A-Z”、“A-Z”、“0-9”、“_“、“-”和“：”组成，其中“0-9”、“”和“-”不允许作为起始字符。附录B.2对锚进行了更详细的描述。
Tools interpreting the XML described here will collapse horizontal whitespace and line breaks to a single whitespace (except inside <artwork> and <sourcecode>) and will trim leading and trailing whitespace. Tab characters (U+0009) inside <artwork> and <sourcecode> are prohibited.
解释此处描述的XML的工具将水平空格和换行符折叠为单个空格（除了<artwork>和<sourcecode>内部），并将修剪前导和尾随空格。禁止<artwork>和<sourcecode>中的制表符（U+0009）。
Some of the elements have attributes that are not described in this section because those attributes are specific to the prep tool. People writing tools to process this format should read all of the appendices for a complete description of these attributes.
某些元素具有本节中未描述的属性，因为这些属性特定于准备工具。编写处理此格式的工具的人员应阅读所有附录，以获得这些属性的完整描述。
Every element in the v3 vocabulary can have an "xml:lang" attribute, an "xml:base" attribute, or both. The xml:lang attribute specifies the language used in the element. This is sometimes useful for renderers that display different fonts for ideographic characters used in China and Japan. The xml:base attribute is sometimes added to an XML file when doing XML-to-XML conversion where the base file has XInclude attributes (see Appendix B.1).
v3词汇表中的每个元素都可以有“xml:lang”属性、“xml:base”属性，或者两者都有。lang属性指定元素中使用的语言。这对于显示中国和日本使用的表意文字的不同字体的渲染器有时很有用。在进行xml到xml的转换时，有时会将xml:base属性添加到xml文件中，其中基本文件具有XInclude属性（参见附录B.1）。
Contains the Abstract of the document. See [RFC7322] for more information on restrictions for the Abstract.
包含文档的摘要。有关摘要限制的更多信息，请参见[RFC7322]。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model:
内容模型：
In any order, but at least one of:
以任何顺序，但至少一种：
o <dl> elements (Section 2.20)
o <dl>要素（第2.20节）
o <ol> elements (Section 2.34)
o <ol>要素（第2.34节）
o <t> elements (Section 2.53)
o <t> 要素（第2.53节）
o <ul> elements (Section 2.63)
o <ul>元件（第2.63节）
Document-wide unique identifier for the Abstract.
摘要的文档范围唯一标识符。
Provides address information for the author.
为作者提供地址信息。
This element appears as a child element of <author> (Section 2.7).
此元素显示为<author>的子元素（第2.7节）。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <postal> element (Section 2.37)
1. 一个可选的<postal>元素（第2.37节）
2. One optional <phone> element (Section 2.36)
2. 一个可选的<phone>元件（第2.36节）
3. One optional <facsimile> element (Section 3.2)
3. 一个可选<传真>元件（第3.2节）
4. One optional <email> element (Section 2.23)
4. 一个可选的<email>元素（第2.23节）
5. One optional <uri> element (Section 2.64)
5. 一个可选的<uri>元素（第2.64节）
Provides additional prose augmenting a bibliographic reference. This text is intended to be shown after the rest of the generated reference text.
提供补充书目参考的附加散文。该文本旨在显示在生成的其余参考文本之后。
This element appears as a child element of <reference> (Section 2.40).
此元素显示为<reference>的子元素（第2.40节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <spanx> elements (Section 3.7)
o <spanx>元件（第3.7节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Provides information about the IETF area to which this document relates (currently not used when generating documents).
提供与本文档相关的IETF区域的相关信息（当前在生成文档时未使用）。
The value ought to be either the full name or the abbreviation of one of the IETF areas as listed on <http://www.ietf.org/iesg/area.html>. A list of full names and abbreviations will be kept by the RFC Series Editor.
该值应为上所列IETF区域之一的全名或缩写<http://www.ietf.org/iesg/area.html>. RFC系列编辑器将保留全名和缩写的列表。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model: only text content.
内容模型：仅文本内容。
This element allows the inclusion of "artwork" in the document. <artwork> provides full control of horizontal whitespace and line breaks; thus, it is used for a variety of things, such as diagrams ("line art") and protocol unit diagrams. Tab characters (U+0009) inside of this element are prohibited.
此元素允许在文档中包含“艺术品”<artwork>提供对水平空白和换行符的完全控制；因此，它被用于各种各样的事情，比如图（“线艺术”）和协议单元图。禁止在此元素内使用制表符（U+0009）。
Alternatively, the "src" attribute allows referencing an external graphics file, such as a vector drawing in SVG or a bitmap graphic file, using a URI. In this case, the textual content acts as a fallback for output representations that do not support graphics; thus, it ought to contain either (1) a "line art" variant of the graphics or (2) prose that describes the included image in sufficient detail.
或者，“src”属性允许使用URI引用外部图形文件，例如SVG中的矢量图形或位图图形文件。在这种情况下，文本内容充当不支持图形的输出表示的后备；因此，它应该包含（1）图形的“线条艺术”变体或（2）足够详细地描述所包含图像的散文。
In [RFC7749], the <artwork> element was also used for source code and formal languages; in v3, this is now done with <sourcecode>.
在[RFC7749]中，<artwork>元素也用于源代码和形式语言；在v3中，这是通过<sourcecode>完成的。
There are at least five ways to include SVG in artwork in Internet-Drafts:
至少有五种方法可以将SVG包含在Internet草稿的艺术作品中：
o Inline, by including all of the SVG in the content of the element, such as: <artwork type="svg"><svg xmlns="http://www.w3.org/2000/ svg...">
o 内联，通过在元素的内容中包含所有SVG，例如：<artwork type=“SVG”><SVG xmlns=”http://www.w3.org/2000/ svg…”>
o Inline, but using XInclude (see Appendix B.1), such as: <artwork type="svg"><xi:include href=...>
o 内联，但使用XInclude（参见附录B.1），例如：<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 作为数据：URI，例如：<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/...">
o 作为外部实体的URI，例如：<artwork type=“svg”src=”http://www.example.com/...">
o As a local file, such as: <artwork type="svg" src="diagram12.svg">
o 作为本地文件，例如：<artwork type=“svg”src=“diagram12.svg”>
The use of SVG in Internet-Drafts and RFCs is covered in much more detail in [RFC7996].
[RFC7996]详细介绍了SVG在互联网草稿和RFC中的使用。
The above methods for inclusion of SVG art can also be used for including text artwork, but using a data: URI is probably confusing for text artwork.
上述包含SVG艺术的方法也可用于包含文本艺术作品，但使用data:URI可能会使文本艺术作品混淆。
Formatters that do pagination should attempt to keep artwork on a single page. This is to prevent artwork that is split across pages from looking like two separate pieces of artwork.
进行分页的格式化程序应尝试在单个页面上保留插图。这是为了防止跨页面分割的艺术品看起来像两个独立的艺术品。
See Section 5 for a description of how to deal with issues of using "&" and "<" characters in artwork.
请参阅第5节，了解如何处理在艺术品中使用“&”和“<”字符的问题。
This element appears as a child element of <aside> (Section 2.6), <blockquote> (Section 2.10), <dd> (Section 2.18), <figure> (Section 2.25), <li> (Section 2.29), <section> (Section 2.46), <td> (Section 2.56), and <th> (Section 2.58).
此元素显示为<aside>（第2.6节）、<blockquote>（第2.10节）、<dd>（第2.18节）、<figure>（第2.25节）、<li>（第2.29节）、<Section>（第2.46节）、<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model:
内容模型：
Either:
要么：
Text
文本
Or:
或：
<svg> elements (Section 4)
<svg>元素（第4节）
Controls whether the artwork appears left justified (default), centered, or right justified. Artwork is aligned relative to the left margin of the document.
控制艺术品是左对齐（默认）、居中还是右对齐。艺术品相对于文档的左边缘对齐。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
Alternative text description of the artwork (which is more than just a summary or caption). When the art comes from the "src" attribute and the format of that artwork supports alternate text, the alternative text comes from the text of the artwork itself, not from this attribute. The contents of this attribute are important to readers who are visually impaired, as well as those reading on devices that cannot show the artwork well, or at all.
艺术品的备选文本描述（不仅仅是摘要或标题）。当艺术品来自“src”属性且该艺术品的格式支持替代文本时，替代文本来自艺术品本身的文本，而不是该属性。该属性的内容对于视力受损的读者，以及那些在不能很好地显示艺术品或根本无法显示艺术品的设备上阅读的读者来说非常重要。
Document-wide unique identifier for this artwork.
此艺术品的文档范围唯一标识符。
Deprecated.
不赞成。
A filename suitable for the contents (such as for extraction to a local file). This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the artwork). Note that the "name" attribute does not need to be unique for <artwork> elements in a document. If multiple <artwork> elements have the same "name" attribute, a processing tool might assume that the elements are all fragments of a single file, and the tool can collect those fragments for later processing. See Section 7 for a discussion of possible problems with the value of this attribute.
适合于内容的文件名（例如用于提取到本地文件）。此属性对于其他类型的工具（例如自动语法检查器，它通过提取艺术品来工作）很有帮助。请注意，“name”属性对于文档中的<artwork>元素不需要是唯一的。如果多个<artwork>元素具有相同的“name”属性，则处理工具可能会假定这些元素都是单个文件的片段，并且该工具可以收集这些片段以供以后处理。有关此属性值可能存在的问题的讨论，请参见第7节。
The URI reference of a graphics file [RFC3986], or the name of a file on the local disk. This can be a "data" URI [RFC2397] that contains the contents of the graphics file. Note that the inclusion of art with the "src" attribute depends on the capabilities of the processing tool reading the XML document. Tools need to be able to handle the file: URI, and they should be able to handle http: and https: URIs as well. The prep tool will be able to handle reading the "src" attribute.
图形文件[RFC3986]的URI引用，或本地磁盘上的文件名。这可以是包含图形文件内容的“数据”URI[RFC2397]。请注意，将art包含在“src”属性中取决于处理工具读取XML文档的能力。工具需要能够处理file:URI，并且还应该能够处理http:URI和https:URI。prep工具将能够处理“src”属性的读取。
If no URI scheme is given in the attribute, the attribute is considered to be a local filename relative to the current directory. Processing tools must be careful to not accept dangerous values for the filename, particularly those that contain absolute references outside the current directory. Document creators should think hard before using relative URIs due to possible later problems if files move around on the disk. Also, documents should most likely use explicit URI schemes wherever possible.
如果属性中没有给出URI方案，则该属性被视为相对于当前目录的本地文件名。处理工具必须小心，不要接受文件名的危险值，尤其是那些包含当前目录之外的绝对引用的文件名。文档创建者在使用相对URI之前应该仔细考虑，因为如果文件在磁盘上移动，以后可能会出现问题。此外，文档应该尽可能使用显式URI方案。
In some cases, the prep tool may remove the "src" attribute after processing its value. See [RFC7998] for a description of this.
在某些情况下，prep工具可能会在处理其值后删除“src”属性。请参阅[RFC7998]以了解此操作的说明。
It is an error to have both a "src" attribute and content in the <artwork> element.
在<artwork>元素中同时具有“src”属性和内容是错误的。
Specifies the type of the artwork. The value of this attribute is free text with certain values designated as preferred.
指定艺术品的类型。此属性的值是自由文本，其中某些值指定为首选值。
The preferred values for <artwork> types are:
<artwork>类型的首选值为：
o ascii-art
o ASCII艺术
o binary-art
o 二元艺术
o call-flow
o 呼叫流
o hex-dump
o 十六进制转储
o svg
o svg
The RFC Series Editor will maintain a complete list of the preferred values on the RFC Editor web site, and that list is expected to be updated over time. Thus, a consumer of v3 XML should not cause a failure when it encounters an unexpected type or no type is specified. The table will also indicate which type of art can appear in plain-text output (for example, type="svg" cannot).
RFC系列编辑器将在RFC编辑器网站上维护首选值的完整列表，该列表预计会随着时间的推移而更新。因此，V3XML的使用者在遇到意外类型或未指定类型时不应导致失败。该表还将指出哪种艺术类型可以出现在纯文本输出中（例如，type=“svg”不能）。
Deprecated.
不赞成。
Deprecated.
不赞成。
This element is a container for content that is semantically less important or tangential to the content that surrounds it.
该元素是一个容器，用于存放语义不太重要或与其周围内容无关的内容。
This element appears as a child element of <section> (Section 2.46).
此元素显示为<section>（第2.46节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o <artwork> elements (Section 2.5)
o <artwork>元素（第2.5节）
o <dl> elements (Section 2.20)
o <dl>要素（第2.20节）
o <figure> elements (Section 2.25)
o <figure>元素（第2.25节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <list> elements (Section 3.4)
o <list>元素（第3.4节）
o <ol> elements (Section 2.34)
o <ol>要素（第2.34节）
o <t> elements (Section 2.53)
o <t> 要素（第2.53节）
o <table> elements (Section 2.54)
o <table>元素（第2.54节）
o <ul> elements (Section 2.63)
o <ul>元件（第2.63节）
Document-wide unique identifier for this aside.
此文档的文档范围唯一标识符。
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]).
文档的<front>元素中包含的<author>元素用于填充样板文件，还用于生成“作者地址”部分（请参见[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).
请注意，“author”也可以只是一个组织（通过不指定任何“name”属性，而是添加<organization>子元素）。
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".
此外，“role”属性可用于将作者标记为“editor”。这反映在头版和“作者地址”部分，以及参考书目中。请注意，本规范并未定义术语“编辑器”的确切含义。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <organization> element (Section 2.35)
1. 一个可选的<organization>元素（第2.35节）
2. One optional <address> element (Section 2.2)
2. 一个可选的<address>元素（第2.2节）
The ASCII equivalent of the author's full name.
作者全名的ASCII等价物。
The ASCII equivalent of the author's initials, to be used in conjunction with the separately specified asciiSurname.
作者姓名首字母的ASCII等价物，与单独指定的asciiSurname一起使用。
The ASCII equivalent of the author's surname, to be used in conjunction with the separately specified asciiInitials.
作者姓名的ASCII等价物，与单独指定的ASCIII开头一起使用。
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.
全名（用于自动生成的“作者地址”部分）。尽管此属性是可选的，但如果一个或多个“asciiFullname”、“asciiInitials”或“asciiSurname”属性具有值，则需要“fullname”属性。
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.
一些处理器会对值进行后期处理——例如，当它只包含一个字母时（在这种情况下，他们可能会添加一个尾随点）。依赖这种后处理可能导致不同格式化程序的结果不同，因此应该避免。
Specifies the role the author had in creating the document.
指定作者在创建文档时的角色。
Allowed value:
允许值：
o "editor"
o “编辑”
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.
作者的姓氏，与单独指定的首字母一起使用。它通常出现在首页、页脚和参考资料中。
Contains the "back" part of the document: the references and appendices. In <back>, <section> elements indicate appendices.
包含文件的“背面”部分：参考文件和附录。在<back>中，<section>元素表示附录。
This element appears as a child element of <rfc> (Section 2.45).
此元素显示为<rfc>的子元素（第2.45节）。
Content model:
内容模型：
In this order:
按此顺序：
1. Optional <displayreference> elements (Section 2.19)
1. 可选<displayreference>元素（第2.19节）
2. Optional <references> elements (Section 2.42)
2. 可选<references>元素（第2.42节）
3. Optional <section> elements (Section 2.46)
3. 可选<section>元素（第2.46节）
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.
标记属于[BCP14]中定义的短语的文本，如“必须”、“不应该”等。在某些输出表示中显示时，此元素中的文本可能会高亮显示。此元素的使用是可选的。
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>".
此元素仅用于BCP 14中的实际短语，而不是需求的完整定义。例如，说“包<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).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<Premission>（第3.6节）、<refcontent>（第2.39节）、<strong>（第2.50节）、<sub>（第2.51节）、<sup>（第2.52节）、<t>（第2.53节）、<td>（第2.56节）的子元素，<th>（第2.58节）和<tt>（第2.62节）。
Content model: only text content.
内容模型：仅文本内容。
Specifies that a block of text is a quotation.
指定文本块是引号。
This element appears as a child element of <section> (Section 2.46).
此元素显示为<section>（第2.46节）的子元素。
Content model:
内容模型：
Either:
要么：
In any order, but at least one of:
以任何顺序，但至少一种：
* <artwork> elements (Section 2.5)
* <artwork> elements (Section 2.5)
* <dl> elements (Section 2.20)
* <dl> elements (Section 2.20)
* <figure> elements (Section 2.25)
* <figure> elements (Section 2.25)
* <ol> elements (Section 2.34)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
* <ul> elements (Section 2.63)
Or:
或：
In any order, but at least one of:
以任何顺序，但至少一种：
* Text
* 文本
* <bcp14> elements (Section 2.9)
* <bcp14> elements (Section 2.9)
* <cref> elements (Section 2.16)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
* <xref> elements (Section 2.66)
Document-wide unique identifier for this quotation.
此报价单的文档范围唯一标识符。
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.
引文的来源。这必须是一个URI。如果给定了“quotedFrom”属性，则处理工具将使用此URI作为该属性文本的链接。
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.
引用此元素中文本的人员或文档的名称。格式化程序应在引号末尾将其呈现为可见文本。
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".
此元素包含<section>元素。此元素中的每个<section>元素都必须将“number”属性设置为“false”。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model:
内容模型：
One or more <section> elements (Section 2.46)
一个或多个<section>元素（第2.46节）
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).
此元素显示为<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
Gives the city name in a postal address.
在邮政地址中提供城市名称。
This element appears as a child element of <postal> (Section 2.37).
此元素显示为<postal>的子元素（第2.37节）。
Content model: only text content.
内容模型：仅文本内容。
The ASCII equivalent of the city name.
城市名称的ASCII等价物。
Gives the postal region code.
提供邮政区域代码。
This element appears as a child element of <postal> (Section 2.37).
此元素显示为<postal>的子元素（第2.37节）。
Content model: only text content.
内容模型：仅文本内容。
The ASCII equivalent of the postal code.
相当于邮政编码的ASCII码。
Gives the country name or code in a postal address.
在邮政地址中提供国家名称或代码。
This element appears as a child element of <postal> (Section 2.37).
此元素显示为<postal>的子元素（第2.37节）。
Content model: only text content.
内容模型：仅文本内容。
The ASCII equivalent of the country name.
国家名称的ASCII等效项。
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).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<c>（第3.1节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<name>（第2.32节）、<postamble>（第3.5节）、<preamble>（第3.6节）、<strong>（第2.50节）、<sub>（第2.51节）、<sup>（第2.52节）的子元素，<t>（第2.53节）、<td>（第2.56节）、<th>（第2.58节）、<tt>（第2.62节）和<ttcol>（第3.9节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Document-wide unique identifier for this comment.
此注释的文档范围唯一标识符。
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.
建议是否应通过格式化工具显示注释。如果您希望在处理注释内容之后在文档中保留注释，则可能会将其设置为“false”。
Allowed values:
允许值：
o "true" (default)
o “true”（默认值）
o "false"
o “假”
Holds the "source" of a comment, such as the name or the initials of the person who made the comment.
保留评论的“来源”，例如发表评论的人的姓名或首字母缩写。
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.
提供有关发布日期的信息。此元素用于两种情况：正在生成的文档的样板文件，以及使用<front>元素的内部参考书目。
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.
Internet草稿和RFC样板：此元素定义当前文档（Internet草稿或RFC）的发布日期。在生成Internet草稿时，prep工具使用此日期计算到期日期（请参见[IDGUIDE]）。如果遗漏了“年”、“月”或“日”中的一个或多个，则如果存在的属性与当前系统日期一致，则准备工具将尝试使用当前系统日期。
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.
在<rfc>元素中的日期中，月份必须是数字或英语中的月份。prep工具将自动将文本月份名称更改为数字。同样，年份必须是四位数。
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.
当prep工具用于创建互联网草稿时，它将拒绝提交的互联网草稿，该草稿本身在样板文件中有一个<date>元素，而不是今天。也就是说，该工具不允许提交者指定提交日期以外的日期。为了避免这个问题，作者可能只是不在样板文件中包含<date>元素。
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.
书目参考：在<reference>元素中的日期中，日期信息可以包含月份或年份的散文文本。例如，允许使用模糊日期（year=“ca.2000”）、日期范围（year=“2012-2013”）、非特定月份（month=“Second quarter”）等。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
The day of publication.
出版日期。
The month or months of publication.
出版月份出版的一个月或几个月。
The year or years of publication.
出版年份出版的一年或几年。
The definition part of an entry in a definition list.
定义列表中条目的定义部分。
This element appears as a child element of <dl> (Section 2.20).
此元素显示为<dl>的子元素（第2.20节）。
Content model:
内容模型：
Either:
要么：
In any order, but at least one of:
以任何顺序，但至少一种：
* <artwork> elements (Section 2.5)
* <artwork> elements (Section 2.5)
* <dl> elements (Section 2.20)
* <dl> elements (Section 2.20)
* <figure> elements (Section 2.25)
* <figure> elements (Section 2.25)
* <ol> elements (Section 2.34)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
* <ul> elements (Section 2.63)
Or:
或：
In any order, but at least one of:
以任何顺序，但至少一种：
* Text
* 文本
* <bcp14> elements (Section 2.9)
* <bcp14> elements (Section 2.9)
* <cref> elements (Section 2.16)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
* <xref> elements (Section 2.66)
Document-wide unique identifier for this definition.
此定义的文档范围唯一标识符。
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":
此元素提供引用的定位点和将显示的名称之间的映射。这允许作者为自动包含的引用显示更多助记锚名称。此元素中的映射仅适用于格式为“默认”的<xref>元素。例如，如果引用使用锚定“RFC6949”，则以下内容将导致显示文档主体中的锚定为“RFC dev”：
<displayreference target="RFC6949" to="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.
预计该元素仅在输入文档中有效。当准备工具替换了所有相关的锚、目标和“derivedContent”属性后，在准备最终版本时，它可能会被准备工具删除。
This element appears as a child element of <back> (Section 2.8).
此元素显示为<back>（第2.8节）的子元素。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
This attribute must be the name of an anchor in a <reference> or <referencegroup> element.
此属性必须是<reference>或<referencegroup>元素中的锚的名称。
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 "_".
此属性是一个名称，将显示为锚点，而不是<reference>元素中给定的锚点。给定的字符串必须以以下字符之一开头：0-9、a-z或a-z。字符串中的其他字符必须是0-9、a-z、a-z、“-”、“.”或“904;”。
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.)
定义列表。每个条目都有一对元素：一个术语（<dt>）和一个定义（<dd>）。（这与HTML中使用的模型稍有不同，也更简单，后者允许对单个定义使用多个术语。）
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).
此元素显示为<abstract>（第2.1节）、<aside>（第2.6节）、<blockquote>（第2.10节）、<dd>（第2.18节）、<li>（第2.29节）、<note>（第2.33节）、<Section>（第2.46节）、<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model:
内容模型：
One or more sequences of:
一个或多个序列：
1. One <dt> element
1. 一个<dt>元素
2. One <dd> element
2. 一个<dd>元素
Document-wide unique identifier for the list.
列表的文档范围唯一标识符。
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.
“挂起”属性定义术语是否与定义出现在同一行上。hanging=“true”表示术语位于定义的左侧，而hanging=“false”表示术语位于单独的一行。
Allowed values:
允许值：
o "false"
o “假”
o "true" (default)
o “true”（默认值）
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.
定义条目之间是否有空行。spacing=“normal”表示单个空行，spacing=“compact”表示空行之间没有空格。
Allowed values:
允许值：
o "normal" (default)
o “正常”（默认）
o "compact"
o “紧凑型”
The term being defined in a definition list.
定义列表中定义的术语。
This element appears as a child element of <dl> (Section 2.20).
此元素显示为<dl>的子元素（第2.20节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Document-wide unique identifier for this term.
此术语的文档范围唯一标识符。
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).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<li>（第2.29节）、<Premission>（第3.6节）、<refcontent>（第2.39节）、<strong>（第2.50节）、<sub>（第2.51节）、<sup>（第2.52节）、<t>（第2.53节）、<td>（第2.56节）的子元素，<th>（第2.58节）和<tt>（第2.62节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Provides an email address.
提供电子邮件地址。
The value is expected to be the addr-spec defined in Section 2 of [RFC6068].
该值应为[RFC6068]第2节中定义的addr规范。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
The ASCII equivalent of the author's email address. This is only used if the email address has any internationalized components.
作者电子邮件地址的ASCII等价物。这仅在电子邮件地址包含任何国际化组件时使用。
Represents an "external" link (as specified in the "target" attribute). This is useful for embedding URIs in the body of a document.
表示“外部”链接（在“目标”属性中指定）。这对于在文档体中嵌入URI很有用。
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.
如果<eref>元素具有非空文本内容，则格式化程序应使用该内容作为链接的显示文本。否则，格式化程序应使用“target”属性的值作为显示的文本。格式化程序将以适合输出格式的方式将显示的文本链接到“target”属性的值。
For example, with an input of:
例如，输入为：
This is described at <eref target="http://www.example.com/reports/r12.html"/>.
这在<eref target=”中描述http://www.example.com/reports/r12.html"/>.
An HTML formatter might generate:
HTML格式化程序可能会生成：
This is described at <a href="http://www.example.com/reports/r12.html"> http://www.example.com/reports/r12.html</a>.
这在<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>.
这被描述为<eref目标=”http://www.example.com/reports/r12.html“>在这个有趣的报告中</eref>。
An HTML formatter might generate:
HTML格式化程序可能会生成：
This is described <a href="http://www.example.com/reports/r12.html"> in this interesting report</a>.
这是在<a href=”中描述的http://www.example.com/reports/r12.html“>在这个有趣的报告中</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).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<c>（第3.1节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<name>（第2.32节）、<postamble>（第3.5节）、<preamble>（第3.6节）、<strong>（第2.50节）、<sub>（第2.51节）的子元素，<sup>（第2.52节）、<t>（第2.53节）、<td>（第2.56节）、<th>（第2.58节）、<tt>（第2.62节）和<ttcol>（第3.9节）。
Content model: only text content.
内容模型：仅文本内容。
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.
链接目标[RFC3986]的URI。这必须以方案名称（如“https://”）开头，因此不能与当前文档的URL相对。
Contains a figure with a caption with the figure number. If the element contains a <name> element, the caption will also show that name.
包含一个带有图号标题的图。如果元素包含<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).
此元素显示为<aside>（第2.6节）、<blockquote>（第2.10节）、<dd>（第2.18节）、<li>（第2.29节）、<Section>（第2.46节）、<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <name> element (Section 2.32)
1. 一个可选的<name>元素（第2.32节）
2. Optional <iref> elements (Section 2.27)
2. 可选<iref>元件（第2.27节）
3. One optional <preamble> element (Section 3.6)
3. 一个可选的<preamble>元素（第3.6节）
4. In any order, but at least one of:
4. 以任何顺序，但至少一种：
* <artwork> elements (Section 2.5)
* <artwork> elements (Section 2.5)
* <sourcecode> elements (Section 2.48)
* <sourcecode> elements (Section 2.48)
5. One optional <postamble> element (Section 3.5)
5. 一个可选的<postamble>元素（第3.5节）
Deprecated.
不赞成。
Note: does not affect title or <artwork> alignment.
注意：不影响标题或对齐。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
Deprecated. If the goal is to provide a single URI for a reference, use the "target" attribute in <reference> instead.
不赞成。如果目标是为引用提供单个URI，请使用<reference>中的“target”属性。
Document-wide unique identifier for this figure.
此图的文档范围唯一标识符。
Deprecated.
不赞成。
Deprecated.
不赞成。
Deprecated.
不赞成。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
Deprecated. Use <name> instead.
不赞成。改用<name>。
Deprecated.
不赞成。
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.
一个<front>元素可以有多个<serieinfo>元素。元素决定文档编号（对于RFC）或名称（对于Internet草稿）。另一个<seriesInfo>元素确定“成熟度级别”（在[RFC2026]中定义），使用“标准跟踪”的“标准”，“bcp”的“bcp”，“信息”的“信息”，“实验”的“经验”和“历史”的“历史”值。这些多个<serieinfo>元素的“name”属性按照第2.47节所述进行交互。
This element appears as a child element of <reference> (Section 2.40) and <rfc> (Section 2.45).
此元素显示为<reference>（第2.40节）和<rfc>（第2.45节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One <title> element (Section 2.60)
1. 一个<title>元素（第2.60节）
2. Optional <seriesInfo> elements (Section 2.47)
2. 可选<serieinfo>元素（第2.47节）
3. One or more <author> elements (Section 2.7)
3. 一个或多个<author>元素（第2.7节）
4. One optional <date> element (Section 2.17)
4. 一个可选的<date>元素（第2.17节）
5. Optional <area> elements (Section 2.4)
5. 可选<area>元件（第2.4节）
6. Optional <workgroup> elements (Section 2.65)
6. 可选<工作组>元素（第2.65节）
7. Optional <keyword> elements (Section 2.28)
7. 可选<keyword>元素（第2.28节）
8. One optional <abstract> element (Section 2.1)
8. 一个可选的<abstract>元素（第2.1节）
9. Optional <note> elements (Section 2.33)
9. 可选<note>元件（第2.33节）
10. One optional <boilerplate> element (Section 2.11)
10. 一个可选的<boilerplate>元素（第2.11节）
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.
索引项可以是常规项（当只给出“item”属性时）或嵌套项（通过指定“subitem”也可以），分组在常规项下。
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.
索引项通常指<iref>元素发生的确切位置。例外情况是作为<section>的子元素出现，在这种情况下，整个节被认为与该索引条目相关。在某些格式中，此类型的索引项可能显示为范围。
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).
此元素显示为<annotation>（第2.3节）、<Side>（第2.6节）、<blockquote>（第2.10节）、<c>（第3.1节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<postamble>（第3.5节）、<preamble>（第3.6节）、<Section>（第2.46节）、<strong>的子元素（第2.50节）、<sub>（第2.51节）、<sup>（第2.52节）、<t>（第2.53节）、<table>（第2.54节）、<td>（第2.56节）、<th>（第2.58节）、<tt>（第2.62节）和<ttcol>（第3.9节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
The item to include.
要包括的项目。
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".
将其设置为“true”将事件声明为“primary”，这可能会导致它在索引中突出显示。“主要”事件的发生次数没有限制。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
The subitem to include.
要包括的子项。
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.
关键字用于RFC索引和生成的文档表示的元数据中。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model: only text content.
内容模型：仅文本内容。
A list element, used in <ol> and <ul>.
列表元素，用于<ol>和<ul>中。
This element appears as a child element of <ol> (Section 2.34) and <ul> (Section 2.63).
此元素显示为<ol>（第2.34节）和<ul>（第2.63节）的子元素。
Content model:
内容模型：
Either:
要么：
In any order, but at least one of:
以任何顺序，但至少一种：
* <artwork> elements (Section 2.5)
* <artwork> elements (Section 2.5)
* <dl> elements (Section 2.20)
* <dl> elements (Section 2.20)
* <figure> elements (Section 2.25)
* <figure> elements (Section 2.25)
* <ol> elements (Section 2.34)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
* <ul> elements (Section 2.63)
Or:
或：
In any order, but at least one of:
以任何顺序，但至少一种：
* Text
* 文本
* <bcp14> elements (Section 2.9)
* <bcp14> elements (Section 2.9)
* <cref> elements (Section 2.16)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
* <xref> elements (Section 2.66)
Document-wide unique identifier for this list item.
此列表项的文档范围唯一标识符。
A link to an external document that is related to the RFC.
指向与RFC相关的外部文档的链接。
The following are the supported types of external documents that can be pointed to in a <link> element:
以下是可在<link>元素中指向的受支持的外部文档类型：
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 RFC系列的当前国际标准序列号（ISSN）。“rel”属性的值为“item”。链接应使用“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 此文档的数字对象标识符（DOI）。“rel”属性的值为“descripeby”。链接应使用[RFC7669]中规定的格式；这一点在未来有望改变。
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 提交给RFC编辑以成为已发布RFC的互联网草稿。“rel”属性的值为“convertedFrom”。链接应指向IETF控制的网站，该网站保留互联网草稿的副本。
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.
o 文档作者提供的文档的表示。“rel”属性的值为“alternate”。该链接可以指向个人运营的网站。
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.
在RFC生产模式下，在发布RFC之前，准备工具需要检查<link>的值。在草稿制作模式下，准备工具可能会在草稿提交过程中删除一些<link>元素。
This element appears as a child element of <rfc> (Section 2.45).
此元素显示为<rfc>的子元素（第2.45节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
The URI of the external document.
外部文档的URI。
The relationship of the external document to this one. The relationships are taken from the "Link Relations" registry maintained by IANA [LINKRELATIONS].
外部文档与此文档的关系。这些关系取自IANA[LINKRELATIONS]维护的“链接关系”注册表。
Represents the main content of the document.
表示文档的主要内容。
This element appears as a child element of <rfc> (Section 2.45).
此元素显示为<rfc>的子元素（第2.45节）。
Content model:
内容模型：
One or more <section> elements (Section 2.46)
一个或多个<section>元素（第2.46节）
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).
此元素显示为<figure>（第2.25节）、<note>（第2.33节）、<references>（第2.42节）、<Section>（第2.46节）、<table>（第2.54节）和<texttable>（第3.8节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
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".
它通常用于向评审员提供附加信息（工作组信息、邮件列表等）或用于附加出版物信息，如“IESG注释”。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <name> element (Section 2.32)
1. 一个可选的<name>元素（第2.32节）
2. In any order, but at least one of:
2. 以任何顺序，但至少一种：
* <dl> elements (Section 2.20)
* <dl> elements (Section 2.20)
* <ol> elements (Section 2.34)
* <ol> elements (Section 2.34)
* <t> elements (Section 2.53)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
* <ul> elements (Section 2.63)
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."
如果设置为“true”，则此注释将在准备工具中标记为文本，指示在文档作为RFC发布之前应将其删除。该文本将为“此注释在作为RFC发布之前删除。”
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
Deprecated. Use <name> instead.
不赞成。改用<name>。
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).
此元素显示为<abstract>（第2.1节）、<aside>（第2.6节）、<blockquote>（第2.10节）、<dd>（第2.18节）、<li>（第2.29节）、<note>（第2.33节）、<Section>（第2.46节）、<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model:
内容模型：
One or more <li> elements (Section 2.29)
一个或多个<li>元件（第2.29节）
Document-wide unique identifier for the list.
列表的文档范围唯一标识符。
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.
当prep工具看到一个具有“group”属性的<ol>元素时，它将继续对该列表进行编号，从该列表中删除具有相同组名的前一个列表。如果<ol>元素同时具有“组”属性和“开始”属性，则组的编号将重置为给定的开始值。
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.
定义条目之间是否有空行。spacing=“normal”表示单个空行，spacing=“compact”表示空行之间没有空格。
Allowed values:
允许值：
o "normal" (default)
o “正常”（默认）
o "compact"
o “紧凑型”
The ordinal value at which to start the list. This defaults to "1" and must be an integer of 0 or greater.
开始列表的序号值。这默认为“1”，并且必须是0或更大的整数。
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:
列表项上标签的类型。如果类型值的长度为1，则其含义与HTML相同：
a Lowercase letters (a, b, c, ...)
a小写字母（a，b，c，…）
A Uppercase letters (A, B, C, ...)
A大写字母（A，B，C，…）
1 Decimal numbers (1, 2, 3, ...)
1个十进制数字（1，2，3，…）
i Lowercase Roman numerals (i, ii, iii, ...)
i小写罗马数字（i，ii，iii，…）
I Uppercase Roman numerals (I, II, III, ...)
I大写罗马数字（I，II，III，…）
For types "a" and "A", after the 26th entry, the numbering starts at "aa"/"AA", then "ab"/"AB", and so on.
对于类型“a”和“a”，在第26个条目之后，编号从“aa”/“aa”开始，然后是“ab”/“ab”，依此类推。
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.
如果类型值的长度大于1，则该值必须包含百分比编码指示符和其他文本。该值为自由格式文本，允许使用“百分比字母”格式插入计数器值。例如，“[REQ%d]”生成格式为“[REQ1]”的标签，其中“%d”将项目编号作为十进制数字插入。
The following formats are supported:
支持以下格式：
%c Lowercase letters (a, b, c, ...)
%c小写字母（a，b，c，…）
%C Uppercase letters (A, B, C, ...)
%C大写字母（A，B，C，…）
%d Decimal numbers (1, 2, 3, ...)
%d十进制数（1，2，3，…）
%i Lowercase Roman numerals (i, ii, iii, ...)
%i小写罗马数字（i，ii，iii，…）
%I Uppercase Roman numerals (I, II, III, ...)
%I大写罗马数字（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.
类型字符串为空是一个错误。对于项目符号列表，请使用<ul>元素。对于既没有项目符号也没有数字的列表，请使用具有“empty=”true“属性的<ul>元素。
If no type attribute is given, the default type is the same as "type='%d.'".
如果未提供类型属性，则默认类型与“类型=“%d.”相同。
Specifies the affiliation [RFC7322] of an author.
指定作者的从属关系[RFC7322]。
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.
此信息出现在“作者地址”部分和首页（有关更多信息，请参阅[RFC7322]）。如果该值很长，则可以在“abbrev”属性中指定缩写变量。
This element appears as a child element of <author> (Section 2.7).
此元素显示为<author>的子元素（第2.7节）。
Content model: only text content.
内容模型：仅文本内容。
Abbreviated variant.
缩写变体。
The ASCII equivalent of the organization's name.
组织名称的ASCII等效项。
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.
使用“全局数字”语法，该值应该是“tel”URI中特定于方案的部分（因此不包括前缀“tel:”）。详见[RFC3966]第3节。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
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.
包含提供邮政信息的可选子元素。这些元素将按特定于格式化程序的顺序显示。邮政地址只能包含一组<street>、<city>、<region>、<code>和<country>元素，或者只能包含一组有序的<postalLine>元素，但不能同时包含这两个元素。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model:
内容模型：
Either:
要么：
In any order:
以任何顺序：
* <city> elements (Section 2.13)
* <city> elements (Section 2.13)
* <code> elements (Section 2.14)
* <code> elements (Section 2.14)
* <country> elements (Section 2.15)
* <country> elements (Section 2.15)
* <region> elements (Section 2.43)
* <region> elements (Section 2.43)
* <street> elements (Section 2.49)
* <street> elements (Section 2.49)
Or:
或：
One or more <postalLine> elements (Section 2.38)
一个或多个<postalLine>元件（第2.38节）
Represents one line of a postal address. When more than one <postalLine> is given, the prep tool emits them in the order given.
表示邮政地址的一行。当给出多个<postalLine>时，prep工具将按照给定的顺序发射它们。
This element appears as a child element of <postal> (Section 2.37).
此元素显示为<postal>的子元素（第2.37节）。
Content model: only text content.
内容模型：仅文本内容。
The ASCII equivalent of the text in the address line.
地址行中文本的ASCII等效值。
Text that should appear between the title and the date of a reference. The purpose of this element is to prevent the need to abuse <seriesInfo> to get such text in a reference.
应出现在引用的标题和日期之间的文本。此元素的目的是防止滥用<serieinfo>以在引用中获取此类文本。
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>
<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.
[April1]Phunny，K.，“关于做傻瓜”，自出版小册子，2000年4月。
This element appears as a child element of <reference> (Section 2.40).
此元素显示为<reference>的子元素（第2.40节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
Represents a bibliographic reference.
表示参考书目。
This element appears as a child element of <referencegroup> (Section 2.41) and <references> (Section 2.42).
此元素显示为<referencegroup>（第2.41节）和<references>（第2.42节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One <front> element (Section 2.26)
1. 一个<front>元件（第2.26节）
2. In any order:
2. 以任何顺序：
* <annotation> elements (Section 2.3)
* <annotation> elements (Section 2.3)
* <format> elements (Section 3.3)
* <format> elements (Section 3.3)
* <refcontent> elements (Section 2.39)
* <refcontent> elements (Section 2.39)
* <seriesInfo> elements (Section 2.47; deprecated in this
context)
* <seriesInfo> elements (Section 2.47; deprecated in this
context)
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.
此引用的文档范围唯一标识符。通常，这将用于在“引用”部分中“标记”引用，并作为指向此引用条目的链接中的标识符。
Specifies whether or not the title in the reference should be quoted. This can be used to prevent quoting, such as on errata.
指定是否引用引用中的标题。这可用于防止引用，例如在勘误表上。
Allowed values:
允许值：
o "true" (default)
o “true”（默认值）
o "false"
o “假”
Holds the URI for the reference.
保存引用的URI。
Represents a list of bibliographic references that will be represented as a single reference. This is most often used to reference STDs and BCPs, where a single reference (such as "BCP 9") may encompass more than one RFC.
表示将表示为单个参考的书目参考列表。这通常用于引用STD和BCP，其中单个引用（如“BCP 9”）可能包含多个RFC。
This element appears as a child element of <references> (Section 2.42).
此元素显示为<references>（第2.42节）的子元素。
Content model:
内容模型：
One or more <reference> elements (Section 2.40)
一个或多个<reference>元件（第2.40节）
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.
此参考组的文档范围唯一标识符。通常，这将用于在“引用”部分中“标记”引用组，并作为指向此引用条目的链接中的标识符。
Contains a set of bibliographic references.
包含一组参考书目。
In the early days of the RFC Series, there was only one "References" section per RFC. This convention was later changed to group references into two sets, "Normative" and "Informative", as described in [RFC7322]. This vocabulary supports the split with the <name> child element. In general, the title should be either "Normative References" or "Informative References".
在RFC系列的早期，每个RFC只有一个“参考”部分。该惯例后来被修改为将参考文献分为两组，“规范性”和“信息性”，如[RFC7322]所述。此词汇表支持使用<name>子元素进行拆分。一般而言，标题应为“规范性参考文件”或“资料性参考文件”。
This element appears as a child element of <back> (Section 2.8).
此元素显示为<back>（第2.8节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <name> element (Section 2.32)
1. 一个可选的<name>元素（第2.32节）
2. In any order:
2. 以任何顺序：
* <reference> elements (Section 2.40)
* <reference> elements (Section 2.40)
* <referencegroup> elements (Section 2.41)
* <referencegroup> elements (Section 2.41)
An optional user-supplied identifier for this set of references.
用户为此引用集提供的可选标识符。
Deprecated. Use <name> instead.
不赞成。改用<name>。
Provides the region name in a postal address.
在邮政地址中提供地区名称。
This element appears as a child element of <postal> (Section 2.37).
此元素显示为<postal>的子元素（第2.37节）。
Content model: only text content.
内容模型：仅文本内容。
The ASCII equivalent of the region name.
区域名称的ASCII等效项。
Represents a link to a specific part of a document that appears in a <reference> element. Formatters that have links (such as HTML and PDF) render <relref> elements as external hyperlinks to the specified part of the reference, creating the link target by combining the base URI from the <reference> element with the "relative" attribute from this element. The "target" attribute is required, and it must be the anchor of a <reference> element.
表示指向出现在<reference>元素中的文档特定部分的链接。具有链接（如HTML和PDF）的格式化程序将<relref>元素呈现为指向引用指定部分的外部超链接，通过将<reference>元素的基本URI与该元素的“relative”属性组合来创建链接目标。“target”属性是必需的，它必须是<reference>元素的锚点。
The "section" attribute is required, and the "relative" attribute is optional. If the reference is not an RFC or Internet-Draft that is in the v3 format, the element needs to have a "relative" attribute; in this case, the value of the "section" attribute is ignored.
“section”属性是必需的，“relative”属性是可选的。如果引用不是v3格式的RFC或Internet草稿，则元素需要具有“相对”属性；在这种情况下，“section”属性的值将被忽略。
An example of the <relref> element with text content might be:
具有文本内容的<relref>元素的示例可能是：
See <relref section="2.3" target="RFC9999" displayFormat="bare"> the protocol overview</relref> for more information.
有关更多信息，请参见协议概述。
An HTML formatter might generate:
HTML格式化程序可能会生成：
See <a href="http://www.rfc-editor.org/rfc/rfc9999.html#s-2.3"> the protocol overview</a> for more information.
请参见<a href=”http://www.rfc-editor.org/rfc/rfc9999.html#s-2.3“>协议概述</a>了解更多信息。
Note that the URL in the above example might be different when the RFC Editor deploys the v3 format.
请注意，当RFC编辑器部署v3格式时，上述示例中的URL可能不同。
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), <em> (Section 2.22), <li> (Section 2.29), <name> (Section 2.32), <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), and <tt> (Section 2.62).
该元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<name>（第2.32节）、<Premission>（第3.6节）、<strong>（第2.50节）、<sub>（第2.51节）、<sup>（第2.52节）、<t>（第2.53节）的子元素，<td>（第2.56节）、<th>（第2.58节）和<tt>（第2.62节）。
Content model: only text content.
内容模型：仅文本内容。
This attribute is used to signal formatters what the desired format of the relative reference should be. Formatters for document types that have linking capability should wrap each part of the displayed text in hyperlinks. If there is content in the <relref> element, formatters will ignore the value of this attribute.
此属性用于通知格式化程序相对引用的所需格式。具有链接功能的文档类型的格式化程序应将显示文本的每一部分包装为超链接。如果<relref>元素中有内容，格式化程序将忽略此属性的值。
"of"
“的”
A formatter should display the relative reference as the word "Section" followed by a space, the contents of the "section" attribute followed by a space, the word "of", another space, and the value from the "target" attribute enclosed in square brackets.
格式化程序应将相对引用显示为单词“Section”后跟一个空格、“Section”属性的内容后跟一个空格、“of”、另一个空格以及方括号中“target”属性的值。
For example, with an input of:
例如，输入为：
See <relref section="2.3" target="RFC9999" displayFormat="of"/> for an overview.
有关概述，请参见<relref section=“2.3”target=“RFC9999”displayFormat=“of”/>。
An HTML formatter might generate:
HTML格式化程序可能会生成：
See <a href="http://www.rfc-editor.org/info/rfc9999#s-2.3"> Section 2.3</a> of [<a href="#RFC9999">RFC9999</a>] for an overview.
请参见<a href=”http://www.rfc-editor.org/info/rfc9999#s-2.3“>RFC9999</a>]的第2.3节了解概述。
Note that "displayFormat='of'" is the default for <relref>, so it does not need to be given in a <relref> element if that format is desired.
请注意，“displayFormat='of'”是<relref>的默认值，因此如果需要该格式，则不需要在<relref>元素中给出它。
"comma"
“逗号”
A formatter should display the relative reference as the value from the "target" attribute enclosed in square brackets, a comma, a space, the word "Section" followed by a space, and the "section" attribute.
格式化程序应将相对引用显示为方括号内的“target”属性、逗号、空格、后跟空格的单词“Section”和“Section”属性的值。
For example, with an input of:
例如，输入为：
See <relref section="2.3" target="RFC9999" displayFormat="comma"/>, for an overview.
有关概述，请参见<relref section=“2.3”target=“RFC9999”displayFormat=“逗号”/>。
An HTML formatter might generate:
HTML格式化程序可能会生成：
See [<a href="#RFC9999">RFC9999</a>], <a href="http://www.rfc-editor.org/info/rfc9999#s-2.3"> Section 2.3</a>, for an overview.
请参见[<a href=“#RFC9999”>RFC9999</a>，<a href=”http://www.rfc-editor.org/info/rfc9999#s-2.3“>第2.3节概述。
"parens"
“帕伦斯”
A formatter should display the relative reference as the value from the "target" attribute enclosed in square brackets, a space, a left parenthesis, the word "Section" followed by a space, the "section" attribute, and a right parenthesis.
格式化程序应将相对引用显示为方括号内的“target”属性、空格、左括号、单词“Section”后跟空格、“Section”属性和右括号中的值。
For example, with an input of:
例如，输入为：
See <relref section="2.3" target="RFC9999" displayFormat="parens"/> for an overview.
有关概述，请参见<relref section=“2.3”target=“RFC9999”displayFormat=“parens”/>。
An HTML formatter might generate:
HTML格式化程序可能会生成：
See [<a href="#RFC9999">RFC9999</a>] (<a href="http://www.rfc-editor.org/info/rfc9999#s-2.3"> Section 2.3</a>) for an overview.
请参见[<a href=“#RFC9999”>RFC9999</a>”（<a href=”http://www.rfc-editor.org/info/rfc9999#s-2.3“>第2.3节（概述）。
"bare"
“裸体”
A formatter should display the relative reference as the contents of the "section" attribute and nothing else. This is useful when there are multiple relative references to a single base reference.
格式化程序应该将相对引用显示为“section”属性的内容，而不是其他内容。当有多个相对引用指向单个基准引用时，这非常有用。
For example:
例如：
See Sections <relref section="2.3" target="RFC9999" displayFormat="bare"/> and <relref section="2.4" target="RFC9999" displayFormat="of"/> for an overview.
有关概述，请参见章节<relref section=“2.3”target=“RFC9999”displayFormat=“bare”/>和<relref section=“2.4”target=“RFC9999”displayFormat=“of”/>。
An HTML formatter might generate:
HTML格式化程序可能会生成：
See Sections <a href="http://www.rfc-editor.org/info/rfc9999#s-2.3"> 2.3</a> and <a href="http://www.rfc-editor.org/info/rfc9999#s-2.4"> Section 2.4</a> of [<a href="#RFC9999">RFC9999</a>] for an overview.
请参见章节<a href=”http://www.rfc-editor.org/info/rfc9999#s-2.3“>2.3</a>和<a href=”http://www.rfc-editor.org/info/rfc9999#s-2.4“>RFC9999</a>]第2.4节的概述。
Allowed values:
允许值：
o "of" (default)
o “of”（默认）
o "comma"
o “逗号”
o "parens"
o “帕伦斯”
o "bare"
o “裸体”
Specifies a relative reference from the URI in the target reference. This value must include whatever leading character is needed to create the relative reference; typically, this is "#" for HTML documents.
从目标引用中的URI指定相对引用。该值必须包括创建相对引用所需的任何主角；通常，对于HTML文档，这是“#”。
Specifies a section of the target reference. If the reference is not an RFC or Internet-Draft in the v3 format, it is an error.
指定目标引用的一部分。如果引用不是v3格式的RFC或Internet草稿，则为错误。
The anchor of the reference for this element. If this value is not an anchor to a <reference> or <referencegroup> element, it is an error. If the reference at the target has no URI, it is an error.
此元素的引用的锚点。如果此值不是<reference>或<referencegroup>元素的锚点，则为错误。如果目标处的引用没有URI，则为错误。
This is the root element of the xml2rfc vocabulary.
这是xml2rfc词汇表的根元素。
Content model:
内容模型：
In this order:
按此顺序：
1. Optional <link> elements (Section 2.30)
1. 可选<link>元素（第2.30节）
2. One <front> element (Section 2.26)
2. 一个<front>元件（第2.26节）
3. One <middle> element (Section 2.31)
3. 一个<middle>元素（第2.31节）
4. One optional <back> element (Section 2.8)
4. 一个可选<back>元件（第2.8节）
Deprecated; instead, use the "name" attribute in <seriesInfo>.
不赞成；相反，请使用<serieinfo>中的“name”属性。
Affects the generated boilerplate. Note that the values of "no" and "yes" are deprecated and are replaced by "false" (the default) and "true".
影响生成的样板文件。请注意，“no”和“yes”的值已被弃用，并由“false”（默认值）和“true”替换。
See [RFC7841] for more information.
有关更多信息，请参阅[RFC7841]。
Allowed values:
允许值：
o "no"
o “没有”
o "yes"
o “是的”
o "false" (default)
o “false”（默认值）
o "true"
o “对”
Deprecated; instead, use the "value" attribute in <seriesInfo>.
不赞成；相反，请使用<serieinfo>中的“value”属性。
Specifies whether or not a formatter is requested to include an index in generated files. If the source file has no <iref> elements, an index is never generated. This option is useful for generating documents where the source document has <iref> elements but the author no longer wants an index.
指定是否请求格式化程序在生成的文件中包含索引。如果源文件没有<iref>元素，则永远不会生成索引。此选项对于生成源文档包含<iref>元素但作者不再需要索引的文档非常有用。
Allowed values:
允许值：
o "true" (default)
o “true”（默认值）
o "false"
o “假”
Represents the Intellectual Property status of the document. See Appendix A.1 for details.
表示文档的知识产权状态。详见附录A.1。
Identifies a single section within the document for which extraction "as is" is explicitly allowed (only relevant for historic values of the "ipr" attribute).
标识文档中明确允许提取“原样”的单个节（仅与“ipr”属性的历史值相关）。
Deprecated; instead, use the "value" attribute in <seriesInfo>.
不赞成；相反，请使用<serieinfo>中的“value”属性。
A comma-separated list of RFC numbers or Internet-Draft names.
以逗号分隔的RFC编号或Internet草稿名称列表。
The prep tool will parse the attribute value so that incorrect references can be detected.
prep工具将解析属性值，以便检测不正确的引用。
The date that the XML was processed by a prep tool. This is included in the XML file just before it is saved to disk. The value is formatted using the "date-time" format defined in Section 5.6 of [RFC3339]. The "time-offset" should be "Z".
准备工具处理XML的日期。在将XML文件保存到磁盘之前，它包含在XML文件中。该值使用[RFC3339]第5.6节中定义的“日期-时间”格式进行格式化。“时间偏移”应为“Z”。
Deprecated; instead, use the "value" attribute in <seriesInfo>.
不赞成；相反，请使用<serieinfo>中的“value”属性。
Specifies whether or not the prep tool will sort the references in each reference section.
指定准备工具是否对每个引用节中的引用进行排序。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
The document stream, as described in [RFC7841]. (The RFC Series Editor may change the list of allowed values in the future.)
文档流，如[RFC7841]中所述。（RFC系列编辑器将来可能会更改允许值的列表。）
Allowed values:
允许值：
o "IETF" (default)
o “IETF”（默认值）
o "IAB"
o “IAB”
o "IRTF"
o “IRTF”
o "independent"
o “独立的”
Specifies whether or not a formatter is requested to use symbolic references (such as "[RFC2119]"). If the value for this is "false", the references come out as numbers (such as "[3]").
指定是否请求格式化程序使用符号引用（如“[RFC2119]”）。如果该值为“false”，则引用将显示为数字（如“[3]”）。
Allowed values:
允许值：
o "true" (default)
o “true”（默认值）
o "false"
o “假”
Specifies the number of levels of headings that a formatter is requested to include in the table of contents; the default is "3".
指定要求格式化程序在目录中包含的标题级别数；默认值为“3”。
Specifies whether or not a formatter is requested to include a table of contents in generated files.
指定是否请求格式化程序在生成的文件中包含目录。
Allowed values:
允许值：
o "true" (default)
o “true”（默认值）
o "false"
o “假”
A comma-separated list of RFC numbers or Internet-Draft names.
以逗号分隔的RFC编号或Internet草稿名称列表。
The prep tool will parse the attribute value so that incorrect references can be detected.
prep工具将解析属性值，以便检测不正确的引用。
Specifies the version of xml2rfc syntax used in this document. The only expected value (for now) is "3".
指定本文档中使用的xml2rfc语法的版本。唯一的期望值（目前）是“3”。
Represents a section (when inside a <middle> element) or an appendix (when inside a <back> element).
表示节（位于<middle>元素内部时）或附录（位于<back>元素内部时）。
Subsections are created by nesting <section> elements inside <section> elements. Sections are allowed to be empty.
子部分是通过在<section>元素中嵌套<section>元素来创建的。节允许为空。
This element appears as a child element of <back> (Section 2.8), <boilerplate> (Section 2.11), <middle> (Section 2.31), and <section> (Section 2.46).
此元素显示为<back>（第2.8节）、<boilerplate>（第2.11节）、<middle>（第2.31节）和<Section>（第2.46节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <name> element (Section 2.32)
1. 一个可选的<name>元素（第2.32节）
2. In any order:
2. 以任何顺序：
* <artwork> elements (Section 2.5)
* <artwork> elements (Section 2.5)
* <aside> elements (Section 2.6)
* <aside> elements (Section 2.6)
* <blockquote> elements (Section 2.10)
* <blockquote> elements (Section 2.10)
* <dl> elements (Section 2.20)
* <dl> elements (Section 2.20)
* <figure> elements (Section 2.25)
* <figure> elements (Section 2.25)
* <iref> elements (Section 2.27)
* <iref> elements (Section 2.27)
* <ol> elements (Section 2.34)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <t> elements (Section 2.53)
* <table> elements (Section 2.54)
* <table> elements (Section 2.54)
* <texttable> elements (Section 3.8)
* <texttable> elements (Section 3.8)
* <ul> elements (Section 2.63)
* <ul> elements (Section 2.63)
3. Optional <section> elements (Section 2.46)
3. 可选<section>元素（第2.46节）
Document-wide unique identifier for this section.
此节的文档范围唯一标识符。
If set to "false", the formatter is requested to not display a section number. The prep tool will verify that such a section is not followed by a numbered section in this part of the document and will verify that the section is a top-level section.
如果设置为“false”，则要求格式化程序不显示节号。准备工具将验证该部分文件中该节后面是否有编号的节，并验证该节是否为顶层节。
Allowed values:
允许值：
o "true" (default)
o “true”（默认值）
o "false"
o “假”
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."
如果设置为“true”，则此注释将在准备工具中标记为文本，指示在文档作为RFC发布之前应将其删除。该文本将为“此注释在作为RFC发布之前删除。”
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
Deprecated. Use <name> instead.
不赞成。改用<name>。
Indicates to a formatter whether or not the section is to be included in a table of contents, if such a table of contents is produced. This only takes effect if the level of the section would have appeared in the table of contents based on the "tocDepth" attribute of the <rfc> element, and of course only if the table of contents is being created based on the "tocInclude" attribute of the <rfc> element. If this is set to "exclude", any section below this one will be excluded as well. The "default" value indicates inclusion of the section if it would be included by the tocDepth attribute of the <rfc> element.
如果生成目录，则向格式化程序指示该节是否包含在目录中。这仅在节的级别基于<rfc>元素的“tocDepth”属性出现在目录中时生效，当然也仅在目录基于<rfc>元素的“tocInclude”属性创建时生效。如果该选项设置为“排除”，则此选项下的任何部分也将被排除。如果节将被<rfc>元素的tocDepth属性包含，则“default”值表示包含该节。
Allowed values:
允许值：
o "include"
o “包括”
o "exclude"
o “排除”
o "default" (default)
o “默认”（默认）
Specifies the document series in which this document appears, and also specifies an identifier within that series.
指定此文档出现的文档系列，并指定该系列中的标识符。
A processing tool determines whether it is working on an RFC or an Internet-Draft by inspecting the "name" attribute of a <seriesInfo> element inside the <front> element inside the <rfc> element, looking for "RFC" or "Internet-Draft". (Specifying neither value in any of the <seriesInfo> elements can be useful for producing other types of documents but is out of scope for this specification.)
处理工具通过检查<RFC>元素中<front>元素中<serieinfo>元素的“name”属性，查找“RFC”或“Internet草稿”，来确定它是在处理RFC还是在处理Internet草稿。（在任何<serieinfo>元素中指定任何一个值都不会对生成其他类型的文档有用，但不在本规范的范围内。）
It is invalid to have multiple <seriesInfo> elements inside the same <front> element containing the same "name" value. Some combinations of <seriesInfo> "name" attribute values make no sense, such as having both <seriesInfo name="rfc"/> and <seriesInfo name="Internet-Draft"/> in the same <front> element.
在同一<front>元素中包含多个包含相同“name”值的<serieinfo>元素是无效的。<serieinfo>“name”属性值的某些组合毫无意义，例如在同一个<front>元素中同时包含<serieinfo name=“rfc”/>和<serieinfo name=“internetdraft”/>。
This element appears as a child element of <front> (Section 2.26) and <reference> (Section 2.40; deprecated in this context).
此元素显示为<front>（第2.26节）和<reference>（第2.40节；在本文中已弃用）的子元素。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
The ASCII equivalent of the name field.
名称字段的ASCII等效项。
The ASCII equivalent of the value field.
值字段的ASCII等效项。
The name of the series. The currently known values are "RFC", "Internet-Draft", and "DOI". The RFC Series Editor may change this list in the future.
系列的名称。目前已知的值是“RFC”、“Internet草稿”和“DOI”。RFC系列编辑器将来可能会更改此列表。
Some of the values for "name" interact as follows:
“name”的某些值的交互作用如下：
o If a <front> element contains a <seriesInfo> element with a name of "Internet-Draft", it can also have at most one additional <seriesInfo> element with a "status" attribute whose value is of "standard", "full-standard", "bcp", "fyi", "informational", "experimental", or "historic" to indicate the intended status of this Internet-Draft, if it were to be later published as an RFC. If such an additional <seriesInfo> element has one of those statuses, the name needs to be "".
o 如果<front>元素包含一个名为“Internet草稿”的<seriesInfo>元素，则它最多还可以有一个附加的<seriesInfo>元素，该元素的“状态”属性的值为“标准”、“完全标准”、“bcp”、“fyi”、“信息”、“实验”或“历史”，以指示此Internet草稿的预期状态，如果以后以RFC的形式发布。如果这样一个附加的<serieinfo>元素具有这些状态之一，则名称需要为“”。
o If a <front> element contains a <seriesInfo> element with a name of "RFC", it can also have at most one additional <seriesInfo> element with a "status" attribute whose value is of "full-standard", "bcp", or "fyi" to indicate the current status of this RFC. If such an additional <seriesInfo> element has one of those statuses, the "value" attribute for that name needs to be the number within that series. That <front> element might also contain an additional <seriesInfo> element with the status of "info", "exp", or "historic" and a name of "" to indicate the status of the RFC.
o 如果<front>元素包含一个名为“RFC”的<serieinfo>元素，则它最多还可以有一个附加的<serieinfo>元素，该元素的“status”属性的值为“full standard”、“bcp”或“fyi”，以指示此RFC的当前状态。如果这样一个附加的<serieinfo>元素具有这些状态之一，则该名称的“value”属性必须是该序列中的数字。该<front>元素还可能包含另一个<serieinfo>元素，其状态为“info”、“exp”或“historic”，名称为“”，以指示RFC的状态。
o A <front> element that has a <seriesInfo> element that has the name "Internet-Draft" cannot also have a <seriesInfo> element that has the name "RFC".
o 具有名为“Internet草稿”的<seriesInfo>元素的<front>元素不能也具有名为“RFC”的<seriesInfo>元素。
o The <seriesInfo> element can contain the DOI for the referenced document. This cannot be used when the <seriesInfo> element is an eventual child element of an <rfc> element -- only as an eventual child of a <reference> element. The "value" attribute should use the form specified in [RFC7669].
o 元素可以包含引用文档的DOI。当<seriesInfo>元素是<rfc>元素的最终子元素时，不能使用此选项——只能作为<reference>元素的最终子元素。“value”属性应使用[RFC7669]中指定的格式。
The status of this document. The currently known values are "standard", "informational", "experimental", "bcp", "fyi", and "full-standard". The RFC Series Editor may change this list in the future.
此文档的状态。目前已知的值为“标准”、“信息”、“实验”、“bcp”、“fyi”和“全标准”。RFC系列编辑器将来可能会更改此列表。
The stream (as described in [RFC7841]) that originated the document. (The RFC Series Editor may change this list in the future.)
生成文档的流（如[RFC7841]中所述）。（RFC系列编辑器将来可能会更改此列表。）
Allowed values:
允许值：
o "IETF" (default)
o “IETF”（默认值）
o "IAB"
o “IAB”
o "IRTF"
o “IRTF”
o "independent"
o “独立的”
The identifier within the series specified by the "name" attribute.
由“name”属性指定的序列中的标识符。
For BCPs, FYIs, RFCs, and STDs, this is the number within the series. For Internet-Drafts, it is the full draft name (ending with the two-digit version number). For DOIs, the value is given, such as "10.17487/rfc1149", as described in [RFC7669].
对于BCP、FYI、RFC和STD，这是系列中的数字。对于Internet草稿，它是完整的草稿名称（以两位数版本号结尾）。对于DOI，如[RFC7669]中所述，给出了值，如“10.17487/rfc1149”。
The name in the value should be the document name without any file extension. For Internet-Drafts, the value for this attribute should be "draft-ietf-somewg-someprotocol-07", not "draft-ietf-somewg-someprotocol-07.txt".
值中的名称应为不带任何文件扩展名的文档名称。对于Internet草稿，此属性的值应为“draft-ietf-somewg-someprotocol-07”，而不是“draft-ietf-somewg-someprotocol-07.txt”。
This element allows the inclusion of source code into the document.
此元素允许在文档中包含源代码。
When rendered, source code is always shown in a monospace font. When <sourcecode> is a child of <figure> or <section>, it provides full control of horizontal whitespace and line breaks. When formatted, it is indented relative to the left margin of the enclosing element. It is thus useful for source code and formal languages (such as ABNF [RFC5234] or the RNC notation used in this document). (When <sourcecode> is a child of other elements, it flows with the text that surrounds it.) Tab characters (U+0009) inside of this element are prohibited.
呈现时，源代码始终以单空格字体显示。当<sourcecode>是<figure>或<section>的子级时，它提供对水平空白和换行符的完全控制。格式化后，它将相对于封闭元素的左边距缩进。因此，它对于源代码和正式语言（如ABNF[RFC5234]或本文档中使用的RNC符号）非常有用。（当<sourcecode>是其他元素的子元素时，它与围绕它的文本一起流动。）禁止使用此元素内的制表符（U+0009）。
For artwork such as character-based art, diagrams of message layouts, and so on, use the <artwork> element instead.
对于基于字符的艺术、消息布局图等艺术品，请使用<artwork>元素。
Output formatters that do pagination should attempt to keep source code on a single page. This is to prevent source code that is split across pages from looking like two separate pieces of code.
执行分页的输出格式化程序应尝试将源代码保留在单个页面上。这是为了防止跨页面拆分的源代码看起来像两段独立的代码。
See Section 5 for a description of how to deal with issues of using "&" and "<" characters in source code.
有关如何在源代码中使用“&”和“<”字符的说明，请参见第5节。
This element appears as a child element of <blockquote> (Section 2.10), <dd> (Section 2.18), <figure> (Section 2.25), <li> (Section 2.29), <section> (Section 2.46), <td> (Section 2.56), and <th> (Section 2.58).
此元素显示为<blockquote>（第2.10节）、<dd>（第2.18节）、<figure>（第2.25节）、<li>（第2.29节）、<Section>（第2.46节）、<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
Document-wide unique identifier for this source code.
此源代码的文档范围唯一标识符。
A filename suitable for the contents (such as for extraction to a local file). This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code). Note that the "name" attribute does not need to be unique for <artwork> elements in a document. If multiple <sourcecode> elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.
适合于内容的文件名（例如用于提取到本地文件）。此属性对于其他类型的工具（例如自动语法检查器，它通过提取源代码来工作）很有帮助。请注意，“name”属性对于文档中的<artwork>元素不需要是唯一的。如果多个<sourcecode>元素具有相同的“name”属性，则格式化程序可能会假定这些元素都是单个文件的片段，这样的格式化程序可以收集这些片段以供以后处理。
The URI reference of a source file [RFC3986].
源文件[RFC3986]的URI引用。
It is an error to have both a "src" attribute and content in the <sourcecode> element.
在<sourcecode>元素中同时具有“src”属性和内容是错误的。
Specifies the type of the source code. The value of this attribute is free text with certain values designated as preferred.
指定源代码的类型。此属性的值是自由文本，其中某些值指定为首选值。
The preferred values for <sourcecode> types are:
<sourcecode>类型的首选值为：
o abnf
o 荷兰银行
o asn.1
o asn.1
o bash
o 猛击
o c++
o C++
o c
o C
o cbor
o cbor
o dtd
o dtd
o java
o JAVA
o javascript
o javascript
o json
o json
o mib
o mib
o perl
o perl
o pseudocode
o 伪码
o python
o python
o rnc
o rnc
o xml
o xml
o yang
o 杨
The RFC Series Editor will maintain a complete list of the preferred values on the RFC Editor web site, and that list is expected to be updated over time. Thus, a consumer of v3 XML should not cause a failure when it encounters an unexpected type or no type is specified.
RFC系列编辑器将在RFC编辑器网站上维护首选值的完整列表，该列表预计会随着时间的推移而更新。因此，V3XML的使用者在遇到意外类型或未指定类型时不应导致失败。
Provides a street address.
提供街道地址。
This element appears as a child element of <postal> (Section 2.37).
此元素显示为<postal>的子元素（第2.37节）。
Content model: only text content.
内容模型：仅文本内容。
The ASCII equivalent of the street address.
相当于街道地址的ASCII码。
Indicates text that is semantically strong. Text enclosed within this element will be displayed as bold 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), <em> (Section 2.22), <li> (Section 2.29), <preamble> (Section 3.6), <refcontent> (Section 2.39), <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).
该元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<Premission>（第3.6节）、<refcontent>（第2.39节）、<sub>（第2.51节）、<sup>（第2.52节）、<t>（第2.53节）、<td>（第2.56节）的子元素，<th>（第2.58节）和<tt>（第2.62节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
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), <blockquote> (Section 2.10), <cref> (Section 2.16), <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), <t> (Section 2.53), <td> (Section 2.56), <th> (Section 2.58), and <tt> (Section 2.62).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<Premission>（第3.6节）、<refcontent>（第2.39节）、<strong>（第2.50节）、<t>（第2.53节）、<td>（第2.56节）、<th>（第2.58节）的子元素，和<tt>（第2.62节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
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.
使文本显示为上标，大约比正常文本高半个字母。此元素可以与其他字符格式元素组合，并且格式将是相加的。
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), <em> (Section 2.22), <li> (Section 2.29), <preamble> (Section 3.6), <refcontent> (Section 2.39), <strong> (Section 2.50), <t> (Section 2.53), <td> (Section 2.56), <th> (Section 2.58), and <tt> (Section 2.62).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<Premission>（第3.6节）、<refcontent>（第2.39节）、<strong>（第2.50节）、<t>（第2.53节）、<td>（第2.56节）、<th>（第2.58节）的子元素，和<tt>（第2.62节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Contains a paragraph of text.
包含一段文字。
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), <list> (Section 3.4), <note> (Section 2.33), <section> (Section 2.46), <td> (Section 2.56), and <th> (Section 2.58).
此元素显示为<abstract>（第2.1节）、<aside>（第2.6节）、<blockquote>（第2.10节）、<dd>（第2.18节）、<li>（第2.29节）、<list>（第3.4节）、<note>（第2.33节）、<Section>（第2.46节）、<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <list> elements (Section 3.4)
o <list>元素（第3.4节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <spanx> elements (Section 3.7)
o <spanx>元件（第3.7节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <vspace> elements (Section 3.10)
o <vspace>元素（第3.10节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Document-wide unique identifier for this paragraph.
此段落的文档范围唯一标识符。
Deprecated. Instead, use <dd> inside of a definition list (<dl>).
不赞成。相反，在定义列表（<dl>）中使用<dd>。
Acts as a hint to the output formatters that do pagination to do a best-effort attempt to keep the paragraph with the next element, whatever that happens to be. For example, the HTML output @media print CSS ("CSS" refers to Cascading Style Sheets) might translate this to page-break-after: avoid. For PDF, the paginator could attempt to keep the paragraph with the next element. Note: this attribute is strictly a hint and not always actionable.
作为对进行分页的输出格式化程序的提示，尽最大努力将段落保留在下一个元素中，不管发生什么情况。例如，HTML输出@media print CSS（“CSS”指级联样式表）可能会将其转换为：avoid之后的分页符。对于PDF，分页器可以尝试在段落中保留下一个元素。注意：这个属性只是一个提示，并不总是可以操作的。
Allowed values:
允许值：
o "false" (default)
o “false”（默认值）
o "true"
o “对”
Acts as a hint to the output formatters that do pagination to do a best-effort attempt to keep the paragraph with the previous element, whatever that happens to be. For example, the HTML output @media print CSS might translate this to page-break-before: avoid. For PDF, the paginator could attempt to keep the paragraph with the previous element. Note: this attribute is strictly a hint and not always actionable.
作为对进行分页的输出格式化程序的提示，尽最大努力使段落与前一个元素保持一致，不管发生什么情况。例如，HTML输出@media print CSS可能会将此转换为：avoid之前的分页符。对于PDF，分页器可以尝试使用前面的元素保留段落。注意：这个属性只是一个提示，并不总是可以操作的。
Allowed values:
允许值：
o "false" (default)
o “false”（默认值）
o "true"
o “对”
Contains a table with a caption with the table number. If the element contains a <name> element, the caption will also show that name.
包含带有标题和表号的表。如果元素包含<name>元素，则标题也将显示该名称。
Inside the <table> element is, optionally, a <thead> element to contain the rows that will be the table's heading and, optionally, a <tfoot> element to contain the rows of the table's footer. If the XML is converted to a representation that has page breaks (such as PDFs or printed HTML), the header and footer are meant to appear on each page.
在<table>元素中，可以选择一个<thead>元素来包含将作为表标题的行，也可以选择一个<tfoot>元素来包含表尾的行。如果XML转换为具有分页符的表示形式（如PDF或打印的HTML），则页眉和页脚将显示在每个页面上。
This element appears as a child element of <aside> (Section 2.6) and <section> (Section 2.46).
此元素显示为<aside>（第2.6节）和<Section>（第2.46节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <name> element (Section 2.32)
1. 一个可选的<name>元素（第2.32节）
2. Optional <iref> elements (Section 2.27)
2. 可选<iref>元件（第2.27节）
3. One optional <thead> element (Section 2.59)
3. 一个可选的<thead>元件（第2.59节）
4. One or more <tbody> elements (Section 2.55)
4. 一个或多个<t车身>元件（第2.55节）
5. One optional <tfoot> element (Section 2.57)
5. 一个可选的<tfoot>元素（第2.57节）
Document-wide unique identifier for this table.
此表的文档范围唯一标识符。
A container for a set of body rows for a table.
表的一组正文行的容器。
This element appears as a child element of <table> (Section 2.54).
此元素显示为<表>（第2.54节）的子元素。
Content model:
内容模型：
One or more <tr> elements (Section 2.61)
一个或多个<tr>元件（第2.61节）
Document-wide unique identifier for the tbody.
tbody的文档范围唯一标识符。
A cell in a table row.
表行中的单元格。
This element appears as a child element of <tr> (Section 2.61).
此元素显示为<tr>的子元素（第2.61节）。
Content model:
内容模型：
Either:
要么：
In any order, but at least one of:
以任何顺序，但至少一种：
* <artwork> elements (Section 2.5)
* <artwork> elements (Section 2.5)
* <dl> elements (Section 2.20)
* <dl> elements (Section 2.20)
* <figure> elements (Section 2.25)
* <figure> elements (Section 2.25)
* <ol> elements (Section 2.34)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
* <ul> elements (Section 2.63)
Or:
或：
In any order:
以任何顺序：
* Text
* 文本
* <bcp14> elements (Section 2.9)
* <bcp14> elements (Section 2.9)
* <br> elements (Section 2.12)
* <br> elements (Section 2.12)
* <cref> elements (Section 2.16)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
* <xref> elements (Section 2.66)
Controls whether the content of the cell appears left justified (default), centered, or right justified. Note that "center" or "right" will probably only work well in cells with plain text; any other elements might make the contents render badly.
控制单元格内容是左对齐（默认）、居中还是右对齐。请注意，“居中”或“右”可能只适用于纯文本单元格；任何其他元素都可能使内容呈现不好。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
Document-wide unique identifier for the cell.
单元格的文档范围唯一标识符。
The number of columns that the cell is to span. For example, setting "colspan='3'" indicates that the cell occupies the same horizontal space as three cells of a row without any "colspan" attributes.
单元格要跨越的列数。例如，设置“colspan='3'”表示该单元格与一行中的三个单元格占用相同的水平空间，但没有任何“colspan”属性。
The number of rows that the cell is to span. For example, setting "rowspan='3'" indicates that the cell occupies the same vertical space as three rows.
单元格要跨越的行数。例如，设置“rowspan='3'”表示单元格与三行占用相同的垂直空间。
A container for a set of footer rows for a table.
表的一组页脚行的容器。
This element appears as a child element of <table> (Section 2.54).
此元素显示为<表>（第2.54节）的子元素。
Content model:
内容模型：
One or more <tr> elements (Section 2.61)
一个或多个<tr>元件（第2.61节）
Document-wide unique identifier for the tfoot.
tfoot的文档范围唯一标识符。
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.
表行中的单元格。渲染时，通常以粗体显示；除此之外，此元素与<td>元素之间没有区别。
This element appears as a child element of <tr> (Section 2.61).
此元素显示为<tr>的子元素（第2.61节）。
Content model:
内容模型：
Either:
要么：
In any order, but at least one of:
以任何顺序，但至少一种：
* <artwork> elements (Section 2.5)
* <artwork> elements (Section 2.5)
* <dl> elements (Section 2.20)
* <dl> elements (Section 2.20)
* <figure> elements (Section 2.25)
* <figure> elements (Section 2.25)
* <ol> elements (Section 2.34)
* <ol> elements (Section 2.34)
* <sourcecode> elements (Section 2.48)
* <sourcecode> elements (Section 2.48)
* <t> elements (Section 2.53)
* <t> elements (Section 2.53)
* <ul> elements (Section 2.63)
* <ul> elements (Section 2.63)
Or:
或：
In any order:
以任何顺序：
* Text
* 文本
* <bcp14> elements (Section 2.9)
* <bcp14> elements (Section 2.9)
* <br> elements (Section 2.12)
* <br> elements (Section 2.12)
* <cref> elements (Section 2.16)
* <cref> elements (Section 2.16)
* <em> elements (Section 2.22)
* <em> elements (Section 2.22)
* <eref> elements (Section 2.24)
* <eref> elements (Section 2.24)
* <iref> elements (Section 2.27)
* <iref> elements (Section 2.27)
* <relref> elements (Section 2.44)
* <relref> elements (Section 2.44)
* <strong> elements (Section 2.50)
* <strong> elements (Section 2.50)
* <sub> elements (Section 2.51)
* <sub> elements (Section 2.51)
* <sup> elements (Section 2.52)
* <sup> elements (Section 2.52)
* <tt> elements (Section 2.62)
* <tt> elements (Section 2.62)
* <xref> elements (Section 2.66)
* <xref> elements (Section 2.66)
Controls whether the content of the cell appears left justified (default), centered, or right justified. Note that "center" or "right" will probably only work well in cells with plain text; any other elements might make the contents render badly.
控制单元格内容是左对齐（默认）、居中还是右对齐。请注意，“居中”或“右”可能只适用于纯文本单元格；任何其他元素都可能使内容呈现不好。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
Document-wide unique identifier for the row.
行的文档范围唯一标识符。
The number of columns that the cell is to span. For example, setting "colspan='3'" indicates that the cell occupies the same horizontal space as three cells of a row without any "colspan" attributes.
单元格要跨越的列数。例如，设置“colspan='3'”表示该单元格与一行中的三个单元格占用相同的水平空间，但没有任何“colspan”属性。
The number of rows that the cell is to span. For example, setting "rowspan='3'" indicates that the cell occupies the same vertical space as three rows.
单元格要跨越的行数。例如，设置“rowspan='3'”表示单元格与三行占用相同的垂直空间。
A container for a set of header rows for a table.
表的一组标题行的容器。
This element appears as a child element of <table> (Section 2.54).
此元素显示为<表>（第2.54节）的子元素。
Content model:
内容模型：
One or more <tr> elements (Section 2.61)
一个或多个<tr>元件（第2.61节）
Document-wide unique identifier for the thead.
THAD的文档范围唯一标识符。
Represents the document title.
表示文档标题。
When this element appears in the <front> element of the current document, the title might also appear in page headers or footers. If it is long (~40 characters), the "abbrev" attribute can be used to specify an abbreviated variant.
当此元素出现在当前文档的<front>元素中时，标题也可能出现在页眉或页脚中。如果是长的（~40个字符），“abbrev”属性可用于指定缩写变量。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model: only text content.
内容模型：仅文本内容。
Specifies an abbreviated variant of the document title.
指定文档标题的缩写变体。
The ASCII equivalent of the title.
标题的ASCII等价物。
A row of a table.
一排桌子。
This element appears as a child element of <tbody> (Section 2.55), <tfoot> (Section 2.57), and <thead> (Section 2.59).
此元素显示为<tbody>（第2.55节）、<tfoot>（第2.57节）和<thead>（第2.59节）的子元素。
Content model:
内容模型：
In any order, but at least one of:
以任何顺序，但至少一种：
o <td> elements (Section 2.56)
o <td>要素（第2.56节）
o <th> elements (Section 2.58)
o <th>元件（第2.58节）
Document-wide unique identifier for the row.
行的文档范围唯一标识符。
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), <blockquote> (Section 2.10), <cref> (Section 2.16), <dd> (Section 2.18), <dt> (Section 2.21), <em> (Section 2.22), <li> (Section 2.29), <name> (Section 2.32), <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), and <th> (Section 2.58).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<name>（第2.32节）、<Premission>（第3.6节）、<refcontent>（第2.39节）、<strong>（第2.50节）、<sub>（第2.51节）、<sup>（第2.52节）、<t>（第2.53节）、<td>（第2.56节）和<th>（第2.58节）。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <relref> elements (Section 2.44)
o <relref>元素（第2.44节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
An unordered list. The labels on the items will be symbols picked by the formatter.
无序的名单。项目上的标签将是格式化程序拾取的符号。
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).
此元素显示为<abstract>（第2.1节）、<aside>（第2.6节）、<blockquote>（第2.10节）、<dd>（第2.18节）、<li>（第2.29节）、<note>（第2.33节）、<Section>（第2.46节）、<td>（第2.56节）和<th>（第2.58节）的子元素。
Content model:
内容模型：
One or more <li> elements (Section 2.29)
一个或多个<li>元件（第2.29节）
Document-wide unique identifier for the list.
列表的文档范围唯一标识符。
Defines whether or not the label is empty. empty="true" indicates that no label will be shown.
定义标签是否为空。empty=“true”表示不显示标签。
Allowed values:
允许值：
o "false" (default)
o “false”（默认值）
o "true"
o “对”
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.
定义条目之间是否有空行。spacing=“normal”表示单个空行，spacing=“compact”表示空行之间没有空格。
Allowed values:
允许值：
o "normal" (default)
o “正常”（默认）
o "compact"
o “紧凑型”
Contains a web address associated with the author.
包含与作者关联的网址。
The contents should be a valid URI; this most likely will be an "http:" or "https:" URI.
内容应该是有效的URI；这很可能是一个“http:”或“https:”URI。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
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).
此元素用于指定文件来源的工作组（IETF）或研究组（IRTF）（如有）。建议的格式是工作组的正式名称（略加大写）。
In Internet-Drafts, this is used in the upper left corner of the boilerplate, replacing the "Network Working Group" string. Formatting software can append the words "Working Group" or "Research Group", depending on the "submissionType" property of the <rfc> element (Section 2.45.12).
在InternetDrafts中，这在样板文件的左上角使用，取代了“NetworkWorkingGroup”字符串。格式化软件可以根据<rfc>元素的“submissionType”属性（第2.45.12节）添加单词“工作组”或“研究组”。
This element appears as a child element of <front> (Section 2.26).
此元素显示为<front>的子元素（第2.26节）。
Content model: only text content.
内容模型：仅文本内容。
A reference to an anchor in this document. Formatters that have links (such as HTML and PDF) are likely to render <xref> elements as internal hyperlinks. This element is useful for referring to references in the "References" section, to specific sections of this document, to specific figures, and so on. The "target" attribute is required.
本文件中对锚的引用。具有链接（如HTML和PDF）的格式化程序可能将<xref>元素呈现为内部超链接。此元素对于引用“参考”部分中的参考、本文件的特定章节、特定图形等非常有用。“target”属性是必需的。
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).
此元素显示为<annotation>（第2.3节）、<blockquote>（第2.10节）、<c>（第3.1节）、<cref>（第2.16节）、<dd>（第2.18节）、<dt>（第2.21节）、<em>（第2.22节）、<li>（第2.29节）、<name>（第2.32节）、<postamble>（第3.5节）、<preamble>（第3.6节）、<strong>（第2.50节）、<sub>（第2.51节）的子元素，<sup>（第2.52节）、<t>（第2.53节）、<td>（第2.56节）、<th>（第2.58节）、<tt>（第2.62节）和<ttcol>（第3.9节）。
Content model: only text content.
内容模型：仅文本内容。
This attribute signals to formatters what the desired format of the reference should be. Formatters for document types that have linking capability should wrap the displayed text in hyperlinks.
此属性向格式化程序发出所需引用格式的信号。具有链接功能的文档类型的格式化程序应将显示的文本包装为超链接。
"counter"
“柜台”
The "derivedContent" attribute will contain just a counter. This is used for targets that are <section>, <figure>, <table>, or items in an ordered list. Using "format='counter'" where the target is any other type of element is an error.
“derivedContent”属性将只包含一个计数器。这用于<section>、<figure>、<table>或有序列表中的项目。如果目标是任何其他类型的元素，则使用“format='counter'”是错误的。
For example, with an input of:
例如，输入为：
<section anchor="overview">Protocol Overview</section> . . . See Section <xref target="overview" format="counter"/> for an overview.
协议概述。有关概述，请参见章节<xref target=“overview”format=“counter”/>。
An HTML formatter might generate:
HTML格式化程序可能会生成：
See Section <a href="#overview">1.7</a> for an overview.
有关概述，请参阅第1.7节。
"default"
“默认值”
If the element has no content, the "derivedContent" attribute will contain a text fragment that describes the referenced part completely, such as "XML" for a target that is a <reference>, or "Section 2" or "Table 4" for a target to a non-reference. (If the element has content, the "derivedContent" attribute is filled with the content.)
如果元素没有内容，“derivedContent”属性将包含一个完整描述引用部分的文本片段，例如对于<reference>的目标，“XML”，对于非引用的目标，“Section 2”或“Table 4”。（如果元素包含内容，“derivedContent”属性将填充内容。）
For example, with an input of:
例如，输入为：
<section anchor="overview">Protocol Overview</section> . . . See <xref target="overview"/> for an overview.
协议概述。有关概述，请参见<xref target=“overview”/>。
An HTML formatter might generate:
HTML格式化程序可能会生成：
See <a href="#overview">Section 1.7</a> for an overview.
请参阅第1.7节的概述。
"none"
“没有”
Deprecated.
不赞成。
"title"
“标题”
If the target is a <reference> element, the "derivedContent" attribute will contain the name of the reference, extracted from the <title> child of the <front> child of the reference. Or, if the target element has a <name> child element, the "derivedContent" attribute will contain the text content of that <name> element concatenated with the text content of each descendant node of <name> (that is, stripping out all of the XML markup, leaving only the text). Or, if the target element does not contain a <name> child element, the "derivedContent" attribute will contain the name of the "anchor" attribute of that element with no other adornment.
如果目标是<reference>元素，“derivedContent”属性将包含引用的名称，该名称从引用的<front>子元素的<title>子元素中提取。或者，如果目标元素有一个子元素<name>，则“derivedContent”属性将包含该<name>元素的文本内容，并与<name>的每个子节点的文本内容连接在一起（即剥离所有XML标记，只留下文本）。或者，如果目标元素不包含<name>子元素，“derivedContent”属性将包含该元素的“anchor”属性的名称，而不包含其他装饰。
Allowed values:
允许值：
o "default" (default)
o “默认”（默认）
o "title"
o “标题”
o "counter"
o “柜台”
o "none"
o “没有”
Deprecated.
不赞成。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
Identifies the document component being referenced. The value needs to match the value of the "anchor" attribute of an element in the document; otherwise, it is an error.
标识要引用的文档组件。该值需要与文档中元素的“锚定”属性的值匹配；否则，这是一个错误。
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.
本节列出了v2中已弃用的元素。请注意，v3中的某些元素具有v2中已弃用的属性；这里没有列出这些。
Deprecated. Instead, use <tr>, <td>, and <th>.
不赞成。相反，请使用<tr>、<td>和<th>。
This element appears as a child element of <texttable> (Section 3.8).
此元素显示为<texttable>（第3.8节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <spanx> elements (Section 3.7)
o <spanx>元件（第3.7节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Deprecated. The <email> element is a much more useful way to get in touch with authors.
不赞成。<email>元素是与作者联系的更有用的方式。
This element appears as a child element of <address> (Section 2.2).
此元素显示为<address>（第2.2节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
Deprecated. If the goal is to provide a single URI for a reference, use the "target" attribute in <reference> instead.
不赞成。如果目标是为引用提供单个URI，请使用<reference>中的“target”属性。
This element appears as a child element of <reference> (Section 2.40).
此元素显示为<reference>的子元素（第2.40节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
Deprecated.
不赞成。
Deprecated.
不赞成。
Deprecated.
不赞成。
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".
不赞成。相反，对于列表/@样式的“挂起”，使用<dl><ul>用于列表/@样式的“空”或“符号”；以及列表/@样式的“字母”、“数字”、“计数器”或“格式”。
This element appears as a child element of <t> (Section 2.53).
此元素显示为<t>的子元素（第2.53节）。
Content model:
内容模型：
One or more <t> elements (Section 2.53)
一个或多个<t>元件（第2.53节）
Deprecated. The functionality of this attribute has been replaced with <ol>/@start.
不赞成。此属性的功能已替换为<ol>/@start。
Deprecated. Use <dl> instead.
不赞成。改为使用<dl>。
Deprecated.
不赞成。
Deprecated. Instead, use a regular paragraph after the figure or table.
不赞成。相反，在图形或表格后使用常规段落。
This element appears as a child element of <figure> (Section 2.25) and <texttable> (Section 3.8).
此元素显示为<figure>（第2.25节）和<texttable>（第3.8节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <spanx> elements (Section 3.7)
o <spanx>元件（第3.7节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Deprecated. Instead, use a regular paragraph before the figure or table.
不赞成。相反，在图表或表格前使用常规段落。
This element appears as a child element of <figure> (Section 2.25) and <texttable> (Section 3.8).
此元素显示为<figure>（第2.25节）和<texttable>（第3.8节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <bcp14> elements (Section 2.9)
o <bcp14>元素（第2.9节）
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <em> elements (Section 2.22)
o <em>要素（第2.22节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <spanx> elements (Section 3.7)
o <spanx>元件（第3.7节）
o <strong> elements (Section 2.50)
o <strong>要素（第2.50节）
o <sub> elements (Section 2.51)
o <sub>元素（第2.51节）
o <sup> elements (Section 2.52)
o <sup>元素（第2.52节）
o <tt> elements (Section 2.62)
o <tt>要素（第2.62节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
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.53).
此元素显示为<annotation>（第2.3节）、<c>（第3.1节）、<postamble>（第3.5节）、<preamble>（第3.6节）和<t>（第2.53节）的子元素。
Content model: only text content.
内容模型：仅文本内容。
Deprecated. Instead of <spanx style="emph">, use <em>; instead of <spanx style="strong">, use <strong>; instead of <spanx style="verb">, use <tt>.
不赞成。使用<em>代替<spanx style=“emph”>；使用<strong>代替<spanx style=“strong”>；使用<tt>代替<spanx style=“verb”>。
Deprecated.
不赞成。
Allowed values:
允许值：
o "default"
o “默认值”
o "preserve" (default)
o “保留”（默认值）
Deprecated. Use <table> instead.
不赞成。改用<table>。
This element appears as a child element of <aside> (Section 2.6) and <section> (Section 2.46).
此元素显示为<aside>（第2.6节）和<Section>（第2.46节）的子元素。
Content model:
内容模型：
In this order:
按此顺序：
1. One optional <name> element (Section 2.32)
1. 一个可选的<name>元素（第2.32节）
2. One optional <preamble> element (Section 3.6)
2. 一个可选的<preamble>元素（第3.6节）
3. One or more <ttcol> elements (Section 3.9)
3. 一个或多个<ttcol>元件（第3.9节）
4. Optional <c> elements (Section 3.1)
4. 可选<c>元件（第3.1节）
5. One optional <postamble> element (Section 3.5)
5. 一个可选的<postamble>元素（第3.5节）
Deprecated.
不赞成。
Allowed values:
允许值：
o "left"
o “左”
o "center" (default)
o “中心”（默认值）
o "right"
o “对”
Deprecated.
不赞成。
Deprecated.
不赞成。
Deprecated.
不赞成。
Allowed values:
允许值：
o "true"
o “对”
o "false" (default)
o “false”（默认值）
Deprecated.
不赞成。
Deprecated. Instead, use <tr>, <td>, and <th>.
不赞成。相反，请使用<tr>、<td>和<th>。
This element appears as a child element of <texttable> (Section 3.8).
此元素显示为<texttable>（第3.8节）的子元素。
Content model:
内容模型：
In any order:
以任何顺序：
o Text
o 文本
o <cref> elements (Section 2.16)
o <cref>要素（第2.16节）
o <eref> elements (Section 2.24)
o <eref>元件（第2.24节）
o <iref> elements (Section 2.27)
o <iref>要素（第2.27节）
o <xref> elements (Section 2.66)
o <xref>元素（第2.66节）
Deprecated.
不赞成。
Allowed values:
允许值：
o "left" (default)
o “左”（默认）
o "center"
o “中心”
o "right"
o “对”
Deprecated.
不赞成。
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.
不赞成。在这种格式的早期版本中，<vspace>经常用于在列表元素中获得额外的空行；在v3词汇表中，这可以通过在<li>元素中使用多个<t>元素来实现。其他用途没有直接替代品。
This element appears as a child element of <t> (Section 2.53).
此元素显示为<t>的子元素（第2.53节）。
Content model: this element does not have any contents.
内容模型：此元素没有任何内容。
Deprecated.
不赞成。
The discussion of the use of SVG can be found in [RFC7996]. This element is part of the namespace "http://www.w3.org/2000/svg".
有关SVG使用的讨论，请参见[RFC7996]。此元素是命名空间的一部分“http://www.w3.org/2000/svg".
A common problem authors have with <artwork> and <sourcecode> elements 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:
作者对<artwork>和<sourcecode>元素的一个常见问题是，如果artwork中的文本包含“&”或“<”字符或字符串“]]>，XML处理器将返回错误。为了避免这些问题，可以分别使用字符串“&；”和“<；”对“&”和“<”字符进行转义；“]]>”字符串可以表示为“]]>；”。或者，它们可以被CDATA结构包围：“<！[CDATA[]]>”。例如：
Desired output:
allowed-chars = "." | "," | "&" | "<" | ">" | "|"
Desired output:
allowed-chars = "." | "," | "&" | "<" | ">" | "|"
Using escaping:
<sourcecode>
allowed-chars = "." | "," | "&" | "<" | ">" | "|"
</sourcecode>
Using escaping:
<sourcecode>
allowed-chars = "." | "," | "&" | "<" | ">" | "|"
</sourcecode>
Using CDATA:
<sourcecode>
<![CDATA[ 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 escapes can cause other problems, such as difficulty of inclusion from other documents.
使用CDATA并不是万灵药，但它确实有助于防止在使用转义可能导致其他问题的地方使用转义，例如难以从其他文档中包含转义。
This format is based on [XML] and thus does not have any issues representing arbitrary Unicode [UNICODE] characters in text content. The RFC Series Editor may restrict some of the characters that can be used in a particular RFC; the rules for such restrictions are covered in [RFC7997].
此格式基于[XML]，因此在文本内容中表示任意Unicode[Unicode]字符时没有任何问题。RFC系列编辑器可能会限制某些可在特定RFC中使用的字符；[RFC7997]中涵盖了此类限制的规则。
The "name" attribute of 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.
<artwork>元素（第2.5.5节）的“name”属性可用于导出文件名以保存到本地文件系统。未经预处理就信任此类信息是一种已知的安全风险；详见[RFC6266]第4.3节。
The "src" attribute of the <artwork> element can be used to read files from the local system. Processing tools must be careful to not accept dangerous values for the filename, particularly those that contain absolute references outside the current directory.
<artwork>元素的“src”属性可用于从本地系统读取文件。处理工具必须小心，不要接受文件名的危险值，尤其是那些包含当前目录之外的绝对引用的文件名。
The "type" attribute of the <artwork> and <sourcecode> elements is meant to encourage formatters to automatically extract known types of content from an RFC or Internet-Draft. While extraction is probably safe, those tools 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 tool that is reading XML input needs to be suspicious of any content that it intends to post-process.
<artwork>和<sourcecode>元素的“type”属性旨在鼓励格式化程序自动从RFC或Internet草稿中提取已知类型的内容。虽然提取可能是安全的，但这些工具也可能认为它们可以进一步处理提取的内容，例如通过呈现艺术品或执行代码。从安全角度来看，在不首先检查提取内容的情况下这样做显然是一个可怕的想法。更一般地说，读取XML输入的工具需要怀疑它打算后期处理的任何内容。
When there is an external reference to a URL, a processor or renderer should fetch the content into a sandbox and should have only a localized impact on the document processing and rendering.
当存在对URL的外部引用时，处理器或呈现器应将内容提取到沙箱中，并且仅对文档处理和呈现产生本地化影响。
All security considerations related to XML processing are relevant as well (see Section 7 of [RFC3470]).
与XML处理相关的所有安全注意事项也都是相关的（参见[RFC3470]第7节）。
IANA maintains the registry of Internet Media Types [RFC6838] at <https://www.iana.org/assignments/media-types>.
IANA在以下位置维护互联网媒体类型注册表[RFC6838]<https://www.iana.org/assignments/media-types>.
This document updates the specification for the Internet Media Type "application/rfc+xml" from the one in [RFC7749]. The following has been registered with IANA.
本文档更新了[RFC7749]中互联网媒体类型“application/rfc+xml”的规范。以下内容已在IANA注册。
Type name: application
类型名称：应用程序
Subtype name: rfc+xml
子类型名称：rfc+xml
Required parameters: There are no required parameters.
必需参数：没有必需的参数。
Optional parameters: "charset": This parameter has identical semantics to the charset parameter of the "application/xml" Media Type specified in Section 9.1 of [RFC7303].
可选参数：“字符集”：该参数与[RFC7303]第9.1节中指定的“应用程序/xml”媒体类型的字符集参数具有相同的语义。
Encoding considerations: Identical to those of "application/xml" as described in Section 9.1 of [RFC7303].
编码注意事项：与[RFC7303]第9.1节中描述的“应用程序/xml”相同。
Security considerations: As defined in Section 7. In addition, as this Media Type uses the "+xml" convention, it inherits the security considerations described in Section 10 of [RFC7303].
安全注意事项：如第7节所定义。此外，由于此媒体类型使用“+xml”约定，因此它继承了[RFC7303]第10节中描述的安全注意事项。
Interoperability considerations: Different implementations of this format have had interoperability issues. It is not expected that publication of this application will cause those implementations to be fixed.
互操作性注意事项：此格式的不同实现存在互操作性问题。此应用程序的发布不会导致这些实现被修复。
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.
使用此媒体类型的应用程序：将xml2rfc转换为输出表示形式（如纯文本或HTML）的应用程序，以及其他分析工具。
Fragment identifier considerations: The "anchor" attribute is used for assigning document-wide unique identifiers that can be used as shorthand pointers, as described in [XPOINTER].
片段标识符注意事项：“anchor”属性用于分配文档范围的唯一标识符，这些标识符可用作速记指针，如[XPOINTER]中所述。
Additional information:
其他信息：
Deprecated alias names for this type: None
此类型的已弃用别名：无
Magic number(s): As specified for "application/xml" in [RFC7303].
幻数：如[RFC7303]中为“应用程序/xml”指定的。
File extension(s): .xml or .rfcxml when disambiguation from other XML files is needed
文件扩展名：.xml或.rfcxml（当需要从其他xml文件中消除歧义时）
Macintosh file type code(s): TEXT
Macintosh文件类型代码：文本
Person & email address to contact for further information: See the Author's Address section of RFC 7991.
联系人和电子邮件地址了解更多信息：请参阅RFC 7991的作者地址部分。
Intended usage: COMMON
预期用途：普通
Restrictions on usage: None
使用限制：无
Author: See the Author's Address section of RFC 7991.
作者：参见RFC 7991的作者地址部分。
Change controller: RFC Series Editor (rse@rfc-editor.org)
更改控制器：RFC系列编辑器(rse@rfc-（www.editor.org）
IANA has registered "convertedFrom" in the "Link Relation Types" registry [LINKRELATIONS].
IANA已在“链接关系类型”注册表[LINKRELATIONS]中注册了“convertedFrom”。
Relation Name: convertedFrom
关系名称：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".
说明：链接到的文档后来被转换为包含此链接关系的文档。例如，RFC可以链接到成为RFC的Internet草稿；在这种情况下，链接关系将是“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 than "previous" in that this relation is used for converted resources, not those that are part of a sequence of resources.
注：此关系不同于“前置版本”，因为“前置版本”用于版本控制系统中的项目。它也不同于“previous”，因为此关系用于转换的资源，而不是资源序列的一部分。
Application Data: None
应用数据：无
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/bcp14>.
[BCP14]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/bcp14>.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, November 2008, <https://www.w3.org/TR/2008/REC-xml-20081126/>.
[XML]Bray，T.，Paoli，J.，Sperberg McQueen，C.，Maler，E.，和F.Yergeau，“可扩展标记语言（XML）1.0（第五版）”，W3C建议REC-XML-20081126，2008年11月<https://www.w3.org/TR/2008/REC-xml-20081126/>.
Latest version available at <http://www.w3.org/TR/xml>.
最新版本可于<http://www.w3.org/TR/xml>.
[IDGUIDE] Housley, R., "Guidelines to Authors of Internet-Drafts", December 2010, <https://www.ietf.org/id-info/ guidelines.html>.
[IDGUIDE]Housley，R.，“互联网草稿作者指南”，2010年12月<https://www.ietf.org/id-info/ guidelines.html>。
[LINKRELATIONS] IANA, "Link Relations", <https://www.iana.org/assignments/ link-relations/>.
[LINKRELATIONS]IANA，“链接关系”<https://www.iana.org/assignments/ 链接关系/>。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, <http://www.rfc-editor.org/info/rfc2026>.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，DOI 10.17487/RFC2026，1996年10月<http://www.rfc-editor.org/info/rfc2026>.
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, DOI 10.17487/RFC2397, August 1998, <http://www.rfc-editor.org/info/rfc2397>.
[RFC2397]Masinter，L.，“数据”URL方案，RFC 2397，DOI 10.17487/RFC2397，1998年8月<http://www.rfc-editor.org/info/rfc2397>.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, DOI 10.17487/RFC2629, June 1999, <http://www.rfc-editor.org/info/rfc2629>.
[RFC2629]Rose，M.“使用XML编写I-D和RFC”，RFC 2629，DOI 10.17487/RFC2629，1999年6月<http://www.rfc-editor.org/info/rfc2629>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, <http://www.rfc-editor.org/info/rfc3339>.
[RFC3339]Klyne，G.和C.Newman，“互联网上的日期和时间：时间戳”，RFC 3339，DOI 10.17487/RFC3339，2002年7月<http://www.rfc-editor.org/info/rfc3339>.
[RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols", BCP 70, RFC 3470, DOI 10.17487/RFC3470, January 2003, <http://www.rfc-editor.org/info/rfc3470>.
[RFC3470]Hollenbeck，S.，Rose，M.，和L.Masinter，“IETF协议中可扩展标记语言（XML）的使用指南”，BCP 70，RFC 3470，DOI 10.17487/RFC3470，2003年1月<http://www.rfc-editor.org/info/rfc3470>.
[RFC3667] Bradner, S., "IETF Rights in Contributions", RFC 3667, DOI 10.17487/RFC3667, February 2004, <http://www.rfc-editor.org/info/rfc3667>.
[RFC3667]Bradner，S.，“IETF在贡献中的权利”，RFC 3667，DOI 10.17487/RFC3667，2004年2月<http://www.rfc-editor.org/info/rfc3667>.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, DOI 10.17487/RFC3966, December 2004, <http://www.rfc-editor.org/info/rfc3966>.
[RFC3966]Schulzrinne，H.，“电话号码的电话URI”，RFC 3966，DOI 10.17487/RFC3966，2004年12月<http://www.rfc-editor.org/info/rfc3966>.
[RFC3978] Bradner, S., Ed., "IETF Rights in Contributions", RFC 3978, DOI 10.17487/RFC3978, March 2005, <http://www.rfc-editor.org/info/rfc3978>.
[RFC3978]Bradner，S.，Ed.，“IETF在贡献中的权利”，RFC 3978，DOI 10.17487/RFC3978，2005年3月<http://www.rfc-editor.org/info/rfc3978>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <http://www.rfc-editor.org/info/rfc3986>.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，DOI 10.17487/RFC3986，2005年1月<http://www.rfc-editor.org/info/rfc3986>.
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008, <http://www.rfc-editor.org/info/rfc5234>.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，DOI 10.17487/RFC5234，2008年1月<http://www.rfc-editor.org/info/rfc5234>.
[RFC5378] Bradner, S., Ed., and J. Contreras, Ed., "Rights Contributors Provide to the IETF Trust", BCP 78, RFC 5378, DOI 10.17487/RFC5378, November 2008, <http://www.rfc-editor.org/info/rfc5378>.
[RFC5378]Bradner，S.，Ed.，和J.Contreras，Ed.，“向IETF信托提供的权利贡献者”，BCP 78，RFC 5378，DOI 10.17487/RFC5378，2008年11月<http://www.rfc-editor.org/info/rfc5378>.
[RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010, <http://www.rfc-editor.org/info/rfc6068>.
[RFC6068]Duerst，M.，Masinter，L.，和J.Zawinski，“mailto”URI方案”，RFC 6068，DOI 10.17487/RFC6068，2010年10月<http://www.rfc-editor.org/info/rfc6068>.
[RFC6266] Reschke, J., "Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)", RFC 6266, DOI 10.17487/RFC6266, June 2011, <http://www.rfc-editor.org/info/rfc6266>.
[RFC6266]Reschke，J.，“超文本传输协议（HTTP）中内容处置头字段的使用”，RFC 6266，DOI 10.17487/RFC6266，2011年6月<http://www.rfc-editor.org/info/rfc6266>.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, DOI 10.17487/RFC6838, January 2013, <http://www.rfc-editor.org/info/rfc6838>.
[RFC6838]Freed，N.，Klensin，J.和T.Hansen，“介质类型规范和注册程序”，BCP 13，RFC 6838，DOI 10.17487/RFC6838，2013年1月<http://www.rfc-editor.org/info/rfc6838>.
[RFC6949] Flanagan, H. and N. Brownlee, "RFC Series Format Requirements and Future Development", RFC 6949, DOI 10.17487/RFC6949, May 2013, <http://www.rfc-editor.org/info/rfc6949>.
[RFC6949]Flanagan，H.和N.Brownlee，“RFC系列格式要求和未来发展”，RFC 6949，DOI 10.17487/RFC6949，2013年5月<http://www.rfc-editor.org/info/rfc6949>.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, DOI 10.17487/RFC7303, July 2014, <http://www.rfc-editor.org/info/rfc7303>.
[RFC7303]Thompson，H.和C.Lilley，“XML媒体类型”，RFC 7303，DOI 10.17487/RFC7303，2014年7月<http://www.rfc-editor.org/info/rfc7303>.
[RFC7322] Flanagan, H. and S. Ginoza, "RFC Style Guide", RFC 7322, DOI 10.17487/RFC7322, September 2014, <http://www.rfc-editor.org/info/rfc7322>.
[RFC7322]Flanagan，H.和S.Ginoza，“RFC风格指南”，RFC 7322，DOI 10.17487/RFC7322，2014年9月<http://www.rfc-editor.org/info/rfc7322>.
[RFC7669] Levine, J., "Assigning Digital Object Identifiers to RFCs", RFC 7669, DOI 10.17487/RFC7669, October 2015, <http://www.rfc-editor.org/info/rfc7669>.
[RFC7669]Levine，J.，“将数字对象标识符分配给RFC”，RFC 7669，DOI 10.17487/RFC7669，2015年10月<http://www.rfc-editor.org/info/rfc7669>.
[RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary", RFC 7749, DOI 10.17487/RFC7749, February 2016, <http://www.rfc-editor.org/info/rfc7749>.
[RFC7749]Reschke，J.“xml2rfc”版本2词汇表”，RFC 7749，DOI 10.17487/RFC7749，2016年2月<http://www.rfc-editor.org/info/rfc7749>.
[RFC7841] Halpern, J., Ed., Daigle, L., Ed., and O. Kolkman, Ed., "RFC Streams, Headers, and Boilerplates", RFC 7841, DOI 10.17487/RFC7841, May 2016, <http://www.rfc-editor.org/info/rfc7841>.
[RFC7841]Halpern，J.，Ed.，Daigle，L.，Ed.，和O.Kolkman，Ed.，“RFC流，标题和样板”，RFC 7841，DOI 10.17487/RFC78412016年5月<http://www.rfc-editor.org/info/rfc7841>.
[RFC7996] Brownlee, N., "SVG Drawings for RFCs: SVG 1.2 RFC", RFC 7996, DOI 10.17487/RFC7996, December 2016, <http://www.rfc-editor.org/info/rfc7996>.
[RFC7996]Brownlee，N.，“RFC的SVG图纸：SVG 1.2 RFC”，RFC 7996，DOI 10.17487/RFC7996，2016年12月<http://www.rfc-editor.org/info/rfc7996>.
[RFC7997] Flanagan, H., Ed., "The Use of Non-ASCII Characters in RFCs", RFC 7997, DOI 10.17487/RFC7997, December 2016, <http://www.rfc-editor.org/info/rfc7997>.
[RFC7997]Flanagan，H.，Ed.，“RFC中非ASCII字符的使用”，RFC 7997，DOI 10.17487/RFC7997，2016年12月<http://www.rfc-editor.org/info/rfc7997>.
[RFC7998] Hoffman, P. and J. Hildebrand, ""xml2rfc" Version 3 Preparation Tool Description", RFC 7998, DOI 10.17487/RFC7998, December 2016, <http://www.rfc-editor.org/info/rfc7998>.
[RFC7998]Hoffman，P.和J.Hildebrand，“xml2rfc”第3版准备工具说明”，RFC 7998，DOI 10.17487/RFC7998，2016年12月<http://www.rfc-editor.org/info/rfc7998>.
[RNC] Clark, J., "RELAX NG Compact Syntax", The Organization for the Advancement of Structured Information Standards (OASIS), November 2002, <https://www.oasis-open.org/committees/ relax-ng/compact-20021121.html>.
[RNC]Clark，J.，“RELAXNG紧凑语法”，结构化信息标准促进组织（OASIS），2002年11月<https://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.
[RNG]ISO/IEC，“信息技术-文档模式定义语言（DSDL）-第2部分：基于规则语法的验证-RELAXNG（第二版）”，ISO/IEC 19757-2:2008（E），2008年12月。
A useful source of RNG-related information is <http://relaxng.org/>.
RNG相关信息的一个有用来源是<http://relaxng.org/>.
[TLP1.0] IETF Trust, "Legal Provisions Relating to IETF Documents", November 2008, <http://trustee.ietf.org/license-info/IETF-TLP-1.htm>.
[TLP1.0]IETF信托，“与IETF文件相关的法律规定”，2008年11月<http://trustee.ietf.org/license-info/IETF-TLP-1.htm>.
[TLP2.0] IETF Trust, "Legal Provisions Relating to IETF Documents", February 2009, <http://trustee.ietf.org/license-info/IETF-TLP-2.htm>.
[TLP2.0]IETF信托，“与IETF文件相关的法律规定”，2009年2月<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>.
[TLP3.0]IETF信托，“与IETF文件相关的法律规定”，2009年9月<http://trustee.ietf.org/license-info/IETF-TLP-3.htm>.
[TLP4.0] IETF Trust, "Legal Provisions Relating to IETF Documents", December 2009, <http://trustee.ietf.org/license-info/IETF-TLP-4.htm>.
[TLP4.0]IETF信托，“与IETF文件相关的法律规定”，2009年12月<http://trustee.ietf.org/license-info/IETF-TLP-4.htm>.
[TLP5.0] IETF Trust, "Legal Provisions Relating to IETF Documents", March 2015, <http://trustee.ietf.org/license-info/IETF-TLP-5.htm>.
[TLP5.0]IETF信托，“与IETF文件相关的法律规定”，2015年3月<http://trustee.ietf.org/license-info/IETF-TLP-5.htm>.
[UAX24] The Unicode Consortium, "UAX #24: Unicode Script Property", <http://www.unicode.org/reports/tr24/>.
[UAX24]Unicode联盟，“UAX#24:Unicode脚本属性”<http://www.unicode.org/reports/tr24/>.
[UNICODE] The Unicode Consortium, "The Unicode Standard", <http://www.unicode.org/versions/latest/>.
[UNICODE]UNICODE联盟，“UNICODE标准”<http://www.unicode.org/versions/latest/>.
[USASCII] American National Standards Institute, "Coded Character Set -- 7-bit American Standard Code for Information Interchange", ANSI X3.4, 1986.
[USASCII]美国国家标准协会，“编码字符集——信息交换用7位美国标准代码”，ANSI X3.41986。
[XInclude] Marsh, J., Orchard, D., and D. Veillard, "XML Inclusions (XInclude) Version 1.0 (Second Edition)", W3C Recommendation REC-xinclude-20061115, November 2006, <https://www.w3.org/TR/2006/REC-xinclude-20061115/>.
[XInclude]Marsh，J.，Orchard，D.和D.Veillard，“XML包含（XInclude）1.0版（第二版）”，W3C建议REC-XInclude-200611152006年11月<https://www.w3.org/TR/2006/REC-xinclude-20061115/>.
Latest version available at <http://www.w3.org/TR/xinclude/>.
最新版本可于<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/>.
[XPOINTER]Grosso，P.，Maler，E.，Marsh，J.，和N.Walsh，“XPOINTER框架”，W3C建议REC-xptr-Framework-200303252003年3月<http://www.w3.org/TR/2003/REC-xptr-framework-20030325/>.
Latest version available at <http://www.w3.org/TR/xptr-framework/>.
最新版本可于<http://www.w3.org/TR/xptr-framework/>.
Appendix A. Front-Page ("Boilerplate") Generation
附录A.首页（“样板文件”）生成
The values listed here will be defined by the RFC Series Editor. Those listed here are believed to be the current values in use.
此处列出的值将由RFC系列编辑器定义。此处列出的值被认为是当前使用的值。
This attribute value can take a long list of values, each of which describes an IPR policy for the document (Section 2.45.5). The values are not the result of a grand design, but they remain simply for historic reasons. Of these values, only a few are currently in use; all others are supported by various tools for backwards compatibility with old source files.
该属性值可以包含一长串值，每个值都描述了文档的IPR策略（第2.45.5节）。这些价值观并不是宏伟设计的结果，但它们只是出于历史原因而存在。在这些值中，只有少数值目前正在使用；所有其他工具都支持与旧源文件向后兼容的各种工具。
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.
注：样板文件的某些变体是根据文件日期选择的；因此，在提交当天归档Internet草稿的XML源时，指定<date>元素的“年”、“月”和“日”属性非常重要。
_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>.
_免责声明：这仅提供实现信息。如果您需要法律咨询，请联系律师。\有关更多信息，请参阅<http://trustee.ietf.org/docs/ IETF版权常见问题解答.pdf>。
For the current "Copyright Notice" text, the submissionType attribute of the <rfc> element (Section 2.45.12) 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.
对于当前的“版权声明”文本，<rfc>元素的submissionType属性（第2.45.12节）决定是否插入关于“代码组件”的语句（这是值“IETF”的情况，它是默认值）。其他值（如“独立”）会抑制文本的这一部分。
The name for these values refers to version 2.0 of the IETF Trust's "Legal Provisions Relating to IETF Documents", sometimes simply called the "TLP", which went into effect on February 15, 2009 [TLP2.0]. Updates to the 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.
这些值的名称是指IETF信托的“与IETF文件有关的法律规定”2.0版，有时简称为“TLP”，于2009年2月15日生效[TLP2.0]。2009年9月12日[TLP3.0]和2009年12月28日[TLP4.0]发布了对该文档的更新，修改了代码组件的许可证（请参阅<http://trustee.ietf.org/ 许可证信息/>了解更多信息）。实际文本位于这些文件的第6节（“IETF文件中包含的文本”）。
The prep tool automatically produces 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 |
+----------+--------------------------------+
+----------+--------------------------------+
| TLP | starting with publication date |
+----------+--------------------------------+
| [TLP3.0] | 2009-11-01 |
| [TLP4.0] | 2010-04-01 |
+----------+--------------------------------+
The TLP was again updated in March 2015 [TLP5.0], but the changes made in that version do not affect the boilerplate text.
TLP于2015年3月再次更新[TLP5.0]，但该版本中所做的更改不会影响样板文本。
This value should be used 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.
除非更具体的“*trust200902”值之一更适合，否则应使用此值。它产生TLP第6.a和6.b节中的文本。
This produces the additional text from Section 6.c.i of the TLP:
这将产生TLP第6.c.i节的附加文本：
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.
不得修改本文件，也不得创建其衍生作品，除非将其格式化为RFC出版或将其翻译为英语以外的其他语言。
Note: this clause is incompatible with RFCs that are published on the Standards Track.
注：本条款与标准轨道上发布的RFC不兼容。
This produces the additional text from Section 6.c.ii of the TLP:
这将产生TLP第6.c.ii节中的附加文本：
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.
注：本条款与RFC不兼容。
This produces the additional text from Section 6.c.iii of the TLP, frequently called the "pre-5378 escape clause" referring to changes introduced in [RFC5378]:
这产生了TLP第6.c.iii节的附加文本，通常称为“5378之前的免责条款”，涉及[RFC5378]中引入的变更：
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.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
See Section 4 of <http://trustee.ietf.org/docs/ IETF-Copyright-FAQ.pdf> for further information about when to use this value.
见本报告第4节<http://trustee.ietf.org/docs/ IETF Copyright FAQ.pdf>了解有关何时使用此值的更多信息。
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".
注：本文本出现在“版权声明”下，除非该文件在2009年11月之前发布，在这种情况下，它出现在“本备忘录的状态”下。
The attribute values "trust200811", "noModificationTrust200811", and "noDerivativesTrust200811" are similar to their "trust200902" counterparts, except that they use text specified in [TLP1.0].
属性值“trust200811”、“noModificationTrust200811”和“noDerivativesTrust200811”与其对应的“trust200902”类似，只是它们使用了[TLP1.0]中指定的文本。
The attribute values "full3978", "noModification3978", and "noDerivatives3978" are similar to their counterparts above, except that they use text specified in [RFC3978].
属性值“full3978”、“noModification3978”和“noDerivatives3978”与上面的对应项类似，只是它们使用了[RFC3978]中指定的文本。
The attribute values "full3667", "noModification3667", and "noDerivatives3667" are similar to their counterparts above, except that they use text specified in [RFC3667].
属性值“full3667”、“noModification3667”和“noDerivatives3667”与其上面的对应项类似，只是它们使用了[RFC3667]中指定的文本。
The attribute values "full2026" and "noDerivativeWorks2026" are similar to their counterparts above, except that they use text specified in Section 10 of [RFC2026].
属性值“full2026”和“NODERIVATIVEWORK2026”与上述对应值类似，只是它们使用了[RFC2026]第10节中指定的文本。
The special value "none" was also used back then; it denied the IETF any rights beyond publication as an Internet-Draft.
当时还使用了特殊值“无”；它否认IETF除了作为互联网草案出版之外的任何权利。
The RFC Editor publishes documents from different "document streams", of which the "IETF stream" is the most prominent. Other streams are the "Independent Submissions stream" (used for things such as discussion of Internet-related technologies that are not part of the IETF agenda), the "IAB stream" (Internet Architecture Board), and the "IRTF stream" (Internet Research Task Force).
RFC编辑器发布来自不同“文档流”的文档，其中“IETF流”最为突出。其他流包括“独立提交流”（用于讨论不属于IETF议程的互联网相关技术）、“IAB流”（互联网架构委员会）和“IRTF流”（互联网研究任务组）。
The values for the attribute are "IETF" (the default value), "independent", "IAB", and "IRTF".
该属性的值为“IETF”（默认值）、“independent”、“IAB”和“IRTF”。
Historically, this attribute did not affect the final appearance of RFCs, except for subtle differences in copyright notices. Nowadays (as of [RFC7841]), the stream name appears in the first line of the front page, and it also affects the text in the "Status of This Memo" section.
从历史上看，除了版权声明中的细微差异外，该属性不会影响RFC的最终外观。现在（从[RFC7841]开始），流名称出现在首页的第一行，它也影响“此备忘录的状态”部分的文本。
For current documents, setting the "submissionType" attribute will have the following effect:
对于当前文档，设置“submissionType”属性将产生以下效果：
o For RFCs, the stream name appears in the upper left corner of the first page (in Internet-Drafts, this is either "Network Working Group" or the value of the <workgroup> element).
o 对于RFC，流名称显示在第一页的左上角（在Internet草稿中，这是“网络工作组”或<workgroup>元素的值）。
o For RFCs, it affects the whole "Status of This Memo" section (see Section 3.2 of [RFC7841]).
o 对于RFC，它影响整个“本备忘录的状态”部分（见[RFC7841]第3.2节）。
o For all RFCs and Internet-Drafts, it determines whether the "Copyright Notice" section mentions the Copyright on Code Components (see Section 6 of the TLP ("Text to Be Included in IETF Documents")).
o 对于所有RFC和互联网草案，它确定“版权声明”部分是否提及代码组件的版权（见TLP第6节（“将包含在IETF文件中的文本”））。
For some of the publication streams (see Appendix A.2), the "Status of This Memo" section depends on whether there was a consensus to publish (again, see Section 3.4 of [RFC7841]).
对于一些发布流（见附录A.2），“本备忘录的状态”部分取决于是否达成了发布共识（同样，见[RFC7841]第3.4节）。
The consensus attribute can be used to supply this information. The acceptable values are "true" (the default) and "false"; "yes" and "no" from v2 are deprecated.
“共识”属性可用于提供此信息。可接受的值为“真”（默认值）和“假”；v2中的“是”和“否”不推荐使用。
The effect of this value for the various streams is:
该值对各种流的影响为：
o "independent": none.
o “独立”：无。
o "IAB": mention that there was an IAB consensus.
o “IAB”：提及有IAB共识。
o "IETF": mention that there was an IETF consensus.
o “IETF”：提及IETF达成共识。
o "IRTF": mention that there was a research group consensus (where the name of the research group is extracted from the <workgroup> element).
o “IRTF”：提到有一个研究小组共识（其中研究小组的名称取自<workgroup>元素）。
This section describes topics that are specific to v3 processing tools. Note that there is some discussion of tools in the main body of the document as well. For example, some elements have descriptions of how a processing tool might create output from the element.
本节介绍特定于v3处理工具的主题。注意，在文档的主体部分也有一些关于工具的讨论。例如，某些元素具有处理工具如何从元素创建输出的描述。
The expected design of the tools that will be used with v3 documents includes:
将与v3文档一起使用的工具的预期设计包括：
o A "prep tool" that takes a v3 document, makes many checks, adds and changes many attribute values, and creates a file that is a "prepared document". The prepared document is a valid v3 document. The prep tool is described in [RFC7998].
o 一个“准备工具”，它接受一个v3文档，进行许多检查，添加和更改许多属性值，并创建一个“准备好的文档”文件。准备好的文档是有效的v3文档。[RFC7998]中描述了准备工具。
The prep tool is expected to have many modes:
准备工具预计有多种模式：
* RFC mode -- The mode 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. The restrictions on the canonical XML for RFCs, as well as how the non-canonical formats will look, are described at <https://www.rfc-editor.org/rse/wiki/ doku.php?id=design:format-and-content-rfcs>.
* RFC模式——RFC编辑器用于处理来自其中一个RFC流的输入以及处理RFC编辑过程中生成的XML的模式。关于RFC规范XML的限制，以及非规范格式的外观，请参见<https://www.rfc-editor.org/rse/wiki/ php？id=design:format and content rfcs>。
* Draft mode -- The mode used by the Internet-Draft submission tool. The restrictions for the XML from this mode will be described later.
* 草稿模式--Internet草稿提交工具使用的模式。稍后将描述此模式对XML的限制。
* Diagnostic mode -- A mode that can be used by document authors to look for errors or warnings before they submit their documents for publication.
* 诊断模式--文档作者可以使用该模式在提交文档以供发布之前查找错误或警告。
* Consolidation mode -- Produces output where no external resources are required to render the file output. This includes expanding the XInclude entities and DTD entities in place, and changing all elements that have "src" attributes with external links into either "data:" URI or content for the element, as specified in [RFC7998].
* 整合模式--生成不需要外部资源即可呈现文件输出的输出。这包括适当地扩展XInclude实体和DTD实体，并将具有“src”属性和外部链接的所有元素更改为“data:”URI或元素的内容，如[RFC7998]中所述。
o Formatting tools that will create HTML, PDF, plain text, and possibly other output formats. These formatters will be created by the IETF, but others can create such tools as well. The IETF tools are expected to take prepared documents as input.
o 用于创建HTML、PDF、纯文本以及可能的其他输出格式的格式化工具。这些格式化程序将由IETF创建，但其他人也可以创建此类工具。IETF工具应将准备好的文件作为输入。
There may also be processing tools that are meant to run on the computers of authors. These tools 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.
也可能有处理工具是为了在作者的计算机上运行。这些工具可用于生成非规范表示的临时版本，以便作者可以查看其XML以后的呈现方式，以不同于RFC编辑器支持的表示方式创建文档，并可能创建不属于Internet草稿或RFC的文档，以及将包含外部信息的XML转换为包含外部信息的XML。
The prep tool is expected to have clear error reporting, giving more context than just a line number. For example, the error messages should differentiate between errors in XML and those from the v3 format.
prep工具应该有清晰的错误报告，提供比行号更多的上下文。例如，错误消息应该区分XML中的错误和v3格式中的错误。
In v2, the grammar was specified as a DTD. In v3, the grammar is specified only as RELAX Next Generation (RNG). This means that tools need to work from the RNG, not from a DTD. Some of the features of the v3 grammar cannot be specified as a DTD.
在v2中，语法被指定为DTD。在v3中，语法仅指定为RELAX Next Generation（RNG）。这意味着工具需要从RNG工作，而不是从DTD工作。v3语法的某些功能不能指定为DTD。
All tools for the v3 format 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.
v3格式的所有工具都应支持XInclude[XInclude]。XInclude指定了一种处理模型和语法，用于通用地包含Internet上或用户计算机本地的信息。
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
<rfc> element; that is, you need to specify
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
<rfc> element; that is, you need to specify
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xi="http://www.w3.org/2001/XInclude"
as one of the attributes in the <rfc> element.
作为<rfc>元素中的属性之一。
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 this is expected to be from the RFC Editor. For example, if a document has three normative references, all RFCs, the document might contain:
使用<xi:include>最常用的方法是拉入已经形成为XML的引用。目前，这可以从xml2rfc.tools.ietf.org完成，但稍后将从RFC编辑器完成。例如，如果一份文件有三个规范性参考文件，即所有RFC，则该文件可能包含：
<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>
<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 can be included with <xi:include>. An example of pulling something from the local disk would be:
<xi:include>可以在任何可以使用XML元素的地方使用（但不能在使用自由文本的地方使用）。例如，如果三个Internet草稿都逐字包含特定段落或章节，则该文本可以保存在文件中或web上的某个位置，并且可以包含在<xi:include>中。从本地磁盘提取内容的示例如下：
<x:include href="file://home/chris/ietf/drafts/commontext.xml"/>
<x:include href="file://home/chris/ietf/drafts/commontext.xml"/>
In general, XInclude should be used instead of ENTITY references and XML Processing Instructions (PIs) that allow external inclusions.
通常，应该使用XInclude，而不是允许外部包含的实体引用和XML处理指令（PI）。
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 parts 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.
撰写和阅读互联网草稿和RFC的人通常希望参考这些文档中的特定位置。对于RFC作者来说，通常希望引用他们文档的另一部分，如“请参阅本文档的第3.2节”。另一方面，读者希望引用他们没有编写的文档部分，如“请参阅RFC 6949的第3.2节”。本文档中的XML词汇表试图支持这两类人。
Authors can leave anchors in a document that can later be used for references with the "anchor" attribute. Anchors can be included in the numerous elements. The author can then refer to that anchor in the "target" attribute of the <xref> element.
作者可以在文档中留下锚定，稍后可以使用“锚定”属性用于引用。锚可包含在众多元素中。然后，作者可以在<xref>元素的“target”属性中引用该锚定。
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 a "pn" attribute.
读者可以通过该属性引用具有“锚定”属性的任何元素。但是，请注意，大多数情况下，元素都没有锚。在常见情况下，读者希望引用一个没有“anchor”属性的元素，但该元素有一个“pn”属性。
Processing tools add the "pn" attribute to many elements during processing. This attribute and its value are automatically generated by the tool if the attribute is not there; if the attribute is already there, the tool may replace the value.
处理工具在处理过程中向许多元素添加“pn”属性。如果该属性不存在，则工具会自动生成该属性及其值；如果该属性已经存在，则该工具可以替换该值。
In the HTML representation of this XML vocabulary, both anchors and "pn" attributes will be used in the "id" attributes of elements. Thus, there can be no overlap between the names entered in "anchor" attributes, in "slugifiedName" attributes, and those that are generated for the "pn" attributes. Also, there are some values for the "anchor" values that are reserved for sections, and those sections can only have those anchor values.
在这个XML词汇表的HTML表示中，元素的“id”属性中将使用锚和“pn”属性。因此，在“锚定”属性、“slugifiedName”属性中输入的名称与为“pn”属性生成的名称之间不能有重叠。此外，还有一些为节保留的“锚定”值，这些节只能具有这些锚定值。
The following rules prevent this overlap:
以下规则防止这种重叠：
o "pn" for regular sections always has the format "s-nnn", where "nnn" is the section number, or the appendix identifier (which starts with a letter). For example, this would be "s-2.1.3" for Section 2.1.3 and "s-a" for Appendix A. For the <abstract> element, it is always "s-abstract". For the <note> element, it is always "s-note-nnn", where "nnn" is a sequential value. For sections in the <boilerplate> element, it is always "s-boilerplate-nnn", where "nnn" is a sequential value.
o 常规章节的“pn”格式始终为“s-nnn”，其中“nnn”是章节编号或附录标识符（以字母开头）。例如，第2.1.3节为“s-2.1.3”，附录a为“s-a”。对于<abstract>元素，始终为“s-abstract”。对于<note>元素，它总是“s-note-nnn”，其中“nnn”是顺序值。对于<boilerplate>元素中的部分，它始终是“s-boilerplate-nnn”，其中“nnn”是顺序值。
o "pn" for <references> elements has the format "s-nnn". It is important to note that "nnn" is a number, not letters, even though the <references> appear in the back. It is the number that is one higher than the highest top-level section number in <middle>. If there are two or more <references>, "nnn" will include a dot as if the <references> are a subsection of a section that is numbered one higher than the highest top-level section number in <middle>.
o <references>元素的“pn”格式为“s-nnn”。重要的是要注意，“nnn”是一个数字，而不是字母，即使<references>出现在后面。它比<middle>中最高的顶级节数高一个。如果有两个或两个以上的<references>，“nnn”将包含一个点，就好像<references>是节的一个子节，其编号比<middle>中最高的顶级节编号高一个。
o "pn" for <figure> elements always has the format "f-nnn", where "nnn" is the figure number. For example, this would be "f-5" for Figure 5.
o <figure>元素的“pn”格式始终为“f-nnn”，其中“nnn”是图号。例如，对于图5，这将是“f-5”。
o "pn" for <iref> elements always has the format "i-ttt-nnn", where "ttt" is the slugified item (plus a hyphen and the slugified subitem if there is a subitem), and "nnn" is the instance of that item/subitem pair. For example, this would be "i-foo-1" for "<iref item='foo'>" and "i-foo-bar-1" for "<iref item='foo' subitem='bar'>".
o <iref>元素的“pn”始终采用“i-ttt-nnn”格式，其中“ttt”是slagified项（如果有子项，则加上连字符和slagified子项），而“nnn”是该项/子项对的实例。例如，这将是“<iref item='foo'>”的“i-foo-1”和“<iref item='foo'subitem='bar'>”的“i-foo-bar-1”。
o "pn" for <table> elements always has the format "t-nnn", where "nnn" is the table number. For example, this would be "t-5" for Table 5.
o <table>元素的“pn”格式始终为“t-nnn”，其中“nnn”是表号。例如，对于表5，这将是“t-5”。
o "pn" for all elements not listed above 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 以上未列出的所有元件的“pn”始终采用“p-nnn-mmm”格式，其中“nnn”是截面编号，“mmm”是截面中的相对位置。例如，第2.1.3节中的第七个零件号为“p-2.1.3-7”。
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 later time.
o “slugifiedName”的格式始终为“n-ttt”，其中“ttt”是Slugified后的名称文本。例如，这将是“协议概述”名称的“n-protocol-overview”。段塞化中的实际转换将在以后指定。
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 processing tool will reject the document.
o 锚固件不得与上述任何部件重叠。确保这一点的最简单方法是不要选择以单个字母开头，后跟连字符的锚名称。如果锚定与上述名称类型之一重叠，则处理工具将拒绝该文档。
Many elements in the v3 vocabulary have new attributes whose role is to hold values generated by the prep tool. These attributes can exist in documents that are input to the prep tool; however, any of these attributes might be added, removed, or changed by the prep tool. Thus, it is explicitly unsafe for a document author to include these attributes and expect that their values will survive processing by the prep tool.
v3词汇表中的许多元素都有新属性，其作用是保存prep工具生成的值。这些属性可以存在于输入到准备工具的文档中；但是，这些属性中的任何一个都可以通过prep工具添加、删除或更改。因此，对于文档作者来说，包含这些属性并期望它们的值在prep工具处理后仍然有效，这显然是不安全的。
The attributes that are controlled by the prep tool are:
准备工具控制的属性包括：
o The "pn" attribute in any element -- The number for this item within the section. The numbering is shared with other elements of a section. The "pn" attribute is added to many block-level elements inside sections.
o 任何元素中的“pn”属性——节中此项的编号。编号与节的其他元素共享。“pn”属性被添加到节内的许多块级元素中。
o <artwork> originalSrc -- This attribute is filled with the original value of the "src" attribute if that attribute is removed by the prep tool.
o <artwork>originalSrc——如果“src”属性被prep工具删除，则该属性将用该属性的原始值填充。
o <figure> originalSrc -- This attribute is filled with the original value of the "src" attribute if that attribute is removed by the prep tool.
o <figure>originalSrc——如果prep工具删除了“src”属性，则该属性将用该属性的原始值填充。
o <name> "slugifiedName" attribute -- This attribute is filled 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.
o <name>“slugifiedName”属性——该属性由元素中文本的“slugified”版本填充。此属性可以在同时具有名称和数字的元素的输出格式中使用。
o <relref> "derivedLink" attribute -- This attribute is filled with the link that is derived from combining the URI from the reference and the relative part that is either a copy of the "relative" attribute or a section number derived from the "section" attribute.
o <relref>“derivedLink”属性——此属性由链接填充，该链接由引用的URI和相对部分组合而成，相对部分是“相对”属性的副本或从“节”属性派生的节号。
o <rfc> "expiresDate" attribute -- This attribute is filled with the date that an Internet-Draft expires. The date is in the format yyyy-mm-dd.
o <rfc>“expiresDate”属性--此属性用Internet草稿的过期日期填充。日期的格式为yyyy-mm-dd。
o <rfc> "mode" attribute -- This attribute is filled with a string that indicates what mode the prep tool was in when it processed the XML, such as whether it was processing a file to become an Internet-Draft or an RFC.
o <rfc>“mode”属性——此属性由一个字符串填充，该字符串指示prep工具在处理XML时所处的模式，例如，它是在处理文件以成为Internet草稿还是rfc。
o <rfc> "scripts" attribute -- This attribute is filled with a list of scripts needed to render this document. The list is comma-separated, with no spaces allowed. The order is unimportant. The names come from [UAX24]. For example, if the document has Chinese characters in it, the value might be "Common,Latin,Han".
o <rfc>“脚本”属性--此属性包含呈现此文档所需的脚本列表。列表以逗号分隔，不允许有空格。顺序不重要。这些名称来自[UAX24]。例如，如果文档中包含汉字，则值可能为“Common、Latin、Han”。
o <sourcecode> "originalSrc" attribute -- This attribute is filled with the original value of the "src" attribute if that attribute is removed by the prep tool.
o <sourcecode>“originalSrc”属性——如果“src”属性被prep工具删除，则该属性将由该属性的原始值填充。
o <xref> "derivedContent" attribute -- This attribute is filled in if there is no content in the <xref> element. The value for this attribute is based on the value in the "displayFormat" attribute. Examples of how this value is filled can be found in Section 2.66.1.
o <xref>“derivedContent”属性——如果<xref>元素中没有内容，则填写此属性。此属性的值基于“displayFormat”属性中的值。第2.66.1节给出了如何填写该值的示例。
In addition, note that the contents of the <boilerplate> element are controlled by the prep tool.
此外，请注意，<boilerplate>元素的内容由prep工具控制。
The following is the RELAX NG schema for the v3 format.
以下是v3格式的RELAXNG模式。
namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
# xml2rfc Version 3 grammar
#xml2rfc版本3语法
rfc =
element rfc {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute number { text }?,
[ a:defaultValue = "" ] attribute obsoletes { text }?,
[ a:defaultValue = "" ] attribute updates { text }?,
attribute category { text }?,
attribute mode { text }?,
[ a:defaultValue = "false" ]
attribute consensus { "no" | "yes" | "false" | "true" }?,
attribute seriesNo { text }?,
attribute ipr { text }?,
attribute iprExtract { xsd:IDREF }?,
[ a:defaultValue = "IETF" ]
attribute submissionType {
"IETF" | "IAB" | "IRTF" | "independent"
}?,
attribute docName { text }?,
[ a:defaultValue = "false" ]
attribute sortRefs { "true" | "false" }?,
[ a:defaultValue = "true" ]
attribute symRefs { "true" | "false" }?,
[ a:defaultValue = "true" ]
attribute tocInclude { "true" | "false" }?,
[ a:defaultValue = "3" ] attribute tocDepth { text }?,
attribute prepTime { text }?,
[ a:defaultValue = "true" ]
attribute indexInclude { "true" | "false" }?,
attribute version { text }?,
[ a:defaultValue = "Common,Latin" ] attribute scripts { text }?,
attribute expiresDate { text }?,
link*,
front,
middle,
back?
}
rfc =
element rfc {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute number { text }?,
[ a:defaultValue = "" ] attribute obsoletes { text }?,
[ a:defaultValue = "" ] attribute updates { text }?,
attribute category { text }?,
attribute mode { text }?,
[ a:defaultValue = "false" ]
attribute consensus { "no" | "yes" | "false" | "true" }?,
attribute seriesNo { text }?,
attribute ipr { text }?,
attribute iprExtract { xsd:IDREF }?,
[ a:defaultValue = "IETF" ]
attribute submissionType {
"IETF" | "IAB" | "IRTF" | "independent"
}?,
attribute docName { text }?,
[ a:defaultValue = "false" ]
attribute sortRefs { "true" | "false" }?,
[ a:defaultValue = "true" ]
attribute symRefs { "true" | "false" }?,
[ a:defaultValue = "true" ]
attribute tocInclude { "true" | "false" }?,
[ a:defaultValue = "3" ] attribute tocDepth { text }?,
attribute prepTime { text }?,
[ a:defaultValue = "true" ]
attribute indexInclude { "true" | "false" }?,
attribute version { text }?,
[ a:defaultValue = "Common,Latin" ] attribute scripts { text }?,
attribute expiresDate { text }?,
link*,
front,
middle,
back?
}
link =
element link {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute href { text },
attribute rel { text }?
}
link =
element link {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute href { text },
attribute rel { text }?
}
front =
element front {
attribute xml:base { text }?,
attribute xml:lang { text }?,
title,
seriesInfo*,
author+,
date?,
area*,
workgroup*,
keyword*,
abstract?,
note*,
boilerplate?
}
front =
element front {
attribute xml:base { text }?,
attribute xml:lang { text }?,
title,
seriesInfo*,
author+,
date?,
area*,
workgroup*,
keyword*,
abstract?,
note*,
boilerplate?
}
title =
element title {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute abbrev { text }?,
attribute ascii { text }?,
text
}
title =
element title {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute abbrev { text }?,
attribute ascii { text }?,
text
}
author =
element author {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute initials { text }?,
attribute asciiInitials { text }?,
attribute surname { text }?,
attribute asciiSurname { text }?,
attribute fullname { text }?,
attribute role { "editor" }?,
attribute asciiFullname { text }?,
organization?,
address?
}
author =
element author {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute initials { text }?,
attribute asciiInitials { text }?,
attribute surname { text }?,
attribute asciiSurname { text }?,
attribute fullname { text }?,
attribute role { "editor" }?,
attribute asciiFullname { text }?,
organization?,
address?
}
organization =
element organization {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute abbrev { text }?,
attribute ascii { text }?,
text
}
organization =
element organization {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute abbrev { text }?,
attribute ascii { text }?,
text
}
address =
element address {
attribute xml:base { text }?,
attribute xml:lang { text }?,
postal?,
phone?,
facsimile?,
email?,
uri?
}
address =
element address {
attribute xml:base { text }?,
attribute xml:lang { text }?,
postal?,
phone?,
facsimile?,
email?,
uri?
}
postal =
element postal {
attribute xml:base { text }?,
attribute xml:lang { text }?,
((city | code | country | region | street)* | postalLine+)
}
postal =
element postal {
attribute xml:base { text }?,
attribute xml:lang { text }?,
((city | code | country | region | street)* | postalLine+)
}
street =
element street {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
street =
element street {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
city =
element city {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
city =
element city {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
region =
element region {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
region =
element region {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
code =
element code {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
code =
element code {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
country =
element country {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
country =
element country {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
postalLine =
element postalLine {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
postalLine =
element postalLine {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
phone =
element phone {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
phone =
element phone {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
facsimile =
element facsimile {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
facsimile =
element facsimile {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
email =
element email {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
email =
element email {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute ascii { text }?,
text
}
uri =
element uri {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
uri =
element uri {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
date =
element date {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
date =
element date {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute day { text }?,
attribute month { text }?,
attribute year { text }?,
empty
}
area =
element area {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
area =
element area {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
workgroup =
element workgroup {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
workgroup =
element workgroup {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
keyword =
element keyword {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
keyword =
element keyword {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
abstract =
element abstract {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
(dl | ol | t | ul)+
}
abstract =
element abstract {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
(dl | ol | t | ul)+
}
note =
element note {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute title { text }?,
attribute pn { text }?,
[ a:defaultValue = "false" ]
attribute removeInRFC { "true" | "false" }?,
name?,
(dl | ol | t | ul)+
}
note =
element note {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute title { text }?,
attribute pn { text }?,
[ a:defaultValue = "false" ]
attribute removeInRFC { "true" | "false" }?,
name?,
(dl | ol | t | ul)+
}
boilerplate =
element boilerplate {
attribute xml:base { text }?,
attribute xml:lang { text }?,
section+
}
boilerplate =
element boilerplate {
attribute xml:base { text }?,
attribute xml:lang { text }?,
section+
}
middle =
element middle {
attribute xml:base { text }?,
attribute xml:lang { text }?,
section+
}
middle =
element middle {
attribute xml:base { text }?,
attribute xml:lang { text }?,
section+
}
section =
element section {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute title { text }?,
[ a:defaultValue = "true" ]
attribute numbered { "true" | "false" }?,
[ a:defaultValue = "default" ]
attribute toc { "include" | "exclude" | "default" }?,
[ a:defaultValue = "false" ]
attribute removeInRFC { "true" | "false" }?,
name?,
(artwork
| aside
| blockquote
| dl
| figure
| iref
| ol
| sourcecode
| t
| table
| texttable
| ul)*,
section*
}
section =
element section {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute title { text }?,
[ a:defaultValue = "true" ]
attribute numbered { "true" | "false" }?,
[ a:defaultValue = "default" ]
attribute toc { "include" | "exclude" | "default" }?,
[ a:defaultValue = "false" ]
attribute removeInRFC { "true" | "false" }?,
name?,
(artwork
| aside
| blockquote
| dl
| figure
| iref
| ol
| sourcecode
| t
| table
| texttable
| ul)*,
section*
}
name =
element name {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute slugifiedName { text }?,
(text | cref | eref | relref | tt | xref)*
}
name =
element name {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute slugifiedName { text }?,
(text | cref | eref | relref | tt | xref)*
}
t =
element t {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute hangText { text }?,
[ a:defaultValue = "false" ]
attribute keepWithNext { "false" | "true" }?,
[ a:defaultValue = "false" ]
attribute keepWithPrevious { "false" | "true" }?,
(text
| bcp14
| cref
| em
| eref
| iref
| \list
| relref
| spanx
| strong
| sub
| sup
| tt
| vspace
| xref)*
}
t =
element t {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute hangText { text }?,
[ a:defaultValue = "false" ]
attribute keepWithNext { "false" | "true" }?,
[ a:defaultValue = "false" ]
attribute keepWithPrevious { "false" | "true" }?,
(text
| bcp14
| cref
| em
| eref
| iref
| \list
| relref
| spanx
| strong
| sub
| sup
| tt
| vspace
| xref)*
}
aside =
element aside {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
(artwork | dl | figure | iref | \list | ol | t | table | ul)*
}
aside =
element aside {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
(artwork | dl | figure | iref | \list | ol | t | table | ul)*
}
blockquote =
element blockquote {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute cite { text }?,
attribute quotedFrom { text }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)+)
}
blockquote =
element blockquote {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute cite { text }?,
attribute quotedFrom { text }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)+)
}
\list =
element list {
attribute xml:base { text }?,
attribute xml:lang { text }?,
[ a:defaultValue = "empty" ] attribute style { text }?,
attribute hangIndent { text }?,
attribute counter { text }?,
attribute pn { text }?,
t+
}
\list =
element list {
attribute xml:base { text }?,
attribute xml:lang { text }?,
[ a:defaultValue = "empty" ] attribute style { text }?,
attribute hangIndent { text }?,
attribute counter { text }?,
attribute pn { text }?,
t+
}
ol =
element ol {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "1" ] attribute type { text }?,
[ a:defaultValue = "1" ] attribute start { text }?,
attribute group { text }?,
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
attribute pn { text }?,
li+
}
ol =
element ol {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "1" ] attribute type { text }?,
[ a:defaultValue = "1" ] attribute start { text }?,
attribute group { text }?,
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
attribute pn { text }?,
li+
}
ul =
element ul {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
([ a:defaultValue = "false" ]
attribute empty { "false" | "true" },
attribute pn { text }?)?,
li+
}
ul =
element ul {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
([ a:defaultValue = "false" ]
attribute empty { "false" | "true" },
attribute pn { text }?)?,
li+
}
li =
element li {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)+)
}
li =
element li {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)+)
}
dl =
element dl {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
[ a:defaultValue = "true" ]
attribute hanging { "false" | "true" }?,
attribute pn { text }?,
(dt, dd)+
}
dl =
element dl {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "normal" ]
attribute spacing { "normal" | "compact" }?,
[ a:defaultValue = "true" ]
attribute hanging { "false" | "true" }?,
attribute pn { text }?,
(dt, dd)+
}
dt =
element dt {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*
}
dt =
element dt {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*
}
dd =
element dd {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)+)
}
dd =
element dd {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)+)
}
xref =
element xref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { xsd:IDREF },
[ a:defaultValue = "false" ]
attribute pageno { "true" | "false" }?,
[ a:defaultValue = "default" ]
attribute format { "default" | "title" | "counter" | "none" }?,
attribute derivedContent { text }?,
text
}
xref =
element xref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { xsd:IDREF },
[ a:defaultValue = "false" ]
attribute pageno { "true" | "false" }?,
[ a:defaultValue = "default" ]
attribute format { "default" | "title" | "counter" | "none" }?,
attribute derivedContent { text }?,
text
}
relref =
element relref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { xsd:IDREF },
[ a:defaultValue = "of" ]
attribute displayFormat { "of" | "comma" | "parens" | "bare" }?,
attribute section { text },
attribute relative { text }?,
attribute derivedLink { text }?,
text
}
relref =
element relref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { xsd:IDREF },
[ a:defaultValue = "of" ]
attribute displayFormat { "of" | "comma" | "parens" | "bare" }?,
attribute section { text },
attribute relative { text }?,
attribute derivedLink { text }?,
text
}
eref =
element eref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { text },
text
}
eref =
element eref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { text },
text
}
iref =
element iref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
attribute pn { text }?,
empty
}
iref =
element iref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
attribute pn { text }?,
empty
}
cref =
element cref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute source { text }?,
[ a:defaultValue = "true" ]
attribute display { "true" | "false" }?,
(text | em | eref | relref | strong | sub | sup | tt | xref)*
}
cref =
element cref {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute source { text }?,
[ a:defaultValue = "true" ]
attribute display { "true" | "false" }?,
(text | em | eref | relref | strong | sub | sup | tt | xref)*
}
tt =
element tt {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| xref)*
}
tt =
element tt {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| xref)*
}
strong =
element strong {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| sub
| sup
| tt
| xref)*
}
strong =
element strong {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| sub
| sup
| tt
| xref)*
}
em =
element em {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*
}
em =
element em {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*
}
sub =
element sub {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| tt
| xref)*
}
sub =
element sub {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| tt
| xref)*
}
sup =
element sup {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| tt
| xref)*
}
sup =
element sup {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| strong
| tt
| xref)*
}
spanx =
element spanx {
attribute xml:base { text }?,
attribute xml:lang { text }?,
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
text
}
spanx =
element spanx {
attribute xml:base { text }?,
attribute xml:lang { text }?,
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
text
}
vspace =
element vspace {
attribute xml:base { text }?,
attribute xml:lang { text }?,
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
vspace =
element vspace {
attribute xml:base { text }?,
attribute xml:lang { text }?,
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
figure =
element figure {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
attribute src { text }?,
attribute originalSrc { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
name?,
iref*,
preamble?,
(artwork | sourcecode)+,
postamble?
}
figure =
element figure {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
attribute src { text }?,
attribute originalSrc { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
name?,
iref*,
preamble?,
(artwork | sourcecode)+,
postamble?
}
table =
element table {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
name?,
iref*,
thead?,
tbody+,
tfoot?
}
table =
element table {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
name?,
iref*,
thead?,
tbody+,
tfoot?
}
preamble =
element preamble {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
preamble =
element preamble {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
artwork =
element artwork {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute xml:space { text }?,
[ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "" ] attribute type { text }?,
attribute src { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
attribute originalSrc { text }?,
(text* | svg)
}
# https://www.rfc-editor.org/materials/format/SVG-1.2-RFC.rnc
artwork =
element artwork {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
attribute xml:space { text }?,
[ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "" ] attribute type { text }?,
attribute src { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
attribute originalSrc { text }?,
(text* | svg)
}
# https://www.rfc-editor.org/materials/format/SVG-1.2-RFC.rnc
sourcecode =
element sourcecode {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
[ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "" ] attribute type { text }?,
attribute src { text }?,
attribute originalSrc { text }?,
text
}
sourcecode =
element sourcecode {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute pn { text }?,
[ a:defaultValue = "" ] attribute name { text }?,
[ a:defaultValue = "" ] attribute type { text }?,
attribute src { text }?,
attribute originalSrc { text }?,
text
}
thead =
element thead {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
tr+
}
thead =
element thead {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
tr+
}
tbody =
element tbody {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
tr+
}
tbody =
element tbody {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
tr+
}
tfoot =
element tfoot {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
tr+
}
tfoot =
element tfoot {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
tr+
}
tr =
element tr {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
(td | th)+
}
tr =
element tr {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
(td | th)+
}
td =
element td {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "0" ] attribute colspan { text }?,
[ a:defaultValue = "0" ] attribute rowspan { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| br
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*)
}
td =
element td {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "0" ] attribute colspan { text }?,
[ a:defaultValue = "0" ] attribute rowspan { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| br
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*)
}
th =
element th {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "0" ] attribute colspan { text }?,
[ a:defaultValue = "0" ] attribute rowspan { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| br
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*)
}
th =
element th {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "0" ] attribute colspan { text }?,
[ a:defaultValue = "0" ] attribute rowspan { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
((artwork | dl | figure | ol | sourcecode | t | ul)+
| (text
| bcp14
| br
| cref
| em
| eref
| iref
| relref
| strong
| sub
| sup
| tt
| xref)*)
}
postamble =
element postamble {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text | cref | eref | iref | spanx | xref)*
}
postamble =
element postamble {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text | cref | eref | iref | spanx | xref)*
}
texttable =
element texttable {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
[ a:defaultValue = "center" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "full" ]
attribute style { "all" | "none" | "headers" | "full" }?,
name?,
preamble?,
ttcol+,
c*,
postamble?
}
texttable =
element texttable {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
[ a:defaultValue = "center" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "full" ]
attribute style { "all" | "none" | "headers" | "full" }?,
name?,
preamble?,
ttcol+,
c*,
postamble?
}
ttcol =
element ttcol {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
(cref | eref | iref | xref | text)*
}
ttcol =
element ttcol {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
(cref | eref | iref | xref | text)*
}
c =
element c {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text | cref | eref | iref | spanx | xref)*
}
c =
element c {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text | cref | eref | iref | spanx | xref)*
}
bcp14 =
element bcp14 {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
bcp14 =
element bcp14 {
attribute xml:base { text }?,
attribute xml:lang { text }?,
text
}
br =
element br {
attribute xml:base { text }?,
attribute xml:lang { text }?,
empty
}
br =
element br {
attribute xml:base { text }?,
attribute xml:lang { text }?,
empty
}
back =
element back {
attribute xml:base { text }?,
attribute xml:lang { text }?,
displayreference*,
references*,
section*
}
back =
element back {
attribute xml:base { text }?,
attribute xml:lang { text }?,
displayreference*,
references*,
section*
}
displayreference =
element displayreference {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { xsd:IDREF },
attribute to { text }
}
displayreference =
element displayreference {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { xsd:IDREF },
attribute to { text }
}
references =
element references {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute pn { text }?,
attribute anchor { xsd:ID }?,
attribute title { text }?,
name?,
(reference | referencegroup)*
}
references =
element references {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute pn { text }?,
attribute anchor { xsd:ID }?,
attribute title { text }?,
name?,
(reference | referencegroup)*
}
reference =
element reference {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID },
attribute target { text }?,
[ a:defaultValue = "true" ]
attribute quoteTitle { "true" | "false" }?,
front,
(annotation | format | refcontent | seriesInfo)*
}
reference =
element reference {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID },
attribute target { text }?,
[ a:defaultValue = "true" ]
attribute quoteTitle { "true" | "false" }?,
front,
(annotation | format | refcontent | seriesInfo)*
}
referencegroup =
element referencegroup {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID },
reference+
}
referencegroup =
element referencegroup {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute anchor { xsd:ID },
reference+
}
seriesInfo =
element seriesInfo {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute name { text },
attribute value { text },
attribute asciiName { text }?,
attribute asciiValue { text }?,
attribute status { text }?,
[ a:defaultValue = "IETF" ]
attribute stream { "IETF" | "IAB" | "IRTF" | "independent" }?,
empty
}
seriesInfo =
element seriesInfo {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute name { text },
attribute value { text },
attribute asciiName { text }?,
attribute asciiValue { text }?,
attribute status { text }?,
[ a:defaultValue = "IETF" ]
attribute stream { "IETF" | "IAB" | "IRTF" | "independent" }?,
empty
}
format =
element format {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { text }?,
attribute type { text },
attribute octets { text }?,
empty
}
format =
element format {
attribute xml:base { text }?,
attribute xml:lang { text }?,
attribute target { text }?,
attribute type { text },
attribute octets { text }?,
empty
}
annotation =
element annotation {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
annotation =
element annotation {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text
| bcp14
| cref
| em
| eref
| iref
| relref
| spanx
| strong
| sub
| sup
| tt
| xref)*
}
refcontent =
element refcontent {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text | bcp14 | em | strong | sub | sup | tt)*
}
start |= rfc
refcontent =
element refcontent {
attribute xml:base { text }?,
attribute xml:lang { text }?,
(text | bcp14 | em | strong | sub | sup | tt)*
}
start |= rfc
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.
以下是v3格式与v2格式的非规范性比较。“-”表示从v2模式中删除的行，“+”表示添加到v3模式中的行。
namespace a =
"http://relaxng.org/ns/compatibility/annotations/1.0"
namespace a =
"http://relaxng.org/ns/compatibility/annotations/1.0"
+ # xml2rfc Version 3 grammar
rfc =
element rfc {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute number { text }?,
[ a:defaultValue = "" ] attribute obsoletes { text }?,
[ a:defaultValue = "" ] attribute updates { text }?,
- attribute category { "std" | "bcp" | "info" | "exp" |
- "historic" }?,
- attribute consensus { "no" | "yes" }?,
+ attribute category { text }?,
+ attribute mode { text }?,
+ [ a:defaultValue = "false" ]
+ attribute consensus { "no" | "yes" | "false" | "true" }?,
attribute seriesNo { text }?,
- attribute ipr {
- "full2026"
- | "noDerivativeWorks2026"
- | "none"
- | "full3667"
- | "noModification3667"
- | "noDerivatives3667"
- | "full3978"
- | "noModification3978"
- | "noDerivatives3978"
- | "trust200811"
- | "noModificationTrust200811"
- | "noDerivativesTrust200811"
- | "trust200902"
- | "noModificationTrust200902"
- | "noDerivativesTrust200902"
- | "pre5378Trust200902"
- }?,
+ # xml2rfc Version 3 grammar
rfc =
element rfc {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute number { text }?,
[ a:defaultValue = "" ] attribute obsoletes { text }?,
[ a:defaultValue = "" ] attribute updates { text }?,
- attribute category { "std" | "bcp" | "info" | "exp" |
- "historic" }?,
- attribute consensus { "no" | "yes" }?,
+ attribute category { text }?,
+ attribute mode { text }?,
+ [ a:defaultValue = "false" ]
+ attribute consensus { "no" | "yes" | "false" | "true" }?,
attribute seriesNo { text }?,
- attribute ipr {
- "full2026"
- | "noDerivativeWorks2026"
- | "none"
- | "full3667"
- | "noModification3667"
- | "noDerivatives3667"
- | "full3978"
- | "noModification3978"
- | "noDerivatives3978"
- | "trust200811"
- | "noModificationTrust200811"
- | "noDerivativesTrust200811"
- | "trust200902"
- | "noModificationTrust200902"
- | "noDerivativesTrust200902"
- | "pre5378Trust200902"
- }?,
+ attribute ipr { text }?, 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 = "false" ] + attribute sortRefs { "true" | "false" }?, + [ a:defaultValue = "true" ] + attribute symRefs { "true" | "false" }?, + [ a:defaultValue = "true" ] + attribute tocInclude { "true" | "false" }?, + [ a:defaultValue = "3" ] attribute tocDepth { text }?, + attribute prepTime { text }?, + [ a:defaultValue = "true" ] + attribute indexInclude { "true" | "false" }?, + attribute version { text }?, + [ a:defaultValue = "Common,Latin" ] attribute scripts { text + }?, + attribute expiresDate { text }?, + link*, front, middle, back? }
+ 属性ipr{text}？、属性iprExtract{xsd:IDREF}？、[a:defaultValue=“IETF”]属性submissionType{IETF”|“IAB”|“IRTF”|“独立”}？、属性docName{text}、-[a:defaultValue=“en”]属性xml:lang{text}、+[a:defaultValue=“false”]+属性sortRefs{true”|“false”、+[a:defaultValue=“true”]+属性symRefs{“真”|“假”}、+[a:defaultValue=“真”]+属性tocInclude{“真”|“假”}、+[a:defaultValue=“3”]属性tocDepth{text}、+属性prepTime{text}、+[a:defaultValue=“真”]+属性indexInclude{“真”|“假”}、+属性版本{text}、+[a:defaultValue=“常用，拉丁文”]属性脚本{text+}？，+属性过期日期{text}？，+链接*，前面，中间，后面？}
+ link = + element link { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute href { text }, + attribute rel { text }? + } front = element front { - title, author+, date, area*, workgroup*, keyword*, abstract?, - note* + attribute xml:base { text }?, + attribute xml:lang { text }?, + title, + seriesInfo*, + author+, + date?, + area*, + workgroup*, + keyword*, + abstract?, + note*, + boilerplate? } title = element title { + attribute xml:base { text }?, + attribute xml:lang { text }?, attribute abbrev { text }?, + attribute ascii { text }?, text } author = element author { + attribute xml:base { text }?, + attribute xml:lang { text }?, attribute initials { text }?, + attribute asciiInitials { text }?, attribute surname { text }?, + attribute asciiSurname { text }?, attribute fullname { text }?, attribute role { "editor" }?, + attribute asciiFullname { text }?, organization?, address? }
+ link=+元素link{+属性xml:base{text}？，+属性xml:lang{text}？，+属性href{text}，+属性rel{text}？++}front=元素front{-标题，作者+，日期，区域*，工作组*，关键字*，摘要？，-注释*+属性xml:base{text}？，+属性xml:lang text}？，+title，+serieinfo*，+author+，+date？，+area*，+workgroup*，+keyword*，+abstract？，+note*，+boilerplate？}title=元素标题{+属性xml:base{text}？，+attribute xml:lang{text}，属性abbrev{text}，+attribute ascii{text}，text}作者=元素作者{+属性xml:base{text}？，+属性xml:lang{text}？、属性首字母{text}？、+属性ASCIIIinitials{text}？、属性姓氏{text}？、+属性asciiSurname{text}？、属性全名{text}？、属性角色{“编辑器”}、+属性asciiFullname{text}？、组织？、地址}
organization =
element organization {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute abbrev { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ address =
+ element address {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ postal?,
+ phone?,
+ facsimile?,
+ email?,
+ uri?
+ }
+ postal =
+ element postal {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ ((city | code | country | region | street)* | postalLine+)
+ }
+ street =
+ element street {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ city =
+ element city {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ region =
+ element region {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute ascii { text }?,
+ text
+ }
organization =
element organization {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute abbrev { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ address =
+ element address {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ postal?,
+ phone?,
+ facsimile?,
+ email?,
+ uri?
+ }
+ postal =
+ element postal {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ ((city | code | country | region | street)* | postalLine+)
+ }
+ street =
+ element street {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ city =
+ element city {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ region =
+ element region {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute ascii { text }?,
+ text
+ }
+ code = + element code { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute ascii { text }?, + text + } + country = + element country { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute ascii { text }?, + text + } + postalLine = + element postalLine { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute ascii { text }?, + text + } + phone = + element phone { + attribute xml:base { text }?, + attribute xml:lang { text }?, + text + } + facsimile = + element facsimile { + attribute xml:base { text }?, + attribute xml:lang { text }?, + text + } + email = + element email { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute ascii { text }?, + text + }
+ code=+元素代码{+属性xml:base{text}？，+属性xml:lang{text}？，+属性ascii{text}？，+text+}+country=+元素国家{+属性xml:base{text}？，+属性xml:lang{text}？，+属性ascii{text}，+text+}+postalLine=+元素postalLine{+属性xml:base{text}？，+属性xml:lang{text}？，+属性ascii{text}？，+text+}+phone=+元素phone{+属性xml:base{text}？，+属性xml:lang{text}？，+text+}+fax=+元素fax{+属性xml:base{text}？，+属性xml:lang{text}，+text+}+email=+元素email{+属性xml:base{text}？，+属性xml:lang{text}？，+属性ascii{text}？，+text+}
+ uri = + element uri { + attribute xml:base { text }?, + attribute xml:lang { 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 } - phone = element phone { text } - facsimile = element facsimile { text } - email = element email { text } - uri = element uri { text } date = element date { + attribute xml:base { text }?, + attribute xml:lang { text }?, 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+ } + area = + element area { + attribute xml:base { text }?, + attribute xml:lang { text }?, + text + } + workgroup = + element workgroup { + attribute xml:base { text }?, + attribute xml:lang { text }?, + text + }
+ uri=+元素uri{+属性xml:base{text}？，+属性xml:lang{text}，text}-地址=元素地址{邮政？、电话？、传真？、电子邮件？，-uri？}-邮政=元素邮政{street+，（城市|地区|代码|国家）*}-街道=元素街道{text}-城市=元素城市{text}-地区=元素地区{text}-code=element code{text}-country=element country{text}-phone=element phone{text}-fax=element fax{text}-email=element email{text}-uri=element uri{text}date=element日期{+属性xml:base{text}？，+属性xml:lang text}，属性日{text}，属性月{text}？，属性年{text}？，空}-区域=元素区域{text}-工作组=元素工作组{text}-关键字=元素关键字{text}-抽象=元素抽象{t+}+区域=+元素区域{+属性xml:base{text}？，+属性xml:lang{text}，+text+}+工作组=+元素工作组{+属性xml:base{text}？，+属性xml:lang{text}？，+text+}
+ keyword = + element keyword { + attribute xml:base { text }?, + attribute xml:lang { text }?, + text + } + abstract = + element abstract { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + attribute pn { text }?, + (dl | ol | t | ul)+ + } note = element note { - attribute title { text }, - t+ + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute title { text }?, + attribute pn { text }?, + [ a:defaultValue = "false" ] + attribute removeInRFC { "true" | "false" }?, + name?, + (dl | ol | t | ul)+ + } + boilerplate = + element boilerplate { + attribute xml:base { text }?, + attribute xml:lang { text }?, + section+ + } + middle = + element middle { + attribute xml:base { text }?, + attribute xml:lang { text }?, + section+ }
+ 关键字=+元素关键字{+属性xml:base{text}？，+属性xml:lang{text}？，+文本+}+抽象=+元素抽象{+属性xml:base{text}？，+属性xml:lang{text}？，+属性锚{xsd:ID}，+属性pn{text}，+（dl | ol | t | ul）+}注释=元素注释{-属性标题{text}，-t++属性xml:base{text}？，+属性xml:lang{text}？，+属性title{text}？，+属性pn{text}？，+[a:defaultValue=“false”]+属性removeInRFC{“true”|“false”}，+name？，+（dl | ol | t | ul）+}+样板文件=+元素样板文件{+属性xml:base{text}，+属性xml:lang text}？，+section++}+middle=+元素middle{+属性xml:base{text}？，+属性xml:lang{text}？，+section++
- middle = element middle { section+ } section = element section { + attribute xml:base { text }?, + attribute xml:lang { text }?, attribute anchor { xsd:ID }?, - attribute title { text }, + attribute pn { text }?, + attribute title { text }?, + [ a:defaultValue = "true" ] + attribute numbered { "true" | "false" }?, [ a:defaultValue = "default" ] attribute toc { "include" | "exclude" | "default" }?, - (t | figure | texttable | iref)*, + [ a:defaultValue = "false" ] + attribute removeInRFC { "true" | "false" }?, + name?, + (artwork + | aside + | blockquote + | dl + | figure + | iref + | ol + | sourcecode + | t + | table + | texttable + | ul)*, section* }
- middle=element middle{section+}section=element section{+attribute xml:base{text}？，+attribute xml:lang{text}？，attribute anchor{xsd:ID}？，-attribute title{text}，+attribute pn{text}，+attribute title{text}，+[a:defaultValue=“true”]+属性编号为{true”| false}，[a:defaultValue=“default default”]属性toc{“包括”|“排除”|“默认”}、-（t |图|文本表| iref）*、+[a:defaultValue=“false”]+属性removeInRFC{“真”|“假”}、+name？、+（artwork+|旁白+| blockquote+| dl+|图+| iref+| ol+|源代码+|表+|文本表+| ul ul |部分*）
+ name = + element name { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute slugifiedName { text }?, + (text | cref | eref | relref | tt | xref)* + } t = element t { + attribute xml:base { text }?, + attribute xml:lang { text }?, attribute anchor { xsd:ID }?, + attribute pn { text }?, attribute hangText { text }?, + [ a:defaultValue = "false" ] + attribute keepWithNext { "false" | "true" }?, + [ a:defaultValue = "false" ] + attribute keepWithPrevious { "false" | "true" }?, (text - | \list - | figure - | xref + | bcp14 + | cref + | em | eref | iref - | cref + | \list + | relref | spanx - | vspace)* + | strong + | sub + | sup + | tt + | vspace + | xref)* + } + aside = + element aside { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + attribute pn { text }?, + (artwork | dl | figure | iref | \list | ol | t | table | ul)* + }
+ name=+元素名称{+属性xml:base{text}？，+属性xml:lang{text}？，+属性slugifiedName{text}，+（text | cref | eref | relref | tt | xref）*+}t=元素t{+属性xml:base{text}？，+属性xml:lang text}？，+属性锚点{xsd:ID}？，+属性pn text{text}，属性hangText}，+[a:defaultValue=“false”]+属性保持与下一个{“false”|“true”}、+[a:defaultValue=“false”]+属性保持与上一个{“false”|“true”}、（text-| \list-| figure-| xref+| bcp14+| cref+| em | eref | iref-| cref+| cref+|列表| relref | spanx-| vspace）*+++aside=+元素aside{+属性xml:base{text}？，+属性xml:lang{text}？，+属性anchor{xsd:ID}？，+属性pn{text}，+（artwork | dl | figure | iref | list | ol | t | table ul）*+]
+ blockquote = + element blockquote { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + attribute pn { text }?, + attribute cite { text }?, + attribute quotedFrom { text }?, + ((artwork | dl | figure | ol | sourcecode | t | ul)+ + | (text + | bcp14 + | cref + | em + | eref + | iref + | relref + | strong + | sub + | sup + | tt + | xref)+) } \list = element list { - attribute style { text }?, + attribute xml:base { text }?, + attribute xml:lang { text }?, + [ a:defaultValue = "empty" ] attribute style { text }?, attribute hangIndent { text }?, attribute counter { text }?, + attribute pn { text }?, t+ } + ol = + element ol { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + [ a:defaultValue = "1" ] attribute type { text }?, + [ a:defaultValue = "1" ] attribute start { text }?, + attribute group { text }?, + [ a:defaultValue = "normal" ] + attribute spacing { "normal" | "compact" }?, + attribute pn { text }?, + li+ + }
+ blockquote=+元素blockquote{+属性xml:base{text}？，+属性xml:lang{text}？，+属性anchor{xsd:ID}？，+属性pn{text}？，+属性cite{text}？，+属性quotedFrom{text}，+（（artwork | dl | figure | ol |源代码| t | ul）+（text+|bcp14+|cref+|em+|eref+|iref+|relref+| strong+| sub+|tt+|xref）+list=元素列表{-属性样式{text}、+属性xml:base{text}、+属性xml:lang text}、+[a:defaultValue=“empty”]属性样式{text}、属性悬挂缩进{text}、属性计数器{text}？，+属性pn{text}，t+}+ol=+元素ol{+属性xml:base{text}？，+属性xml:lang{text}？，+属性锚点{xsd:ID}？，+[a:defaultValue=“1”]属性类型{text}，+[a:defaultValue=“1”]属性开始{text}？，+属性组{text}，+[a:defaultValue=“normal normal”]+属性间距{normal|“compact”}？，+属性pn{text}？，+li++}
+ ul = + element ul { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + [ a:defaultValue = "normal" ] + attribute spacing { "normal" | "compact" }?, + ([ a:defaultValue = "false" ] + attribute empty { "false" | "true" }, + attribute pn { text }?)?, + li+ + } + li = + element li { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + attribute pn { text }?, + ((artwork | dl | figure | ol | sourcecode | t | ul)+ + | (text + | bcp14 + | cref + | em + | eref + | iref + | relref + | strong + | sub + | sup + | tt + | xref)+) + } + dl = + element dl { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + [ a:defaultValue = "normal" ] + attribute spacing { "normal" | "compact" }?, + [ a:defaultValue = "true" ] + attribute hanging { "false" | "true" }?, + attribute pn { text }?, + (dt, dd)+ + }
+ ul=+元素ul{+属性xml:base{text}？，+属性xml:lang{text}？，+属性锚点{xsd:ID}，++[a:defaultValue=“normal”]+属性间距{“normal”|“compact”}，+（[a:defaultValue=“false”]+属性空{“false”|“true”}，+属性pn text}？，+li+++li=+元素li{+属性xml:base{text}、+attribute xml:lang{text}、+attribute anchor{xsd:ID}、+attribute pn{text}、+（（artwork | dl | figure | ol | sourcecode | t | ul）+++|（text++bcp14+| cref+| em+| eref+| iref+| relref+| relref++| strong++| sub sup tt+| xref trade=+基元素{xml:}{text}？，+属性锚点{xsd:ID}，+[a:defaultValue=“normal”]+属性间距{“normal”|“compact”}，+[a:defaultValue=“true”]+属性挂起{“false”|“true”}，+属性pn{text}，+（dt，dd）+}
+ dt = + element dt { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + attribute pn { text }?, + (text + | bcp14 + | cref + | em + | eref + | iref + | relref + | strong + | sub + | sup + | tt + | xref)* + } + dd = + element dd { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + attribute pn { text }?, + ((artwork | dl | figure | ol | sourcecode | t | ul)+ + | (text + | bcp14 + | cref + | em + | eref + | iref + | relref + | strong + | sub + | sup + | tt + | xref)+) + }
+ dt=+元素dt{+属性xml:base{text}？，+属性xml:lang{text}？，+属性锚点{xsd:ID}？，+属性pn{text}，+（text+| bcp14+| cref+| em+| eref+| iref+| relref+| strong+| sub+| sup+| tt+| xref）*}+dd=+元素dd{+属性xml:base{text}，+attribute？，+属性锚点{xsd:ID}？，+属性pn{text}，+（（artwork | dl | figure | ol | sourcecode | t | ul）+++|（text+| bcp14+| cref+| em+| eref+| iref+| relref+| strong+| sub+| sup+| tt+| xref）+）
xref =
element xref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute target { xsd:IDREF },
- [ a:defaultValue = "false" ] attribute pageno { "true" |
- "false" }?,
+ [ a:defaultValue = "false" ]
+ attribute pageno { "true" | "false" }?,
[ a:defaultValue = "default" ]
- attribute format { "counter" | "title" | "none" | "default"
+ attribute format { "default" | "title" | "counter" | "none"
+ }?,
+ attribute derivedContent { text }?,
+ text
+ }
+ relref =
+ element relref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute target { xsd:IDREF },
+ [ a:defaultValue = "of" ]
+ attribute displayFormat { "of" | "comma" | "parens" | "bare"
}?,
+ attribute section { text },
+ attribute relative { text }?,
+ attribute derivedLink { text }?,
text
}
eref =
element eref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute target { text },
text
}
iref =
element iref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
+ attribute pn { text }?,
empty
}
xref =
element xref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute target { xsd:IDREF },
- [ a:defaultValue = "false" ] attribute pageno { "true" |
- "false" }?,
+ [ a:defaultValue = "false" ]
+ attribute pageno { "true" | "false" }?,
[ a:defaultValue = "default" ]
- attribute format { "counter" | "title" | "none" | "default"
+ attribute format { "default" | "title" | "counter" | "none"
+ }?,
+ attribute derivedContent { text }?,
+ text
+ }
+ relref =
+ element relref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute target { xsd:IDREF },
+ [ a:defaultValue = "of" ]
+ attribute displayFormat { "of" | "comma" | "parens" | "bare"
}?,
+ attribute section { text },
+ attribute relative { text }?,
+ attribute derivedLink { text }?,
text
}
eref =
element eref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute target { text },
text
}
iref =
element iref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute item { text },
[ a:defaultValue = "" ] attribute subitem { text }?,
[ a:defaultValue = "false" ]
attribute primary { "true" | "false" }?,
+ attribute pn { text }?,
empty
}
cref =
element cref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute source { text }?,
- text
+ [ a:defaultValue = "true" ]
+ attribute display { "true" | "false" }?,
+ (text | em | eref | relref | strong | sub | sup | tt | xref)*
+ }
+ tt =
+ element tt {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | iref
+ | relref
+ | strong
+ | sub
+ | sup
+ | xref)*
+ }
+ strong =
+ element strong {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | iref
+ | relref
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
cref =
element cref {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
attribute source { text }?,
- text
+ [ a:defaultValue = "true" ]
+ attribute display { "true" | "false" }?,
+ (text | em | eref | relref | strong | sub | sup | tt | xref)*
+ }
+ tt =
+ element tt {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | iref
+ | relref
+ | strong
+ | sub
+ | sup
+ | xref)*
+ }
+ strong =
+ element strong {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | iref
+ | relref
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ em = + element em { + attribute xml:base { text }?, + attribute xml:lang { text }?, + (text + | bcp14 + | cref + | eref + | iref + | relref + | strong + | sub + | sup + | tt + | xref)* + } + sub = + element sub { + attribute xml:base { text }?, + attribute xml:lang { text }?, + (text + | bcp14 + | cref + | em + | eref + | iref + | relref + | strong + | tt + | xref)* + } + sup = + element sup { + attribute xml:base { text }?, + attribute xml:lang { text }?, + (text + | bcp14 + | cref + | em + | eref + | iref + | relref + | strong + | tt + | xref)* }
+ em=+元素em{+属性xml:base{text}？，+属性xml:lang{text}，+（text+|bcp14+| cref+| eref+| iref+| relref+| strong+| sub+|sup+| tt+| xref）*+++元素sub sub{+属性xml:base{text}？，+属性xml:lang text}，+（text+| bcp14+| cref+| em+| eref+| iref+| relref+| strong+| tt+| xref）*++sup=+元素sup{属性xml:base{text}，+属性xml:lang{text}，++（text+| bcp14+| cref+|em+| eref+|iref+| relref
spanx =
element spanx {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
text
}
vspace =
element vspace {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
figure =
element figure {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
+ attribute pn { text }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
attribute src { text }?,
+ attribute originalSrc { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
+ name?,
iref*,
preamble?,
- artwork,
+ (artwork | sourcecode)+,
postamble?
}
spanx =
element spanx {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
[ a:defaultValue = "preserve" ]
attribute xml:space { "default" | "preserve" }?,
[ a:defaultValue = "emph" ] attribute style { text }?,
text
}
vspace =
element vspace {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
[ a:defaultValue = "0" ] attribute blankLines { text }?,
empty
}
figure =
element figure {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
+ attribute pn { text }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
attribute src { text }?,
+ attribute originalSrc { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "" ] attribute alt { text }?,
[ a:defaultValue = "" ] attribute width { text }?,
[ a:defaultValue = "" ] attribute height { text }?,
+ name?,
iref*,
preamble?,
- artwork,
+ (artwork | sourcecode)+,
postamble?
}
+ table = + element table { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + attribute pn { text }?, + name?, + iref*, + thead?, + tbody+, + tfoot? + } preamble = - element preamble { (text | xref | eref | iref | cref | spanx)* } + element preamble { + attribute xml:base { text }?, + attribute xml:lang { text }?, + (text + | bcp14 + | cref + | em + | eref + | iref + | relref + | spanx + | strong + | sub + | sup + | tt + | xref)* + }
+ table=+元素表{+属性xml:base{text}？，+属性xml:lang{text}？，+属性锚点{xsd:ID}？，+属性pn{text}？，+name？，+iref*，+thead？，+tbody+，+tfoot？+}前导=-元素前导{（text | xref eref | iref | cref | spanx）*}+元素前导{+属性xml:base{text}？，+属性xml:lang{text}？，+（text++bcp14++cref++em++eref++iref++relref++spanx++strong++sub++sup++tt++xref）*++
artwork =
element artwork {
- [ a:defaultValue = "preserve" ]
- attribute xml:space { "default" | "preserve" }?,
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ attribute pn { text }?,
+ 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 }?,
- text*
+ attribute originalSrc { text }?,
+ (text* | svg)
+ }
+ # https://www.rfc-editor.org/materials/format/SVG-1.2-RFC.rnc
+ sourcecode =
+ element sourcecode {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ attribute pn { text }?,
+ [ a:defaultValue = "" ] attribute name { text }?,
+ [ a:defaultValue = "" ] attribute type { text }?,
+ attribute src { text }?,
+ attribute originalSrc { text }?,
+ text
+ }
+ thead =
+ element thead {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ tr+
+ }
+ tbody =
+ element tbody {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ tr+
+ }
artwork =
element artwork {
- [ a:defaultValue = "preserve" ]
- attribute xml:space { "default" | "preserve" }?,
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ attribute pn { text }?,
+ 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 }?,
- text*
+ attribute originalSrc { text }?,
+ (text* | svg)
+ }
+ # https://www.rfc-editor.org/materials/format/SVG-1.2-RFC.rnc
+ sourcecode =
+ element sourcecode {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ attribute pn { text }?,
+ [ a:defaultValue = "" ] attribute name { text }?,
+ [ a:defaultValue = "" ] attribute type { text }?,
+ attribute src { text }?,
+ attribute originalSrc { text }?,
+ text
+ }
+ thead =
+ element thead {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ tr+
+ }
+ tbody =
+ element tbody {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ attribute anchor { xsd:ID }?,
+ tr+
+ }
+ tfoot = + element tfoot { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + tr+ + } + tr = + element tr { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + (td | th)+ + } + td = + element td { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + [ a:defaultValue = "0" ] attribute colspan { text }?, + [ a:defaultValue = "0" ] attribute rowspan { text }?, + [ a:defaultValue = "left" ] + attribute align { "left" | "center" | "right" }?, + ((artwork | dl | figure | ol | sourcecode | t | ul)+ + | (text + | bcp14 + | br + | cref + | em + | eref + | iref + | relref + | strong + | sub + | sup + | tt + | xref)*) + }
+ tfoot=+element-tfoot{+attribute xml:base{text}？，+attribute xml:lang{text}？，+attribute anchor{xsd:ID}？，+tr++}+tr=+element-tr{+attribute xml:base{text}？，+attribute xml:lang{text}，+attribute anchor{xsd:ID}，+（td|th）++td=+element-td{+attribute td{+attribute xml:base{text}，+attribute xml:base{text}，+lang text}？，+属性锚点{xsd:ID}？，+[a:defaultValue=“0”]属性列{text}？，+[a:defaultValue=“0”]属性行{text}，+[a:defaultValue=“left”]+属性对齐{“left”|“center”|“right”}，+（（插图| dl |图| ol |源代码| t | ul）++（文本+| bcp14+| br+| cref+| em+| eref+| iref+| relref+| strong+| sup+| tt+|外部参照）*++
+ th = + element th { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }?, + [ a:defaultValue = "0" ] attribute colspan { text }?, + [ a:defaultValue = "0" ] attribute rowspan { text }?, + [ a:defaultValue = "left" ] + attribute align { "left" | "center" | "right" }?, + ((artwork | dl | figure | ol | sourcecode | t | ul)+ + | (text + | bcp14 + | br + | cref + | em + | eref + | iref + | relref + | strong + | sub + | sup + | tt + | xref)*) } postamble = - element postamble { (text | xref | eref | iref | cref | spanx)* + element postamble { + attribute xml:base { text }?, + attribute xml:lang { text }?, + (text | cref | eref | iref | spanx | xref)* }
+ th=+元素th{+属性xml:base{text}？，+属性xml:lang{text}？，+属性锚点{xsd:ID}？，+[a:defaultValue=“0”]属性colspan{text}？，+[a:defaultValue=“0”]属性行span{text}，+[a:defaultValue=“left”]+属性对齐{“left”|“center”|“right”}，+(（艺术作品（艺术作品）dl | dl |艺术作品（艺术作品）dl |电路图（艺术作品）dl | dl |艺术作品（艺术作品）dl | dl | dl |艺术作品（艺术作品）dl | dl 124;数字|数字124;数字124;数字124;电路电路|数字|数字|电路电路|数字|数字|数字124;数字124;数字|数字|数字|数字|数字|数字|数字|数字|数字|数字|数字|数字124+（文本| cref | eref | iref | spanx | xref）*}
texttable =
element texttable {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
[ a:defaultValue = "center" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "full" ]
attribute style { "all" | "none" | "headers" | "full" }?,
+ name?,
preamble?,
ttcol+,
c*,
postamble?
}
ttcol =
element ttcol {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
+ (cref | eref | iref | xref | text)*
+ }
+ c =
+ element c {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text | cref | eref | iref | spanx | xref)*
+ }
+ bcp14 =
+ element bcp14 {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
text
}
- c = element c { (text | xref | eref | iref | cref | spanx)* }
- back = element back { references*, section* }
+ br =
+ element br {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ empty
+ }
texttable =
element texttable {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute anchor { xsd:ID }?,
[ a:defaultValue = "" ] attribute title { text }?,
[ a:defaultValue = "false" ]
attribute suppress-title { "true" | "false" }?,
[ a:defaultValue = "center" ]
attribute align { "left" | "center" | "right" }?,
[ a:defaultValue = "full" ]
attribute style { "all" | "none" | "headers" | "full" }?,
+ name?,
preamble?,
ttcol+,
c*,
postamble?
}
ttcol =
element ttcol {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
attribute width { text }?,
[ a:defaultValue = "left" ]
attribute align { "left" | "center" | "right" }?,
+ (cref | eref | iref | xref | text)*
+ }
+ c =
+ element c {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text | cref | eref | iref | spanx | xref)*
+ }
+ bcp14 =
+ element bcp14 {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
text
}
- c = element c { (text | xref | eref | iref | cref | spanx)* }
- back = element back { references*, section* }
+ br =
+ element br {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ empty
+ }
+ back = + element back { + attribute xml:base { text }?, + attribute xml:lang { text }?, + displayreference*, + references*, + section* + } + displayreference = + element displayreference { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute target { xsd:IDREF }, + attribute to { text } + } references = element references { - [ a:defaultValue = "References" ] attribute title { text }?, - reference+ + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute pn { text }?, + attribute anchor { xsd:ID }?, + attribute title { text }?, + name?, + (reference | referencegroup)* } reference = element reference { + attribute xml:base { text }?, + attribute xml:lang { text }?, attribute anchor { xsd:ID }, attribute target { text }?, + [ a:defaultValue = "true" ] + attribute quoteTitle { "true" | "false" }?, front, - seriesInfo*, - format*, - annotation* + (annotation | format | refcontent | seriesInfo)* + }
+ back=+元素back{+属性xml:base{text}？，+属性xml:lang{text}？，+displayreference*，+references*，+section*+}+displayreference=+元素displayreference{+属性xml:base{text}？，+属性xml:lang{text}？，+属性目标{xsd:IDREF}，+属性到{text}+}+}引用=元素引用{-[a:defaultValue=“References”]属性标题{text}、-reference++属性xml:base{text}、+attribute xml:lang{text}、+attribute pn{text}、+attribute anchor{xsd:ID}、+attribute title{text}、+name？、+（reference | referencegroup）*}reference=元素引用{+属性xml:base{text}？，+属性xml:lang{text}？、属性锚{xsd:ID}、属性目标{text}、+[a:defaultValue=“true”]+属性引号{“true”|“false”}、front、-seriesInfo*、-format*、-annotation*+（annotation | format | refcontent | seriesInfo）*++
+ referencegroup = + element referencegroup { + attribute xml:base { text }?, + attribute xml:lang { text }?, + attribute anchor { xsd:ID }, + reference+ } seriesInfo = element seriesInfo { + attribute xml:base { text }?, + attribute xml:lang { text }?, attribute name { text }, attribute value { text }, + attribute asciiName { text }?, + attribute asciiValue { text }?, + attribute status { text }?, + [ a:defaultValue = "IETF" ] + attribute stream { "IETF" | "IAB" | "IRTF" | "independent" }?, empty } format = element format { + attribute xml:base { text }?, + attribute xml:lang { text }?, attribute target { text }?, attribute type { text }, attribute octets { text }?, empty }
+ referencegroup=+元素referencegroup{+属性xml:base{text}？，+属性xml:lang{text}？，+属性锚点{xsd:ID}，+reference+}seriesInfo=元素seriesInfo{+属性xml:base{text}？，+属性xml:lang{text}，属性名称{text}，属性值{text}，+属性名称{text}？，+属性asciiValue{text}？，+属性状态{text}？，+[a:defaultValue=“IETF”]+属性流{IETF”|“IAB”|“IRTF”|“独立”}？，空}格式=元素格式{+属性xml:base{text}？，属性xml:lang text}？，属性目标{text}？，属性类型{text}，属性八位字节{text}？，空}
annotation =
- element annotation { (text | xref | eref | iref | cref |
- spanx)* }
- start = rfc
+ element annotation {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | iref
+ | relref
+ | spanx
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ refcontent =
+ element refcontent {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text | bcp14 | em | strong | sub | sup | tt)*
+ }
+ start |= rfc
annotation =
- element annotation { (text | xref | eref | iref | cref |
- spanx)* }
- start = rfc
+ element annotation {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text
+ | bcp14
+ | cref
+ | em
+ | eref
+ | iref
+ | relref
+ | spanx
+ | strong
+ | sub
+ | sup
+ | tt
+ | xref)*
+ }
+ refcontent =
+ element refcontent {
+ attribute xml:base { text }?,
+ attribute xml:lang { text }?,
+ (text | bcp14 | em | strong | sub | sup | tt)*
+ }
+ start |= rfc
IAB Members at the Time of Approval
批准时的IAB成员
The IAB members at the time this memo was approved were (in alphabetical order):
本备忘录批准时，IAB成员为（按字母顺序排列）：
Jari Arkko Ralph Droms Ted Hardie Joe Hildebrand Russ Housley Lee Howard Erik Nordmark Robert Sparks Andrew Sullivan Dave Thaler Martin Thomson Brian Trammell Suzanne Woolf
贾里·阿克科·拉尔夫·德罗姆斯·泰德·哈迪·乔·希尔德布兰德·罗斯·霍斯利·李·霍华德·埃里克·诺德马克·罗伯特·斯帕克斯·安德鲁·沙利文·戴夫·泰勒·马丁·汤姆森·布莱恩·特拉梅尔·苏珊娜·伍尔夫
Acknowledgements
致谢
Thanks to everybody who reviewed this document and provided feedback and/or specification text. Thanks especially go to Julian Reschke for editing [RFC7749] and those who provided feedback on that document.
感谢审阅本文件并提供反馈和/或规范文本的所有人。特别感谢Julian Reschke编辑[RFC7749]以及提供该文档反馈的人员。
We also thank Marshall T. Rose for both the original design and the reference implementation of the "xml2rfc" processor.
我们还感谢Marshall T.Rose对“xml2rfc”处理器的原始设计和参考实现。
Author's Address
作者地址
Paul Hoffman ICANN
保罗·霍夫曼·伊坎
Email: paul.hoffman@icann.org
Email: paul.hoffman@icann.org