UC2 - Terminology management

[mabablue]

Terminology management

Gather/curate and maintain the individual terms within a terminology.

Corresponding user stories

• Asset manager tracks nitrogen model changes to assess impact on related apps
• Terminology provider - access agreed mappings - gain efficiency in data exchange

Requirements identified in the spreadsheet (and open for discussion)

• [x] Requires concepts that have persistent resolvable URIs
• [x] Requires the terminology be hosted by a trustworthy semantic repository
• [ ] Requires terminologies based on simple atomic terms (e.g. used to make more complex compound terms)
• [ ] Requires (agreement of) top-level, domain-independent categorization scheme/ontology
• [ ] Requires that the terminology includes semantic relations between concepts
• [ ] Requires mappings between terminologies
• [ ] Requires that the provenance and status metadata of mappings between concepts be accessible.
• [ ] Requires coarse-grained terminologies for observable properties
• [ ] Requires fine-grained terminologies for observable properties
• [x] Requires a long-term commitment to the terminology content governance
• [x] Requires a community-endorsed terminology
• [ ] Requires the terminology to be discoverable (not just technically but also e.g. listed in relevant community portals or discoverable via search engines)
• [ ] Requires that the terminology supports multilingual terms
• [x] Requires common minimum metadata describing the terminology
• [ ] Requires definitions of the individual terms within a terminology
• [ ] Requires that any underlying model used by the terminology be described and accessible
• [ ] Requires the provenance properties of individual terms to be documented in a standardized way
• [ ] Requires examples of usage of the terminology to be available and documented
• [ ] Requires the terminology to be accessible programmatically
• [ ] Requires deprecated term status and deprecation policy
• [ ] Requires tools supporting annotation using the terminologies
• [ ] Requires tools validating the applied terms against terminologies
• [ ] Requires tools for mapping
• [ ] Requires a mean to manage alternative notations

last updated: 2020-09-21

[kitchenprinzessin3880]

Requires terminologies managed in a semantic repository & Requires a long-term commitment governance setup

• for simplicity, we can combine these into requires management and long term preservation of terminologies

Requires a reliable technical infrastructure, i.e., that enables findability and accessibility of terminologies.

Requires input from domain experts, e.g., as part of creation and quality control (review) of...

[mariutzica]

Requires some agreed-upon top-level categorization scheme.

[SirkoS]

^{[automated message]} Updated top entry of this issue on 2020-07-11

[SirkoS]

Requires deprecated term status and deprecation policy

Isnt that also part of managing a terminology?

[gwemon]

@SirkoS @mariutzica @kitchenprinzessin3880 I have put a thumb up to indicate that your suggestions have been implemented. The tick list at the top of this ticket should reflect this (8 requirements).

[SirkoS]

^{[automated message]} Updated top entry of this issue on 2020-09-21