[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 RFC 4617

INTERNET-DRAFT                                Jurijs Kornijenko
Expires in six months                         ABC Software
Obsoletes: RFC 3383                           02 February 2006

A URN Namespace for the Latvian National Government Integration Project
            Suggested filename: <draft-kornijenko-ivis-urn-00.txt>

Status of this Memo

Internet-Drafts are working documents of 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.  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 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 of which he or she 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.



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.


Kornijenko              IVIS URN Definition                    [Page 1]

INTERNET-DRAFT    draft-kornijenko-ivis-urn-00.txt     February 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,
RIX Technologies LTD and Microlink LTD) for naming information resources
published and produced by the Latvian National Government Integration
Project (latvian abbreviation - IVIS).






1. Introduction

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

2. Specification Template

2.1 Namespace ID:

      "IVIS" requested.

2.2 Registration information:

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

2.3 Declared registrant of the namespace:

Name: Jurijs Kornijenko
Title: software architect
Affiliation: Mag.sc.ing.
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:

<NID> ::= "IVIS"


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

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

<ResID - suffix> ::= <upper> | <lower> | <number> | <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"


Kornijenko              IVIS URN Definition                    [Page 2]

INTERNET-DRAFT    draft-kornijenko-ivis-urn-00.txt     February 2006


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 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 with URN syntax:

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

2.12 Validation mechanism:

<IVIS Org ID> could be validated by using special IVIS database service.
<ResID - suffix> could be validated by 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

Kornijenko              IVIS URN Definition                    [Page 3]

INTERNET-DRAFT    draft-kornijenko-ivis-urn-00.txt     February 2006

4. Community Considerations

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


5. Namespace Considerations

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

1.Information resource uniqueness

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

2.Namespace understandability

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

3.Information resource resolution

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

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


6. Security Considerations

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


Kornijenko              IVIS URN Definition                    [Page 4]

INTERNET-DRAFT    draft-kornijenko-ivis-urn-00.txt     February 2006



Acknowledgments

The authors acknowledge the thoughtful contributions of Jurijs
Kornijenko to this document.

7.  References:

7.1.  Normative References

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

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

7.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]  Narten, T,. Alvestrand, H,. "Guidelines for Writing an IANA
considerations Section in RFC's", RFC 2434, October 1998.

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

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

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



8. Author's Addresses

      Name:        Jurijs Kornijenko
      Address:     Tallinas - 51, Riga, LV-1012
      Phone:       +371 7082635
      Email:        j.kornienko@abcsoftware.lv



Kornijenko              IVIS URN Definition                    [Page 5]

INTERNET-DRAFT    draft-kornijenko-ivis-urn-00.txt     February 2006


Full Copyright

  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.

Kornijenko              IVIS URN Definition                    [Page 6]
INTERNET-DRAFT    draft-kornijenko-ivis-urn-00.txt     February 2006

Disclaimer of Validity

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.


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/