Browse Prior Art Database

URN Namespace Definition Mechanisms (RFC2611)

IP.com Disclosure Number: IPCOM000003198D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 17 page(s) / 25K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Daigle: AUTHOR [+4]

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".

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group L. Daigle

Request for Comments: 2611 Thinking Cat Enterprises

BCP: 33 D. van Gulik

Category: Best Current Practice ISIS/CEO, JRC Ispra

R. Iannella

DSTC Pty Ltd

P. Faltstrom

Tele2/Swipnet

June 1999

URN Namespace Definition Mechanisms

Status of this Memo

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".

1.0 Introduction

Uniform Resource Names (URNs) are resource identifiers with the

specific requirements for enabling location independent

identification of a resource, as well as longevity of reference.

There are 2 assumptions that are key to this document:

Assumption #1:

Assignment of a URN is a managed process.

I.e., not all strings that conform to URN syntax are necessarily

valid URNs. A URN is assigned according to the rules of a

particular namespace (in terms of syntax, semantics, and process).

Assumption #2:

The space of URN namespaces is managed.

I.e., not all syntactically correct URN namespaces (per the URN

syntax definition) are valid URN namespaces. A URN namespace

must have a recognized definition in order to be valid.

The purpose of this document is to outline a mechanism and provide a

template for explicit namespace definition, along with the mechanism

for associating an identifier (called a "Namespace ID", or NID) which

is registered with the Internet Assigned Numbers Authority, IANA.

Note that this document restricts itself to the description of

processes for the creation of URN namespaces. If "resolution" of any

so-created URN identifiers is desired, a separate process of

registration in a global NID directory, such as that provided by the

NAPTR system [RFC2168], is necessary. See [NAPTR-REG] for

information on obtaining registration in the NAPTR global NID

directory.

2.0 What ...