Omni Systems, Inc. |  | Mif2Go User's Guide, Version 55 |  |  |  |  |

> 15 Converting to DITA XML > 15.5 Nesting DITA block elements > 15.5.6 Avoiding invalid ancestries

### 15.5.6 Avoiding invalid ancestries

For the purpose of constructing ancestries, by default Mif2Go treats topic as a synonym for concept, task, reference, glossentry, and any other topic type, and treats body as a synonym for any of the body types, such as conbody. This can cause invalid interpolated ancestries, because Mif2Go might include an element, or wrap an element in a parent, that is not valid for the topic type.

To avoid this problem and direct Mif2Go to treat topic and body as applying only to the generic topic type:

[DITAOptions]

; UseCommonNames = Yes (default, in [DITAParents] and

; in [DITAElementSets], treat "topic" as a synonym for

; concept, task, reference, glossentry, and any other

; topic type, and treat "body" as a synonym for any of

; the body types like conbody), or No (treat topic and

; body as applying only to the generic "topic" type)

UseCommonNames = No

For example, when UseCommonNames=Yes (the default) and UseFormatAsTag=Yes (see §15.4.2 Treating FrameMaker format names as DITA element names), a paragraph whose format is Body will be allowed as a <body> element n a reference topic, where <body> is not valid.

See also:

§15.5.5 Specifying alternate ancestries for the same element

> 15 Converting to DITA XML > 15.5 Nesting DITA block elements > 15.5.6 Avoiding invalid ancestries

| Mif2Go User's Guide: 15.5.5 Specifying alternate ancestries for the same element |  | Mif2Go User's Guide: 15.5.7 Specifying first-child status for nested elements |