You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

ARK specification 

Estimate JAK .02 FTE for one year

This document has been stable since 2008, with pending changes greatly informed by Notes from ARK "Experts" meetings, March 22 and June 11, 2018. The need is for a few volunteers to guide it through the Internet RFC process, a Technical WG task. 

ARK Resolver Anatomy

NAAN registry hosting and maintenance

Estimate JAK .02 FTE for one year, on-going volunteer .01 FTE per year

The registry is a text file in a human- and machine-readable format. Probably could use github for free hosting, and possibly change requests. The need is for transition away from CDL hosting and as volunteers to add and correct entries. New entries are received via a google form.


ARK resolver

Estimate, per year: $25,000 in AWS fees, developer .05 FTE for maintenance, dev .23 FTE for enhancements

The ARK resolver is N2T.net. One wrinkle is that also does compact identifiers (a bit more than ARKs estimate dev .02 FTE for maintenance), but that could be done by CDL.

Beyond the Basics

ARK brochure site

Estimate, per year: $40 hosting? with on-going volunteers to maintain?

Unlike every other identifier scheme, ARKs have never had a brochure site, which would be an expected recommendation from the Outreach WG. ARK resolver is N2T.net. One wrinkle is that also does compact identifiers (a bit more than ARKs estimate dev .02 FTE for maintenance), but that could be done by CDL.

ARK resolver, next generation

Estimate, per year: $25,000 in AWS fees ongoing; one-time developer costs -- 1.5 FTE (or 1 FTE for 18 months)

The resolver code could use a major rewrite, for maintainability and efficiency.

Resolver front end, "identifier management made easy" (EZID)

Estimate, per year: $25,000 in AWS fees; developer .10 FTE

The idea is that the existing EZID front end might be a source of revenue for AITO. EZID provides lots of UI and API services, as well as link checking, search, download, and OAI-PMH for harvesting. A variety of income methods could be added (eg, micropayments) if this were run outside of CDL.

  1. a community-supported front-end service (eg, EZID) is added to support a variety of income methods (subscriptions, micro-payments)

ARK resolver
EZID UI/API could be of value, charging fees, etc.
(potential revenue generator)

NAAN reg: volunteers to add/change entries [time+hosting]


EZID: (potential revenue generator) (same, if community adapted and ran)
-Greg, Joan, Andy, Kurt, Rondy
Note: a future ARK web presence, brochure site could have cost


  • No labels