The SAXON XSLT Processor from Michael Kay

Edit Package saxon10
http://saxon.sourceforge.net/

The Saxon package is a collection of tools for processing XML documents. The
main components are:

• An XSLT processor, which can be used from the command line, or invoked from
an application, using a supplied API. Saxon implements the XSLT 3.0
Recommendation. The product can also be used to run XSLT 2.0 stylesheets, or
XSLT 1.0 stylesheets in backwards compatibility mode.

• An XPath processor accessible to applications via a supplied API. This
supports XPath 2.0 and XPath 3.1. It can also be used in
backwards-compatibility mode to evaluate XPath 1.0 expressions.

• An XQuery processor that can be used from the command line, or invoked from
an application by use of a supplied API. This supports XQuery 3.1, which also
allows XQuery 1.0 or 3.0 queries to be executed. With Saxon-EE, you can also
use the XQuery extensions defined in the XQuery Update 1.0 Recommendation, but
later working drafts of XQuery Update are not supported (W3C has abandoned work
on these versions).

• An XML Schema Processor. This supports both XSD 1.0 and XSD 1.1. This can be
used on its own to validate a schema for correctness, or to validate a source
document against the definitions in a schema. It is also used to support the
schema-aware functionality of the XSLT and XQuery processors. Like the other
tools, it can be run from the command line, or invoked from an application.

• On the Java platform, when using XSLT, XPath, XQuery, or XML schema
validation, Saxon offers a choice of APIs. If you need portability across
different vendors' tools, you can use the JAXP API for XSLT, XPath, and XML
Schema processing, and the XQJ interface for XQuery. On the other hand, if you
want a more integrated and complete API offering access to all Saxon's
facilities, the s9api interface is recommended. You can also dive down deeper
into the Saxon internals if you need to: there has been no particular attempt
to make interfaces private, and all public interfaces are documented in the
JavaDoc. Clearly, the deeper you go, the greater the risk of interfaces
changing in future releases.

• On the .NET platform, Saxon offers an API that enables close integration with
other services available from .NET, notably the XML-related classes in the
System.Xml namespace. It isn't possible to use Saxon as a transparent plug-in
replacement for the System.Xml.Xsl processor, because the API for the Microsoft
engine using concrete classes rather than abstract interfaces. However, it is
possible to use it as a functional replacement with minor changes to your
application code.

Refresh
Refresh
Source Files
Filename Size Changed
Saxon-HE-10.9.pom 0000003873 3.78 KB
saxon-resources-10-cleaned.zip 0022507073 21.5 MB
saxon10-9source.zip 0005104799 4.87 MB
saxon10-generate-tarball.sh 0000000349 349 Bytes
saxon10.build.xml 0000004464 4.36 KB
saxon10.changes 0000009187 8.97 KB
saxon10.gizmo.pod 0000022307 21.8 KB
saxon10.gizmo.script 0000000473 473 Bytes
saxon10.saxon.pod 0000032947 32.2 KB
saxon10.saxon.script 0000001106 1.08 KB
saxon10.saxonq.pod 0000025066 24.5 KB
saxon10.saxonq.script 0000001100 1.07 KB
saxon10.spec 0000010013 9.78 KB
Comments 0
No comments available
openSUSE Build Service is sponsored by