SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
| Version 8.9 (2007-02-12)
| Version 8.8 (2006-09-05)
| Version 8.7.3 (2006-06-13)
| Version 8.7.2 (2006-04-19)
| Version 8.7.1 (2006-04-13)
| Version 8.7 (2006-02-24)
| Version 8.6.1 (24 November 2005)
» | Version 8.6 (3 November 2005)
| Version 8.5.1 (26 August 2005)
| Version 8.5 (2 August 2005)
| Version 8.4 (4 April 2005)
| Version 8.3 (11 February 2005)
| Version 8.2 (21 December 2004)
| Version 8.1.1 (8 October 2004)
| Version 8.1 (24 September 2004)
| Version 8.0 (1 June 2004)
Conditions of Use
Using XSLT 2.0
Using XQuery
Handling Source Documents
XML Schema Processing
XPath API for Java
Saxon on .NET
Extensibility
Saxon Extensions
Sample Saxon Applications
The Saxon SQL Extension
XSLT Elements
XPath 2.0 Expression Syntax
Function Library
Standards Conformance

# XML 1.1 support

There is a new option `setXMLVersion()` in the `Configuration`, which defaults to 1.0.

This configuration setting affects:

- validation of names used in XQuery and XPath expressions, including names of elements, attributes, functions, variables, and types

- validation of names of constructed elements, attributes, and processing instructions in XQuery and XSLT

- schema validation of values of type NCName, QName, NOTATION, and ID

- permitted names of stylesheet objects such as keys, templates, decimal-formats, output declarations, and output methods

- characters considered valid in the source of an XQuery query

- characters considered valid in the result of the functions codepoints-to-string() and unparsed-text()

- characters considered valid in the result of certain Saxon extension functions

- the way in which line endings in XQuery queries are normalized

- the default version used by the serializer (with output method XML)

The Saxon configuration setting has no effect on the XML parser. If XML 1.1 documents are supplied as input to Saxon, then you MUST call `config.setXMLVersion(Configuration.XML11)` (or use -1.1 on the command line). Saxon won't necessarily detect the error if you fail to do so (especially if the documents don't use any XML 1.1 features).

Note that there are a few incompatibilities introduced by this change, for example XQuery will only accept XML 1.1 line endings if the -1.1 flag is set.

Next