1. OMG Mailing List
  2. Robotic Interaction Service (RoIS) Framework 1.1 RTF

Open Issues

  • Issues not resolved
  • Name: rois-rtf
  • Issues Count: 6

Issues Descriptions

"Overview" section is a bit misplaced.

  • Key: ROIS12-5
  • Status: open  
  • Source: JARA ( Koji Kamei)
  • Summary:

    The specification starts with an “Overview” section, that has useful information to understand the specification. However it is placed before Clause 1 “Scope” and therefore a bit misplaced, from a standards document layout point of view. It would be good if a follow-on RTF would place this material into a more appropriate location, preferably as a new, informative Clause 7 and move the existing Clauses 7 and higher up by one number.

    The new Clause 7 should then be combined with the material from the existing Clause 7.2, which has good explanations, but is a bit misplaced in the middle of normative message and interface specifications.

  • Reported: RoIS 1.0 — Sat, 7 Nov 2015 07:03 GMT
  • Updated: Mon, 6 Nov 2017 00:56 GMT

overview Package and UML Class diagram.

  • Key: ROIS12-4
  • Status: open  
  • Source: JARA ( Koji Kamei)
  • Summary:

    The specification would benefit in the future from an overview Package and UML Class diagram [class names only].

    Two extra layers of Packages named “RoIS” around the Packages containing real model elements. While strictly speaking not wrong, those extra onion layers look a bit odd.

  • Reported: RoIS 1.0 — Sat, 7 Nov 2015 07:08 GMT
  • Updated: Mon, 6 Nov 2017 00:56 GMT
  • Attachments:

"Platform Specific Model" which is located in the chapter "Platform Independent Model" should be moved to a new section.

  • Key: ROIS12-6
  • Status: open  
  • Source: AIST ( Toshio Hori)
  • Summary:

    "Platform Specific Model (PSM)" is located in the chapter 7 "Platform Independent Model (PIM)" currently.
    PSM should be located at the same level with PIM.

  • Reported: RoIS 1.1 — Tue, 6 Dec 2016 17:57 GMT
  • Updated: Mon, 6 Nov 2017 00:56 GMT

Atomic allocation of multiple HRI Components required

  • Key: ROIS12-3
  • Legacy Issue Number: 17133
  • Status: open  
  • Source: JARA ( Koji Kamei)
  • Summary:

    Methods "search," "bind" and "bind_any" may be extended for allocating
    multiple components at once avoiding race condition.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Updated: Mon, 6 Nov 2017 00:56 GMT

Ambiguous definition of "Condition"

  • Key: ROIS12-2
  • Legacy Issue Number: 17138
  • Status: open  
  • Source: JARA ( Koji Kamei)
  • Summary:

    "Condition" is used in many interfaces and method, but it is difficult
    to implement without example.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Updated: Mon, 6 Nov 2017 00:56 GMT
  • Attachments:

Dependency among HRI Components should be defined

  • Key: ROIS12-1
  • Legacy Issue Number: 17134
  • Status: open  
  • Source: JARA ( Koji Kamei)
  • Summary:

    Dependencies (Requisite conditions) among HRI Components should be
    defined in HRI Profile.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Updated: Mon, 6 Nov 2017 00:56 GMT