RFC - 2611
URN Namespace Definition Mechanisms
| Original: | ftp://ftp.isi.edu/in-notes/rfc2611.txt |
|---|---|
| Authors: | L. Daigle [Thinking Cat Enterprises], D. van Gulik [ISIS/CEO, JRC Ispra], R. Iannella [DSTC Pty Ltd], P. Faltstrom [Tele2/Swipnet] |
| Date: | June 1999 |
| Category: | Best Current Practice [ BCP-33 ] |
| This specification has been !!! obsoleted !!! | |
| Obsoleted by: | |
|---|---|
| RFC-3406 [BCP 66] |
Uniform Resource Names (URN) Namespace Definition Mechanisms |
| Referred by: | 15 RFC |
| Refers to: | 8 RFC |
Status
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract
The URN WG has defined a syntax for Uniform Resource Names (URNs) [RFC2141], as well as some proposed mechanisms for their resolution and use in Internet applications ([RFC2168, RFC2169]). The whole rests on the concept of individual "namespaces" within the URN structure. Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed ([RFC2288]), and this document lays out general definitions of and mechanisms for establishing URN "namespaces".
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry