Network Working Group R. Morgan
Request for Comments: 3613 Univ. of Washington
Category: Informational K. Hazelton
Univ. of Wisconsin-Madison
October 2003
Network Working Group R. Morgan
Request for Comments: 3613 Univ. of Washington
Category: Informational K. Hazelton
Univ. of Wisconsin-Madison
October 2003
Definition of a Uniform Resource Name (URN) Namespace for the Middleware Architecture Committee for Education (MACE)
中间件体系结构教育委员会（MACE）统一资源名（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 (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
Abstract
摘要
This document describes a Uniform Resource Name (URN) namespace for the Internet2 Middleware Architecture Committee for Education (MACE). This namespace is for naming persistent resources defined by MACE, its working groups and other designated subordinates.
本文档描述了Internet2教育中间件体系结构委员会（MACE）的统一资源名（URN）命名空间。此名称空间用于命名由MACE、其工作组和其他指定下属定义的持久资源。
The Internet2 Middleware Architecture Committee for Education (MACE) produces many kinds of documents: specifications, working drafts, object classes, schemas, stylesheets, etc. It also defines directory attributes and controlled vocabularies for the values of some of those attributes.
Internet2教育中间件体系结构委员会（MACE）生成多种文档：规范、工作草案、对象类、模式、样式表等。它还为某些属性的值定义目录属性和受控词汇表。
MACE wishes to provide global, distributed, persistent, location-independent names for these resources. The Uniform Resource Name (URN) variant of URIs meets these requirements.
MACE希望为这些资源提供全局、分布式、持久、位置独立的名称。URI的统一资源名（URN）变体满足这些要求。
MACE working groups and other MACE-affiliated groups will benefit from the MACE URN namespace by having an easy, efficient way to assign globally unique, persistent identifiers to resources that they create. The nature of MACE work is that serves the needs of one or more communities of interest. A namespace managed so as to facilitate the creation, registration and resolution of unique, persistent identifiers will be of great value for MACE, its affiliates and the higher education community generally.
MACE工作组和其他MACE附属组将受益于MACE URN名称空间，因为它们可以通过一种简单、高效的方式为所创建的资源分配全局唯一、持久的标识符。MACE工作的本质是服务于一个或多个感兴趣社区的需要。对命名空间进行管理，以便于创建、注册和解析唯一的持久标识符，这对MACE、其附属公司和高等教育界都具有重大价值。
This URN namespace specification is for a formal namespace.
此URN命名空间规范适用于正式命名空间。
Namespace ID:
命名空间ID:
"mace"
“狼牙棒”
Registration Information:
注册资料：
Registration Version Number 1
注册版本号1
Registration Date: 2003-08-01
注册日期：2003-08-01
Registrant of the namespace:
名称空间的注册人：
Middleware Architecture Committee for Education (MACE) ATTN: Lisa Hogeboom Internet2 3025 Boardwalk Suite 200 Ann Arbor, MI 48108
教育中间件体系结构委员会（MACE）收件人：Lisa Hogeboom Internet2 3025木板路套房200安娜堡，密苏里州48108
Phone: +1 734 913 4250
电话：+1734 913 4250
Contact: Keith Hazelton
联系人：基思·哈泽尔顿
Affiliation: Univ. of Wisconsin-Madison 1210 W. Dayton St. Madison, WI 53706 Phone: +1 608 262 0771
附属机构：威斯康星大学麦迪逊分校，威斯康星州麦迪逊市代顿街西1210号，邮编53706电话：+1608 262 0771
hazelton@doit.wisc.edu
hazelton@doit.wisc.edu
Syntactic structure:
句法结构：
The Namespace Specific Strings (NSS) of all URNs assigned by MACE will conform to the syntax defined in section 2.2 of RFC 2141, "URN Syntax" [1]. In addition, all MACE URN NSSs will consist of a left-to-right series of tokens delimited by colons. The left-to-right sequence of colon-delimited tokens corresponds to descending nodes in a tree. To the right of the lowest naming authority node there may be zero, one or more levels of hierarchical naming nodes terminating in a rightmost leaf node. See the section entitled "Identifier assignment" below for more on the semantics of NSSs. This syntax convention is captured in the following normative ABNF rules for MACE NSSs (see RFC 2234) [2]:
MACE分配的所有URN的命名空间特定字符串（NSS）将符合RFC 2141第2.2节“URN语法”[1]中定义的语法。此外，所有MACE URN NSS将由一系列由左至右用冒号分隔的标记组成。从左到右的冒号分隔标记序列对应于树中的降序节点。在最低命名机构节点的右侧，可能有零个、一个或多个层次的命名节点终止于最右侧的叶节点。有关NSS语义的更多信息，请参阅下面标题为“标识符分配”的部分。MACE NSS的以下规范性ABNF规则（见RFC 2234）[2]中包含了这种语法约定：
MACE-NSS = 1*(subStChar) 0*(":" 1*(subStChar))
MACE-NSS = 1*(subStChar) 0*(":" 1*(subStChar))
subStChar = trans / "%" HEXDIG HEXDIG
subschar=trans/“%”HEXDIG HEXDIG
trans = ALPHA / DIGIT / other / reserved
trans = ALPHA / DIGIT / other / reserved
other = "(" / ")" / "+" / "," / "-" / "." /
other = "(" / ")" / "+" / "," / "-" / "." /
"=" / "@" / ";" / "$" /
"=" / "@" / ";" / "$" /
"_" / "!" / "*" / "'"
"_" / "!" / "*" / "'"
reserved = "%" / "/" / "?" / "#"
reserved = "%" / "/" / "?" / "#"
The exclusion of the colon from the list of "other" characters means that the colon can only occur as a delimiter between string tokens. Note that this ABNF rule set guarantees that any valid MACE NSS is also a valid RFC 2141 NSS.
从“其他”字符列表中排除冒号意味着冒号只能作为字符串标记之间的分隔符出现。请注意，此ABNF规则集保证任何有效的MACE NSS也是有效的RFC 2141 NSS。
Relevant ancillary documentation:
相关辅助文件：
None.
没有一个
Identifier uniqueness:
标识符唯一性：
It is the responsibility of MACE directors to guarantee uniqueness of the names of immediately subordinate naming authorities. Each lower-level naming authority in turn inherits the responsibility of guaranteeing uniqueness of names in their branch of the naming tree.
MACE董事有责任确保直接下属命名机构名称的唯一性。每个较低级别的命名机构依次继承了保证其命名树分支中名称唯一性的责任。
Identifier persistence:
标识符持久性：
MACE directors bear ultimate responsibility for maintaining the usability of MACE URNs over time. This responsibility may be delegated to subordinate naming authorities per the discussion in the section below on identifier assignment. That section provides a mechanism for the delegation to be revoked in case a subordinate naming authority ceases to function.
随着时间的推移，MACE主管对维护MACE骨灰盒的可用性负有最终责任。根据下文关于标识符分配一节中的讨论，可将此职责委托给下级命名机构。该部分提供了一种机制，以便在下级命名机构停止运行时撤销委托。
Identifier assignment:
标识符分配：
MACE directors will create an initial series of immediately subordinate naming authorities, and will define a process for adding to that list of authorities. Each top-level working group of MACE will be invited to designate a naming authority and to suggest one or more candidate names for that authority. The MACE-Shibboleth group, for example, might propose creating a
MACE主管将创建一系列直接下属命名机构，并定义一个添加到该机构列表中的流程。将邀请MACE的每个顶级工作组指定一个命名机构，并为该机构推荐一个或多个候选名称。例如，梅斯·希伯利斯集团（MaceShibboleth group）可能会提议创建一个
naming authority under "urn:mace:shib," "urn:mace:shibboleth" or some other name.
“urn:mace:shib”、“urn:mace:shibboleth”或其他名称下的命名权限。
Institutions and communities affiliated with MACE may request, through their designated MACE liaison, that they be granted MACE-subordinate naming authority status. They may propose candidate names for that authority. One way for such entities to guarantee uniqueness of their proposed name is to base it on a DNS name. That is, if Georgetown University wished to be designated a subordinate naming authority under MACE, the institutional MACE liaison could propose to MACE directors that they be delegated control over names beginning with "urn:mace:georgetown.edu". Institutions seeking affiliation with MACE should send email to mace-submit@internet2.edu, nominating an institutional liaison and providing contact information for that person.
隶属于MACE的机构和社区可通过其指定的MACE联络人请求授予其MACE下属命名机构地位。他们可以提出该机构的候选人名单。此类实体保证其提议名称唯一性的一种方法是基于DNS名称。也就是说，如果乔治敦大学希望被指定为MACE的下属命名机构，则机构MACE联络人可以向MACE董事提议，授权他们控制以“urn:MACE:Georgetown.edu”开头的名称。寻求加入MACE的机构应向MACE发送电子邮件-submit@internet2.edu，提名一名机构联络人，并为此人提供联系信息。
On at least an annual basis, MACE directors will contact the liaisons or directors of each immediately subordinate naming authority. If there is no response, or if the respondent indicates that they wish to relinquish naming authority, the authority over that branch of the tree reverts to MACE. This process will be enforced recursively by each naming authority on its subordinates. This process guarantees that responsibility for each branch of the tree will lapse for less than one year at worst before being reclaimed by a superior authority.
MACE董事将至少每年联系一次各直属命名机构的联络人或董事。如果没有回应，或者如果回应者表示他们希望放弃命名权，则对该树枝的权限将恢复为MACE。此过程将由其下属的每个命名机构递归执行。这一过程保证了在上级当局收回树木之前，树木每一个分支的责任最坏情况下将失效不到一年。
Lexical equivalence of two MACE namespace specific strings (NSSs) is defined below as an exact, case-sensitive string match. MACE will assign names of immediately subordinate naming authorities in a case-insensitive fashion, so that there will not be two MACE-subordinate naming authorities whose names differ only in case.
下面将两个MACE命名空间特定字符串（NSSs）的词汇等价性定义为精确的、区分大小写的字符串匹配。MACE将以不区分大小写的方式分配直接下属命名机构的名称，这样就不会有两个MACE下属命名机构的名称仅在大小写上有所不同。
Identifier resolution:
标识符解析：
MACE directors will maintain an index of all MACE and MACE workgroup assigned URNs at the web site http://middleware.internet2.edu/urn-mace/urn-mace.html. That index will map URNs to resource identifiers or resource specifications (e.g., protocol parameters). MACE-affiliated naming authorities will specify how to resolve the URNs they assign if they are resolvable.
MACE主管将在网站上维护所有MACE和MACE工作组分配的URN的索引http://middleware.internet2.edu/urn-mace/urn-mace.html. 该索引将URN映射到资源标识符或资源规范（例如，协议参数）。MACE附属命名机构将指定如何解析其分配的骨灰盒（如果它们是可解析的）。
Lexical equivalence:
词汇对等：
Lexical equivalence of two MACE namespace specific strings (NSSs) is defined as an exact, case-sensitive string match.
两个MACE命名空间特定字符串（NSSs）的词汇等价性定义为精确的、区分大小写的字符串匹配。
Conformance with URN syntax:
符合URN语法：
All MACE NSSs fully conform to RFC 2141 syntax rules for NSSs.
所有MACE NSS完全符合NSS的RFC 2141语法规则。
Validation mechanism:
验证机制：
As specified in the "Identifier resolution" section above, MACE directors will maintain an index of all MACE and MACE workgroup assigned URNs on its web site, http://middleware.internet2.edu/urn-mace/urn-mace.html. Presence in that index implies that a given URN is valid. MACE-affiliated naming authorities will specify how to validate the URNs they assign.
如上文“标识符解析”部分所述，MACE主管将在其网站上维护所有MACE和MACE工作组分配的URN的索引，http://middleware.internet2.edu/urn-mace/urn-mace.html. 该索引中的存在意味着给定的URN是有效的。MACE附属命名机构将指定如何验证其分配的URN。
Scope:
范围：
Global.
全球的
There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general.
除了通常与骨灰盒的使用和解析相关的安全注意事项外，没有其他安全注意事项。
Registration of an NID specific to MACE is reasonable given the following considerations:
考虑到以下因素，登记MACE特定的NID是合理的：
1. MACE would like to assign URNs to some very fine-grained objects (such as specific controlled vocabulary values of an attribute in MACE-defined LDAP object classes). This does not seem to be the primary intended use of the XMLORG namespace (RFC 3120) [3], let alone the more tightly controlled OASIS namespace (RFC 3121) [4].
1. MACE希望将URN分配给一些非常细粒度的对象（例如MACE定义的LDAP对象类中属性的特定受控词汇表值）。这似乎不是XMLORG名称空间（RFC3120）[3]的主要预期用途，更不用说更严格控制的OASIS名称空间（RFC3121）[4]。
2. MACE seeks naming autonomy. We understand that the XMLORG registrants left the door open to subordinate naming authorities, "OASIS may assign portions of its XMLORG namespace for assignment by other parties" (RFC 3120) [3], but there is no specified process for such assignment. That would in any case mean having a fixed XMLORG-assigned prefix on every single object to which we assign a URN. MACE has a number of active work groups that may well generate a growing number of subordinate naming authorities. Moreover, MACE is not a member of OASIS, so becoming a subordinate naming authority under the OASIS URN space is currently not an option.
2. 梅斯寻求命名自主权。我们了解到，XMLORG注册人向下级命名机构敞开了大门，“OASIS可以将其XMLORG名称空间的一部分分配给其他方”（RFC 3120）[3]，但没有指定的分配流程。这在任何情况下都意味着在我们分配URN的每个对象上都有一个固定的XMLORG分配前缀。MACE有许多活跃的工作组，这些工作组很可能产生越来越多的下属命名机构。此外，MACE不是OASIS的成员，因此成为OASIS URN空间下的下属命名机构目前不是一个选项。
3. MACE will want to assign URNs to non-XML objects as well. That is another reason that XMLORG may not be an appropriate higher-level naming authority for MACE.
3. MACE还希望将URN分配给非XML对象。这是XMLORG可能不是MACE的合适的更高级别命名机构的另一个原因。
Some MACE-developed schema and namespaces may be good candidates for inclusion in the XMLORG registry. The fact that such an object might already have a MACE-assigned URN shouldn't be a hindrance. Work is in progress to update RFC 2611 [5], which includes an explicit statement that two or more URNs may point to the same resource. A resource with a MACE-assigned namespace-specific-string would, of course, be given an XMLORG namespace-specific-string at the time it enters the XMLORG registry.
一些MACE开发的模式和名称空间可能很适合包含在XMLORG注册表中。事实上，这样一个物体可能已经被分配了一个狼牙棒瓮，这不应该成为一个障碍。更新RFC 2611[5]的工作正在进行中，其中包括两个或多个URN可能指向同一资源的明确声明。当然，具有MACE分配的命名空间特定字符串的资源在进入XMLORG注册表时将获得一个XMLORG命名空间特定字符串。
The IANA has formally registered URN namespace 13 to MACE, within the IANA registry of URN NIDs.
IANA已在URN NIDs的IANA注册中心向MACE正式注册了URN名称空间13。
[1] Moats, R., "URN Syntax", RFC 2141, May 1997.
[1] 护城河，R.，“瓮语法”，RFC 21411997年5月。
[2] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[2] Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。
[3] Best, K. and N. Walsh, "A URN Namespace for XML.org", RFC 3120, June 2001.
[3] Best，K.和N.Walsh，“XML.org的URN名称空间”，RFC31202001年6月。
[4] Best, K. and N. Walsh, "A URN Namespace for OASIS", RFC 3121, June 2001.
[4] 贝斯特，K.和N.沃尔什，“绿洲的瓮名称空间”，RFC31212001年6月。
[5] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611, June 1999.
[5] Daigle，L.，van Gulik，D.，Iannella，R.和P.Faltstrom，“URN名称空间定义机制”，BCP 33，RFC 2611，1999年6月。
RL "Bob" Morgan 4545 15th Ave. NE Seattle, WA 98105 U.S.A.
美国华盛顿州西雅图东北第15大道4545号RL“Bob”Morgan 98105。
EMail: rlmorgan@washington.edu
EMail: rlmorgan@washington.edu
Keith D. Hazelton University of Wisconsin-Madison 1210 W. Dayton St. Madison, WI 53706 U.S.A.
基思D哈泽尔顿威斯康星大学麦迪逊1210 W戴顿圣麦迪逊，WI 53706美国。
EMail: hazelton@doit.wisc.edu
EMail: hazelton@doit.wisc.edu
Copyright (C) The Internet Society (2003). All Rights Reserved.
版权所有（C）互联网协会（2003年）。版权所有。
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编辑功能的资金目前由互联网协会提供。