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

# Version 8.6.1 (24 November 2005)

This is a maintenance release: all confirmed bugs in Saxon 8.6 are fixed.

A new extension function saxon:deep-equal() is introduced. This is equivalent to the standard fn:deep-equal() function but with an extra argument to control the comparison details. For example the flag "N" can be set to require two elements to have identical namespace nodes. The function also provides a flag "?" which causes warnings to be displayed explaining the reason for any non-match.

The code that handles binding of imported functions and variables in XQuery has been redesigned, to fix a problem that sometimes resulted in references not being correctly resolved.

Type error FORG0006 occurs when computing the effective boolean value of a sequence for which no EBV is defined (for example, a sequence containing a single date). This error may now be reported statically if it can be detected statically. Like other early reporting of type errors in Saxon, this is done optimistically: that is, an error is reported statically only if there is no valid instance of the supplied type for which EBV is defined.

The warning message produced when a schema uses types such as xs:NMTOKEN or xs:ID for elements (rather than attributes) has been dropped. Although the XML Schema specification says that "for compatibility" such types should not be used for elements, this admonition appears to serve no useful purpose and is widely ignored, not least by tools that generate schemas automatically.

Next