16.2.5.5 Specifying a collection-type attribute for each topic type

To specify a collection-type attribute for a topic type in a Mif2Go-generated relationship table for a chapter map:

[DITARelGroups]

; DITA type name = collection-type attribute to use in the <colspec>

;  for the chapter map <reltable> column for that DITA type.

topictype = colltype

To specify a collection-type attribute for a topic type in a relationship table for a book map:

[DITARelBookGroups]

; DITA type name = collection-type attribute to use in the <colspec>

;  for the book map <reltable> column for that DITA type.

topictype = colltype

If you do not include a setting for a topic type in [DITARelBookGroups], Mif2Go uses the setting for that topic type (if any) in [DITARelGroups] for the relationship table for the book map.

We suggest the following collection-type attributes; however, you can specify others: 

family	(equivalent to the usual ALink behavior)
sequence	(links are in order of appearance in the chapter)
choice	(processor dependent)

The default is no collection-type, so that topics in that column do not link to each other, but only to topics in other columns in the same row.

For example:

concept = family

task = sequence

These settings would yield the following results:

• Concept topics would link to other concepts, and to task and reference topics in the same row (same DITARelRow value; see §16.2.5.3 Adding ALink rows to relationship tables).

• Task topics would link to each other as an ordered set, and to concept and reference topics normally.

• Reference topics would link to tasks and concepts in the same row, but not to each other.

---

> 16 Configuring DITA maps > 16.2 Configuring DITA ditamaps > 16.2.5 Adding relationship tables to ditamaps > 16.2.5.5 Specifying a collection-type attribute for each topic type