Configure the custom topic shell DTD
After creating a custom DTD plugin that includes a renamed copy of IxiaDitabase.dtd (CompanyDitabase.dtd), you need to make a few changes to your custom topic shell DTD.
- Check out and open CompanyDitabase.dtd.
- At the beginning of the file, edit the header to reflect an appropriate name, version, and date
for the DTD.
<!-- ============================================================= --> <!-- HEADER --> <!-- ============================================================= --> <!-- MODULE: COMPANY DITA BASE DTD --> <!-- VERSION: 1.0 --> <!-- DATE: October 2016 --> <!-- --> <!-- ============================================================= -->
-
Just after that, edit the public identifier to be something
unique, and change the file name to match your filename.
<!-- ============================================================= --> <!-- PUBLIC DOCUMENT TYPE DEFINITION --> <!-- TYPICAL INVOCATION --> <!-- --> <!-- Refer to this file by the following public identfier or an appropriate system identifier PUBLIC "-//COMPANY//DTD DITA Composite//EN" Delivered as file "CompanyDitabase.dtd" -->
Remember that public identifiers are resolved through the catalog. You do not want a catalog to have duplicate identifiers pointing to different resources, as that will create confusion and problems with validation. You want to be sure that your DTD has a completely unique identifier. This section of the DTD does not connect the DTD and its public identifier in any way, but it is good to document what the identifier in the catalog is.
- Optional:
Delete the following section, or use it to keep a revision
history of the file.
<!-- ============================================================= --> <!-- SYSTEM: Darwin Information Typing Architecture (DITA) --> <!-- --> <!-- PURPOSE: Base DTD holding all the information types --> <!-- used by IXIASOFT --> <!-- --> <!-- ORIGINAL CREATION DATE: --> <!-- January 2006 --> <!-- --> <!-- ============================================================= -->
-
At the end of CompanyDitabase.dtd, change the "End" comment as shown.
<!-- ============= End Customer DITA Base DTD ============= -->
- Save and check in CompanyDitabase.dtd.
Next, you need to create your own map shell DTD and add it to your plugin.