1. Desktop Profile Web Profile Mobile Profile Communications Profile Communications Profile Service Framework Abstraction Identity Management Policy Life Cycle Mgmt Telecom Management SOA Profile Security Component Service Tier Component Service Tier Event Driven Architecture Event Driven Architecture Presentation and Encoding Event Notification Service Facades SIP, CSTA…other RIA FAT Hybrid System (I.e. B2B, cloud, social..) System (I.e. B2B, cloud, social..) 6 5 4 2 3 1 Inter-operability 1.Transaction Endpoints Specification 2. Notification 3. SOAP Protocol 4. SAML Token Correlation 5. User-ID Forwarding 6. Services exposing Management Interface 7. Metadata in support of Service Lifecycle Management 8. Universal Communications Profile, 7 8

2. Desktop Profile Web Profile Mobile Profile Communications Profile Communications Profile SOA Framework Abstraction Identity Management Policy Life Cycle Mgmt Telecom Management SOA Profile Security Component Service Tier Component Service Tier Event Driven Architecture Event Driven Architecture Presentation and Encoding Event Notification Service Facades SIP, CSTA…other RIA FAT Hybrid System (I.e. B2B, cloud, social..) System (I.e. B2B, cloud, social..)

3. Use Case and Definitions 1.Transaction Endpoints Specification, related to a possible issue on the W3C WS-Addressing specification; the necessity to specify the endpoint of a final result of a “process/transaction" (i.e. asynchronous response) result should be sent. 2.Notification, related to a possible issue on the OASIS WS-Notification specification, the necessity to specify for the Provider of a notifications service to specify the endpoint to which the Notification should be sent. 3.SOAP Protocol issue, related on a possible issue on the W3C SOAP specification; the necessity for an “intermediate SOAP node” to also cover the role of “SOAP ultimate receiver node”. 4.SAML Token Correlation, related to a possible issue on the OASIS WS-Security specification; the necessity of enabling “correlation” of a security token to another. 5.User-ID Forwarding, related to a possible issue in the OASIS WS-Security specification; the necessity to define a common means to add two (or more) credentials in one message. 6.Services exposing Management Interface, related to possible issues on the OASIS SOA Reference Model (SOA RM) and SOA Service Component Architecture (SCA) Assembly Model; the necessity to specify more than one service interface for a single SOA service. 7.Metadata in support of Service Lifecycle Management, related to the possibility to enrich the OASIS SOA Reference Architecture (SOA RA) with metadata necessary for Service Lifecycle Management identified within the TM Forum SDF program. 8.Universal Communications Profile, related to the specification of a possible common profile for universal interoperability across domains.