W3C home > Mailing lists > Public > public-ws-chor-comments@w3.org > February 2005

Fwd: LAST CALL COMMENT 1/31/2005: State relationship between WS-CDL and ebBP

From: Greg Ritzinger <gritzinger@novell.com>
Date: Mon, 07 Feb 2005 08:51:58 -0700
Message-Id: <s2072c41.069@sinclair.provo.novell.com>
To: <public-ws-chor-comments@w3.org>
Forwarded to comments list on behalf of Charlton Barreto

>>>Charlton Barreto <charlton_b@mac.com> 01/31/05 1:28 pm >>>

The WS-CDL specification (Web Services Choreography Description
Language version 1.0 W3C Last Call Draft 17 December 2004
http://www.w3.org/TR/2004/WD-ws-cdl-10-20041217/) should state the
relationship between WS-CDL and the OASIS ebXML Business Process
Specification Schema (ebBP) work in OASIS.

Although WS-CDL and ebBP address similar problem domains, the divergent
foci of the two enables them to be layerable - while WS-CDL focuses
primarily on the web service perspective, ebBP describes the pure
business message flow and state alignment. As such they are not
mutually exclusive. Toward this, ebBP v2.0 (which is nearing a vote for
OASIS Committee Draft) supports mapping of Business Transaction
patterns to abstract operations through the OperationMapping
constructs, definition of business QoS guidelines, and it can be
supported by CPPA, which maps to concrete WSDL. These mechanisms
provide the avenue for WS-CDL and ebBP compatibility.

Given this, the WS-CDL specification should include similar language to
that expressed in Section 1.3 (Specification Composability) and 1.5
(Relationship to Business Process Languages). It is recommended that
language be added to indicate WS-CDL and ebBP are not mutually
exclusive, and that, through mechanisms such as those mentioned above,
compatibility exists between the two. This is consistent with the
current text that references BPML, BPEL, etc. Note that, at present,
Section 1.5 only addresses CDL's relationship with executable
languages. If including the language for stating the relationship with
ebBP is not consistent for Section 1.5, it is recommended that a
subsequent section be added to address ebBP (and like specifications).

It is proposed that we add the following to 1.3:

Specification Composability. This specification will work alongside
and complement other specifications such as the WS-Reliability [WSRM],
WS-Composite Application Framework (WS-CAF) [WSCAF], WS-Security [WSS],
Business Process Execution Language for WS (WS-BPEL) [WSBPEL], ebXML
Business Process Specification Schema [ebBP], etc.

It is proposed that we add the following either to 1.5 or in a
subsequent new section:

Relationship with the ebXML Business Process framework

The ebXML Business Process Specification Schema technical specification
defines a standard language by which business systems may be configured
to support execution of business collaborations. Such business
collaborations consist of business transactions, which are implemented
through semantics defined in one of several standard, extensible or
trading partner-specific business transaction patterns. These patterns
specify the business message exchange (requests, responses and business
signals) applicable to a given business transaction definition.

Through ebBP mapping of Business Transaction patterns to abstract
operations, and when preferred, combined with CPPA support of concrete
WSDL, WS-CDL and ebBP can be used in a complementary manner.
Received on Monday, 7 February 2005 15:52:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:10 GMT