Robotic Interaction Service Avatar
  1. OMG Specification

Robotic Interaction Service — Open Issues

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

Issues Descriptions

Figure B.1 to be fixed.

  • Key: ROIS2-12
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    Some arrows in Figure B.1 are not aligned to the destination boxes.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:41 GMT
  • Updated: Mon, 12 May 2025 11:41 GMT

Explanation of "navigation."

  • Key: ROIS2-11
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    It may be a good idea to review the definition of "navigation".
    Considering the expansion of the features of service robots of these days, current definition of "navigation" in this docuement is too limited.
    This document only defines navigation as to navigate another agent to the indicate goal point. These days, there are some other "navigation" that robots can do.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:39 GMT
  • Updated: Mon, 12 May 2025 11:39 GMT

Replace "he/she" with "user."

  • Key: ROIS2-10
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    In Table 8.42, there is one he/she expression in the second sentence.
    For diversity perspective, it should be replaced with "user" like the other parts.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:38 GMT
  • Updated: Mon, 12 May 2025 11:38 GMT

Conflict descriptions in "person detection."

  • Key: ROIS2-9
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    The description of "person detection" component says "Detects number of people", but Figure 8.14 shows the flow that firstly returns if there are people.
    There is a conflict between them.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:37 GMT
  • Updated: Mon, 12 May 2025 11:37 GMT

Duplicated descriptions for profiles.

  • Key: ROIS2-8
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    Paragraphs in p.10 and p.36 are identical.
    The duplicated one in p.36 should be simplified and moved into following four sections.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:35 GMT
  • Updated: Mon, 12 May 2025 11:35 GMT

Inconsistent table titles.

  • Key: ROIS2-7
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    Titles of Table 8.39 and 8.40 are different from those in their rdfs:label columns. They should be fixed.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:34 GMT
  • Updated: Mon, 12 May 2025 11:34 GMT

Use of sub-engines to be explained.

  • Key: ROIS2-6
  • 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 sholuld be more specific explanation.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:32 GMT
  • Updated: Mon, 12 May 2025 11:32 GMT

Use of ‘hasTimeLimit’

  • Key: ROIS2-5
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    As 'hasTimeLimit' is defined in RoSO 1.0 FTF, descriptions of RoIS components to be updated with it.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:30 GMT
  • Updated: Mon, 12 May 2025 11:30 GMT

Terms for component parameters required.

  • Key: ROIS2-4
  • Status: open  
  • Source: JARA ( Mr. Koji Kamei)
  • Summary:

    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.

    (This issue is identical to ROSO11-4, and the resolution in RoSO 1.1 RTF is expected to be reflected into RoIS 2.0 FTF.)

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:29 GMT
  • Updated: Mon, 12 May 2025 11:29 GMT

‘Detects’ and ‘causes’ to be defined.

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

    Relationships between function/component and event/action are not described.
    To describe them, vocabularies such as 'detects' and 'causes' have to be defined.

    (This issue is identical to ROSO11-3, and the resolution in RoSO 1.1 RTF is expected to be reflected into RoIS 2.0 FTF.)

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:28 GMT
  • Updated: Mon, 12 May 2025 11:28 GMT

Terms for component action/event required.

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

    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.

    (This issue is identical to ROSO11-2, and the resolution in RoSO 1.1 RTF is expected to be reflected into RoIS 2.0 FTF.)

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:27 GMT
  • Updated: Mon, 12 May 2025 11:27 GMT

Robotic interaction service to be explained in overview.

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

    Relationship among Robotic Service and Service Robot including the viewpoint of Robotic Interaction Service to be described in the overview section.

  • Reported: RoIS 2.0a1 — Mon, 12 May 2025 11:23 GMT
  • Updated: Mon, 12 May 2025 11:23 GMT