include terms covering the temporal regions of the scenario analysis space

[stap-m]

Description of the issue

Include scenario year, weather year, typical year/period, ...

Ideas of solution

If you already have ideas for the solution describe them here

Workflow checklist

• I discussed the issue with someone else than me before working on a solution
• I already read the latest version of the workflow for this repository
• The goal of this ontology is clear to me

I am aware that

• every entry in the ontology should have a definition
• classes should arise from concepts rather than from words

[stap-m]

Are those terms really referring to 1-D temporal regions or rahter to data sets like 'time sampled measurement data set'?
My spontanious description of meteorological year would be something like "a time series of meteorological measurements in a historic year".
@OpenEnergyPlatform/oeo-general-expert-formal-ontology
@OpenEnergyPlatform/oeo-domain-expert-meteorology

[l-emele]

Those there two different things: One thing meteorological year itself is a 1-D temporal region. The other thing is the data representing that 1-D temporal region. The time series of measurements is the latter.

[stap-m]

And how would you define the meteorological year itself?

[sfluegel05]

I would argue that scenario year, weather year, ... are one-dimensional temporal regions (probably even time steps) that are related to time series. Every time series consists of zero-dimensional temporal regions which themselves are related to quantity values.

So we would basically use the "entity in reality/quantity value"-distinction suggested in #434 (comment) twice: The zero-dimensional temporal region is an entity in reality which has a quantity value. And, a bit modified, the scenario year (or similar) is an entity in reality and the related time series is a "quantity value" which (in this case indirectly) provides the actual data.

I couldn't find a fitting object property to relate scenario year and time series yet. Something like has quantity value (but not just for quantity values) or an inverse of is about would be nice.

[akleinau]

this issue is targeting a lot of different terms, we should split it up in several issues and implement one after each other.
@stap-m do you have a list of terms necessary to get included?

[stap-m]

From #764:
add relation is about to analysis scope

[sfluegel05]

Based on the discussion so far and based on new classes and relationships that weren't there at the start of this issue (e.g., #538 ) the consensus seems to be that we have two things: We have temporal regions and we data items that provide measurement data about these temporal regions.
For example to describe a meteorological year, we need a 1-dim temporal region that is a particular year, and we need a time series that contains the measurement data taken during the year.

Does everyone agree with this structure? If so, the next steps would be to
(A) find concepts we want to include in the ontology
(B) define temporal regions and data sets for each concept

[sfluegel05]

So far we have the following temporal regions with preliminary labels and definitions:

• scenario year: A scenario year is a time step that has a duration of one year and is part of a scenario horizon.
• meteorological year: A meteorological year is a time step in which meteorological data was collected and that has a duration of one year.
• scenario horizon: A scenario horizon is a time step that is under investigation and consists entirely of one or more scenario years. (see add concept 'analysis scope' #638 (comment))

For each of them we can define a data set according to the schema A X data set is a time series that contains data about a specific X.
For the year-classes, we can also include the axiomatic connection has part some (duration and 'has unit' some year and 'has number' value 1) (has number is yet to be included, see #829)

I also opened a new issue for typical year, since this seems to be a special case that doesn't fit the temporal region-data set-schema: #830

[l-emele]

I think, this is ready for implementation. @stap-m : Do you agree?

[l-emele]

We can also apply the axiom has part some (duration and 'has unit' some year and 'has number' value 1) to typical year and a slightly adapted axiom has part some (duration and 'has unit' some day and 'has number' value 1) to typical day.