ROSO 1.0b2 FTF Avatar
  1. OMG Issue

ROSO — Definition of RoIS parameters to be described by name in addition to classes.

  • Key: ROSO-7
  • Status: closed  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    Every component parameter in RoIS 1.2 (and the RoIS 2.0 draft, if possible) must be instantiated and described in relation to the component.
    As an example of detail missing for a PSM, there is a class named Direction with no properties or definitions for how a specific direction would be represented.

  • Reported: ROSO 1.0b1 — Mon, 20 May 2024 14:06 GMT
  • Disposition: Resolved — ROSO 1.0b2
  • Disposition Summary:

    Definition of RoIS parameters to be described by name in addition to classes.

    For Secion 7.3 Robotic Service Function Ontology,
    1. Relationship between Function and Component renamed.

    • Object property ‘hasFunction’ renamed to ‘features.’

    2. Relationship between Function and Event/Action introduced.

    • Object property ‘detects’ for sensors which detects events
    • Object property ‘causes’ for actuators which causes action

    Figure 7 in RoSO-10 to be updated with two figures as well as other two ontologies.

    In Annex A,
    4. Section title indicated as ‘Informative’ instead of ‘non-normative.’
    5. Figure 6 in beta1 replaced with two new figures that represents Person Detection Component as an example.

    • Figure 9: Classes for Person Detection
    • Figure 10: RoIS Parameters used in Person Detection defined as object properties

    Update of ontology RDF files are also attached with this issue.

  • Updated: Mon, 24 Mar 2025 13:36 GMT
  • Attachments: