You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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 am aware that
The text was updated successfully, but these errors were encountered: