Differences between revisions 3 and 4
Revision 3 as of 2006-11-01 14:23:06
Size: 11798
Editor: andreasSpall
Comment:
Revision 4 as of 2009-09-20 22:47:40
Size: 11902
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
[http://www.google.com/search?q=WS-Acknowledgement WS-Acknowledgement]: The WS-Acknowledgement protocol is designed to enable WS-Acknowledgement senders to request explicit acknowledgement from WS-Acknowledgement receivers that a WS-Acknowledgement Request Message has been received. [[http://www.google.com/search?q=WS-Acknowledgement|WS-Acknowledgement]]: The WS-Acknowledgement protocol is designed to enable WS-Acknowledgement senders to request explicit acknowledgement from WS-Acknowledgement receivers that a WS-Acknowledgement Request Message has been received.
Line 5: Line 5:
[http://www.google.com/search?q=WS-ActiveProfile 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. [[http://www.google.com/search?q=WS-ActiveProfile|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.
Line 7: Line 7:
[http://www.google.com/search?q=WS-Addressing 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. [[http://www.google.com/search?q=WS-Addressing|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.
Line 9: Line 9:
[http://www.google.com/search?q=WS-Attachments 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. [[http://www.google.com/search?q=WS-Attachments|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.
Line 11: Line 11:
[http://www.google.com/search?q=WS-Authorization WS-Authorization]: will describe how to manage authorization data and authorization policies. [[http://www.google.com/search?q=WS-Authorization|WS-Authorization]]: will describe how to manage authorization data and authorization policies.
Line 13: Line 13:
[http://www.google.com/search?q=WS-AtomicTransaction 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. [[http://www.google.com/search?q=WS-AtomicTransaction|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.
Line 15: Line 15:
[http://www.google.com/search?q=WS-BusinessActivity WS-BusinessActivity]: defines a specific set of protocols that plug into the WS-Coordination model to implement long-running, compensation-based transaction protocols. [[http://www.google.com/search?q=WS-BusinessActivity|WS-BusinessActivity]]: defines a specific set of protocols that plug into the WS-Coordination model to implement long-running, compensation-based transaction protocols.
Line 17: Line 17:
[http://www.google.com/search?q=WS-CAF WS-CAF]: Composite Application Framework - open, multi-level framework for standard coordination of long-running business processes across multiple, incompatible transaction processing models and architectures. [[http://www.google.com/search?q=WS-CAF|WS-CAF]]: Composite Application Framework - open, multi-level framework for standard coordination of long-running business processes across multiple, incompatible transaction processing models and architectures.
Line 19: Line 19:
[http://www.google.com/search?q=WS-Callback WS-Callback]: used to dynamically specify where to send asynchronous responses to a SOAP request. [[http://www.google.com/search?q=WS-Callback|WS-Callback]]: used to dynamically specify where to send asynchronous responses to a SOAP request.
Line 21: Line 21:
[http://www.google.com/search?q=WS-Coordination WS-Coordination]: describes an extensible framework for providing protocols that coordinate the actions of distributed applications. [[http://www.google.com/search?q=WS-Coordination|WS-Coordination]]: describes an extensible framework for providing protocols that coordinate the actions of distributed applications.
Line 23: Line 23:
[http://www.google.com/search?q=WS-Eventing WS-Eventing]: The WS-Eventing specification "describes a protocol that allows Web services to subscribe to or accept subscriptions for event notification messages." [[http://www.google.com/search?q=WS-Eventing|WS-Eventing]]: The WS-Eventing specification "describes a protocol that allows Web services to subscribe to or accept subscriptions for event notification messages."
Line 25: Line 25:
[http://www.google.com/search?q=WS-Events WS-Events]: The WS-Events specification defines an XML syntax and a set of processing rules for advertising, subscribing, producing and consuming Web Services Events using a push and pull mode. [[http://www.google.com/search?q=WS-Events|WS-Events]]: The WS-Events specification defines an XML syntax and a set of processing rules for advertising, subscribing, producing and consuming Web Services Events using a push and pull mode.
Line 27: Line 27:
[http://www.google.com/search?q=WS-Federation WS-Federation]: will describe how to manage and broker the trust relationships in a heterogeneous federated environment including support for federated identities. [[http://www.google.com/search?q=WS-Federation|WS-Federation]]: will describe how to manage and broker the trust relationships in a heterogeneous federated environment including support for federated identities.
Line 29: Line 29:
[http://www.google.com/search?q=WS-Inspection WS-Inspection]: is an XML format for assisting in the inspection of a site for available services. [[http://www.google.com/search?q=WS-Inspection|WS-Inspection]]: is an XML format for assisting in the inspection of a site for available services.
Line 31: Line 31:
[http://www.google.com/search?q=WS-Manageability WS-Manageability]: introduces the general concepts of a manageability model in terms of manageability topics and the aspects used to define them. [[http://www.google.com/search?q=WS-Manageability|WS-Manageability]]: introduces the general concepts of a manageability model in terms of manageability topics and the aspects used to define them.
Line 33: Line 33:
[http://www.google.com/search?q=WS-ActiveProfile 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. [[http://www.google.com/search?q=WS-ActiveProfile|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.
Line 35: Line 35:
[http://www.google.com/search?q=WS-EndpointResolution 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. [[http://www.google.com/search?q=WS-EndpointResolution|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.
Line 37: Line 37:
[http://www.google.com/search?q=WS-MessageData WS-MessageData] introduces two specific types of message meta-data, MessageId and RefToMessageId. [[http://www.google.com/search?q=WS-MessageData|WS-MessageData]] introduces two specific types of message meta-data, MessageId and RefToMessageId.
Line 39: Line 39:
[http://www.google.com/search?q=WS-MetadataExchange WS-MetadataExchange] specification enables a service to provide metadata to others through a Web services interface. [[http://www.google.com/search?q=WS-MetadataExchange|WS-MetadataExchange]] specification enables a service to provide metadata to others through a Web services interface.
Line 41: Line 41:
[http://www.google.com/search?q=WS-Policy 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). [[http://www.google.com/search?q=WS-Policy|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).
Line 43: Line 43:
[http://www.google.com/search?q=WS-PolicyAssertions WS-PolicyAssertions]: provides an initial set of assertions to address some common needs of Web Services applications. [[http://www.google.com/search?q=WS-PolicyAssertions|WS-PolicyAssertions]]: provides an initial set of assertions to address some common needs of Web Services applications.
Line 45: Line 45:
[http://www.google.com/search?q=WS-PolicyAttachment 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. [[http://www.google.com/search?q=WS-PolicyAttachment|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.
Line 47: Line 47:
[http://www.google.com/search?q=WS-Provisioning 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. [[http://www.google.com/search?q=WS-Provisioning|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.
Line 49: Line 49:
[http://www.google.com/search?q=WS-Privacy WS-Privacy]: will describe a model for how Web services and requesters state privacy preferences and organizational privacy practice statements. [[http://www.google.com/search?q=WS-Privacy|WS-Privacy]]: will describe a model for how Web services and requesters state privacy preferences and organizational privacy practice statements.
Line 51: Line 51:
[http://www.google.com/search?q=WS-Referral 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 [[http://www.google.com/search?q=WS-Referral|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
Line 53: Line 53:
[http://www.google.com/search?q=WS-Reliability WS-Reliability]: is a SOAP-based protocol for exchanging SOAP messages with guaranteed delivery, no duplicates, and guaranteed message ordering. [[http://www.google.com/search?q=WS-Reliability|WS-Reliability]]: is a SOAP-based protocol for exchanging SOAP messages with guaranteed delivery, no duplicates, and guaranteed message ordering.
Line 55: Line 55:
[http://www.google.com/search?q=WS-ReliableMessaging 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. [[http://www.google.com/search?q=WS-ReliableMessaging|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.
Line 57: Line 57:
[http://www.google.com/search?q=WS-Routing 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. [[http://www.google.com/search?q=WS-Routing|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.
Line 59: Line 59:
[http://www.google.com/search?q=WS-SecureConversation WS-SecureConversation]: will describe how to manage and authenticate message exchanges between parties including security context exchange and establishing and deriving session keys. [[http://www.google.com/search?q=WS-SecureConversation|WS-SecureConversation]]: will describe how to manage and authenticate message exchanges between parties including security context exchange and establishing and deriving session keys.
Line 61: Line 61:
[http://www.google.com/search?q=WS-Security 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. [[http://www.google.com/search?q=WS-Security|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.
Line 63: Line 63:
[http://www.google.com/search?q=WS-SecurityPolicy 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 [[http://www.google.com/search?q=WS-SecurityPolicy|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
Line 65: Line 65:
[http://www.google.com/search?q=WS-Transaction WS-Transaction]: defines what constitutes a transaction and what will determine when it has completed successfully. [[http://www.google.com/search?q=WS-Transaction|WS-Transaction]]: defines what constitutes a transaction and what will determine when it has completed successfully.
Line 67: Line 67:
[http://www.google.com/search?q=WS-TransmissionControl 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. [[http://www.google.com/search?q=WS-TransmissionControl|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.
Line 69: Line 69:
[http://www.google.com/search?q=WS-Trust WS-Trust]: will describe a framework for trust models that enables Web services to securely interoperate. [[http://www.google.com/search?q=WS-Trust|WS-Trust]]: will describe a framework for trust models that enables Web services to securely interoperate.
Line 71: Line 71:
[http://www.google.com/search?q=WSMF WSMF]: The Web Services Management Framework (WSMF) is a logical architecture [[http://www.google.com/search?q=WSMF|WSMF]]: The Web Services Management Framework (WSMF) is a logical architecture
Line 74: Line 74:
[http://www.google.com/search?q=WSDM WSDM]: The purpose of this TC is to define web services management, including [[http://www.google.com/search?q=WSDM|WSDM]]: The purpose of this TC is to define web services management, including
Line 79: Line 79:
[http://www.google.com/search?q=WSRF WSRF]: The WS-Resource Framework is a set of specifications that provide a [[http://www.google.com/search?q=WSRF|WSRF]]: The WS-Resource Framework is a set of specifications that provide a
Line 85: Line 85:
[http://www.google.com/search?q=WS-Notification WS-Notification]: WS-Notification (WSN) is a set of specifications that provide support for [[http://www.google.com/search?q=WS-Notification|WS-Notification]]: WS-Notification (WSN) is a set of specifications that provide support for
Line 89: Line 89:
[http://www.google.com/search?q=SOAP+1.1 SOAP 1.1]: SOAP 1.1 is a lightweight protocol for exchange of information in a decentralized, distributed environment. [[http://www.google.com/search?q=SOAP+1.1|SOAP 1.1]]: SOAP 1.1 is a lightweight protocol for exchange of information in a decentralized, distributed environment.
Line 91: Line 91:
[http://www.google.com/search?q=SOAP+1.2 SOAP 1.2]: SOAP 1.2 is the latest version of SOAP and provides the definition of the XML-based information which can be used for exchanging structured and typed information between peers in a decentralized, distributed environment. [[http://www.google.com/search?q=SOAP+1.2|SOAP 1.2]]: SOAP 1.2 is the latest version of SOAP and provides the definition of the XML-based information which can be used for exchanging structured and typed information between peers in a decentralized, distributed environment.
Line 93: Line 93:
[http://www.google.com/search?q=WSDL+1.1 WSDL 1.1]: WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. [[http://www.google.com/search?q=WSDL+1.1|WSDL 1.1]]: WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.
Line 95: Line 95:
[http://www.google.com/search?q=WSDL+2.0 WSDL 2.0]: WSDL 2.0 (formerly known as 1.2) is the latest version of WSDL [[http://www.google.com/search?q=WSDL+2.0|WSDL 2.0]]: WSDL 2.0 (formerly known as 1.2) is the latest version of WSDL
Line 97: Line 97:
[http://www.google.com/search?q=UDDI+2.0 UDDI 2.0]: Universal Description, Discovery and Integration, or UDDI, is the name of a group of web-based registries that expose information about a business or other entity[2] and its technical interfaces (or API’s). [[http://www.google.com/search?q=UDDI+2.0|UDDI 2.0]]: Universal Description, Discovery and Integration, or UDDI, is the name of a group of web-based registries that expose information about a business or other entity[2] and its technical interfaces (or API’s).
Line 99: Line 99:
[http://www.google.com/search?q=UDDI+3.0 UDDI 3.0]: The UDDI Version 3.0 Specification describes the Web services, data structures and behaviors of all instances of a UDDI registry. [[http://www.google.com/search?q=UDDI+3.0|UDDI 3.0]]: The UDDI Version 3.0 Specification describes the Web services, data structures and behaviors of all instances of a UDDI registry.
Line 101: Line 101:
[http://www.google.com/search?q=SAML SAML]: SAML is an XML framework for exchanging authentication and authorization information. [[http://www.google.com/search?q=SAML|SAML]]: SAML is an XML framework for exchanging authentication and authorization information.
Line 103: Line 103:
[http://www.google.com/search?q=BPEL4WS ["BPEL4WS"]]: defines a notation for specifying business process behavior based on Web Services [[http://www.google.com/search?q=BPEL4WS|["BPEL4WS"]]]: defines a notation for specifying business process behavior based on Web Services
Line 105: Line 105:
[http://www.google.com/search?q=WS-Choreography WS-Choreography]: describes mechanisms to co-ordinate the interaction among Web Services and their users [[http://www.google.com/search?q=WS-Choreography|WS-Choreography]]: describes mechanisms to co-ordinate the interaction among Web Services and their users
Line 107: Line 107:
[http://www.google.com/search?q=WSRP WSRP]: are visual, user-facing web services centric components that plug-n-play with portals or other intermediary web applications that aggregate content or applications from different sources. [[http://www.google.com/search?q=WSRP|WSRP]]: are visual, user-facing web services centric components that plug-n-play with portals or other intermediary web applications that aggregate content or applications from different sources.
Line 109: Line 109:
[http://www.google.com/search?q=WSXL WSXL]: is a Web services centric component model for interactive Web applications, that is, for applications that provide a user experience across the Internet [[http://www.google.com/search?q=WSXL|WSXL]]: is a Web services centric component model for interactive Web applications, that is, for applications that provide a user experience across the Internet
Line 111: Line 111:
[http://www.google.com/search?q=ws-messagedelivery WS-MD] MessageDelivery [[http://www.google.com/search?q=ws-messagedelivery|WS-MD]] MessageDelivery
Line 117: Line 117:
Deutsche Übersicht über alle Web Service Spezifikationen: [http://www.google.com/search?q=WS-Universe+Spezifikationsuebersicht WS-Universe Spezifikationsuebersicht] Deutsche Übersicht über alle Web Service Spezifikationen: [[http://www.google.com/search?q=WS-Universe+Spezifikationsuebersicht|WS-Universe Spezifikationsuebersicht]]
Line 122: Line 122:
If you see any others not listed here, please feel free to edit the Wiki or let me know [mailto:dims@yahoo.com Davanum Srinivas (dims@yahoo.com)] If you see any others not listed here, please feel free to edit the Wiki or let me know [[mailto:dims@yahoo.com|Davanum Srinivas (dims@yahoo.com)]]

Web Service Specifications

WS-Acknowledgement: The WS-Acknowledgement protocol is designed to enable WS-Acknowledgement senders to request explicit acknowledgement from WS-Acknowledgement receivers that a WS-Acknowledgement Request Message has been received.

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-CAF: Composite Application Framework - open, multi-level framework for standard coordination of long-running business processes across multiple, incompatible transaction processing models and architectures.

WS-Callback: used to dynamically specify where to send asynchronous responses to a SOAP request.

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

WS-Eventing: The WS-Eventing specification "describes a protocol that allows Web services to subscribe to or accept subscriptions for event notification messages."

WS-Events: The WS-Events specification defines an XML syntax and a set of processing rules for advertising, subscribing, producing and consuming Web Services Events using a push and pull mode.

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-MessageData introduces two specific types of message meta-data, MessageId and RefToMessageId.

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: Web Services Referral Protocol (WS-Referral) is a SOAP-based, stateless protocol for inserting, deleting, and querying routing entries in a SOAP router

WS-Reliability: is a SOAP-based protocol for exchanging SOAP messages with guaranteed delivery, no duplicates, and guaranteed message ordering.

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-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.

WSMF: The Web Services Management Framework (WSMF) is a logical architecture for managing computing resources, including Web services themselves, through Web services. Obsolete - superseded by WSDM.

WSDM: The purpose of this TC is to define web services management, including using web services architecture and technology to manage distributed resources. This TC will also develop the model of a web service as a manageable resource. Consists of Management using Web Services (MuWS) and Management of Web Services (MoWS).

WSRF: The WS-Resource Framework is a set of specifications that provide a consistent way to describe and access Web services that offer access to stateful resources (being standardized at http://www.oasis-open.org/committees/wsrf/). Comprised of WS-Resource, WS-ResourceProperties, WS-ResourceLifetime, WS-ServiceGroup, and WS-BaseFaults.

WS-Notification: WS-Notification (WSN) is a set of specifications that provide support for eventing using web services technologies (being standardized at http://www.oasis-open.org/committees/wsn/). Comprised of WS-BaseNotification, WS-Topics, and WS-BrokeredNotification.

SOAP 1.1: SOAP 1.1 is a lightweight protocol for exchange of information in a decentralized, distributed environment.

SOAP 1.2: SOAP 1.2 is the latest version of SOAP and provides the definition of the XML-based information which can be used for exchanging structured and typed information between peers in a decentralized, distributed environment.

WSDL 1.1: WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.

WSDL 2.0: WSDL 2.0 (formerly known as 1.2) is the latest version of WSDL

UDDI 2.0: Universal Description, Discovery and Integration, or UDDI, is the name of a group of web-based registries that expose information about a business or other entity[2] and its technical interfaces (or API’s).

UDDI 3.0: The UDDI Version 3.0 Specification describes the Web services, data structures and behaviors of all instances of a UDDI registry.

SAML: SAML is an XML framework for exchanging authentication and authorization information.

["BPEL4WS"]: defines a notation for specifying business process behavior based on Web Services

WS-Choreography: describes mechanisms to co-ordinate the interaction among Web Services and their users

WSRP: are visual, user-facing web services centric components that plug-n-play with portals or other intermediary web applications that aggregate content or applications from different sources.

WSXL: is a Web services centric component model for interactive Web applications, that is, for applications that provide a user experience across the Internet

WS-MD MessageDelivery

Other languages

German

Deutsche Übersicht über alle Web Service Spezifikationen: WS-Universe Spezifikationsuebersicht

===========================================================================================================================

If you see any others not listed here, please feel free to edit the Wiki or let me know Davanum Srinivas (dims@yahoo.com)

WebServiceSpecifications (last edited 2009-09-20 22:47:40 by localhost)