INTERNET-DRAFT                                Jurijs
Network Working Group                                      J. Kornijenko
Expires in six months
Request for Comments: 4617                                  ABC Software
Obsoletes: RFC 3383                           02 February software
Category: Informational                                      August 2006

          A URN Uniform Resource Name (URN) Formal Namespace for
          the Latvian National Government Integration Project
            Suggested filename: <draft-kornijenko-ivis-urn-00.txt>

Status of this This Memo

Internet-Drafts are working documents of

   This memo provides information for the Internet Engineering Task
Force (IETF), its areas, and its working groups.  Note that other groups may
also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. community.  It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress".

The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/1id-abstracts.html

The list does
   not specify an Internet standard of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims kind.  Distribution of which he or she this
   memo is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2006).All Rights Reserved.
   Please see the Full Copyright section near the end of this document
   for more information. (2006).

Abstract

   This document describes a Uniform Resource Name (URN) namespace that
   is engineered by a consortium (general contractor - contractor, Olimps Ltd LTD, and
subcontractors -
   subcontractors, ABC software LTD, Microsoft Latvia LTD,
RIX Riga Internet
   eXchange (RIX) Technologies LTD LTD, and Microlink LTD) for naming
   information resources published and produced by the Latvian National
   Government Integration Project (latvian (Latvian abbreviation - 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

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

2.  Specification Template

2.1

   Namespace ID:

      "IVIS" requested.

2.2 requested according to [RFC3406].

   Registration information:

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

2.3

   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
Affiliation: Mag.sc.ing. Software Architect
   Address: Tallinas - 51, Riga, LV-1012
   Phone: +371 7082635
   Email: j.kornienko@abcsoftware.lv

2.4

   Declaration of structure:

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

<NID> ::= "IVIS"

<NSS>            ::= <IVIS Org ID>:<ResID - suffix>

<IVIS Org ID>    ::= <number> 1*<number>    { subsystem ID from IVIS database}

<ResID - suffix> ::= <upper> 1*(<upper> | <lower> | <number> | <other> <other>)
{an ID generated by IVIS subsystem and that is unique within
this subsystem}

<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"

<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"

2.5

   Relevant ancillary documentation:

      IVIS ancillary documentation is under development.

2.6

   Identifier uniqueness considerations:

      Uniqueness is guaranteed by the IVIS that issues the numbers.  The
      numbers are not re-assigned.

2.7 reassigned.

   Identifier persistence considerations:

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

2.8

   Process of identifier assignment:

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

   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.

2.10

   Rules for Lexical Equivalence:

      The entire URN is case-insensitive.

2.11 Conformance case insensitive.

   Conformity with URN syntax:

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

2.12

   Validation mechanism:

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

2.13

   Scope:

      Global.

3.  Example

   The following examples are not guaranteed to be real.  They are provided for
   pedagogical reasons only:

    URN:IVIS:100001:DOC-METADATA
    URN:IVIS:100002:NDR1021365 purposes only.

      URN:IVIS:000000:DOC-METADATA
      URN:IVIS:000000:NDR1021365

4.  Community Considerations

   Every Latvian ministry, ministry's local authority produces many kinds of
   different documents, offers public services.  Each of the information
   resources is
unique already uniquely identified within authority-producer already. an authority-
   producer.  The IVIS URN namespace helps to 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 registration,
   and resolution services.  The primary IVIS namespace usage is to
   identify information resources, such as XML messages, their schemas schemas,
   and other recourses, resources, which can be public or have a special
   destination, when a few different parties are involved in the
   interchange.

5.  IANA Considerations

   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).

6.  Namespace Considerations

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

1.Information

   - Information resource uniqueness

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

2.Namespace

   - Namespace understandability

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

3.Information

   - Information resource resolution

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

So,

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

6.

7.  Security Considerations

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

Acknowledgments

The authors acknowledge

8.  Acknowledgements

      Since the thoughtful contributions of Jurijs
Kornijenko to specification described in this document.

7.  References:

7.1. 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.

9.  References

9.1.  Normative References

[1]

   [RFC3406]   Daigle, L., van Gulik, D., Iannella, R. R., and Falstrom P,. P.
               Faltstrom, "Uniform Resource Names (URN) Namespace
               Definition Mechanisms, Mechanisms", BCP 66, RFC 3406, October 2002.

[2]

   [RFC3986]   Berners-Lee, T., Fielding, R. R., and L. Masinter, L,. "Uniform
               Resource
Identifiers Identifier (URI): Generic Syntax", STD 66, RFC 2396, August 1998.

7.2.
               3986, January 2005.

9.2.  Informative References

[3]  Berners-Lee, T., Fielding, R and Masinter L,. "Uniform Resource
Identifiers (URI): Generic Syntax draft-fielding-uri-rfc2396bis-07",
September 2004.

[4]

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

[5]

   [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.

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

[6]

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

[7]

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

8.
               <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.

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

Author's Addresses

      Name: Address

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

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

Full Copyright Statement

   Copyright (C) The Internet Society (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.

   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 Rights

   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.

   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.

   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.

Disclaimer of Validity

This document and

Acknowledgement

   Funding for the information contained herein are RFC Editor function is 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. by the IETF
   Administrative Support Activity (IASA).