Robotic Interaction Service Avatar
  1. OMG Specification

Robotic Interaction Service — Closed Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
ROIS12-6 "Platform Specific Model" which is located in the chapter "Platform Independent Model" should be moved to a new section. RoIS 1.1 RoIS 1.2b1 Resolved closed
ROIS12-4 overview Package and UML Class diagram. RoIS 1.0 RoIS 1.2b1 Resolved closed
ROIS12-3 Atomic allocation of multiple HRI Components required RoIS 1.0b1 RoIS 1.2b1 Deferred closed
ROIS12-2 Ambiguous definition of "Condition" RoIS 1.0b1 RoIS 1.2b1 Resolved closed
ROIS12-1 Dependency among HRI Components should be defined RoIS 1.0b1 RoIS 1.2b1 Duplicate or Merged closed
ROIS12-5 "Overview" section is a bit misplaced. RoIS 1.0 RoIS 1.2b1 Resolved closed
ROIS11-29 overview Package and UML Class diagram. RoIS 1.0 RoIS 1.1 Deferred closed
ROIS11-28 "Overview" section is a bit misplaced. RoIS 1.0 RoIS 1.1 Deferred closed
ROIS11-3 Atomic allocation of multiple HRI Components required RoIS 1.0b1 RoIS 1.1 Deferred closed
ROIS11-2 Ambiguous definition of "Condition" RoIS 1.0b1 RoIS 1.1 Deferred closed
ROIS11-1 Dependency among HRI Components should be defined RoIS 1.0b1 RoIS 1.1 Deferred closed
ROIS11-23 CORBA IDL needs to be corrected to be conformant with CORBA standard RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-22 C++ headers need to be corrected RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-4 "operable time" in System Information should be modified to deal with multiple time spans RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-21 Change cited version of RLS from 1.0 to 1.1 RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-6 Definition of timestamp refers to non normative document [W3C-DT]. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-40 CORBA PSM fails to compile. It should implement data types imported from RLS 1.1. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-39 C++ PSM should implement data types imported from RLS 1.1. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-41 Add an organization to Acknowledgment. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-32 Component Profiles are not valid against the XML Schema dtc/15-06-11.xsd. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-31 C++/CORBA PSMs lack Include protection. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-30 Empty comments in XML files should be removed. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-27 Reference to UML specification should be updated from 2.3 to 2.4.1. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-19 XML Profiles of Basic Component is missing. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-16 Proposal to add a new example of WheelChairComponent as C.4. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-13 DateTime in User-defined HRI Component should refer to [ISO8601]. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-11 inconsistent use of vector and List in C++ PSM. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS11-9 Description of a parameter is missing. RoIS 1.0 RoIS 1.1 Resolved closed
ROIS-6 Order of HRI Engine and Service Application should be changed RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-5 Definition of HRI Engine is ambiguous RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-8 Parameter definitions for Error Message RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-7 Relationship with RTC and ROS RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-9 Occurrence of sub component for Component Profile RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-4 Command Result Message definitions (rois-ftf) RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-27 Schematic diagram of RoIS Framework (Figure 5, in Section 7.2) requires an update RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-25 Copyright holders should be modified RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-26 Two types of parameters to be distinguished RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-13 Parameters for Localization component RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-12 Parameters for System Information component RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-24 "Supported by" in Acknowledgements should be modified RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-23 Table number missing in 7.6 RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-11 RoIS_Common in System Information component RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-10 Parameter in HRI Engine Profile RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-20 Unifying Notation of Terms RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-19 Miss speling in Table 7.2 RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-15 Additional Normative References RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-14 Parameters for Speech Synthesis component RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-17 Wrong Expression RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-16 Notification of Profile change RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-21 Complex definition of "Command Unit List" RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-22 General System Message Class should be defined RoIS 1.0b1 RoIS 1.0 Resolved closed
ROIS-18 Condition for identifying message RoIS 1.0b1 RoIS 1.0 Resolved closed

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 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

"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: ROIS11-29
  • 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: Deferred — RoIS 1.1
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 12 Jul 2016 14:53 GMT

"Overview" section is a bit misplaced.

  • Key: ROIS11-28
  • 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: Deferred — RoIS 1.1
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 12 Jul 2016 14:53 GMT

Atomic allocation of multiple HRI Components required

  • Key: ROIS11-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.1
  • Disposition Summary:

    This issue should be deferred to the future revision.

    This issue is not discussed thoroughly and there are several opinions to resolve this so I propose to defer the issue to the future revision.

  • Updated: Tue, 12 Jul 2016 14:53 GMT

Ambiguous definition of "Condition"

  • Key: ROIS11-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: Deferred — RoIS 1.1
  • Disposition Summary:

    This issue should be deferred to the future revision.

    This issue is not discussed thoroughly and there are several opinions to resolve this so I propose to defer the issue to the future revision.

  • Updated: Tue, 12 Jul 2016 14:53 GMT

Dependency among HRI Components should be defined

  • Key: ROIS11-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: Deferred — RoIS 1.1
  • Disposition Summary:

    This issue should be deferred to the future revision.

    This issue is not discussed thoroughly and there are several opinions to resolve this. Though a resolution is partially described in a new example of Wheel Chair Robot in C.4 but
    I propose to defer the issue to the future revision.

  • Updated: Tue, 12 Jul 2016 14:53 GMT

CORBA IDL needs to be corrected to be conformant with CORBA standard

  • Key: ROIS11-23
  • Status: closed  
  • Source: AIST ( Toshio Hori)
  • Summary:

    There are several errors in CORBA IDL in Section 7.7.2 which should be corrected.

    1. missing typedefs such as DateTime and Integer.
    2. several TYPOS such as extra semicolons and commas in typedefs and parameter list.

    These should be corrected to conform to CORBA standard.

  • Reported: RoIS 1.0 — Thu, 18 Jun 2015 05:00 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Correct errors in CORBA IDL files

    CORBA PSM (CORBA IDL files) in Section 7.7.2 is corrected as follows:

    1. missing typedefs are added in RoIS_HRI.idl (DateTime and Integer).
    2. There are TYPOs such as extra commas and semicolons, and curly braces are misused which should be parentheses.
  • Updated: Tue, 29 Mar 2016 15:10 GMT

C++ headers need to be corrected

  • Key: ROIS11-22
  • Status: closed  
  • Source: AIST ( Toshio Hori)
  • Summary:

    There are errors in C++ header files which should be corrected.

    1. missing typedefs such as DateTime and Integer.
    2. 'vector' is used without specifying its namespace, which should be 'std::vector'
    3. a header file, RoIS_Person Identification.h, is included in the document twice.
    4. several TYPOs such as extra commas at the end of parameters and misused curly braces which should be parentheses.

    These should be corrected so that the header files can be compiled.

  • Reported: RoIS 1.0 — Thu, 18 Jun 2015 04:53 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Correct errors in C++ headers

    C++ PSM (C++ headers) in Section 7.7.1 is corrected as follows:

    1. missing typedefs are added in RoIS_HRI.h (DateTime and Integer) and RoIS_Service.h (DateTime).
    2. all the occurrences of 'vector' are modified as 'std::vector' to conform to C++ standard namespace.
    3. RoIS_Person_Identification.h is included twice in the document so remove one.
    4. There are TYPOs such as extra commas and semicolons at the end of parameter list, and curly braces are misused which should be parentheses.
  • Updated: Tue, 29 Mar 2016 15:10 GMT

"operable time" in System Information should be modified to deal with multiple time spans

  • Key: ROIS11-4
  • Status: closed  
  • Source: AIST ( Toshio Hori)
  • Summary:

    A field "operable time" in System Information is defined as a single 'Date Time' value in ver.1.0, but service time (i.e. operable time) of a robot system may be described as multiple time spans, such as "9AM-5PM, Mon-Fri and 10AM-5PM, Sat&Sun".
    Single 'Date Time' data type cannot deal with such use case so the data type of this field should be modified.

  • Reported: RoIS 1.0 — Wed, 15 Apr 2015 04:17 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Parameter type of 'operable time' is modified to be a list of DateTime.

    in Type of operable_type is changed to List<DateTime[ISO8601]>.

    Reference to non-normative document [W3C-DT] is changed to [ISO8601] as the normative one.

    1. Description of result 'operable time' in engine_status method in Table 7.37 in Chapter 7.6.1 is modified as follows.
    2. Figure 17 is updated to conform to the description.
  • Updated: Tue, 29 Mar 2016 15:10 GMT
  • Attachments:

Change cited version of RLS from 1.0 to 1.1

  • Key: ROIS11-21
  • Status: closed  
  • Source: AIST ( Toshio Hori)
  • Summary:

    Robotic Localization Service (RLS) was revised after RoIS 1.0 was submitted so its reference is changed from 1.0 to 1.1.
    Reference URLs in C++ header files are also changed accordingly.

  • Reported: RoIS 1.0 — Thu, 18 Jun 2015 04:44 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Reference to RLS including C++ header files are updated from 1.0 to 1.1

    To follow the revision of Robotic Localization Service (RLS), normative reference and reference URLs in C++ header files are updated.

    1. In Section 3.1 (Normative References), version number is changed to 1.1 and its year is changed to 2012.
    2. In Section 7.7.1 (C++ PSM), all the occurrences of reference URLs are changed to point to 'http://www.omg.org/spec/RLS/20110501/Architecture.hpp'
  • Updated: Tue, 29 Mar 2016 15:10 GMT

Definition of timestamp refers to non normative document [W3C-DT].

  • Key: ROIS11-6
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    Definition of timestamp refers to non normative document [W3C-DT] in section 7.6.
    It should refer to [ISO8601].

  • Reported: RoIS 1.0 — Fri, 15 May 2015 08:43 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    *Type 'DateTime [W3C-DT]' changed to 'DateTime[ISO8601]'. *

    Definition of time stamp refers to non normative document [W3C-DT] in section 7.4.2.2, 7.4.3.4, 7.4.3.6 and through out the section 7.6. It should refer to [ISO8601].

    This change affects: Table 7.6 (in section 7.4.2.2), Table 7.21 (in section 7.4.3.4), Table 7.23 (in section 7.4.3.6) and Table 7.37 through 7.46 (in section 7.6).

  • Updated: Tue, 29 Mar 2016 15:10 GMT

CORBA PSM fails to compile. It should implement data types imported from RLS 1.1.

  • Key: ROIS11-40
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    CORBA PSM fails to compile. It lacks proper typedef to imported types. It does not include RLS (and ISO19XXX) definitions as well as C++ PSM.

  • Reported: RoIS 1.0 — Mon, 7 Dec 2015 23:45 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    CORBA PSM fails to compile. It should implement data types imported from RLS 1.1.

    Just as same as C++ PSM (issue ROIS11-39), CORBA PSM does not contain definitions of RLS (and ISO19XXX) related elements. The IDL files also lacks proper typedef to imported types.
    As a solution RLS related element is implemented in RoIS_HRI.idl. Other IDL files modified to include RoIS_Common.idl (and indirectly RoIS_HRI.idl) to import corresponding types and then typedef definitions are added in each module.

    RLS related definitions are included in five files: RoIS_Face_Localization.idl, RoIS_Navigation.idl, RoIS_Person_Localization.idl, RoIS_Sound_Localization.idl, RoIS_System_Information.idl.
    Typedef of 'RoLo_DataSeq' is added to each module to define corresponding variables.
    In addition, as a trivial revision, unnecessary 'public' label is removed from RoIS_Person_Identification.idl.

  • Updated: Tue, 29 Mar 2016 15:10 GMT
  • Attachments:

C++ PSM should implement data types imported from RLS 1.1.

  • Key: ROIS11-39
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    Even though RLS machine readable files are imported, RoIS C++ PSM is not able to compile because it does not contain ISO19XXX definitions.

  • Reported: RoIS 1.0 — Mon, 7 Dec 2015 23:37 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    C++ PSM should implement data types imported from RLS 1.1.

    There are no definition of RLS 1.1 related elements in RoIS 1.1 C++ PSM. The machine consumable files are therefore incomplete to be compiled. Even though RLS machine readable files are imported, they does not implement ISO19XXX definitions.
    As a possible and concise solution, the RLS-related definition(s) are implemented in RoIS_HRI.hpp, which is included by ALL other header files.

    In addition to this issue, editorial fixes to RoIS11-31 are also included in the attachment file. #ifndef, #define directives were capitalized so modified them into lower-case.

  • Updated: Tue, 29 Mar 2016 15:10 GMT
  • Attachments:

Add an organization to Acknowledgment.

  • Key: ROIS11-41
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    Since the contribution from ATR was done under a research project of Ministry of Internal Affairs and Communication, Japan, both ATR and MIC should be listed in the supported by part of Acknowledgment.

  • Reported: RoIS 1.0 — Tue, 8 Dec 2015 00:01 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Add an organization to Acknowledgment.

    Since the contribution from ATR was done under a research project of Ministry of Internal Affairs and Communications, Japan, both ATR and MIC should be listed in the supported by part of Acknowledgment.

  • Updated: Tue, 29 Mar 2016 15:10 GMT

Component Profiles are not valid against the XML Schema dtc/15-06-11.xsd.

  • Key: ROIS11-32
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    When validating FaceDetection.xml against the XML Schema dtc/15-06-11.xsd, a list of errors are reported.

    • Attribute 'id' must appear on element 'rois:HRIComponentProfile'.
    • Attribute 'codeSpace' must appear on element 'gml: identifier'.
    • 'urn:x-rois:def:Component:OMG::RoISCommon' is not a valid name for 'NCName'.
    • The value 'urn:x-rois:def:Component:OMG::RoISCommon' of element 'rois:SubComponentProifle' is not valid.
    • Cannot resolve 'rois:EventDetailMessageProfileType' to a type definition for element 'rois:MessageProfile'.
  • Reported: RoIS 1.0 — Sat, 7 Nov 2015 07:32 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Component Profiles are not valid against the XML Schema dtc/15-06-11.xsd.

    When validating FaceDetection.xml against the XML Schema dtc/15-06-11.xsd, a list of errors are reported.

    • Attribute 'id' must appear on element 'rois:HRIComponentProfile'.
    • Attribute 'codeSpace' must appear on element 'gml: identifier'.
    • 'urn:x-rois:def:Component:OMG::RoISCommon' is not a valid name for 'NCName'.
    • The value 'urn:x-rois:def:Component:OMG::RoISCommon' of element 'rois:SubComponentProifle' is not valid.
    • Cannot resolve 'rois:EventDetailMessageProfileType' to a type definition for element 'rois:MessageProfile'.

    The section 7.7.3 XML PSM is newlly added in this RTF according to the issue RoIS11-19. Since this issue is also applied to the newly added section, the modifications do not appear in the specification changebar file.

  • Updated: Tue, 29 Mar 2016 15:10 GMT
  • Attachments:

C++/CORBA PSMs lack Include protection.

  • Key: ROIS11-31
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    The set of C++ header files included lack proper include protection. [From a procedural point of view this is considered as an editorial correction since their technical content is identical with the files resulting from the revision process.]

    Also, each C++ header specifies its own namespace, which reflects the name of the header. While this is not wrong, it would be advisable to make those namespaces more unique, for example with a “rois” prefix, or enclose them within an outer rois namespace. [this is a suggestion for the future and not an error in the current revision]

  • Reported: RoIS 1.0 — Sat, 7 Nov 2015 07:17 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    C++/CORBA PSMs lack Include protection.

    The set of C++ header files included lack proper include protection. From a procedural point of view this is considered as an editorial correction since their technical content is identical with the files resulting from the revision process.

  • Updated: Tue, 29 Mar 2016 15:10 GMT

Empty comments in XML files should be removed.

  • Key: ROIS11-30
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    In RoISCommon.xml (and other xml files) are empty comments for "Event Message", "Error Message" and "Parameter". [This is not per se wrong but cosmetically not so pleasing. If you choose to remove them, that would be editorial]

  • Reported: RoIS 1.0 — Sat, 7 Nov 2015 07:11 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Empty comments in XML files should be removed.

    In RoISCommon.xml (and other xml files) are empty comments for "Event Message", "Error Message" and "Parameter". This is not per se wrong but cosmetically not so pleasing. Removal of them would be editorial.

    The section 7.7.3 XML PSM is newlly added in this RTF according to the issue RoIS11-19. Since this issue is also applied to the newly added section, the modifications do not appear in the specification changebar file.

  • Updated: Tue, 29 Mar 2016 15:10 GMT

Reference to UML specification should be updated from 2.3 to 2.4.1.

  • Key: ROIS11-27
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    RoIS 1.0 refers to UML 2.3 as a normative reference. It should refer to UML 2.4.1 (dated version 20110701).

  • Reported: RoIS 1.0 — Sat, 7 Nov 2015 06:53 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Reference to UML specification should be updated from 2.3 to 2.4.1.

    RoIS 1.0 refers to UML 2.3 as a normative reference. It should refer to UML 2.4.1 (dated version 20110701).

  • Updated: Tue, 29 Mar 2016 15:10 GMT

XML Profiles of Basic Component is missing.

  • Key: ROIS11-19
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    XML Profiles of Basic Component is missing. To be added as a part of PSM as well as C++/CORBA PSM.

  • Reported: RoIS 1.0 — Sun, 17 May 2015 00:37 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Add a section of XML Component Profile as a PSM.

    In RoIS 1.0, section 7.7.3 describes XML schema definition of HRI Component Profile but examples of Component Profiles of Basic HRI Component in XML is missing. (partly shown in Appendix A.)

    Here I propose to insert a new section of 'XML PSM' as section 7.7.3 with attached XML profiles, as well as C++/CORBA PSM in the previous sections.

    Rename the current 7.7.3 as '7.7.4 XML PSM of Component Profile Schema.'

  • Updated: Tue, 29 Mar 2016 15:10 GMT
  • Attachments:

Proposal to add a new example of WheelChairComponent as C.4.

  • Key: ROIS11-16
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    As a new example of User-defined HRI Component, WheelChairComponent was proposed in 2014 Boston meeting and it was suitable to be added as section C.4.

  • Reported: RoIS 1.0 — Sat, 16 May 2015 22:59 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    A new example of WheelChairComponent was added as section C.4.

    A new example of WheelChairRobot component that extends existing Navigation component was proposed as Section C.4.

  • Updated: Tue, 29 Mar 2016 15:10 GMT
  • Attachments:

DateTime in User-defined HRI Component should refer to [ISO8601].

  • Key: ROIS11-13
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    As well as the fix of DateTime in Section 7.6, DateTime should refer to [ISO8601] instead of [W3C-DT] through Section C.

  • Reported: RoIS 1.0 — Sat, 16 May 2015 22:13 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    DateTime modified through Section C.

    Definitions of time stamp refers to non normative document [W3C-DT] are modified to refer to [ISO8601].

    In Table C.1, definitions of parameter timestamp, timestamp_speech_start and timestamp_speech_end were modified.
    Other timestamps in Table C.4 and Table C.5 were also modified.

  • Updated: Tue, 29 Mar 2016 15:10 GMT

inconsistent use of vector and List in C++ PSM.

  • Key: ROIS11-11
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    In the definition of Move component in C++ PSM, List is used instead of vector.
    Other part in the C++ PSM consistently use vector and there seems no reason to use List.

  • Reported: RoIS 1.0 — Sat, 16 May 2015 16:44 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Use of List in C++ PSM is modified to vector.

    In the C++ PSM, use vector consistently instead of List.
    Use of List in the definition of Move Component (Move.h) are replaced with vector.

  • Updated: Tue, 29 Mar 2016 15:10 GMT

Description of a parameter is missing.

  • Key: ROIS11-9
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    In the definition of Person Localization component, get_parameter method should return two parameters such as detection threshold and detection interval.
    The former is duplicated and the latter is missing.

  • Reported: RoIS 1.0 — Sat, 16 May 2015 16:03 GMT
  • Disposition: Resolved — RoIS 1.1
  • Disposition Summary:

    Missing parameter 'minimum interval.'

    As result values of get_parameter method of Person Localization component, definition of 'minimum interval' parameter was missing but 'detection threshold' was duplicated.
    A parameter 'minimum interval' should be defined here.

    1. Description of result value 'minimum interval' in get_parameter method in Table 7.39 in Chapter 7.6.3 is modified as follows.
    2. Figure 19 is updated to conform to the description.
  • Updated: Tue, 29 Mar 2016 15:10 GMT
  • Attachments:

Order of HRI Engine and Service Application should be changed

  • Key: ROIS-6
  • Legacy Issue Number: 16894
  • Status: closed  
  • Source: ETRI ( Su Young Chi)
  • Summary:

    In Section 4, Order of HRI Engine and Service Application should be changed

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    All the entries in Terms and Definitions table are arranged alphabetically for simplicity (i.e. not to concern about forward/backward references).

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Definition of HRI Engine is ambiguous

  • Key: ROIS-5
  • Legacy Issue Number: 16893
  • Status: closed  
  • Source: ETRI ( Su Young Chi)
  • Summary:

    In Section 4, definition of HRI Engine is ambiguous

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Parameter definitions for Error Message

  • Key: ROIS-8
  • Legacy Issue Number: 16923
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In 7.4.3 “Message Data”, there is no definition of “Error Message” for “get_error_detail” method, and there is no profile for the result parameters for this message in 7.5.2 7.5.3.

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Resolution for issue #16560 is merged with this issue.
    Add definition of “Error Message” as section 7.4.3.6 and table 7.24.
    Add definition of “Error Detail Message” as section 7.4.3.7 and table 7.25.
    Remove definition of “Event Message Profile” in section 7.5.3 because “Event Message” has no extensible element so it does not require any profile definition.
    Add definition of “Command Result Message Profile”, “Event Detail Message Profile” and “Error Detail Message Profile” in section 7.5.3 as table 7.28, 7.31 and 7.32, respectively.
    Add both message profile classes to Figure 16.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Relationship with RTC and ROS

  • Key: ROIS-7
  • Legacy Issue Number: 16895
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    Relationship with ROS, RTC should be clarified

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Add description in Overview section.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Occurrence of sub component for Component Profile

  • Key: ROIS-9
  • Legacy Issue Number: 16924
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In Table 7.29 “Component Profile”, occurrence of sub_component is N to avoid double definition. For example, if the each sub component include “RoIS_Common”, the main component may include the two same common messages defined in RoIS_Common.
    Therefore, the occurence should be "1".

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    The occurrence of sub_component in HRI Component Profile should be changed as 1.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Command Result Message definitions (rois-ftf)

  • Key: ROIS-4
  • Legacy Issue Number: 16560
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In 7.5.2 there is no profile for the result parameters related with 7.4.3.2

  • Reported: RoIS 1.0b1 — Tue, 20 Sep 2011 04:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Disposition: See issue #16923 for disposition

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Schematic diagram of RoIS Framework (Figure 5, in Section 7.2) requires an update

  • Key: ROIS-27
  • Legacy Issue Number: 17145
  • Status: closed  
  • Source: AIST ( Toshio Hori)
  • Summary:

    Interfaces between the Service Application and HRI Engine had been
    changed when we submitted the revised submission but the diagram had not
    updated upon submission.


    I also found TYPOs and grammatical mistakes so I correct them when I
    submit the FTF report.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Update the diagram to conform to the latest interface structure

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Copyright holders should be modified

  • Key: ROIS-25
  • Legacy Issue Number: 17142
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    ATR and AIST should be removed from copyright holders.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    These organizations were added by misunderstanding. So I propose removing them.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Two types of parameters to be distinguished

  • Key: ROIS-26
  • Legacy Issue Number: 17143
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    There are two types of parameters to be distinguished.
    For example, "language" and "character" in speech synthesis are stable ones,
    but on the other hand, "speech_text" and "volume" are instant ones.
    Engine or Component should re-transmit or interpret them correctly.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Parameters for Localization component

  • Key: ROIS-13
  • Legacy Issue Number: 16928
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In Table 7.36 “person_localization”( and other localization components), parameters of sensing-cycle and/or resolution (minimum position difference which sensor can distinguish) are required. These parameters should be added for (optional ) get_parameter. In addition, Detection-cycle (multiple of sensing-cycle) and Detection-difference (larger than resolution) may be set by set_parameter.

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Add command_method entries for set_parameter and get_parameter to the table 7.36, and also add two parameters detection-threshold and minimum-interval.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Parameters for System Information component

  • Key: ROIS-12
  • Legacy Issue Number: 16927
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In Table 7.34 “System Information”, “robot ref(List<RoIS_Identifier>)” is required for “robot_position”, same as person position data in "Person localization"
    In addition, ”position_data” should be List<Data>.

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    A system may operate several robots in an HRI Engine when the engine has sub HRI Engines or it controls multiple robots. In this case, each robot position should be distinguished by robot's ID (i.e. robot ref). So the ordered lists of robot ref and position are returned as result parameters

  • Updated: Fri, 6 Mar 2015 20:58 GMT

"Supported by" in Acknowledgements should be modified

  • Key: ROIS-24
  • Legacy Issue Number: 17141
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    Miss speling in ATR (missing 'd').
    Several organization should be added such as Korean Robot Association,
    Future Robot Co., Ltd., University of Tokyo an Hitachi.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    As these organizations supported drafting a document, I'd like to add them to the acknowledgment list

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Table number missing in 7.6

  • Key: ROIS-23
  • Legacy Issue Number: 17140
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    In p. 46, line 3, Table number (7.31) is missing.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    TYPO. Should be added.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

RoIS_Common in System Information component

  • Key: ROIS-11
  • Legacy Issue Number: 16926
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In Figure 17, “RoIS_Common” should be removed because System Information component does not include RoIS_Common messages.

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    RoIS_Common should be removed

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Parameter in HRI Engine Profile

  • Key: ROIS-10
  • Legacy Issue Number: 16925
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In Table 7.30 “HRI_Engine_Profile”, parameters of HRI engine is defined in this profile. However, these parameter should be defined in the Component Profile of “System Information Component” for this Engine. Therefore, "parameter" definitions in HRI engine profile should be removed.

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Remove the definition of "parameter" from the profile

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Unifying Notation of Terms

  • Key: ROIS-20
  • Legacy Issue Number: 17136
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    "HRI Engine," "HRI Components" and other terms defined in Section 4 should be
    unified as in the definition table.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    For example, "engine" and "component" are general words while the terms "HRI Engine" and "HRI Component" are specific to this document. To distinguish them, the notation of specific terms will be unified as "HRI Engine," "HRI Component," etc. as in Section 4.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Miss speling in Table 7.2

  • Key: ROIS-19
  • Legacy Issue Number: 17135
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    In Table 7.2 (p.31), the word "Enghien" should be "Engine." (in the "connect" row)

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    TYPO. Should be corrected.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Additional Normative References

  • Key: ROIS-15
  • Legacy Issue Number: 16930
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In 3.1 “Normative References”, ISO19143 (Geographic information - Filter encoding) should be added in the list.
    This reference is referred for QueryExpression.

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    The reference should be added

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Parameters for Speech Synthesis component

  • Key: ROIS-14
  • Legacy Issue Number: 16929
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    In Table 7.44 “speech synthesis”, data type of the argument and result parameter of “character” should be “RoIS_Identifier”.

  • Reported: RoIS 1.0b1 — Tue, 10 Jan 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    "Character" in this context indicates male, female, adult, child, etc. and the available character types depend on a speech synthesis component. To distinguish and designate a character type in Command Message (set_parameter) and Query Message (get_parameter), it is better to use identifiers assigned to each character types than strings.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Wrong Expression

  • Key: ROIS-17
  • Legacy Issue Number: 16932
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    P.23 line 3, “each type of error” should be corrected to “each error”.

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    This is a grammatical error so it should be corrected.
    Revised Text:
    In 7.4.1.1.2 System Error Notification, “each type of error” should be replaced with “each error”.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Notification of Profile change

  • Key: ROIS-16
  • Legacy Issue Number: 16931
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    It is required to consider methods about notification when the engine or component profile changed.
    "receive_error" method is usable for this purpose.
    “PROFILE_CHANGED( tentative name )” should be added in the enumeration of "Error Type" (Table 7.7).
    However, this status is not an error, so "receive_error" and "Error Type" should be renamed

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Disposition: See issue 17139 for disposition

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Complex definition of "Command Unit List"

  • Key: ROIS-21
  • Legacy Issue Number: 17137
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    Implementing "Command Unit List" is very difficult. It should be simplified

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Difficulty of the originally proposed Command Unit List resides in its structure which allows hierarchical parallel command sequences (i.e. parallel command sequences in a parallel command sequence). To simplify the structure, modify it as follows:
    1. Rename CommandUnitList to CommandUnitSequence.
    2. Make CommandUnit class abstract then derive both CommandMessage and ConcurrentCommands from it.
    3. A ConcurrentCommands should hold Branches instead of CommandUnits, then each Branch should hold a sequence of CommandMessages instead of CommandUnit.
    By this change, CommandUnitSequence can hold a sequence of CommandUnit and the units are executed sequentially in their order. Some unit in the sequence can be a ConcurrentCommands-class object which holds Branch-class objects and each Branch is executed in parallel. This resolution prohibits a hierarchical parallel command sequence because the Branch-class object cannot hold any ConcurrentCommands objects.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

General System Message Class should be defined

  • Key: ROIS-22
  • Legacy Issue Number: 17139
  • Status: closed  
  • Source: JARA ( Koji Kamei)
  • Summary:

    The structure of message-related classes should be organized
    concerning issues #16560, #16923 and #16931.

  • Reported: RoIS 1.0b1 — Mon, 20 Feb 2012 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    Merged with #16931.
    Rename the methods receive_event () and receive_error () to notify_event() and notify_exception() respectively.
    Following topics are discussed and decided not to change in this revision. Discussion should be deferred to the next revision.
    • A base class for all Messages can be defined.
    • In PIM, for types of messages should be separated.
    • In Table 7.7, rename the “Error Type” to “RoIS Exception Type.”

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Condition for identifying message

  • Key: ROIS-18
  • Legacy Issue Number: 16933
  • Status: closed  
  • Source: JARA ( Miki Sato)
  • Summary:

    Condition of ”get_error_detail (Table 7.2),” “get_command_result (Table 7.3),” and “get_event_detail (Table 7.5)” can be omitted because these method can identify their message by message_id (such as command_id, event_id and error_id).

  • Reported: RoIS 1.0b1 — Mon, 12 Dec 2011 05:00 GMT
  • Disposition: Resolved — RoIS 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT