The Document Type Association preferences panel is opened from menu → → +Document Type Association
- User roles
You can select between two user roles Content author and Developer. When the selected role is Content author you can modify only the properties of the Document Type Associations stored in the user preferences. The externally stored associations cannot be modified and you will have to duplicate them in order to further customize these associations. The Developer user can change any document type association.
- Document types table
The table presents the currently defined document type associations. The columns are:
- Document type
Contains the name of the document type.
- Enabled
When checked the corresponding document type association is enabled, it is analyzed when trying to determine the type of a document opened in oXygen.
- Storage
Presents the location where the document type association is stored.
When expanding a Document Type Association its defined rules are presented. A rule is described by:
- Namespace
Specifies the namespace of the root element from the association rules set (any by default). If you want to apply the rule only when the root element is in no namespace you must leave this field empty (remove the <ANY> string).
- Root local name
Specifies the local name of the root element (any by default).
- File name
Specifies the name of the file (any by default).
- Public ID
Represents the Public ID of the matched document.
- Java class
Presents the name of the class which will be used to determine if a document matches the rule.
- New
Opens a new dialog allowing you to add a new association.
- Edit
Opens a new dialog allowing you to edit an existing association.
- Delete
Deletes one of the existing association.
- Up
Moves the selected association one level up (the order is important because the first document type association in the list that can be associated with the document will be used).
- Down
Moves the selected association one level down.
- Enable DTD/XML Schema processing in document type detection
When this is enabled the matching process will also examine the DTD/XML Schema associated with the document. For example the fixed attributes declared in the DTD for the root element will be analyzed also if this is specified in the association rules.
Example 19.1. Enabling DTD Processing for DITA customizations
If you are writing DITA customizations you should enable this checkbox. DITA Topics and Maps are also matched by looking for the DITAArchVersion attribute in the root element. If the DTD is not processed on detection then this attribute specified as default in the DTD will not be detected on the root element and the DITA customization will not be correctly matched.
- Only for local DTDs/XML Schemas
When the previous feature is enabled you can choose to process only the local DTDs/XML Schemas.