Stefano,
I'm sorry that I have to disagree. Yes, for simple applications, a
WSDL-like description might be all that is needed. The service-interface
section of tpaML might be another example.
However, the CPA-less configuration might have the same level of
functionality that might be needed for B2B with ebXML. Take a look at
IBM's Websphere Business Integrator product.
People should understand that without a CPA, for a given application, each
party still has to provide the same configuration about the other party to
its system. If there is no CPA, the two parties have to use phone and fax
to understand each other's requirements and then manually populate the same
runtime database as with a CPA.
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
*************************************************************************************
"Stefano POGLIANI" <stefano.pogliani@sun.com> on 11/05/2001 08:29:23 AM
To: Martin W Sachs/Watson/IBM@IBMUS, "David Fischer"
<david@drummondgroup.com>
cc: "Dan Weinreb" <dlw@exceloncorp.com>,
<ebxml-msg@lists.oasis-open.org>, <ebxml-cppa@lists.oasis-open.org>
Subject: RE: [ebxml-cppa] RE: [ebxml-msg] Attributes specified in both
the message and the CPA
Sorry to jump in late.
I think that when the Messaging is used "without CPA", then the
configuration is
given by something similar to the WSDL file; I mean, when I am not working
with
a CPA, I am probably exposing a Web Service with ebXML-TRP bindings. This
W/s
may not be choregraphed or it may be choreographed by something different
than
the ebXML BPSS.
But, I agree with Marty, the two parties wanting to talk need to agree on
the
way they can understand each other. This may be done via "dynamic
negotiation"
or via "the CPA" or via something else. I am not sure that the message
should
carry all the information required to properly catch it and react to it
(but
perhaps I do not see the whole scenario)
Best regards
/stefano
>