RFC - 3406
Uniform Resource Names (URN) Namespace Definition Mechanisms
| Original: | ftp://ftp.isi.edu/in-notes/rfc3406.txt |
|---|---|
| Authors: | L. Daigle [Thinking Cat Enterprises], D.W. van Gulik [WebWeaving], R. Iannella [IPR Systems], P. Faltstrom [Cisco] |
| Date: | October 2002 |
| Category: | Best Current Practice [ BCP-66 ] |
| Obsoletes: | |
|---|---|
| RFC-2611 [BCP 33] |
URN Namespace Definition Mechanisms (Obsoleted by RFC-3406) |
| Referred by: | 20 RFC |
| Refers to: | 15 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 (2002). All Rights Reserved.
Abstract
This document lays out general definitions of and mechanisms for establishing Uniform Resource Names (URN) "namespaces". The URN WG has defined a syntax for URNs in RFC 2141prop, as well as some proposed mechanisms for their resolution and use in Internet applications in RFC 3401 and RFC 3405. 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 in RFC 2288.
-
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