stap-m

I think, the cleanest solution is to use `has characteristic` instead of `has function`: - `has characteristic` is the parent object property of `has function` - it is inverse of...

Well spotted. I can reproduce the bug. Reading the definition, I think OEO_00140170 should be a data property, instead. Annotation properties are used to annotate oeo entities, not models.

> Reading the definition, I think OEO_00140170 should be a data property, instead. Annotation properties are used to annotate oeo entities, not models. Any comments? We should fix this rather...

> I think, it is helpful to define a general `energy loss` first. Here is a first proposal: _An energy loss is a process attribute that describes the difference of...

ENVO has a concept for [snow](https://www.ebi.ac.uk/ols4/ontologies/envo/classes/http%253A%252F%252Fpurl.obolibrary.org%252Fobo%252FENVO_01000406) which could be reused. It is classified as `environmental material`, a class that OEO does not have. But `water` might be a good parent...

I'm ok with your proposal. Since it seems to be at least inspired by ENVO, we might cite or mention it, though, e.g. by an annotation `may be identical to`...

I'd be ok to introduce specific weather time series, as proposed by @ap-peh , maybe as equivalent classes. Regarding the axioms for specific weather time series, `is about` is probably...

> Another time series needed for a forecasting model is a consumption time series. Here, too, the entity Consumption already exists and should be used to express that the time...

From your comment, I figure that `forecast time series` should be an own type of time series, since weather time series can be forecast time series or measured or even...

> I would suggest creating a specific property for the statement: The time series is of type XY. Ok, good idea. `time series`, being GDCs, are not intuitive for adding...