Web Services
StandardWS-Calendar Version 1.0
Describes:
. A semantic (or information) model for exchange of calendar information to coordinate activities
. A means of synchronizing and maintaining calendars
The specification includes XML vocabularies for the interoperable and standard exchange of:
. Schedules, including sequences of schedules
. Intervals, including sequences of Intervals
. Other calendar information consistent with the IETF iCalendar standards
These vocabularies describe schedules and Intervals future, present, or past (historical).
The specification is divided into three parts.
1) The information model and XML vocabularies for exchanging schedule information
2) RESTful Services for calendar update and synchronization
3) Web services for calendar update and synchronization
The Technical Committee has decided not to publish Parts 2 and 3 until a later version.
WS-Calendar Version 1.0
Describes:
. A semantic (or information) model for exchange of calendar information to coordinate activities
. A means of synchronizing and maintaining calendars
The specification includes XML vocabularies for the interoperable and standard exchange of:
. Schedules, including sequences of schedules
. Intervals, including sequences of Intervals
. Other calendar information consistent with the IETF iCalendar standards
These vocabularies describe schedules and Intervals future, present, or past (historical).
The specification is divided into three parts.
1) The information model and XML vocabularies for exchanging schedule information
2) RESTful Services for calendar update and synchronization
3) Web services for calendar update and synchronization
The Technical Committee has decided not to publish Parts 2 and 3 until a later version.
Produced by:
OASIS Web Services Calendar (WS-Calendar) TCVoting history:
July 2011
OASIS Standard:
Cite as:
Cite as:
[WS-Calendar]
WS-Calendar Version 1.0. Edited by Toby Considine and Mike Douglass. 30 July 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/ws-calendar/ws-calendar-spec/v1.0/cs01/ws-calendar-spec-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/ws-calendar-1.0-spec.html
StandardWeb Services Quality Factors Version 1.0
Provides a standard for quality factors of web services in their development, usage and management. Web services usually have distinguished characteristics. They are service-oriented, network-based, variously bind-able, loosely-coupled, platform independent, and standard-protocol based. As a result, a web service system requires its own quality factors unlike installation-based software. For instance, as the quality of web services can be altered in real-time according to changes by the service provider, considering real-time properties of web services is very meaningful in describing the web services quality. This document presents the quality factors of web services with definition, classification, and sub-factors case by case. For each quality factor, related specifications are cited with a brief explanation. This specification can be generally extended to the definition of quality of SOA and to provide the foundation for quality in the SOA system.
Web Services Quality Factors Version 1.0
Provides a standard for quality factors of web services in their development, usage and management. Web services usually have distinguished characteristics. They are service-oriented, network-based, variously bind-able, loosely-coupled, platform independent, and standard-protocol based. As a result, a web service system requires its own quality factors unlike installation-based software. For instance, as the quality of web services can be altered in real-time according to changes by the service provider, considering real-time properties of web services is very meaningful in describing the web services quality. This document presents the quality factors of web services with definition, classification, and sub-factors case by case. For each quality factor, related specifications are cited with a brief explanation. This specification can be generally extended to the definition of quality of SOA and to provide the foundation for quality in the SOA system.
Produced by:
OASIS Web Services Quality Model TCVoting history:
July 2011
OASIS Standard:
Cite as:
Cite as:
[WS-Quality-Factors-v1.0]
Web Services Quality Factors Version 1.0. Edited by Eunju Kim, Yongkon Lee, Yeongho Kim, Hyungkeun Park, Jongwoo Kim, Byoungsun Moon, Junghee Yun, and Guil Kang. 22 July 2011. OASIS Committee Specification 01. http://docs.oasis-open.org/wsqm/WS-Quality-Factors/v1.0/cs01/WS-Quality-Factors-v1.0-cs01.html. Latest version: http://docs.oasis-open.org/wsqm/WS-Quality-Factors/v1.0/WS-Quality-Factors-v1.0.html
StandardOASIS ebCore Party Id Type Technical Specification Version 1.0
A mechanism for the identification of business partners in business documents based on XML (or other structured formats) and message headers using URN-based identifier types is required in many electronic business exchanges. This specification specifies a formal URN-based mechanism for referencing party types from the ISO 6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace. Sample applications include (but are not limited to): ebXML message headers; ebXML collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents; the UN/CEFACT SBDH; and XBRL documents.
OASIS ebCore Party Id Type Technical Specification Version 1.0
A mechanism for the identification of business partners in business documents based on XML (or other structured formats) and message headers using URN-based identifier types is required in many electronic business exchanges. This specification specifies a formal URN-based mechanism for referencing party types from the ISO 6523, ISO 9735 and ISO 20022 identification scheme catalogs using the oasis URN namespace. Sample applications include (but are not limited to): ebXML message headers; ebXML collaboration protocol profiles and agreements; UBL, UN/CEFACT and OAGIS XML business documents; the UN/CEFACT SBDH; and XBRL documents.
Produced by:
OASIS ebXML Core (ebCore) TCVoting history:
September 2010
OASIS Standard:
Cite as:
Cite as:
[PartyIdType-v1.0] OASIS ebCore Party Id Type Technical Specification Version 1.0. Edited by Dale Moberg and Kathryn Breininger. 28 September 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/CS01/PartyIdType-1.0.html. Latest version: http://docs.oasis-open.org/ebcore/PartyIdType/v1.0/PartyIdType-1.0.html.
StandardWeb Services – Human Task (WS-HumanTask) Specification Version 1.1
Introduces the definition of human tasks, including their properties, behavior and a set of operations used to manipulate human tasks. A coordination protocol is introduced in order to control autonomy and life cycle of service-enabled human tasks in an interoperable manner.
Web Services – Human Task (WS-HumanTask) Specification Version 1.1
Introduces the definition of human tasks, including their properties, behavior and a set of operations used to manipulate human tasks. A coordination protocol is introduced in order to control autonomy and life cycle of service-enabled human tasks in an interoperable manner.
Produced by:
OASIS BPEL4People TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[ws-humantask-v1.1] Web Services – Human Task
(WS-HumanTask) Specification Version 1.1. Edited by Luc Clément, Dieter König, Vinkesh Mehta, Ralf Mueller, Ravi Rangaswamy, Michael Rowley, and Ivana Trickovic. 17 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cs-01.html. Latest version: http://docs.oasis-open.org/bpel4people/ws-humantask-1.1.html.
StandardWS-BPEL Extension for People (BPEL4People) Specification Version 1.1
Introduces a model for business processes based on Web services. A BPEL process orchestrates interactions among different Web services. The language encompasses features needed to describe complex control flows, including error handling and compensation behavior. In practice, however many business process scenarios require human interactions. A process definition should incorporate people as another type of participants, because humans may also take part in business processes and can influence the process execution.
This specification introduces a BPEL extension to address human interactions in BPEL as a first-class citizen. It defines a new type of basic activity which uses human tasks as an implementation, and allows specifying tasks local to a process or use tasks defined outside of the process definition. This extension is based on the WS-HumanTask specification.
WS-BPEL Extension for People (BPEL4People) Specification Version 1.1
Introduces a model for business processes based on Web services. A BPEL process orchestrates interactions among different Web services. The language encompasses features needed to describe complex control flows, including error handling and compensation behavior. In practice, however many business process scenarios require human interactions. A process definition should incorporate people as another type of participants, because humans may also take part in business processes and can influence the process execution.
This specification introduces a BPEL extension to address human interactions in BPEL as a first-class citizen. It defines a new type of basic activity which uses human tasks as an implementation, and allows specifying tasks local to a process or use tasks defined outside of the process definition. This extension is based on the WS-HumanTask specification.
Produced by:
OASIS BPEL4People TCVoting history:
August 2010
OASIS Standard:
Cite as:
Cite as:
[bpel4people-v1.1] WS-BPEL Extension for People (BPEL4People) Specification Version 1.1. Edited by Luc Clément, Dieter König, Vinkesh Mehta, Ralf Mueller, Ravi Rangaswamy, Michael Rowley, and Ivana Trickovic. 17 August 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/bpel4people/bpel4people-1.1-spec-cs-01.html. Latest version: http://docs.oasis-open.org/bpel4people/bpel4people-1.1.html.
StandardDevices Profile for Web Services (DPWS) v1.1
Defines a minimal set of implementation constraints to enable secure Web service messaging, discovery, description, and eventing on resource-constrained endpoints.
Devices Profile for Web Services (DPWS) v1.1
Defines a minimal set of implementation constraints to enable secure Web service messaging, discovery, description, and eventing on resource-constrained endpoints.
Produced by:
OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TCVoting history:
July 2009
StandardWeb Services Dynamic Discovery (WS-Discovery) v1.1
Defines a discovery protocol to locate services. In an ad hoc mode of operation, probes are sent to a multicast group, and target services that match return a response directly to the requester. To scale to a large number of endpoints and to extend the reach of the protocol, this protocol defines a managed mode of operation and a multicast suppression behavior if a discovery proxy is available on the network. To minimize the need for polling, target services that wish to be discovered send an announcement when they join and leave the network.
Web Services Dynamic Discovery (WS-Discovery) v1.1
Defines a discovery protocol to locate services. In an ad hoc mode of operation, probes are sent to a multicast group, and target services that match return a response directly to the requester. To scale to a large number of endpoints and to extend the reach of the protocol, this protocol defines a managed mode of operation and a multicast suppression behavior if a discovery proxy is available on the network. To minimize the need for polling, target services that wish to be discovered send an announcement when they join and leave the network.
Produced by:
OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TCVoting history:
July 2009
Produced by:
OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TCVoting history:
July 2009
StandardWeb Services Federation Language (WS-Federation) v1.2
Defines mechanisms to allow different security realms to federate, such that authorized access to resources managed in one realm can be provided to security principals whose identities and attributes are managed in other realms. This includes mechanisms for brokering of identity, attribute, authentication and authorization assertions between realms, and privacy of federated claims.
By using the XML, SOAP and WSDL extensibility models, the WS-* specifications are designed to be composed with each other to provide a rich Web services environment. WS-Federation by itself does not provide a complete security solution for Web services. WS-Federation is a building block that is used in conjunction with other Web service, transport, and application-specific protocols to accommodate a wide variety of security models.
Web Services Federation Language (WS-Federation) v1.2
Defines mechanisms to allow different security realms to federate, such that authorized access to resources managed in one realm can be provided to security principals whose identities and attributes are managed in other realms. This includes mechanisms for brokering of identity, attribute, authentication and authorization assertions between realms, and privacy of federated claims.
By using the XML, SOAP and WSDL extensibility models, the WS-* specifications are designed to be composed with each other to provide a rich Web services environment. WS-Federation by itself does not provide a complete security solution for Web services. WS-Federation is a building block that is used in conjunction with other Web service, transport, and application-specific protocols to accommodate a wide variety of security models.
StandardWS-SecureConversation v1.4
Defines extensions that build on [WS-Security] to provide a framework for requesting and issuing security tokens, and to broker trust relationships.
WS-SecureConversation v1.4
Defines extensions that build on [WS-Security] to provide a framework for requesting and issuing security tokens, and to broker trust relationships.
StandardWeb Services MakeConnection v1.1
Describes a protocol that allows messages to be transferred between nodes implementing this protocol by using a transport-specific back-channel. The protocol is described in this specification in a transport-independent manner allowing it to be implemented using different network technologies. To support interoperable Web services, a SOAP binding is defined within this specification.
The protocol defined in this specification depends upon other Web services specifications for the identification of service endpoint addresses and policies. How these are identified and retrieved are detailed within those specifications and are out of scope for this document.
By using the XML [XML], SOAP [SOAP 1.1], [SOAP 1.2] and WSDL [WSDL 1.1] extensibility model, SOAP-based and WSDL-based specifications are designed to be composed with each other to define a rich Web services environment. As such, WS-MakeConnection by itself does not define all the features required for a complete messaging solution. WS-MakeConnection is a building block that is used in conjunction with other specifications and application-specific protocols to accommodate a wide variety of requirements and scenarios related to the operation of distributed Web services.
Web Services MakeConnection v1.1
Describes a protocol that allows messages to be transferred between nodes implementing this protocol by using a transport-specific back-channel. The protocol is described in this specification in a transport-independent manner allowing it to be implemented using different network technologies. To support interoperable Web services, a SOAP binding is defined within this specification.
The protocol defined in this specification depends upon other Web services specifications for the identification of service endpoint addresses and policies. How these are identified and retrieved are detailed within those specifications and are out of scope for this document.
By using the XML [XML], SOAP [SOAP 1.1], [SOAP 1.2] and WSDL [WSDL 1.1] extensibility model, SOAP-based and WSDL-based specifications are designed to be composed with each other to define a rich Web services environment. As such, WS-MakeConnection by itself does not define all the features required for a complete messaging solution. WS-MakeConnection is a building block that is used in conjunction with other specifications and application-specific protocols to accommodate a wide variety of requirements and scenarios related to the operation of distributed Web services.
StandardWeb Services ReliableMessaging v1.2
Describes a protocol that allows messages to be transferred reliably between nodes implementing this protocol in the presence of software component, system, or network failures. The protocol is described in this specification in a transport-independent manner allowing it to be implemented using different network technologies. To support interoperable Web services, a SOAP binding is defined within this specification.
The protocol defined in this specification depends upon other Web services specifications for the identification of service endpoint addresses and policies. How these are identified and retrieved are detailed within those specifications and are out of scope for this document.
By using the XML [XML], SOAP [SOAP 1.1], [SOAP 1.2] and WSDL [WSDL 1.1] extensibility model, SOAP-based and WSDL-based specifications are designed to be composed with each other to define a rich Web services environment. As such, WS-ReliableMessaging by itself does not define all the features required for a complete messaging solution. WS-ReliableMessaging is a building block that is used in conjunction with other specifications and application-specific protocols to accommodate a wide variety of requirements and scenarios related to the operation of distributed Web services.
Web Services ReliableMessaging v1.2
Describes a protocol that allows messages to be transferred reliably between nodes implementing this protocol in the presence of software component, system, or network failures. The protocol is described in this specification in a transport-independent manner allowing it to be implemented using different network technologies. To support interoperable Web services, a SOAP binding is defined within this specification.
The protocol defined in this specification depends upon other Web services specifications for the identification of service endpoint addresses and policies. How these are identified and retrieved are detailed within those specifications and are out of scope for this document.
By using the XML [XML], SOAP [SOAP 1.1], [SOAP 1.2] and WSDL [WSDL 1.1] extensibility model, SOAP-based and WSDL-based specifications are designed to be composed with each other to define a rich Web services environment. As such, WS-ReliableMessaging by itself does not define all the features required for a complete messaging solution. WS-ReliableMessaging is a building block that is used in conjunction with other specifications and application-specific protocols to accommodate a wide variety of requirements and scenarios related to the operation of distributed Web services.
No results with the selected filters