Re: FYI: Article on ebXML and Interoperability

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

Quoted without comment.

*************************************************************************************

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
*************************************************************************************
---------------------- Forwarded by Martin W Sachs/Watson/IBM on 08/26/2001
06:17 PM ---------------------------

Thomas Gagne <tgagne@efinnet.com>@demai05.mw.mediaone.net on 08/24/2001
09:54:29 PM

Sent by:  tgagne@demai05.mw.mediaone.net


To:   ebxml-dev list <ebxml-dev@lists.ebxml.org>
cc:
Subject:  Re: FYI: Article on ebXML and Interoperability



Interesting analysis.  It confirms some of my suspicions about ebXML, but
they
vary slightly.  One of them being ebXML is far too complicated to gain wide
acceptance, and far too ambiguous to function as a guide.  Both of these
contribute to the cost of attempting an ebXML initiative within a company,
and
because of their scope, it becomes financially infeasible.

What I am, and I expect others are, looking for is a base template of
messages
to exchange with trading partners.  I want to know *how* we're going to
find
each other on the net, how we're going to identify each to the other, what
the
format and content of our messages will be, and what documented and
agreed-to
extensions there might be.

It seems odd that Automated Teller Machine networks can publish
documentation
describing all these things, and that programming staffs at various
institutions can readily implement them, even with extensions (like support
for Point-of-Sale terminals).  Additionally, there are resources for
testing
your implementation and achieving a certification/verification status that
your interface works properly.

I am anxiously awaiting some type of implementation document describing how
to
implement an ebXML (or any other business protocol standard) compliant
system
without having to spend US$500,000.  Unless it can be made practical I
don't
see how it can achieve any kind of traction, regardless which big-boys
announce their support for it.

--
.tom

----------------------------------------------------------------
The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>