A URN Namespace for OASIS
RFC 3121

Document Type RFC - Informational (June 2001; No errata)
Was draft-best-urn-oasis (individual)
Last updated 2013-03-02
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3121 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            K. Best
Request for Comments: 3121                                   OASIS, Inc.
Category: Informational                                         N. Walsh
                                                  Sun Microsystems, Inc.
                                                               June 2001

                       A URN Namespace for OASIS

Status of this Memo

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

Copyright Notice

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

Abstract

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

1. Introduction

   The Organization for the Advancement of Structured Information
   Standards (OASIS) produces many kinds of documents: specifications,
   working drafts, technical resolutions, schemas, stylesheets, etc.

   OASIS wishes to provide global, distributed, persistent, location-
   independent names for these resources.

   The Extensible Markup Language (XML) requires that all resources
   provide a system identifier, which must be a URI, in addition to an
   optional public identifier (which provides an alternate mechanism for
   constructing identifiers) and many evolving specifications require
   authors to identify documents by URI alone (XML Namespaces, XML
   Schema, XSLT, etc.).

   Motivated by these observations, OASIS would like to assign URNs to
   some resources in order to retain unique, permanent location-
   independent names for them.

Best & Walsh                 Informational                      [Page 1]
RFC 3121               A URN Namespace for OASIS               June 2001

   This namespace specification is for a formal namespace.

2. Specification Template

   Namespace ID:

      "oasis" requested.

   Registration Information:

      Registration Version Number: 3
      Registration Date: 2001-02-05

   Declared registrant of the namespace:

      Karl Best
      OASIS - Organization for the Advancement of Structured
      Information Standards
      Post Office Box 455
      Billerica, MA USA 01821

      Phone: +1 (978) 667 5115

   Declaration of structure:

      The Namespace Specific String (NSS) of all URNs assigned by OASIS
      will have the following hierarchical structure:

      There are two branches at the top of the hierarchy: "names" and
      "member".

   The Names Hierarchy

      The NSS in the names hierarchy begins with a document class
      identifier.  There are three classes of identifiers:

      "specification", "tc", and "technical".

      Specifications

         The "specification" hierarchy is for OASIS Specifications.  The
         general structure of the NSS in the specification hierarchy has
         the form:

            urn:oasis:names:specification:{specification-id}
                           :{type}{:subtype}?:{document-id}

Best & Walsh                 Informational                      [Page 2]
RFC 3121               A URN Namespace for OASIS               June 2001

         where "specification-id" is a unique identifier for the
         specification, "type" identifies the document type (document,
         schema, stylesheet, entity, xmlns, etc.), the optional
         "subtype" provides additional information about the document
         type (for example, stylesheet or schema language), and
         "document-id" is a unique identifier for the document.

         The Director of Technical Operations at OASIS assigns document
         types, subtypes, and all unique identifiers.

      Technical Committee Work Products

         The "tc" hierarchy is for work products of OASIS Technical
         Committees.  The general structure of the NSS in the tc
         hierarchy has the form:

            urn:oasis:names:tc:{tc-id}:{type}{:subtype}?:{document-id}

         where "tc-id" is a unique identifier for the Technical
         Committee, and the remaining fields are assigned as per the
         specification hierarchy.

      Technical Papers

         The "technical" hierarchy identifies legacy documents
         (Technical Notes, Resolutions, Memoranda, and Research Papers).
         The general structure of the NSS in the "technical" hierarchies
         has the form:

            urn:oasis:names:technical:{document-type}
                           :{document-id}:{amendment-id}

         The document type is one of the following: "note",
         "resolution", "memorandum", or "researchpaper".

         The document and amendment identifiers are derived from the
Show full document text