Saxon

SaxonCS includes an interface `Saxon.Ejavax.xml.transform.URIResolver which is intended to emulate the Java interface java.xml.transform.URIResolver. However, it's only method is declared as

Source resolve(string baseUri, string relativeUri);

whereas the corresponding method in Java is

Source resolve(String href, String base)

The reversal of the parameter order leads to the URIResolver being called incorrectly. It's rather surprising that this didn't lead to test failures, but this is probably because the test suites mainly use absolute URIs.

I'm going to correct this by changing the parameter order to match what it is in Java.