Cultural Heritage markup can quickly become complex because of the need to represent multiple, and even overlapping, hierarchical structures. It can therefore become very difficult to maintain correctly.
This talk suggests that a better approach is now possible: markup that is designed to represent different aspects of a text could be handled separately from the point of view of checking and maintenance, and then only combined into a single document when needed, e.g. for some kind of analysis. Advances in comparison and merge tools for XML make this a possibility.
This paper describes how a divide-and-conquer approach might be used to handle the complex markup structure that results from recording multiple variants of an historical document in a single XML document.
The issue of how best to represent overlapping hierarchy in XML has been the topic of a number of papers over the years. This paper is a further contribution to this important issue but approaching the problem from a different direction.
DeltaXML and DeltaJSON products look within the structure of your data to identify relevant differences, so you can diagnose, debug and process data efficiently.
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.