The choice of the openness of the CES framework is a challenging issue. One side, the cloud provider could make it an closed framework with CES designed and hosted by the cloud provider just like current cloud WS. This would add a huge burden over the cloud provider and also be unfavorable by a significant class of cloud users skeptical about the offthe-shelf model the clouds are following just as it was in PC applications. On the other end of the spectrum, the cloud provider could have an open framework allowing for adding CES following a strict cloud protocol for CES quality and description. This would consequently bring along the defects of open systems. A model in between would be allowing developers to write CES, yet host them in the cloud after some form of cloud provider arbitration. A similar model is the one used by Apple’s App Store which allows developers to develop Apps and upload them to the App store after arbitration from an Apple management entity. This challenge is a large topic to be discussed independently in a following publication. However, for the current paper, adding a new CES through the framework is unspecified whether it is directly by a cloud user, cloud provider or cloud provider on behalf of the cloud user.