| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| ROSO11-9 | section title for 7.3 is to be fixed. | ROSO 1.0b2 | open | |||
| ROSO11-3 | ‘Detects’ and ‘causes’ to be defined. | ROSO 1.0b2 | open | |||
| ROSO11-4 | Terms for component parameters required. | ROSO 1.0b2 | open | |||
| ROSO11-2 | Terms for component action/event required. | ROSO 1.0b2 | open | |||
| ROSO11-1 | [urgent] Reference to standards to be updated | ROSO 1.0b1 | open |
The section title for 7.3 should be "Robotic Service Function Ontology."
Relationships between function/component and event/action are not described.
To describe them, vocabularies such as 'detects' and 'causes' have to be defined.
There is a lack of definitions of vocabularies to define parameters of RoIS component functions and it causes insufficience in some of the use cases.
More vocabularies should be defined.
The current document already defines the events detected from environments by functional components and the actions caused in the environments by functional components.
However, there is a lack of definitions of vocabulary to describe the events notified to services and the actions requested from services.
Therefore, it is currently impossible to describe relationships between the environment, components, and services.
Figures 1 and 2 are taken from the RoSO RFP, which was issued in 2018. The references to other standards need to be updated, and the main text in Section 1 (scope) and Section 3 (reference) need to be synchronized.