Network Working Group D. Smith
Request for Comments: 4358 Open Mobile Alliance
Category: Informational January 2006
Network Working Group D. Smith
Request for Comments: 4358 Open Mobile Alliance
Category: Informational January 2006
A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA)
开放移动联盟（OMA）的统一资源名称（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 (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the Open Mobile Alliance (OMA). OMA defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided by the Open Mobile Naming Authority (OMNA).
本文档描述了开放移动联盟（OMA）发布的统一资源名称空间（URN）资源的名称空间标识符（NID）。OMA定义并管理使用此URN名称模型的资源。这些和其他资源类型的管理活动由开放移动命名机构（OMNA）提供。
Table of Contents
目录
1. Introduction ....................................................2
2. URN Specification for "oma" NID .................................2
3. Examples ........................................................4
4. Namespace Considerations ........................................4
5. Community Considerations ........................................5
6. Security Considerations .........................................5
7. IANA Considerations .............................................5
8. Informative References ..........................................5
1. Introduction ....................................................2
2. URN Specification for "oma" NID .................................2
3. Examples ........................................................4
4. Namespace Considerations ........................................4
5. Community Considerations ........................................5
6. Security Considerations .........................................5
7. IANA Considerations .............................................5
8. Informative References ..........................................5
OMA is a specification development body developing technologies for mobile devices. This activity is supported by a membership composed of network operators, equipment vendors, content providers, and other suppliers to the mobile market.
OMA是一个为移动设备开发技术的规范开发机构。该活动由网络运营商、设备供应商、内容提供商和移动市场的其他供应商组成的成员支持。
Some of the technologies being developed by OMA need XML namespaces that are managed so that they are unique and persistent. To assure that the uniqueness is absolute, the registration of a specific NID for use by OMA was deemed appropriate. Therefore, a full and complete registration will follow the namespace specification process as defined in [RFC3406].
OMA开发的一些技术需要管理XML名称空间，以便它们是唯一和持久的。为了确保唯一性是绝对的，OMA使用特定NID的注册被认为是合适的。因此，完全注册将遵循[RFC3406]中定义的命名空间规范过程。
Namespace ID:
命名空间ID:
The NID "oma" is requested.
请求NID“oma”。
Registration Information:
注册资料：
registration version number: 1 registration date: 2005-07-18
注册版本号：1注册日期：2005-07-18
Declared registrant of the namespace:
已声明命名空间的注册人：
Registering organization Name: Open Mobile Alliance Address: 4275 Executive Square Suite 240s La Jolla, CA 92037
注册机构名称：开放移动联盟地址：4275行政广场套房240s La Jolla，CA 92037
Designated contact Role: Technical Program Manager Email: TPM@omaorg.org
指定联系人角色：技术项目经理电子邮件：TPM@omaorg.org
Declaration of syntactic structure:
句法结构声明：
The Namespace Specific String (NSS) of all URNs that use the "oma" NID will have the following structure:
使用“oma”NID的所有URN的命名空间特定字符串（NSS）将具有以下结构：
urn:oma:{OMAresource}:{ResourceSpecificString}
urn:oma:{OMAresource}:{ResourceSpecificString}
where the "OMAresource" is a US-ASCII string that conforms to the URN syntax requirements [RFC2141] and defines a specific class of resource type. Each resource type has a specific labeling scheme
其中，“OMAROURCE”是符合URN语法要求[RFC2141]的US-ASCII字符串，并定义资源类型的特定类别。每种资源类型都有一个特定的标签方案
that is covered by "ResourceSpecificString", which also conforms to the naming requirements of [RFC2141].
“ResourceSpecificString”涵盖了这一点，它也符合[RFC2141]的命名要求。
OMA maintains a naming authority, the Open Mobile Naming Authority (OMNA), that will manage the assignment of "OMAresources" and the specific registration values assigned for each resource class.
OMA维护一个命名机构，即开放式移动命名机构（OMNA），该机构将管理“OMA资源”的分配以及为每个资源类别分配的特定注册值。
Relevant ancillary documentation:
相关辅助文件：
The Open Mobile Naming Authority (OMNA) provides information on the registered resources and the registrations for each. More information about OMNA and the registration activities and procedures to be followed are available at:
开放式移动命名机构（OMNA）提供有关已注册资源和每个资源的注册的信息。有关OMNA以及注册活动和程序的更多信息，请访问：
http://www.openmobilealliance.org/tech/omna
http://www.openmobilealliance.org/tech/omna
Identifier uniqueness considerations:
标识符唯一性注意事项：
The OMNA will manage resources using the "oma" NID and will be the authority for managing the resources and subsequent strings associated. In the associated procedures, OMNA will ensure the uniqueness of the strings themselves or shall permit secondary responsibility for management of well-defined sub-trees.
OMNA将使用“oma”NID管理资源，并将成为管理资源和后续相关字符串的机构。在相关程序中，OMNA将确保管柱本身的唯一性，或允许对定义明确的子树进行二级管理。
OMA may permit use of experimental type values that will not be registered. As a consequence, multiple users may end up using the same value for separate uses. As experimental usage is only intended for testing purposes, this should not be a real issue.
OMA可能允许使用未注册的实验类型值。因此，多个用户可能最终使用相同的值进行单独使用。由于实验用途仅用于测试目的，因此这不应该是一个真正的问题。
Identifier persistence considerations:
标识符持久性注意事项：
OMNA will provide clear documentation of the registered uses of the "oma" NID. This will be structured such that each OMAresource will have a separate description and registration table.
“OMNA”将提供关于“oma注册使用”的清晰文件。其结构将确保每个OMA资源都有一个单独的描述和注册表。
The registration tables and information will be published and maintained by OMNA on its web site.
OMNA将在其网站上公布和维护登记表和信息。
Process of identifier assignment:
标识符分配过程：
OMNA will provide procedures for registration of each type of resource that it maintains. Each such resource may have three types of registration activities:
OMNA将为其维护的每种类型的资源提供注册程序。每个此类资源可能有三种类型的注册活动：
1) Registered values associated with OMA specs or services 2) Registration of values or sub-trees to other entities 3) Name models for use in experimental purposes
1) 与OMA规范或服务相关的注册值2）将值或子树注册到其他实体3）命名用于实验目的的模型
Process for identifier resolution:
标识符解析过程：
The namespace is not listed with an RDS; this is not relevant.
名称空间未与RDS一起列出；这是不相关的。
Rules for Lexical Equivalence:
词汇对等规则：
No special considerations; the rules for lexical equivalence of [RFC2141] apply.
没有特别考虑；[RFC2141]的词汇对等规则适用。
Conformance with URN Syntax:
符合URN语法：
No special considerations.
没有特别考虑。
Validation mechanism:
验证机制：
None specified. URN assignment will be handled by procedures implemented in support of OMNA activities.
没有具体说明。URN分配将由支持OMNA活动的程序执行。
Scope:
范围：
Global
全球的
The following examples are representative urns that could be assigned by OMNA. They may not be the actual strings that would be assigned.
以下示例是OMNA可以分配的代表性URN。它们可能不是要分配的实际字符串。
urn:oma:ac:oma-presence Defines the urn to be used for the Application Characteristic object definition for providing attributes to the Presence enabler defined in OMA.
urn:oma:ac:oma presence定义用于应用程序特征对象定义的urn，用于向oma中定义的状态启用码提供属性。
urn:oma:drms:org-foobar Defines the urn associated with the Digital Rights Management System object definition allocated to foobar, which is an external organization that made request via OMNA for a drms urn.
urn:oma:drms:org foobar定义与分配给foobar的数字版权管理系统对象定义关联的urn，foobar是通过OMNA请求drms urn的外部组织。
The Open Mobile Alliance is developing a variety of application and service enablers. Some of these enablers require that supporting information (e.g., data descriptions, attributes, etc.) be fully specified. For proper operation, descriptions of the needed supporting information must exist and be available in a unique, reliable, and persistent manner. These dependencies provide the basis of need for namespaces, in one form or another.
开放移动联盟正在开发各种应用和服务使能技术。其中一些使能技术要求完全指定支持信息（例如，数据描述、属性等）。对于正确的操作，必须存在所需支持信息的描述，并以独特、可靠和持久的方式提供。这些依赖关系以某种形式提供了名称空间需求的基础。
As the Open Mobile Alliance work is ongoing and covers many technical areas, the possibility of binding to various other namespace repositories has been deemed impractical. Each object or description, as defined in OMA, could possibly be related to multiple different other namespaces, so further conflicts of association could occur. Thus the intent is to utilize the Open Mobile Naming Authority, operated by OMA, as the naming authority for OMA-defined objects and descriptions.
由于开放移动联盟的工作正在进行中，并且涵盖了许多技术领域，因此绑定到各种其他名称空间存储库的可能性被认为是不切实际的。OMA中定义的每个对象或描述可能与多个不同的其他名称空间相关，因此可能会发生进一步的关联冲突。因此，目的是利用OMA运营的开放式移动命名机构作为OMA定义的对象和描述的命名机构。
The objects and descriptions required for enablers produced by OMA are generally available for use by other organizations. The Open Mobile Naming Authority will provide access and support for name requests by these organizations. This support can be enabled in a timely and responsive fashion as new objects and descriptions are produced. These will be enabled in a fashion similar to current OMNA support.
OMA生成的使能器所需的对象和描述通常可供其他组织使用。开放式移动命名机构将为这些组织的命名请求提供访问和支持。随着新对象和描述的产生，这种支持可以以及时和响应的方式启用。这些将以类似于当前OMNA支持的方式启用。
There are no additional security considerations other than those normally associated with the use and resolution of URNs in general.
除了通常与使用和解决骨灰盒相关的安全注意事项外，没有其他安全注意事项。
The requested NID has been entered into the IANA registry for URN NIDs. The update can be found at: http://www.iana.org/assignments/urn-namespaces and any associated mirrors.
请求的NID已输入到URN NID的IANA注册表中。更新可在以下位置找到：http://www.iana.org/assignments/urn-namespaces 以及任何相关的镜子。
[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月。
Author's Address
作者地址
Dwight Smith (Chair, Operations and Process Committee, OMA) Motorola 5555 N Beach Street Ft. Worth, TX 76137
德怀特·史密斯（OMA运营和流程委员会主席）德克萨斯州沃思堡海滩街北5555号，邮编76137
EMail: dwight.smith@motorola.com
EMail: dwight.smith@motorola.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
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 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
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.
Acknowledgement
确认
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。