Download to read offline
Uploaded byJohn Kunze
A Vocabulary for Persistence
The document discusses the development of a metadata vocabulary for persistence statements, emphasizing the need for a nuanced understanding of persistence in various contexts. It introduces a crowdsourced metadata dictionary, yamz.net, that utilizes reputation-based voting to define terms, aiming to improve the clarity of user expectations about data and content persistence. The authors call for contributions to this initiative and highlight use cases such as reproducible science and data papers.
A Vocabulary for Persistence
- 1.
- 2. 2 Two themes 1. Proposed metadata for “persistence statements” • What you mean by persistence • Informing user linking choices 2. Metadata hardened in open yamz.net dicNonary • Crowdsourced, but with reputaNon-based voNng • Every term has a unique persistent idenNfier (PID) 2
- 3. • Open idenNfiers deserve their own fesNval • 9 and 10 November in Reykjavik, Iceland! • If you’re doing something interesNng with PIDs (or you want to!) come and share your ideas with a crowd of like- minded innovators
- 4. 4 “Persistence” used, but not defined • Persistence is not binary • Persistence is usually a forecast about stubbornness or sNckiness • Persistence is nuanced and dimensional 4
- 5.
- 6. 6 Use cases and goals • Classic case: reproducible science • Overlooked cases: data papers, sohware releases • Goal: propose persistence metadata • Goal: whatever link you find, be able to query the provider for its “persistence statement” 6
- 7. 7 Sejng user expectaNons Terms for content variance • frozen – unchanging bitstream • keeping – unchanging content • fixing – subject to correcNon • rising – subject to acNve enhancement • moul7ng – unchanging theme 7
- 8. 8 Sejng user expectaNons Terms for object availability • finite – ends at known date or event • indefinite – no special commitment • life7me – as long as the provider exists • subinfinite – beyond provider’s lifeNme 8
- 9.
- 10. 10 Why should we believe you? Terms specifying the nature of the provider • name – of organizaNon • iden7fier – unique organizaNonal idenNfier • mission – is preservaNon in your mission? • succession policy 10
- 11.
- 12.
- 13. 13 Naming and remediaNon policy If there’s a problem, what repair priority? • high – high priority • standard – not high priority Forming idenNfier strings • NR – non-reassignment • OP – opaque idenNfiers • CC – check character added 13
- 14. 14 Concept ids (naming and remediaNon) If there’s a problem, what repair priority? • high – n2t.net/ark:/99152/h1207 • standard – n2t.net/ark:/99152/h1208 Forming idenNfier strings • NR – n2t.net/ark:/99152/h1215 • OP – n2t.net/ark:/99152/h1218 • CC – n2t.net/ark:/99152/h1219 14
- 15.
- 16. 16 Problem: tradiNonal standardizaNon • Change by commi<ee is ugly, costly, and slow • Example: Dublin Core, 15 cross-domain terms • same terms aher 5 years as aher 11 months • new terms banned in fear of fragile consensus 16 European Parliament Technology - DG ITEC @ flickr
- 17.
- 18.
- 19.
- 20.
- 21.
- 22. 22 An alternate metadata universe • Vision: one dicNonary, one namespace • All research domains, any part of “metadata speech” • Names, values, units, relaNonships, ... 22 SimonRobertson@flickr
- 23.
- 24.
- 25. 25 YAMZ usage pa<erns 25 Search for terms (words and definiNons) find a term you love great – use it find a term you kind of love try it out, comment, engage with author no workable term found instantly enter own term and watch for comments find a word you love “I want that word!”, so enter a compeNng term but a defini7on you hate
- 26.
- 27. 27 In conclusion • Choosing which objects to cite is hard • Few well-defined terms to express persistence • … or to set user expectaNons of change • Thanks to yamz.net for be<er, cheaper, faster vocabulary-building; projects include • CiNzen Science; DesignSafe; Persistence statements 27