Connection between "model calculation" and "service"

[ap-peh]

Description of the issue

How can the entity service be used to express that, for example, a forecast model is used in a service that requires specific inputs and outputs? So, with which property can the entity "model calculation" be linked to the entity "service"? Or is this connection rather not useful?

Ideas of solution

If there is not yet a property that can establish a connection between the entities "model calculation" and "service" I would suggest to create one or to enable an existing one to express this relationship.

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

[l-emele]

To me, it is not clear what kind of relation you need. Can you describe the relation that you want to express?

• A model calculation is a service?
• A model calculation depicts a service?
• A service that uses a model calculation?
• A service that has a model calculation as part?
• Something else?

And what kind of service are you referring to?

[ap-peh]

A service that has a model calculation as part - It is possible, for example, that a forecast model calculation is used in a Python service that offers a REST API. Now the properties of the service are to be described and then the properties of the entity "model calculation". For example, an agent is to be added to the service, which is not annotated in the "model calculation".

Thus, the service offers the results obtained by a special model calculation. The entity "service" expresses that an agent can use it to achieve a certain goal.