Internet Engineering Task Force (IETF) V. Giralt
Request for Comments: 6338 Univ. Malaga
Category: Informational R. McDuff
ISSN: 2070-1721 Univ. Queensland
August 2011
Internet Engineering Task Force (IETF) V. Giralt
Request for Comments: 6338 Univ. Malaga
Category: Informational R. McDuff
ISSN: 2070-1721 Univ. Queensland
August 2011
Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC)
学术界架构（SCAC）的统一资源名称（URN）命名空间的定义
Abstract
摘要
This document describes a Uniform Resource Name (URN) namespace for the Schema for Academia (SCHAC).
本文档描述了学术模式（SCAC）的统一资源名称（URN）命名空间。
The namespace described in this document is for naming persistent resources defined by the SCHAC participants internationally, their working groups, and other designated subordinates. The main use of this namespace will be for the creation of controlled vocabulary values for attributes in the SCHAC schema. These values will be associated with particular instances of persons or objects belonging to any of the SCHAC object classes.
本文档中描述的名称空间用于命名SCAC国际参与者、其工作组和其他指定下属定义的持久资源。该名称空间的主要用途是为SCHAC模式中的属性创建受控词汇表值。这些值将与属于任何SCAC对象类的人员或对象的特定实例相关联。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6338.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6338.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
The Schema for Academia (SCHAC) international activity was born inside the Task Force on European Middleware Coordination and Collaboration (TF-EMC2) of the Trans-European Research and Education Networking Association (TERENA) [6]. The initial aim of SCHAC was to harmonize the disjoint person schemas of the participating countries in order to have a common way for expressing data about persons, exchanged between educational organizations. SCHAC, as are other person schemas, is designed to ease the sharing of information about a given individual between parties, mostly, but not limited to, educational and research institutions. The main aims of this sharing are to provide resources to individuals and to allow said individuals to move, virtually and physically, between such institutions. Thus, the SCHAC schema was defined with input from all participants' national person schemas [7].
学术界模式（SCHC）国际活动诞生于泛欧研究和教育网络协会（TERENA）[6]的欧洲中间件协调与协作工作组（TF-EMC2）内。SCHC的最初目的是协调参与国不相交的人员模式，以便有一种共同的方式来表达教育组织之间交换的人员数据。与其他人模式一样，SCAC旨在简化各方（主要是但不限于教育和研究机构）之间关于特定个人的信息共享。这种共享的主要目的是为个人提供资源，并允许上述个人在此类机构之间进行虚拟和实际的移动。因此，SCAC模式是由所有参与者的国民人格模式输入定义的[7]。
SCHAC does not supplant other person schemas such as organizationalPerson [8], inetOrgPerson [9], or eduPerson [10]; it extends those where needed for the purposes of Higher Education outside the United States. This characteristic has made SCHAC, originally a European effort, useful for groups outside Europe.
SCHAC不会取代其他人模式，如organizationalPerson[8]、inetOrgPerson[9]或eduPerson[10]；它在美国以外的高等教育领域扩展了那些需要的领域。这一特点使得最初是欧洲努力的SCAC对欧洲以外的团体非常有用。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [1].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[1]中所述进行解释。
Namespace ID:
命名空间ID:
schac
沙克
Registration Information:
注册资料：
Registration Version Number 1
注册版本号1
Registration Date: 2011-06-22
注册日期：2011-06-22
Registrant of the namespace:
名称空间的注册人：
European Committee for Academic Middleware (ECAM) Trans-European Research and Education Networking Association (TERENA) Singel Amsterdam The Netherlands
欧洲学术中间件委员会（ECAM）泛欧研究和教育网络协会（TERENA）荷兰阿姆斯特丹Singel
Designated contacts:
指定联系人：
Contact: Licia Florio Affiliation: TERENA Singel 468 D Amsterdam, 1017 AW The Netherlands
联系人：Licia Florio附属机构：荷兰首都阿姆斯特丹第468 D街TERENA Singel
EMail: florio@terena.org
Phone: +31(0)20 5304488
EMail: florio@terena.org
Phone: +31(0)20 5304488
Contact: Victoriano Giralt Affiliation: University of Malaga Central ICT Services Blvd. Louis Pasteur, 33 Campus de Teatinos 29071 Malaga Spain
联系：Victoriano Giralt附属：马拉加大学中央ICT服务BLVD。路易斯巴斯德，西班牙马拉加市蒂蒂诺斯校区33号，邮编29071
EMail: victoriano@uma.es
Phone: +34 95 213 1415
EMail: victoriano@uma.es
Phone: +34 95 213 1415
Syntactic structure:
句法结构：
The Namespace Specific Strings (NSSs) of all URNs assigned by SCHAC will conform to the syntax defined in Section 2.2 of RFC 2141, "URN Syntax" [11]. In addition, all SCHAC 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 "Identifier assignment" section below for more on the semantics of NSSs. This syntax convention is captured in the following normative ABNF rules for SCHAC NSSs (see RFC 5234 [2]):
SCAC分配的所有URN的命名空间特定字符串（NSS）将符合RFC 2141第2.2节“URN语法”[11]中定义的语法。此外，所有SCAC URN NSS将由一系列由左至右用冒号分隔的标记组成。从左到右的冒号分隔标记序列对应于树中的降序节点。在最低命名机构节点的右侧，可能有零级、一级或多级分层命名节点终止于最右侧的叶节点。有关NSS语义的更多信息，请参见下面的“标识符分配”部分。该语法约定包含在以下针对SCHC NSSs的规范性ABNF规则中（参见RFC 5234[2]）：
SCHAC-NSS = 1*subStChar *( ":" 1*subStChar )
SCHAC-NSS = 1*subStChar *( ":" 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 SCHAC NSS is also a valid RFC 2141 NSS.
从“其他”字符列表中排除冒号意味着冒号只能作为字符串标记之间的分隔符出现。请注意，此ABNF规则集保证任何有效的SCHC NSS也是有效的RFC 2141 NSS。
Relevant ancillary documentation:
相关辅助文件：
None.
没有一个
Identifier uniqueness:
标识符唯一性：
It is the responsibility of TERENA 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 its branch of the naming tree.
TERENA有责任保证直接下属命名机构名称的唯一性。每个较低级别的命名机构依次继承了保证其命名树分支中名称唯一性的责任。
Identifier persistence:
标识符持久性：
TERENA bears ultimate responsibility for maintaining the usability of SCHAC 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 the case where a subordinate naming authority ceases to function.
随着时间的推移，TERENA承担着维护SCAC骨灰盒可用性的最终责任。根据下文关于标识符分配一节中的讨论，可将此职责委托给下级命名机构。该节规定了在下级命名机构停止运作的情况下撤销授权的机制。
Identifier assignment:
标识符分配：
TERENA will create an initial series of immediately subordinate naming authorities, and will define a process for adding to that list of authorities. Such a list, and the policy for adding to it, will be published at the root registry page. Each country with a representative in SCHAC will be invited to designate a naming authority. Country-specific namespaces based on the country Internet Top-Level Domain (TLD) [12] will then be assigned to the designated authority. The subordinated namespaces int and eu will remain under TERENA authority, controlled by the SCHAC activity members, for entities of global, international, or European interest. There is also the possibility of granting subordinate namespaces to multi-country organizations; in this case, the organizational Internet Fully Qualified Domain Name (FQDN) will be used as the prefix.
TERENA将创建一系列直接下属的命名机构，并定义一个添加到该机构列表的过程。这样的列表及其添加策略将在根注册表页面上发布。每个在SCAC中有代表的国家将被邀请指定一个命名机构。然后，基于国家互联网顶级域（TLD）[12]的国家特定名称空间将分配给指定机构。对于具有全球、国际或欧洲利益的实体，附属名称空间int和eu仍将由SCAC活动成员控制的TERENA管理局管理。还可以向多国组织授予从属名称空间；在这种情况下，将使用组织Internet完全限定域名（FQDN）作为前缀。
As an example, a European-level interest entity would be any value related to information used in the Higher Education European Space, or the so-called Bologna process. Such entities will belong in the eu subordinate namespace.
例如，欧洲层面的利益实体可以是与欧洲高等教育空间或所谓博洛尼亚过程中使用的信息相关的任何价值。此类实体将属于eu从属名称空间。
Global international entities could encompass values related to the Grid community or values useful both for some European and for some Australian universities. Such entities would belong in the int subordinate namespace.
全球国际实体可以包含与网格社区相关的价值观，或者对一些欧洲大学和一些澳大利亚大学都有用的价值观。这些实体将属于int从属名称空间。
Examples of multi-country organizations include TERENA itself or an association like the Educational Policy Institute (EPI) (educationalpolicy.org) that has members from Australia, Canada, and the US.
多国组织的例子包括TERENA本身或教育政策研究所（EPI）（educationalpolicy.org）等协会，其成员来自澳大利亚、加拿大和美国。
URNs intended for values of SCHAC attributes will include the attribute name immediately after the NSS prefix, before any geographical namespace delegation, such that any string can convey information about the attribute for which it is a value. For example, values for schacUserStatus will be of the form:
用于SCHC属性值的URN将在任何地理名称空间委派之前，在NSS前缀之后立即包含属性名称，这样，任何字符串都可以传递有关其为值的属性的信息。例如，schacUserStatus的值将采用以下形式：
urn:schac:userStatus:int
urn:schac:userStatus:au or
urn:schac:userStatus:terena.org
urn:schac:userStatus:int
urn:schac:userStatus:au or
urn:schac:userStatus:terena.org
If at all possible, automated registry publication mechanisms will be provided, based on the work on distributed URN registries done by the TF-EMC2 task force members.
如果可能的话，将根据TF-EMC2工作队成员所做的分布式URN注册工作，提供自动注册发布机制。
Institutions and communities affiliated with SCHAC participants may request that they be granted subordinate naming authority status. Uniqueness of these namespaces under country authority will be based on the requestor's Internet FQDN. This subordination procedure SHOULD be carried along the delegation chain; i.e., if at all possible, all entities that receive a delegated namespace MUST have a valid FQDN and MUST publish an Internet accessible URN value registry, based on the URN registry mechanisms designed by the TF-EMC2 task force members.
SCAC参与者的附属机构和社区可要求授予其下属命名机构身份。国家/地区授权下这些名称空间的唯一性将基于请求者的Internet FQDN。这种从属程序应该沿着委托链进行；i、 例如，如果可能，所有接收委派命名空间的实体必须具有有效的FQDN，并且必须根据TF-EMC2工作组成员设计的URN注册表机制发布可通过互联网访问的URN值注册表。
On at least an annual basis, TERENA 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 TERENA. 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.
TERENA将至少每年联系一次各直属命名机构的联络人或董事。如果没有回应，或者如果回应者表示他们希望放弃命名权，则对该树枝的权限将恢复为TERENA。此过程将由其下属的每个命名机构递归执行。这一过程保证了每一棵树的责任在被上级当局收回之前，最坏的情况下，将在不到一年的时间内失效。
Lexical equivalence of two SCHAC Namespace Specific Strings (NSSs) is defined below as an exact, case-sensitive string match. TERENA will assign names of immediately subordinate naming authorities in lowercase only. This forestalls the registration of two SCHAC-subordinate naming authorities whose names differ only in case. Attribute names will use the same mixed-case format as in the schema definition.
两个特定于SCHAC名称空间的字符串（NSSs）的词汇等价性定义如下：精确的、区分大小写的字符串匹配。TERENA将仅以小写字母指定直接下属命名机构的名称。这阻止了两个SCAC下属命名机构的注册，其名称仅在案例中有所不同。属性名称将使用与模式定义中相同的大小写混合格式。
Identifier resolution:
标识符解析：
The namespace is not currently listed with a Resolution Discovery System (RDS), but nothing about the namespace prohibits the future definition of appropriate resolution methods or listing with an RDS.
名称空间当前未与解析发现系统（RDS）一起列出，但名称空间的任何内容都不禁止将来定义适当的解析方法或与RDS一起列出。
TERENA will maintain a registry of all SCHAC-assigned URN values, both final and for delegation, on its web site:
TERENA将在其网站上维护所有SCAC分配的URN值（最终值和授权值）的注册表：
https://urnreg.terena.org/
https://urnreg.terena.org/
Delegation entries will have a pointer to the registry of the subordinate naming authority. This SHOULD recurse down the delegation tree, but registries for several delegated namespaces MAY be maintained by a single naming authority.
委派条目将有一个指向下级命名机构注册表的指针。这应该沿着委托树递归，但是多个委托名称空间的注册表可以由一个命名机构维护。
All registries MUST publish their URNs over https links [3]. The https links MUST be secured by sites offering credentials signed by a SCHAC-community recognized Certification Authority (CA) using the latest secure methods for accessing a web site (which at present is the latest version of Transport Layer Security (TLS) [4]). Registries SHOULD consider the user interface implications of their choice of CA, taking into account issues like browser alerts and blind trust.
所有注册中心都必须通过https链接发布其URN[3]。https链接必须由提供由SCAC社区认可的证书颁发机构（CA）签署的凭据的站点进行安全保护，使用最新的安全方法访问网站（目前是传输层安全性（TLS）[4]的最新版本）。注册中心应该考虑他们选择CA的用户界面含义，考虑到浏览器警报和盲目信任等问题。
Lexical equivalence:
词汇对等：
Lexical equivalence of two SCHAC Namespace Specific Strings (NSSs) is defined as an exact, case-sensitive string match.
两个SCAC命名空间特定字符串（NSSs）的词法等价性定义为精确的、区分大小写的字符串匹配。
Conformance with URN syntax:
符合URN语法：
All SCHAC NSSs fully conform to RFC 2141 syntax rules for NSSs.
所有SCHC NSS完全符合NSS的RFC 2141语法规则。
Validation mechanism:
验证机制：
As specified in the "Identifier resolution" section above, TERENA will maintain an index of all SCHAC-assigned URNs on its web site: https://urnreg.terena.org/. Presence in that registry or in any subordinate registry implies that a given URN is valid. Delegated naming authorities MUST guarantee that values are valid in their assigned spaces.
如上文“标识符解析”部分所述，TERENA将在其网站上维护所有SCAC分配的URN的索引：https://urnreg.terena.org/. 在该注册表或任何下级注册表中的存在意味着给定的URN是有效的。委派的命名权限必须保证值在其指定的空间中有效。
Scope:
范围：
Global.
全球的
The following examples are not guaranteed to be real. They are listed for pedagogical reasons only.
以下示例不能保证是真实的。它们仅出于教学原因列出。
urn:schac:personalUniqueID:es:DNI:9999999Z
urn:schac:personalUniqueCode:es:uma.es:codUni:061696758X
urn:schac:userStatus:au:uq.edu.au:service:mail:receive:disabled
urn:schac:personalPosition:pl:umk.pl:programmer
urn:schac:personalUniqueID:es:DNI:9999999Z
urn:schac:personalUniqueCode:es:uma.es:codUni:061696758X
urn:schac:userStatus:au:uq.edu.au:service:mail:receive:disabled
urn:schac:personalPosition:pl:umk.pl:programmer
There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general.
除了通常与骨灰盒的使用和解析相关的安全注意事项外，没有其他安全注意事项。
In order to guarantee the validity and origin of SCHAC-NSS URN values, they MUST be published over https links [3]. The https links MUST be secured by sites offering credentials signed by a SCHAC-community recognized Certification Authority (CA) using the latest secure methods for accessing a web site (which at present is the latest version of TLS [4]).
为了保证SCAC-NSS URN值的有效性和来源，它们必须通过https链接发布[3]。https链接必须由提供由SCAC社区认可的证书颁发机构（CA）签署的凭据的网站进行保护，这些证书使用最新的安全方法访问网站（目前是TLS的最新版本[4]）。
Registration of a Namespace Identifier (NID) specific to SCHAC is reasonable given the following considerations:
考虑到以下因素，注册特定于SCAC的命名空间标识符（NID）是合理的：
SCHAC would like to assign URNs to some very fine-grained objects. This does not seem to be the primary intended use of the XML.org namespace (RFC 3120) [13], or the more tightly controlled Organization for the Advancement of Structured Information Standards (OASIS) [14] namespace (RFC 3121) [15].
SCHAC希望将URN分配给一些非常细粒度的对象。这似乎不是XML.org名称空间（RFC 3120）[13]或更严格控制的结构化信息标准促进组织（OASIS）[14]名称空间（RFC 3121）[15]的主要预期用途。
SCHAC seeks naming autonomy. SCHAC is not a member of OASIS, so becoming a subordinate naming authority under the OASIS URN space is not an option. There is the MACE (Middleware Architecture Committee for Education) (RFC 3613) [16] namespace, but the SCHAC development is done outside of the MACE activity scope; thus, the attributes and values do not belong in the MACE namespace. Using the MACE namespace requires that the SCHAC namespace be placed under one of the SCHAC participants' namespaces, which hinders its global scope.
SCHAC寻求命名自主。SCHC不是OASIS的成员，因此成为OASIS URN空间下的下属命名机构不是一个选项。存在MACE（教育中间件体系结构委员会）（RFC 3613）[16]名称空间，但SCAC开发在MACE活动范围之外进行；因此，属性和值不属于MACE名称空间。使用MACE名称空间需要将SCAC名称空间放在SCAC参与者的名称空间之一下，这会妨碍其全局范围。
SCHAC will want to assign URNs to non-XML objects as well. That is another reason that XML.org may not be an appropriate higher-level naming authority for SCHAC.
SCHAC还希望将URN分配给非XML对象。这是XML.org可能不是SCHAC的合适的更高级别命名机构的另一个原因。
Some of the already defined SCHAC attribute values have been assigned URNs under the urn:mace:terena.org namespace. These values will enter a deprecation cycle, with a clear indication that they will be replaced by values under the new namespace once it is assigned. In any case, RFC 3406 [5] (which replaced RFC 2611) includes an explicit statement that two or more URNs may point to the same resource.
一些已定义的SCHC属性值已在urn:mace:terena.org命名空间下分配了urn。这些值将进入一个弃用周期，并明确表示一旦分配新名称空间，它们将被新名称空间下的值替换。在任何情况下，RFC 3406[5]（取代了RFC 2611）都包含一条明确的语句，即两个或多个URN可能指向同一资源。
The assignment and use of identifiers within the namespace are open, and the related rule is established by the SCHAC activity members. Registration agencies (the next-level naming authorities) will be the National Research and Education Networks (NRENs) and established organizational cross-border organizations that participate in SCHAC.
命名空间中标识符的分配和使用是开放的，相关规则由SCAC活动成员建立。注册机构（下一级命名机构）将是国家研究和教育网络（NREN）和参与SCAC的已建立的跨境组织。
It is expected that the majority of the European NRENs, their constituencies, participants in the Australian Access Federation, and some other international activities will make use of the SCHAC namespace.
预计大多数欧洲NREN、其选区、澳大利亚访问联合会的参与者以及其他一些国际活动将使用SCAC名称空间。
After the establishment of the SCHAC namespace, TERENA will establish a registry service (analogously to other distributed pan-European services, such as eduroam, PerfSONAR, etc.) for the namespace clients. This registry will be available via the root page of the namespace: https://urnreg.terena.org/. The policy for registrations will be defined in documents available at the root page of the registry.
在SCHAC名称空间建立之后，TERENA将为名称空间客户端建立一个注册表服务（类似于其他分布式泛欧服务，如eduroam、PerfSONAR等）。此注册表将通过命名空间的根页面提供：https://urnreg.terena.org/. 注册策略将在注册表根页面上的可用文档中定义。
In accordance with BCP 66 [5], IANA has registered the Formal URN Namespace 'schac' in the Registry of URN Namespaces, using the registration template presented in Section 2 of this document.
根据BCP 66[5]，IANA已使用本文件第2节中提供的注册模板在URN名称空间注册表中注册了正式的URN名称空间“schac”。
SCHAC is the result of the TERENA TF-EMC2 task force and many others that have contributed ideas to the development of the schema.
SCHAC是TERENA TF-EMC2特别工作组和许多其他人的成果，他们为模式的开发提供了想法。
This document was discussed on the URN-NID list, with the special help of Alfred Hoenes, who thoroughly reviewed the document, helped us correct errors, and suggested clarifications to the text.
在阿尔弗雷德·霍恩斯（Alfred Hoenes）的特别帮助下，本文件在URN-NID清单上进行了讨论。霍恩斯彻底审查了本文件，帮助我们纠正错误，并建议对文本进行澄清。
Peter Saint-Andre has also provided comments that have improved the overall document quality, for which we herein thank him. We'd also like to thank Chris Lonvick for helping us express our security concerns in a better way. Finally, we thank other reviewers that have helped us to give the final touches to the text.
彼得·圣安德烈（Peter Saint Andre）也提出了一些意见，这些意见提高了文件的整体质量，对此我们在此表示感谢。我们还要感谢Chris Lonvick帮助我们以更好的方式表达我们的安全顾虑。最后，我们感谢帮助我们对文本进行最后润色的其他评论员。
Special thanks should go to Dyonisius Visser from the TERENA technical team for taking the time and effort required to set up the root instance of the namespace registry.
应该特别感谢TERENA技术团队的Dyonisius Visser花费时间和精力来设置名称空间注册表的根实例。
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[1] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
[2] Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，STD 68，RFC 5234，2008年1月。
[3] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[3] Rescorla，E.，“TLS上的HTTP”，RFC 2818，2000年5月。
[4] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[4] Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，2008年8月。
[5] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[5] Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[6] TERENA, "Trans-European Research and Education Networking Association", <http://www.terena.org/>.
[6] TERENA，“跨欧洲研究和教育网络协会”<http://www.terena.org/>.
[7] TERENA TF-EMC2, "SCHAC activity web site", <http://www.terena.org/activities/tf-emc2/schac.html>.
[7] TERENA TF-EMC2，“SCHC活动网站”<http://www.terena.org/activities/tf-emc2/schac.html>.
[8] Sciberras, A., Ed., "Lightweight Directory Access Protocol (LDAP): Schema for User Applications", RFC 4519, June 2006.
[8] Sciberas，A.，编辑，“轻量级目录访问协议（LDAP）：用户应用程序模式”，RFC45192006年6月。
[9] Smith, M., "Definition of the inetOrgPerson LDAP Object Class", RFC 2798, April 2000.
[9] Smith，M.，“inetOrgPerson LDAP对象类的定义”，RFC 2798，2000年4月。
[10] MACE-Dir, "eduPerson Object Class Specification", December 2007, <http://middleware.internet2.edu/eduperson/docs/ internet2-mace-dir-eduperson-200712.html>.
[10] MACE Dir，“eduPerson对象类规范”，2007年12月<http://middleware.internet2.edu/eduperson/docs/ internet2-mace-dir-eduperson-200712.html>。
[11] Moats, R., "URN Syntax", RFC 2141, May 1997.
[11] 护城河，R.，“瓮语法”，RFC 21411997年5月。
[12] IANA, "Country TLDs", <http://www.iana.org/domains/root/db/>.
[12] IANA，“国家TLD”<http://www.iana.org/domains/root/db/>.
[13] Best, K. and N. Walsh, "A URN Namespace for XML.org", RFC 3120, June 2001.
[13] Best，K.和N.Walsh，“XML.org的URN名称空间”，RFC31202001年6月。
[14] OASIS, "Organization for the Advancement of Structured Information Standards: OASIS", <http://www.oasis-open.org/>.
[14] OASIS，“结构化信息标准促进组织：OASIS”<http://www.oasis-open.org/>.
[15] Best, K. and N. Walsh, "A URN Namespace for OASIS", RFC 3121, June 2001.
[15] 贝斯特，K.和N.沃尔什，“绿洲的瓮名称空间”，RFC31212001年6月。
[16] Morgan, R. and K. Hazelton, "Definition of a Uniform Resource Name (URN) Namespace for the Middleware Architecture Committee for Education (MACE)", RFC 3613, October 2003.
[16] Morgan，R.和K.Hazelton，“教育中间件体系结构委员会（MACE）统一资源名（URN）命名空间的定义”，RFC 3613，2003年10月。
Authors' Addresses
作者地址
Victoriano Giralt, M.D. University of Malaga Avd. Cervantes, 2 Malaga, Malaga E-29071 Spain
Victoriano Giralt，马拉加大学医学院医学博士。塞万提斯，马拉加2号，马拉加E-29071西班牙
Phone: +34-95-213-1415
EMail: victoriano@uma.es
URI: http://www.uma.es/
Phone: +34-95-213-1415
EMail: victoriano@uma.es
URI: http://www.uma.es/
Dr. Rodney McDuff The University of Queensland
Rodney McDuff博士昆士兰大学
EMail: r.mcduff@uq.edu.au
URI: http://www.uq.edu.au/
EMail: r.mcduff@uq.edu.au
URI: http://www.uq.edu.au/