The software is issued as two directories
SaxonceDebug, each containing a similar set of files, the first optimized for production and the second for development. (The files are generated by the GWT compiler from Java source code, with diagnostic code 'compiled out' for the files in the production directory). The code all runs client-side: there are no dependencies on the web server environment other than the ability to serve static content.
One of the included files (in each directory),
Saxonce.nocache.js, is the entry point, and is referenced from a
script element in user-written HTML pages.
The other files have cryptic hexadecimal names. There are in fact five such files, each containing almost the same code, but each tailored for a different browser. The master code
Saxonce.nocache.js will load whichever of these modules is appropriate to the browser in use.
To verify the license, Saxon-CE will look for a valid license file in the same path as the
SaxonceDebug directory. The license file will be suffixed with the release phase and major version number that the license corresponds to, so
saxonce‑license‑1.txt is used for release 1.0 to 1.n. The directories can be renamed, but their contents and the license filename should not be changed.
Also included in each directory are two data files,
unicodeBlocks.xml. These contain information used by the XPath
normalize-unicode() function and regular expression functions respectively; they're read from the server only if such a function is actually called.