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

Compare with Current View Page History

« Previous Version 4 Next »

Date

Attendees

Goals

Follow up on test resolution, review charter and deliverables for coming year

Discussion items

ItemWhoNotes
Announcements

Calls for papers, submission deadlines, upcoming meetings: Calendar of events


Any news items we should blog about?

Bug fix at N2T, possible enhancement to "quick" test ARK resolution, per the documentation at ARK Shoulders FAQ below. It appears that N2T may not be following the documentation. See email thread ending Jan 4.

Is there a quick way to get started creating test ARKs?

Yes. Instead of reserving a 99999 shoulder, if your organization already has its own NAAN, you can immediately create and use a "quick test ARK". This is an ARK that starts with ark:/99999/9NNNNN_, where NNNNN represents the NAAN (preceded by '9' and followed by '_'). There is no need to register a quick test namespace since it is automatically set aside for each NAAN. As with any prefix, there is an infinite number of possible test ARKs in each NAAN's quick test namespace. Two versions of an example quick test ARK belonging to the BnF (NAAN 12148) are

https://ark.bnf.fr/ark:/99999/912148_testxyz

   https://n2t.net/ark:/99999/912148_testxyz

Note that N2T.net is configured to forward any quick test ARK it receives (second version above) to the appropriate local resolver (first version).

That last sentence isn't quite true, as N2T actually forwards the second to:

   https://n2t.net/ark:/12148/99999/912148_testxyz

which redirects to

   http://ark.bnf.fr/ark:/12148/99999/912148_testxyz 

That should then allow the local resolver (in this case bnf.fr) to handle the test ARK, as per the current documentation.

OTOH, a future enhancement of N2T might conceivably improve this, so that the first redirect went directly to

   http://ark.bnf.fr/ark:/99999/912148_testxyz

That way, the local resolver sees the NAAN of 99999 and can treat it as a test NAAN (consistent with how all resolvers should treat a NAAN of 99999). At the moment, a kludge is required to treat the ARK as some special case "object"-as-test-NAAN, where the object is called "99999" within the 12148 NAAN namespace. Not a great design (mea culpa), even if it works for now with a local resolver that can add this code in order to publish "functional" test ARKs.


 working group home page and sidebar cleanup
  • compress sidebar list of 3 years of meetings 
  • revisit objectives, deliverables via this googledoc


Action items

  •  
  • No labels