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.

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