For block elements such as <li> that can have more than one possible ancestry, map any paragraph formats to the intended (required) parent element, and if necessary, grandparent element, even great-grandparent element. List ancestors in hierarchical order. Specify a parent only if it is required to prevent incorrect output. If you find "Parent Error" comments in the resulting XML, first try commenting out any related parent assignment in [DITAParents].
Note: Do not specify parents for paragraph formats that are part of a FrameMaker table. If necessary you can specify parents for the contents of table cells, but do not go above <entry>. See §22.214.171.124 .
Therefore, each Numbered1 paragraph starts a new <ol> if and only if an <ol> is not already open; and starts a new <li> if and only if an <li> under the <ol> is not already open. To force a new <ol><li> for Numbered1 paragraphs, you must also give the Numbered1 paragraph format first-child status under both parent and grandparent elements; see §14.5.6 .
If a parent element has more than one possible parent, and only one of those parents can be a grandparent of the paragraph format in question, list both the grandparent and parent, in hierarchical order.
To override the [DITAParents] assignment for a given instance of a paragraph format, place a DITAParent marker in the paragraph. Make the content of the marker the name(s) of the ancestor element(s), in hierarchical order. A DITAParent marker specifies the required ancestry for the current block element, overriding whatever is specified in [DITAParents].
Although you can specify ancestors for tables (see §14.6.2 ), do not specify parents for paragraph formats that are part of a FrameMaker table. Mif2Go uses a different mechanism for table components. You can specify parents for the contents of table cells, but do not go above <entry>. See §126.96.36.199 .