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

RE: Asynchronous Service Access Protocol (ASAP)

From: Keith Swenson <KSwenson@us.fujitsu.com>
Date: Mon, 22 Aug 2005 00:25:17 -0700
Message-ID: <6DDD4D6558F5704A89316276BAAD812217B517AF@exchange.regatta.fswroot.fsw.fujitsu.com>
To: Steve Ross-Talbot <steve@pi4tech.com>, Charlton Barreto <charlton_b@mac.com>
Cc: "'WS-Choreography List'" <public-ws-chor@w3.org>
Ouch!  I am the one usually complaining about the over-hype of BPEL to the
exclusion of many other fine efforts.

Let me start by apologizing about failing to mention WS-CDL.  It is a shame,
and I would like to correct it, but I need some help.  (I do, by the way,
mention it regularly in the presentations.)

I have always viewed ASAP and WS-CDL as complimentary.  If I am correct,
WS-CDL is a language that can be used to describe any possible choreography,
that is it describes the sequencing requirements of a set of SOAP calls.
ASAP, on the other hand, is a specific choreography, that is: there is a
specific set of SOAP calls with well defined meanings that can be made, and
a specified temporal relationship that the calls must be made in.

As such, I believe that ASAP can be described using WS-CDL.  The ASAP
technical committee has simply not had the time to become familiar enough
with WS-CDL to know how to properly express ASAP in WS-CDL.   Currently ASAP
is defined in terms of an XML schema XSD file, a WSDL file, and
specification document that tells you when you can make what call.  If a CDL
definition of the choreography could be constructed, then we could make it
available on the ASAP site to help make the choreography clear, and make it
available on the WS-CDL site as a real world example.  That would go a long
ways to reduce the confusions that people are going to naturally have when
trying to figure out how these are related.  Steve Ross-Talbot mentioned (in
a later message) that he is willing to spearhead this effort.

At a very minimum, I want to propose a "Reciprocal Reference".  We jointly
define a paragraph that accurately describes how the two efforts are
related, and on both sites we include this paragraph with references to the
other site.


Keith D Swenson, < kswenson at us . fujitsu . com >
Fujitsu Software Corporation
1250 E. Arques Avenue, Sunnyvale, CA 94085
(408) 746-6276 mobile: (408) 859-1005

> -----Original Message-----
> From: Steve Ross-Talbot [mailto:steve@pi4tech.com] 
> Sent: Sunday, August 07, 2005 11:05 AM
> To: Charlton Barreto
> Cc: 'WS-Choreography List'
> Subject: Re: Asynchronous Service Access Protocol (ASAP)
> I find it continually interesting that we see such 
> initiatives as ASAP that fail to mention how they fit with 
> respect to us. They never do this with BPEL (must be the 
> proliferation of marketing dollars) of course. I find it 
> rather a shame. Certainly if it were an academic paper given 
> the words used, failure to reference WS-CDL would be grounds 
> for failure. Certainly would not get int oa conference.
> Cheers
> Steve T
> On 5 Aug 2005, at 18:54, Charlton Barreto wrote:
> >
> > This effort seems to focus on service contracts rather than 
> > collaboration. It may be something useful for WS-CDL in terms of 
> > defining collaborations with ASAP services. I'm interested in what 
> > develops in this effort and how we can ensure it can be 
> leveraged by 
> > WS-CDL....
> >
> > On 03/08/2005, at 11:26, Steve Ross-Talbot wrote:
> >
> >>
> >> I got this from a trusted friend. I have asked Keith (the 
> author) how 
> >> this fits with WS-CDL. Any comments anyone?
> >>
> >> Cheers
> >>
> >> Steve T
> >>
> >> Begin forwarded message:
> >>
> >>
> >>> Am I missing something, or is this just a lame attempt at 
> doing the 
> >>> same things as WS-CDL? - 
> >>> 
> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=asap or 
> >>> more specifically 
> >>> http://www.oasis-open.org/committees/download.php/7590/
> >>> ASAP_BrainStorm.ppt
> >>>
> >>>
> >>
> >>
> >>
> >
> >
> >
> >
Received on Tuesday, 23 August 2005 08:20:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:08 UTC