Extensible XML Editor Starting with version 9 <oXygen/>
XML Editor adds a new concept called Document Type that solves the problem of providing
ready to use support for a framework or an XML language. The Document Type concept is
used to provide the built in support <oXygen/> XML Editor has for a number of XML
frameworks (DITA, DocBook, TEI) but, more importantly, it can be employed to provide
support for a user defined framework that needs to be shared with other
users. You can modify the built-in document type associations or to create your own new
associations. In this way you can customize the editor to match exactly your use
cases. Default schemaYou can specify the default schema to be used for validation
and content completion for the documents that match a document type. This schema can
be overwritten if the XML document itself specifies a schema inside. All the current
schema languages are supported DTD, XML Schema, Relax NG, ISO Schematron, ISO NVDL.
Default CSS filesYou can specify a set of CSS files, including alternates and
default CSS that will be used by <oXygen/> when editing in Author mode. Custom actionsYou can define custom actions for the Author mode that will
appear in tool bar, menu or contextual menu. These actions in general add support for
inserting XML markup structures, lists, list items, tables, table rows, table columns,
etc. in the specific framework the document type describes. <oXygen/> provides a set
of operations that can be used to implement most of the actions. If needed you can
code your own operations in Java and use them to define your actions. Document templates You can specify a folder where you have document templates
(XML or not). These templates will be gathered automatically by <oXygen/> and will
appear in the new file dialog allowing easy creation of the new documents of the
defined document type. XML catalogsYou can specify XML Catalogs for the document type that resolve
remote resources to local copies. This allows a faster access to those resources
(schemas, stylesheets, etc.) and also allows to work off-line without changing the XML
documents to explicitly point to local resources. Default transformation scenariosYou can specify a set of transformation scenarios to convert
the XML documents to different formats like HTML and PDF. |