OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Web Services Transaction v1.1 Submitted for OASIS Standard

OASIS Members:

The OASIS Web Services Transaction (WS-TX) Technical Committee has submitted the following specification set, which is
an approved Committee Specification, to be considered as an OASIS Standard:

Web Services Transaction Version 1.1:
Web Services Atomic Transaction (WS-AtomicTransaction) Version 1.1
Web Services Business Activity (WS-BusinessActivity) Version 1.1
Web Services Coordination (WS-Coordination) Version 1.1

The text of the TC submission is appended.

You now have until 15 March to familiarize yourself with the submission and provide input to your organization's voting

On 16 March, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have
until the last day of March, inclusive, to cast their ballots on whether this Committee Specification should be approved
as an OASIS Standard or not.

Members who wish to discuss this ballot may do so through member-discuss@lists.oasis-open.org.

In accordance with the OASIS Technical Committee Process, this Committee Specification has already completed the
necessary 60-day public review period as noted in the submission below.

The normative TC Process for approval of Committee Specifications as OASIS Standards is found at

Any statements related to the IPR of this specification are posted at:

Your participation in the review and balloting process is greatly appreciated.


Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
phone: 603.232.9090


(a) Links to the approved Committee Specification in the TC's document repository. 
  - Specification: 
  - WSDL: 
  - Schema: 

  - Specification: 
  - WSDL: 
  - Schema: 

  - Specification: 
  - WSDL: 
  - Schema: 

(b) The editable version of all files that are part of the Committee Specification. 
  - Word doc: 
  - Word doc: 
  - Word doc: 

(c) Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or
reference, including fragments of such, are well formed, and that all expressions are valid; 
All schema and XML instances included in the specification are well formed and all expressions are valid. 

(d) A clear English-language summary of the specification; 
Web Services Transaction v1.1 is a set of 3 specifications consisting of WS-Coordination, WS-AtomicTransaction and

The WS-Coordination specification describes an extensible framework for providing protocols that coordinate the actions
of distributed applications. Such coordination protocols are used to support a number of applications, including those
that need to reach consistent agreement on the outcome of distributed activities.
The specification defines a coordination context XML type that identifies a specific activity and the "coordination
type" of the agreement protocol supported by the coordinatoin context. The specification also defines protocols that
enable an application service to create a coordination context and to register for coordination protocols. The framework
enables existing transaction processing, workflow, and other systems for coordination to hide their proprietary
protocols and to operate in a heterogeneous environment. 

The WS-AtomicTransaction specification provides the definition of the Atomic Transaction coordination type that is to be
used with the extensible coordination framework described in WS-Coordination. This specification defines three specific
agreement coordination protocols for the Atomic Transaction coordination type: completion, volatile two-phase commit,
and durable two-phase commit. Developers can use any or all of these protocols when building applications that require
consistent agreement on the outcome of short-lived distributed activities that have the all-or-nothing property. 

The WS-BusinessActivity specification provides the definition of two Business Activity coordination types: AtomicOutcome
or MixedOutcome, that are to be used with the extensible coordination framework described in the WS-Coordination
specification. This specification also defines two specific Business Activity agreement coordination protocols for the
Business Activity coordination types: BusinessAgreementWithParticipantCompletion, and
BusinessAgreementWithCoordinatorCompletion. Developers can use these protocols when building applications that require a
compensation-based, consistent agreement on the outcome of long-running distributed activities. 

(e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards
developing organizations. 

-- OASIS Web Services Business Process Execution Language (WSBPEL) TC.   
The WSBPEL TC focuses on an overall business process orchestration language.  WS-TX does not discuss how an application
operates internally, nor make any overall statement about the overall business process orchestration, but instead
focuses on individual, pair-wise message exchanges between a participant in an activity and the coordinator of that

-- Web Services Composite Application Framework (WS-CAF) TC also offers a set of consensus protocols, some of which are
complementary to WS-TX.  The WS-TX TC focuses on solidifying a proven foundation for an extensible coordination
framework, and updating two fundamental consensus protocols. It provides explicit rules in the form of state tables and
message schemas for both successful and faulting behavior. It offers an explicit security model for authorizing
participation. It emphasizes composition with other WS-* standards, such as WS-Addressing and WS- Security.
-- OASIS Business Transactions (BTP) TC. The WS-TX TC has a different focus with regard to specification scope, required
functions, policy, and other Web Services composeability. WS-TX focuses solely on simple, pair-wise message exchange
patters that can be used to reach either atomic commitment, or looser application consensus. WS-TX provides simpler
interoperability by focusing exclusively on externally visible service behavior at the protocol level. It does not
impose constraints on internal service implementations. It emphasizes clean composition with other WS-* standards, such
as WS-Addressing and WS-Security. WS-TX concentrates on interoperability, specifying relatively few variations and
providing simple state tables rather than extensive options with considerable application semantics. 

(f) Certification by at least three OASIS member organizations that they are successfully using the specification; 
The following 3 companies have certified their use of all 3 committee specifications: 



Red Hat:

(g) The beginning and ending dates of the public review(s), a pointer to the announcement of the public review(s), and a
pointer to an account of each of the comments/issues raised during the public review period(s), along with its

Announcement of the public review for WS-Coordination and WS-AtomicTransaction: 
The public review ran from 15 September 2006 until 14 November 2006. 
Comment/issue log: 

Announcement of the public review for WS-BusinessActivity: 
The public review ran from 13 November 2006 until 12 January 2007. 
Comment/issue log: 

(h) An account of and results of the voting to approve the specification as a Committee Specification, including the
date of the ballot and a pointer to the ballot; 

The approval ballot was conducted by the TC Admin and closed on 8 February 2007. 
16 of 20 eligible voters voted YES to submit the specifications to the OASIS membership. There were no NO votes or
The results can be viewed at:

(i) An account of or pointer to votes and comments received in any earlier attempts to standardize substantially the
same specification, together with the originating TC's response to each comment; 

This is the first submission to the OASIS membership. 

(j) A pointer to the publicly visible comments archive for the originating TC; 

(k) A pointer to any minority reports submitted by one or more Members who did not vote in favor of approving the
Committee Specification, which report may include statements regarding why the member voted against the specification or
that the 

There are no minority reports. 

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]