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

# XQuery changes

Namespace undeclarations (`declare namespace p = ""`) are now accepted in the Query prolog.

URILiterals appearing in a query (for example, namespace URIs, collation URIs, module locations, schema locations, the base URI) now recognize ampersand-escaping of special characters. In particular, an ampersand used within a URI must be written as `&amp;`.

A collation URI appearing either in an `order by` clause or in the `default collation` declaration is now required to be a valid URI, and if it is relative, it is resolved relative to the base URI from the static context before being passed to the `CollationURIResolver`.

Comments may now be empty, that is, `(::)` is allowed. This also affects XPath.

The contents of a pragma are now validated: the pragma must start with a valid QName. If the QName is in the Saxon namespace, then the local-name must represent a recognized pragma.

A new pragma extension is available in Saxon-SA: the construct `(# saxon:validate-type type-name #){ expr }` causes the result of the expression `expr` to be validated against a named global type. This follows the same rules as the `type="type-name"` attribute in XSLT. Validating against a global type has been found to be useful when using schemas such as FpML, which make extensive use of `xsi:type`, and feature local element declarations with global types.

To make it easier to embed XQuery in other environments, a new method `setExternalNamespaceResolver` is provided on the `StaticQueryContext` object.

The -v option, which invokes DTD validation, has been added to the Query command line.

Next