Version 1.0 - April 15, 2002 Version 1.1 - May 15, 2002 Version 1.1.5 - May 20, 2002 Version 1.1.6 - May 24, 2002 Version 1.1.7 - May 27, 2002 Version 1.1.8 - June 5, 2002 Version 1.1.9 - June 15, 2002 Version 1.2 - June 27, 2002 Version 1.2.1 - September 27, 2002 Version 1.2.2 - October 22, 2002 Version 1.2.3 - November 27, 2002 Version 1.2.4 - December 17, 2002

2003

2

Version 2.0 - April 2, 2003 Version 2.0.1 - May 15, 2003 Version 2.0.2 - June 9, 2003 Version 2.0.3 - August 14, 2003 Version 2.0.4 - September 19, 2003

2004

3

Version 3.0 - January 14, 2004 Version 3.1 - February 6, 2004

4

Version 4.0 - April 30, 2004 Version 4.1 - June 10, 2004 Version 4.2 - July 15, 2004

5

Version 5.0 - October 15, 2004 Version 5.1 - January 18, 2005

2005

6

Version 6.0 - May 22, 2005 Version 6.1 - July 19, 2005 Version 6.2 - September 19, 2005

2006

7

Version 7.0 - January 13, 2006 Version 7.1 - March 2, 2006 Version 7.2 - June 6, 2006

8

Version 8.0 - November 20, 2006 Version 8.1 - January 25, 2007 Version 8.2 - May 7, 2007

2007

9

Version 9.0 - November 2, 2007 Version 9.1 - December 18, 2007 Version 9.2 - May 9, 2008 Version 9.3 - July 2, 2008

2008

10

Version 10.0 - October 23, 2008 Version 10.1 - February 25, 2009 Version 10.2 - April 15, 2009 Version 10.3 - June 29, 2009

2009

11

Version 11.0 - October 9, 2009 Version 11.1 - December 17, 2009 Version 11.2 - March 16, 2010

2010

12

Version 12.0 - September 14, 2010 Version 12.1 - January 12, 2011 Version 12.2 - May 19, 2011

2011

13

Version 13.0 - August 29, 2011 Version 13.1 - October 26, 2011 Version 13.2 - January 12, 2012

2012

14

Version 14.0 - June 27, 2012 Version 14.1 - October 19, 2012 Version 14.2 - February 13, 2013

2013

15

Version 15.0 - June 7, 2013 Version 15.1 - October 7, 2013 Version 15.2 - January 22, 2014

2014

16

Version 16.0 - May 20, 2014 Version 16.1 - October 7, 2014

2015

17

Version 17.0 - May 5, 2015 Version 17.1 - October 20, 2015

2016

18

Version 18.0 - April 21, 2016

18.1

Version 18.1 - October 18, 2016

2017

19

Version 19 - April 5, 2017

Oxygen XML Editor 7.0

Validation

Oxygen can be configured to continuously report validation
errors in an edited document as you modify it. By selecting the Enable
automatic validation option, validation errors will automatically be
displayed as you type, after a configurable delay.

The location of errors, including those that are generated by
continuous validation, are marked in-place with an underline. The error locations are
also marked in red on the right side of the editing view, in an overview ruler that
allows you to quickly navigate between the errors.

Support for Caching When Validating Against Schemas

By default the validate action will cache the parsed schemas. There is
also a "Reset cache and validate" action provided to allow revalidation in
development environments when the schema is changed.

Various CSS profiles are supported (CSS2, CSS3, etc.), as well
as various media types (for instance, 'Braille' or 'screen'). You can also choose the
verbosity level of the validation warnings.

The validation results are descriptive and in accordance with
the W3C specifications. Along with the automatic validation feature, spotting and
fixing errors in the Oxygen CSS editor is a simple task.

XPath

XPath-Aware Content Completion Assistant

Editing XPath expressions for the "match", "select", or "test" attributes
is not always straight forward. Oxygen XSLT Editor makes this task
easier by showing the proposed list of XPath functions in the Content
Completion Assistant, all documented with sections from the W3C
specifications.

If you have configured a scenario for the edited stylesheet, then the
proposal list contains also the names of the elements from the input
document that are currently accepted in the XPath expression.

Support for XPath Default Namespace

For XPath 2.0 queries the XPath default namespace can be
configured/automatically detected and used to write XPath queries.

The XPath expressions are evaluated from the context of the
current element, thus relative expressions can be evaluated in various contexts.

XSLT

XSLT Input Document View

This view displays the tree structure of the XML document set as input for
the current stylesheet in the associated transformation scenario.

You can create templates or other XSLT snippets by dragging the nodes from
the tree into the stylesheet. The generated XPath expressions are context
aware.

Search XSLT References

This search is performed for any XSLT component that has references
(variables, functions, named templates, attribute sets, etc.) The search
scope can be the current file, the project, or all the imported/included
files starting from the current file or from a specified file.

Search XSLT Declarations

This search is performed for any XSLT component that has declarations
(variables, functions, named templates, attribute sets, etc.) The search
scope can be the current file, the project, all the imported/included files
starting from the current file or from a specified file.

Search XSLT Occurrences

This provides a quick retrieval of all the declarations and references of
a component in the current file.

Rename XSLT Occurrences

This allows renaming XSLT components such as variables, templates,
functions, etc. The user is fully in control of the changes as the modified
files are presented in a Diff view that allows inspecting all the changes
that will be done before actually performing them. The scope can be the
current file, the project, all the imported/included files starting from the
current file or from a specified file.

Create XSLT Stylesheet from Selection

The selection is placed in a new stylesheet that is then included in the
current stylesheet.

Create XSLT Template from Selection

The selection is placed in a named template and is replaced with a
call-template instruction. The variables and parameters used inside the
selection will be passed as template parameters.

Apply the Transformation Scenarios for Multiple Files in One Action

From the Project view it is possible to select multiple files and apply
their associated transformation scenarios on each one.

Apply a Specified Transformation Scenario on a Set of Files

From the Project view a set of files can be selected then a
transformation scenario will be selected and applied on each of the selected
files.

Allow Configuring the XSLT Transformer Options Through Preferences

Processor specific options for Saxon, XSLTProc, MSXML and MSXML.NET can
be configured through the Oxygen preferences.

Support the System.Xml 2.0 Transformer

The .NET 2.0 framework transformer can now be used from
Oxygen.

Support for the Latest Version of Saxon 8

Saxon 8.6.1 from Saxonica (http://www.saxonica.com) is now
supported.

XQuery

Save time when developing complicated XQuery expressions by
using the Oxygen XQuery debugger. Oxygen can debug and profile expressions run
over MarkLogic or Berkeley XML databases, or using the Saxon EE processors.

You can profile your XQuery queries to identify the performance
issues by using two comprehensive data views of the activated templates: an Invocation
Tree view and a Hotspots view. The profiling information can be saved to XML or HTML
formats.

Profiling is available only for the Saxon XQuery processor that
is bundled with Oxygen.

Schema Editors

Schema Components View

The schema components were moved from the schema editor in a dockable
view called the Schema Components view.

Content Completion Assistant

The proposals that have previously been used are promoted at
the top of the content completion list, thus allowing for efficient re-use. For
example, when editing an XSLT stylesheet, you use a small fraction from the entire set
of XSLT and HTML elements. By sorting the recently used proposals to appear at the top
of the list, it makes it easier to find them the next time you want to use
them.

Handling of Namespace Prefixes

The namespace prefixes are presented first in the list of proposals for
elements, thus making editing really easy for documents that use prefixes for
elements.

Present #ID URI Fragments for anyURI Attribute
Values

When an attribute value is of type anyURI (in both XML
Schema and Relax NG schema) Oxygen will present proposals of the form #ID
for each defined ID value in the document.

Look for Type Annotations if the Elements or Attributes Don't Have
Annotations

When editing documents against an XML Schema Oxygen will look as
deep as needed in the type hierarchy for an element type or an attribute type if
the respective element or attribute do not have an annotation and will present
the first encountered annotation next to the content completion proposal.

The Content Completion Assistant Displays Element Values When Using a Relax
NG Schema

The element values support in the Content Completion Assistant was
extended to work also when the document is edited against a Relax NG
schema.

Support for Presenting the xsi:nil Attribute for Nillable
Elements

If an element is defined as nillable in the associated XML Schema,
Oxygen offers the xsi:nill attribute through the Content
Completion Assistant for possible attributes for that element.

GUI

Not only can the views be moved around the interface but
the editors can also be arranged inside the overall editing area.

Additionally, each editor can be split horizontally or
vertically. Splitting an editor allows you to easily copy or move text and markup
between two sections of the same document.

Split Editor in Two

It is possible to have two editors on the same file side by side so you
can edit a different location in a file while looking at some other location in
the same file in the other editor.

The Find Dialog Box is not Modal

The Find dialog box now allows going to the editor while it is still
open and then allows resuming the search.

Configurable GUI Fonts

It is possible to specify the fonts to be used not only for editor but
also for GUI text components and for the other GUI components. This allows
having a user-friendly and accessible application even on configurations with a
very large DPI setting.

All the Result Views Allow Both Table and Tree Layouts

The information presented in the Results view (for instance, the errors
after a validation action) can be presented either in a table layout or in a
tree layout that groups the messages by system ID. Also support for removing the
selected items or all the items in a view is provided.

Close Icons for the Editor Tabs

Editor tabs can be easily closed not only with a middle click but also
using the X close icon that appears in each editor tab.

Folding Support for JavaScript and CSS

The folding is now based on curly brackets.

Other

Allow Different Element Colors Depending on XML Prefix

This allows, for instance, to have the XSLT elements in a different color
than the result elements, or the XML Schema elements different from the
elements used inside annotations.

Automatic Insertion of Ending Quotes or Apostrophes

If a starting quote or apostrophe is entered the ending quote,
respectively apostrophe is automatically inserted.

The Information view shows messages for what
happens behind the scenes (for instance, when a validation is performed, it informs
you of what file was validated and the schema it was validated against).