14.5.1 Understanding how Mif2Go determines element nesting
For each element, Mif2Go considers whether that element can go inside the current parent element. If not, Mif2Go uses heuristic methods based on the possible parents, level limitations, and current context. Mif2Go does not interpret the DTD to determine element nesting.
For example, suppose your document uses a sequential structure for steps in a procedure: paragraph format Step1 for the first step, followed by several StepNext paragraphs. To convert this structure to a hierarchical DITA structure, with paragraphs in both formats becoming <step> children of a <steps> element, you would specify just one setting (see §14.4.3 Mapping paragraph formats to DITA elements):
The first paragraph in the group forces creation of <steps>, because DITA requires <steps> as the parent of <step>. As soon as Mif2Go encounters a paragraph format that is not valid in <steps>, the parent tag is closed.
For problem cases, you can use a DITALevel marker to explicitly set the level for an element; see §14.5.11 Specifying DITA element levels. However, for nested lists, use a different approach; see §14.5.5 Specifying alternate ancestries for the same element.
> 14 Producing DITA XML > 14.5 Nesting DITA block elements > 14.5.1 Understanding how Mif2Go determines element nesting