Update your custom map shell

These steps assume a plugin name of com.company.dita.dtd and a topic shell name of CompanyMap.dtd. The steps also assume that com.company.dita.dtd is in system/plugins.

These steps also assume that your map shell is essentially a copy of IxiaMap.dtd. If you have integrated additional element or attribute domains, you must make appropriate changes to those entity declarations which this procedure cannot anticipate.

Open system/plugins/com.ixiasoft.dita13.dtd/dtd/IxiaMap.dtd.
Check out and open system/plugins/com.company.dita.dtd/dtd/CompanyMap.dtd.
In CompanyMap.dtd, find the MAP ENTITY DECLARATIONS section.
Compare each entity in the section to the corresponding entity in the MAP ENTITY DECLARATIONS section of IxiaDitabase.dtd. For example:
```
(CompanyMap.dtd)
<!ENTITY % bookmap-dec 
  PUBLIC "-//OASIS//ENTITIES DITA 1.2 BookMap//EN" 
         "../../../dtd/bookmap/dtd/bookmap.ent"
>%bookmap-dec;
```
```
(IxiaMap.dtd)
<!ENTITY % bookmap-dec 
  PUBLIC "-//OASIS//ENTITIES DITA 1.3 BookMap//EN" 
         "../../org.oasis-open.dita.v1_3/dtd/bookmap/dtd/
         ¶bookmap.ent"
>%bookmap-dec;
```
Note: The ¶ symbol indicates a manual line break that has been inserted here for formatting. There should be no actual line break in the code.

Notice that the public id of the entities in IxiaMap.dtd (which uses DITA 1.3) references DITA 1.3. Notice also that the relative path in the system id of the entities in CompanyMap.dtd point to the DITA 1.2 DTDs that are in system/dtd while the relative path in the system id of the entities in IxiaMap.dtd point to the DITA 1.3 DTDs that are in system/plugins/org.oasis-open.dita.v1_3/dtd.
Change the public id of each entity in the MAP ENTITY DECLARATIONS section of CompanyMap.dtd to reference DITA 1.3 rather than DITA 1.2.
Change the relative path in the system id of each entity in the MAP ENTITY DECLARATIONS section of CompanyMap.dtd to point to the DITA 1.3 DTDs that are in system/plugins/org.oasis-open.dita.v1_3/dtd rather than the DITA 1.2 DTDs that are in system/dtd.
You can select just the ../../../ part of each path and replace it with ../../org.oasis-open.dita.v1_3/. The remainder of the path is always the same.
Important:
This simple replacement depends on your DTD plugin being in system/plugins
and having exactly this structure:
```
system
|_plugins
  |_com.company.dita.dtd
    |_dtd
      |_CompanyDitabase.dtd
      |_CompanyMap.dtd
```
If your plugin is in any other location or if the folder structure differs (for example, your DTDs are in a subfolder of the /dtd subfolder, or they are not in a /dtd subfolder at all), you must calculate the correct relative path between CompanyMap.dtd and the DTDs in org.oasis-open.dita.v1_3.
Add the following to the MAP ENTITY DECLARATIONS section of CompanyMap.dtd.
```
<!ENTITY % subjectScheme-dec 
  PUBLIC "-//OASIS//ENTITIES DITA Subject Scheme Map//EN" 
         "../../org.oasis-open.dita.v1_3/dtd/subjectScheme/dtd/
         ¶subjectScheme.ent"
>%subjectScheme-dec;
```
Note: You can add this anywhere in the MAP ENTITY DECLARATIONS section; the order of the declarations does not matter.
Repeat the same comparison and update to public and system id's for each entity in the DOMAIN ENTITY DECLARATIONS section of CompanyMap.dtd.

Add the following to the DOMAIN ENTITY DECLARATIONS section of CompanyMap.dtd.

<!ENTITY % ditavalref-d-dec
  PUBLIC "-//OASIS//ENTITIES DITA 1.3 DITAVAL Ref Domain//EN"
         "../../org.oasis-open.dita.v1_3/dtd/base/dtd/
         ¶ditavalrefDomain.ent"
>%ditavalref-d-dec;

<!ENTITY % markup-d-dec 
  PUBLIC "-//OASIS//ENTITIES DITA 1.3 Markup Domain//EN" 
         "../../org.oasis-open.dita.v1_3/dtd/technicalContent/dtd/
         ¶markupDomain.ent"
>%markup-d-dec;

<!ENTITY % relmgmt-d-dec 
  PUBLIC "-//OASIS//ENTITIES DITA 1.3 Release Management Domain//EN" 
         "../../org.oasis-open.dita.v1_3/dtd/technicalContent/dtd/
         ¶releaseManagementDomain.ent"
>%relmgmt-d-dec;

<!ENTITY % xml-d-dec
  PUBLIC "-//OASIS//ENTITIES DITA 1.3 XML Domain//EN"
         "../../org.oasis-open.dita.v1_3/dtd/technicalContent/dtd/
         ¶xmlDomain.ent"
>%xml-d-dec;

Note: You can add these anywhere in the DOMAIN ENTITY DECLARATIONS section; the order of the declarations does not matter.

In the DOMAIN ATTRIBUTE DECLARATIONS section of CompanyMap.dtd, add the following.
```
<!ENTITY % deliveryTargetAtt-d-dec
  PUBLIC "-//OASIS//ENTITIES DITA 1.3 Delivery Target Attribute Domain//EN"
         "../../org.oasis-open.dita.v1_3/dtd/base/dtd/
         ¶deliveryTargetAttDomain.ent"
>%deliveryTargetAtt-d-dec;
```
Note: You can add these anywhere in the DOMAIN ATTRIBUTE DECLARATIONS section; the order of the declarations does not matter.

For the localization-loc-d-dec entity, change the system id from

../../com.ixiasoft.dita.dtd/dtd/localizationDomain.ent

../../com.ixiasoft.dita13.dtd/dtd/localizationDomain.ent

In the DOMAIN EXTENSIONS section of CompanyMap.dtd, add these entities.

<!ENTITY % data         "data |
                         %ut-d-data;
                        ">
<!ENTITY % term         "term | 
                         %abbrev-d-term;
                        ">
<!ENTITY % metadata     "metadata | 
                         %relmgmt-d-metadata;
                        ">

Note: You can add these anywhere in the DOMAIN EXTENSIONS section; the order of the extensions does not matter.

Edit the keyword entity as follows.

<!ENTITY % keyword      "keyword | 
                         %markup-d-keyword; |
                         %pr-d-keyword; | 
                         %sw-d-keyword; |
                         %ui-d-keyword; |
                         %xml-d-keyword;
                        ">

Edit the topicref entity as follows.

<!ENTITY % topicref     "topicref | 
                         %ditavalref-d-topicref; |
                         (%mapgroup-d-topicref;) | 
                         (%glossref-d-topicref;)
                        ">

In the DOMAIN ATTRIBUTE EXTENSIONS section of CompanyMap.dtd, replace
```
<!ENTITY % props-attribute-extensions  "" >
```
to
```
<!ENTITY % props-attribute-extensions
  "%deliveryTargetAtt-d-attribute;"                                  
>
```
Important: If you have already specialized attributes from @props, simply add %deliveryTargetAtt-d-attribute; to that list; do not replace the entire entity declaration.
In the DOMAINS ATTRIBUTE OVERRIDE section of CompanyMap.dtd, add the following domains to the list, as shown.
```
...
&subjectScheme-att;
&deliveryTargetAtt-d-att;
&ditavalref-d-att;
&markup-d-att;
&relmgmt-d-att;
&xml-d-att;
```
Note: You can add these anywhere in the DOMAINS ATTRIBUTE OVERRIDE section; the order of the overrides in the list does not matter.
In the MAP ELEMENT INTEGRATION section of CompanyMap.dtd compare the public and system id's of each entity to those of the corresponding entity in the TOPIC ELEMENT INTEGRATION section of IxiaDitabase.dtd.
Change the public id of each entity in the MAP ELEMENT INTEGRATION section of CompanyMap.dtd to reference DITA 1.3 rather than DITA 1.2.
Change the relative path in the system id of each entity in the MAP ELEMENT INTEGRATION section of CompanyMap.dtd to point to the DITA 1.3 DTDs that are in system/plugins/org.oasis-open.dita.v1_3/dtd rather than the DITA 1.2 DTDs that are in system/dtd.
In the MAP ELEMENT INTEGRATION section of CompanyMap.dtd, add the following.
```
<!ENTITY % subjectScheme-type 
  PUBLIC "-//OASIS//ELEMENTS DITA 1.3 Subject Scheme Map//EN" 
         "../../org.oasis-open.dita.v1_3/dtd/subjectScheme/dtd/
         ¶subjectScheme.mod"
>%subjectScheme-type;
```
Note: You can add this anywhere in the MAP ELEMENT INTEGRATION section; the order of the entities does not matter.
In the DOMAIN ELEMENT INTEGRATION section of CompanyMap.dtd compare the public and system id's of each entity to those of the corresponding entity in the DOMAIN ELEMENT INTEGRATION section of IxiaDitabase.dtd.
Change the public id of each entity in the DOMAIN ELEMENT INTEGRATION section of CompanyMap.dtd to reference DITA 1.3 rather than DITA 1.2.
Change the relative path in the system id of each entity in the DOMAIN ELEMENT INTEGRATION section of CompanyMap.dtd to point to the DITA 1.3 DTDs that are in system/plugins/org.oasis-open.dita.v1_3/dtd rather than the DITA 1.2 DTDs that are in system/dtd.

In the DOMAIN ELEMENT INTEGRATION section of CompanyMap.dtd, add the following.

<!ENTITY % ditavalref-d-def
  PUBLIC "-//OASIS//ELEMENTS DITA 1.3 DITAVAL Ref Domain//EN"
         "../../org.oasis-open.dita.v1_3/dtd/base/dtd/
         ¶ditavalrefDomain.mod"
>%ditavalref-d-def;

<!ENTITY % markup-d-def 
  PUBLIC "-//OASIS//ELEMENTS DITA 1.3 Markup Domain//EN" 
         "../../org.oasis-open.dita.v1_3/dtd/technicalContent/dtd/
         ¶markupDomain.mod"
>%markup-d-def;

<!ENTITY % relmgmt-d-def 
  PUBLIC "-//OASIS//ELEMENTS DITA 1.3 Release Management Domain//EN" 
         "../../org.oasis-open.dita.v1_3/dtd/technicalContent/dtd/
         ¶releaseManagementDomain.mod"
>%relmgmt-d-def;

<!ENTITY % xml-d-def
  PUBLIC "-//OASIS//ELEMENTS DITA 1.3 XML Domain//EN"
         "../../org.oasis-open.dita.v1_3/dtd/technicalContent/dtd/
         ¶xmlDomain.mod"
>%xml-d-def;

Note: You can add these anywhere in the DOMAIN ELEMENT INTEGRATION section; the order of the entities does not matter.

You have completed the changes needed to your topic shell. Because MathML content is only used within topics, there are no map shell changes to be made for MathML integration.