Names, Things, and Open Identifier Infrastructure: N2T and ARKs
Click here to load reader
-
Upload
john-kunze -
Category
Technology
-
view
561 -
download
1
Transcript of Names, Things, and Open Identifier Infrastructure: N2T and ARKs
![Page 1: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/1.jpg)
Names, Things, and Open Identifier Infrastructure: N2T and ARKs
J o h n K u n z e
C a l i f o r n i a D i g i t a l L i b r a r y
![Page 2: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/2.jpg)
2
Open identifier infrastructure?
• URL infrastructure is mostly open
• But “persistent identifier” infrastructure is mostly closed
![Page 3: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/3.jpg)
3
Non-traditional id persistence
Traditional silos: doi.org, handle.net, purl.org, urn.arpa
2001: ARK (Archival Resource Key) scheme published
• Decentralized resolution shouldn't hurt, ie,
http://soviet.org/ark:/12345/9876
should be the same as
http://russia.org/ark:/12345/9876
• Embryonic and dynamic content
• Provider intention should be queryable
![Page 4: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/4.jpg)
4
Persistence nonsense
URLs aren't long-term, instead use ... (which are URLs)
URLs are locations, instead use ... (which are URLs)
URL hostnames break, instead use ... (which are URLs)
It’s all about hosts – which of these do we trust?
• doi.org, purl.org, handle.net, n2t.net
• bnf.fr, bl.uk, loc.gov, nla.gov.au, nlm.nih.gov
![Page 5: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/5.jpg)
5
ARKs breaking with tradition
• Syntax does not confer persistence
• ARK registry grows monthly, now 360+ insititutions
• ARKs appear along with DOIs in Thomson Reuters Data Citation Index
• ARK as a collection of ideas for ids
![Page 6: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/6.jpg)
6
ARKs breaking with tradition
• Simple relationships shouldn't hurt
• A/B means A logically contains B
• A.B and A.C means A has two variant forms
• Machine-readable metadata shouldn't hurt
• Méthode ancienne – label: value
• "id?" requests metadata
• "id??" requests more metadata
• no conflict with “content negotiation”
• “Inflections” reduce need to create more ids
![Page 7: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/7.jpg)
7
Breaking with centralized resolver tradition
2007: N2T (Name-to-Thing) resolver introduced
• Centralized resolution for ARKs, but also for any other identifier type
• Proposed consortium (on hold since 2008)
• Plus suffix pass-through (hierarchy shouldn't hurt)
![Page 8: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/8.jpg)
8
N2T under the hood
• Built using open source components
• Replica running in Edinburgh
• Primary running in California
• Supports ARKs, DOIs, URNs
• Ids from EZID, Internet Archive, and YAMZ.net
• Experimental load of 60 million CrossRef DOIs
![Page 9: Names, Things, and Open Identifier Infrastructure: N2T and ARKs](https://reader038.fdocuments.in/reader038/viewer/2022100807/58a54e561a28abef2c8b4bd9/html5/thumbnails/9.jpg)
9
Summary – ARK and N2T
• Inflections (metadata shouldn't hurt)
• Structure with / and . (relations shouldn't hurt)
• Hostnames inert (decentralization shouldn't hurt)
• Id-agnostic resolution (centralization shouldn't hurt)
• Suffix pass-through (hierarchy shouldn’t hurt)
• Let’s build to the “Principles for open scholarly infrastructures” (Bilder, Lin, & Neylon)