UC1 - Semantic modelling

[mabablue]

Semantic modelling

Develop formal terminologies to represent the concepts being described and the relationships between those concepts.

Corresponding user stories

• Soil Data manager - Normalize data - Achievement of a standard
• Scientist - Create standardized descriptions of new particle formation events - Interoperable and reusable data
• Data Manager - ObservableProperty with parameters - create identifiers for property+parameters
• Data engineer - create variable list - harmonize vocabulary

Requirements identified in the spreadsheet (and open for discussion)

• [ ] Requires concepts that have persistent resolvable URIs
• [ ] Requires the terminology be hosted by a trustworthy semantic repository
• [x] Requires terminologies based on simple atomic terms (e.g. used to make more complex compound terms)
• [x] Requires (agreement of) top-level, domain-independent categorization scheme/ontology
• [x] 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
• [x] Requires fine-grained terminologies for observable properties
• [ ] Requires a long-term commitment to the terminology content governance
• [ ] 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
• [ ] 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

[gwemon]

3 key requirements have been identified so far:

• The semantic modelling of observable properties requires a source/store (or sources) of simple atomic concepts in order to correctly capture essential information about what is being measured/modelled/observed.
• It also requires the ability to build and maintain relationships between these atomic concepts.
• The conceptualisation of scientific variables using a semantic model requires that the person in charge of the conceptualisation have a good understanding of the measurement methods and benefits from input/validation from domain experts.

[kitchenprinzessin3880]

@gwemon after re-thinking about this UC1, i wonder if we should rewrite this use case statement, e.g., Develop formal terms to represent the concepts being described and the relationships between those (??) the reason is that one might develop and add new term to an already existing terminology..

another related requirement is that the metadata of the term creator and related sources. this may be considered as provenance information of term creation.

[kitchenprinzessin3880]

following a quick discussion with @mabablue , it would be great to add further description about this use case where it refers to data model (e.g., SSN) or 'content' model (e.g., PATO).

[gwemon]

Thanks for comments @kitchenprinzessin3880 what is PATO?

[kitchenprinzessin3880]

Phenotype And Trait Ontology, http://obofoundry.org/ontology/pato.html

[mariutzica]

I think this would also require (4) "Requires top-level, domain-independent categorization scheme/ontology" as part of the process.

[gwemon]

@gwemon after re-thinking about this UC1, i wonder if we should rewrite this use case statement, e.g., Develop formal terms to represent the concepts being described and the relationships between those (??) the reason is that one might develop and add new term to an already existing terminology..

another related requirement is that the metadata of the term creator and related sources. this may be considered as provenance information of term creation.

For me "developing formal terminologies" does include the act of extending existing terminologies to cover new requirements. Semantc modelling does need some structure so it goes beyond the "development of terms".

[gwemon]

I think this would also require (4) "Requires top-level, domain-independent categorization scheme/ontology" as part of the process.

Hi @mariutzica. I thought about it but concluded that this was desirable more than essential and this is because it says "domain-independent"- I feel that you could have semantic modelling schemes that have a top-level categorization scheme that is domain-dependent but could still be connected to a domain-independent categorization scheme. We can explore.

[SirkoS]

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

[SirkoS]

Requires examples of usage of the terminology to be available and documented

this is the prime use case for this requirement, isnt it?

[gwemon]

I think this would also require (4) "Requires top-level, domain-independent categorization scheme/ontology" as part of the process.

Hi @mariutzica. I thought about it but concluded that this was desirable more than essential and this is because it says "domain-independent"- I feel that you could have semantic modelling schemes that have a top-level categorization scheme that is domain-dependent but could still be connected to a domain-independent categorization scheme. We can explore.

Well this requirement has been ticked, so maybe others agreed with you @mariutzica and it is indeed needed ;-)

[gwemon]

Requires examples of usage of the terminology to be available and documented

this is the prime use case for this requirement, isnt it?

Added in

[SirkoS]

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