32.4.1 Content model [Topic] settings
The following content-model settings specify information for either a DITA or a DocBook content model:
; TopicRoot = name of root element for this content model.
; PrologDType = PUBLIC name used in DOCTYPE header.
PrologDType = "-//OASIS//DTD DITA Concept//EN"
; PrologDTD = SYSTEM name, such as "concept.dtd", can include a path.
PrologDTD ="http://docs.oasis-open.org/dita/v1.1/CD01/dtd/concept.dtd"
; ModelName = name of content model.
TopicRoot is the name of the root element for the content model. For DITA, TopicRoot is the name of one of the built-in topic types: topic, concept, task, reference, map, or (for DITA version 1.1) glossary.
Double quotes are required for the PUBLIC name and the SYSTEM name. If the SYSTEM name is less than 16 characters long, you must prefix the name with two spaces. For example:
Mif2Go always removes the first space after the equals sign, and retains any subsequent spaces. DOCTYPE styles differ: some require an indent, some prohibit an indent, some want a return, some do not. Mif2Go includes a return automatically if (and only if) the SYSTEM name is more than 16 characters long. Therefore a shorter SYSTEM name requires a leading space, to separate it from the preceding PUBLIC name when the DOCTYPE header is generated.
If you are providing a replacement content model, ModelName specifies the name of the built-in content model to be replaced by the current content model. ModelName is effective only when the current content model is listed in [DITAContentModels], or specified for [DocBookOptions]ContentModel, in your project configuration file.
The following settings apply only to DITA content models:
; TopicStart = name of element that starts topic, such as "glossterm"
; (for glossary) or "title" (for every other type).
; TopicBody = name for its body element, such as conbody for concept.
; TopicDerivation = name of type from which it is derived.
See §32.7 Specializing or modifying DITA topic types.
> 32 Working with content models > 32.4 Understanding content-model configurations > 32.4.1 Content model [Topic] settings