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 Schema-Aware XSLT and XQuery Processing

A new option `-vw` is added to the schema-aware versions of the command line interfaces for XSLT and XQuery processing, with an equivalent option `VALIDATION_WARNINGS` in the Java API. This option causes validation errors encountered in processing a final result tree to be treated as warnings, allowing processing to continue. This allows more than one error to be reported in a single run. The result document is serialized as if validation were successful, but with XML comments inserted to show where the validation errors were found. This option does not necessarily recover from all validation errors, for example at present it does not recover from errors in uniqueness or referential constraints. In the case of XSLT it applies only to result trees validated using the `validation` attribute of `xsl:result-document`.

The syntax for `declare validation` in the Query prolog is replaced by `declare construction`, as defined in the July 2004 draft specification. The syntax for the `validate{}` expression has also been updated to the latest draft. This removes the ability to validate any element other than one having a global element declaration in the schema.

DTD-defined attribute types are no longer retained automatically as type annotations in the data model. They will only be retained if the method `setRetainDTDAttributeTypes` is called on the `Configuration` object. This setting is available only in the schema-aware product, which means that with the basic product, nodes will always be annotated as untyped or untypedAtomic. ID attributes marked as such are still recognized for the purposes of the `id()` function, but they will be annotated as untypedAtomic.

Next