| | 35 | |
| | 36 | === CLAVAS === |
| | 37 | * Production instance @ Meertens on the way. Depends on release of OpenSKOS 2.1 (framework for vocabularies), code of which needs to be merged. [TODO] |
| | 38 | * -> vocabularies.clarin.eu (not yet the final version) |
| | 39 | * ISO639-3 vocabulary is in there, but an old version - aligned with component registry |
| | 40 | ==== Vocabularies in preparation ==== |
| | 41 | |
| | 42 | ===== IANA media types (mime types) vocabulary ===== |
| | 43 | * Can be retrieved in XML format. This can be converted into a vocabulary (work by Menzo @ Meertens). |
| | 44 | * (Nearly) ready to be included in CLAVAS in principle, only descriptions and URIs/handles (internal vs ‘natural’) need to be decided on. |
| | 45 | * Add narrower concepts for e.g. TEI (more specific resource types than ‘plain’ media types allows for) by using skos:inScheme and skos:Broader |
| | 46 | * On basis of this a component can be created for all media types |
| | 47 | * [TODO] Subcollections need some thought/work, API does not know about such subsets |
| | 48 | ===== Licences ===== |
| | 49 | * Norway has licences spreadsheet; Menzo has converted this to SKOS. Not all information is represented there (yet). |
| | 50 | * Concept scheme per licence family (e.g. GNU, CLARIN, CC) |
| | 51 | * [TODO] Properties (PUB/ACA/RES + BY, NC, SA etc) to be encoded - probably we will have to define our own vocabulary for this |
| | 52 | * Merging/aligning with curation TF’s licence vocabulary |
| | 53 | * [TODO] This is the plan but has to be worked out |
| | 54 | * Vocabulary ownership (‘content admin’) |
| | 55 | * Legally: Oddrun talked to Gunn Inger. Ownership is now university. Should be ok to base a SKOS vocab on it. |
| | 56 | * A person or group of persons has to be responsible for the content. Obvious candidates would be curation task force and/or legal issues committee |
| | 57 | * [TODO] Discussion with experts (legal issues committee, ..) still pending |
| | 58 | ===== Organisations ===== |
| | 59 | * Menzo started creating a vocabulary based on ‘old’ organisations vocabulary from first version of CLAVAS that got out of sync and was lacking in (linked) information |
| | 60 | * New vocabulary bootstrapped from information in the VLO |
| | 61 | * Added information |
| | 62 | * Spelling variations, multilingual labels |
| | 63 | * Also typos -> hidden labels |
| | 64 | * Intended applications |
| | 65 | * Organisations component(s) - primarily as an open vocabulary |
| | 66 | * Harmonisation of spelling variations |
| | 67 | * Collaborative curation effort needed |
| | 68 | Ideally directly in XML, sharing the file on GitHub |
| | 69 | * Look up/sync with authority file (e.g. viaf.org), use URI found there |
| | 70 | ===== Resource types(?) ===== |
| | 71 | * Curation efforts: Coverage of resource type in VLO is bad. Could be improved by deriving from resource type -> cross facet mapping, will be integrated in VLO. |
| | 72 | * [TODO] Contact Jan Odijk about this? |
| | 73 | * Workshop to get to such a unified vocabulary? (see other business) |
| | 74 | * A lot of information is already there |
| | 75 | |
| | 76 | === CCR === |
| | 77 | * Importance stressed in best practices |
| | 78 | * Not much has happened recently, some contact among coordinators |
| | 79 | * New pending sets of proposals: |
| | 80 | * IDS submitted proposals for 2 concepts |
| | 81 | * Jan Odijk is proposing concepts based on CLARIN-NL… |
| | 82 | * Concepts mapping directly to VLO facets |
| | 83 | * (Required) action by coordinators |
| | 84 | * Discussion -> approval; Then Menzo can import them |
| | 85 | * Menzo, Oddrun: will attempt to get the procedure on track again (Ineke is now involved again) |
| | 86 | * “Coordination of coordinators” is lacking |
| | 87 | * When would coordinators meet? Raise as issue to ERIC. [TODO] |
| | 88 | * CCR coordinators can meet during CAC (over lunch?) |
| | 89 | * [TODO] [Report here] |
| | 90 | |
| | 91 | === Helpdesk === |
| | 92 | |
| | 93 | * Nothing happened: no support requests in the past 100 days. |
| | 94 | * Request before were handled well |
| | 95 | |
| | 96 | === Best practices === |
| | 97 | |
| | 98 | * Draft at https://www.clarin.eu/content/cmdi-best-practice-guide |
| | 99 | * Will be presented at Bazaar and paper session |
| | 100 | * [TODO] Can ask centre committee representative to mention this in plenary “Short reports on Committee meetings, by the respective chairs” slot |
| | 101 | * Task force members are requested to be present to talk CMDI (BP) :) |
| | 102 | * Schematron implementation of some best practices |
| | 103 | * By Menzo, incorporated in toolkit (dev branch, see https://github.com/clarin-eric/cmdi-toolkit/tree/develop/src/main/resources/toolkit/sch) |
| | 104 | * Can be used to evaluate component files or records, e.g. using oXygen |
| | 105 | * Implementation brings additional insight into best practices, could be reflected in next editing iteration (e.g. overlapping BPs) |
| | 106 | * [TODO] To be integrated into curation module |
| | 107 | |
| | 108 | === Other business === |
| | 109 | |
| | 110 | * Workshop(s)/hackathon towards proposal for curation workflow and practices (see CLAVAS) |
| | 111 | * Start with (for example) resource types - vocabulary + mapping definitions |
| | 112 | * Small group of people (4-5) willing to work on this |
| | 113 | * Scopes: content and workflow (separate + combined sessions) |
| | 114 | * [TODO] be organised/hosted by Vienna |
| | 115 | * Within the next quarter/half year |
