add time step, time series

[akleinau]

part of #267

• moves quantity value class over to oeo-shared bc it's needed in oeo-model too and was in oeo-physical
• moved lenght value with it bc I think it's also needed in more than oeo-physical

add classes with definitions:

• start time and end time: start time is a zero-dim temporal region that indicates the beginning of a 1-dim temporal region. End time indicating the end, accordingly.
• duration is a quantity value that can be related to both time step and time series. duration is a quantity value indicating the time span of a 1-dim temporal region, measured in a time unit.
• time step: a time step is a 1-dim temporal region that has a start time and an endtime and thus a finite duration.
• time series: time series is a data set that references a set of time steps or zero-dim temporal regions.

add relations:

• duration: is about some 1-dim temporal region and has unit some time unit
• time step: has part some start time and has part some end time and has part some duration
• time series: has part some start time and has part some end time and has part some duration
• time series: is about some (time step or zero-dim temporal region)

[stap-m]

moved lenght value with it bc I think it's also needed in more than oeo-physical

@akleinau Do you have an example for length value to be used in another module?
It's a point worth a discussion. Our models depict what's located in the physical world. Thus, many classes from oeo-model will be related to classes from oeo-physical. Can relations work across modules?

For time series it definitely makes sense to be part of oeo-model.
But start time etc could also be seen as part of oeo-physical.

[akleinau]

moved lenght value with it bc I think it's also needed in more than oeo-physical

@akleinau Do you have an example for length value to be used in another module?
It's a point worth a discussion. Our models depict what's located in the physical world. Thus, many classes from oeo-model will be related to classes from oeo-physical. Can relations work across modules?

For time series it definitely makes sense to be part of oeo-model.
But start time etc could also be seen as part of oeo-physical.

yes, that asks the question which relations and entities are placed in oeo-shared (imported in all modules) and which in oeo.omn (put on top of all modules). I would say to put everything thats needed in more than one module to connect classes of one module to each other in oeo-shared and everything that combines more modules in oeo.omn.

So start time and end time could be needed in both modules to build relations in these modules and therefore oeo-shared.
Length value is used for relations in oeo-physical and might be for relations between oeo-physical and oeo-model, therefore it is in oeo-physical and these relations will be in oeo.omn

[Vera-IER]

Please start the sentence with a capital letter.

[Vera-IER]

See above

[Vera-IER]

See above

[Vera-IER]

Please start the sentence with a capital letter.

[sfluegel05]

I would also add an "A" in the beginning, so "A start time..." (and analogous for the others).

[Vera-IER]

See above.

[sfluegel05]

I tried to resolve the merge conflicts. I wasn't sure about some things:

• in commit e902808 the unique individual identifier from Add annotation property unique individual identifier and some IPCC sector indiviuals #523 got removed (I re-added it)
• in 7c26aa6 you added quantity value to oeo-shared without removing it from oeo-physical (those two were also different versions of quantity value, in oeo-physical it was the version after Add is about property #518, in oeo-shared it was the version before Add is about property #518 ) (I removed it from oeo-physical and updated it in oeo-shared)
• oeo-physical doesn't import the uo-module anymore and oeo-shared doesn't import the iao-minimal-module anymore. I don't know if this will lead to problems or not.

But I think it is working now.