RFC 4617

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

📅 published August 2006, from ietf

RFC 4617 bestie edition 💖

Network Working Group · Request for Comments: 4617 · Category: Informational · August 2006 🎀

Okay so this one's by Jurijs Kornijenko from ABC software, and it's a formal namespace for the Latvian National Government Integration Project 🇱🇻✨. It's an Informational doc, so it's sharing info, not setting an Internet standard. The title block doesn't list anything it obsoletes or updates, so there's no drama there 💅.

Title ✨

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

Status of This Memo 🧚

This memo gives info to the Internet community. It does not specify an Internet standard of any kind. Distribution is unlimited, so share away 🫶.

Copyright Notice 💜

Abstract 🦋

Okay, so this doc describes a URN namespace that a consortium engineered 🛠️. The consortium is the general contractor Olimps LTD plus subcontractors ABC software LTD, Microsoft Latvia LTD, Riga Internet eXchange (RIX) Technologies LTD, and Microlink LTD. The namespace names information resources published and produced by the Latvian National Government Integration Project, which goes by the 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 💅

IVIS makes and uses so many kinds of information resources, like E-services, E-service instances, specifications, standards, working documents, and XML schemas 📚. An ID in IVIS has to be unique for global use every single time. Main character energy for uniqueness 👑.

2. Specification Template 🎀

Here's the whole template, bestie, so let's go step by step ✨.

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 every URN IVIS assigns has this hierarchical structure. The grammar is written in ABNF, following [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}
<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 still under development 🚧.

Identifier uniqueness considerations: the IVIS that issues the numbers guarantees uniqueness, and the numbers are not reassigned 🔒.

Identifier persistence considerations: persistence depends on the system name assignment staying persistent, as kept up by the system name holders 🕰️.

Process of identifier assignment: IVIS and its subsystems fully control and manage every assignment 🗂️.

Process of identifier resolution: the system name holders are responsible for running resolution servers for their system, or delegating that job, wherever they've assigned URNs 🛰️.

Rules for Lexical Equivalence: the entire URN is case insensitive 🔤.

Conformity with URN syntax: the IVIS schema URN fully conforms to [RFC2141] syntax, with one exception: the symbols ' and : were excluded from <other> 🙈.

Validation mechanism: <IVIS Org ID> could be validated through a special IVIS database service. <ResID - suffix> could be validated by an appropriate subsystem ✅.

Scope: Global 🌍.

3. Example 🧚

These examples are not real, bestie. They're just for teaching purposes 🍓.

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

4. Community Considerations 🫶

Every Latvian ministry's local authority makes loads of different documents and offers public services 🏛️. Each information resource is already uniquely identified inside its authority-producer. The IVIS URN namespace helps unify those identifiers by reusing the existing Latvian government authority identification procedures, so E-services and documents with lots of parties involved stay organised 🗂️✨. Any citizen or organisation with a web browser is entitled to access the namespace and its associated application, registration, and resolution services 🌐. The main use of the IVIS namespace is identifying information resources, like XML messages, their schemas, and other resources. Those can be public or have a special destination, especially when a few different parties are interchanging things 💌.

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 💭

The team spent a lot of time picking the identifier schema, and they landed on URN, because the IVIS URN namespace has to solve three problems 🧠:

Information resource uniqueness: uniqueness makes it possible to find the resource you need and call it anytime. It also gives stability to message sending and storing operations 📮.
Namespace understandability: an IVIS URN is made of parts, and those parts keep the namespace legible 👀.
Information resource resolution: one part of the IVIS namespace identifies where the resource can be found (resolved) 📍.

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

7. Security Considerations 🔐

There are no additional security considerations beyond the ones normally tied to using and resolving URNs in general 🛡️.

8. Acknowledgements 💖

This spec is derived from [RFC3305], [RFC3616], [RFC3986], [RFC3622], and [RFC3406], so the acknowledgements in those documents still apply 🙌. The author also wants to thank Leslie Daigle, Ted Hardie, and Dinara Suleymanova for their suggestions and review 🥰.

9. References 📚

9.1. Normative References

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

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

9.2. Informative References

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

[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, "A
            Uniform Resource Name (URN) Namespace for Foundation for
            Intelligent Physical Agents (FIPA)", RFC 3616, September
            2003.

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

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

[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 Address 🎀

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

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

Full Copyright Statement ⚖️

This document is subject to the rights, licenses and restrictions contained in BCP 78. Except as set forth there, the authors keep all their rights 💜.

This document and the info in it are provided on an "AS IS" basis. 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 USING 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 on the validity or scope of any Intellectual Property Rights or other rights that might be claimed to apply to implementing or using the technology described here. It also doesn't say whether any license under those rights might or might not be available, and it hasn't made any independent effort to find such rights 🔍. Info on the procedures for rights in RFC documents is in BCP 78 and BCP 79 📖.

Copies of IPR disclosures made to the IETF Secretariat, any assurances of licenses to be made available, or the result of an attempt to get a general license or permission for implementers or users to use these proprietary rights, can be found in the IETF online IPR repository at http://www.ietf.org/ipr 🗃️.

The IETF invites any interested party to bring to its attention any copyrights, patents, patent applications, or other proprietary rights that may cover technology needed to implement this standard. Send that info to the IETF at ietf-ipr@ietf.org 📬.

Acknowledgement 🌈

Funding for the RFC Editor function comes from the IETF Administrative Support Activity (IASA) 💸✨.

📦 where this page comes from

ietf: rfc4617 2006-08
💖 girlified by claude-haiku-5-5 on 2026-10-16: a language model's rewrite of the original, under its terms