DeltaXML’s algorithms work through each of your files in turn, examining their structure to match-up all the corresponding elements with the original.
XML Compare identifies all of the differences in your content according to your specific configuration. It then writes them to an output file which combines your original content with new markup detailing the changes.
Display the changes from XML Compare or XML Merge in an XML editor to manually accept or reject changes. Or apply custom rules to automatically determine whether to accept the changes or mark them up in the output file as unresolved changes.
The results are passed through a pipeline so you can transform the XML into whatever form is required by your systems or processes. This is all managed through DeltaXML’s API.
If you’re wanting to see all DeltaXML has to offer book a one-to-one demo with a DeltaXML developer.
In XML, text formatting uses structural markup like
strong to add styling to text content. DeltaXML handles this markup with specific processing so that you have a clear understanding of where text remains unchanged despite formatting changes. Even where text remains the same, our compare and merge delta format shows you how formatting changed between versions.
XML tables are complex enough without having to worry about how to compare and merge them. We process CALS and HTML tables to make sure that the results are valid against the table models while still delivering accurate comparisons and merging.
MathML handling is built into XML Compare’s ‘Document Comparator’. When MathML content inside your documents is compared, change highlighting is created using MathML syntax to add coloring and styling to your MathML. Three different output styles allow you to choose the one that best suits your publication.
Comparison results can be configured to show in any form you need, whether for automated processing or human review.
When the aim of a merge is to reach a new version of a document, you’re often only interested in reviewing the conflicting changes. XML Merge allows you to automatically ‘accept’ changes that don’t conflict, only marking up those that are in conflict. This reduces the time needed to review the result. Of course if you do want to review all differences between the documents, including those which don’t conflict, that’s still possible. In fact you can determine which changes should be included in the result using our rule-based processing feature.
Sometimes you don’t need to see every tiny change, especially for content that you know will change, like dates and timestamps. That’s why we offer samples showing you how to configure XML Compare to ignore these insignificant changes. All you need is a custom XSLT transformation plus a couple more that we’ve already written for you.
Whether you choose to include all changes or just those that conflict across versions, the changes are output in our simple XML-based delta format for easy processing. Designed to be easily transformed using XSLT, our delta format sits lightly within the original XML content to ensure that your results are as close as possible to the original XML format.
XML is often used as the output from applications and processes, particularly for web APIs. When implementations change it is important to prove that expected output remains consistent with regression testing. But often, the layout or ordering of the XML output is inconsequential to the success of the test or perhaps the output contains data that will always be different from one run to the next. With its ability to ignore specific changes and its built-in algorithms for ignoring the ordering where appropriate, XML Compare has proven to be a vital component in regression testing XML output.
When it comes to reviewing documentation, combining the suggested edits or comments from multiple reviewers can be a time-consuming task. You could make sure that only one person at a time is allowed to make review changes but even then, how do you know who made which changes? To speed things up, XML Merge enables a concurrent reviewing process. After sending a document out to as many reviewers as you like, XML Merge will merge the reviewed versions back together into a single document, allowing you to see where multiple people suggested the same changes, where there are conflicting changes, and where simple changes have been made.
When you publish documents, like standards, that are relied on as a key part of your customers’ work it can be difficult for them to manage the transition to an updated version. Many customers, including standards bodies (international, national and industry-specific), use XML Compare to drive a redline document workflow. XML Compare identifies the changes between publication versions, marks them in the source XML and the resulting delta feeds into the usual publication workflow where styling is added to changed content to help your customers to understand exactly what updates appear in this latest revision.
What is the DeltaXML package?
DeltaXML is a package consisting of the toolkits XML Compare and XML Merge. While XML Compare finds all of the meaningful changes between any two XML files, XML Merge recombines multiple XML documents or datasets into a single file.
How do I integrate or embed the DeltaXML package?
Both XML Compare and XML Merge are optimised for integration into any enterprise workflow and content management systems. All of their functionality is accessed through Java or REST APIs, which are fully documented and come with complete, working examples. On top of these API’s we have created plugins for popular XML authoring tools, including oXygen and FrameMaker for seamless content authoring and reviewing.
Can I ignore changes I know about?
Yes. DeltaXML can be configured to tell you about the differences that matter to you and ignore those that don’t, including changes to attributes, the order of content, differences in whitespace and external links.
If you are working with documents or textual content, you have fine control over differences between words, sentences and whole blocks of text. XML Compare also allows you to specify how formatting changes are reported, while XML Merge can apply custom rules to specify what is merged automatically and what is marked-up for further attention.
How is DeltaXML different from other diff tools?
Rather than comparing XML line-by-line, DeltaXML identifies and matches up all the XML elements across your files, so it has a meaningful and dependable basis for comparing and merging your content.
This pairing process uses a combination of element names, parent names, position in the XML tree and the structure of child elements. It understands namespaces and prefixes and can be configured to use keys to guide alignment of content.
How are found differences represented?
DeltaXML generates output files that are structured in the same way as your original files, so they can be viewed in your regular editor or managed in your CMS. With XML Merge an output file which is based closely on your original ancestor file will be generated, with all unresolved changes laid-out using precise, descriptive XML markup.
The real power comes from its use of XSLT pipelines, which enable you to apply transformations and generate the exact output that you require, for internal workflow, wider distribution or in your product code.
How do I buy a DeltaXML package license?
So you’re only paying for what you need we offer a range of license models dependent on the system architecture you’re using and your current use case. Fill in our get a quote form to receive more details on your pricing options.
If you have a question you cannot find the answer to please complete the form below and we’ll get back to you as soon as possible.
So you’re only paying for what you need our licensing options are dependent on how you’ll be using our software. Get a quote by clicking the button below.
If you need assistance with a product evaluation or you’re a customer with a technical question about any of our products please head over to our support portal.