Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Saxon XSLT
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Versions == The original development line of Saxon ended with the version 6 series. This is a series of XSLT 1.0 processors. The current version, 6.5.5, is not undergoing further development aside from maintenance. The 6 series is only available for the Java programming language. The current development line, Saxon 12, implements the XSLT 3.0 and XQuery 3.1 specifications. Saxon 12 can process XSLT 1.0 and XSLT 2.0 stylesheets. (XSLT 2.0 and 3.0 are highly backwards compatible with XSLT 1.0.<ref>This Recommendation builds on the success of [XSLT 1.0], which was published on 16 November 1999. Many new features have been added to the language (see J.2 New Functionality) while retaining a high level of backwards compatibility. [http://www.w3.org/TR/xslt20/ XSL Transformations (XSLT) Version 2.0]</ref>) and also includes selective support for the proposed XSLT 4.0 specification.<ref>[https://qt4cg.org/specifications/xslt-40/ XSL Transformations (XSLT) Version 4.0.]</ref> There are two separate source bases: the Java source, and the JavaScript source. The Java source is used to generate products for three platforms: SaxonJ (for Java and other JVM languages such as Scala), SaxonCS (for C# and other .NET languages such as VB.NET), and SaxonC (with APIs for C, C++, Python, and PHP). The JavaScript source base is used to generate SaxonJS, which runs in Web browsers and under Node.js. The Java-built versions come in three levels: Home Edition offers the minimal level of standards conformance defined in the specifications, as an open-source product. Professional Edition adds vendor-specific functionality not required by the standards, for example a range of extension functions and serialisation options. Enterprise Edition adds advanced features (defined in the W3C standards as optional) including schema-awareness and streaming, as well as performance-related features such as multi-threaded execution and bytecode generation. The SaxonCS product is built from the Java source base by means of a custom Java-to-C# [[Source-to-source_compiler|transpiler]] written in XSLT (see [https://markupuk.org/webhelp/index.html#ar04.html ] {{Webarchive|url=https://web.archive.org/web/20220610095817/https://markupuk.org/webhelp/index.html#ar04.html |date=2022-06-10 }}). As of April 2022, only the Enterprise Edition is offered on this platform. From 2004 until 2009, Saxon was available into two separate forms: Saxon-B and Saxon-SA. Both of these were built on similar codebases. Saxon-B was [[open-source license|open-source]] software released under the [[Mozilla Public License]], while Saxon-SA was a closed-source commercial product. The difference between Saxon-B and Saxon-SA was that B was "basic" while SA was "schema-aware". These terms are references to terms in the XSLT 2.0 and XQuery 1.0 specification. A processor that is "schema-aware" is able to use a [[XML Schema (W3C)|W3C XML Schema]] to define the data types of the various elements in the source XML document(s). These data types can then be used in [[XPath]] 2.0 and XSLT 2.0 commands. A "basic" XSLT 2.0 processor is unable to use data typing information. Saxon offers strict conformance to the XSLT 2.0, XPath 2.0 and 3.0, and XQuery 1.0 and 3.0 W3C Recommendations, and also implements XML Schema 1.0 and 1.1. As of 2021 the current version (10.6) conforms with the W3C Recommendations for XSLT 3.0, XPath 3.1, and XQuery 3.1. The Saxon source code is written in Java. During 2005-6, M. David Peterson and others demonstrated that Saxon could be cross-compiled to run on .NET using the [[IKVM]] cross-compiler, launching Saxon.NET as a separate product independent of the original developer. With the release of Saxon 8.7, Saxonica adopted this technology and from that release onwards, all versions have been released simultaneously for Java and .NET. The .NET version of the product omits features that are specific to the Java platform (such as integration with [[JDOM]], [[Dom4j]], and [[XML Object Model|XOM]]) and instead provides features that integrate with the XML processing capabilities of the .NET platform. In 2012, following a series of prototypes, Saxonica released Saxon Client Edition (Saxon-CE), a version of the product adapted to run within the browser environment. This is achieved by adapting the Java source code so that it can be cross-compiled to JavaScript using the [[Google Web Toolkit|GWT]] cross-compiler produced by [[Google]]. Saxon-CE provides the first implementation of XSLT 2.0 running on the browser, and also extends the language so that rather than merely generating HTML, it can directly handle user interaction. With the release of Saxon-CE 1.1 in February 2013, the product became open source. In February 2016 Michael Kay announced that Saxonica was working on a replacement for Saxon-CE written in pure JavaScript, and dubbed Saxon-JS.<ref>{{Cite web|url=http://dev.saxonica.com/blog/mike/2016/02/introducing-saxon-js.html|title = Introducing Saxon-JS}}</ref> [[Michael Howard Kay|Michael Kay]], the author of Saxon, was the editor of the XSLT 2.0 specification and is also editor of the XSLT 3.0 draft.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)