draft-ietf-urn-syntax-04.txt   rfc2141.txt 
Internet-Draft Ryan Moats Network Working Group R. Moats
draft-ietf-urn-syntax-04.txt AT&T Request for Comments: 2141 AT&T
Expires in six months March 1997 Category: Standards Track May 1997
URN Syntax URN Syntax
Filename: draft-ietf-urn-syntax-04.txt
Status of This Memo Status of This Memo
This document is an Internet-Draft. Internet-Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its Internet community, and requests discussion and suggestions for
areas, and its working groups. Note that other groups may also improvements. Please refer to the current edition of the "Internet
distribute working documents as Internet-Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as ``work
in progress.''
To learn the current status of any Internet-Draft, please check
the ``1id-abstracts.txt'' listing contained in the Internet-
Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net
(Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East
Coast), or ftp.isi.edu (US West Coast).
Abstract Abstract
Uniform Resource Names (URNs) are intended to serve as persistent, Uniform Resource Names (URNs) are intended to serve as persistent,
location-independent, resource identifiers. This document sets location-independent, resource identifiers. This document sets
forward the canonical syntax for URNs. A discussion of both existing forward the canonical syntax for URNs. A discussion of both existing
legacy and new namespaces and requirements for URN presentation and legacy and new namespaces and requirements for URN presentation and
transmission are presented. Finally, there is a discussion of URN transmission are presented. Finally, there is a discussion of URN
equivalence and how to determine it. equivalence and how to determine it.
skipping to change at page 6, line 40 skipping to change at page 6, line 38
Thanks to various members of the URN working group for comments on Thanks to various members of the URN working group for comments on
earlier drafts of this document. This document is partially earlier drafts of this document. This document is partially
supported by the National Science Foundation, Cooperative Agreement supported by the National Science Foundation, Cooperative Agreement
NCR-9218179. NCR-9218179.
10. References 10. References
Request For Comments (RFC) and Internet Draft documents are available Request For Comments (RFC) and Internet Draft documents are available
from <URL:ftp://ftp.internic.net> and numerous mirror sites. from <URL:ftp://ftp.internic.net> and numerous mirror sites.
[1] K. R. Sollins, "Requirements and a Framework for [1] Sollins, K. R., "Requirements and a Framework for
URN Resolution Systems," Internet Draft (work in URN Resolution Systems," Work in Progress.
progress), November 1996.
[2] T. Berners-Lee, "Universal Resource Identifiers in [2] Berners-Lee, T., "Universal Resource Identifiers in
WWW," RFC 1630, June 1994. WWW," RFC 1630, June 1994.
[3] K. Sollins and L. Masinter, "Functional Require- [3] Sollins, K. and L. Masinter, "Functional Requirements
ments for Uniform Resource Names," RFC 1737. for Uniform Resource Names," RFC 1737.
December 1994. December 1994.
[4] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform [4] Berners-Lee, T., R. Fielding, L. Masinter, "Uniform
Resource Locators (URL)," Internet Draft (work in Resource Locators (URL)," Work in Progress.
progress), December 1996.
[5] Appendix A.2 of The Unicode Consortium, "The [5] Appendix A.2 of The Unicode Consortium, "The
Unicode Standard, Version 2.0", Addison-Wesley Unicode Standard, Version 2.0", Addison-Wesley
Developers Press, 1996. ISBN 0-201-48345-9. Developers Press, 1996. ISBN 0-201-48345-9.
11. Editor's address 11. Editor's address
Ryan Moats Ryan Moats
AT&T AT&T
15621 Drexel Circle 15621 Drexel Circle
Omaha, NE 68135-2358 Omaha, NE 68135-2358
USA USA
Phone: +1 402 894-9456 Phone: +1 402 894-9456
EMail: jayhawk@ds.internic.net EMail: jayhawk@ds.internic.net
Appendix A. Handling of URNs by URL resolvers/browsers. Appendix A. Handling of URNs by URL resolvers/browsers.
The URN syntax has been defined so that URNs can be used in places The URN syntax has been defined so that URNs can be used in places
where URLs are expected. A resolver that conforms to the current URL where URLs are expected. A resolver that conforms to the current URL
syntax specification [3] will extract a scheme value of "urn:" syntax specification [3] will extract a scheme value of "urn:" rather
rather than a scheme value of "urn:<nid>". than a scheme value of "urn:<nid>".
An URN MUST be considered an opaque URL by URL resolvers and passed An URN MUST be considered an opaque URL by URL resolvers and passed
(with the "urn:" tag) to an URN resolver for resolution. The URN (with the "urn:" tag) to an URN resolver for resolution. The URN
resolver can either be an external resolver that the URL resolver resolver can either be an external resolver that the URL resolver
knows of, or it can be functionality built-in to the URL resolver. knows of, or it can be functionality built-in to the URL resolver.
To avoid confusion of users, an URL browser SHOULD display the com- To avoid confusion of users, an URL browser SHOULD display the
plete URN (including the "urn:" tag) to ensure that there is no con- complete URN (including the "urn:" tag) to ensure that there is no
fusion between URN namespace identifiers and URL scheme identifiers. confusion between URN namespace identifiers and URL scheme
identifiers.
This Internet Draft expires September 30, 1997.
 End of changes. 12 change blocks. 
43 lines changed or deleted 29 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/