Skip to main content

A URN Namespace for OASIS

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3121.
Authors Karl Best , Norman Walsh
Last updated 2013-03-02 (Latest revision 2001-02-08)
RFC stream Legacy stream
Intended RFC status Informational
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3121 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3121

        Title:      A URN Namespace for OASIS
        Author(s):  K. Best, N. Walsh
        Status:     Informational
        Date:       June 2001
        Pages:      7
        Characters: 11074
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-best-urn-oasis-02.txt


This document describes a URN (Uniform Resource Name) namespace that
is engineered by the Organization for the Advancement of Structured
Information Standards (OASIS) for naming persistent resources
published by OASIS (such as OASIS Standards, XML (Extensible Markup
Language) Document Type Definitions, XML Schemas, Namespaces,
Stylesheets, and other documents).

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.