XML Editor

• The possibility to insert a topic reference to a DITA-compatible resource in the DITA Maps Manager.
• The title for each referenced resource is presented in the DITA Maps Manager.
• When inserting topic references, cross references, or content references to content inside DITA-compatible documents, the insertion dialog box presents a list of DITA-specific IDs from the target document.
• Utilizing the Validate and Check for Completeness action, DITA-compatible documents that are referenced in the DITA map are now converted to DITA topics in the background and validated the same as any other DITA topic.
• When transforming DITA maps that have DITA-compatible documents referenced, the transformation converts the documents to normal DITA output on the fly.

• Validating JSON schemas version 2020-12 against the specification.
• Content completion proposals when editing JSON schemas version 2020-12.
• Validating JSON/YAML documents against a JSON schema version 2020-12.
• Converting older JSON schemas to version 2020-12.
• A specific framework that will allow you to edit JSON schema documents in Author mode.

• Search References - Searches all references of the selected definition in a scope determined by the schemas referenced in the file and the main schemas declared in validation scenarios.
• Search References in - Searches for all references of the selected definition in a defined scope.
• Search Occurrences in file - Searches all occurrences of the currently selected definition in the current file.
• Rename Component in - Allows you to rename the selected component name. You can preview the files being affected and these files are identified by searching the references of the selected component in the scope provided.
• Extract definition in another file - Extracts a definition to a new file. If the file does not already exist, the action will create a new file. If the file does exist, the action will find a corresponding group (or create one) and append the extracted definition.

• Redesign - The documentation output has a new design to make it easier to read and understand the OpenAPI specification.
• OpenAPI 3.1 Support - Support was added to generate documentation for OpenAPI 3.1 documents.
• Supports for YAML Files - The input file used for generating the documentation can be in either YAML or JSON format.

• A new Run OpenAPI Test Scenario tool is available in the Tools > JSON Tools menu. It provides you with the capability of running a test suite for an OpenAPI document.
• Syntax highlights are now rendered in the Request body and Response area to help make the code more readable.
• Undo/redo support was added in the Request body and Response area.

• A new Validate each file before committing option was added in the Git Client preferences page. Selecting this option enables automatic validation of each file before each commit.
• A new Validate all files from the project's "Main Files" folder before pushing option was added in the Git Client preferences page. Selecting this option enables automatic validation of the files located in the Main Files folder before the push operation processes.
• The integrated JGit library was upgraded to version 6.3, which brings support for ssh-agent forwarding.

For a complete list of updates added in the Git Client, see https://github.com/oxygenxml/oxygen-git-plugin/releases.

• XPath Context - You can define simple XPath expressions for particular defined rules to match or skip specific elements.
• Part of Speech Tagging - When scanning for terminology problems, the problem is presented only if the term's part of speech matches the one specified in the defined rule (available only for the English language).
• Phases - In the terminology configuration file, you can set the phase in which incorrect terms are detected (editing/validation/always). Performance improvements were also implemented when checking files.
• Load Terms Provided by Other Add-ons - Any Oxygen add-on (plugin) can now contribute terminology files to be used by the Terminology Checker. The contributed terminology files will be loaded and used if the contributor add-on is enabled. For more details, see Terminology Files Contributed from Other Oxygen Add-ons.

• You can specify a certain schema file to validate against.
• You can validate using the schema(s) that are internally associated within files.
• You can validate using the default Oxygen validation scenarios for respective file types.
• You can specify a validation scenario name to be referenced from either a scenarios file or a project file.