RFC 3120 on A URN Namespace for XML.org

RFC Editor <rfc-ed@ISI.EDU> Mon, 18 June 2001 19:01 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16895; Mon, 18 Jun 2001 15:01:36 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA24867 for ietf-123-outbound.10@ietf.org; Mon, 18 Jun 2001 14:55:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA24824 for <all-ietf@loki.ietf.org>; Mon, 18 Jun 2001 14:50:26 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16567 for <all-ietf@ietf.org>; Mon, 18 Jun 2001 14:50:18 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f5IIoaG07188; Mon, 18 Jun 2001 11:50:36 -0700 (PDT)
Message-Id: <200106181850.f5IIoaG07188@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3120 on A URN Namespace for XML.org
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 18 Jun 2001 11:50:36 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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:    karl.best@oasis-open.org,
                    Norman.Walsh@East.Sun.COM 
        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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc3120.txt"><ftp://ftp.isi.edu/in-notes/rfc3120.txt>