A transformation scenario is a set of complex operations and settings that gives you the
possibility to obtain outputs of multiple types (XML, HTML, PDF, EPUB, etc.) from the same
source of XML files and stylesheets.
Executing a transformation scenario implies multiple actions, such as:
- Validating the input file.
- Obtaining intermediate output files (for example, formatting objects for the XML to PDF
transformation).
- Using transformation engines to produce the output.
Before transforming an XML document in Oxygen XML Editor, you need to define a
transformation scenario to apply to that document. A scenario is a set of values for various
parameters that define a transformation. It is not related to a particular document, but
rather to a document type. Types of transformation scenarios include:
- Scenarios that Apply to XML Files - This type of scenario contains the location of
an XSLT stylesheet that is applied on the edited XML document, as well as other
transformation parameters.
- Scenarios that Apply to XSLT Files - This type of scenario contains the location of
an XML document, on which the edited XSLT stylesheet is applied, as well as other transform
parameters.
- Scenarios that Apply to XQuery Files - This type of scenario contains the location
of an XML source, on which the edited XQuery file is applied, as well as other transform
parameters. When the XML source is a native XML database, the XML source field of the
scenario is empty because the XML data is read with XQuery-specific functions, such as
document(). When the XML source is a local XML file, the URL of the
file is specified in the XML input field of the scenario.
- Scenarios that Apply to SQL Files - This type of scenario specifies a database
connection for the database server that runs the SQL file that is associated with the
scenario. The data processed by the SQL script is located in the database.
- Scenarios that Apply to XProc Files - This type of scenario contains the location
of an XProc script, as well as other transform parameters.
- DITA-OT Scenarios - This type of scenario provides the parameters for an Ant
transformation that executes a DITA-OT build script. Oxygen XML Editor comes with a
built-in version of Ant and a built-in version of DITA-OT, although you can also set other
versions in the scenario.
- ANT Scenarios - This type of scenario contains the location of an
Ant build script, as well as other transform parameters.
Note:
Status messages generated during the transformation
process are displayed in the Information view.