Message text written by "eberhard speer jr."
>Folks,
it seems to me to both are 'right' but that they both live in a different
universe.
<<<<<<<<<<<<
Not so, the critical factors are NOT the mapping or the formatting
themselves. Anyone can do simple mapping in whatever ad hoc
fashion they deem fit. Any manager of a serious company knows
that such an unscientific approach leads toward a very expensive
path, where support costs overrun, and resources capable of
supporting such a 'built-on-the-fly' solution are hard to come-by
and then retain, not to mention the costs of maintaining proprietary
rather than broader industry formats.
What the ebXML initiative is rightly focused on is solving the
complete solution - not just what the tag names are. The operational
issues, versioning, authentication, business semantics exchange
and core shared repository definitions are some of the major items.
Simply taking an EDI message and adding an XML veneer fools
noone when it comes to deploying mission critical, bet-your-business
solutions, rather than cute pilots and PR grabbing partnering.
DW.
==========================================
XML/EDI Group members-only discussion list
Homepage = http://www.xmledi.com
Brought to you by: Online Technologies Corporation
Home of BizServe - www.bizserve.com
TO UNSUBSCRIBE: Send email to <[EMAIL PROTECTED]>
Leave the subject blank, and
In the body of the message, enter ONLY: unsubscribe
Questions/requests should be sent to: [EMAIL PROTECTED]
To join the XML/EDI Group complete the form located at:
http://www.geocities.com/WallStreet/Floor/5815/mail1.htm
