| | 52 | |
| | 53 | === Definition of tasks === |
| | 54 | Agreement on overall objective. Some rephrasing of specific task descriptions: |
| | 55 | |
| | 56 | __Core metadata and extensions__: Define a set of general purpose components, together forming a basis for (more or less) use case specific profiles. The components must implement CMDI best practices, enable adherence to FAIR principles, and facilitate interoperability with the broader research infrastructure for research resources and technologies. |
| | 57 | |
| | 58 | Aim is not to define a 'most generic/minimal metadata' profile but rather keep the approach modular and create components to be combined into more use case specific profiles. |
| | 59 | |
| | 60 | __FAIR vocabularies__: Evaluate which broadly supported/used vocabularies can be used '''[..in two ways - at two levels (value domain in instance vs semantics for schema constituents..]''' in the CMDI core metadata definitions (see above), and possibly also replace concepts currently in use. FAIR criteria for vocabularies need to be taken into account. |
| | 61 | |
| | 62 | On the nature of FAIR vocabularies: essential property is that vocabulary items have a globally unique identifier assigned to them. |
| | 63 | |
| | 64 | |
| | 65 | === Planning === |
| | 66 | Until the next meeting: work on the [https://docs.google.com/spreadsheets/d/1a8rCRqAbCMm_XO2-oV1oWAqZY2-JfUGc7faa3uTlKvY/edit?usp=sharing inventory spreadsheets]. |
| | 67 | |
| | 68 | Discussion and other related communication continues on the [https://clarineric.slack.com/archives/CSAKYPUFL #tf-cmdi-core-and-vocabs] [[Slack]] channel. If the need for a meeting before the [../Meeting20200212|next general CMDI meeting] arises, this can be discussed and organised in that channel as well. |
