Robotic Interaction Service Avatar
  1. OMG Specification

Robotic Interaction Service — Closed Issues

  • Acronym: RoIS
  • Issues Count: 6
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

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

  • Key: ROIS12-6
  • Status: closed  
  • 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
  • Disposition: Resolved — RoIS 1.2b1
  • Disposition Summary:

    Move the description of PSMs in Chapter 7.7 to a new chapter.

    Description of C++, CORBA and XML PSMs in Chapter 7.7 were moved to a new chapter 9 (created).
    No update of its contents was required.

  • Updated: Mon, 2 Apr 2018 18:08 GMT

"Overview" section is a bit misplaced.

  • Key: ROIS12-5
  • Status: closed  
  • 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
  • Disposition: Resolved — RoIS 1.2b1
  • Disposition Summary:

    A new chapter 'RoIS Framework' was created and merge 'Overview' and (old) Section 7.2 were merged into the chapter.

    The overview and the structure of RoIS Framework were placed in the 'Overview' section and Section 7.2 in RoIS 1.1 so we merge them into one place (a chapter).
    We create a new chapter 7 entitled 'RoIS Framework' and merge the overview and the structure of RoIS Framework into this new chapter.
    As a result, the (old) Chapter 7 will be renumbered to Chapter 8.

  • Updated: Mon, 2 Apr 2018 18:08 GMT

overview Package and UML Class diagram.

  • Key: ROIS12-4
  • Status: closed  
  • 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
  • Disposition: Resolved — RoIS 1.2b1
  • Disposition Summary:

    A new section is added for package overview and the model is updated.

    In accordance with the resolution of issue 12-5, the package structure is added as a new section "8.2 Package structure” with a package diagram as below.

    The model is also updated with the attached xml file that do not contain the extra RoIS layer.
    It is referenced as http://www.omg.org/spec/RoIS/20171201/UML_Model.xmi.

  • Updated: Mon, 2 Apr 2018 18:08 GMT
  • Attachments:

Atomic allocation of multiple HRI Components required

  • Key: ROIS12-3
  • Legacy Issue Number: 17133
  • Status: closed  
  • 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
  • Disposition: Deferred — RoIS 1.2b1
  • Disposition Summary:

    Atomic allocation of multiple HRI components requires API changes.

    To achieve atomic allocation of multiple HRI components, a new API such as bind_all() may be required. Such a change should be discussed in major update (RoIS 2.0).

  • Updated: Mon, 2 Apr 2018 18:08 GMT

Ambiguous definition of "Condition"

  • Key: ROIS12-2
  • Legacy Issue Number: 17138
  • Status: closed  
  • 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
  • Disposition: Resolved — RoIS 1.2b1
  • Disposition Summary:

    *Four examples of "Conditions" are added as Annex E to illustrate how to implement "Condition." *

    As "Conditions" are used in many interfaces and methods, there are no particular examples in the previous revision of RoIS. Four examples of "Conditions" are added to illustrate how to implement "Condition."

    Contents of the attached file (RoIS12-2-AnnexE.odt) is added at the last of specification as a new section named "Annex E: Examples of Conditions."

  • Updated: Mon, 2 Apr 2018 18:08 GMT
  • Attachments:

Dependency among HRI Components should be defined

  • Key: ROIS12-1
  • Legacy Issue Number: 17134
  • Status: closed  
  • 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
  • Disposition: Duplicate or Merged — RoIS 1.2b1
  • Disposition Summary:

    Components' dependency will be addressed in conjunction with simultaneous allocation of multiple components in major update.

    If a component requires several sub components to work, it is desirable such subcomponents are bound automatically when the top-level component is bound. Such a solution (at least internally) requires API extension to bind multiple components at once as discussed in ROIS12-3. This issue is proposed to be merged into ROIS12-3, that is proposed to be deferred to RoIS 2.0 major update.

  • Updated: Mon, 2 Apr 2018 18:08 GMT