GSoSD Arrowhead Core Systems 5.0 / Concepts Reference: The concept of service type

[PerOlofsson-Sinetiq]

The concept of service type should be present in both the AH 5.0 Definition document and should be used in the GSoSD document.

The Service Description document should define the Service Type?

For example the Orchestration concept should benefit from beeing able to serve consumer systems with a plate of services according to a service type rather than pinpointing all instances of services.

[MatsBJohansson]

Section 2.3 Service Provision and Consumption My view in that the service provider is the system that publish the service in the service registry. Regardless in which direction the main information payload travels.

Section 2.4, footer An Arrowhead cloud "conforms to various architectural requirements put forth by the Eclipse Arrowhead project in a separate document." What document? The GSoSD?

[jerkerdelsing]

@PerOlofsson-Sinetiq The service type concept is extensively used in the Arrowhead DSL and SysML modeling. I understand that your request is a way of allowing usage of other Orchestration microsystems than the reference implementation. What need to be considered here is further interoperability with other Orchestration concepts used. We need to find the balance between interoperability and acceptance by industrial customers.

[jerkerdelsing]

Section 2.3 Service Provision and Consumption My view in that the service provider is the system that publish the service in the service registry. Regardless in which direction the main information payload travels.

Section 2.4, footer An Arrowhead cloud "conforms to various architectural requirements put forth by the Eclipse Arrowhead project in a separate document." What document? The GSoSD?

I think these comments are obsolete with the agreed version from early 2024.