Network Working Group J. Goodwin
Request for Comments: 5141 H. Apel
Category: Informational ISO
March 2008
Network Working Group J. Goodwin
Request for Comments: 5141 H. Apel
Category: Informational ISO
March 2008
A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)
国际标准化组织（ISO）的统一资源名称（URN）命名空间
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Abstract
摘要
This document describes a Uniform Resource Name Namespace Identification (URN NID) for the International Organization for Standardization (ISO). This URN NID is intended for use for the identification of persistent resources published by the ISO standards body (including documents, document metadata, extracted resources such as standard schemata and standard value sets, and other resources).
本文档描述了国际标准化组织（ISO）的统一资源名称空间标识（URN NID）。此URN NID用于标识ISO标准机构发布的持久性资源（包括文档、文档元数据、提取的资源，如标准模式和标准值集，以及其他资源）。
Table of Contents
目录
1. Introduction ....................................................2
2. Specification Template ..........................................4
2.1. Namespace ID ...............................................4
2.2. Registration Information ...................................4
2.3. Declared Registrant of the Namespace .......................4
2.4. Declaration of Structure ...................................4
2.4.1. Definition ..........................................4
2.4.2. Examples ...........................................12
2.5. Relevant Ancillary Documentation ..........................15
2.6. Identifier Uniqueness Considerations ......................15
2.7. Identifier Persistence Considerations .....................15
2.8. Process for Identifier Resolution .........................16
2.9. Rules for Lexical Equivalence .............................16
2.10. Conformance with URN Syntax ..............................17
2.11. Validation Mechanism .....................................17
2.12. Scope ....................................................17
3. Namespace Considerations .......................................17
4. Community Considerations .......................................18
5. IANA Considerations ............................................20
6. Security Considerations ........................................20
7. References .....................................................21
7.1. Normative References ......................................21
7.2. Informative References ....................................21
Appendix A. Alternative Naming Schemes ............................23
Appendix B. ABNF Definition of Namespace ID = "iso"
(Informative) .........................................24
1. Introduction ....................................................2
2. Specification Template ..........................................4
2.1. Namespace ID ...............................................4
2.2. Registration Information ...................................4
2.3. Declared Registrant of the Namespace .......................4
2.4. Declaration of Structure ...................................4
2.4.1. Definition ..........................................4
2.4.2. Examples ...........................................12
2.5. Relevant Ancillary Documentation ..........................15
2.6. Identifier Uniqueness Considerations ......................15
2.7. Identifier Persistence Considerations .....................15
2.8. Process for Identifier Resolution .........................16
2.9. Rules for Lexical Equivalence .............................16
2.10. Conformance with URN Syntax ..............................17
2.11. Validation Mechanism .....................................17
2.12. Scope ....................................................17
3. Namespace Considerations .......................................17
4. Community Considerations .......................................18
5. IANA Considerations ............................................20
6. Security Considerations ........................................20
7. References .....................................................21
7.1. Normative References ......................................21
7.2. Informative References ....................................21
Appendix A. Alternative Naming Schemes ............................23
Appendix B. ABNF Definition of Namespace ID = "iso"
(Informative) .........................................24
The International Organization for Standardization (ISO) was created by international agreement in 1947. ISO is a network of the national standards institutes of many countries, on the basis of one member per country, with a Central Secretariat in Geneva, Switzerland, that coordinates the system. ISO acts as a bridging organization in which a consensus can be reached on solutions that meet both the requirements of business and the broader needs of society, such as the needs of stakeholder groups like consumers and users.
国际标准化组织（ISO）于1947年根据国际协议成立。ISO是一个由许多国家的国家标准协会组成的网络，每个国家有一名成员，在瑞士日内瓦设有一个中央秘书处，负责协调该系统。ISO充当了一个桥梁组织，在这个组织中，可以就同时满足业务需求和更广泛的社会需求（如消费者和用户等利益相关者群体的需求）的解决方案达成共识。
Further information is provided at http://www.iso.org/iso/about.htm.
进一步资料载于http://www.iso.org/iso/about.htm.
The core mission of ISO is to develop technical standards constituting technical agreements that provide the framework for compatible technology worldwide. ISO standards contribute to making the development, manufacturing, and supply of products and services more efficient, safer, and cleaner. They make trade between countries easier and fairer.
ISO的核心任务是制定技术标准，构成技术协议，为全球兼容技术提供框架。ISO标准有助于使产品和服务的开发、制造和供应更加高效、安全和清洁。它们使国与国之间的贸易更加容易和公平。
Every participating ISO member institute (full members) has the right to take part in the development of any standard that it judges to be important to its country's economy. No matter what the size or strength of that economy, each participating member in ISO has one vote. ISO's activities are thus carried out in a democratic framework where each country is on an equal footing to influence the direction of ISO's work at the strategic level, as well as the technical content of its individual standards. Although the ISO standards are voluntary, the fact that they are developed in response to market demand, and are based on consensus among the interested parties, ensures widespread applicability of the standards. Consensus, like technology, evolves and ISO takes account of both evolving technology and evolving interests by requiring a review of its standards at least every five years to decide whether they should be maintained, updated, or withdrawn.
每个参与的ISO成员机构（正式成员）都有权参与其认为对其国家经济重要的任何标准的制定。无论该经济体的规模或实力如何，ISO的每个参与成员都有一票。因此，ISO的活动是在一个民主的框架内进行的，在这个框架内，每个国家都平等地影响ISO在战略层面的工作方向，以及其各自标准的技术内容。尽管ISO标准是自愿性的，但它们是根据市场需求制定的，并且基于相关方之间的共识，这一事实确保了标准的广泛适用性。与技术一样，共识也在不断发展，ISO考虑到不断发展的技术和不断发展的利益，要求至少每五年对其标准进行一次审查，以决定是否应保持、更新或撤销这些标准。
ISO publishes International Standards and other technical specifications that are cited in the definitions of required or expected practices in many industries in many nations. These specifications contain dictionaries of standard terms, catalogues of reference values, definitions of formal languages, formal schemata for information capture and exchange, specifications for standard practices, and other information resources of general use to international trade and industry. ISO wishes to create and manage globally unique, persistent, location-independent identifiers for these resources.
ISO发布了国际标准和其他技术规范，这些标准和规范在许多国家的许多行业的要求或预期实践的定义中引用。这些规范包括标准术语词典、参考值目录、正式语言定义、信息捕获和交换的正式模式、标准实践规范以及国际贸易和工业普遍使用的其他信息资源。ISO希望为这些资源创建和管理全局唯一、持久、位置独立的标识符。
This specification defines the syntax for URNs that identify documents developed by the International Organization for Standardization (ISO) in accordance with the standards development procedures defined in the ISO/IEC Directives, Part 1 [ISODIR-1] and the ISO supplement [ISODIR-S] and processed by the ISO Central Secretariat. The syntax extends to identify document metadata and resources related to these documents or otherwise associated with them. It does not extend to products derived from these documents and published by ISO (e.g., handbooks, compendia) or documents at or below the Technical Committee level. Revisions of this specification may define syntax for URNs in this namespace that identify other ISO objects, when the ISO community defines a requirement for such identifiers.
本规范定义了URN的语法，这些URN标识了国际标准化组织（ISO）根据ISO/IEC指令第1部分[ISODIR-1]和ISO补充[ISODIR-S]中定义的标准开发程序开发的文件，并由ISO中央秘书处处理。语法扩展以标识与这些文档相关或与之关联的文档元数据和资源。它不适用于从这些文件中衍生出来并由ISO发布的产品（如手册、简编）或技术委员会级别或以下的文件。当ISO团体定义了对此类标识符的要求时，本规范的修订版可能会定义此命名空间中标识其他ISO对象的URN的语法。
"iso"
“iso”
Version 2.1 Date: 2007-12-13
版本2.1日期：2007-12-13
J. Goodwin ISO Central Secretariat International Organization for Standardization (ISO) Case Postale 56 CH-1211 Geneva 20 Switzerland
J.Goodwin ISO中央秘书处国际标准化组织（ISO）案例邮递56 CH-1211瑞士日内瓦20
E-mail: goodwin@iso.org
电邮：goodwin@iso.org
The Namespace Specific Strings (NSSs) of all URNs assigned by ISO will conform to the syntax defined in Section 2.2 of [RFC2141].
ISO分配的所有URN的命名空间特定字符串（NSS）将符合[RFC2141]第2.2节中定义的语法。
The NSS has the following ABNF [RFC5234] specification:
NSS具有以下ABNF[RFC5234]规格：
NSS = std-nss
NSS = std-nss
All URNs conforming to this specification begin the NSS with the prefix "std:" to denote the restriction to documents developed by the ISO standards development procedures as defined in the ISO/IEC Directives, Part 1 [ISODIR-1] and the ISO Supplement [ISODIR-S]. Prefixes that identify ISO objects of other kinds may be defined in future revisions of this specification.
符合本规范的所有URN在NSS开头加上前缀“std:”表示对ISO/IEC指令第1部分[ISODIR-1]和ISO补充[ISODIR-S]中定义的ISO标准开发程序开发的文件的限制。识别其他类型ISO对象的前缀可在本规范的未来版本中定义。
std-nss = "std:" docidentifier *supplement *docelement
[addition]
std-nss = "std:" docidentifier *supplement *docelement
[addition]
The prefix "std:" distinguishes an <std-nss>. An <std-nss>
identifies the ISO document that is designated by the
<docidentifier>, as extended or modified by any identified
<supplement>. (An <std-nss> that identifies all parts of a
multipart ISO document is a special case as described under the
The prefix "std:" distinguishes an <std-nss>. An <std-nss>
identifies the ISO document that is designated by the
<docidentifier>, as extended or modified by any identified
<supplement>. (An <std-nss> that identifies all parts of a
multipart ISO document is a special case as described under the
element <partnumber>.) If the <std-nss> contains an <addition> element, the NSS identifies a resource extracted from the ISO document or otherwise associated with it (see below).
元素<partnumber>）如果<std nss>包含<addition>元素，则nss标识从ISO文档中提取的资源或与之相关的资源（见下文）。
docidentifier = originator [":" type] ":" docnumber [":" partnumber]
[[":" status] ":" edition]
[":" docversion] [":" language]
docidentifier = originator [":" type] ":" docnumber [":" partnumber]
[[":" status] ":" edition]
[":" docversion] [":" language]
<docidentifier> provides the complete identification of an ISO document. Each of its component elements is described below.
<docidentifier>提供ISO文档的完整标识。其每个组成元素如下所述。
originator = "iso" / "iso-iec" / "iso-cie" / "iso-astm" /
"iso-ieee" / "iec"
originator = "iso" / "iso-iec" / "iso-cie" / "iso-astm" /
"iso-ieee" / "iec"
<originator> is the organization (usually an international body) from which a document emanates.
<originator>是文件产生的组织（通常是一个国际机构）。
Current values:
当前值：
iso = International Organization for Standardization
iso=国际标准化组织
iec = International Electrotechnical Commission (IEC), or Commission Electrotechnique Internationale
iec=国际电工委员会（iec）或国际电工委员会
iso-iec = jointly developed by ISO and IEC
iso-iec = jointly developed by ISO and IEC
iso-cie = jointly developed by ISO and the Commission Internationale d'Eclairage (CIE)
iso cie=由iso和国际航空委员会（cie）联合开发
iso-astm = jointly developed by ISO and the American Society for Testing and Materials (ASTM) International
iso astm=由iso和美国材料试验协会（astm）国际联合开发
iso-ieee = jointly developed by ISO and the Institute for Electrical and Electronics Engineers (IEEE)
iso ieee=由iso和电气与电子工程师协会（ieee）联合开发
Revisions of this specification may define additional values.
本规范的修订版可定义附加值。
type = "data" / "guide" / "isp" / "iwa" /
"pas" / "r" / "tr" / "ts" / "tta"
type = "data" / "guide" / "isp" / "iwa" /
"pas" / "r" / "tr" / "ts" / "tta"
<type> designates the ISO deliverable type. If the <type> element is not present, the classification is "international standard". Other current values:
<type>指定ISO可交付成果类型。如果<type>元素不存在，则分类为“国际标准”。其他当前值：
data = Data (document type no longer published)
数据=数据（不再发布文档类型）
guide = Guide
guide = Guide
isp = International Standardized Profile
isp = International Standardized Profile
iwa = International Workshop Agreement
iwa = International Workshop Agreement
pas = Publicly Available Specification
pas = Publicly Available Specification
r = Recommendation (document type no longer published)
r=建议（不再发布的文档类型）
tr = Technical Report
tr = Technical Report
ts = Technical Specification
ts = Technical Specification
tta = Technology Trends Assessment
tta = Technology Trends Assessment
docnumber = DIGITS
docnumber = DIGITS
<docnumber> is the reference number assigned to the document by ISO and/or IEC. An ISO document may comprise a single document, or two or more separate parts each of which is identified by <partnumber>.
<docnumber>是ISO和/或IEC分配给文件的参考号。ISO文件可以包括单个文件，或两个或多个单独的部分，每个部分由<partnumber>标识。
partnumber = "-" 1*( DIGIT / ALPHA / "-" )
partnumber = "-" 1*( DIGIT / ALPHA / "-" )
<partnumber> is the reference number that identifies a part of a multipart standard.
<partnumber>是标识多部分标准一部分的参考号。
Where it is required to refer to a multipart ISO document in its entirety, this can be designated by omitting the <partnumber> element. However, this precludes the possibility of using any further elements except <addition>.
如果需要完整地引用多部分ISO文件，可以通过省略<partnumber>元素来指定。但是，这排除了使用除<addition>之外的任何其他元素的可能性。
NOTE: The option to refer to a multipart ISO document by omitting the <partnumber> element has been included to align with the provision in the ISO/IEC Directives, Part 2, 2004 [ISODIR-2] subclause 6.2.2 of making an undated reference to all parts of an ISO document. It is only permissible to use this option where the URN is referring to a multipart ISO document in its entirety. Since the use of this option precludes the designation of the elements <status> and <edition>, it is implicit that the URN needs to remain valid irrespective of any future changes to the multipart document (see the rules for undated references given in the ISO/IEC Directives, Part 2, 2004 [ISODIR-2] subclause 6.6.7.5.2). This shall be taken into consideration in the use (and maintenance) of any URN specification employing this option.
注：通过省略<partnumber>元素引用多部分ISO文件的选项已包括在内，以符合ISO/IEC指令2004年第2部分[ISODIR-2]第6.2.2款中关于引用ISO文件所有部分的未注明日期的规定。仅允许在URN完整引用多部分ISO文档时使用此选项。由于该选项的使用排除了元素<status>和<edition>的指定，因此无论将来对多部分文件进行任何更改，URN都必须保持有效（参见ISO/IEC指令第2部分2004[ISODIR-2]第6.6.7.5.2子条款中未注明日期的参考规则）。在使用（和维护）任何采用该选项的URN规范时，应考虑到这一点。
NOTE: In the case where the multipart document comprises different types of ISO deliverable, the <type> of the core part (usually part 1) applies. See the example "Reference to a resource related to all parts of a multipart document".
注：如果多部分文件包含不同类型的ISO可交付成果，则核心部分（通常为第1部分）的<type>。请参阅示例“引用与多部分文档的所有部分相关的资源”。
Except for the case where it is required to refer to a multipart document in its entirety, the element <partnumber> is required if the identified resource is a part of an ISO document. Otherwise, this element is not used.
除了需要完整引用多部分文档的情况外，如果标识的资源是ISO文档的一部分，则需要元素<partnumber>。否则，不使用此元素。
status = ( "draft" / "cancelled" ) / stage
status = ( "draft" / "cancelled" ) / stage
<status> indicates the publication status of the document. When the <status> element is not present, the NSS refers to a published document. Other values:
<status>指示文档的发布状态。当<status>元素不存在时，NSS引用已发布的文档。其他值：
draft = document that has not yet been accepted for publication by international ballot
草稿=尚未通过国际投票接受出版的文件
cancelled = document that has been deleted or withdrawn
已取消=已删除或撤回的文档
stage = "stage-" stagecode ["." iteration]
stage=“stage-”stagecode[“”迭代]
<stage> indicates the stage code and iteration of the document.
<stage>表示文档的阶段代码和迭代。
stagecode = DIGIT DIGIT "." DIGIT DIGIT
stagecode=数字“.”数字
<stagecode> is the harmonized stage code in accordance with ISO Guide 69:1999, "Harmonized Stage Code system (Edition 2) -- Principles and guidelines for use" [ISOGUIDE69].
<stagecode>是符合ISO指南69:1999“协调阶段代码系统（第2版）-使用原则和指南”[ISOGUIDE69]的协调阶段代码。
iteration = "v" DIGITS
迭代=“v”位
<iteration> is a sequential number that refers to a specific iteration of the project's lifecycle through the designated stage.
<iteration>是一个序列号，表示项目生命周期中通过指定阶段的特定迭代。
If no <iteration> is specified, the reference is to the highest iteration available for the specified stagecode.
如果未指定<iteration>，则引用指定的stagecode可用的最高迭代。
NOTE: In the ISO Central Secretariat project management database, the <iteration> is referred to as the "project version".
注：在ISO中央秘书处项目管理数据库中，<迭代>被称为“项目版本”。
edition = "ed-" DIGITS
edition=“ed-”数字
<edition> designates a specific edition of the document. (DIGITS is the (sequential) edition number.) If no <edition> is specified, the NSS refers to the latest edition.
<edition>指定文档的特定版本。（数字是（顺序）版本号。）如果未指定<edition>，则NSS指最新版本。
docversion = "v" (simpleversion / isoversion)
docversion=“v”（简化版本/isoversion）
simpleversion = DIGITS
simpleversion = DIGITS
<docversion> designates the version number of a document's <edition>. It is altered by correction (corrected version; Technical Corrigendum) or amendment (Amendment; Addendum) and is distinct from a revision, which changes the edition number.
<docversion>指定文档的<edition>版本号。它通过更正（更正版本；技术勘误）或修订（修订；附录）进行更改，与更改版本号的修订不同。
In the <simpleversion>, the first version published is 1, and each subsequent correction or amendment increases the version number by 1.
在<simpleversion>中，发布的第一个版本是1，随后的每个更正或修订都会将版本号增加1。
If no <docversion> is specified, the reference is to the highest version number available for the denoted <edition>.
如果未指定<docversion>，则参考所示<edition>的最高版本号。
Current values of <simpleversion>:
<simpleversion>的当前值：
1 - first version published
1-第一版已出版
2 - corrected version published
2-已发布的更正版本
isoversion = baseversion *includedsuppl
isoversion=基本版本*包括支持
baseversion = DIGITS
baseversion = DIGITS
includedsuppl = "-" suppltype supplnumber [ "." supplversion ]
includedsuppl=“-”suppltype supplnumber[”“supplversion]
An <isoversion> can be linked to a simpleversion by defining an existing simpleversion as baseversion and listing all the <supplement> elements (corrections and amendments) incorporated into that version.
通过将现有simpleversion定义为baseversion并列出并入该版本的所有<supplement>元素（更正和修订），可以将<isoversion>链接到simpleversion。
Examples for the <isoversion> (internal ISO version) scheme:
<isoversion>（内部ISO版本）方案示例：
1 = first version of standard
1 = first version of standard
1-amd1.v1 = first version of standard incorporating first version of Amendment 1
1-amd1.v1=包含修订件1第一版的标准第一版
1-amd1.v1-amd2.v1 = first version of standard incorporating first version of Amendment 1 and first version of Amendment 2
1-amd1.v1-amd2.v1=包含修订件1第一版和修订件2第一版的标准第一版
1-amd1.v2-amd2.v1-amd3 = first version of standard incorporating corrected version of Amendment 1, first version of Amendment 2, and highest version of Amendment 3
1-amd1.v2-amd2.v1-amd3=标准的第一版，包括修正案1的修正版、修正案2的第一版和修正案3的最高版本
1-cor3 = first version of standard incorporating highest version of Technical Corrigendum 3
1-cor3=包含技术勘误表3最高版本的标准第一版本
1-amd1-cor3 = first version of standard incorporating highest version of Amendment 1 and highest version of Technical Corrigendum 3
1-amd1-cor3=包含最高版本修改件1和最高版本技术勘误表3的标准第一版
language = monolingual / bilingual / trilingual
language = monolingual / bilingual / trilingual
monolingual = "en" / "fr" / "ru" / "es" / "ar"
monolingual = "en" / "fr" / "ru" / "es" / "ar"
bilingual = "en,fr" / "en,ru" / "fr,ru"
bilingual = "en,fr" / "en,ru" / "fr,ru"
trilingual = "en,fr,ru"
三语=“英语、法语、俄语”
<language> designates the official ISO language(s), or the language of an official translation, in which the document (object) is processed and published by ISO (excluding languages that constitute only specific elements of the content). The value is one or more alpha-2 codes, each of which designates a language, as specified in ISO 639-1 [ISO639-1]. If no language element is specified, <en> is assumed.
<language>指定ISO处理和发布文档（对象）时使用的官方ISO语言或官方翻译语言（不包括仅构成内容特定元素的语言）。该值是一个或多个alpha-2代码，每个代码指定一种语言，如ISO 639-1[ISO639-1]所规定。如果未指定语言元素，则假定为<en>。
NOTE: Although [ISO639-1] recommends that language codes be written in lowercase, this ABNF definition allows the use of uppercase language codes because in ABNF [RFC5234], terminal symbols defined as literal strings are explicitly case-insensitive. This case distinction does not carry any meaning (see Section 2.9) and it is recommended to use language codes in lowercase. For additional information about the usage of language tags in information objects, see [RFC4646].
注：尽管[ISO639-1]建议语言代码使用小写，但该ABNF定义允许使用大写语言代码，因为在ABNF[RFC5234]中，定义为文字字符串的终端符号明确不区分大小写。这种区分不具有任何意义（见第2.9节），建议使用小写语言代码。有关在信息对象中使用语言标记的更多信息，请参阅[RFC4646]。
supplement = ":" suppltype ":" supplnumber
[":" supplversion ] [":" language ]
supplement = ":" suppltype ":" supplnumber
[":" supplversion ] [":" language ]
suppltype = "amd" / "cor" / "add"
suppltype = "amd" / "cor" / "add"
supplnumber = DIGITS
supplnumber = DIGITS
supplversion = "v" DIGITS
supplersion=“v”位
<supplement> designates a technical alteration of or addition to an ISO standard that does not result in a new <edition> or <version>. Each <supplement> may be one of the three types, designated by <suppltype>:
<supplement>指定ISO标准的技术变更或增补，不会产生新的<edition>或<version>。每个<supplement>可以是三种类型中的一种，由<suppltype>指定：
amd = Amendment -- a document that alters and/or adds to previously agreed upon technical provisions in an existing ISO document; an amendment is subject to acceptance by ballot in accordance with the ISO/IEC Directives, Part 1, 2004 [ISODIR-1] subclause 2.10.3
amd=修订——修改和/或增加现有ISO文件中先前商定的技术条款的文件；根据ISO/IEC指令，第1部分，2004[ISODIR-1]第2.10.3款的规定，修改须以投票方式接受
cor = Technical Corrigendum -- a document that corrects a technical error or ambiguity, or updates the ISO document in such a way that the modification has no effect on the technical normative elements; a Technical Corrigendum is not balloted -- see the ISO/IEC Directives, Part 1, 2004 [ISODIR-1] subclause 2.10.2
cor=技术勘误表——纠正技术错误或歧义的文件，或以修改不影响技术规范要素的方式更新ISO文件；技术勘误表未经投票表决——见ISO/IEC指令，第1部分，2004[ISODIR-1]第2.10.2款
add = Addendum -- (document type no longer published) Addenda were documents that changed (by correction, addition, or deletion) the technical requirements of an ISO document; an addendum was subject to acceptance by ballot in accordance with the ISO/IEC Directives, Part 1. (Addenda are included in this RFC because some of them are still valid.)
add=附录--（不再发布的文件类型）附录是指改变（通过更正、添加或删除）ISO文件技术要求的文件；附录须根据ISO/IEC指令第1部分以投票方式接受。（本RFC中包括附录，因为其中一些附录仍然有效。）
Supplements are numbered consecutively per ISO document, and within each supplement type.
每个ISO文件和每个补充类型内的补充都连续编号。
<supplnumber> identifies the number of the supplement.
<supplnumber>标识补充资料的编号。
<supplversion> designates the version of a published supplement. At present, only two versions are used in practice: when a supplement is published, it is version 1. If that supplement is subsequently corrected by issuing a corrected version, as designated by the term "Corrected" on the cover page together with a date, the corrected version is version 2.
<supplversion>指定已发布补充的版本。目前，在实践中只使用了两个版本：当增刊出版时，它是第1版。如果随后通过发布封面上“更正”一词和日期指定的更正版本对该补充文件进行了更正，则更正版本为第2版。
The language of a supplement can be different from that of the document. For example, a supplement may apply to only one of the languages of a bilingual document. For such cases, the language of a supplement can be identified using the <language> element defined above. The interpretation is the same, except that it applies only to the supplement.
补充文件的语言可以与文件的语言不同。例如，补编可能只适用于双语文件的一种语言。在这种情况下，可以使用上文定义的<language>元素来识别补遗的语言。解释是相同的，只是它只适用于补编。
docelement = ":" ( "clause" / "figure" / "table" / "term" ) ":"
elementnumber / elementrange
*( "," elementnumber / elementrange )
docelement = ":" ( "clause" / "figure" / "table" / "term" ) ":"
elementnumber / elementrange
*( "," elementnumber / elementrange )
elementnumber = ( ALPHA / DIGITS ) *( "." DIGITS )
elementnumber = ( ALPHA / DIGITS ) *( "." DIGITS )
elementrange = elementnumber "-" elementnumber
elementrange=elementnumber“-”elementnumber
<docelement> identifies one or more numbered subdivisions of a document. Types of numbered subdivision are specified in the ISO/ IEC Directives, Part 2 [ISODIR-2]. This RFC currently specifies forms for reference to clauses, figures, tables, and terms only. It does not provide for reference to subfigures. Revisions of this specification may define additional values.
<docelement>标识文档的一个或多个编号的子部分。ISO/IEC指令第2部分[ISODIR-2]规定了编号细分的类型。本RFC目前指定的表格仅供参考条款、图表、表格和术语。它不提供对子图形的引用。本规范的修订版可定义附加值。
<clause> represents the selection of one or more clauses or subclauses of the document. <figure> represents the selection of one or more figures of the document. <table> represents the selection of one or more tables of the document. <term> represents the selection of one or more terms of the document.
<clause>表示选择文档的一个或多个子句或子子句<figure>表示选择文档的一个或多个图<table>表示选择文档的一个或多个表<term>表示选择文档的一个或多个术语。
<elementnumber> designates a numbered subdivision in a document, where the type of subdivision is identified by the literal "clause", "figure", "table", or "term". When the first character of <elementnumber> is a digit, the reference is to the subdivision designated by that digit string and by any additional digit strings separated by periods. When the first character of <elementnumber> is alphabetical, the reference is to the corresponding Annex, and to the subdivisions designated by additional digit strings.
<elementnumber>指定文档中的编号细分，其中细分类型由文字“子句”、“图”、“表”或“术语”标识。当<elementnumber>的第一个字符是数字时，引用的是由该数字字符串和由句点分隔的任何附加数字字符串指定的细分。当<elementnumber>的第一个字符按字母顺序排列时，参考相应的附录以及由附加数字字符串指定的细分。
The form <elementnumber> HYPHEN <elementnumber> designates a range of subdivisions, and the form <elementnumber> COMMA <elementnumber> designates a list. A list can contain ranges.
表单<elementnumber>连字符<elementnumber>指定一系列细分，表单<elementnumber>逗号<elementnumber>指定一个列表。列表可以包含范围。
addition = techdefined / isodefined
addition = techdefined / isodefined
techdefined = ":tech" *techelement
techdefined = ":tech" *techelement
techelement = <unspecified>
techelement = <unspecified>
isodefined = <unspecified>
isodefined = <unspecified>
<addition> is an additional element of the NSS intended to identify a representation of an ISO document, an extract from an ISO document, or some related information set, as a resource in its own right.
<addition>是NSS的附加元素，旨在将ISO文档的表示、ISO文档的摘录或某些相关信息集本身识别为资源。
<techdefined> represents an associated or embedded resource defined by the committee that develops or maintains the identified document. All such <addition> elements begin with the prefix ":tech".
<techdefined>表示委员会定义的相关或嵌入式资源，用于开发或维护已识别的文件。所有这些<addition>元素都以前缀“：tech”开头。
<isodefined> represents associated or embedded resources defined by the ISO Central Secretariat. The definition of an <addition> element beginning with any symbol other than <tech> is reserved to the ISO Central Secretariat.
<isodefined>表示ISO中央秘书处定义的相关或嵌入式资源。以<tech>以外的任何符号开头的<addition>元素的定义保留给ISO中央秘书处。
The syntax of the <addition> element is not specified in this RFC. Specific syntax for this element will be specified as needed by the ISO Central Secretariat, or by the individual committee that has the responsibility for developing or maintaining the identified document. It is necessary that these definitions comply with the rules for lexical equivalence specified in Section 2.9 and take into account the process for identifier resolution as discussed in Section 2.8.
此RFC中未指定<addition>元素的语法。ISO中央秘书处或负责编制或维护确定文件的独立委员会将根据需要指定该元素的具体语法。这些定义必须符合第2.9节中规定的词汇等效规则，并考虑第2.8节中讨论的标识符解析过程。
DIGITS = DIGIT *DIGIT
位数=位数*位数
DIGIT = %x30-39 ; 0-9
DIGIT = %x30-39 ; 0-9
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
Basics of the ABNF notation used :
所用ABNF符号的基础：
" " literals (terminal character strings); terms not in quotes are non-terminals
“”文本（终端字符串）；不在引号中的术语是非终结符
/ alternatives
/替代品
[] indicates an optional rule
[]表示可选规则
() indicates a sequence group, used as a single alternative or as a single repeating group
（）表示序列组，用作单个备选方案或单个重复组
<a>*<b> indicates that the following term or group can repeat at
least <a> and at most <b> times; default values are 0 and
infinity, respectively
<a>*<b> indicates that the following term or group can repeat at
least <a> and at most <b> times; default values are 0 and
infinity, respectively
; comment
; 议论
o Language handling:
o 语言处理：
urn:iso:std:iso:9999:-1:ed-1:en
refers to the 1st edition of ISO 9999-1, in English
urn:iso:std:iso:9999:-1:ed-1:en
refers to the 1st edition of ISO 9999-1, in English
urn:iso:std:iso:9999:-1:ed-1:en,fr
refers to the 1st edition of ISO 9999-1, in English/French
(bilingual document)
urn:iso:std:iso:9999:-1:ed-1:en,fr
refers to the 1st edition of ISO 9999-1, in English/French
(bilingual document)
o Originators/document type:
o 发起人/文件类型：
urn:iso:std:iso-iec:tr:9999:-1:ed-1:en
refers to the 1st edition of ISO/IEC TR 9999-1, in English
urn:iso:std:iso-iec:tr:9999:-1:ed-1:en
refers to the 1st edition of ISO/IEC TR 9999-1, in English
o Status:
o 地位：
urn:iso:std:iso-iec:9075:-3:cancelled:ed-2:en
urn:iso:std:iso-iec:9075:-3:stage-95.99:ed-2:en
both refer to the cancelled 2nd edition of ISO/IEC 9075-3, in
English
urn:iso:std:iso-iec:9075:-3:cancelled:ed-2:en
urn:iso:std:iso-iec:9075:-3:stage-95.99:ed-2:en
both refer to the cancelled 2nd edition of ISO/IEC 9075-3, in
English
urn:iso:std:iso-iec:9075:-3:draft:ed-4:en
urn:iso:std:iso-iec:9075:-3:stage-30.60:ed-4:en
both refer to the draft 4th edition of ISO/IEC 9075-3, in English
urn:iso:std:iso-iec:9075:-3:draft:ed-4:en
urn:iso:std:iso-iec:9075:-3:stage-30.60:ed-4:en
both refer to the draft 4th edition of ISO/IEC 9075-3, in English
urn:iso:std:iso:128:-20:en
urn:iso:std:iso:128:-20:stage-90.20:ed-1:en
both refer to the published (90.20 = under 2nd periodic review)
1st edition of ISO 128-20, in English
urn:iso:std:iso:128:-20:en
urn:iso:std:iso:128:-20:stage-90.20:ed-1:en
both refer to the published (90.20 = under 2nd periodic review)
1st edition of ISO 128-20, in English
urn:iso:std:iso:128:-71:cancelled:ed-1:en
urn:iso:std:iso:128:-71:stage-30.98.v2:ed-1:en
both refer to the cancelled (30.98 = project deleted) 1st edition
of ISO 128-71, in English; the second example refers specifically
to the 2nd iteration (projectversion) at stage 30
urn:iso:std:iso:128:-71:cancelled:ed-1:en
urn:iso:std:iso:128:-71:stage-30.98.v2:ed-1:en
both refer to the cancelled (30.98 = project deleted) 1st edition
of ISO 128-71, in English; the second example refers specifically
to the 2nd iteration (projectversion) at stage 30
o Non-numeric part number:
o 非数字零件号：
urn:iso:std:iso:9999:-A02:ed-1:en
refers to the 1st edition of ISO 9999-A02, in English
urn:iso:std:iso:9999:-A02:ed-1:en
refers to the 1st edition of ISO 9999-A02, in English
o Reference to a resource related to all parts of a multipart document:
o 引用与多部分文档的所有部分相关的资源：
urn:iso:std:iso:20022:tech:xsd:camt.001.001.01
refers to a "techdefined" resource (i.e., a resource defined by
the committee that develops or maintains the identified document)
associated with ISO 20022 in its entirety; in this example, the
techdefined part comprises ":xsd:camt.001.001.01"
urn:iso:std:iso:20022:tech:xsd:camt.001.001.01
refers to a "techdefined" resource (i.e., a resource defined by
the committee that develops or maintains the identified document)
associated with ISO 20022 in its entirety; in this example, the
techdefined part comprises ":xsd:camt.001.001.01"
NOTE: At the time of drafting of this schema, ISO 20022 comprises 5 parts: parts 1 and 2 are International Standards; parts 3 to 5 are Technical Specifications. Therefore, the <doctype> "international standard" is used in the URN.
注：在起草本方案时，ISO 20022由5部分组成：第1部分和第2部分为国际标准；第3至5部分为技术规范。因此，URN中使用了<doctype>“国际标准”。
o Docversion handling:
o 文档版本处理：
urn:iso:std:iso:9999:-1:ed-1:v2:en
refers to the corrected English version of the 1st edition of ISO
9999-1
urn:iso:std:iso:9999:-1:ed-1:v2:en
refers to the corrected English version of the 1st edition of ISO
9999-1
urn:iso:std:iso:9999:-1:ed-1:v1-amd1:en
refers to the version comprising the 1st edition of ISO 9999-1,
incorporating the latest version of Amendment 1, in English
urn:iso:std:iso:9999:-1:ed-1:v1-amd1:en
refers to the version comprising the 1st edition of ISO 9999-1,
incorporating the latest version of Amendment 1, in English
urn:iso:std:iso:9999:-1:ed-1:v1:en,fr:amd:1:v2:en
refers to the 2nd version of Amendment 1, in English, which amends
the 1st version of edition 1 of ISO 9999-1, in English/French
(bilingual document)
urn:iso:std:iso:9999:-1:ed-1:v1:en,fr:amd:1:v2:en
refers to the 2nd version of Amendment 1, in English, which amends
the 1st version of edition 1 of ISO 9999-1, in English/French
(bilingual document)
urn:iso:std:iso:9999:-1:ed-1:v1-amd1.v1:en,fr:amd:2:v2:en
(isoversion scheme)
refers to the corrected version of Amendment 2, in English, which
amends the document comprising the 1st version of edition 1 of ISO
9999-1 incorporating the 1st version of Amendment 1, in English/
French (bilingual document)
urn:iso:std:iso:9999:-1:ed-1:v1-amd1.v1:en,fr:amd:2:v2:en
(isoversion scheme)
refers to the corrected version of Amendment 2, in English, which
amends the document comprising the 1st version of edition 1 of ISO
9999-1 incorporating the 1st version of Amendment 1, in English/
French (bilingual document)
urn:iso:std:iso:5817:ed-2:v2:en:cor:1:en
refers to the 1st version of Technical Corrigendum 1, in English,
which amends the corrected version of edition 2 of ISO 5817, in
English
urn:iso:std:iso:5817:ed-2:v2:en:cor:1:en
refers to the 1st version of Technical Corrigendum 1, in English,
which amends the corrected version of edition 2 of ISO 5817, in
English
o Supplement handling:
o 补充处理：
urn:iso:std:iso:9999:-1:ed-2:en:amd:1
refers to Amendment 1 to the 2nd edition of ISO 9999-1, in English
urn:iso:std:iso:9999:-1:ed-2:en:amd:1
refers to Amendment 1 to the 2nd edition of ISO 9999-1, in English
urn:iso:std:iso:9999:-1:ed-2:en:amd:1:v2
refers to the corrected version of Amendment 1 to the 2nd edition
of ISO 9999-1, in English
urn:iso:std:iso:9999:-1:ed-2:en:amd:1:v2
refers to the corrected version of Amendment 1 to the 2nd edition
of ISO 9999-1, in English
urn:iso:std:iso:9999:1:ed-2:en,fr:amd:2:en
refers to Amendment 2 in English to the 2nd edition of ISO 9999-1,
in English/French (bilingual document)
urn:iso:std:iso:9999:1:ed-2:en,fr:amd:2:en
refers to Amendment 2 in English to the 2nd edition of ISO 9999-1,
in English/French (bilingual document)
urn:iso:std:iso:9999:-1:ed-2:en:amd:1:cor:1
refers to Corrigendum 1 to Amendment 1 to the 2nd edition of ISO
9999-1, in English
urn:iso:std:iso:9999:-1:ed-2:en:amd:1:cor:1
refers to Corrigendum 1 to Amendment 1 to the 2nd edition of ISO
9999-1, in English
o Docelement handling:
o 文档元素处理：
urn:iso:std:iso:105:-c12:ed-1:en:clause:a.1,a.2
urn:iso:std:iso:105:-c12:ed-1:en:clause:a.1-a.2
both refer to clauses A.1 and A.2 in the 1st edition of ISO
105-C12, in English
urn:iso:std:iso:105:-c12:ed-1:en:clause:a.1,a.2
urn:iso:std:iso:105:-c12:ed-1:en:clause:a.1-a.2
both refer to clauses A.1 and A.2 in the 1st edition of ISO
105-C12, in English
urn:iso:std:iso:9999:-1:ed-1:v1-
amd1.v1:en,fr:amd:2:v2:en:clause:3.1,a.2-b.9 (isoversion scheme)
refers to (sub)clauses 3.1 and A.2 to B.9 in the corrected version
of Amendment 2, in English, which amends the document comprising
the 1st version of edition 1 of ISO 9999-1 incorporating the 1st
version of Amendment 1, in English/French (bilingual document)
urn:iso:std:iso:9999:-1:ed-1:v1-
amd1.v1:en,fr:amd:2:v2:en:clause:3.1,a.2-b.9 (isoversion scheme)
refers to (sub)clauses 3.1 and A.2 to B.9 in the corrected version
of Amendment 2, in English, which amends the document comprising
the 1st version of edition 1 of ISO 9999-1 incorporating the 1st
version of Amendment 1, in English/French (bilingual document)
urn:iso:std:iso:9999:-1:ed-2:en:amd:1:term:3.2,3.3,3.4.1-
3.4.4,3.12
refers to the terms 3.2, 3.3, 3.4.1 to 3.4.4, and 3.12 in
Amendment 1 to the 2nd edition of ISO 9999-1, in English
urn:iso:std:iso:9999:-1:ed-2:en:amd:1:term:3.2,3.3,3.4.1-
3.4.4,3.12
refers to the terms 3.2, 3.3, 3.4.1 to 3.4.4, and 3.12 in
Amendment 1 to the 2nd edition of ISO 9999-1, in English
ISO/IEC Directives, Part 1 [ISODIR-1] and Part 2 [ISODIR-2], and ISO supplement [ISODIR-S].
ISO/IEC指令，第1部分[ISODIR-1]和第2部分[ISODIR-2]以及ISO补充文件[ISODIR-S]。
Assignment of URNs for documents in the requested namespace will be managed by the ISO Central Secretariat, which will ensure that the assigned URNs are consistent with the ISO Directives for unique identification of ISO documents.
ISO中央秘书处将管理所请求名称空间中文件的URN分配，确保分配的URN与ISO文件唯一标识的ISO指令一致。
Assignment of URNs for Technical Committee resources related to ISO documents will be managed by the Technical Committees developing or maintaining those documents. As indicated above, each such URN will extend the URN for the containing document via the element <addition>. The responsibility of the Technical Committee will therefore be to ensure the uniqueness of the techdefined <addition> element that constitutes the identifier for the resource within the document namespace, and thus the uniqueness of the overall resource identifier within the requested namespace.
与ISO文件相关的技术委员会资源的URN分配将由开发或维护这些文件的技术委员会管理。如上所述，每个这样的URN将通过元素<addition>扩展包含文档的URN。因此，技术委员会的责任是确保构成文档命名空间内资源标识符的techdefined<addition>元素的唯一性，从而确保请求命名空间内整个资源标识符的唯一性。
Assigned URNs will not be reused and will remain valid beyond the lifecycle of the referenced resources. However, it should be noted that although the URNs remain valid, the status of the referenced resource may change.
分配的URN将不会被重用，并且在引用资源的生命周期之后仍然有效。但是，应该注意，尽管URN仍然有效，但引用资源的状态可能会更改。
Resolving document identifiers:
解析文档标识符：
This schema has been developed with the intent that a URN identifying an ISO document can be transformed to a valid http URI by replacing the requested URN namespace prefix ("iso") and the "std:" prefix with the domain name "standards.iso.org", replacing all occurrences of ":" within the identifier with "/", and converting characters to lowercase. (ISO is planning to develop a website implementation to support these URIs.)
开发此模式的目的是，通过将请求的URN命名空间前缀（“ISO”）和“std:”前缀替换为域名“standards.ISO.org”，将标识符中出现的“：”替换为“/”，可以将标识ISO文档的URN转换为有效的http URI，以及将字符转换为小写。（ISO计划开发一个网站实现来支持这些URI。）
Examples:
示例：
urn:iso:std:iso:9999:-1:ed-1:en: corresponds to
http://standards.iso.org/iso/9999/-1/ed-1/en/
urn:iso:std:iso:9999:-1:ed-1:en: corresponds to
http://standards.iso.org/iso/9999/-1/ed-1/en/
urn:iso:std:iso-iec:tr:9999:-1:ed-1:en: corresponds to
http://standards.iso.org/iso-iec/tr/9999/-1/ed-1/en/
urn:iso:std:iso-iec:tr:9999:-1:ed-1:en: corresponds to
http://standards.iso.org/iso-iec/tr/9999/-1/ed-1/en/
urn:iso:std:iso:9999:-1:ed-2:en,fr:amd:2: corresponds to
http://standards.iso.org/iso/9999/-1/ed-2/en,fr/amd/2/
urn:iso:std:iso:9999:-1:ed-2:en,fr:amd:2: corresponds to
http://standards.iso.org/iso/9999/-1/ed-2/en,fr/amd/2/
Resolving identifiers for <addition> resources:
解析<addition>资源的标识符：
For URNs in the requested namespace that refer to additional resources related to ISO documents, the ISO Central Secretariat will specify the resolution procedure at the time it defines the syntax for the corresponding <addition> to the <std-nss>. In most cases, those resources will be maintained on an ISO website, as extensions to the http URIs described above.
对于所请求名称空间中引用与ISO文件相关的其他资源的URN，ISO中央秘书处将在定义<std nss>的相应<addition>语法时指定解决程序。在大多数情况下，这些资源将作为上述http URI的扩展维护在ISO网站上。
URNs are lexically equivalent if they are octet-by-octet equal after the following preprocessing:
如果经过以下预处理后，URN是八进制的，则它们在词汇上是等价的：
1. normalize the case of the leading "urn:" token
1. 规范化前导“urn:”标记的大小写
2. normalize the case of the NID
2. 使NID的情况正常化
3. normalize the case of any %-escaping
3. 使任何情况正常化
4. normalize the case of all elements
4. 规范化所有元素的大小写
Further information is specified in [RFC2141], Section 5.
[RFC2141]第5节规定了更多信息。
No special considerations.
没有特别考虑。
None specified.
没有具体说明。
Global.
全球的
The ISO-specific requirements are as follows:
ISO的具体要求如下：
o globally unique, persistent identifiers
o 全局唯一的持久标识符
o location-independent identifiers
o 位置无关标识符
o human-interpretable identifiers
o 人类可解释标识符
o a scheme applicable to paper documents as well as machine-readable documents
o 一种适用于纸质文档和机器可读文档的方案
o a scheme applicable to conceptual documents and explicit forms of documents
o 适用于概念性文件和明确形式文件的方案
o a scheme applicable to resources extracted from documents
o 一种适用于从文档中提取资源的方案
o a scheme applicable to "metadata" associated with documents
o 适用于与文档关联的“元数据”的方案
o a scheme in which the identifier assignment is managed by the ISO Central Secretariat
o 由ISO中央秘书处管理标识符分配的一种方案
Location-independence: Because the publication of ISO standards is a complex arrangement involving multiple development organizations and national standards institutes, a given ISO document may be available in a number of forms from a number of sources. This makes it important to have a document identifier that is global in scope, widely and uniformly used, and independent of the text source used by any given reference.
位置独立性：由于ISO标准的发布是一项涉及多个开发组织和国家标准研究所的复杂安排，因此给定的ISO文件可以从多个来源以多种形式提供。这使得文档标识符的作用域是全局的、使用范围广泛且统一，并且独立于任何给定引用所使用的文本源非常重要。
Human-interpretable: Many, perhaps most, references to documents appear in text generated by human authors. It is important that an author familiar with the scheme be able to generate a correct URN for a document for which the author has the ISO reference (or document identifier). Conversely, it is important that a reader unfamiliar
人类可解释：许多，也许是大多数，对文档的引用出现在人类作者生成的文本中。熟悉该方案的作者必须能够为其具有ISO参考（或文档标识符）的文档生成正确的URN。相反，重要的是读者不熟悉
with the scheme be able to identify the URN as a reference to an ISO document, particularly an ISO standard, and also to recognize identifiers for forms, languages, or metadata sets.
使用该方案，您可以将URN识别为ISO文档（特别是ISO标准）的引用，还可以识别表单、语言或元数据集的标识符。
Paper documents: Older ISO standards that are commonly used as industrial references exist only in paper form or in earlier machine-readable forms that are not commonly used on the Internet. It is important to have a document identifier scheme that extends to these resources as well. (In fact, many of these have been converted to Internet forms, and others are being converted, but it is important that the identifier be independent of the form in which the document can be obtained at any given time.)
纸质文档：通常用作工业参考的较旧ISO标准仅以纸质形式存在，或以互联网上不常用的早期机器可读形式存在。有一个扩展到这些资源的文档标识符方案也很重要。（事实上，其中许多已转换为Internet表单，其他正在转换，但标识符必须独立于在任何给定时间获取文档的表单。）
Conceptual documents vs. representation forms: Because ISO documents are regularly maintained and re-published in multiple forms, it is important to have document identifiers that denote the conceptual document, without regard to publication form. At the same time, it is necessary for certain types of use to be able to refer to specific editions, or specific publication forms (for example, editions in different languages, or to PDF or HTML versions). This URN specification allows for the identification of these different types of use in the <isodefined> part of the <addition> element.
概念性文件与表示形式：由于ISO文件定期维护并以多种形式重新发布，因此重要的是要有表示概念性文件的文件标识符，而不考虑发布形式。同时，某些类型的使用必须能够引用特定的版本或特定的出版物形式（例如，不同语言的版本，或PDF或HTML版本）。本URN规范允许在<addition>元素的<isodefined>部分识别这些不同类型的使用。
Document extracts: ISO standards may contain formal specifications in machine-processable languages, or formal specifications that also have representations in machine-processable languages. It is useful to be able to extract these specifications in machine-processable form as separate resources, and therefore it is necessary to give these "extracted resources" global identifiers derived from the document identifier using a consistent identification scheme.
文档摘录：ISO标准可能包含机器可处理语言的正式规范，或者也包含机器可处理语言表示的正式规范。能够以机器可处理的形式提取这些规范作为单独的资源是很有用的，因此有必要使用一致的标识方案为这些“提取的资源”提供从文档标识符派生的全局标识符。
Document metadata: Certain uses of documents and document text, primarily bibliographic, also extract information from the documents, and that information, commonly called "metadata", is organized in machine-readable forms conforming to other standards. These metadata sets then become resources in their own right. It is important to give them URN identifiers consistent with the document identification scheme.
文档元数据：文档和文档文本的某些用途，主要是书目，也从文档中提取信息，这些信息通常称为“元数据”，以符合其他标准的机器可读形式组织。然后，这些元数据集本身就成为资源。为他们提供与文件标识方案一致的URN标识符非常重要。
The ISO community is broad in two dimensions. In one dimension, its documents are developed and used in a large variety of industries and professions: natural sciences, manufacturing, construction, transportation, information technology, social sciences, etc. In the other dimension, it is a community of expert developers, standards
ISO社区在两个方面都很广泛。在一个维度上，它的文档被开发并用于多种行业和职业：自然科学、制造业、建筑业、交通运输业、信息技术、社会科学等。在另一个维度上，它是一个由专家开发人员、标准制定者和标准制定者组成的社区
managers, publishers, professional users, and consumers. And Internet information technologies are a part of common professional practice in all of these areas in both dimensions.
经理、出版商、专业用户和消费者。互联网信息技术是所有这些领域在这两个方面的共同专业实践的一部分。
ISO standards are cited in business agreements, in professional publications, in product descriptions, and in standards development and publication activities. When these citations appear in electronic form, the references must be unambiguous.
ISO标准在商业协议、专业出版物、产品说明以及标准开发和出版活动中引用。当这些引文以电子形式出现时，参考文献必须明确无误。
The information technology community is itself very active in the development and use of standards, and many ISO publications are developed by and for that community. When an Internet information exchange uses a form specified in an ISO document, or a terminology defined in an ISO document, it is often necessary to identify that ISO specification in the envelope surrounding the exchange. That identification should use a formal, unambiguous identifier in a form readily recognized by the receiving software, and possibly by the ultimate human recipient of the information.
信息技术界本身非常积极地参与标准的开发和使用，许多ISO出版物都是由该界开发并为其服务的。当Internet信息交换使用ISO文档中指定的格式或ISO文档中定义的术语时，通常需要在围绕交换的信封中标识该ISO规范。该标识应使用一个正式的、明确的标识符，其形式易于被接收软件识别，也可能被信息的最终人类接收者识别。
In order to facilitate the use of existing and emerging Internet technologies for all of these purposes, URNs conforming to [RFC2141] represent the most useful form of formal, globally unambiguous identifiers. The use of a managed namespace for such identifiers, following a consistent scheme for identifying ISO documents and their derivatives, would be of significant benefit to the entire ISO community.
为了便于将现有和新兴的互联网技术用于所有这些目的，符合[RFC2141]的URN代表了最有用的形式的正式、全球明确的标识符。按照识别ISO文档及其派生文档的一致方案，为此类标识符使用托管名称空间，将对整个ISO社区带来重大好处。
It would give professional users in many industries a standard form for electronic reference to ISO standards in HTML, XML, PDF, etc., documents.
它将为许多行业的专业用户提供一个标准表格，用于以HTML、XML、PDF等文档的形式对ISO标准进行电子参考。
It would give software developers a standard form for reference to ISO standard protocols, schemata, languages, data sets, etc.
它将为软件开发人员提供一个参考ISO标准协议、模式、语言、数据集等的标准格式。
It would give standards developers a standard form for reference to other ISO publications in various stages of development. And it would give them a standard form for creating identifiers for machine-readable information sets contained in, or derived from, the specifications.
它将为标准开发人员提供一个标准表格，供在不同开发阶段参考其他ISO出版物。它将为他们提供一种标准形式，用于为规范中包含或派生的机器可读信息集创建标识符。
It would give standards managers and publishers a formal uniform scheme for reference to specific publications, editions, and versions of ISO documents.
它将为标准管理者和发布者提供一个正式的统一方案，用于参考ISO文件的特定出版物、版本和版本。
While the assignment of identifiers under this scheme is managed by the ISO Central Secretariat, the processes by which the identified objects arise and acquire such identifiers are the result of agreements made by the member bodies. Every such project is
虽然本方案下标识符的分配由ISO中央秘书处管理，但识别对象产生和获取此类标识符的过程是成员机构达成协议的结果。每一个这样的项目都是
initiated by one member body and reviewed and voted on by the others. Every accepted project is open to participation by any member body, and in fact, participation by a certain minimum number (usually 5) of member bodies is required for acceptance of most projects. In general, the member bodies are open professional and industrial organizations reflecting broad expertise and national interest.
由一个成员机构发起，并由其他成员机构审查和表决。每一个被接受的项目都开放给任何成员机构参与，事实上，大多数项目的验收都需要一定数量（通常为5个）的成员机构参与。一般来说，成员机构是公开的专业和工业组织，反映了广泛的专业知识和国家利益。
It should be noted that ISO documents in draft state are not usually made available outside the ISO standards development community. Making them available to professionals outside of the process might well mislead the recipients into premature adoption of practices that are not yet completely specified or have not yet achieved consensus, and therefore may well change.
应该注意的是，处于起草状态的ISO文件通常不会在ISO标准开发社区之外提供。向流程之外的专业人员提供这些信息可能会误导接收者过早地采用尚未完全指定或尚未达成共识的做法，因此很可能会发生变化。
It should also be noted that ISO documents are not, in general, freely available over the Internet. Rather, there are complex agreements between ISO and its member institutes as to the rights to the publications and the corresponding fees that may be charged for paper or electronic copies of various editions. Some ISO documents are freely available, and some are freely available in certain forms. In general, derivatives of ISO documents (schemata, metadata sets, etc.) are freely available over the Internet in the appropriate machine-readable forms. A URL associated with a URN in the requested namespace may therefore lead directly to a machine-readable copy of the text of the document or derivative, or it may lead to a site that can provide that text for a fee, or it may lead to a site that can only sell a paper copy of the document. Bearing in mind that ISO is a network of otherwise independent institutes, this behavior is simply a property of the ISO community.
还应注意的是，一般来说，国际标准化组织文件不是通过互联网免费提供的。相反，ISO与其成员机构之间就出版物的权利以及各种版本的纸质或电子版可能收取的相应费用达成了复杂的协议。有些ISO文件是免费提供的，有些是以某种形式免费提供的。一般来说，ISO文档的派生版本（模式、元数据集等）可以在互联网上以适当的机器可读形式免费获得。因此，与请求名称空间中的URN关联的URL可能直接指向文档或衍生文档文本的机器可读副本，也可能指向可以收费提供该文本的网站，或者指向只能销售文档纸质副本的网站。请记住，ISO是一个由其他独立机构组成的网络，这种行为只是ISO社区的财产。
Finally, it should be noted that, for many purposes, reference to the ISO standard is what is required, and only the product engineer or software tool builder actually needs access to the text. This request is based on the need to standardize the form of reference, not the means of access.
最后，需要注意的是，出于许多目的，需要参考ISO标准，并且只有产品工程师或软件工具构建者实际需要访问文本。这一要求是基于需要标准化参考表格，而不是访问方式。
IANA has assigned "iso" (29) as a formal NID.
IANA已将“iso”（29）指定为正式NID。
The ISO Central Secretariat will maintain a registry of the permissible values for the elements comprising the NSS. Information may be obtained from the following address: urn@iso.org.
ISO中央秘书处将保留NSS组成要素的允许值登记册。可从以下地址获取信息：urn@iso.org.
The ISO URN Namespace ID shares the security considerations outlined in [RFC3406], but has no other known security considerations.
ISO URN命名空间ID共享[RFC3406]中概述的安全注意事项，但没有其他已知的安全注意事项。
[ISODIR-1] International Organization for Standardization, "Procedures for the technical work", ISO/IEC Directives Part 1, Edition 5, 2004.
[ISODIR-1]国际标准化组织，“技术工作程序”，ISO/IEC指令第1部分，第5版，2004年。
[ISODIR-2] International Organization for Standardization, "Rules for the structure and drafting of International Standards", ISO/IEC Directives Part 2, Edition 5, 2004.
[ISODIR-2]国际标准化组织，“国际标准的结构和起草规则”，ISO/IEC指令第2部分，第5版，2004年。
[ISODIR-S] International Organization for Standardization, "Procedures specific to ISO", ISO/IEC Directives Supplement.
[ISODIR-S]国际标准化组织，“ISO特定程序”，ISO/IEC指令补充。
[ISOGUIDE69] International Organization for Standardization, "Harmonized Stage Code system (Edition 2) - Principles and guidelines for use", ISO Guide 69:1999.
[ISO指南69]国际标准化组织，“协调阶段代码体系（第2版）-使用原则和指南”，ISO指南69:1999。
[ISO639-1] International Organization for Standardization, "Codes for the representation of names of languages - Part 1: Alpha-2 code", ISO 639-1:2002.
[ISO639-1]国际标准化组织，“语言名称表示代码-第1部分：阿尔法-2代码”，ISO 639-1:2002。
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5234]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[ISO8879:1986] International Organization for Standardization, "Information processing -- Text and office systems -- Standard Generalized Markup Language (SGML)", ISO 8879:1986.
[ISO8879:1986]国际标准化组织，“信息处理——文本和办公系统——标准通用标记语言（SGML）”，ISO 8879:1986。
[ISO/IEC9070:1991] International Organization for Standardization, "Information technology -- SGML support facilities -- Registration procedures for public text owner identifiers", ISO/IEC 9070:1991.
[ISO/IEC9070:1991]国际标准化组织，“信息技术——SGML支持设施——公共文本所有者标识符的注册程序”，ISO/IEC 9070:1991。
[ISO/IEC8824-1:2002] International Organization for Standardization, "Information technology -- Abstract Syntax Notation One (ASN.1): Specification of basic notation -- Part 1", ISO/IEC 8824-1:2002.
[ISO/IEC8824-1:2002]国际标准化组织，“信息技术——抽象语法符号一（ASN.1）：基本符号规范——第1部分”，ISO/IEC 8824-1:2002。
[ISO/IEC8825:1987] International Organization for Standardization, "Information processing systems -- Open Systems Interconnection -- Specification of Basic Encoding Rules for Abstract Syntax Notation ONE (ASN.1)", ISO/IEC 8825:1987.
[ISO/IEC8825:1987]国际标准化组织，“信息处理系统——开放系统互连——抽象语法符号1（ASN.1）基本编码规则规范”，ISO/IEC 8825:1987。
[CCITT] "Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)", CCITT Recommendation X.209, January 1988.
[CCITT]“抽象语法符号1（ASN.1）基本编码规则规范”，CCITT建议X.209，1988年1月。
[RFC3061] Mealling, M., "A URN Namespace of Object Identifiers", RFC 3061, February 2001.
[RFC3061]Mealling，M.，“对象标识符的URN名称空间”，RFC 3061，2001年2月。
[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月。
[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying Languages", BCP 47, RFC 4646, September 2006.
[RFC4646]Phillips，A.和M.Davis，“识别语言的标记”，BCP 47，RFC 46462006年9月。
Before initiating this request, ISO attempted to find an existing or currently proposed URN NID scheme that might be used instead of a dedicated scheme. Two existing schemes were carefully considered because they clearly meet part of the requirements:
在发起此请求之前，ISO试图找到一个现有的或当前提议的URN NID方案，该方案可能被用来代替专用方案。我们仔细考虑了两项现有计划，因为它们显然符合部分要求：
o The OID scheme, documented in [RFC3061]
o [RFC3061]中记录的OID方案
o The PublicId scheme, documented in [RFC3151]
o [RFC3151]中记录的PublicId方案
The OID scheme is derived from the joint ISO/ITU-T ASN.1 object-identifier scheme specified in [ISO/IEC8824-1:2002] (original edition 1984; [RFC3061] cites the 1988 [CCITT] edition of the encoding rules in [ISO/IEC8825:1987]. This standard assigned the registry authority for all identifiers in the { iso(1) } namespace to ISO, and therefore, ISO controls the registry of all identifiers beginning "oid:1:". And in fact, ISO has developed, and is using, an identification scheme under ASN.1 that meets most of the above requirements. ISO could clearly define a use of the OID scheme that would be adequate to meet all of its technical objectives, although it would further complicate the current ASN.1 scheme.
OID方案源自[ISO/IEC8824-1:2002]（1984年原版；[RFC3061]引用了[ISO/IEC8825:1987]中1988年[CCITT]版的编码规则。本标准为{ISO（1）}中的所有标识符分配了注册机构命名空间，因此，ISO控制从“oid:1:开始的所有标识符的注册表：事实上，ISO已经开发并正在使用ASN.1下的识别方案，该方案满足上述大部分要求。ISO可以明确定义OID方案的使用，该方案足以满足其所有技术目标，尽管这将使当前ASN.1方案进一步复杂化。
The original intent of ISO 8824 was to permit both a human-readable form for the identifier, to maximize intuitive recognition, and an encoding that minimized the number of bits needed to communicate an OID value over a network. Regrettably, the encoding chosen in RFC 3061 is much closer to the minimal bits encoding than to the human-readable one. The NSS for the OID scheme consists entirely of digits and punctuation. For example, the ASN.1 identifier { iso(1) standard(0) 7852 part(2) edition(3) } becomes: urn:oid:1:0:7852:2:3.
ISO 8824的初衷是允许标识符采用人类可读的形式，以最大限度地提高直观识别，并允许编码最小化通过网络传输OID值所需的位数。遗憾的是，在RFC 3061中选择的编码比人类可读的编码更接近最小比特编码。OID方案的NSS完全由数字和标点组成。例如，ASN.1标识符{iso（1）标准（0）7852第（2）部分版本（3）}变成：urn:oid:1:0:7852:2:3。
This is difficult for a human reader or author to interpret. It is also easy to mistype, and the scheme contains no "check-digits", which makes it difficult to validate, leading to the propagation of URNS that are invalid or valid but erroneous. Finally, the all-numeric form conveys no hint of the name of the responsible organization, and therefore no hint of any URL that might aid a human reader in interpreting the reference. The OID scheme makes all of the required identifiers technically possible and technically useable by software, but for all practical purposes, the OID URNs are useful only to software.
这对于人类读者或作者来说是很难理解的。此外，很容易输入错误，并且该方案不包含“校验位”，这使得验证变得困难，从而导致传播无效或有效但错误的URN。最后，全数字表单不表示负责组织的名称，因此也不表示可能有助于人类读者解释引用的任何URL。OID方案使所有必需的标识符在技术上成为可能，并且在技术上可供软件使用，但就所有实际目的而言，OID URN仅对软件有用。
The PublicId scheme is derived from Standard Generalized Markup Language (SGML) [ISO8879:1986] and [ISO/IEC9070:1991] bibliographic catalogue forms. Narrowed to ISO publications, it is adequate for the unique global persistent identification of published documents, in both paper and machine-processable form.
PublicId方案源自标准通用标记语言（SGML）[ISO8879:1986]和[ISO/IEC9070:1991]书目目录形式。仅限于ISO出版物，它足以以纸张和机器可处理形式对已发布文档进行唯一的全局持久性标识。
Importantly, the PublicId scheme does not have a "conceptual document" notion -- it identifies specific publications and editions. "Weak identification" could be used to implement the conceptual document concept, but the PublicId scheme does not document that interpretation. In any case, the PublicId scheme does not extend to draft documents, which are often referenced in pilot implementations, to separate forms of a document, or to resources extracted from documents. It supports only those metadata elements that are defined in SGML. The scheme could be extended to do most of these, but the ISO-specific extensions would not in general extend to the much broader base of documents identified by PublicIds. (Version and edition management practices vary significantly across publishers, depending on their milieu.) Further, the ISO Central Secretariat could not and should not control the registry of such URNs.
重要的是，PublicId方案没有“概念性文档”的概念——它标识特定的出版物和版本。“弱识别”可用于实施概念性文件概念，但PublicId方案并未记录该解释。在任何情况下，PublicId方案都不会扩展到试点实施中经常引用的文档草稿、文档的单独形式或从文档中提取的资源。它只支持SGML中定义的元数据元素。该方案可以扩展到大部分，但特定于ISO的扩展通常不会扩展到PublicID标识的更广泛的文档基础。（不同出版商的版本和版本管理实践差异很大，取决于他们所处的环境。）此外，ISO中央秘书处不能也不应该控制此类URN的注册。
ISO therefore concluded that the alternative schemes are not adequate to meet the requirements of the ISO community.
因此，ISO得出结论，替代方案不足以满足ISO团体的要求。
Whilst requesting a new namespace for ISO documents and their derivatives, ISO does not wish to discourage the use of these other identifiers for ISO publications. The PublicId form, in particular, is useful for referring to ISO publications in a larger bibliographic information space.
在为ISO文档及其派生文档请求新名称空间的同时，ISO不希望阻止在ISO出版物中使用这些其他标识符。PublicId表格尤其有助于在更大的书目信息空间中引用ISO出版物。
Appendix B. ABNF Definition of Namespace ID = "iso" (Informative)
附录B.名称空间ID=“iso”的ABNF定义（资料性）
NSS = std-nss
NSS = std-nss
std-nss = "std:" docidentifier *supplement *docelement
[addition]
std-nss = "std:" docidentifier *supplement *docelement
[addition]
docidentifier = originator [":" type] ":" docnumber [":" partnumber]
[[":" status] ":" edition]
[":" docversion] [":" language]
docidentifier = originator [":" type] ":" docnumber [":" partnumber]
[[":" status] ":" edition]
[":" docversion] [":" language]
originator = "iso" / "iso-iec" / "iso-cie" / "iso-astm" /
"iso-ieee" / "iec"
originator = "iso" / "iso-iec" / "iso-cie" / "iso-astm" /
"iso-ieee" / "iec"
; iso = International Organization for ; Standardization
; 国际标准化组织（iso）；标准化
; iec = International Electrotechnical
; Commission (IEC), or Commission
; Electrotechnique Internationale
; iec = International Electrotechnical
; Commission (IEC), or Commission
; Electrotechnique Internationale
; iso-iec = jointly developed by ISO and IEC
; iso iec=由iso和iec联合开发
; iso-cie = jointly developed by ISO and the
; Commission Internationale d'Eclairage
; (CIE)
; iso-cie = jointly developed by ISO and the
; Commission Internationale d'Eclairage
; (CIE)
; iso-astm = jointly developed by ISO and the
; American Society for Testing and
; Materials (ASTM) International
; iso-astm = jointly developed by ISO and the
; American Society for Testing and
; Materials (ASTM) International
; iso-ieee = jointly developed by ISO and the
; Institute for Electrical and
; Electronics Engineers (IEEE)
; iso-ieee = jointly developed by ISO and the
; Institute for Electrical and
; Electronics Engineers (IEEE)
type = "data" / "guide" / "isp" / "iwa" /
"pas" / "r" / "tr" / "ts" / "tta"
type = "data" / "guide" / "isp" / "iwa" /
"pas" / "r" / "tr" / "ts" / "tta"
; data = Data (document type no longer published)
; 数据=数据（不再发布文档类型）
; guide = Guide
; 指南
; isp = International Standardized Profile
; isp=国际标准化配置文件
; iwa = International Workshop Agreement
; iwa=国际研讨会协议
; pas = Publicly Available Specification
; pas=公开可用的规范
; r = Recommendation (document type no longer ; published)
; r=建议（不再使用文档类型；已发布）
; tr = Technical Report
; tr=技术报告
; ts = Technical Specification
; ts=技术规范
; tta = Technology Trends Assessment
; tta=技术趋势评估
docnumber = DIGITS
docnumber = DIGITS
partnumber = "-" 1*( DIGIT / ALPHA / "-" )
partnumber = "-" 1*( DIGIT / ALPHA / "-" )
status = ( "draft" / "cancelled" ) / stage
status = ( "draft" / "cancelled" ) / stage
; draft = document that has not yet been
; accepted for publication by
; international ballot
; draft = document that has not yet been
; accepted for publication by
; international ballot
; cancelled = document that has been deleted or ; withdrawn
; 已取消=已删除或删除的文档；撤回
stage = "stage-" stagecode ["." iteration]
stage=“stage-”stagecode[“”迭代]
stagecode = DIGIT DIGIT "." DIGIT DIGIT
stagecode=数字“.”数字
iteration = "v" DIGITS
迭代=“v”位
edition = "ed-" DIGITS
edition=“ed-”数字
docversion = "v" (simpleversion / isoversion)
docversion=“v”（简化版本/isoversion）
simpleversion = DIGITS
simpleversion = DIGITS
; 1 = first version published
; 1=发布的第一个版本
; 2 = corrected version published
; 2=已发布的更正版本
isoversion = baseversion *includedsuppl
isoversion=基本版本*包括支持
baseversion = DIGITS
baseversion = DIGITS
includedsuppl = "-" suppltype supplnumber [ "." supplversion ]
includedsuppl=“-”suppltype supplnumber[”“supplversion]
language = monolingual / bilingual / trilingual
language = monolingual / bilingual / trilingual
monolingual = "en" / "fr" / "ru" / "es" / "ar"
monolingual = "en" / "fr" / "ru" / "es" / "ar"
bilingual = "en,fr" / "en,ru" / "fr,ru"
bilingual = "en,fr" / "en,ru" / "fr,ru"
trilingual = "en,fr,ru"
三语=“英语、法语、俄语”
supplement = ":" suppltype ":" supplnumber
[":" supplversion ] [":" language ]
supplement = ":" suppltype ":" supplnumber
[":" supplversion ] [":" language ]
suppltype = "amd" / "cor" / "add"
suppltype = "amd" / "cor" / "add"
; amd = Amendment
; 修正案
; cor = Technical Corrigendum
; cor=技术勘误表
; add = Addendum
; add=附录
supplnumber = DIGITS
supplnumber = DIGITS
supplversion = "v" DIGITS
supplersion=“v”位
docelement = ":" ( "clause" / "figure" / "table" / "term" ) ":"
elementnumber / elementrange
*( "," elementnumber / elementrange )
docelement = ":" ( "clause" / "figure" / "table" / "term" ) ":"
elementnumber / elementrange
*( "," elementnumber / elementrange )
elementnumber = ( ALPHA / DIGITS ) *( "." DIGITS )
elementnumber = ( ALPHA / DIGITS ) *( "." DIGITS )
elementrange = elementnumber "-" elementnumber
elementrange=elementnumber“-”elementnumber
addition = techdefined / isodefined
addition = techdefined / isodefined
techdefined = ":tech" *techelement
techdefined = ":tech" *techelement
techelement = <unspecified>
techelement = <unspecified>
isodefined = <unspecified>
isodefined = <unspecified>
DIGITS = DIGIT *DIGIT
位数=位数*位数
DIGIT = %x30-39 ; 0-9
DIGIT = %x30-39 ; 0-9
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
Authors' Addresses
作者地址
Joanna Goodwin International Organization for Standardization Case Postal 56 Geneva 20 1211 Switzerland
乔安娜·古德温国际标准化组织案例邮政56日内瓦20 1211瑞士
EMail: goodwin@iso.org
URI: http://www.iso.org
EMail: goodwin@iso.org
URI: http://www.iso.org
Holger Apel International Organization for Standardization Case Postal 56 Geneva 20 1211 Switzerland
Holger-Apel国际标准化组织案例邮政56日内瓦20 1211瑞士
EMail: apel@iso.org
URI: http://www.iso.org
EMail: apel@iso.org
URI: http://www.iso.org
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights 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; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.