Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Represent increase/decrease opposed to absolute values #1407

Closed
1 task done
lumi321 opened this issue Nov 18, 2022 · 7 comments · Fixed by #1644
Closed
1 task done

Represent increase/decrease opposed to absolute values #1407

lumi321 opened this issue Nov 18, 2022 · 7 comments · Fixed by #1644
Assignees

Comments

@lumi321
Copy link
Contributor

lumi321 commented Nov 18, 2022

Description of the issue

Not all values are depicting absolut values at a given point in time. Some values are depicting an increase of some parameter over a certain time span. How this notion can be represented in metadata depends on the structure of the data and the metadata.

Ideas of solution

  1. add concepts that indicate increase/decrease and use them in combination with other concepts for "usual" annotation (related to the composed module discussion)
  2. use a table-wide key in the metadata, e.g. subject, to indicate that all values in the table represent an increase or decrease
  3. ask for an additional key in the metadata that indicates whether a value is absolut, shows an increase or a decrease
  4. something else

Workflow checklist

  • I am aware of the workflow for this repository
@lumi321 lumi321 added the To do Issues that haven't got discussed yet label Nov 18, 2022
@l-emele l-emele added this to the oeo-release-1.13.0 milestone Nov 21, 2022
@stap-m
Copy link
Contributor

stap-m commented Jul 18, 2023

Related to #1595 ?

@nelekoehler or @viktorwichern can you take a look at this issue?

@nelekoehler
Copy link
Contributor

It seems to be related. In #1595 it's suggested to add processes heating and cooling, which would be used to describe the increase/decrease of thermal energy of a material entity. So maybe the suggested concepts of increase and decrease in this issue could be used for that too.

@nelekoehler
Copy link
Contributor

Maybe Increase and decrease could each be introduced into the ontology as a process. (Increase: to become progressively greater and decrease: to become progressively less).
These concepts could then be used for heating and cooling, as it was questioned in #1595 , among others, by adding something like: has participant some increase or decrease and has unit some temperature unit as axioms). On the one hand, this is perhaps a bit more long-winded then using something like heating or cooling, on the other hand, increase and decrease can be used in a more versatile way (i.e. not only with temperature units and connected to thermal energy, but also with other units of measurements).

@github-actions github-actions bot removed the To do Issues that haven't got discussed yet label Jul 24, 2023
@nelekoehler
Copy link
Contributor

In the following I would like to suggest some definitions:

Increase:

  • A process of becoming larger, more numerous, more important, or more likely.

Decrease:

  • A process of becoming smaller, less numerous, less important, or less likely.

I looked at different ontologies and these are the ones used in the NCI (a biomedical ontology) and I think it is general enough to be fitting for different uses.

Other ontologies like the INO, also have definitions for increase or decrease, but they use these terms also in the definition itself, so they seem circular, which isn’t ideal.

Possible Axiom:

  • Has participant some entity

With reference to the other issue #1595 heating and cooling could be, as @stap-m already mentioned, something like: 
- heating EquivalentTo: increase and ('has energy input' some 'thermal energy') and ('has energy output' some 'thermal energy') and cooling resp.

@stap-m
Copy link
Contributor

stap-m commented Aug 30, 2023

I am ok with the proposed definitions.

@l-emele @areleu @chrwm any opinion to the suggested structure with respect to heating etc.? For charging #1622 this could also be used. Probably there are more processes.

@l-emele
Copy link
Contributor

l-emele commented Aug 30, 2023

I am fine with these proposals.

@nelekoehler
Copy link
Contributor

Okay, if there aren't any other suggestions or concerns, I am going to implement it.

@github-project-automation github-project-automation bot moved this to Done in Issues Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants