A Uniform Resource Name (URN) Formal Namespace for the Latvian National Government Integration Project
RFC 4617
Document | Type |
RFC - Informational
(August 2006; No errata)
Was draft-kornijenko-ivis-urn (individual in gen area)
|
|
---|---|---|---|
Author | Jurijs Kornijenko | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4617 (Informational) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Ted Hardie | ||
Send notices to | (None) |
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 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). 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). 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 Kornijenko Informational [Page 1] RFC 4617 IVIS URN Definition August 2006 1. Introduction 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. 2. Specification Template Namespace ID: "IVIS" requested according to [RFC3406]. Registration information: Registration Version Number: 1 Registration Date: 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 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]): <NID> ::= "IVIS" <NSS> ::= <IVIS Org ID>:<ResID - suffix> <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} Kornijenko Informational [Page 2] RFC 4617 IVIS URN Definition August 2006 <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" Relevant ancillary documentation: IVIS ancillary documentation is under development. Identifier uniqueness considerations: Uniqueness is guaranteed by the IVIS that issues the numbers. The numbers are not reassigned. 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. 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. Rules for Lexical Equivalence: The entire URN is case insensitive.Show full document text