#### 26.1.2 Understanding what information you must supply

DITA2Go does not try to validate the output; you must use a validating parser to check output validity. However, DITA2Go does ensure valid parental relationships and first-child restrictions. Valid sequence of items within those constraints has to come from the implied or explicit structure of the DITA document.

DITA2Go support for DocBook requires you to supply the following kinds of information in addition to your DITA document:

DTD properties

DITA mappings

DTD properties

DITA2Go provides two built-in configurations for content models for DocBook version 4.5: one for articles, and one for books.

If you need to modify one of these content models, you can download a copy from Omni Systems; see §41.2.1 Obtaining a copy of a built-in content-model. However, the only valid purpose for modifying a built-in content model would be to correct settings for element types. See §41.6 Inspecting and correcting element types.

To replace a content model, use free command-line utility dtd2ini to generate a content model from another DTD, and produce a content-model configuration file for your DocBook project. See §41.2.2 Generating a content model from a DTD.

DITA mappings

You must map formats to DocBook elements. This information goes into configuration file d2docbook.ini, and possibly into chapter-specific configuration files. You might have to use PI marker in your DITA document to provide information such as topic IDs, element names, and attributes, in cases where these items cannot be derived from the document.

Previous Topic: 26.1.1 Understanding what you need to know about DocBook

Next Topic: 26.2 Setting up a DocBook XML project

Parent Topic: 26.1 Generating DocBook XML with DITA2Go

Sibling Topics:

26.1.1 Understanding what you need to know about DocBook

Table of Contents • Index