Re: CPA-CPP ver. 0.92 distributed today

[Martin W Sachs <mwsachs@us.ibm.com>]

Michael,

rejoinders embedded below.

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
*************************************************************************************



Michael Joya <mike.joya@xmlglobal.com> on 03/02/2001 05:31:44 PM

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:   ebxml-tp@lists.ebxml.org
Subject:  Re: CPA-CPP ver. 0.92 distributed today



>   That works well enough on paper. In reality, businesses like Fedex and
> Boeing that have 15,000 online customers a day would have to invent some
> infrastructure
> to support the creation and communication of CPAId's to other parties.
And that's
> BEFORE they send the ebXML messages to each other.
>
> MWS:  Anone who has more than 2 online customers a day has to have that
> infrastructure whether you call the basis a CPA or a phone conversation
between them.
> We
> keep tripping over the ebXML oversight not to deal with middleware for
e-business.

  ...and that middleware will undoubtably require some sort of messaging
standard, but
we still don't have a way to send a configuration document from point A to
point B.

MWS:  Yep - the bootstrap problem again.  I thought that TRP was looking at
proposals on
this.

Ha-ha. Suppose a business already has the necessary infrastructure to
communicate those
documents with a partner, what does it need ebXML for? They might as well
use the same
facility to transfer business messages.

MWS:  That's true.  Partners A and B can continue using their EDI VAN, SNA,
or whatever
and just keep going, just like I still use my 1948 portable typewrite.
Since you are
active here, I assume that you must think that there is a market for ebXML.


  The tech arch spec is finished now, but it's too bad we couldn't prepend
some terse
caveat like "In order to use this business messaging framework, you must
support another
business messaging framework."

MWS:  I am sure that TRP would be happy to entertain a proposal.  The could
probably flesh
it out in the 2 weeks remaining.


--
// Michael Joya
// XML Global Research and Development
// 1818 Cornwall Ave. Suite 9
// Vancouver, Canada
// 604-717-1100x230




------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-tp-request@lists.ebxml.org