Vol. 8, No. 1 February, 2000 ™ !!! www.gilbane.com Published by: Bluebill Advisors, Inc. (617) 497.9443 Fax (617) 249.0424 www.bluebilladvisors.com XML, EDI, CONTENT & COMMERCE Editor: It is a bit surprising how much confusion exists over the relation between Frank Gilbane
[email protected] XML and EDI. There are certainly some special interests contributing to (617) 497.9443 the confusion but there is remarkably little discussion regarding the mi- Associate Editors: nor controversy not conducted in good faith. This is not a complicated Michelle Berrong issue, but is one you need to understand to avoid wasting resources.
[email protected] (781) 871.9000 Leonor Ciarlone The way to think about the XML versus EDI question is to step back and
[email protected] look at the bigger picture of e-commerce. EDI was created to grease the (781) 871.9000 Mike Maziarka wheels of commerce by facilitating rapid and frictionless exchange of
[email protected] business documents. Mostly these documents looked more like struc- (781) 871.9000 Bill Trippe tured databases than documents. This structure allowed EDI to be simple
[email protected] and reliable. Although EDI was created in a commerce environment that (781) 662-6672 was stable and well understood there were still opposing views about the Subscriptions: best way to encode simple business documents, as the competition be-
[email protected] tween ANSI X12 and EDIFACT showed. (617) 497.9443 Customer Service:
[email protected] Nonetheless, the relative success of EDI naturally raised the question: "Why can’t we use EDI to exchange all these other documents as well?" The answer was that most documents were not as structured and pre- dictable as a purchase order or invoice was.