A URN Namespace for XML.org
draft-best-xmlorg-01
This document is an Internet-Draft (I-D) that has been submitted to the Legacy stream.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
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 3120.
|
|
|---|---|---|---|
| Authors | Karl Best , Norman Walsh | ||
| Last updated | 2013-03-02 (Latest revision 2001-02-08) | ||
| RFC stream | Legacy | ||
| Intended RFC status | Informational | ||
| Formats | |||
| Stream | Legacy state | (None) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Became RFC 3120 (Informational) | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-best-xmlorg-01
A new Request for Comments is now available in online RFC libraries.
RFC 3120
Title: A URN Namespace for XML.org
Author(s): K. Best, N. Walsh
Status: Informational
Date: June 2001
Mailbox: [email protected],
[email protected]
Pages: 5
Characters: 8068
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-best-xmlorg-01.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3120.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 stored
in the XML.org repository (such as 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 [email protected]. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body
help: ways_to_get_rfcs. For example:
To: [email protected]
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 [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
[email protected]. Please consult RFC 2223, Instructions to RFC
Authors, for further information.