Saxon

Correction - this is with version 9.5.1.4

I've successfully validated my package with 9.9.1.6 so perhaps I was hitting a bug in an older version.

I think the answer is that it should work provided the schemas are compatible. Saxon maintains a global (Configuration-level) schema (= a set of schema components) and when validation uses xsi:schemaLocation, the schema components at that location are added to the global pool. If this causes conflicts (two different types with the same name, for example) you'll get an error.

I doubt this is well tested, so if you get a failure, please send us the details so we can try and reproduce it.

Thanks Michael.

As noted above I was able to validate my package with a later version of Saxon.

The package does not validate against more than one XML schema. Only one data model is a schema but both DTD (JATS 1.2) and schema (a bespoke data model) contain definitions of elements with the same name.

E.g. is common to both data models but has a namespace in the schema.

(So no conflict because the namespace makes it different?)