Davanum Srinivas' weblog

[WS-ActiveProfile]: The WS-Federation specification defines an integrated model for federating identity, authentication and authorization across different trust realms. This specification defines how the federation model is applied to active requestors such as SOAP applications.

[WS-Addressing]: provides transport-neutral mechanisms to address Web services and messages. Specifically, this specification defines XML elements to identify Web service endpoints and to secure end-to-end endpoint identification in messages.

[WS-Attachments]: defines an abstract model for SOAP attachments and based on this model defines a mechanism for encapsulating a SOAP message and zero or more attachments in a DIME message.

[WS-Authorization]: will describe how to manage authorization data and authorization policies.

[WS-AtomicTransaction]: provides the definition of the atomic transaction coordination type that is to be used with the extensible coordination framework described in the WS-Coordination specification.

[WS-BusinessActivity]: defines a specific set of protocols that plug into the WS-Coordination model to implement long-running, compensation-based transaction protocols.

[WS-Coordination]: describes an extensible framework for providing protocols that coordinate the actions of distributed applications.

[WS-Federation]: will describe how to manage and broker the trust relationships in a heterogeneous federated environment including support for federated identities.

[WS-Inspection]: is an XML format for assisting in the inspection of a site for available services.

[WS-Manageability]: introduces the general concepts of a manageability model in terms of manageability topics and the aspects used to define them.

[WS-PassiveProfile] describes how the cross trust realm identity, authentication and authorization federation mechanisms defined in WS-Federation can be utilized used by passive requestors such as Web browsers to provide Identity Services. Passive requesters of this profile are limited to the HTTP protocol.

[WS-EndpointResolution]: A set of Web service mechanisms that support selecting a specific endpoint for an operation or message from a set of allowed candidates. This is particularly useful in server farms and mobile environments.

[WS-MetadataExchange] specification enables a service to provide metadata to others through a Web services interface.

[WS-Policy]: will describe the capabilities and constraints of the security (and other business) policies on intermediaries and endpoints (e.g. required security tokens, supported encryption algorithms, privacy rules).

[WS-PolicyAssertions]: provides an initial set of assertions to address some common needs of Web Services applications.

[WS-PolicyAttachment]: defines an abstract policy model and an XML policy expression grammar for making policy assertions. This specification defines a general-purpose mechanism for associating policy expressions with subjects.

[WS-Provisioning]: describes the APIs and schemas necessary to facilitate interoperability between provisioning systems and to allow software vendors to provide provisioning facilities in a consistent way.

[WS-Privacy]: will describe a model for how Web services and requesters state privacy preferences and organizational privacy practice statements.

[WS-Referral]: is a SOAP-based, stateless protocol for inserting, deleting, and querying routing entries in a SOAP router.

[WS-ReliableMessaging]: describes a protocol that allows messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures.

[WS-Routing]: is a SOAP-based, stateless protocol for exchanging one-way SOAP messages from an initial sender to the ultimate receiver, potentially via a set of intermediaries.

[WS-Referral]: Web Services Referral Protocol (WS-Referral) is a SOAP-based, stateless protocol for inserting, deleting, and querying routing entries in a SOAP router

[WS-SecureConversation]: will describe how to manage and authenticate message exchanges between parties including security context exchange and establishing and deriving session keys.

[WS-Security]: describes how to attach signature and encryption headers to SOAP messages. In addition, it describes how to attach security tokens, including binary security tokens such as X.509 certificates and Kerberos tickets, to messages.

[WS-SecurityPolicy]: builds on WS-Security by defining how to describe policies related to various features defined in the WS-Security specification, and is therefore considered an "addendum" to the WS-Security specification

[WS-Transaction]: defines what constitutes a transaction and what will determine when it has completed successfully.

[WS-TransmissionControl]: A set of constructs for controlling the exchange of messages between services to improve reliability by preventing message loss due to service unavailability, overloading queues, and other causes.

[WS-Trust]: will describe a framework for trust models that enables Web services to securely interoperate.