CMDI specific task force meeting 2020-01-15

---

• What?
  • Kick-off and initial (planning) discussion of tasks on 1) core metadata components and profiles + extensions; 2) (investigation into) use of FAIR vocabularies in CLARIN metadata
• Who?
  • Those partcipating in the relevant specific CMDI taskforces
  • Wednesday 15 January 2020, 14:00 - 15:00 CET (on basis of ​doodle)
• Where?
  • Zoom: ​https://clarin.zoom.us/j/534115968
  • Note: If using Zoom for the first time, allow for some setup time before the meeting. The above link should get you started. See ​documentation for more information.

Documents

• ​Proposal/working document for these two related tasks
• ​Earlier draft document collecting some thouhgts and preliminary work on use of external vocabularies and concepts
• ​CMDI strategy

Preparation

• Suggest/think about more specific task definitions
• Collect relevant use cases
• Prepare a summary of any ongoing, completed or abandoned work you are or have been involved in that can contribute to these tasks

Agenda

(Tentative)

1. Definition of tasks
   1. Overall objective
   2. Use cases
   3. Task definition: CMDI core components & profiles
   4. Task definition: FAIR vocabularies for concepts and controlled vocabularies in CLARIN metadata
2. Current state
   1. Related activities & existing work
      1. General info/recommended component activities as part of CMDI Best Practices task (Marcin, Oddrun, Twan, ...)
      2. Common use cases (Andreas, Twan)
      3. ISO 24622 - Part 3: "Recommended components" (Penny)
      4. META-SHARE schema work (Penny)
      5. Quest project (Felix)
      6. CMDI <> DDI, DataCite conversions (Twan, Dieter)
      7. Work on vocabularies, ontologies in European projects (Dieter, Matej)
         • ​SSHOC WP4 "Developing the SSHOC Reference Ontology"
         • ​DARIAH-EU Thesaurus Maintenance
      8. ​RDA Research Metadata Schemas (anyone?)
3. Planning
   1. Approach/actions, distribution of work
   2. Timeline
   3. Next meeting

Notes

Definition of tasks

Agreement on overall objective. Some rephrasing of specific task descriptions:

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.

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. However, it would be nice if we could implement a (non-instantiable) template for such profiles.

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.

On the nature of FAIR vocabularies: essential property is that vocabulary items have a globally unique identifier assigned to them.

* this phrasing needs to be finalised; important to have consistent terminology to distinguish between two uses of vocabularies (semantic annotaiton at component/profile/schema level vs value domain at instance level)

Current state: Related activities & existing work

Common use cases: besides the ​report document (work in progress), there is also a new ​spreadsheet that quantifies and aggregates the survey responses in terms of information aspects per resource type.

ISO 24622 - Part 3: "Recommended components": Although frozen as an activitiy, quite a bit of preliminary output of analysis and modelling work is available that can be used as input in our activities. See public ​Google Drive share.

META-SHARE schema work: Work in progress in context of European Language Grid, based on Metashare ontology and aiming to reuse existing vocabularies and ontologies where possible (prioritise on specific ones like DCAT). Penny will share documents.

Planning

Until the next meeting: work on the ​inventory spreadsheets.

Discussion and other related communication continues on the ​#tf-cmdi-core-and-vocabs Slack channel. If the need for a meeting before the next general CMDI meeting (2020-02-12) arises, this can be discussed and organised in that channel as well.