Merging XML is particularly tricky, but often necessary to consolidate data feeds from heterogeneous systems, or to synchronise submissions of XML fragments which make up a larger document.
An automated mechanism for defining and controlling such merges has been developed and is demonstrated to provide a consistent, adaptable and resilient solution to this problem. Integration into an information pipeline allows limitless customisation.
As XML becomes ubiquitous so the need for powerful tools to manipulate XML data becomes more pressing. As XML tools become more powerful, so the possibility of achieving a genuine, intelligent merge of XML data sets becomes a reality.
Merging XML documents is a particularly tricky operation but is often required to consolidate or synchronise two or more independent edit paths or versions. As XML tools become more powerful, the possibility of achieving an intelligent merge of XML data sets become reality.
It’s common to have data in two files that we need to merge together, two different people or two different processes have made changes. Does it matter who or what has made this change? This question might help to decide whether you need a 2-way or 3-way merge.
Branch and merge may be a software developer’s dream, but using this technique with structured documents can turn into a nightmare. The merge process is so often a manual one: cut and paste and get frustrated. Can structured XML merge turn the nightmare back into a dream?