Oxygen XML Editor
The Premier All-In-One XML Editing Suite
Oxygen XML Author
Single-Source XML Authoring and Multi-Channel Publishing
Oxygen XML Developer
The Required Tools for Designing XML Schemas and Transformation Pipelines
Oxygen JSON Editor
The Perfect Tool to Simplify Your JSON Editing Experience
Oxygen Publishing Engine
The Complete DITA Publishing Solution for WebHelp and PDF Output
Oxygen PDF Chemistry
Chemistry Converts HTML and XML to PDF Using CSS
Oxygen XML WebHelp
Publish DITA and DocBook Content to WebHelp Output
Oxygen Styles Basket
Customize the Look and Feel of Your PDF and WebHelp Output
Oxygen XML Web Author
Engage Your Whole Organization In Content Creation
Oxygen Content Fusion
The Web-based Collaboration Platform to Craft Tomorrow's Content
Oxygen Feedback
Modern Commenting Platform
Cloud
Enterprise
Oxygen AI Positron
Enhance Your Productivity with the Power of AI
Oxygen Scripting
Automate and Run Oxygen Utilities from the Command-Line Interface
Oxygen SDK
Specifically designed for application developers and integrators
Shop
Pricing and licensing for businesses, Academic and individuals
This plugin installs an external Saxon 9.7 XSLT & XQuery processor into <oXygen/>. You will be able to validate and transform XSLT/XQuery with Saxon 9.7.
Note: Debugging XSLT/XQuery transformations based on this engine is NOT supported.
After installing the plugin, there are two possiblities to use Saxon 9.7 for validating XSLT:
Create a Transformation Scenario that uses Saxon-EE 9.7.0.21 (External) as the engine and associate it with the stylesheet.
Saxon 9.7 allows one to export the compiled form of a stylesheet as an XML file. The plugin also contributes an action on the toolbar that will compile and export an XSLT.
After installing the plugin, there are two possiblities to use Saxon 9.7 for validating XQuery:
Create a Transformation Scenario that uses Saxon-EE XQuery 9.7.0.21 (External) as the engine and associate it with the XQuery file.
This plugin will allow you to perform transformations with data extracted from a database, but there are a few changes you will have to make to use this:
Run the transformation scenario.
If this does not work, try the following: