UC4 - Terminology search

[kitchenprinzessin3880]

Terminology search

Search for relevant terminologies and/or terms within terminologies. Retrieve the search results.

Corresponding user stories

• Observer- Annotate observation in situ - interoperable descriptions from start
• Vocabulary manager - Select the right URI for "nitrogen" - Better data integration and interoperability

Requirements identified in the spreadsheet (and open for discussion)

• [ ] 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
• [ ] Requires a long-term commitment to the terminology content governance
• [ ] Requires a community-endorsed terminology
• [x] 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]

Requirements (assuming the terminology search is done by a data provider and who then harvests the terms included in the terminology) R1. Terminology name (e.g., L05) R2. Terminology access endpoint (api) (note: this is technical requirement, not content requirement) R3. Collections/branches (name, url) within the terminology that will be harvested and including their relations (e.g., skos:broader, exactMatch) R4. for incremental harvest, we need creation and modified dates at term-level R5. term status (e.g., accepted)

@gwemon @mabablue Can you please check if the requirements above fit the scope of the use case? i described it based on the harvesters i implemented for pangaea (e.g., nerc, itis, past, etc.) also, the requirements above may depend on the type of terminology (taxanomy, chemincal entities)

[SirkoS]

(my requirements, as usual, a little more into the details)

• (+++) labels to identify concepts - not just human readable IRIs
• (+) labels in multiple languages for lookup in the preferred user language

i-adopt/users_stories#6 calls for a ranking of results, for this context is needed. I see the following options:

• (++) relationships between instances of different classes. based on already used classes the system could find closely related concepts (given a keyword)
• (+++) description of the concept beyond a mere label; standard search ranking depends on textual information

[kitchenprinzessin3880]

one thing missing is terminology provider name, but i am not sure if this use case is under the scope of IADOPT in general, if the focus is on an interoperability framework for observable property and related concepts

[gwemon]

@kitchenprinzessin3880 to respond to your last comment about terminology provider name, that would be part of the requirement what we called in the spreadsheet: "Requires the terminology to use a common minimum metadata schema to describe semantic artefacts and their content". It is one of the requirements listed in Yann LeFranc et al's draft document for FAIR semantics criteria. Also in your comment of 18 days ago, I had not noticed but just correcting that "NERC" would not be the terminology name. Valid terminology names would be: "BODC Parameter Usage Vocabulary" or "CF Standard Names" or "EnvThes" or "ENVO" or "Scientific Variable Ontology" . Also this infor would be come under that minimum metadata requirement too.

[kitchenprinzessin3880]

@gwemon i updated the terminology name to L05. I just realised that i am using github instead of your spreadsheet. I will incorporate the details into the spreadsheet in next few days....

[gwemon]

Requirements transferred to spreadsheet for discussion tomorrow.

[gwemon]

Requirements identified in the spreadsheet (and open for discussion)

• [ ] Requires concepts that have persistent resolvable URIs
• [x] Requires terminologies managed in a semantic repository
• [ ] Requires terminologies based on simple atomic terms
• [ ] Requires (agreement of) top-level, domain-independent categorization scheme/ontology
• [ ] Requires semantic relations between concepts
• [ ] Requires mappings between terminologies
• [ ] Requires that the provenance of mapping properties be trusted
• [ ] Requires terminologies with coarse granularity
• [ ] Requires terminologies with fine granularity
• [ ] Requires a long-term commitment governance setup
• [ ] Requires an active community supporting the terminology
• [ ] Requires a reliable technical infrastructure
• [ ] Requires input from domain experts
• [x] Requires that the terminology be part of federated community specific and/or cross-domain portals
• [ ] Requires that the terminology supports multilingual terms
• [ ] Requires multilingual editorial team or multilingual community effort
• [ ] Requires terminologies published as Linked Data
• [x] Requires the terminology to use a common minimum metadata schema to describe semantic artefacts and their content
• [ ] Requires definitions of the concepts within a terminology
• [ ] Requires used data models to be explicit and accessible
• [ ] Requires the terminology to track the provenance of individual terms

[kitchenprinzessin3880]

Requires that the terminology be part of federated community specific and/or cross-domain portals is this also includes terminology access endpoint?

[SirkoS]

Requires that the terminology be part of federated community specific and/or cross-domain portals

is this also includes terminology access endpoint?

I think this requirement has already been merged into "Requires the terminology is hosted and served by (and synchronized across) one or more reliable repositories".

Here, especially the "served by" part in my reading includes an access endpoint.

[SirkoS]

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

[SirkoS]

• Requires semantic relations between concepts
• Requires that the terminology supports multilingual terms
• Requires definitions of the concepts within a terminology
• Requires alternative syntax (like alternative notation e.g. chemical formula, abbreviations)
• Requires synonym management

Not strictly mandatory, but certainly helpful in either search itself or evaluating the results.

[SirkoS]

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