Archival Resource Keys (ARKs) serve as persistent identifiers, or stable, trusted references for information objects. Among other things, they aim to be web addresses (URLs) that don’t return 404 Page Not Found errors. The ARK Alliance is an open global community supporting the ARK infrastructure on behalf of research and scholarship. End users, especially researchers, rely on ARKs for long term access to the global scientific and cultural record. Since 2001 some 8.2 billion ARKs have been created by over 1000 organizations — libraries, data centers, archives, museums, publishers, government agencies, and vendors. They identify anything digital, physical, or abstract. ARKs are open, mainstream, non-paywalled, decentralized persistent identifiers that can be created by an organization as soon as it is registered with a NAAN (Name Assigning Authority Number). Once registered, an ARK organization can create unlimited numbers of ARKs and publicize them via the n2t.net global resolver or via their own local resolver.
Local identifiers in Archival Resource Key should match this
Compact URIs (CURIEs) constructed from Archival Resource Key should match
this regular expression:
namespaceEmbeddedInLUIas true. The actual part that gets prefixed before the local unique identifier regex, otherwise known as the banana, is
ark:. Therefore, you might see local unique identifiers written out as CURIEs.
The metaregistry provides mappings between the Bioregistry and other registries. There are
4 mappings to external registries for
2 unique external prefixes.
|Registry Name||Registry Metaprefix||External Prefix||Curate|
Providers are various services that resolve CURIEs to URLs. The example CURIE
is used to demonstrate the provides available for
ark. Generation of OLS and BioPortal URLs requires additional programmatic
logic beyond string formatting.
|Archival Resource Key||