RFC 3187: Using International Standard Book Numbers as Uniform Resource Names
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8254.
Current document in this lineage: RFC 8254 — Uniform Resource Name (URN) Namespace Registration Transition
In plain English — editorial summary, not part of the RFC
This document discusses how International Standard Book Numbers (ISBN) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion below is based on the ideas expressed in RFC 2288. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3187
- Published
- October 2001
- Authors
- J. Hakala; H. Walravens
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 8254
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3044 (2001)
- RFC 3187 (2001)
- RFC 8254 (2017) ✓
Read the full history of Uniform Resource Name (URN) Namespace Registration Transition →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3188Using National Bibliography Numbers as Uniform Resource NamesObsoleted
October 2001
- RFC 2397The "data" URL schemeCurrent
August 1998
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2928Initial IPv6 Sub-TLA ID AssignmentsCurrent
September 2000
- RFC 29216BONE pTLA and pNLA Formats (pTLA)Current
September 2000
- RFC 2483URI Resolution Services Necessary for URN ResolutionCurrent
January 1999
- RFC 2450Proposed TLA and NLA Assignment RuleCurrent
December 1998
- RFC 2276Architectural Principles of Uniform Resource Name ResolutionUpdated
January 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?