Compare XML Schemas

XML Schema comparison by mapping in Altova DiffDog

DiffDog XML Schema Mapping:

  • Automatic connection of identical child elements
  • Generate XSLT to transform XML data files
  • Send XSLT directly to XMLSpy
  • Generate MapForce mappings between XML Schemas
  • Save XML Schema comparison settings for re-use

Download Trial

Compare XML Schemas by Mapping

DiffDog® 2017 includes powerful XML Schema differencing functionality that extends and complements XML-aware file comparison of .xsd documents and eases conversion of XML data.

XML developers frequently need to modify and enhance XML Schemas as XML-based applications are created. Similarly, users of industry-standard XML-based data exchange systems need to update XML file formats to maintain compatibility with evolving standards. Along with its XML file comparison capabilities, the DiffDog XML Schema compare tool helps you efficiently update XML data files when XML Schemas change.

Simply choose Compare XML Schemas from the File menu or the DiffDog tool bar, select two XML Schemas, and click the compare button. The DiffDog Schema comparison tool automatically maps schema elements with the same names.

You can select different root elements for each XML Schema, and you can also manually connect dissimilar elements to map them, or override automatic element mappings.

Transformations for XML Data Files

After you map two XML Schemas, DiffDog lets you generate an XSLT file to transform existing XML documents for the new schema by clicking either Copy button on the DiffDog toolbar or via a context menu in the comparison window. This saves time and effort over writing and debugging XSLT code by hand.

You can create an XSLT file for left-to-right or right-to-left translation.

A portion of the XSLT file for the example mapping is shown at the right. Every feedback element in the source will be saved as an email element in the output (lines 12-16).

Portion of an XSLT file generated by DiffDog

Save Mappings for Altova MapForce

DiffDog lets you generate a fully editable MapForce mapping file between the schemas. In our example, the XML Schema on the right contains the publication element, with no corresponding element on the left. As one option, MapForce lets you define a string constant or apply another data processing function to fill that value during transformation.