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

# Schema processing changes

A restriction has been lifted: `fixed` and `default` values are now supported for elements with a complex type (specifically, a complex type with mixed content).

A `SchemaURIResolver` may now be specified for resolving the location hints found in `xsd:import`, `xsd:include`, and `xsd:redefines`; in the `xsi:schemaLocation` and `xsi:noNamespaceSchemaLocation` attributes in instance documents; in the `xsl:import-schema` declaration in XSLT; and in the `import schema` declaration in XQuery. This differs from a normal `URIResolver` in that the decision may be made based both on the target namespace of the schema being loaded, and on the location hints.

It is no longer an error for schema documents to include each other recursively. This condition now results in a warning message rather than an error message.

Next