t easing the Web service creation. These frameworks feature a high level view on the Service Delivery Platforms development process and a rapid deployment over different server platforms like Java or .NET. A popular framework for Web 2.0 application is Ruby on Rails. 3.2.5 Key Entity in the WIMS 2.0 SDP The axial concept for convergence within the WIMS 2.0 SDP is the exposure of capabilities through Web-friendly APIs. The entity in charge is the IMS Exposure Layer. There are two aspects for the technical realization of this entity: on one side, the Web-friendly APIs that exposes IMS service capabilities toward Web applica- tions and, on the other side, the internal logic to interwork and interact with the underlying IMS infrastructure in order to execute the functionalities exposed via the API. The IMS Exposure Layer shall implement a gateway adapting the HTTP-based API primitives into SIP and XCAP protocol operations to enable communication between the Web world and the IMS. This mission affects two levels of communi- cation in the telecom side: the signaling plane and the media plane. Wherever pos- sible, both planes need to be adapted from a pure technical perspective, although continuous real-time media is not supposed to be adapted by means of API approaches. This means, that audiovisual media exchange between a Telco end- point and a Web component is not processed through an API and thus, not handled by the IMS Exposure Layer. The following IMS service capabilities constitute a nonexhaustive list of capa- bilities that can be exposed via the IMS Exposure Layer, and thus, the underlying gateway shall be able to communicate with the enabling servers implementing these service capabilities: Presence: An API client might be able to at least subscribe, consult, or modify Presence information for a given user. XDM: to manage lists and contact items in the IMS domain. Instant Messaging both in pager mode as well as session mode. Multimedia Telephony, to provide third-party call ability to Web applica- tions and ca