1 / 10

TLA/CLARIN CLAVAS Use Cases: Overview

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

tamas
Download Presentation

TLA/CLARIN CLAVAS Use Cases: Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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?

  3. 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

  4. CMDI integration:Metadata editing (Arbil)

  5. 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

  6. Resource Annotation (ELAN)

  7. 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

  8. Kinship data (KinOath)

  9. 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)

  10. 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?

More Related