Sources of inspiration Discussions in DFT Use Cases Discussions in DF Use Cases „Paris“ Document Comments on „PARIS“ document Urgently need “Basic and Simple” Messages PARIS Doc: Data Management Trends, Principles and Components - What Needs to be Done Next? V6.1 DFT, Data Fabric and Metadata
Project-Infrastructures (NoMaD, DOBES, etc.) Domain-Infrastructures (CLARIN, ELIXIR, etc.) e-Infrastructures (EUDAT, OpenAIRE, etc.) Metadata Universe Why basic and simple Messages
Layers Metadata Is it all the same? NO We need to be more specific.
1.5 Metadata Definition Metadata contains descriptive, contextual and provenance assertions about the properties of a DO. Note: Such metadata will make the DO for example discoverable, accessible and usable/interpretable. Note: To make metadata referable it needs to be associated with a PID and thus is a DO. Note: Metadata minimally needs to contain the PID of the DO. DFT Model -> Explicitness
Collections
Cycles and Fabrics Metadata (relevant at different phases, MD for scientific work # MD for occasional searching)
Metadata Creation Phases
Core of the Fabric Prov plays an important role here, very detailed MD needed
Reduce heterogeneity & costs Make solutions stronger Achieve sustainability Leave flexibility Even more opportunities Leave flexibility Even more opportunities Scientific Analytics Scientific Creation Management Curation Access PID, AAI, MD, WF, Registries, Repositories, meta- semantics, etc. Finding CoCos
CLARIN Example: CDMI CLARIN concept registry (SKOS) component editor myprofile metadata editor metadata descriptions CLARIN component registry New conc component registration concept registration DC etc.
Much confusion and huge solutions space Schema directory is very good – first step Urgent actions: Terminology system MD, PID Info Types, administrational, descriptive, archival, rights, relations, external/internal, etc. semantic tags WF type of MD Term Wiki Components/Packages Framework Registry Packages/components Specs for WF code snippets incl. PROV And now …