Validating XDIME 2 documents

The editor can validate XDIME 2 documents. The validation is performed automatically when the page author edits the document contents, but can also be invoked manually (the Validate command is available via the right-click menu when editing an XDIME 2 document in the Source page). Validation errors (such as typos, invalid content, missing attributes, etc.), will be highlighted and displayed in the workbench Problems view. The error information is updated each time the author changes the document. Refer to the topic entitled Validation for additional information.

The editor can validate XDIME 2 documents. The validation is performed automatically when the page author edits the document contents, but can also be invoked manually (the Validate command is available via the right-click menu when editing an XDIME 2 document in the Source page). Validation errors (such as typos, invalid content, missing attributes, etc.), will be highlighted and displayed in the workbench Problems view. The error information is updated each time the author changes the document. Refer to the topic entitled Validation for additional information.

Using external schemata

By default, the editor supports XDIME 2 markup. The schemata are placed in a jar file located in the ${MCS_HOME}/eclipse/plugin directory, and they cannot be removed or modified by page authors. However, the editor can use custom/external schemata defined in XSD files. Refer to the topic entitled Managing external schemata for the configuration instructions.

Well-formed XDIME 2 documents

XDIME 2 documents must conform to the XML syntax rules and need to be namespace well-formed. This, among other things, means that:

Refer to the Extensible Markup Language specification for more information.

Limitations

There are a number of limitations that apply to the validation mechanism. Refer to the section entitled Limitations in About the XDIME 2 editor for more information.

Related topics