Network Working Group                                      J. Kornijenko
Request for Comments: 4617                                  ABC software
Category: Informational                                      August 2006
        
Network Working Group                                      J. Kornijenko
Request for Comments: 4617                                  ABC software
Category: Informational                                      August 2006

A Uniform Resource Name (URN) Formal Namespace for the Latvian National Government Integration Project

拉脱维亚国家政府整合项目的统一资源名称（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 a Uniform Resource Name (URN) namespace that is engineered by a consortium (general contractor, Olimps LTD, and subcontractors, ABC software LTD, Microsoft Latvia LTD, Riga Internet eXchange (RIX) Technologies LTD, and Microlink LTD) for naming information resources published and produced by the Latvian National Government Integration Project (Latvian abbreviation IVIS).

本文档描述了由联合体（总承包商、Olimps有限公司和分包商、ABC软件有限公司、Microsoft拉脱维亚有限公司、里加互联网交换（RIX）技术有限公司和Microlink有限公司）设计的统一资源名（URN）命名空间用于命名拉脱维亚国家政府整合项目（拉脱维亚缩写IVIS）发布和制作的信息资源。

Table of Contents

目录 

   1. Introduction ....................................................2
   2. Specification Template ..........................................2
   3. Example .........................................................4
   4. Community Considerations ........................................4
   5. IANA Considerations .............................................4
   6. Namespace Considerations ........................................5
   7. Security Considerations .........................................5
   8. Acknowledgements ................................................5
   9. References ......................................................6
      9.1. Normative References .......................................6
      9.2. Informative References .....................................6
        
   1. Introduction ....................................................2
   2. Specification Template ..........................................2
   3. Example .........................................................4
   4. Community Considerations ........................................4
   5. IANA Considerations .............................................4
   6. Namespace Considerations ........................................5
   7. Security Considerations .........................................5
   8. Acknowledgements ................................................5
   9. References ......................................................6
      9.1. Normative References .......................................6
      9.2. Informative References .....................................6
1. Introduction
1. 介绍

The IVIS uses and produces many kinds of information resources such as E-services, E-service instances, specifications, standards, working documents, and XML schemas. An ID in IVIS has to be unique for global use every time.

IVIS使用并生成多种信息资源，如电子服务、电子服务实例、规范、标准、工作文档和XML模式。IVIS中的ID必须是唯一的，以便每次全局使用。

2. Specification Template
2. 规范模板

Namespace ID:

命名空间ID:

"IVIS" requested according to [RFC3406].

根据[RFC3406]要求的“IVI”。

Registration information:

注册资料：

Registration Version Number: 1 Registration Date: 2006-MM-DD

注册版本号：1注册日期：2006-MM-DD

Declared registrant of the namespace:

已声明命名空间的注册人： 

   Organization: ABC software LTD on behalf of The Secretariat of the
      Special Assignments Minister for Electronic Government Affairs
   Name: Jurijs Kornijenko
   Title: Software Architect
   Address: Tallinas - 51, Riga, LV-1012
   Phone: +371 7082635
   Email: j.kornienko@abcsoftware.lv
        
   Organization: ABC software LTD on behalf of The Secretariat of the
      Special Assignments Minister for Electronic Government Affairs
   Name: Jurijs Kornijenko
   Title: Software Architect
   Address: Tallinas - 51, Riga, LV-1012
   Phone: +371 7082635
   Email: j.kornienko@abcsoftware.lv

Declaration of structure:

结构声明：

The Namespace Specific String (NSS) of all URNs assigned by the IVIS will have the following hierarchical structure (ABNF, according to [RFC4234]):

IVI分配的所有URN的命名空间特定字符串（NSS）将具有以下层次结构（ABNF，根据[RFC4234]）： 

<NID> ::= "IVIS"
        
<NID> ::= "IVIS"
        
<NSS>            ::= <IVIS Org ID>:<ResID - suffix>
        
<NSS>            ::= <IVIS Org ID>:<ResID - suffix>
        
<IVIS Org ID>    ::= 1*<number>    { subsystem ID from IVIS database}
        
<IVIS Org ID>    ::= 1*<number>    { subsystem ID from IVIS database}
        
<ResID - suffix> ::= 1*(<upper> | <lower> | <number> | <other>)
{an ID generated by IVIS subsystem that is unique within
this subsystem}
        
<ResID - suffix> ::= 1*(<upper> | <lower> | <number> | <other>)
{an ID generated by IVIS subsystem that is unique within
this subsystem}
        
<other>          ::= "(" | ")" | "+" | "," | "-" | "." |
                     "=" | "@" | ";" | "$" |
                     "_" | "!" | "*"
        
<other>          ::= "(" | ")" | "+" | "," | "-" | "." |
                     "=" | "@" | ";" | "$" |
                     "_" | "!" | "*"
        
<upper>          ::= "A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" |
                     "I" | "J" | "K" | "L" | "M" | "N" | "O" | "P" |
                     "Q" | "R" | "S" | "T" | "U" | "V" | "W" | "X" |
                     "Y" | "Z"
        
<upper>          ::= "A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" |
                     "I" | "J" | "K" | "L" | "M" | "N" | "O" | "P" |
                     "Q" | "R" | "S" | "T" | "U" | "V" | "W" | "X" |
                     "Y" | "Z"
        
<lower>          ::= "a" | "b" | "c" | "d" | "e" | "f" | "g" | "h" |
                     "i" | "j" | "k" | "l" | "m" | "n" | "o" | "p" |
                     "q" | "r" | "s" | "t" | "u" | "v" | "w" | "x" |
                     "y" | "z"
        
<lower>          ::= "a" | "b" | "c" | "d" | "e" | "f" | "g" | "h" |
                     "i" | "j" | "k" | "l" | "m" | "n" | "o" | "p" |
                     "q" | "r" | "s" | "t" | "u" | "v" | "w" | "x" |
                     "y" | "z"
        
<number>         ::= "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" |
                     "8" | "9"
        
<number>         ::= "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" |
                     "8" | "9"

Relevant ancillary documentation:

相关辅助文件：

IVIS ancillary documentation is under development.

IVIS辅助文件正在开发中。

Identifier uniqueness considerations:

标识符唯一性注意事项：

Uniqueness is guaranteed by the IVIS that issues the numbers. The numbers are not reassigned.

唯一性由发布数字的IVI保证。这些数字没有重新分配。

Identifier persistence considerations:

标识符持久性注意事项：

Persistence of identifiers is dependent upon the persistence of the system name assignment by system name holders.

标识符的持久性取决于系统名称持有者对系统名称分配的持久性。

Process of identifier assignment:

标识符分配过程：

All the assignments of identifiers are fully controlled and managed by the IVIS and its subsystems.

所有标识符的分配都由IVIS及其子系统完全控制和管理。

Process of identifier resolution:

标识符解析过程：

The holders of system names are responsible for operating or delegating resolution servers for the system in which they have assigned URNs.

系统名称持有者负责为其分配URN的系统操作或委派解析服务器。

Rules for Lexical Equivalence:

词汇对等规则：

The entire URN is case insensitive.

整个URN不区分大小写。

Conformity with URN syntax:

符合URN语法：

IVIS schema URN fully conforms to [RFC2141] syntax, except that symbols "'" and ":" were excluded from <other>.

IVIS架构URN完全符合[RFC2141]语法，除了符号“'”和“：”被排除在<other>之外。

Validation mechanism:

验证机制：

<IVIS Org ID> could be validated by using a special IVIS database service. <ResID - suffix> could be validated by an appropriate subsystem.

<IVIS Org ID>可以通过使用特殊的IVIS数据库服务进行验证<ResID-suffix>可以由适当的子系统进行验证。

Scope:

范围：

Global.

全球的

3. Example
3. 实例

The following examples are not to be real. They are provided for pedagogical purposes only.

下面的例子并不真实。它们仅用于教学目的。 

      URN:IVIS:000000:DOC-METADATA
      URN:IVIS:000000:NDR1021365
        
      URN:IVIS:000000:DOC-METADATA
      URN:IVIS:000000:NDR1021365
4. Community Considerations
4. 社区考虑

Every Latvian ministry's local authority produces many kinds of different documents, offers public services. Each of the information resources is already uniquely identified within an authority-producer. The IVIS URN namespace helps unify information resource identifiers by using existent Latvian government authority identification procedures to produce E-services and different documents where many parties are involved. Any citizen or organization with Internet web browser capability will be entitled to access the namespace and its associated application, registration, and resolution services. The primary IVIS namespace usage is to identify information resources, such as XML messages, their schemas, and other resources, which can be public or have a special destination, when a few different parties are involved in the interchange.

拉脱维亚各部的地方当局都制作各种不同的文件，提供公共服务。每个信息资源都已在授权生产者中唯一标识。IVIS URN名称空间通过使用现有的拉脱维亚政府机构识别程序来生成电子服务和涉及多方的不同文档，帮助统一信息资源标识符。具有Internet web浏览器功能的任何公民或组织都有权访问命名空间及其相关应用程序、注册和解析服务。IVIS名称空间的主要用途是识别信息资源，如XML消息、它们的模式和其他资源，这些资源可以是公共的，也可以有一个特殊的目的地，当交换涉及到几个不同的方时。

5. IANA Considerations
5. IANA考虑

This document includes a RUN Network Identifier (NID) registration for IVIS for entry in the IANA registry of URN NIDs (see [RFC2434] for more information).

本文档包括IVIS的运行网络标识符（NID）注册，用于进入URN NIDs的IANA注册表（有关更多信息，请参阅[RFC2434]）。

6. Namespace Considerations
6. 命名空间注意事项

To select necessary identifier schema, we spend a lot time and decided on URN, because an IVIS URN namespace has to resolve the following problems:

为了选择必要的标识符模式，我们花费了大量时间并决定使用URN，因为IVIS URN命名空间必须解决以下问题：

- Information resource uniqueness

- 信息资源唯一性

Uniqueness makes it possible to find a necessary resource and call it anytime. Uniqueness gives stability in message sending and storing operations.

唯一性使您能够找到必要的资源并随时调用它。唯一性提供了消息发送和存储操作的稳定性。

- Namespace understandability

- 命名空间可理解性

IVIS URN consists of parts, which can guarantee namespace legibility.

IVIS URN由多个部分组成，可以保证名称空间的易读性。

- Information resource resolution

- 信息资源解析

One of the IVIS namespace parts identifies the place where the resource can be found (resolved).

IVIS命名空间的一个部分标识可以找到（解析）资源的位置。

Therefore, a new URN assignment is required, and individual URNs shall be assigned through the process of development of each XML schema.

因此，需要一个新的URN分配，并且应通过每个XML模式的开发过程分配各个URN。

7. Security Considerations
7. 安全考虑

There are no additional security considerations besides those normally associated with the use and resolution of URNs in general.

除了通常与骨灰盒的使用和解决相关的安全注意事项外，没有其他安全注意事项。

8. Acknowledgements
8. 致谢

Since the specification described in this document is derived from [RFC3305], [RFC3616], [RFC3986], [RFC3622], and [RFC3406] the acknowledgements in those documents still apply. In addition, the author wishes to acknowledge Leslie Daigle, Ted Hardie, and Dinara Suleymanova for their suggestions and review.

由于本文件中描述的规范源自[RFC3305]、[RFC3616]、[RFC3986]、[RFC3622]和[RFC3406]，因此这些文件中的确认仍然适用。此外，作者希望感谢Leslie Daigle、Ted Hardie和Dinara Suleymanova的建议和评论。

9. References
9. 工具书类
9.1. Normative References
9.1. 规范性引用文件

[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月。

[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.

[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。

9.2. Informative References
9.2. 资料性引用

[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.

[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。

[RFC3305] Mealling, M. and R. Denenberg, "Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations", RFC 3305, August 2002.

[RFC3305]Mealling，M.和R.Denenberg，“W3C/IETF URI规划联合兴趣小组的报告：统一资源标识符（URI）、URL和统一资源名称（URN）：澄清和建议”，RFC 33052002年8月。

[RFC3616] Bellifemine, F., Constantinescu, I., and S. Willmott, "A Uniform Resource Name (URN) Namespace for Foundation for Intelligent Physical Agents (FIPA)", RFC 3616, September 2003.

[RFC3616] BelLimeMin，F，Constantinescu，I.和S. Willmott，“统一资源名称（URN）命名空间，用于智能物理代理基金会（FIPA）”，RFC 3616，2003年9月。

[RFC3622] Mealling, M., "A Uniform Resource Name (URN) Namespace for the Liberty Alliance Project", RFC 3622, February 2004.

[RFC3622]Mealling，M.“自由联盟项目的统一资源名（URN）命名空间”，RFC36222，2004年2月。

[W3C/IETF] URI Planning Interest Group, W3C/IETF September 2001, <http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/>http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/.

[W3C/IETF]URI规划兴趣小组，W3C/IETF，2001年9月<http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/>http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921/.

[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.

[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。

[RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005.

[RFC4234]Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 4234，2005年10月。

Author's Address

作者地址

Jurijs Kornijenko ABC software LTD Software Architect Tallinas - 51 Riga, LV-1012

Jurijs Kornijenko ABC软件有限公司软件架构师Tallinas-51 Riga，LV-1012 

   Phone: +371 7082635
   EMail: j.kornienko@abcsoftware.lv
        
   Phone: +371 7082635
   EMail: j.kornienko@abcsoftware.lv

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）提供。