XML/EDI is not just hype - it will become a reality. However, many pieces will have to fall into place before this dream is realized. Vendors of traditional EDI software must begin to plan on supporting XML/EDI or be superseded in the marketplace. XML/EDI products should begin to hit the market by the first half of 1999 and by the year 2002 XML/EDI standards, technologies, and products should be ready for mainstream deployment. Standards bodies such as ASC ANSI X12/DISA and CEFACT, therefore, must quickly adapt and shift away from the traditional EDI paradigm in order to support the XML/EDI. The document-processing model of XML/EDI is different from what is practiced with traditional X12/EDIFACT-based batch EDI. We all must agree on a standard methodology for encoding the necessary elements and attributes in the XML markup that is needed for providing backward compatibility to legacy EDI applications. This is essential and must occur before standard translators for legacy EDI standards can be developed. Traditional VANs should rethink their business strategy to embrace XML/EDI services for SMEs. To gain the maximum benefits of XML/EDI, users will eventually need to implement new EDI processes and new data management processes. There is a belief that more resources, more international coordination, and more influence is needed for the standards bodies to withstand the rapid demands of industry beyond the next two years.
Currently, XML/EDI is somewhere between the embryonic and growth phases of its life-cycle. In the near term, there are some critical issues that remain unresolved. These issues must be resolved for the XML/EDI standard to move forward. Some of these issues include the following:
1. How do we leverage the work already done on data dictionaries by X12 and EDIFACT?
2. What is the business case for creating and sustaining XML/EDI repositories?
a. How do we identify where an element comes from?
b. How do we maintain version control of the standards and DTDs?
c. How do we manage whether the element from X12 or EDIFACT or an industry group?
3. Who will standardize how EDI information is structured and named using XML?
4. Do we support both X12 and EDIFACT in a dual capacity?
5. How do we establish data dictionaries that do not currently exist in EDI?
6. How do we make the data dictionaries usable to general-purpose electronic commerce applications?
