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 Processing

Checking of the Unique Particle Attribute constraint is now done more rigorously. In particular, (a) a violation is now reported in the case where two particles of the form <element ref="foo"/> referring to the same element declaration exist in the same content model (in a position where either could match), and (b) conflicts between two <xs:any> particles, or between an <xs:any> particle and an <xs:element> particle, are now detected.

The `com.saxonica.Validate` command now outputs multiple validation errors in a single run.

The same facility is available when validation is invoked from user applications, provided that the application calls `configuration.validationWarnings(true)`.

The method `getSchemaTypeInfo()` is now available on Saxon nodes in the TinyTree object model. This method is defined in DOM Level 3 to return a `TypeInfo` object, which provides basic information about the type of the node following schema validation. At present Saxon provides a copy of the TypeInfo interface, to avoid introducing a dependency on DOM Level 3 being installed.

Next