David,
I didn't miss the point at all. My point is that if you want "simple", you
have SOAP/WSDL. If you want reliability, security, etc., that's what we
have done that SOAP doesn't have. However this rich function comes at a
price of some cost for generating compatible configurations.
One way of extending MSG/CPPA for B2C is by allowing a service provider to
publish a CPP (or a CPA template) that is a take-it-or-leave-it CPP. "If
you want to do business with me, you set up this way." That might be fine
for customers but it probably wouldn't be sufficient for B2B. However,
many people will ask, why not just use WSDL?
Regards,
Marty
*************************************************************************************
Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown
Hts, NY 10598
914-784-7287; IBM tie line 863-7287
Notes address: Martin W Sachs/Watson/IBM
Internet address: mwsachs @ us.ibm.com
*************************************************************************************
"Burdett, David" <> on 01/07/2002 12:45:05 PM
To:
Martin W Sachs/Watson/IBM@IBMUS, "Burdett, David"
<>
cc:
David Fischer <>, Jacques Durand
<>, Arvola Chan <>, ebXML Msg
<>, "Ian. C. Jones (E-mail)"
<>
Subject:
RE: [ebxml-msg] Messaging Spec v1.092
Marty
I think you miss the point. SOAP is not fit for purpose as it does not
include reliability and security. What we really need to do is extend
SOAP/WSDL to include security, reliability, end-to-end acks, etc, but in
the
declarative, take-it-or-leave-it style of WSDL **as well as** the
negotiated
way consisting of the merging of templates that I think you are suggesting.
Remember, I really am not anti-CPA, I just want them to be used in the
right
way i.e. to record the agreement between two parties where they want to
constrain how they do business together.
David
