OTS11 — ChildBegin on a subordinate node

The final adopted specification of the Activity Service specification
states, in section 2.2.1:
"If the parent of a sub-Activity is not a root Activity (i.e., it is an
interposed subordinate)
then the distribution of the ChildLifetime signals is delegated upstream to
the superior
ActivityCoordinator."

Since no service context would flow on a delegated process_signal_set
request to an
upstream ActivityCoordinator, then any Action registered in the upstream
node with an
interest in the ChildLifetime SignalSet would not be able to determine the
identity
of the child activity begun.

Any solution to this problem needs to interoperable rather than dependent
on implementation
since the upstream ActivityCoordinator could be part of a foreign domain.

2 potential solutions are:
1. New methods on the ActivityCoordinator and and SignalSet interfaces:
ActivityCoordinator::process_signal_set_with_data(in string ssName,
in CompletionStatus cs, in any signalData);
and
SignalSet::get_signal_with_data(inout boolean lastSignal, in any signalData);

The subordinate Coordinator-Action could build the ActivityInformation any
required by the ChildLifetime SignalSet and pass this in the signalData on
the upstream process_signal_set_with_data.
2. Change the specification to state that ChildLifetime signals are distributed
from the node in which the child Activity begins. In the case where there are
Actions registered with the parent in an upstream node on which the child does
not execute, then these Actions are not informed of the event.

(2) is simpler but compromises the ideal of location transparency.

see above