The definition of BaseBusinessObject declares itself as an event publisher
for objects typically exposed within client applications presenting a
desktops and associated workspaces. If a client is maintaining a cache, the
client, following disconnection from and reconnection to an event channel
cannot establish if its internal cache is consistent with a source. As such
a client is obliged to rebuild a cache following any disconnection from the
event supplier creating an unacceptable performance degradation. Operations
are require to expose creation and modification timestamps related to the
event producer enabling client verification of creation and last
modification dates.

The specification of BaseBusinessObject includes inheritance of the
CosNotifyComm::StructuredPushConsumer and StructuredPushSupplier interfaces.
The semantics of StructuredPushSupplier implies association to a single
StructuredProxyPushConsumer, however, the BaseBusinessObject interface is
intended to support multiple concurrent consumers from potentially different
business domains without mandating nor excluding the use of Notification
channels as an implementation mechanisms. To enable the documented
behaviour an explicit factory operation is required through which a
StructuredPushSupplier reference can be exposed for a given consumer.

The Task and Session Specification defines a "contains" relationship between
a Workspace and AbstractResources contained by the workspace. An
AbstractResources may be contained within many Workspaces and Workspaces are
themselves AbstractResources. However, the semantics of "contains" with
respect to strong or weak aggregation are ambiguous. Achievement of
consistent behaviour of lifecycle operations (remove, copy and move) across
implementations requires explicit distinction between strong containment as
opposed to weak containment. Strong containment is required in order to
associate a resource with 0 to 1 principal workspace. Under strong
containment, the removal of a containing workspace implies the removal of
strongly contained resources. Under weak containment the removal of a
containing workspace implies the removal of "contained_by" relationships
held by contained resources towards the workspace. Under strong containment,
it should be illegal for a resource to strongly contain a resource it is
already strongly contained by.

The AbstractResource interface contains an operation called "expand" which
enables client applications to access relationships between resources.
Invocation of expand returns a sequence of iterator instances representing
the extent of a set of relationships, however, the iterator interface does
not expose the size of the extent. This restricts the ability of interactive
client applications dealing with navigation and graphic presentation of
relationship extents.