Issues for Mailing list of the Robotic Technology Component (RTC) Revision Task Force

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

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 16619: Change relationship between ExecutionContext and LightweightRTC (rtc-rtf)

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.

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

The get_owned_contexts() method shall be removed. RTCs will no longer be able to own ECs, they will only participate in them.

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

Section 5.2.2.2.8 should be removed to reflect the get_owned_contexts() method being removed.

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

The heading "Ownership and Participation" should be changed to "Participation" to reflect the new relationship between LightweightRTObjects and ExecutionContexts.

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

The first paragraph under "Ownership and Participation" should be removed, as LightweightRTObjects will not own ExecutionContexts if other changes are approved.

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

Change "An autonomous RTC" to "An RTC" under "Ownership and Participation".

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

The ExecutionContext will not be owned by a LightweightRTObject, so the "owner" field should be removed from the ExecutionContextProfile structure.

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

Remove the get_owned_contexts() method from the LightweightRTObject interface.

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

Remove "RTObject owner;" from the ExecutionContextProfile struct.

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