...
Typically, scheme-based services are designed as silos ("walled gardens") to serve , or closed platforms, serving a particular identifier type (eg, such as Handle, DOI, or PURL). Each silo performs the same main functions – mapping names (identifiers strings) to things (objects or metadata). Excluding all but one type of identifier string may help to capture markets, but it's wasteful and non-inclusive. It requires building the same set of services over and over for each type and violates basic principles of openness, so the N2T (Name-to-Thing) resolver and EZID (identifiers made easy) management interface were designed to work with all identifiers. Work put into any new feature can be efficiently leveraged across all types, which sometimes creates surprising flexibility; for example, ARKs are often stored in EZID with "DOI metadata", and every DOI stored in N2T can benefit from "ARK resolution features" such as inflections and suffix passthrough, which are not available via the main DOI resolver (doi.org).
...