- 3 - XML Explained Michael Broberg/Lalith Reddy, Jun 2000 © 2001 Sixhills Consulting Ltd & Author through XML. By letting clients browse, search, and view data locally, this division of labour eliminates the need for multiple queries to the server, which updates displayed information only as needed. This in turn, means faster access to information for the user. Dynamic mapping and routing. XML/EDI scripting can specify how XML-defined elements or objects must be processed. For example, scripting may define how a document is to be displayed or, if the document is an EDI transaction, how it is to be mapped. Scripting can also further define rules to integrate transactions into existing workflow processes or back-end applications. Forms for seamless integration. To help integrate XML with your current EDI processes, you can have your users complete forms that generate XML/EDI messages to be transmitted via the Internet or traditional VANs. Once a standard XML/EDI-capable browser receives a message, the EDI data can be easily interpreted using predefined rules for displaying or integrating the data with application systems. This method eliminates the need for custom program development, which is often required in a traditional EDI environment. An example of XML code to generate a Purchase Order <?xml version ="1.0" ?> <!DOCTYPE Order SYSTEM "C:\\xml\dtds\order.dtd"> <Order> <MessageID type="Autogenerate"/> <Date>19991105</Date> <RefersToDocType="ContractNo" DocID="652744"/> <Buyer> <EAN>5012345678900</EAN> </Buyer> <Supplier> <EAN>6012345678900</EAN> </Supplier> <OtherParty Role="Carrier"> <EAN>7012345678900</EAN> </OtherParty> <OtherParty Role="ShipFrom"> <EAN>7012345678950</EAN> </OtherParty> <OtherParty Role="DeliverTo"> <Name>The Village Store</Name> <AddressLine>2 The Reddings</AddressLine> <AddressLine>Cheltenham</AddressLine> <AddressLine>Glos. GL51 2UP</AddressLine> </OtherParty> <Item> <ItemID Agency="EAN">37534656</ItemID>
< Page 2 | Page 4 >