Robotic Interaction Service Framework Avatar
  1. OMG Specification

Robotic Interaction Service Framework — Open Issues

  • Acronym: RoIS
  • Issues Count: 3
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Components (from RoIS extension) to be added.

  • Key: ROIS21-3
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    Components discussed in RoIS extension RFI to be added as basic components.

  • Reported: RoIS 2.0b1 — Tue, 31 Mar 2026 21:53 GMT
  • Updated: Tue, 31 Mar 2026 21:53 GMT

Explanation of layered engines (deferred from RoIS 2.0 FTF [RoIS2-6])

  • Key: ROIS21-2
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    It is hard to understand the steps for HRI Engine to choose appropriate sub–HRI Engine. There should be more specific explanation.

  • Reported: RoIS 2.0b1 — Tue, 31 Mar 2026 21:52 GMT
  • Updated: Tue, 31 Mar 2026 21:52 GMT

Replace HRI Engine / HRI Component with RoIS Engine / RoIS Component.

  • Key: ROIS21-1
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    As discussed in RoIS extension RFI presentation, the target of RoIS component functions should not be limited to HRI (Human Robot Interaction).
    At present, RoSO enables the description of component functions designed for both human and non-human targets.
    As the target of components can be extended to objects, environment and so on, the term HRI used in HRI Engine and HRI Component to be replaced with more general word (such as RoIS Engine and RoIS Component) for further extension.

  • Reported: RoIS 2.0b1 — Tue, 31 Mar 2026 21:51 GMT
  • Updated: Tue, 31 Mar 2026 21:51 GMT