Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

URN Syntax (RFC2141)

IP.com Disclosure Number: IPCOM000002697D
Original Publication Date: 1997-May-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 6 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Moats: AUTHOR

Abstract

Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers. This document sets forward the canonical syntax for URNs. A discussion of both existing legacy and new namespaces and requirements for URN presentation and transmission are presented. Finally, there is a discussion of URN equivalence and how to determine it.

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

Network Working Group R. Moats

Request for Comments: 2141 AT&T

Category: Standards Track May 1997

URN Syntax

Status of This Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Abstract

Uniform Resource Names (URNs) are intended to serve as persistent,

location-independent, resource identifiers. This document sets

forward the canonical syntax for URNs. A discussion of both existing

legacy and new namespaces and requirements for URN presentation and

transmission are presented. Finally, there is a discussion of URN

equivalence and how to determine it.

1. Introduction

Uniform Resource Names (URNs) are intended to serve as persistent,

location-independent, resource identifiers and are designed to make

it easy to map other namespaces (which share the properties of URNs)

into URN-space. Therefore, the URN syntax provides a means to encode

character data in a form that can be sent in existing protocols,

transcribed on most keyboards, etc.

2. Syntax

All URNs have the following syntax (phrases enclosed in quotes are

REQUIRED):

::= "urn:" ":"

where is the Namespace Identifier, and is the Namespace

Specific String. The leading "urn:" sequence is case-insensitive.

The Namespace ID determines the _syntactic_ interpretation of the

Namespace Specific String (as discussed in [1]).

RFC 1630 [2] and RFC 1737 [3] each presents additional considerations

for URN encoding, which have implications as far as limiting syntax.

On the other hand, the requirement to support existing legacy naming

systems has the effect of broadening syntax. Thus, we discuss the

acceptable syntax for both the Namespace Identifier and the Namespace

Specific String separately.

2.1 Namespace Identifier Syntax

The following is the syntax for the Namespace Identifier. To (a) be

consistent with all potential resolution schemes and (b) not put any

undue constraints on any potential resolution scheme, the syntax for

the Namespace Identifier is:

::= [ 1,31 ]

::= | | | "-"

::= | |

<...