RFC 3188: Using National Bibliography Numbers as Uniform Resource Names
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8458.
Current version: RFC 8458 — Using National Bibliography Numbers as Uniform Resource Names
In plain English — editorial summary, not part of the RFC
This document discusses how national bibliography numbers (persistent and unique identifiers assigned by the national libraries) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion is based on the ideas expressed in RFC 2288. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3188
- Published
- October 2001
- Authors
- J. Hakala
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 13
- Also known as
- —
- Obsoleted by:
- RFC 8458
Topics
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 3187Using International Standard Book Numbers as Uniform Resource NamesObsoleted
October 2001
- RFC 2483URI Resolution Services Necessary for URN ResolutionCurrent
January 1999
- RFC 2276Architectural Principles of Uniform Resource Name ResolutionUpdated
January 1998
- RFC 4854A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP)Current
April 2007
- RFC 5031A Uniform Resource Name (URN) for Emergency and Other Well-Known ServicesUpdated
January 2008
- RFC 5165A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC)Current
April 2008
- RFC 5174A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU)Current
May 2008
- RFC 6755An IETF URN Sub-Namespace for OAuthCurrent
October 2012
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?