The Handle System: Ensuring Persistent Access to Digital Resources
In the rapidly evolving digital landscape, the stability of information is a constant challenge. As websites change and files are moved, the links we rely on often break—a phenomenon known as "link rot." To combat this, the Handle System was developed as a robust solution for creating persistent identifiers that ensure digital resources remain accessible, regardless of changes to their physical location.
Understanding the Handle System
The Handle System is a proprietary registry that assigns persistent identifiers, known as handles, to information resources. These handles are used to resolve "those handles into the information necessary to locate, access, and otherwise make use of the resources." Unlike many other digital identifiers, handles are opaque. This means the identifier itself encodes no information about the underlying resource; instead, it is strictly bound to metadata (data that describes the resource).
ไม่มีภาพประกอบBecause the handle is opaque, it remains valid even if the resource's metadata changes. For example, if a document is moved from one server to another, the handle does not need to change. Only the metadata pointing to the new location needs to be updated, preventing the broken links that plague traditional web structures.
The Anatomy of a Handle
A handle is composed of two distinct parts: a prefix and a suffix. The prefix identifies a "naming authority," while the suffix provides the "local name" of the specific resource. This structure is similar to the domain name system (DNS) used on the internet.
Prefixes and Naming Authorities
Prefixes are issued to naming authorities by one of the system's "multi-primary administrators" (MPAs) upon payment of an annual fee. A single naming authority can create any number of handles within its assigned prefix. Prefixes can also represent a hierarchy; for instance, a prefix might consist of multiple segments separated by periods, representing subordinate authorities.
Example Breakdown
To understand how this works in practice, consider the handle 20.1000/100:
- 20.1000 is the prefix assigned to the naming authority (in this case, Handle.net). Within this, "20" represents the CNRI, and "1000" represents a subordinate authority.
- 100 is the local name within that specific namespace.
The local name can include any characters from the Unicode UCS-2 character set, providing significant flexibility for creators.
Handle vs. URL: Why Persistence Matters
It is helpful to contrast the Handle System with a Uniform Resource Locator (URL). A URL is designed to tell a computer exactly how to find a resource, often encoding the protocol (like HTTP), the server hostname, and the specific file path. While efficient, this makes URLs fragile; if the file is moved or the server is renamed, the URL becomes invalid.
| Feature | Uniform Resource Locator (URL) | Handle System Identifier |
|---|---|---|
| Information Encoded | Protocol, host, port, and file path. | None (Opaque identifier). |
| Stability | High risk of "link rot" if location changes. | Persistent; remains valid if metadata changes. |
| Primary Function | Directly locates a resource on a network. | Resolves to metadata to facilitate access. |
Global Infrastructure and Administration
The Handle System was originally developed by Bob Kahn at the Corporation for National Research Initiatives (CNRI) as part of the Digital Object Architecture (DOA). The project was funded by the Defense Advanced Research Projects Agency (DARPA) between 1992 and 1996. Since its first implementation in autumn 1994, the system has grown into a massive, distributed network.
Today, the system is administered by the DONA Foundation, which manages the Global Handle Registry (GHR) and accredits Multi-Primary Administrators (MPAs). These administrators include CNRI and the International DOI Foundation. The infrastructure consists of:
- Local Handle Services: Sites that store specific handles.
- Global Handle Registry (GHR): A unique service that stores information on prefixes and directs queries to the correct Local Handle Service.
- Global Resolver: A decentralized, mirrored entity that facilitates the resolution of handles across the network.
This distributed model allows the system to be highly scalable and reliable. Currently, thousands of handle services are in operation across 71 countries, receiving over 200 million resolution requests per month.
Key Facts
- Core Purpose: Provides persistent identifiers to prevent link rot and ensure long-term access to digital resources.
- Key Applications: Serves as the underlying infrastructure for Digital Object Identifiers (DOI) and DSpace.
- Scale: Over 1,000 services are operated by universities, libraries, government agencies, and commercial enterprises.
- Structure: Uses an opaque prefix/suffix system to decouple the identifier from the resource's location.
- Licensing: Available under a royalty-free public license, similar to open-source software.
Frequently Asked Questions
What makes a handle "opaque"?
An opaque identifier is one that does not contain any descriptive information about the resource it represents. Because the handle is just a "dumb number" or string, it doesn't matter if the resource's name, owner, or location changes; the handle remains the same.
How does the resolution process work?
When a user requests a handle, the query is sent to the Global Handle Registry. The GHR identifies which Local Handle Service manages that prefix and directs the query there. The Local Handle Service then returns the metadata (such as a URL), which the user's system uses to access the actual resource.
Can a single resource have multiple handles?
Yes. It is possible for the same underlying information resource to be associated with multiple handles. For example, two different university libraries might generate different handles (and different sets of metadata) for the same book.
Is the Handle System the same as a DOI?
Not exactly, but they are closely related. The Digital Object Identifier (DOI) is a specific namespace that uses the Handle System as its underlying infrastructure. While all DOIs are handles, not all handles are DOIs.
What is the difference between a handle and a PURL or ARK?
While Persistent URLs (PURLs) and Archival Resource Keys (ARKs) are similar in goal, they rely on the Domain Name System (DNS). The Handle System is compatible with DNS but does not require it, utilizing its own separate prefix registration and handle server architecture instead.