You can add a new Document Type Association or edit the properties of an existing one from the option pane. All the changes can be made into the Document type edit dialog.
The Document Type
You can specify the following properties for a document type:
- Name - The name of the document type.
- Priority - When multiple document types match the same document,
the priority determines the order in which they are applied. It can be one of:
Lowest, Low, Normal,
High, Highest. The predefined document types that are
already configured when the application is installed on the computer have the default
Low priority.Note: The frameworks having the same priority are alphabetically sorted.
- Description - The document type description displayed as a tooltip in the Document Type Association table.
- Storage - The location where the document type is saved. If you select the External storage, the document type is saved in the specified file with a mandatory framework extension, located in a subfolder of the current frameworks directory. If you select the Internal storage option, the document type data is saved in the current .xpr Oxygen XML Editor plugin project file (for Project-level Document Type Association Options) or in the Oxygen XML Editor plugin internal options (for Global-level Document Type Association Options). You can change the Document Type Association Options level in the Document Type Association panel.
- Initial edit mode - Allows you to select the initial editing mode (Editor specific, Text, Author, Grid and Design (available only for the W3C XML Schema editor)) for this document type. If the Editor specific option is selected, the initial edit mode is determined depending on the editor type. You can find the mapping between editors and edit modes in the Edit modes preferences page. You can decide to impose an initial mode for opening files which match the association rules of the document type. For example if the files are usually edited in the Author mode you can set it in the Initial edit mode combo box.
You can specify the association rules used for determining a document type for an opened XML document. A rule can define one or more conditions. All conditions need to be fulfilled in order for a specific rule to be chosen. Conditions can specify:
- Namespace - The namespace of the document that matches the document type.
- Root local name of document - The local name of the document that matches the document type.
- File name - The file name (including the extension) of the document that matches the document type.
- Public ID (for DTDs) - The PUBLIC identifier of the document that matches the document type.
- Attribute - This field allows you to associate a document type depending on a certain value of the attribute in the root.
- Java class - Name of Java class that is called for finding if the document type should be used for an XML document. Java class must implement ro.sync.ecss.extensions.api.DocumentTypeCustomRuleMatcher interface from Author API.
In the Schema tab, you can specify the type and URI of schema used for validation and content completion of all documents from the document type, when there is no schema detected in the document.
You can choose one of the following schema types:
- DTD;
- Relax NG schema (XML syntax);
- Relax NG schema (XML syntax) + Schematron;
- Relax NG schema (compact syntax);
- XML Schema;
- XML Schema + Schematron rules;
- NVDL schema.
