TLA/CLARIN CLAVAS Use Cases: Overview CMDI integration – Metadata editing Resource Annotation Kinship data

CMDI integration: open/closed vocabularies Open vocabularies – New in CMDI – Implementation: augment standard elements (typically String) by reference to vocabulary ID Specify preferred label Automatically fetch vocabulary from data category?

CMDI integration: open/closed vocabularies Closed vocabularies – Already available in CMDI – Reference solution has some issues: Validation outside schema – 'Proxy' through schema Dynamic nature – Value set provides context. » E.g. adding a color or language changes semantics of existing values – Solution: versioning? – Import function in Component Registry Will ‘freeze’ vocabulary

CMDI integration: Metadata editing (Arbil)

Vocabulary URI is taken from profile schema Vocabulary gets read entirely from the API (probably in RDF format) and deserialised Existing UI components are fed with deserialised vocabulary information Autocomplete API for large vocabularies (online usage) Localisation

Resource Annotation (ELAN)

Use cases: – Language list – Part of speech tags – Glosses within specific domain (e.g. sign language transcription) ELAN already supports custom vocabularies – XML files (local/server) Multilingual in development – Potential to extend with support for OpenSKOS

Kinship data (KinOath)

Same use cases as CMDI editing Non-profiled (unstructured) data sets – User defined vocabulary links Potential for centralized vocabularies (per-project with defaults): – Field names for entity properties (name, date of birth) – Relation types (ancestor, descendant, adopted, milk) – Kin terms (uncle, aunt, grandfather, heeroom) – Kin types (E=ego, F=father, M=mother, P=parent) – Entity types (individual, object, location, event)

Summing up… Use cases in metadata, annotation and kinship software TODO: technical design of integration into CMDI – Then implement support in Arbil Will we be using OpenSKOS to its full extent?