BTW: Just to note that Saxon 11.3 has been working fine for me under Basex 9.x,

But it requires including the included xmlresolver files in the class path:

export CLASSPATH=/usr/local/Cellar/saxon/11.3/libexec/saxon-he-11.3.jar:/usr/local/Cellar/saxon/11.3/libexec/lib/*.jar

Oh. I stumbled upon the same thing. But I don't add a directory to the class path where I store a stand alone copy of an XML resolver (and Saxon).

There is a jar that seems to contain everything needed and I put it in lib/custom together with saxon-he-11.3.jar (and that is added to the classpath by the startup scripts):

 lib/custom/Saxon-HE-11.3.jar
 lib/custom/xmlresolver-4.3.0.jar

But I haven’t done any special testing using the resolver from either Saxon or BaseX — 

Just running my current development code without noticing any problems. 

— Steve M.

-- 
Mag. Ing. Omar Siam
Austrian Center for Digital Humanities and Cultural Heritage
Österreichische Akademie der Wissenschaften | Austrian Academy of Sciences
Stellvertretende Behindertenvertrauensperson | Deputy representative for disabled persons
Bäckerstraße 13, 1010 Wien, Österreich | Vienna, Austria
T: +43 1 51581-7295
omar.siam@oeaw.ac.at | www.oeaw.ac.at/acdh