W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 1997

RFC 2141 on URN Syntax

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Tue, 6 May 1997 10:41:24 -0700
Message-Id: <af951cc00e02100412f5@[]>
To: w3c-dist-auth@w3.org

Of potential interest to participants of this WG.

- Jim

>To: IETF-Announce: ;
>Subject: RFC 2141 on URN Syntax
>Cc: rfc-ed@isi.edu
>Mime-Version: 1.0
>Date: Mon, 05 May 97 13:53:28 PDT
>From: RFC Editor <rfc-ed@isi.edu>
>A new Request for Comments is now available in online RFC libraries.
>        RFC 2141:
>        Title:      URN Syntax
>        Author:     R. Moats
>        Date:       May 1997
>        Mailbox:    jayhawk@ds.internic.net
>        Pages:      8
>        Characters: 14077
>        Updates/Obsoletes: None
>        URL:        ftp://ds.internic.net/rfc/rfc2141.txt
>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 document is the product of
>the Uniform Resource Names Working Group of the IETF.
>This is now a Proposed Standard Protocol.
>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.
>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@CNRI.RESTON.VA.US.  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@ISI.EDU with the message body
>help: ways_to_get_rfcs.  For example:
>        To: rfc-info@ISI.EDU
>        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 admin@DS.INTERNIC.NET.  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
>Authors, for further information.
>Joyce K. Reynolds and Mary Kennedy
>USC/Information Sciences Institute
Received on Tuesday, 6 May 1997 14:07:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:15 UTC