1. EDI to XML The following slides provide a brief comparison of traditional X12 EDI and XML. We have used a simple receipt schedule to show how the two data formats would convey the same information.

2. EDI Schedule, Product and Mode Segments

3. EDI Origin and Seller Segments

4. EDI Carrier and Destination Segments

5. EDI Bill of Lading Date and Gallons Segments

6. XML Schedule Structure

7. XML Location Structure * MFLocationType used for Origin, Destination and Revised Destination detail

8. XML Participant Structure * MFParticipantType used for Carrier, Seller and Purchaser detail

9. Compare EDI and XML Output EDI segment for Schedule, Product and Mode TFS~T3~3A~PG~065~94~J \ XML for Schedule, Product and Mode elements 3A 065 J

10. EDI Receipt Schedule Output TFS~T3~3A~PG~065~94~J \ N1~OT~~TC~T62TN2200\ N1~SE~FUNKY FUEL INC.~24~137777777\ N1~CA~HAULING STUFF~24~591234567\ N1~WD~~FA~018500002\ FGS~D~BM~ SampleRec\ DTM~095~20090211\ TIA~5005~~~1065~GA\

11. XML Receipt Schedule Output 3A 065 J SampleRec 20090211 T62TN2200 018500002 591234567 HAULING STUFF 137777777 FUNKY FUEL INC. 1065

12. EDI to XML This simple example was designed to help with the understanding of how XML relates to legacy EDI data structures. We hope this will aid those states that currently use EDI to capture their return data, but are considering moving to XML. Obviously, there are other components such as the header and financial transaction that are shared with the MeF program. TIGERS and the Motor Fuel Uniformity Committee have created the XML needed to process the Supplier, Operator, Distributor, Carrier and Retailer reports. You can access the most current version of the Motor Fuel Schemas via the TIGERS Webpage.