Duane, I agree with you on all except one minor point, which I must clarify so as not to perpetuate a misunderstanding. EDI is not specifically an "ASCII" format for data. X12 EDI only specifies the graphical character set. It can, and often is, rendered in character encodings other than ASCII, such as EBCDIC. For UN/EDIFACT, "the 7-bit codes in the basic ISO 646 standard shall be used, unless the corresponding 8-bit codes in ISO 6947 and 8859 or other bit codes are specifically agreed between the interchanging partners." That from ISO 9735 V2, and I doubt that V4 is much different. Cheers, Mike At 08:44 AM 7/13/2004 -0700, Duane Nickull wrote: >They are comparing apples and oranges. EDI is an ASCII format for data, >ebXML is an infrastructure. EDI may be used within the ebXML infrastructure. > >Accordingly, finding that the infrastructure is larger than one of it's >components is understandable and I would agree with the author of this email. > >Furthermore, it is my belief that any technology needs to be "hidden" >before it will be successful. I did not have to know SMTP in order to send >this email - the clever engineers at Netscape hid all that from me and >presented me only with a "send" button. Same with clicking on a >hyperlink. One does not have to know anything about HTTP. > --------------------------------------------------------------- Michael C. Rawlins, Rawlins EC Consulting www.rawlinsecconsulting.com Using XML with Legacy Business Applications (Addison-Wesley, 2003) www.awprofessional.com/titles/0321154940 The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The list archives are at http://lists.ebxml.org/archives/ebxml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://www.oasis-open.org/mlmanage/>
<<attachment: winmail.dat>>