Network Working Group M. Mealling
Request for Comments: 3688 VeriSign, Inc.
BCP: 81 January 2004
Category: Best Current Practice
Network Working Group M. Mealling
Request for Comments: 3688 VeriSign, Inc.
BCP: 81 January 2004
Category: Best Current Practice
The IETF XML Registry
IETFXML注册表
Status of this Memo
本备忘录的状况
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
Abstract
摘要
This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.
本文档描述了IETF标准的IANA维护注册表，该注册表使用可扩展标记语言（XML）相关项，如名称空间、文档类型声明（DTD）、模式和资源描述框架（RDF）模式。
Over the past few years, the Extensible Markup Language (XML) [W3C.REC-xml] has become a widely used method for data markup. There have already been several IETF Working Groups that have produced standards that define XML Document Type Definitions (DTDs), XML Namespaces [W3C.REC-xml-names], and XML Schemas [W3C.REC-xmlschema-1]. Each one of these technologies uses Uniform Resource Identifiers (URIs) [RFC2396] and other standardized identifiers to identify various components.
在过去几年中，可扩展标记语言（XML）[W3C.recXML]已成为广泛使用的数据标记方法。已经有几个IETF工作组制定了定义XML文档类型定义（DTD）、XML名称空间[W3C.REC XML名称]和XML模式[W3C.REC-xmlschema-1]的标准。这些技术中的每一种都使用统一资源标识符（URI）[RFC2396]和其他标准化标识符来识别各种组件。
For example, while it has been the practice within some standards that use Document Type Definitions (DTDs) to forego the use of the PUBLIC identifiers in favor of 'well known' SYSTEM identifiers, it has proven to be more trouble than its worth to attempt to standardize SYSTEM identifiers. The result is that several IETF standards that have simply created non-resolvable URIs in order to simply identify but not resolve the DTD for some given XML document.
例如，虽然在一些标准中，使用文档类型定义（DTD）放弃使用公共标识符，转而使用“众所周知的”系统标识符，但事实证明，尝试标准化系统标识符比其价值更麻烦。结果是，一些IETF标准只是创建了不可解析的URI，以便简单地识别但不解析某些给定XML文档的DTD。
This document seeks to standardize and improve these practices by creating an IANA maintained registry of XML element identifiers so that document authors and implementors have a well maintained and
本文档旨在通过创建由IANA维护的XML元素标识符注册中心来标准化和改进这些实践，以便文档作者和实现者有一个维护良好的
authoritative location for their XML elements. As part of this standard, the IANA will maintain:
其XML元素的权威位置。作为本标准的一部分，IANA将保持：
o the public representation of the document,
o 文件的公众代表性，
o the URI for the elements if one is provided at the time of registration,
o 元素的URI（如果在注册时提供），
o a registry of Public Identifiers as URIs.
o 作为URI的公共标识符的注册表。
In the case where the registrant does not request a particular URI, the IANA will assign it a Uniform Resource Name (URN) that follows [RFC3553].
在注册人不请求特定URI的情况下，IANA将在[RFC3553]之后为其分配一个统一资源名（URN）。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[RFC2119]中的说明进行解释。
All elements (except PUBLIC identifiers) in this registry will require a URI in order to be registered. If the registrant wishes to have a URI assigned, then a URN of the form
此注册表中的所有元素（公共标识符除外）都需要URI才能注册。如果注册人希望分配URI，则需要表单的URN
urn:ietf:params:xml:<class>:<id>
urn:ietf:params:xml:<class>:<id>
will be assigned where <class> is the type of the document being registered (see below). <id> is a unique id generated by the IANA based on any means the IANA deems necessary to maintain uniqueness and persistence. NOTE: in order for a URN of this type to be assigned, the item being registered MUST have been through the IETF consensus process. Basically, this means that it must be documented in a RFC. The RFC 3553 [RFC3553] URN registration template is found in Section 6.
将被分配，其中<class>是正在注册的文档的类型（见下文）<id>是IANA根据IANA认为保持唯一性和持久性所必需的任何方式生成的唯一id。注：为了分配此类URN，注册的项目必须通过IETF协商一致流程。基本上，这意味着必须将其记录在RFC中。RFC 3553[RFC3553]URN注册模板见第6节。
The IANA will also maintain a file server available via at least HTTP and FTP that contains all of the registered elements in some publicly accessible file space in the same way that all of the IANA's registered elements are available via http://www.iana.org/assignments/. While the directory structure of this server is up to the IANA, it is suggested that the files be organized by the <class> and the individual files have the <id> as their filename.
IANA还将至少通过HTTP和FTP维护一个文件服务器，该服务器包含一些可公开访问的文件空间中的所有注册元素，与IANA的所有注册元素通过HTTP和FTP可用的方式相同http://www.iana.org/assignments/. 虽然此服务器的目录结构由IANA决定，但建议文件由<class>组织，并且单个文件的文件名为<id>。
Implementors are warned that they should not programatically rely on those resources being available or the directory structure remaining static for any reason. It is explicitly recognized that some software tools attempt to download DTDs, schema, etc., 'on the fly' and that developers should understand when this is done and when to not reference IANA network resources as a 'schema download repository'. This is the reason that the IANA will not register or provide SYSTEM identifiers.
实现者被警告，他们不应该以编程的方式依赖那些可用的资源，或者目录结构出于任何原因保持静态。人们明确认识到，一些软件工具试图“动态”下载DTD、模式等，开发人员应该了解何时完成下载，何时不将IANA网络资源作为“模式下载存储库”引用。这就是IANA不会注册或提供系统标识符的原因。
The list of types of XML elements that can be registered with the IANA are:
可向IANA注册的XML元素类型列表如下：
publicid -- An XML document that contains a DOCTYPE declaration or any other external reference can identify that reference via both a PUBLIC identifier and a SYSTEM identifier. The SYSTEM identifier is system-specific information that enables the entity manager of an XML system to locate the file, memory location, or pointer within a file where the entity can be found. It should also be noted that a system identifier could be an invocation of a program that controls access to an entity that is being identified. Thus, they are not registered items. In many cases, SYSTEM identifiers are also URIs. However, in these cases, the URI is still only used for system-specific information. In the case where a PUBLIC Identifier is also a URI, it is possible for the SYSTEM Identifier to contain the same URI but this behavior is not recommended unless its side effects are well known and understood to not cause any unacceptable harm.
publicid——包含DOCTYPE声明或任何其他外部引用的XML文档可以通过公共标识符和系统标识符标识该引用。系统标识符是特定于系统的信息，它使XML系统的实体管理器能够在可以找到实体的文件中定位文件、内存位置或指针。还应注意，系统标识符可以是对程序的调用，该程序控制对被标识实体的访问。因此，它们不是登记物品。在许多情况下，系统标识符也是URI。但是，在这些情况下，URI仍然仅用于系统特定的信息。在公共标识符也是URI的情况下，系统标识符可能包含相同的URI，但不推荐这种行为，除非其副作用是众所周知的，并且被理解为不会造成任何不可接受的伤害。
A PUBLIC identifier is a name that is intended to be meaningful across systems and different user environments. Typically, it will be a name that has a registered owner associated with it, so that public identifiers will be guaranteed unique and no two entities will have the same public identifier. In practice, PUBLIC identifiers are typically Formal Public Identifiers [ISO.8879.1986] but they are not restricted to just that set. As said in [RFC3151]:
公共标识符是一个在系统和不同用户环境中有意义的名称。通常，它将是一个具有与之关联的注册所有者的名称，以便保证公共标识符是唯一的，并且没有两个实体具有相同的公共标识符。实际上，公共标识符通常是正式的公共标识符[ISO.8879.1986]，但它们并不局限于该集合。如[RFC3151]所述：
"Any string which consists only of the public identifier characters (defined by Production 13 of Extensible Markup Language (XML) 1.0 Second Edition) is a legal public identifier."
“任何仅由公共标识符字符（由可扩展标记语言（XML）1.0第二版的产品13定义）组成的字符串都是合法的公共标识符。”
Therefore, it is legal for a PUBLIC identifier to be a URN if it adheres to the character set restrictions.
因此，如果公共标识符遵守字符集限制，则将其作为URN是合法的。
Thus, the identifier registered along with a DTD is its PUBLIC identifier. The only restriction being that it must adhere to the character set restrictions. In the case where the registrant does not provide one, the IANA will assign one of the form 'urn:ietf:params:xml:pi:<id>'. Registrants are encouraged to investigate RFC 3151 [RFC3151] as a recommended method for minting a URN that can also be represented as an FPI.
因此，与DTD一起注册的标识符是其公共标识符。唯一的限制是它必须遵守字符集限制。在注册人未提供的情况下，IANA将指定“urn:ietf:params:xml:pi:<id>”形式之一。鼓励注册人调查RFC 3151[RFC3151]作为制作瓮的推荐方法，该瓮也可以表示为FPI。
ns -- XML Namespaces [W3C.REC-xml-names] are named by a URI. They have no real, machine-parseable representation. Thus, the registered document will be either the specification or a reference to it. In the case where a URI is not provided by the registrant, the IANA will assign a URN of the form 'urn:ietf:params:xml:ns:<id> which will be the XML Namespace's name.
ns—XML名称空间[W3C.REC XML名称]由URI命名。它们没有真正的、机器可解析的表示。因此，注册文件将是规范或其参考。在注册人未提供URI的情况下，IANA将分配一个格式为“URN:ietf:params:xml:ns:<id>的URN，该格式将是xml命名空间的名称。
schema -- XML Schemas [W3C.REC-xmlschema-1] are also identified by a URI but their contents are machine parseable. The IANA registered document will be the XML Schema file. The URN the IANA assigns can be used as the URI for the schema and is of the form 'urn:ietf:params:xml:schema:<id>'.
模式——XML模式[W3C.REC-xmlschema-1]也由URI标识，但其内容是可由机器解析的。IANA注册的文档将是XML模式文件。IANA分配的URN可用作架构的URI，格式为“URN:ietf:params:xml:schema:<id>”。
rdfschema -- The Resource Description Format (RDF) [W3C.CR-rdf-schema] is an XML serialization of a connected graph based data model used for metadata expression. RDF makes use of schemas for RDF that express grammars about relationships between URIs. These grammars are identified by URIs. The URN assigned by the IANA can be used as the identifying URI and is of the form 'urn:ietf:params:xml:rdfschema:<id>'.
rdfschema——资源描述格式（ResourceDescriptionFormat，RDF）[W3C.CR RDF模式]是用于元数据表达式的基于连接图的数据模型的XML序列化。RDF使用RDF的模式来表示URI之间关系的语法。这些语法由URI标识。IANA分配的URN可用作标识URI，其形式为“URN:ietf:params:xml:rdfschema:<id>”。
Until the IANA requests or implements an automated process for the registration of these elements, any specifications must make that request part of the IANA considerations section of their respective documents. That request must be in the form of the following template:
在IANA请求或实施这些要素注册的自动化流程之前，任何规范都必须使该请求成为其各自文档IANA注意事项部分的一部分。该请求必须采用以下模板的形式：
URI The URI or PUBLIC identifier that identifies the XML component. If the registrant is requesting that the IANA assign a URI then this field should be specified as "please assign".
URI标识XML组件的URI或公共标识符。如果注册人请求IANA分配URI，则该字段应指定为“请分配”。
Registrant Contact The individual/organization that is the registration contact for the component being registered. Ideally, this will be the name and pertinent physical and network contact information. In the case of IETF developed standards, the Registrant will be the IESG.
注册人联系作为注册组件的注册联系人的个人/组织。理想情况下，这将是姓名以及相关的物理和网络联系信息。如果是IETF制定的标准，注册人将是IESG。
XML The exact XML to be stored in the registry. Unless the beginning and end of the file is obvious, the document should use the text "BEGIN" to mark the beginning of the file and "END" to mark the end of the file. The IANA will insert any text between those two strings (minus any page breaks and RFC formatting inserted by the RFC Editor) into the file kept in the repository.
XML要存储在注册表中的确切XML。除非文件的开头和结尾很明显，否则文档应使用文本“开始”标记文件的开头，“结束”标记文件的结尾。IANA将把这两个字符串之间的任何文本（减去RFC编辑器插入的任何分页符和RFC格式）插入到存储库中保存的文件中。
The information maintained by the IANA will be authoritative and will be a target for attack. In some cases, such as XML Schema and DTDs, the content maintained by the IANA may be directly input into software. Thus, extra care should be taken by the IANA to maintain the security precautions required for an important reference location for the Internet.
IANA维护的信息具有权威性，将成为攻击目标。在某些情况下，如XML模式和DTD，IANA维护的内容可以直接输入到软件中。因此，IANA应特别注意维护互联网重要参考位置所需的安全预防措施。
Beyond this concern, there are no other security considerations not already found with any other IANA registry.
除此之外，任何其他IANA注册中心都没有其他安全注意事项。
This document seeks to create a rather large registry for which the IANA (at the direction of the IESG) will be primarily responsible. The amount of effort required to maintain this registry is not insignificant and the policies and procedures surrounding any approval process are non-trivial. The registry is on a First Come First Served basis, but a Specification is Required. Once the IETF has some experience with this registry, these policies may change.
本文件旨在创建一个相当大的注册中心，IANA（在IESG的指导下）将主要负责该注册中心。维护此注册表所需的工作量并非微不足道，围绕任何批准流程的政策和程序也并非微不足道。注册表是以先到先得的方式提供的，但需要一个规范。一旦IETF对该注册表有了一些经验，这些策略可能会改变。
RFC 3553 [RFC3553] specifies that any new registry requiring a name, to be assigned below the 'urn:ietf:params' namespace and must specify the structure of that space in template form. The IANA has created and will maintain this new sub-namespace:
RFC 3553[RFC3553]指定需要在“urn:ietf:params”命名空间下分配名称的任何新注册表，并且必须以模板形式指定该空间的结构。IANA已创建并将维护此新子命名空间：
Registry-name: xml
注册表名：xml
Specification: This document contains the registry specification. The namespace is organized with one sub-namespace which is the <id>.
规范：此文档包含注册表规范。名称空间由一个子名称空间组织，该子名称空间是<id>。
Repository: To be assigned according to the guidelines found above.
存储库：根据上述指南进行分配。
Index value: The class name
索引值：类名
[ISO.8879.1986] International Organization for Standardization, "Information processing - Text and office systems - Standard generalized markup language (SGML)", ISO Standard 8879, 1986.
[ISO.8879.1986]国际标准化组织，“信息处理-文本和办公系统-标准通用标记语言（SGML）”，ISO标准8879，1986。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RFC2396]Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。
[RFC3151] Walsh, N., Cowan, J. and P. Grosso, "A URN Namespace for Public Identifiers", RFC 3151, August 2001.
[RFC3151]Walsh，N.，Cowan，J.和P.Grosso，“公共标识符的URN名称空间”，RFC 31511901年8月。
[RFC3553] Mealling, M., Masinter, L., Hardie, T. and G. Klyne, "An IETF URN Sub-namespace for Registered Protocol Parameters", BCP 73, RFC 3553, June 2003.
[RFC3553]Mealling，M.，Masinter，L.，Hardie，T.和G.Klyne，“注册协议参数的IETF URN子命名空间”，BCP 73，RFC 3553，2003年6月。
[W3C.CR-rdf-schema] Brickley, D. and R. Guha, "Resource Description Framework (RDF) Schema Specification 1.0", W3C CR-rdf-schema, March 2000, <http://www.w3.org/TR/2000/CR-rdf-schema-20000327>.
[W3C.CR rdf模式]Brickley，D.和R.Guha，“资源描述框架（rdf）模式规范1.0”，W3C CR rdf模式，2000年3月<http://www.w3.org/TR/2000/CR-rdf-schema-20000327>.
[W3C.REC-xml] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler, "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, October 2000, <http://www.w3.org/TR/REC-xml>.
[W3C.REC xml]Bray，T.，Paoli，J.，Sperberg McQueen，C.和E.Maler，“可扩展标记语言（xml）1.0（第二版）”，W3C REC xml，2000年10月<http://www.w3.org/TR/REC-xml>.
[W3C.REC-xml-names] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", W3C REC-xml-names, January 1999, <http://www.w3.org/TR/REC-xml-names>.
[W3C.REC xml名称]Bray，T.，Hollander，D.和A.Layman，“xml中的名称空间”，W3C REC xml名称，1999年1月<http://www.w3.org/TR/REC-xml-names>.
[W3C.REC-xmlschema-1] Thompson, H., Beech, D., Maloney, M. and N. Mendelsohn, "XML Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001, <http://www.w3.org/TR/xmlschema-1/>.
[W3C.REC-xmlschema-1]汤普森，H.，比奇，D.，马洛尼，M.和N.门德尔松，“XML模式第1部分：结构”，W3C REC-xmlschema-1，2001年5月<http://www.w3.org/TR/xmlschema-1/>.
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
Michael Mealling VeriSign, Inc. Mountain View, CA USA
美国加利福尼亚州山景城Michael Mealling VeriSign公司
EMail: michael@verisignlabs.com
URI: http://www.research.verisignlabs.com
EMail: michael@verisignlabs.com
URI: http://www.research.verisignlabs.com
Copyright (C) The Internet Society (2004). All Rights Reserved.
版权所有（C）互联网协会（2004年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。