Mine lives in $HOME/bin/basex, so the actual executables are $HOME/bing/basex/basex/bin because there's a variety of versions:
On Wed, Jul 23, 2025, at 12:06, Rory Campbell-Lange wrote:Dear List
I may be working soon on a commercial server supporting XQuery 3.1+ with its own proprietary extensions, and XSLT 2.0.
Would basex 12 be the best match for these protocol versions (except of the proprietary components, of course)? I'm most interesting in working in an iterative fashion on the command line, as I'm used to doing with vim and psql (the postgresql interactive terminal).
If you want XSLT 2.0 with BaseX, you additionally need to add Saxon HE, only that the currently supported versions 12 and 11 of Saxon are really XSLT 3.0 processors, not XSLT 2.0. Any XSLT 2 code would run well with those versions, however, as far as I can tell. But Saxon 12 or 11 are technically XSLT 3 processors, meaning you can run XSLT 3.0 code with them without problems and without any checking against the XSLT 2.0 spec, meaning if your target system only supports XSLT 2.0 you would not notice if you have written XSLT 3.0 only code before executing it on the target, XSLT 2.0 system. The older versions of Saxon, that only support XSLT 2.0 (I would need to check whether it was 9.6 or 9.7 as the latest) are of course still around, even if no longer officially supported.