...
there's the protocol (https://) plus hostname, followed by the Name Assigning Authority (99999 or 10.99999), which is the organization that created the identifiers. Finally there's the name, or local identifier, that it assigned (12345).
By no means an exhaustive list, here Here are some ways in which ARKs, DOIs, Handles, PURLs, and URNs differ. This is by no means an exhaustive list.
- When (not if, since all things pass) the https:// protocol and the hostname cease to exist, only ARKs and URNs will still indicate the kind of identifier that remains.
- To create DOIs, Handles, and PURLs, you are required to use their respective resolvers. There are no such silos with ARKs and URNs; , for them which you can use your own resolver.
- To create DOIs and Handles, you are also required to pay a membership fee and per-DOI charges. There are no fees such paywalls for ARKs, PURLs, and URNs.
- It is hard to generalize how people use these identifiers. DOIs, for example, used to be known primarily as identifiers for scientific and scholarly publications, with a mature community and service offering around "Crossref DOIs", but since 2013 enough new assigners have joined that it is hard to make generalizations about DOIs.
- Although you can use your own or a vendor resolver for your ARKs, all ARKs can be resolved via n2t.net. Thus n2t.net is the closest thing to a "global ARK resolver".
- There is no single global resolver for URNs.
- Strong principles of openness prevented n2t.net, which was built for ARKs, from becoming just another DOI/Handle/PURL-type silo. As a result, the "global ARK resolver" also resolves DOIs, Handles, PURLs, and URNs, along with 600 other kinds of identifier. This anti-silo approach principle is exemplified by ARK micro-service tools such as "noid", also built for ARKs, that are routinely used by organizations to mint Handles.
...
https://n2t.net/ark:/65665/3c2e39526-e0c3-41ae-be4f-07558a9458eb
...