Fig. 5.5, Although it is repeated and emphasized under Error Handling subtitle (on page 15), I propose that the following words "reset_component" be added on the return path from Error[1], Error[2], and Error[3] to Inactive[1], Inactive[2] and Inactive[n] respectively. There is no harm in repeating the same as long as it makes the specification clear to understand.

General Comment: I propose the inclusion of a chapter on "Definitions" of some terms that may not seem obvious to some developers/users. May be it is not a requirement by OMG, but it is the International Practice to define some terms in such a specification.

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.

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.

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.

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.

The return arrow from the "Error" state in each partition of Figure 5.5 must be labled with "reset_component".

Update the figure to add a “reset_component” label to the return arrows from the Error states.

In Figure 5.5 on page 14, the three occurrences of "on_aborting" must be prefixed with "ComponentAction::".

Update the figure to add “ComponentAction::” to the three occurrences of “on_aborting.”.

This method is missing from the LightweightRTObject interface:

ExecutionContextHandle_t LightweightRTObject::get_context_handle(in ExecutionContext cxt);

Update the IDL in Annex A.

LightweightRTObject::reset() does not exist in the PIM. It was moved to ExecutionContext::reset_component(). This must be reflected in the IDL.

Update the IDL in Annex A.

interface DataFlowComponent, interface Fsm, interface FsmParticipant and interface MultiModeObject should all inherit from LightweightRTObject.

Update the IDL in Annex A

Grammatical correction. Change the sentence "Large number of components" to "A large number of components".

Update the text.

The get_context_handle() operation must be added to the IDL to make it complete.

ExecutionContextHandle_t get_context_handle(in ExecutionContext cxt);

Disposition: See issue 16617 for disposition

Remove "RTObject owner;" from the ExecutionContextProfile struct.

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

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

Remove the get_owned_contexts() method from the LightweightRTObject interface.

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

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.

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

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

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