1 / 3

Desktop Profile

Desktop Profile. System (I.e. B2B, cloud, social..). 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

reese-byers
Download Presentation

Desktop Profile

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Desktop Profile System (I.e. B2B, cloud, social..) • 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, Web Profile RIA FAT Hybrid 1 3 2 4 5 6 7 8 Mobile Profile Inter-operability Communications Profile Service Framework Event Notification Life Cycle Mgmt Security Policy Identity Management Presentation and Encoding Service Facades Event Driven Architecture Component Service Tier Telecom Management SOA Profile Abstraction SIP, CSTA…other

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

  3. Use Case and Definitions • 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. • 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. • 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”. • 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. • 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. • 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. • 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. • Universal Communications Profile, related to the specification of a possible common profile for universal interoperability across domains.

More Related