XML/EDIFACT
XML/EDIFACT combines EDIFACT content with XML syntax. XML/EDIFACT is used in B2B practice for the reasons
1) Newer EAI or B2B systems, e.g. SAP XI, often cannot handle EDI (Electronic Data Interchange) syntax directly. Simple syntax converters do a 1:1 conversion before. Their input is an EDIFACT transaction file, their output an XML/EDIFACT instance file.
2) It keeps XML B2B transactions relatively small. XML element names derived from EDIFACT tags are much shorter and more formal than those derived from natural language. Such formal tags, the "EDIFACT modelling language", are readable by B2B experts worldwide.
3) It reuses business content defined in UN/EDIFACT. Since 1987, the UN/EDIFACT libary was enriched by global business needs for all sectors of industry, transport and public services. For XML, there is no such comprehensive vocabulary available.
The rules for XML/EDIFACT are defined by ISO TS 20625.
Example 1: Pure EDIFACT
An NAD segment, containing customer ID and customer address, expressed in EDIFACT syntax:
NAD+BY+CST9955::91++Candy Inc+Sirup street 15+Sugar Town++55555'
Example 2: XML/EDIFACT
The same information content in an XML/EDIFACT instance file:
<S_NAD><D_3035>BY</D_3035><C_C082><D_3039>CST9955</D_3039><D_3055>91</D_3055></C_C082><C_C080><D_3036>Candy Inc</D_3036></C_C080><C_C059><D_3042>Sirup street 15</D_3042></C_C059><D_3164>Sugar Town</D_3164><D_3251>55555</D_3251></S_NAD>