Entity forecast SubClass of model calculation

[ap-peh]

Description of the issue

Currently, the entity "forecast" is SubClass of the entity "information content entity". Optimisation is located under the entity "model calculation".

Ideas of solution

Since the "forecast" also requires a model and has inputs and outputs, I would suggest defining the "forecast" entity as a SubClass of "model calculation".

Workflow checklist

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

I am aware that

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

[l-emele]

Thanks for your feedback.

The class forecast is currently defined as: A forecast is an information content entity that contains statements about the most probable future development predicted with the help of past and present data. This is a result of a discussion in issue #1544.

What you mean, is probably the process of forecasting using a model, but this is a different concept than what we wanted to depict with the existing class. The concept of forecasting we do not yet have in the OEO but we might add it. I thus change the label to "[A] new term".

A potential definition might be: Forecasting is a model calculation that produces a forecast.

[l-emele]

@ap-peh : Any feedback on my proposal in the comment above?

[ap-peh]

I think it is a good suggestion to create a new entity that expresses Forecasting is a model calculation that produces a forecast.

[l-emele]

No further comments, so I will implement forecasting.