#### 24.5.6 Avoiding invalid ancestries

For the purpose of constructing ancestries, by default DITA2Go 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 DITA2Go 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 DITA2Go 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), a paragraph whose format is Body will be allowed as a <body> element n a reference topic, where <body> is not valid.

See also:

§24.5.5 Specifying alternate ancestries for the same element

Previous Topic: 24.5.5 Specifying alternate ancestries for the same element

Next Topic: 24.5.7 Specifying first-child status for nested elements

Parent Topic: 24.5 Nesting DITA block elements

Sibling Topics:

24.5.1 Understanding how DITA2Go determines element nesting

24.5.2 Designating DITA ancestor elements

24.5.3 Fixing up interpolated ancestries

24.5.4 Deciding when to fully specify ancestry

24.5.5 Specifying alternate ancestries for the same element

24.5.7 Specifying first-child status for nested elements

24.5.8 Configuring nested lists

24.5.9 Closing DITA ancestor elements

24.5.10 Opening DITA ancestor elements

24.5.11 Configuring multi-paragraph list items

24.5.12 Specifying DITA element levels

Table of Contents • Index