< draft-hakala-urn-nbn-rfc3188bis-00.txt   draft-hakala-urn-nbn-rfc3188bis-02.txt >
Network Working Group J. Hakala Network Working Group J. Hakala
Internet-Draft The National Library of Finland Internet-Draft The National Library of Finland
Obsoletes: 3188 (if approved) April 16, 2018 Obsoletes: 3188 (if approved) June 14, 2018
Intended status: Informational Intended status: Informational
Expires: October 18, 2018 Expires: December 16, 2018
Using National Bibliography Numbers as Uniform Resource Names Using National Bibliography Numbers as Uniform Resource Names
draft-hakala-urn-nbn-rfc3188bis-00 draft-hakala-urn-nbn-rfc3188bis-02
Abstract Abstract
National Bibliography Numbers, NBNs, are used by the national National Bibliography Numbers (NBNs) are used by the national
libraries and other organizations in order to identify resources in libraries and other organizations in order to identify resources in
their collections. Generally, NBNs are applied to resources that are their collections. NBNs are usually applied to resources that are
not catered for by established (standard) identifier systems such as not catered for by established (standard) identifier systems such as
ISBN. ISBN.
A URN (Uniform Resource Names) namespace for NBNs was established in A URN (Uniform Resource Names) namespace for NBNs was established in
2001 in RFC 3188. Since then, several European national libraries 2001 in RFC 3188. Since then, a number of European national
have implemented URN:NBN-based systems. libraries have implemented URN:NBN-based systems.
This document replaces RFC 3188 and defines how NBNs can be supported This document replaces RFC 3188 and defines how NBNs can be supported
within the updated URN framework. A revised namespace registration within the updated URN framework. A revised namespace registration
(version 4) compliant to RFC 8141 is included. (version 4) compliant to RFC 8141 is included.
Relationship to earlier documents
This draft replaces draft-ietf-urnbis-rfc3188bis-nbn-urn-04, posted
2012-10-22.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 18, 2018. This Internet-Draft will expire on December 16, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Discussion list . . . . . . . . . . . . . . . . . . . . . 4 1.1. Discussion list . . . . . . . . . . . . . . . . . . . . . 5
2. Conventions used in this document . . . . . . . . . . . . . . 4 2. Conventions used in this document . . . . . . . . . . . . . . 5
3. Fundamental Namespace and Community Considerations for NBN . 5 3. Fundamental Namespace and Community Considerations for NBN . 5
3.1. The URN:NBN Namespace . . . . . . . . . . . . . . . . . . 5 3.1. The URN:NBN Namespace . . . . . . . . . . . . . . . . . . 5
3.2. Community Considerations for NBNs . . . . . . . . . . . . 5 3.2. Community Considerations for NBNs . . . . . . . . . . . . 6
4. National Bibliography Numbers (NBNs) . . . . . . . . . . . . 7 4. National Bibliography Number URNs . . . . . . . . . . . . . . 7
4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Assignment . . . . . . . . . . . . . . . . . . . . . . . 7
4.2. Encoding Considerations and Lexical Equivalence . . . . . 7 4.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3. Resolution and Persistence of NBN-based URNs . . . . . . 9 4.2.1. Usage of r-component and q-component . . . . . . . . 10
4.4. Additional considerations . . . . . . . . . . . . . . . . 10 4.2.2. Usage of f-component . . . . . . . . . . . . . . . . 10
4.3. Encoding Considerations and Lexical Equivalence . . . . . 10
4.4. Resolution and Persistence of NBN-based URNs . . . . . . 11
4.5. Additional considerations . . . . . . . . . . . . . . . . 13
5. URN Namespace ID (NID) Registration for the National 5. URN Namespace ID (NID) Registration for the National
Bibliography Number (NBN) . . . . . . . . . . . . . . . . . . 10 Bibliography Number (NBN) . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 16 10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 17 10.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Significant Changes from RFC 3188 . . . . . . . . . 18 Appendix A. Significant Changes from RFC 3188 . . . . . . . . . 18
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 19 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 18
B.1. draft-hakala-rfc3188bis-nbn-urn-00 to draft-ietf- B.1. draft-hakala-rfc3188bis-nbn-urn-00 to draft-ietf-
urnbis-*-00 . . . . . . . . . . . . . . . . . . . . . . . 19 urnbis-*-00 . . . . . . . . . . . . . . . . . . . . . . . 18
B.2. draft-ietf-urnbis-rfc3188bis-nbn-urn-00 to -01 . . . . . 20 B.2. draft-ietf-urnbis-rfc3188bis-nbn-urn-00 to -01 . . . . . 19
B.3. draft-ietf-urnbis-rfc3188bis-nbn-urn-01 to -02 . . . . . 20 B.3. draft-ietf-urnbis-rfc3188bis-nbn-urn-01 to -02 . . . . . 19
B.4. draft-ietf-urnbis-rfc3188bis-nbn-urn-02 to -03 . . . . . 20 B.4. draft-ietf-urnbis-rfc3188bis-nbn-urn-02 to -03 . . . . . 20
B.5. draft-ietf-urnbis-rfc3188bis-nbn-urn-03 to -04 . . . . . 21 B.5. draft-ietf-urnbis-rfc3188bis-nbn-urn-03 to -04 . . . . . 20
B.6. draft-ietf-urnbis-rfc3188bis-nbn-urn-04 (2012-10-22) to B.6. draft-ietf-urnbis-rfc3188bis-nbn-urn-04 (2012-10-22) to
draft-hakala-urn-nbn-rfc3188bis-00 . . . . . . . . . . . 21 draft-hakala-urn-nbn-rfc3188bis-00 . . . . . . . . . . . 20
B.7. draft-hakala-urn-nbn-rfc3188bis-00 (2018-06-02) to draft-
hakala-urn-nbn-rfc3188bis-01 . . . . . . . . . . . . . . 21
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21
1. Introduction 1. Introduction
One of the basic permanent URI schemes (cf. RFC 3986 [RFC3986], One of the basic permanent URI schemes (cf. RFC 3986 [RFC3986],
[IANA-URI]) is 'URN' (Uniform Resource Name) as originally defined in [IANA-URI]) is 'URN' (Uniform Resource Name). URNs were originally
RFC 2141 [RFC2141] with new definitions and registration procedure in defined in RFC 2141 [RFC2141]. In 2017, a revision was adopted with
2017 [RFC8141]. Any traditional identifier, when used within the URN new definitions and registration procedures [RFC8141]. Any
system, must to have a namespace of its own, registered with IANA traditional identifier, when used within the URN system, must have a
[IANA-URN]. National Bibliography Number (NBN) is one such namespace of its own, registered with IANA [IANA-URN]. National
namespace, specified in 2001 in RFC 3188 [RFC3188]. Bibliography Number (NBN) is one such namespace, specified in 2001 in
RFC 3188 [RFC3188].
This document describes the syntax and usage of NBN URNs, and updates
the registration of the associated URN namespace. This document
additionally describes certain policy assumptions about how National
Libraries and their partner organizations partition, delegate, and
manage the namepace. Violation of those assumptions could impact the
utility of the NBN URN namespace.
URN:NBNs are in production use in several European countries URN:NBNs are in production use in several European countries
including (in alphabetical order) Austria, Finland, Germany, Italy, including (in alphabetical order) Austria, Finland, Germany, Hungary,
Hungary, the Netherlands, Norway, Sweden, and Switzerland. The Italy, the Netherlands, Norway, Sweden, and Switzerland. The URN:NBN
URN:NBN namespace is collectively managed by these national namespace is collectively managed by these national libraries. URN:
libraries. URN: NBNs have been applied to diverse content including NBNs have been applied to diverse content including Web archives,
Web archives, digitized materials, research data, and doctoral digitized materials, research data, and doctoral dissertations. They
dissertations. They can be used by the national libraries and can be used by the national libraries and organizations co-operating
organizations co-operating with them. with them.
As a part of the initial development of the URN system in the late As a part of the initial development of the URN system in the late
1990s, the IETF URN working group agreed that it was important to 1990s, the IETF URN working group agreed that it was important to
demonstrate that the URN syntax can accommodate existing identifier demonstrate that the URN syntax can accommodate existing identifier
systems. RFC 2288 [RFC2288] investigated the feasibility of using systems. RFC 2288 [RFC2288] investigated the feasibility of using
ISBN, ISSN and SICI (see below) as URNs, with positive results; ISBN, ISSN, and SICI (for further discussion of how these systems
however, it did not formally register corresponding URN namespaces. have evolved as URNs, see the discussion in RFC 8254 [RFC8254]) as
This was in part due to the still evolving process to formalize URNs, with positive results; however, it did not formally register
criteria for namespace definition documents and registration, corresponding URN namespaces. This was in part due to the still
consolidated later in the IETF, first into RFC 2611 [RFC2611], then evolving process to formalize criteria for namespace definition
into RFC 3406 [RFC3406], and now given by RFC 8141 [RFC8141]. documents and registration, consolidated later in the IETF, first
into RFC 2611 [RFC2611], then into RFC 3406 [RFC3406], and now given
by RFC 8141 [RFC8141].
URN Namespaces have subsequently been registered for NBN (National URN Namespaces have been registered for NBN (National Bibliography
Bibliography Number), ISBN (International Standard Book Number), and Number), ISBN (International Standard Book Number), and ISSN
ISSN (International Serial Standard Number) in RFCs 3188 [RFC3188], (International Serial Standard Number) in RFCs 3188 [RFC3188], 3187
3187 [RFC3187], and 3044 [RFC3044], respectively. [RFC3187], and 3044 [RFC3044], respectively. ISBN and ISSN
namespaces were made compliant with RFC 8141 [RFC8141] in 2017 by
publishing revised ISSN [ISSN-namespace] and ISBN [ISBN-namespace]
namespace registrations.
The term "National Bibliography Number" encompasses persistent local The term "National Bibliography Number" encompasses persistent local
identifier systems that the national libraries and their partner identifier systems that the national libraries and their partner
organizations use in addition to the more formally (and organizations use in addition to the more formally (and
internationally) established identifiers. These partner internationally) established identifiers. These partner
organizations include university libraries, universities and other organizations include universities and their libraries and other
research organizations and governmental organizations. Some national subsidiaries, other research institutions, plus governmental and
libraries have a lot of these liaisons; for instance, the German public organizations. Some national libraries maintain a significant
number of these liaison relationships; for instance, the German
National Library had almost 400 by early 2018 [NBN-Resolving]. National Library had almost 400 by early 2018 [NBN-Resolving].
In practice, NBN differs from standard identifier systems such as In practice, NBN differs from standard identifier systems such as
ISBN and ISSN because it is not a single identifier system with ISBN and ISSN because it is not a single identifier system with
standard-specified scope and syntax. Each NBN implementer creates standard-specified scope and syntax. Each NBN implementer creates
its own system with its own syntax and assignment rules. Each user its own system with its own syntax and assignment rules. Each user
organization is also obliged to keep track of how NBNs are being organization is also obliged to keep track of how NBNs are being
used, but within the generic framework set in this document, local used; however, within the generic framework set in this document,
NBN assignment policies may vary considerably. local NBN assignment policies may vary considerably.
Historically, NBNs were only applied in the national bibliographies Historically, NBNs have been applied in the national bibliographies
to identify the resources catalogued into it. Prior to the emergence to identify the resources catalogued into them. Prior to the
of bibliographic standard identifiers identifiers in the early 1970s, emergence of bibliographic standard identifiers in the early 1970s,
every publication got an NBN. national libraries assigned NBNs to all catalogued publications.
Since the late 1990s, the NBN scope has been extended to cover a vast Since the late 1990s, the NBN scope has been extended to cover a vast
range of digitized and born digital resources. Only a small subset range of resources, both originally digital and digitized. Only a
of these resources is cataloged in the national bibliographies or small subset of these resources is cataloged in the national
other bibliographic databases. Digitized resources and their bibliographies or other bibliographic databases. Digitized resources
component parts (such as still images in books, or journal articles) and their component parts (such as still images in books or journal
are examples of resources that may get NBNs. articles) are examples of resources that may get NBNs.
It is possible to extend the scope of the NBN much further. The It is possible to extend the scope of the NBN much further. The
National Library of Finland is using them in the Finnish National National Library of Finland is using them in the Finnish National
Ontology Service Finto to identify corporate names (see Ontology Service Finto to identify corporate names (see
http://finto.fi/cn/en/). NBNs to identify metadata elements provides http://finto.fi/cn/en/). Using NBNs to identify metadata elements
a stable basis for creation of linked data. provides a stable basis for creation of linked data.
Simple guidelines for using NBNs as URNs and the original namespace Simple guidelines for using NBNs as URNs and the original namespace
registration were published in RFC 3188 [RFC3188]. The RFC at hand registration were published in RFC 3188 [RFC3188]. The RFC at hand
replaces RFC 3188; sections discussing the methods in which URN:NBNs replaces RFC 3188; sections discussing the methods by which URN:NBNs
should be resolved have been updated, unused features have been should be resolved have been updated, unused features have been
eliminated, and the text is compliant with the stipulations of the eliminated, and the text is compliant with the stipulations of the
revised URN specification [RFC8141]. revised URN specification [RFC8141].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.1. Discussion list 1.1. Discussion list
Comments are welcome and should be directed to the urn@ietf.org Comments are welcome and should be directed to the urn@ietf.org
mailing list or the authors. mailing list or to the author.
[[CREF1: RFC-Editor: this subsection to be deleted before RFC [[CREF1: RFC-Editor: this subsection to be deleted before RFC
publication.]] publication.]]
2. Conventions used in this document 2. Conventions used in this document
"NBN" refers to any National Bibliography Number identifier system "NBN" refers to any National Bibliography Number identifier system
used by the national libraries and other institutions, which use used by the national libraries (or equivalent organizations) and
these identifiers with the national library's support and permission. other institutions, which use these identifiers with national
libraries' support and permission.
In this memo, "URN:NBN" is used as a shorthand for "NBN-based URN". In this memo, "URN:NBN" is used as a shorthand for "NBN-based URN".
3. Fundamental Namespace and Community Considerations for NBN 3. Fundamental Namespace and Community Considerations for NBN
3.1. The URN:NBN Namespace 3.1. The URN:NBN Namespace
NBNs are widely used to identify both hand-held and digital resources NBNs are widely used to identify both hand-held and digital resources
in the collections of national libraries and other institutions that in the collections of national libraries and other institutions that
are responsible for preserving the cultural heritage of their are responsible for preserving the cultural heritage of their
constituents. Resources in these collections are usually preserved constituents. Resources in these collections are usually preserved
for a long time (i.e., for centuries). While the preferred methods for a long time (i.e., for centuries). While the preferred methods
for digital preservation may vary over time and depending on the for digital preservation may vary over time and depend on the
content, the favorite one is currently migration. Whenever content, the favorite one has been migration. Whenever necessary, a
necessary, a resource in outdated file format is migrated into a more resource in outdated file format is migrated into a more modern file
modern file format. All old versions of the resource are also kept, format. To the extent possible, all old versions of the resource are
in order to alleviate the negative effects of partially successful also kept, in order to alleviate the negative effects of partially
migrations and gradual loss of original look and feel that may successful migrations and gradual loss of original look and feel that
accompany even fully successful migrations. When there are multiple may accompany even fully successful migrations. When NBN is used to
manifestations of a digital object, each one SHOULD have its own NBN. identify manifestations and there are many of them for a single work,
local policy can require that each manifestation ought to have its
own NBN.
NBNs SHOULD only be used for objects when standard identifiers such NBNs are typically used to identify objects for which standard
as ISBN are not applicable. However, NBNs MAY be used for component identifiers such as ISBN are not applicable. However, NBNs can be
resources even when the resource as a whole qualifies for a standard used for component resources even when the resource as a whole
identifier. For instance, even if a digitized book has an ISBN, JPEG qualifies for a standard identifier. For instance, if a digitized
image files of its pages get NBNs. These URN:NBNs can be used as book has an ISBN, JPEG image files of its pages might be assigned
persistent links to the pages. NBNs. These URN:NBNs can be used as persistent links to the pages.
The scope of standard identifier systems such as ISBN and ISSN is The scope of standard identifier systems such as ISBN and ISSN is
limited; they are applicable only to certain kinds of resources. limited; they are applicable only to certain kinds of resources. One
Generally speaking, the role of the NBN is to fill in the gaps. of the roles of the NBN is to fill in the gaps left by the standard
Collectively, the standard identifiers and NBNs cover all resources identifiers. Collectively, these identifiers and NBNs cover all
the national libraries and their partners need to preserve for the resources the national libraries and their partners need to include
long term. in their collections.
Section 4 below, and there in particular Section 4.1, presents a more Section 4 below, and particularly Section 4.1, present a more
detailed overview of the structure of the NBN namespace, related detailed overview of the structure of the NBN namespace, related
institutions, and the identifier assignment principles used. institutions, and the identifier assignment principles used.
3.2. Community Considerations for NBNs 3.2. Community Considerations for NBNs
National libraries are the key organizations providing persistent URN National libraries are the key organizations providing persistent URN
resolution services for resources identified with NBNs, independent resolution services for resources identified with NBNs, independent
of their form. National libraries MAY allow other organizations such of their form. As co-ordinators of NBN usage, national libraries
as university libraries or governmental organizations to assign NBNs have allowed other organizations such as university libraries or
to the resources they preserve for long term. In such case, the governmental organizations to assign NBNs to the resources these
national library MUST co-ordinate the use of NBNs at the national organizations preserve for the long term. In such case, the national
level. National libraries can also provide URN resolution services library co-ordinates the use of NBNs at the national level. National
and technical services to other NBN users. These organizations MUST libraries can also provide URN resolution services and technical
services to other NBN users. These organizations are expected to
either establish their own URN resolution services or use the either establish their own URN resolution services or use the
technical infrastructure provided by the national library. In the technical infrastructure provided by the national library. URN:NBNs
URN:NBN namespace, each persistent identifier should be resolvable are expected to be resolvable and support one or more resolution
and provide one or more resolution services. services.
NBNs MAY be used to identify component resources, but the NBN Although NBNs can be used to identify component resources, the NBN
Namespace does not specify a generic, intrinsic syntax for doing Namespace does not specify a generic, intrinsic syntax for doing
that. However, there are at least three different ways in which that. However, there are at least two different ways in which
component resources can be identified and used within the NBN component resources can be taken into account within the NBN
namespace. namespace.
The simplest and probably the most common approach is to assign a The simplest and probably the most common approach is to assign a
separate NBN for each component resource such as a file containing a separate NBN for each component resource such as a file containing a
digitized page of a book, and make no provisions to make such NBNs digitized page of a book, and make no provisions to make such NBNs
discernible in a systematical way from others. The URN:NBN assigned discernible in a systematical way from others.
to the component resource enables direct and persistent access to the
page, which might otherwise be available only via browsing the book
from the title page to the page wanted.
Second, a local "fragment" syntax MAY be used to identify component
resources in a structured manner within the NSS, independently of the
requirements of RFC 3986. These private fragment identifiers SHOULD
be recognized as such by the appropriate URN resolver application.
The resolver SHOULD be able to process the fragment part in the URN:
NBN correctly; if so, the result is the identified component part of
the resource. For instance, if the resource is a database table, the
identified component could be a single data element stored in the
table.
Finally, if the stipulations of the URI Generic Syntax [RFC3986] and Second, if the stipulations of the URI Generic Syntax [RFC3986] and
the Internet media type specification [RFC2046] are met, in the Internet media type specification [RFC2046] are met, in
accordance with the provisions in RFC 8141, the URN f-component MAY accordance with the provisions in RFC 8141, the URN f-component can
be attached to URN:NBNs in order to indicate the desired location be attached to URN:NBNs in order to indicate the desired location
within the resource supplied by URN resolution. within the resource supplied by URN resolution.
Note that the f-component is not a part of the NSS and therefore the From the library community point of view it is important that the
component part is not identified. Moreover, the resolution process f-component is not a part of the NSS and therefore f-component
SHALL retrieve the entire resource. The fragment selection is attachment does not mean that the relevant component part is
applied by the resolution client (e.g., browser) to the media identified. Moreover, the resolution process still retrieves the
returned by the resolution process. In other words, in this latter entire resource even if there is an f-component. The component part
case the fragments are logical and physical components of the selection is applied by the resolution client (e.g., browser) to the
identified resource whereas in the former cases these "fragments" are resource returned by the resolution process. In other words, in this
actually complete, independently named entities. latter case the component parts are just logical and physical parts
of the identified resource whereas in the former cases they are
independently named entities.
Resources identified by NBNs are not always available in the Resources identified by NBNs are not always available in the
Internet. In that case, a surrogate such as a metadata record of the Internet. If one is not, the URN:NBN can resolve to a surrogate such
identified resource can be supplied. as a metadata record describing the identified resource.
If an NBN identifies an immaterial work, descriptive metadata about
the work SHOULD be supplied. The metadata record MAY contain links
to Internet-accessible digital manifestations of the work.
Section 4 below, and in particular Section 4.3 therein, presents a Section 4 below, and particularly its Section 4.4, presents a
detailed overview of the application of the URN:NBN Namespace as well detailed overview of the application of the URN:NBN Namespace as well
as the principles of, and systems used for, the resolution of NBN- as the principles of, and systems used for, the resolution of NBN-
based URNs. based URNs.
4. National Bibliography Numbers (NBNs) 4. National Bibliography Number URNs
4.1. Overview 4.1. Assignment
National Bibliography Number (NBN) is a generic term referring to a National Bibliography Number (NBN) is a generic term referring to a
group of identifier systems administered by the national libraries group of identifier systems administered by national libraries and
and institutions authorized by them. The NBN assignment is typically institutions authorized by them. The NBN assignment is typically
performed by the organization hosting the resource. National performed by the organization hosting the resource. National
libraries are committed to permanent preservation of their deposit libraries are committed to permanent preservation of their deposit
collections. collections.
Assignment of NBN-based URNs is controlled on national level by the
national library (or national libraries, if there is more than one).
National guidelines can differ, but the identified resources
themselves are usually persistent.
Different national URN:NBN assignment policies have resulted in
varying levels of control of the assignment process. Manual URN:NBN
assignment by the library personnel provides the tightest control,
especially if the URN:NBNs cover only resources catalogued into the
national bibliography. In most national libraries, the scope of
URN:NBN is already much broader than this. Usage rules can vary
within one country, from one URN:NBN sub-namespace to the next.
Each national library uses NBNs independently of other national Each national library uses NBNs independently of other national
libraries; apart from this document, there is no global authority libraries; apart from this document, there are no guidelines which
that specifies or controls NBN usage. NBNs as such are unique only specify or control NBN usage. NBNs as such are unique only on the
on the national level. When used as URNs, base NBN strings MUST be national level. When used as URNs, base NBN strings MUST be
augmented with a controlled prefix, which is the particular nation's augmented with a controlled prefix, which is the particular nation's
ISO 3166-1 alpha-2 two-letter country code. These prefixes guarantee ISO 3166-1 alpha-2 two-letter country code (referred to as "ISO
uniqueness of the URN:NBNs at the global scale [Iso3166MA"/>. country code" below) [ISO3166-1]. These prefixes guarantee
uniqueness of the URN:NBNs at the global scale [Iso3166MA].
A national library using URN:NBNs SHOULD specify a local assignment National libraries using URN:NBNs usually specify local assignment
policy; such policy SHOULD limit the URN:NBN usage to the information policies for themselves. Such policy can limit the URN:NBN usage to
resources stored permanently in the national library's digital e.g. the resources stored in the national library's digital
collections or databases. A more liberal URN:NBN assignment policy collections or databases. Athough this specification does not
MAY be applied, but NBNs assigned to a short-lived resources SHOULD specify principles for URN:NBN assignment policies that can be
NOT be made URN: NBNs. applied, NBNs assigned to short-lived resources should not be made
URN:NBNs unless such policy can be justified.
URN:NBN assignment policy SHOULD also clarify the local policy URN:NBN assignment policy can clarify for instance the local policy
concerning identifier assignment to component parts of resources, and concerning identifier assignment to component parts of resources, and
specify with sufficient detail the syntax of local component specify with sufficient detail the syntax of local component
identifiers (if there is one as a discernible part of the NBNs). The identifiers (if there is one as a discernible part of the NBNs). The
policy SHOULD also cover any employed extensions to the default NBN policy can also cover any employed extensions to the default NBN
scope (e.g., to cover identification of metadata elements). scope.
4.2. Encoding Considerations and Lexical Equivalence NBNs as such are locally but not globally unique; two national
libraries can assign the same NBN to different resources. A prefix,
based on the ISO country code as described above, guarantees the
global uniqueness of URN:NBNs. An NBN, once it has been assigned to
a resource, MUST be persistent, and therefore URN:NBNs are persistent
as well.
Expressing NBNs as URNs is usually straightforward, as traditionally A URN:NBN, once it has been generated from a NBN, MUST NOT be re-
only ASCII characters have been used in NBN strings. If necessary, used for another resource.
NBNs must be translated into canonical form as specified in RFC 8141.
Users of the URN:NBN namespace MUST ensure that they do not assign
the same URN:NBN twice. Different policies can be applied to
guarantee this. For instance, NBNs and corresponding URN:NBNs can be
assigned sequentially by programs in order to avoid human mistakes.
It is also possible to use printable representations of checksums
such as SHA-1 [RFC6234] as NBNs.
4.2. Syntax
The namespace-specific string (NSS) will consist of three parts:
o a prefix, consisting of an ISO 3166-1 alpha-2 country code and
optional sub-namespace code(s) separated by colon(s),
o a hyphen (-) as the delimiting character, and
o an NBN string assigned by the national library or sub-delegated
authority.
The following formal definition uses ABNF [RFC5234].
nbn_nss = prefix "-" nbn_string
prefix = iso_cc *( ":" subspc )
; the entire prefix is case-insensitive
iso_cc = 2ALPHA
; alpha-2 country code as assigned by ISO 3166, part 1
; (identifies the national library to which the branch
; is delegated)
subspc = 1*(ALPHA / DIGIT)
; as assigned by the respective national library
nbn_string = path-rootless
; the "path-rootless" rule is defined in RFC 3986.
; syntax requirements specified in RFC 8141 MUST be
; taken into account.
Colon SHOULD be used within the prefix only as a delimiting character
between the ISO 3166-1 country code and sub-namespace code(s), which
split the national namespace into smaller parts.
The structure (if any) of the nbn_string is determined by the
authority for the prefix. Whereas the prefix is regarded as case-
insensitive, NBN strings can be case-sensitive at the preference of
the assigning authority; parsers therefore MUST treat these as case-
sensitive; any case mapping needed to introduce case-insensitivity is
the responsibility of the relevant resolution system.
Hyphen SHOULD be used as the delimiting character between the prefix
and the NBN string. Within the NBN string, hyphen MAY be used for
separating different sections of the identifier from one another.
All two-letter codes are reserved by the ISO 3166 Maintenance Agency
for either existing and possible future ISO country codes (or for
private use).
Sub-namespace identifiers MUST be registered on the national level by
the national library that assigned the identifier. The list of such
identifiers can be made publicly available via the Web.
Note: Because case mapping for ASCII letters is completely reversible
and does not lose information, the case used in case-insensitive
matching is a local matter; implementations can convert to lower or
upper case as they see fit; they only need to do it consistently.
4.2.1. Usage of r-component and q-component
URN:NBN resolvers do not currently support the use of either
r-component or q-component.
Resolution services based on r-component can be implemented in the
future when the r-component syntax and semantics has been specified.
4.2.2. Usage of f-component
If URN:NBN resolves to the identified resource and the media type of
the resource supports f-component usage, it can be used to indicate a
location within the identified resource. Persistence is achieved if
the URN:NBN is assigned to one and only one version of a resource,
such as PDF/A version of a book.
The URN:NBN Namespace does not impose any restrictions of its own on
f-component usage.
4.3. Encoding Considerations and Lexical Equivalence
Expressing NBNs as URNs is usually straightforward, as normally only
ASCII characters are used in NBN strings. If this is not the case,
non-ASCII characters in NBNs MUST be translated into canonical form
as specified in RFC 8141. If a national library uses NBNs that can
contain percent-encoded characters higher than U+007F, the library
needs to carefully define the canonical transformation from theseNBNs
into URNs, including normalization forms.
When an NBN is used as a URN, the namespace-specific string (NSS) When an NBN is used as a URN, the namespace-specific string (NSS)
MUST consist of three parts: MUST consist of three parts:
o a prefix, structured as a primary prefix, which is a two-letter o a prefix, structured as a primary prefix, which is a two-letter
ISO 3166-1 country code, and zero or more secondary prefixes, each ISO 3166-1 country code of the library's country, and zero or more
indicated by a delimiting colon character (:) and a sub-namespace secondary prefixes, each indicated by a delimiting colon character
identifier, (:) and a sub-namespace identifier,
o a hyphen (-) as a delimiting character, and o a hyphen (-) as a delimiting character, and
o the NBN string. o the NBN string.
The prefix is case-insensitive. An NBN string can be either case-
sensitive or case-insensitive, depending on the NBN syntax applied.
Future implementers of NBNs SHOULD make their NBN strings case-
insensitive.
Different delimiting characters are not semantically equivalent. Different delimiting characters are not semantically equivalent.
Use of colon as the delimiting character is allowed if and only if The syntax and roles of the three parts listed above are described in
the country code-based NBN namespace (identified by the respective Section 4.2.
ISO 3166-1 country code used as the primary part of the prefix) is
split further into smaller sub-namespaces, in which case the colon
separates the ISO 3166-1 country code from the sub-namespace
identifier. These subdivisions (including the colon separator) form
an optional part of the prefix. A colon MUST NOT be used for any
other purpose in the prefix.
A hyphen MUST be used for separating the prefix and the NBN string,
or the part of the NBN string that is assigned to the identified
object by a sub-division authority.
If there are several national libraries in one country, these If there are several national libraries in one country, these
libraries MUST agree on how to divide the national namespace between libraries MUST agree on how to divide the national namespace between
themselves using this method before the URN:NBN assignment begins in themselves using this method before the URN:NBN assignment begins in
any of these libraries. any of these libraries.
A national library MAY also assign to trusted organization(s) -- such A national library MAY also assign URN:NBN sub-namespaces to trusted
as a university or a government institution -- its own NBN sub- organizations such as universities or government institutions. The
namespace. The sub-namespace MAY be further divided by the partner sub-namespace MAY be further divided by the partner organization.
organization (the national library MUST be informed about these sub- All sub-namespace identifiers used within a country-code-based
namespaces).
Being part of the prefix, sub-namespace identifier strings are case-
insensitive. They MUST NOT contain any hyphens.
The sub-namespace identifiers used beneath a country-code-based
namespace MUST be registered on the national level by the national namespace MUST be registered on the national level by the national
library that assigned the code. The national register of these codes library that assigned the code. The national register of these codes
SHOULD be made available online. SHOULD be made available online.
Being part of the prefix, sub-namespace identifier strings are case-
insensitive. They MUST NOT contain any colons or hyphens.
Formally, two URN:NBNs are lexically equivalent if they are octet-
by-octet equal after the following (conceptional) preprocessing:
1. convert all characters in the leading "urn:nbn:" token to a
single case;
2. convert all characters in the prefix (country code and its
optional sub-divisions) to a single case;
3. convert all characters embedded in any percent-encodings to a
single case;
Models (indicated linebreak inserted for readability): Models (indicated linebreak inserted for readability):
URN:NBN:<ISO 3166 alpha-2 country code>-<assigned NBN string> URN:NBN:<ISO 3166 alpha-2 country code>-<assigned NBN string>
URN:NBN:<ISO 3166 alpha-2 country code>:<sub-namespace code>-\ URN:NBN:<ISO 3166 alpha-2 country code>:<sub-namespace code>-\
<assigned NBN string> <assigned NBN string>
Examples: Examples:
URN:NBN:fi-fe201003181510 URN:NBN:fi-fe201003181510
urn:nbn:ch:bel-9039 urn:nbn:ch:bel-9039
urn:nbn:se:uu:diva-3475 urn:nbn:se:uu:diva-3475
urn:nbn:hu-3006 urn:nbn:hu-3006
4.3. Resolution and Persistence of NBN-based URNs 4.4. Resolution and Persistence of NBN-based URNs
Eventually, URNs might be resolved with the help of a resolver Eventually, URNs might be resolved with the help of a global resolver
discovery service (RDS). Since no such system has been installed yet discovery service (GRDS), and URN:NBN syntax makes it possible to
in the Internet, URN:NBNs are usually embedded in HTTP URIs in order locate the relevant resolver. Since no GRDS system has been
to make them actionable in the present Internet. In these HTTP URIs, installed yet in the Internet, URN:NBNs are embedded in HTTP URIs in
the authority part must point to the appropriate URN resolution order to make them actionable in the present Internet. In these HTTP
URIs, the authority part must point to the appropriate URN resolution
service. For instance, in Finland, the address of the national URN service. For instance, in Finland, the address of the national URN
resolver is <http://urn.fi>. Thus the HTTP URI for the Finnish URN resolver is <http://urn.fi>. Thus the HTTP URI for the Finnish URN
in the example above is <http://urn.fi/URN:NBN:fi-fe201003181510>. in the example above is <http://urn.fi/URN:NBN:fi-fe201003181510>.
The country code-based prefix part of the URN:NBN namespace-specific The country code-based prefix part of the URN:NBN namespace-specific
string will provide a hint needed to find the correct resolution string will provide a hint needed to find the correct resolution
service for URN:NBNs from the global resolver discovery service when service for URN:NBNs from the GRDS when it is established.
it is established.
There are three inter-related aspects of persistence that need to be There are three inter-related aspects of persistence that need to be
discussed: persistence of the objects itself, persistence of the discussed: persistence of the objects itself, persistence of the
identifier, and persistence of the URN resolvers. identifier, and persistence of the URN resolvers.
NBNs have traditionally been assigned to printed resources, which NBNs have traditionally been assigned to printed resources, which
tend to be persistent. In contrast, digital resources require tend to be persistent. In contrast, digital resources require
frequent migrations to guarantee accessibility. Although it is frequent migrations to guarantee accessibility. Although it is
impossible to estimate how often migrations are needed, hardware and impossible to estimate how often migrations are needed, hardware and
software upgrades take place frequently, and a life time exceeding software upgrades take place frequently, and a life time exceeding
10-20 years can be considered as long. 10-20 years can be considered as long.
However, it is a common practice to keep also the original and However, it is a common practice to keep also the original and
previously migrated versions of resources. Therefore even outdated previously migrated versions of resources. Therefore even outdated
versions of resources can be available, no matter how old or versions of resources can be available in digital archives, no matter
difficult to use they have become. how old or difficult to use they have become.
If all versions of a resource are kept, a user who requires If all versions of a resource are kept, a user who requires
authenticity may retrieve the original version of the resource, authenticity can retrieve the original version of the resource,
whereas a user to whom the ease of use is a priority is likely to be whereas a user to whom the ease of use is a priority is likely to be
satisfied with the latest version. In order to enable the users to satisfied with the latest version. In order to enable the users to
find the best match, an archive can link all manifestations of a find the best match, a national library can link all manifestations
resource to each other (possibly via a work level metadata record) so of a resource to each other so as to make a user aware of them.
as to make the users aware of them.
Thus, even if specific versions of digital resources are not normally Thus, even if specific versions of digital resources are not normally
persistent, persistent identifiers such as URN:NBNs support persistent, persistent identifiers such as URN:NBNs support
information architectures that enable persistent access to any information architectures that enable persistent access to any
version of the resource, including ones which can only be utilized by version of the resource, including ones which can only be utilized by
using digital archeology tools such as custom made applications to using digital archeology tools such as custom made applications to
render the resource. render the resource.
Persistence of URN resolvers themselves is mainly an organizational Persistence of URN resolvers themselves is mainly an organizational
issue, related to the persistence of organizations maintaining them. issue, related to the persistence of organizations maintaining them.
As URN:NBN resolution services will be supplied (primarily) by the As URN:NBN resolution services will be supplied (primarily) by the
national libraries, these services are likely to be long-lived. national libraries, these services are likely to be long-lived.
4.4. Additional considerations 4.5. Additional considerations
URN:NBNs (or other persistent identifiers) SHOULD be applied to all It is a good idea to apply URN:NBNs (or other persistent identifiers)
resources which have been prioritized in the organization's digital to all resources that have been prioritized in the organization's
preservation plan. digital preservation plan.
URN:NBNs SHOULD NOT be assigned to resources that are known to not be Assignment of URN:NBNs to resources that are known to not be
persistent. URN:NBNs MAY however be applied to resources that have a persistent should be considered carefully. URN:NBNs can however be
low-level preservation priority and will not be migrated to more applied to resources that have a low-level preservation priority and
modern file formats. will not be migrated to more modern file formats or preserved via
emulation.
If the identified version of a resource has disappeared, the If the identified version of a resource has disappeared, the
resolution process SHOULD supply a surrogate if one exists, such as resolution process can supply a surrogate if one exists. A surrogate
the original printed version of a resource, or a more modern digital can be for instance a more modern digital version of the original
version of that resource. electronic resource.
5. URN Namespace ID (NID) Registration for the National Bibliography 5. URN Namespace ID (NID) Registration for the National Bibliography
Number (NBN) Number (NBN)
This URN Namespace registration describes how National Bibliography This URN Namespace registration describes how National Bibliography
Numbers (NBNs) can be supported within the URN framework; it uses the Numbers (NBNs) can be supported within the URN framework; it uses the
updated IANA template specified in RFC 8141. updated IANA template specified in RFC 8141.
Namespace ID: NBN Namespace Indentifier: NBN
This Namespace ID was formally assigned to the National This Namespace ID was formally assigned to the National
Bibliography Number in October 2001 when the namespace was Bibliography Number in October 2001 when the namespace was
registered officially [RFC3188]. Utilization of URN:NBNs had registered officially [RFC3188]. Utilization of URN:NBNs had
started in demo systems already in 1998. Since 2001, tens of started in demo systems already in 1998. Since 2001, tens of
millions of URN:NBNs have been assigned. The number of users of millions of URN:NBNs have been assigned. The number of users of
the namespace has grown in two ways: new national libraries have the namespace has grown in two ways: new national libraries have
started using NBNs, and many national libraries using the system started using NBNs, and many national libraries using the system
have formed new liaisons. have formed new liaisons.
Kind of named resources: Version: 4
Resources (digital or otherwise) in the collections of national
libraries and their partner organizations.
Component parts of identified resources.
Metadata records describing the identified resources.
Individual data elements in identified metadata records.
Registration Information: Date: 2018-04-09
Version: 4
Date: 2018-04-09
Declared registrant of the namespace: Registrant:
Name: Juha Hakala Name: Juha Hakala
Affiliation: Senior Adviser, The National Library of Finland Affiliation: Senior Adviser, The National Library of Finland
Email: juha.hakala@helsinki.fi Email: juha.hakala@helsinki.fi
Postal: P.O.Box 15, 00014 Helsinki University, Finland Postal: P.O.Box 15, 00014 Helsinki University, Finland
Web URL: http://www.nationallibrary.fi/ Web URL: http://www.nationallibrary.fi/
The National Library of Finland registered the namespace on behalf The National Library of Finland registered the namespace on behalf
of the Conference of the European National Librarians (CENL) and of the Conference of the European National Librarians (CENL) and
Conference of Directors of National Libraries (CDNL). The NBN Conference of Directors of National Libraries (CDNL). The NBN
namespace is available for free for the national libraries. They namespace is available for free for the national libraries. They
MAY allow other organizations to assign URN:NBNs and use the can allow other organizations to assign URN:NBNs and use the
resolution services established by the library for free or for a resolution services established by the library for free or for a
fee. The fees, if collected, SHOULD be based on, e.g., the fee. The fees, if collected, can be based on, e.g., the
maintenance costs of the system. maintenance costs of the system.
Declaration of syntactic structure of NSS part: Purpose: See Section 3 of RFC XXXX
The namespace-specific string (NSS) will consist of three parts:
* a prefix, consisting of an ISO 3166-1 alpha-2 country code and
optional sub-namespace code(s) separated by colon(s),
* a hyphen (-) as the delimiting character, and
* an NBN string assigned by the national library or sub-delegated
authority.
Formal declaration of the NSS:
This definition uses ABNF [RFC5234].
nbn_nss = prefix "-" nbn_string
prefix = iso_cc *( ":" subspc )
; the entire prefix is case-insensitive
iso_cc = 2ALPHA
; country code as assigned by ISO 3166, part 1 --
; identifies the national library
; to which the branch is delegated
subspc = 1*(ALPHA / DIGIT)
; as assigned by the respective national library
nbn_string = &lt;specific per prefix&gt;
; MUST adhere to RFC 3986 &lt;path-rootless&gt; syntax;
; parsers must regard nbn_strings as case-sensitive
Colon MAY be used as a delimiting character only within the
prefix, between ISO 3166-1 country code and sub-namespace code(s),
which split the national namespace into smaller parts.
Whereas the prefix is regarded as case-insensitive, NBN-strings
MAY be case-sensitive at the preference of the assigning
authority; parsers therefore MUST treat these as case-sensitive;
any case mapping needed to introduce case-insensitivity MUST be
implemented in the responsible resolution system.
Hyphen MUST be used as the delimiting character between the prefix
and the NBN string. Within the NBN string, hyphen MAY be used for
separating different sections of the identifier from one another.
All two-letter codes are reserved by the ISO 3166 Maintenance
Agency for either existing and possible future ISO country codes
(or for private use).
Sub-namespace identifiers MUST be registered on the national level
by the national library that assigned the code. The list of such
identifiers SHOULD be available via the Web.
See Section 4.2 of RFC XXXX for examples.
Relevant ancillary documentation:
National Bibliography Number (NBN) is a generic name referring to
a group of identifier systems used by the national libraries and
their partner organizations for identification of resources (and
their component parts) that lack a 'canonical' identifier. The
scope of NBN has been extended to also include, e.g., metadata
records and their elements. Each national library uses NBNs
independently of other national libraries; there is neither a
general standard defining the NBN syntax nor a global authority to
control the use of these identifier systems.
The syntax of NBN strings is specified locally. NBNs used in
national bibliographies contain only characters that belong to the
US-ASCII character set. Following the expansion of the NBN scope
and semi- and fully automated NBN assignment processes, some
future NBNs MAY contain characters that MUST be translated into
canonical form according to the specifications in RFC 8141.
Conformance with URN syntax:
The NSS syntax specified in this registration is in full
conformance with RFC 8141 and its predecessors.
Rules for lexical equivalence of NSS part:
The prefix, consisting of an ISO 3166-1 country code and its
(optional) sub-divisions, is case-insensitive. The NBN string MAY
be case-sensitive or case-insensitive, depending on the rules
chosen by the NBN authority designated by the prefix; therefore,
general-purpose resolver clients without sub-namespace specific
knowledge) MUST treat NBN strings as case-sensitive. Syntax
requirements expressed in RFC 8141 MUST be taken into account.
Formally, two URN:NBNs are lexically equivalent if they are octet-
by-octet equal after the following (conceptional) preprocessing:
1. normalize the case of the leading "urn:" token;
2. normalize the case of the prefix (country code and its
optional sub-divisions);
3. normalize the case of any percent-encoding;
Note: The case used in the normalization steps is a local matter;
implementations can normalize to lower or upper case as they see
fit, they only need to do it consistently.
Usage of r-component and q-component:
URN:NBN resolvers MAY support several services. Some of them have
been formally specified in RFC 2483; some remain unspecified.
Examples of existing relevant services are URI to URL or URLs, URI
to URN or URNs, URI to resource or resources, and URI to resource
metadata. In the latter case it is important to be able to
indicate the preferred metadata format or the completeness of the
metadata record or the metadata content requested such as table of
contents. A URN resolver maintained by a national library can
utilize for instance the national bibliography, digital asset
management systems and digital preservation systems to supply
these services.
Examples of services that can be specified and implemented in the
future: request the oldest and most original version of the
resource; request the latest version of the resource, and request
rights metadata related to the resource.
Depending on the technical infrastructure within which digital
resources are preserved and made available, any service can be
provided either via q-component, r-component or both.
Usage of f-component:
If URI-to-resource service is used and the media type of a
resource supports the use of an f-component, it can be used to
indicate a location within the identified resource because NBNs
SHOULD be assigned to one and only one version of a resource, such
as a PDF version of an article.
The URN:NBN Namespace does not impose any restrictions of its own
on f-component usage.
Identifier uniqueness and persistence considerations:
NBNs as such are not unique; different national libraries can
assign the same NBN to different resources. Therefore, to
guarantee the uniqueness of URN:NBNs, a prefix, based on the ISO
country code, is added to the resource. An NBN, once it has been
assigned to a resource, MUST be persistent, and therefore URN:NBNs
are persistent as well.
A URN:NBN, once it has been generated from a NBN, MUST NOT be re- Syntax: See Section 4.2 of RFC XXXX
used for another resource.
Users of the URN:NBN namespace MUST ensure that they do not assign Assignment: See Section 4.1 of RFC XXXX
the same URN:NBN twice. Different policies can be applied to
guarantee this. For instance, NBNs and corresponding URN:NBNs MAY
be assigned sequentially by programs in order to avoid human
mistakes. It is also possible to use printable representations of
checksums such as SHA-1 [RFC6234] or MD5 [RFC1321] as NBNs.
Process of identifier assignment: Security and Privacy: See Section 7 of RFC XXXX
Assignment of NBN-based URNs MUST be controlled on national level Interoperability:
by the national library (or national libraries, if there is more National libraries and their partners usually apply URN:NBNs if a
than one). National guidelines MAY differ, but the identified standard identifier such as ISBN is not applicable for the
resources themselves SHOULD be persistent. resource to be identified. Some overlap with other URN namespaces
is possible.
Different URN:NBN assignment policies have resulted in varying URN:NBNs may contain characters which must be percent-encoded, but
levels of control of the assignment process. Manual URN usually they consist of printable ASCII characters only.
assignment by the library personnel provides the tightest control,
especially if the URN:NBNs cover only resources catalogued into
the national bibliography. In most national libraries, the scope
of URN:NBN is already much broader than this. Usage rules MAY
vary within one country, from one URN:NBN sub-namespace to the
next. As of yet, there are no international guidelines for
URN:NBN use beyond those expressed in this document.
Process for identifier resolution: Resolution: See Section 4.4 of RFC XXXX
See Section 4.3 of RFC XXXX.
Validation mechanism: Documentation: RFC XXXX
None specified on the global level (beyond a routine check of
those characters that require special encoding when employed in
URIs). NBNs may have a well specified and rich syntax (including,
e.g., fixed length and checksum). In such case, it is possible to
validate the correctness of NBNs programmatically.
Scope: Revision Information:
NBNs are applied to resources held in the collections of national This version of the URN:NBN namespace registration has beens
libraries and their partner organizations. NBNs may also be used updated to use the revised definition of URN syntax from RFC 8141,
to identify, e.g., component parts of these resources or metadata although usage of r-components is not specified yet. In addition,
records describing resources or their component parts. non-ISO 3166 (country code) based NBNs have been deleted due to
lack of deployment. The entire NBN prefix is now specified to be
case-insensitive in accordance with established practice. This
version also includes numerous clarifications based on actial
usage of UR:NBNs.
6. IANA Considerations 6. IANA Considerations
IANA is asked to update the existing registration of the Formal URN IANA is asked to update the existing registration of the Formal URN
Namespace 'NBN' using the template given above in Section 5. Namespace 'NBN' using the template given above in Section 5.
7. Security Considerations 7. Security Considerations
This document proposes means of encoding NBNs as URNs. A URN This document defines means of encoding NBNs as URNs. A URN
resolution service for NBN-based URNs is depicted, but only at a resolution service for NBN-based URNs is depicted, but only at a
generic level; thus, questions of secure or authenticated resolution generic level; thus, questions of secure or authenticated resolution
mechanisms and authentication of users are out of scope of this mechanisms and authentication of users are out of scope of this
document. It does not deal with means of validating the integrity or document.
authenticating the source or provenance of URN:NBNs. Issues
regarding intellectual property rights associated with objects Although no validation mechanisms are specified on the global level
identified by the URN:NBNs are also beyond the scope of this (beyond a routine check of those characters that require special
document, as are questions about rights to the databases that might encoding when employed in URIs), NBNs assigned by any given authority
be used to construct resolution services. can have a well-specified and rich syntax (including, e.g., fixed
length and checksum). In such cases, it is possible to validate the
correctness of NBNs programmatically.
Issues regarding intellectual property rights associated with objects
identified by the URN:NBNs are beyond the scope of this document, as
are questions about rights to the databases that might be used to
construct resolution services.
Beyond the generic security considerations laid out in the underlying Beyond the generic security considerations laid out in the underlying
documents listed in the Normative References (Section 9.1), no documents listed in the Normative References (Section 10.1), no
specific security threats have been identified for NBN-based URNs. specific security threats have been identified for NBN-based URNs.
8. Acknowledgements 8. Acknowledgements
Revision of RFC 3188 started during the project PersID [PERSID] Later Revision of RFC 3188 started during the project PersID. [PERSID]
the revision was included in the charter of the URNbis working group Later the revision was included in the charter of the URNbis working
and worked on in that group in parallel with what became RFC 8141 and group and worked on in that group in parallel with what became RFC
RFC 8254. The author wishes to thank his colleagues in the PersID 8141 and RFC 8254. The author wishes to thank his colleagues in the
project and the URNbis participants for their support and review PersID project and the URNbis participants for their support and
comments. review comments.
Tommi Jauhiainen has provided feedback on an early version of this Tommi Jauhiainen has provided feedback on an early version of this
draft. The author wishes to thank Tommi Jauhiainen, Bengt Neiss, and draft. The author wishes to thank Tommi Jauhiainen, Bengt Neiss, and
Lars Svensson for the comments they have provided to various versions Lars Svensson for the comments they have provided to various versions
of this draft. of this draft.
John Klensin provided significant editorial and advisory support for John Klensin provided significant editorial and advisory support for
late versions of the draft. later versions of the draft.
9. Contributors 9. Contributors
Alfred Hoenes was the editor and co-author of two of the documents This document would not have been possible without contributions by
from which this one is, in part, derived. This document would not Alfred Hoenes.
have been possible without his contributions.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 17, line 11 skipping to change at page 16, line 26
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
[RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names
(URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017,
<https://www.rfc-editor.org/info/rfc8141>. <https://www.rfc-editor.org/info/rfc8141>.
10.2. Informative References 10.2. Informative References
[I-D.ietf-urnbis-rfc3187bis-isbn-urn]
Huttunen, M., Hakala, J., and A. Hoenes, "Using
International Standard Book Numbers as Uniform Resource
Names", October 2006.
draft-ietf-urnbis-rfc3187bis-isbn-urn-03 (Expired draft).
[IANA-URI] [IANA-URI]
IANA, "URI Schemes Registry", IANA, "URI Schemes Registry",
<http://www.iana.org/assignments/uri-schemes>. <http://www.iana.org/assignments/uri-schemes>.
[IANA-URN] [IANA-URN]
IANA, "URN Namespace Registry", IANA, "URN Namespace Registry",
<http://www.iana.org/assignments/urn-namespaces>. <http://www.iana.org/assignments/urn-namespaces>.
[ISBN-namespace]
Griffiths, S., "Namespace Registration for International
Standard Book Number (ISBN) ISO 2108:2017",
<https://www.iana.org/assignments/urn-formal/isbn>.
[ISO3166-1]
ISO, "Codes for the representation of names of countries
and their subdivisions -- Part 1: Country codes",
ISO 3166-1:2013, 2013,
<https://www.iso.org/standard/63545.html>.
[Iso3166MA] [Iso3166MA]
ISO, "ISO Maintenance agency for ISO 3166 country codes", ISO, "ISO Maintenance agency for ISO 3166 country codes",
2006, <http://www.iso.org/iso/country_codes.htm>. 2006, <http://www.iso.org/iso/country_codes.htm>.
[ISSN-namespace]
Bequet, G., "Namespace Registration for International
Standard Serial Number (ISSN) and Linking ISSN (ISSN-L)
based on ISO 3297:2007",
<https://www.iana.org/assignments/urn-formal/issn>.
[NBN-Resolving] [NBN-Resolving]
Deutsche Nationalbibliothek, "URN:NBN Resolver fuer Deutsche Nationalbibliothek, "URN:NBN Resolver fuer
Deutschland und Schweiz: Information ueber Partner Deutschland und Schweiz: Information ueber Partner
Institutionen", Captured 2018-04-09, Institutionen", Captured 2018-04-09,
<https://nbn-resolving.org/institutions>. <https://nbn-resolving.org/institutions>.
[PERSID] PersID initiative, 2009-2011, "persid: Building a [PERSID] PersID initiative, 2009-2011, "persid: Building a
persistent identifier infrastructure", persistent identifier infrastructure",
Captured 2018-04-09, <http://www.persid.org>. Captured 2018-04-09, <http://www.persid.org>.
skipping to change at page 19, line 8 skipping to change at page 18, line 35
Numerous clarifications based on a decade of experience with RFC Numerous clarifications based on a decade of experience with RFC
3188. 3188.
Non-ISO 3166 (country code) based NBNs have been removed due to lack Non-ISO 3166 (country code) based NBNs have been removed due to lack
of usage. of usage.
In accordance with established practice, the whole NBN prefix is now In accordance with established practice, the whole NBN prefix is now
declared case-insensitive. declared case-insensitive.
Updated URN:NBN Namespace Registration template for IANA; whole The document is based on the new URN Syntax specification, RFC 8141.
document adapted to new URN Syntax document, RFC 2141bis, and new URN
Namespace Registration document, RFC 3406bis (now retired and merged
into 2141bis.
Use of query directives and fragment parts with this Namespace is now Use of query components and fragment components with this Namespace
specified, in accordance with the aforementioned RFCs. is now specified, in accordance with RFC 8141.
Appendix B. Change Log Appendix B. Change Log
[[CREF2: RFC-Editor: Please delete this whole section before RFC [[CREF2: RFC-Editor: Please delete this whole section before RFC
publication.]] publication.]]
B.1. draft-hakala-rfc3188bis-nbn-urn-00 to draft-ietf-urnbis-*-00 B.1. draft-hakala-rfc3188bis-nbn-urn-00 to draft-ietf-urnbis-*-00
o formal updates for a WG draft; no more "Updates: 2288"; o formal updates for a WG draft; no more "Updates: 2288";
skipping to change at page 21, line 29 skipping to change at page 21, line 5
o Conversion of document to XML2RFC format, change of name (not a WG o Conversion of document to XML2RFC format, change of name (not a WG
task). task).
o Adjusted for changes to 2141bis, consolidation of RFC 3406bis, o Adjusted for changes to 2141bis, consolidation of RFC 3406bis,
creation of transition document. creation of transition document.
o Made a number of changes to reflect publication of RFC 8141 o Made a number of changes to reflect publication of RFC 8141
(previously 2141bis and 3406bis) and update terminology, (previously 2141bis and 3406bis) and update terminology,
references, and current status to early 2018. references, and current status to early 2018.
B.7. draft-hakala-urn-nbn-rfc3188bis-00 (2018-06-02) to draft-hakala-
urn-nbn-rfc3188bis-01
o Adjusted on the basis of feedback from IESG.
o Theoretical discussion on the usage of r- and q-components has
been deleted.
o Out-of-date sections of the text have been updated.
Author's Address Author's Address
Juha Hakala Juha Hakala
The National Library of Finland The National Library of Finland
P.O. Box 15, Helsinki University P.O. Box 15, Helsinki University
Helsinki, MA FIN-00014 Helsinki, MA FIN-00014
Finland Finland
Email: juha.hakala@helsinki.fi Email: juha.hakala@helsinki.fi
 End of changes. 94 change blocks. 
438 lines changed or deleted 412 lines changed or added

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