obile phone (calendaring, date, etc.). JSR 248 specification, contributed signifi- cantly by Sun Microsystems, is a step toward that direction. To compose richer Telecom applications, one can wrap the device functionality using the SewNet proxy model and make them available to a developer during the composition process. In this case, such "device-side" proxies will not only ease the access to device functionality, but also shield the developer from the heterogeneity of the underlying device itself. SCL on the other hand aims to fill a technology gap in the architecture of cur- rent SDPs in terms of applying transparent and fine-grained service control requirements to next-generation IMS-based service delivery. The focus of SCL has been on processing SIP messages to apply service control. However, in a Web 2.0 domain, SCL might additionally need to process non-SIP (e.g., SOAP) messages generated from a user-driven session. Accordingly, the functionality of SCL can be extended to model such interactions and apply rule-driven blending of Web/ Telecom capabilities. Further to this, the role of SCL could be extended in enrich- ing a range of service delivery scenarios, for example, rich media sessions of a peer- to-peer nature that might otherwise be beyond the control of the service provider. References 1. Telco Web 2.0 Mashups: A New Blueprint for Service Creation. http://www.network mashups.com/docs/ssi_0507.pdf. 2. S. M. D. Chakraborty, S. Goyal, and S. Mukherjea. On the changing face of service composition in Telecom. In Proceedings of MNCNA: Middleware for Next-Generation Converged Networks and Applications, California, 2007. 3. K. Dasgupta, N. Banerjee, and S. Mukherjea. Providing middleware support for the control and co-ordination of Telecom mashups. In Proceedings of MNCNA: Middleware for Next-Generation Converged Networks and Applications, Newport Beach, USA, 2007. 4. Open service access (OSA); Parlay X web services; part 1: Common. 3GPP TS 29.199-01. 5. Web 21c sdk. http://web21c.bt.com/ * http://www.apple