1. Arbitrary and Cascading Operations
CL2 Issues #7 & #8

2. The Problem
There is no way to know how the top-level operation is intended to map to operations on content elements and requisite packages.
The semantics of features is problematic if an SDD supports multiple operations.

3. Proposed Solution:
Limit CompositeInstallable elements to a single top-level operation.
Restriction does not apply to CL1 SDDs. SDDs without a CompositeInstallable support all operations for which a corresponding artifact is defined.
Individual content elements can support any operation and any artifact type needed to accomplish the top-level operation.
All artifacts in scope for a particular deployment are used.
This may be a temporary v1 restriction.
Add operation attribute to ReferencedPackageType to identify the operation that should be applied to the package if it contains a CL1 SDD. If referenced package has a CL2 SDD, the single top-level operation is the one that will be used.

4. Schema changes: Add operation attribute to CompositeInstallableType
<attribute name="operation" type="sdd-dd:OperationApplicabilityType" use="required"/>
Add operation attribute to ReferencedPackageType
<attribute name="operation" type="sdd-dd:OperationApplicabilityType" use=“optional"/>
Interpretation:
If the referenced package element points to an SDD with a CompositeInstallable element, the operation identified in the CompositeInstallable is performed if the referenced package is in scope.
If the referenced package element points to an SDD without a CompositeInstallable, and
Operation is specified by the referenced package, then perform that operation
Operation is not specified by the referenced package, then perform the top-level operation of the referencing SDD.