...
The only prerequisite is to fill out an online request for a NAAN on behalf of your organization. There is no charge to obtain a NAAN and all memory organizations are welcome. Within a day or two you should receive an email containing a NAAN for your organization's exclusive use. Meanwhile consider the following.
...
To convert ordinary web server processes into ARK-aware processes, all you difference between providing access to ARK-identified objects vs URL-identified is like with providing access for ordinary URL-identified objects. For example, you could run all your own custom infrastructure – including content management, web hosting, minting (generating unique identifier strings), and running your own server/resolver. That infrastructure could be very simple, such as server configured to convert incoming ARK-based URLs to server file pathnames. When you request your NAAN you will be asked to supply the base URL of your local server or resolver.
At the other end of the spectrum, you could work with a vendor that supplies all the infrastructure so that, for example, you could focus on creating content. Hybrid solutions are also common, such as just taking your current web server arrangement and just adding an identifier management piece (eg, the API/UI provided by ezid.cdlib.org, which partners with n2t.net).
If you run a resolver, you will also want to think about whether to advertise (publish) your ARKs based at your resolver or at n2t.net. Resolving through n2t.net is always possible as a cost-free side-effect of obtaining a NAAN.
...
Unlike Crossref and DataCite DOIs, which require specific metadata (eg, see the DataCite schema), ARKs do not constrain any of these activities. Moreover the N2T.net resolver actually supports all of them.
If ARKs don't require it, why
...
bother
...
creating metadata?
Creating metadata (extra information associated with or describing an object) has several key benefits. First, no matter what the ARK redirects to , whether to – whether a landing page or a file, metadata can give people more file – metadata gives users vital information about the object, such as details about its origins, references to newer versions, provenance, etc. Typically for For ARKs typically metadata is accessed via DRAFT ARK Identifiers FAQ.
Metadata is also critical to your users making selection decisions when direct object access is expensive or inconvenient. They want to read an abstract before buying, or limiting search results to a particular author.also eases some persistence pain. By themselves, persistent identifier strings are often opaque, revealing little about what they identify (generally because non-opaque identifiers do not age or travel well). On the other hand, opaque But opaque identifiers are difficult because both creators and receivers have no idea they give you no clues as to what the identifier was identifiers were meant to identify, so in the absence of metadata everyone is you are forced to trust access the accessed object itself . In this way, metadata also shores up identifier persistence (what object the ARK string is associated with). Any discrepancy between the to remind yourself what it is, and to trust that it's the correct object. Metadata to the rescue. Moreover, discrepancies between returned metadata and the accessed object helps to help detect identifier changes in that associationand errors.
The primary assertion of the binding is the experience of resolving the identifier to the object. A secondary, confirming assertion of the binding is the experience of resolving to its metadata.
Metadata is for grownups. It is far less important for immature objects and their identifiers than for those that have been released. Access Third, providing access to metadata demonstrates basic provider credibility and commitment . This adds credibility to the seriousness of its intentions since not every object provider can return object metadata. Finally, adding basic metadata, especially for objects that don't have textual representations, makes your objects more findable. to high-functioning identifiers. Not every provider is up to this task.
Metadata for identifiers need not be expensive. Building it from scratch is expensive, but metadata is usually created and managed by object providers, in which case it can be leveraged efficiently for identifiers. Ideally, master metadata (maintained by object providers) will be reflected in independent copies so that it is harder to tamper undetectably with identifier associations meant to be truly persistent.
What metadata is recommended for ARKs? xxx
...