If the maximum running time of the workspace has expired and the workspace is shutdown, this element triggers the kind of shutdown that should happen. Currently Serialize is not implemented. If this element is missing from WorkspaceDeployment, Normal is assumed. If Trash is chosen, the images will be removed and there will be no un-propagation step. This is useful when the client doesn't need any result or state files on the image after it has run (this could be used in conjunction with a read-only site image repository for example). Wrapper for CPU resource specification. CPUPercentage, IndividualPhysicalMemory, and IndividualCPUCount are in practice all computed as a function of this CPU entity. CPU requested/granted is not necessarily just an architecture plus speed. For most accurate negotiation, JSDL extension points of CPUArchitecture_Type (the type of jsdl:CPUArchitecture listed below) could be used to specify exact chip models or properties. The duration request/grant of a workspace deployment could be highly dependent on combination of all information including CPU's cache sizes and motherboard's bus, especially in HPC. This is temporary and only advisory. Ultimately this is inferrable from CPU definition. JSDL's IndividualNetworkBandwidth type does not allow separate selections for ingoing and outgoing. jsdl:IndividualNetworkBandwidth is of type jsdl:RangeValue_Type, but we need two. Allocation may be requested by just number of NICs, so bandwidths are optional. This should match what is in definition section for the blank storage. This only specifies blank disk space requested/given.