Issues for Mailing list of the Robotic Technology Component (RTC) Revision Task Force
To comment on any of these issues, send email to rtc-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.
List of issues (green=resolved, yellow=pending Board vote, red=unresolved)
Issue 16611: Change on_aborting to ComponentAction::on_aborting in three places in figure 5.5
Issue 16612: Add "reset_component" to the return arrow from the Error states to the Inactive states in all thre RTCs in Figure 5.5
Issue 16613: Change "Large number of components" to "A large number of components".
Issue 16614: Figure 5.33 must clarify the order of notify_connect calls
Issue 16615: Figure 5.34 must clarify the order of notify_disconnect calls
Issue 16616: LightweightRTObject::reset() does not exist in the PIM but is in the IDL
Issue 16617: LightweightRTObject interface is missing the get_context_handle() method
Issue 16618: Missing inheritence in IDL
Issue 16619: Change relationship between ExecutionContext and LightweightRTC
Issue 16620: Remove get_owned_contexts() method from LightweightRTObject
Issue 16621: Remove get_owned_contexts() method from LightweightRTObject (section 5.2.2.2.8)
Issue 16622: Change heading "Ownership and Participation" to "Participation"
Issue 16623: Remove the first paragraph under "Ownership and Participation"
Issue 16624: Change "An autonomous RTC" to "An RTC"
Issue 16625: Remove the "owner" field from the ExecutionContextProfile structure
Issue 16626: Remove the get_owned_contexts() method from the LightweightRTObject interface
Issue 16627: Remove the "owner" member from the ExecutionContextProfile structure
Issue 16629: Add get_context_handle() to the IDL
Issue 16611: Change on_aborting to ComponentAction::on_aborting in three places in figure 5.5 (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary:
In Figure 5.5 on page 14, the three occurrences of "on_aborting" must be prefixed with "ComponentAction::".
Resolution: Update the figure to add “ComponentAction::” to the three occurrences of “on_aborting.”.
Revised Text: see dtc/2011-11-02 page 6
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16612: Add "reset_component" to the return arrow from the Error states to the Inactive states in all thre RTCs in Figure 5.5 (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: The return arrow from the "Error" state in each partition of Figure 5.5 must be labled with "reset_component".
Resolution: Update the figure to add a “reset_component” label to the return arrows from the Error states.
Revised Text: see page 8 of dtc/2011-11-02
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16613: Change "Large number of components" to "A large number of components". (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: Grammatical correction. Change the sentence "Large number of components" to "A large number of components".
Resolution: Update the text.
Revised Text: The first sentence of the final paragraph on page 22:
Large number of components may collaborate tightly within a single node or process.
Shall be edited to read:
A large number of components may collaborate tightly within a single node or process.
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16614: Figure 5.33 must clarify the order of notify_connect calls (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: In Figure 5.33, the notify_connect call to Port1 is not shown. It must be added to clarify that the method is called in the order Port0, Port1, Port2, Port3.
Resolution: Update the figure to add the notify_connect call to Port1, and a call from Port1 to Port2, as well as the corresponding call returns.
Revised Text: see figure 5.33 o page 10 of dtc/2011-11-02
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16615: Figure 5.34 must clarify the order of notify_disconnect calls (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: In Figure 5.34, the notify_disconnect call to Port1 is not shown. It must be added to clarify that the method is called in the order Port0, Port1, Port2, Port3.
Resolution: Update the figure to add the notify_disconnect call to Port1, and a call from Port1 to Port2, as well as the corresponding call returns.
Revised Text: see figure 5.32 on page 11 of dtc/2011-11-02
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16616: LightweightRTObject::reset() does not exist in the PIM but is in the IDL (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: LightweightRTObject::reset() does not exist in the PIM. It was moved to ExecutionContext::reset_component(). This must be reflected in the IDL.
Resolution: Update the IDL in Annex A.
Revised Text: Delete the following line from interface LightweightRTObject:
ReturnCode_t reset();
The new interface is as follows:
interface LightweightRTObject : ComponentAction {
ReturnCode_t initialize();
ReturnCode_t finalize();
boolean is_alive(in ExecutionContext exec_context);
ReturnCode_t exit();
ExecutionContextHandle_t attach_context(
in ExecutionContext exec_context);
ReturnCode_t detach_context(
in ExecutionContextHandle_t exec_handle);
ExecutionContext get_context(
in ExecutionContextHandle_t exec_handle);
ExecutionContextList get_owned_contexts();
ExecutionContextList get_participating_contexts();
};
Note: See also Issue 16617
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16617: LightweightRTObject interface is missing the get_context_handle() method (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: This method is missing from the LightweightRTObject interface:
ExecutionContextHandle_t LightweightRTObject::get_context_handle(in ExecutionContext cxt);
Resolution: Update the IDL in Annex A.
Revised Text: Add the following lines to interface LightweightRTObject:
ExecutionContextHandle_t LightweightRTObject::get_context_handle(in ExecutionContext cxt);
The new interface is as follows:
interface LightweightRTObject : ComponentAction {
ReturnCode_t initialize();
ReturnCode_t finalize();
boolean is_alive(in ExecutionContext exec_context);
ReturnCode_t exit();
ReturnCode_t reset();
ExecutionContextHandle_t attach_context(
in ExecutionContext exec_context);
ReturnCode_t detach_context(
in ExecutionContextHandle_t exec_handle);
ExecutionContext get_context(
in ExecutionContextHandle_t exec_handle);
ExecutionContextList get_owned_contexts();
ExecutionContextList get_participating_contexts();
ExecutionContextHandle_t LightweightRTObject::get_context_handle(in ExecutionContext cxt);
};
Note: See also Issue 16616.
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16618: Missing inheritence in IDL (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: interface DataFlowComponent, interface Fsm, interface FsmParticipant and interface MultiModeObject should all inherit from LightweightRTObject.
Resolution: Update the IDL in Annex A
Revised Text: Change the IDL for the DataFlowComponent, Fsm, FsmParticipant and MultiModeObject interfaces to the following by adding inheritance from LightweightRTObject to each:
interface DataFlowComponent
: LightweightRTObject, DataFlowComponentAction {
};
interface Fsm
: LightweightRTObject {
};
interface FsmParticipant
: LightweightRTObject, FsmParticipantAction {
};
interface MultiModeObject
: LightweightRTObject, ModeCapable, MultiModeComponentAction {
};
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue
Issue 16619: Change relationship between ExecutionContext and LightweightRTC (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: In Figure 5.3, ExecutionContext may be a composite member of a LightweightRTC. This relationship will be removed. RTCs will not own ECs, they will only participate in them.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16620: Remove get_owned_contexts() method from LightweightRTObject (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: The get_owned_contexts() method shall be removed. RTCs will no longer be able to own ECs, they will only participate in them.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16621: Remove get_owned_contexts() method from LightweightRTObject (section 5.2.2.2.8) (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: Section 5.2.2.2.8 should be removed to reflect the get_owned_contexts() method being removed.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16622: Change heading "Ownership and Participation" to "Participation" (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Enhancement
Severity: Minor
Summary: The heading "Ownership and Participation" should be changed to "Participation" to reflect the new relationship between LightweightRTObjects and ExecutionContexts.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16623: Remove the first paragraph under "Ownership and Participation" (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Enhancement
Severity: Minor
Summary: The first paragraph under "Ownership and Participation" should be removed, as LightweightRTObjects will not own ExecutionContexts if other changes are approved.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16624: Change "An autonomous RTC" to "An RTC" (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Enhancement
Severity: Minor
Summary: Change "An autonomous RTC" to "An RTC" under "Ownership and Participation".
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16625: Remove the "owner" field from the ExecutionContextProfile structure (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Enhancement
Severity: Minor
Summary: The ExecutionContext will not be owned by a LightweightRTObject, so the "owner" field should be removed from the ExecutionContextProfile structure.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16626: Remove the get_owned_contexts() method from the LightweightRTObject interface (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Enhancement
Severity: Minor
Summary: Remove the get_owned_contexts() method from the LightweightRTObject interface.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16627: Remove the "owner" member from the ExecutionContextProfile structure (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Enhancement
Severity: Minor
Summary: Remove "RTObject owner;" from the ExecutionContextProfile struct.
Resolution:
Revised Text:
Actions taken:
October 18, 2011: received issue
Discussion: There were two votes for and two votes against making this change. This followed late discussion about whether the change can be done in an RTF or needs to wait for the next major version (2.0) of the specification. Due to the API-breaking change this issue involves and the obvious disagreement about whether it should be done in this RTF, the decision is to defer the change until the next RFP.
Disposition: Deferred
Issue 16629: Add get_context_handle() to the IDL (rtc-rtf)
Click here for this issue's archive.
Source: JARA (Mr. Geoffrey Biggs, Ph.D., geoffrey.biggs(at)aist.go.jp)
Nature: Clarification
Severity: Minor
Summary: The get_context_handle() operation must be added to the IDL to make it complete.
ExecutionContextHandle_t get_context_handle(in ExecutionContext cxt);
Resolution: Disposition: See issue 16617 for disposition
Revised Text:
Actions taken:
October 18, 2011: received issue
April 10, 2012: closed issue