Chapter 1. Customizer's Guide for the DocBook DTD

[Prev] [Next]


1.2 Reusing Individual DocBook Modules

To reuse specific DocBook modules, reference them from within your own DTD driver file, making sure to use the preferred formal public identifiers for them. Though you could also reference them from an internal subset, if you are supplying a significant amount of markup structure you're likely to want to use the same DTD with many documents, and will want to store them in their own file.

For example, here is a new DTD for software product ``release letters'' that uses the whole DocBook information pool:

<!ENTITY % infopool PUBLIC
"-//Davenport//ELEMENTS DocBook Information Pool V2.3//EN">
%infopool;
<!ELEMENT ReleaseLetter - - (Title, ProductNumber, RevHistory,
 (%component.mix;)*, LetterSect*)>
<!ATTLIST ReleaseLetter
        %common.attrib;
        Status         (Draft|Shipped)         #IMPLIED
>
<!ELEMENT LetterSect - - (Title, TitleAbbrev?, (%component.mix;)*)>
<!ATTLIST LetterSect %common.attrib;>


[Prev] Setting Up DocBook for Customization
[Next] Customization Specifics
[Customizer's Home] [Davenport Group Home]