There was a repackaging of Saxon functionality between Saxon 9.1 (two packages, Saxon-B and Saxon-SA) and Saxon 9.2 (three packages, Saxon-HE, Saxon-PE, and Saxon-EE). Some facilities that were in the open source Saxon-B (notably, extensions like saxon:evaluate()) were not carried forward into Saxon-HE.
Sorry about the inconvenience. The decision was made for purely commercial reasons, to try to ensure that more of the people who run large commercial applications on Saxon pay something for the privilege. You can of course stay with Saxon-B 9.1 if it meets all your requirements, but it won't be developed any further.


Michael Kay

From: Vincent Lambert []
Sent: 24 February 2010 20:30
To: 'Mailing list for the SAXON XSLT and XQuery processor'
Subject: [saxon] Saxon .NET API and extension functions

I have been usign one of the latest version of saxon, to develop or XSLT v2 stylesheets. I have a licence for saxon-pe and enterprise versions that came with my xml editor (oXygen). The editor that the technical writers are using (XMetal) is usign Saxon, the open source version, and I am usign the .NET API for my generation program.
I recently started usign saxon:evaluate() and had no problems in oXygen or in XMetal, but I get a syntax error when I try to process
my stylesheet with the .NET api.
I read there ( that saxon extension functions are only supported from the professional edition, but if it is the case, why have I been able to use them using the open source version of saxon (in XMetal) ?
Thanks a lot for your help 
Vincent Lambert
Matrox Electronic Systems
XML Programmer