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

# Changes to internal APIs

The `Receiver` interface has changed so it now passes a `Configuration` down the pipeline rather than a `NamePool`. The `Configuration` gives access to the `NamePool` and to much else besides (for example, schema information, and the ErrorListener).

The `getTypedValue()` method of the `NodeInfo` interface now takes a parameter, the `Configuration` object. This is to provide access to schema information needed to extract the typed value of the node. The schema information available in this Configuration must include definitions of the schema types that were used to validate the node and give it a type annotation.

The specification (and implementation) of the `getURI()` method of the `NodeInfo` interface has been tidied up: it was previously unclear when it returned null and when it returned an empty string. It now returns an empty string in all cases where the node has no namespace URI (which matches the behavior of the XPath `namespace-uri()` function).

When output is directed to a SAX `ContentHandler`, any type annotations on attributes that correspond to the basic XML attribute types (such as ID and IDREFS) are now supplied to the ContentHandler. Namespace undeclarations of the form `xmlns:p=""` (as permitted by XML Namespaces 1.1) are now passed to the `startPrefixMapping()` method of a user-defined `ContentHandler` only if `undeclare-namespaces="yes"` is specified on `xsl:output`.

Next