Summary

  • RFC 3188 put National Bibliography Numbers into URNs, but NBN was a family of locally governed identifier systems rather than one standard global syntax and assignment regime.
  • A country or delegated prefix made local strings globally unique and helped select a resolver. It did not prove deposit, preservation, resolver authenticity, original bytes, public access or rights.

Published in October 2001 as Informational, Using National Bibliography Numbers as Uniform Resource Names registered NBN under the URN framework of RFC 2141 and RFC 2611. The document did not specify an Internet standard. It described how national libraries could turn identifiers already rooted in their cataloguing and deposit work into globally usable names.

The object called NBN was deliberately plural. Each national library used its own strings, syntax, scope and assignment policy independently. There was no global authority deciding what every local NBN meant. The same base string could name different resources in two countries without either library making a mistake.

Global uniqueness came from composition. A controlled prefix, normally an ISO 3166 two-letter country code, was placed before the local string. Colon-separated subnamespaces could divide a national branch among multiple national libraries or trusted organizations. A hyphen separated that prefix from the assigned NBN. The structure made two local ledgers coexist; it did not merge their rules.

NBNs historically filled gaps. They identified deposited or catalogued material lacking an ISBN or other publisher-assigned identifier, including grey literature. By 2001, Finland, Norway and Sweden were also using them for electronic resources and Web archives. The name could therefore attach to a catalogue record, a physical publication, a harvested page or a machine-captured bitstream.

This made NBN different from the ISBN edition model. A Web archive could not safely trust an identifier embedded in a document, because the string might belong to another object. Several archived variants of a book might properly share an ISBN. The Finnish harvesting example instead derived a local identifier from an MD5 checksum of the captured resource.

That mechanism narrowed identity to bits. In the automatic path, bit-identical documents were treated as identical and received the same NBN. A changed bitstream produced another value. The historical collision estimate in RFC 3188 described the assumptions of 2001; it is not a current security recommendation for MD5.

A checksum-shaped name still did not preserve anything. The harvester had to capture the resource, the archive had to retain it, and a resolver had to keep a route to it. Validation of a string, assignment of a name, custody of bytes and successful delivery remained different events.

Human assignment created a different object model. National guidelines decided when versions should share or receive different numbers. Authors and publishers could fetch NBNs from a generator for network documents. If no deposit or cataloguing duty accompanied that act, the resource might never enter the national bibliography.

In that case resolution depended on a national Web index or archive. A valid name could exist before any durable copy was secured. The number recorded an allocation; it did not supply missing custody.

Physical holdings exposed another boundary. If the named material existed only on paper or another physical medium, the best resolver response could be bibliographic metadata and a holding location. That was useful discovery, not electronic delivery.

Even deposited digital material might not be downloadable. RFC 3188 noted that legal-deposit restrictions could prevent delivery outside the national library premises. Preservation, discoverability and reader access were three separate claims.

The prefix helped locate the appropriate service. A country branch could lead first to a national bibliography and second to a Web archive; delegated organizations could operate their own resolvers. Syntax described where authority had been allocated, not whether the service was online, current or honest.

RFC 3188 expressed persistence in institutional terms. NBN persistence was said to be guaranteed by the persistence of national libraries and their information systems. The statement exposed the real dependency: durable symbols relied on organizations continuing to fund catalogues, archives, resolver mappings and migrations.

In 2018, RFC 8458 obsoleted RFC 3188. It aligned the registration with RFC 8141, removed undeployed non-country prefixes, described hundreds of partner relationships and clarified the separation among object, identifier and resolver persistence. The new document also recognized Web archives, research data, doctoral dissertations, digitized components and linked-data names.

RFC 8458 made migration visible. Digital objects may need new formats while archives retain original and intermediate manifestations. A resolver may return a newer surrogate if the exact version has disappeared. That can preserve usability, but a surrogate is not the original bitstream. The response needs provenance and an explicit relationship.

The prefix was never a certificate of sovereignty over the work. It reserved a namespace branch and located a coordination path. Universities, governmental bodies and research institutions could receive subnamespaces; they still needed assignment records and resolution services. National coordination did not become ownership of every named object.

Security and rights stayed outside the number. RFC 3188 did not define secure or authenticated resolution, validate the source or provenance of the URN, or decide intellectual-property rights in the resource or resolver database. RFC 8458 retained those boundaries.

A defensible NBN record therefore preserves the country and subnamespace delegation, assigning organization, local policy version, assignment event, object or manifestation claim, checksum method where used, catalogue record, deposit and custody state, resolver endpoint and timestamp, response type, retrieved bytes, migration or surrogate relation, authentication context and access restriction. The name becomes useful evidence only when its institutional chain remains visible.