BaseX version, installation recommendations

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 basex 12 is recommended, any pointers to getting this running on Debian would be gratefully received. Unfortunately Debian testing (https://packages.debian.org/sid/basex) still points to basex 10.5. I'm not familiar with Java installation requirements. > > Thank you for the project, which looks excellent. > > Many thanks, > Rory >

On 23/07/2025 18:42, Graydon Saunders wrote: > The zip package from (currently) > https://files.basex.org/releases/12.0/BaseX120.zip > unpacks and you're basically done. (With the caveat of needing an > appropriate Java installed.) > > 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). >>

On 23/07/2025 22:49, Rory Campbell-Lange wrote: > On 23/07/25, Martin Honnen via BaseX-Talk (basex-talk at mailman.uni-konstanz.de) wrote: >> On 23/07/2025 18:42, Graydon Saunders wrote: >>> The zip package from (currently) >>> https://files.basex.org/releases/12.0/BaseX120.zip >>> unpacks and you're basically done. > ... > >>> On Wed, Jul 23, 2025, at 12:06, Rory Campbell-Lange wrote: >>>> 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 >> that the currently supported versions 12 and 11 of Saxon are really XSLT 3.0 >> processors, not XSLT 2.0. > Thank you for the clarification about XSLT 3.0, Martin and Graydon. > > I've installed the latest basex (BaseX 12.1) and put Saxon-HE.jar in the lib folder. > > The example from page 116 of "XSLT, 2nd Edition" by Doug Tidwell which has an XSLT 2.0 example with the use of `separator` for <xsl:value-of>. > > Running > > saxon -s:cars.xml -xsl:cars.xsl -o:/tmp/o.xml > > works fine (where "saxon" means `java -jar /usr/share/java/Saxon-HE.jar $@`). > > Whereas: > > basex -o /tmp/o.xml "xslt:transform('cars.xml', 'cars.xsl')" > > Fails with: > > Stopped at <path>/basex/, 1/15: > [FODC0002] "" (Line 1): Content is not allowed in prolog. > > I assume I need to do something to fix the install path of the Saxon-HE.jar file. > > At the risk of trying everyone's patience further, further advice would be helpful. >