| 16 | | - [https://office.clarin.eu/v/CE-2017-1076-CMDI-Best-Practices.pdf first (draft) version of the CMDI Best Practice guide] as a CE document |
| 17 | | - [https://docs.google.com/document/d/1Cr_UqoQFPLt3ucovUuCxne7XVSMZ4awUupev2bTzewc/edit?usp=sharing draft CMDI Best Practices doc] on Google Docs |
| 18 | | - [attachment:CAC17-CMDI-BP-final.pdf final version of the CAC 17 abstract] |
| 19 | | - [https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20170118#Documents existing (draft) best practices documents] |
| 20 | | - [https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20161025-28 Notes from the Task Forces meeting @ CAC 2016] |
| | 17 | - [https://office.clarin.eu/v/CE-2017-1076-CMDI-Best-Practices.pdf first (draft) version of the CMDI Best Practice guide] as a CE document |
| | 18 | - [https://docs.google.com/document/d/1Cr_UqoQFPLt3ucovUuCxne7XVSMZ4awUupev2bTzewc/edit?usp=sharing draft CMDI Best Practices doc] on Google Docs |
| | 19 | - [attachment:CAC17-CMDI-BP-final.pdf final version of the CAC 17 abstract] |
| | 20 | - [https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20170118#Documents existing (draft) best practices documents] |
| | 21 | - [https://trac.clarin.eu/wiki/Taskforces/CMDI/Meeting20161025-28 Notes from the Task Forces meeting @ CAC 2016] |
| 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 |
| | 44 | * Can be retrieved in XML format. This can be converted into a vocabulary (work by Menzo @ Meertens). |
| | 45 | * (Nearly) ready to be included in CLAVAS in principle, only descriptions and URIs/handles (internal vs ‘natural’) need to be decided on. |
| | 46 | * Add narrower concepts for e.g. TEI (more specific resource types than ‘plain’ media types allows for) by using skos:inScheme and skos:Broader |
| | 47 | * On basis of this a component can be created for all media types |
| | 48 | * `[TODO]` Subcollections need some thought/work, API does not know about such subsets |
| 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 |
| | 50 | * Norway has licences spreadsheet; Menzo has converted this to SKOS. Not all information is represented there (yet). |
| | 51 | * Concept scheme per licence family (e.g. GNU, CLARIN, CC) |
| | 52 | * `[TODO]` Properties (PUB/ACA/RES + BY, NC, SA etc) to be encoded - probably we will have to define our own vocabulary for this |
| | 53 | * Merging/aligning with curation TF’s licence vocabulary |
| | 54 | * `[TODO]` This is the plan but has to be worked out |
| | 55 | * Vocabulary ownership (‘content admin’) |
| | 56 | * Legally: Oddrun talked to Gunn Inger. Ownership is now university. Should be ok to base a SKOS vocab on it. |
| | 57 | * 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 |
| | 58 | * `[TODO]` Discussion with experts (legal issues committee, ..) still pending |
| 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 |
| | 60 | * 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 |
| | 61 | * New vocabulary bootstrapped from information in the VLO |
| | 62 | * Added information |
| | 63 | * Spelling variations, multilingual labels |
| | 64 | * Also typos -> hidden labels |
| | 65 | * Intended applications |
| | 66 | * Organisations component(s) - primarily as an open vocabulary |
| | 67 | * Harmonisation of spelling variations |
| | 68 | * Collaborative curation effort needed |
| 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 |
| | 72 | * 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. |
| | 73 | * `[TODO]` Contact Jan Odijk about this? |
| | 74 | * Workshop to get to such a unified vocabulary? (see other business) |
| | 75 | * A lot of information is already there |
| 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] |
| | 85 | * Discussion -> approval; Then Menzo can import them |
| | 86 | * Menzo, Oddrun: will attempt to get the procedure on track again (Ineke is now involved again) |
| | 87 | * “Coordination of coordinators” is lacking |
| | 88 | * When would coordinators meet? Raise as issue to ERIC. `[TODO]` |
| | 89 | * CCR coordinators can meet during CAC (over lunch?) |
| | 90 | * `[TODO]` [Report here] |
| 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 |
| | 104 | * By Menzo, incorporated in toolkit (dev branch, see https://github.com/clarin-eric/cmdi-toolkit/tree/develop/src/main/resources/toolkit/sch) |
| | 105 | * Can be used to evaluate component files or records, e.g. using oXygen |
| | 106 | * Implementation brings additional insight into best practices, could be reflected in next editing iteration (e.g. overlapping BPs) |
| | 107 | * `[TODO]` To be integrated into curation module |
| 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 |
| | 112 | * Start with (for example) resource types - vocabulary + mapping definitions |
| | 113 | * Small group of people (4-5) willing to work on this |
| | 114 | * Scopes: content and workflow (separate + combined sessions) |
| | 115 | * `[TODO]` be organised/hosted by Vienna |
| | 116 | * Within the next quarter/half year |
| | 117 | |
| | 118 | == TODOs == |
| | 119 | * Complete OpenSKOS release (requires merge with OpenSKOS 2.1 code) |
| | 120 | * Subcollections in CLAVAS need some thought/work, API does not know about such subsets |
| | 121 | * Properties (PUB/ACA/RES + BY, NC, SA etc) to be encoded in licences vocabulary - probably we will have to define our own vocabulary for this |
| | 122 | * Merging/aligning of licences vocabulary with curation TF’s licence vocabulary has to be worked out. |
| | 123 | * Discuss licences vocabulary responsibilites ('ownership') with experts (legal issues committee, ..) still pending |
| | 124 | * Organise workshop/hackathon to focus on creating a resource type vocabulary |
| | 125 | * Push for meeting of CCR coordinators |
| | 126 | * Report on meeting of coordinators |
| | 127 | * Ask centre committee representative to mention this in plenary “Short reports on Committee meetings, by the respective chairs” slot |
| | 128 | * Integrate best practices schematron into curation module |
