[basex-talk] Quick Windows issue: Invalid reply on port 1984, works fine on port 8984

2019-03-28 Thread Jim Salmons
Hello BaseX folk, I have just installed version 9.1.2 and am starting to learn BaseX in support of my post-cancer #PayItForward Bonus Round #CitizenScientist research in #DigitalHumanities and #MachineLearning. My goal is to "cut out the middleman" of writing intermediate JSON and XML fragment

Re: [basex-talk] Higher order functions in XSLT

2019-03-28 Thread Liam R. E. Quin
On Thu, 2019-03-28 at 11:48 +0100, nikos dimitrakas wrote: > [...] > XPST0003: Inline functions require support for higher-order- > functions, which needs Saxon-PE or higher. I am using Saxon EE > 9.9.1.2 (also tried PE 9.9.1.2) This suggests BaseX is picking up the wrong version of Saxon, or

Re: [basex-talk] Higher order functions in XSLT

2019-03-28 Thread nikos dimitrakas
On 2019-03-28 11:54, Martin Honnen wrote: Am 28.03.2019 um 11:48 schrieb nikos dimitrakas: > Hi! > > Is there something in BaseX that prohibits using higher order > functions in XSLT (called with xslt:transform)? > > for-each($somenodes, function($q) { string($q) }) > > and > >

Re: [basex-talk] Higher order functions in XSLT

2019-03-28 Thread Martin Honnen
Am 28.03.2019 um 11:48 schrieb nikos dimitrakas: Hi! Is there something in BaseX that prohibits using higher order functions in XSLT (called with xslt:transform)? for-each($somenodes, function($q) { string($q) }) and for-each($somenodes, string#1) both work in XQuery in BaseX, but when I

[basex-talk] Higher order functions in XSLT

2019-03-28 Thread nikos dimitrakas
Hi! Is there something in BaseX that prohibits using higher order functions in XSLT (called with xslt:transform)? for-each($somenodes, function($q) { string($q) }) and for-each($somenodes, string#1) both work in XQuery in BaseX, but when I use the same call in an XSLT that I call with