El 17/11/20 a las 16:01, Bridget Almas escribió:> Does this mean that if
I can include a URL mapping rule when I request
> an entry in the NAAN registry N2T.net will be able to resolve it? And if
> so, what are the specs for the URL mapping rules? Or do I really need to
> go through (and pay for) the EZID service to get global resolution of
> the ARKs?
By default
n2t.net has no knowledge about individual ARKs. It redirects
all ARKs with your NAAN to your resolver. You state the prefix for your
resolver at the time of registration.
E.g.: If you are given NAAN 99999 and your resolver prefix is
<
https://example.org>, then <
https://n2t.net/ark:99999/x9fuvt> will
redirect to <
https://example.org/ark:99999/x9fuvt>.
n2t.net has no
knowledge of whether <ark:99999/x9fuvt> is assigned nor what it is
assigned to. In the next step your own resolver is supposed to redirect
to the final destination, a landing page with metadata about that ARK,
or display an “ARK not found” message.
n2t.net also offers a service where they keep track of your individual
ARKs. Then you do not need a resolver of your own and the prefix in the
NAAN registry for organization NAAN is listed as
https://n2t.net . I do
not run nor profit from this service.