Network Working Group K. Best
Request for Comments: 3121 OASIS, Inc.
Category: Informational N. Walsh
Sun Microsystems, Inc.
June 2001
Network Working Group K. Best
Request for Comments: 3121 OASIS, Inc.
Category: Informational N. Walsh
Sun Microsystems, Inc.
June 2001
A URN Namespace for OASIS
OASIS的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.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This document describes a URN (Uniform Resource Name) namespace that is engineered by the Organization for the Advancement of Structured Information Standards (OASIS) for naming persistent resources published by OASIS (such as OASIS Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents).
本文档描述了由结构化信息标准促进组织（OASIS）设计的URN（统一资源名称）命名空间，用于命名OASIS发布的持久性资源（如OASIS标准、XML（可扩展标记语言））文档类型定义、XML模式、名称空间、样式表和其他文档）。
The Organization for the Advancement of Structured Information Standards (OASIS) produces many kinds of documents: specifications, working drafts, technical resolutions, schemas, stylesheets, etc.
结构化信息标准促进组织（OASIS）生产多种文档：规范、工作草案、技术解决方案、模式、样式表等。
OASIS wishes to provide global, distributed, persistent, location-independent names for these resources.
OASIS希望为这些资源提供全局、分布式、持久、位置独立的名称。
The Extensible Markup Language (XML) requires that all resources provide a system identifier, which must be a URI, in addition to an optional public identifier (which provides an alternate mechanism for constructing identifiers) and many evolving specifications require authors to identify documents by URI alone (XML Namespaces, XML Schema, XSLT, etc.).
可扩展标记语言（XML）要求所有资源除了可选的公共标识符（提供构造标识符的替代机制）之外，还提供一个系统标识符（必须是URI），并且许多不断发展的规范要求作者仅通过URI标识文档（XML名称空间、XML模式、XSLT等）。
Motivated by these observations, OASIS would like to assign URNs to some resources in order to retain unique, permanent location-independent names for them.
出于这些观察的动机，OASIS希望将URN分配给某些资源，以便为它们保留唯一、永久的独立于位置的名称。
This namespace specification is for a formal namespace.
此名称空间规范适用于正式名称空间。
Namespace ID:
命名空间ID:
"oasis" requested.
“绿洲”请求。
Registration Information:
注册资料：
Registration Version Number: 3 Registration Date: 2001-02-05
注册版本号：3注册日期：2001-02-05
Declared registrant of the namespace:
已声明命名空间的注册人：
Karl Best OASIS - Organization for the Advancement of Structured Information Standards Post Office Box 455 Billerica, MA USA 01821
卡尔·贝斯特绿洲-结构化信息标准促进组织美国马萨诸塞州比尔里卡455号邮政信箱01821
Phone: +1 (978) 667 5115
电话：+1（978）6675115
Declaration of structure:
结构声明：
The Namespace Specific String (NSS) of all URNs assigned by OASIS will have the following hierarchical structure:
OASIS分配的所有URN的命名空间特定字符串（NSS）将具有以下层次结构：
There are two branches at the top of the hierarchy: "names" and "member".
在层次结构的顶部有两个分支：“名称”和“成员”。
The Names Hierarchy
名称层次结构
The NSS in the names hierarchy begins with a document class identifier. There are three classes of identifiers:
名称层次结构中的NSS以文档类标识符开头。有三类标识符：
"specification", "tc", and "technical".
“规范”、“技术规范”和“技术规范”。
Specifications
规格
The "specification" hierarchy is for OASIS Specifications. The general structure of the NSS in the specification hierarchy has the form:
“规范”层次结构用于OASIS规范。规范层次结构中NSS的一般结构具有以下形式：
urn:oasis:names:specification:{specification-id}
:{type}{:subtype}?:{document-id}
urn:oasis:names:specification:{specification-id}
:{type}{:subtype}?:{document-id}
where "specification-id" is a unique identifier for the specification, "type" identifies the document type (document, schema, stylesheet, entity, xmlns, etc.), the optional "subtype" provides additional information about the document type (for example, stylesheet or schema language), and "document-id" is a unique identifier for the document.
其中“规范id”是规范的唯一标识符，“类型”标识文档类型（文档、模式、样式表、实体、xmlns等），可选的“子类型”提供关于文档类型的附加信息（例如，样式表或模式语言），“文档id”是文档的唯一标识符。
The Director of Technical Operations at OASIS assigns document types, subtypes, and all unique identifiers.
OASIS技术运营总监分配文档类型、子类型和所有唯一标识符。
Technical Committee Work Products
技术委员会工作产品
The "tc" hierarchy is for work products of OASIS Technical Committees. The general structure of the NSS in the tc hierarchy has the form:
“tc”层次结构用于OASIS技术委员会的工作产品。tc层次结构中NSS的一般结构具有以下形式：
urn:oasis:names:tc:{tc-id}:{type}{:subtype}?:{document-id}
urn:oasis:names:tc:{tc-id}:{type}{:subtype}?:{document-id}
where "tc-id" is a unique identifier for the Technical Committee, and the remaining fields are assigned as per the specification hierarchy.
其中“tc id”是技术委员会的唯一标识符，其余字段根据规范层次结构分配。
Technical Papers
技术论文
The "technical" hierarchy identifies legacy documents (Technical Notes, Resolutions, Memoranda, and Research Papers). The general structure of the NSS in the "technical" hierarchies has the form:
“技术”层次结构识别遗留文档（技术说明、决议、备忘录和研究论文）。“技术”层次结构中NSS的一般结构有以下形式：
urn:oasis:names:technical:{document-type}
:{document-id}:{amendment-id}
urn:oasis:names:technical:{document-type}
:{document-id}:{amendment-id}
The document type is one of the following: "note", "resolution", "memorandum", or "researchpaper".
文档类型为以下类型之一：“注释”、“决议”、“备忘录”或“研究论文”。
The document and amendment identifiers are derived from the legacy system for naming these documents. The document identifier consists of a two digit year and a sequential number, the amendment identifier is the year of the amendment.
文档和修订标识符源自用于命名这些文档的旧系统。文件标识符由两位数的年份和序列号组成，修订标识符是修订的年份。
The Members Hierarchy
成员层次结构
The NSS in the members hierarchy begins with a unique member identifier assigned by OASIS. The string following the member identifier is opaque. For example:
成员层次结构中的NSS以OASIS分配的唯一成员标识符开始。成员标识符后面的字符串是不透明的。例如：
urn:oasis:member:A00024:x
urn:oasis:member:A00024:x
The member identifiers will be assigned by The Director of Technical Operations at OASIS. The opaque string is defined by the owner of the branch that begins with "urn:oasis:member:{member-id}:".
成员标识符将由OASIS技术运营总监分配。不透明字符串由以“urn:oasis:member:{member id}:”开头的分支的所有者定义。
Relevant ancillary documentation:
相关辅助文件：
None
没有一个
Identifier uniqueness considerations:
标识符唯一性注意事项：
Identifier uniqueness will be enforced by the Director of Technical Operations who assigns unique identifiers to all documents identified by URN.
标识符唯一性将由技术运营总监执行，该总监为URN识别的所有文件分配唯一标识符。
Identifier persistence considerations:
标识符持久性注意事项：
OASIS is committed to maintaining the accessibility and persistence of all the resources that are assigned URNs.
OASIS致力于维护分配给URN的所有资源的可访问性和持久性。
Process of identifier assignment:
标识符分配过程：
Assignment is limited to the owner and those authorities that are specifically designated by the owner. OASIS will assign portions of its namespace (specifically, those under the members hierarchy) for assignment by other parties.
转让仅限于业主和业主特别指定的机构。OASIS将分配其命名空间的一部分（特别是成员层次结构下的部分），以供其他方分配。
Process of identifier resolution:
标识符解析过程：
The owner will distribute catalogs (OASIS TR9401 Catalogs) that map the assigned URNs to resource identifiers (e.g., URLs). A more interactive, online resolution system will also be deployed in the near future.
所有者将分发将分配的URN映射到资源标识符（例如URL）的目录（OASIS TR9401目录）。在不久的将来，还将部署一个更具互动性的在线解决系统。
The owner will authorize additional resolution services as appropriate.
业主将酌情授权额外的解决服务。
Rules for Lexical Equivalence:
词汇对等规则：
URNs are lexically equivalent if they are lexically identical.
如果URN在词汇上相同，则它们在词汇上是等价的。
Conformance with URN Syntax:
符合URN语法：
No special considerations.
没有特别考虑。
Validation mechanism:
验证机制：
None specified. The owner will publish OASIS TR9401 Catalogs. The presence of a URN in a catalog indicates that it is valid.
没有具体说明。所有者将发布OASIS TR9401目录。目录中存在URN表示它是有效的。
Scope:
范围：
Global
全球的
The following examples are not guaranteed to be real. They are listed for pedagogical reasons only.
以下示例不能保证是真实的。它们仅出于教学原因列出。
urn:oasis:names:specification:docbook:dtd:xml:4.1.2
urn:oasis:names:tc:docbook:dtd:xml:docbook:5.0b1
urn:oasis:names:technical:memo:9502:1995
urn:oasis:member:A00024:x
urn:oasis:names:specification:docbook:dtd:xml:4.1.2
urn:oasis:names:tc:docbook:dtd:xml:docbook:5.0b1
urn:oasis:names:technical:memo:9502:1995
urn:oasis:member:A00024:x
There are no additional security considerations other than those normally associated with the use and resolution of URNs in general.
除了通常与使用和解决骨灰盒相关的安全注意事项外，没有其他安全注意事项。
References
工具书类
[1] Goldfarb, C. F., "ISO (International Organization for Standardization) ISO 8879:1986(E) Information Processing -- Text and Office Systems -- Standard Generalized Markup Language (SGML)", 1986.
[1] Goldfarb，C.F.，“ISO（国际标准化组织）ISO 8879:1986（E）信息处理——文本和办公系统——标准通用标记语言（SGML）”，1986年。
[2] W3C, XML WG, "Extensible Markup Language (XML) 1.0", February 1998, <http://www.w3.org/TR/REC-xml>.
[2] W3C，XML工作组，“可扩展标记语言（XML）1.0”，1998年2月<http://www.w3.org/TR/REC-xml>.
[3] W3C, Namespaces WG, "Namespaces in XML", January 1999, <http://www.w3.org/TR/REC-xml-names>.
[3] W3C，名称空间工作组，“XML中的名称空间”，1999年1月<http://www.w3.org/TR/REC-xml-names>.
[4] OASIS, Entity Mgmt. TC, "Entity Management: OASIS Technical Resolution 9401:1997 (Amendment 2 to TR 9401)", January 1994, <http://www.oasis-open.org/html/a401.htm>.
[4] 绿洲，实体管理。TC，“实体管理：OASIS技术决议9401:1997（TR 9401修正案2）”，1994年1月<http://www.oasis-open.org/html/a401.htm>.
[5] Moats, R., "URN Syntax", RFC 2141, May 1997.
[5] 护城河，R.，“瓮语法”，RFC 21411997年5月。
[6] Mealling, M. and R. Daniel, "URI Resolution Services Necessary for URN Resolution", RFC 2483, January 1999.
[6] Mealling，M.和R.Daniel，“URN解析所需的URI解析服务”，RFC 2483，1999年1月。
Authors' Addresses
作者地址
Karl Best OASIS, Inc. P.O. Box 455 Billerica, MA 01821 US
美国马萨诸塞州比尔里卡市卡尔贝斯特绿洲公司邮政信箱455号邮编01821
EMail: karl.best@oasis-open.org
EMail: karl.best@oasis-open.org
Norman Walsh Sun Microsystems, Inc. One Network Drive MS UBUR02-201 Burlington, MA 01803-0902 US
美国马萨诸塞州伯灵顿市诺曼沃尔什太阳微系统公司一号网络驱动器MS UBUR02-201邮编01803-0902
EMail: Norman.Walsh@East.Sun.COM
EMail: Norman.Walsh@East.Sun.COM
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
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 assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
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编辑功能的资金目前由互联网协会提供。