– Don’t bother that the namespace is a URN.
– Don’t confuse namespaces with schema locations.
– Apparently BaseX cannot use a catalog resolver for resolving schema locations. – Use other more or less portable ways for accessing the schemas, for ex. store them in a database or put the base file system paths into an external variable. – There is no default catalog location; you specify the catalog to use with the CATFILE option.


You can store an XML catalog file anywhere you like. Then you set the option CATFILE to this file location, or you can do it in the XQuery file like this:

declare option db:catfile "path/relative/to/cwd/catalog.xml";

Of course you can also supply an absolute path.

On 21.10.2019 22:05, SW-Service wrote:
Good day,
Where is the catalog.xml file stored?
I want to validate xml files against XSD, but the xsd is referenced via an urn.
thank you very much

Guten Tag,
Wo wird die catalog.xml Datei abgelegt?
Ich möchte xml-Dateien gegen XSD validieren, aber die XSD wird über einen urn referenziert.
Herzlichen Dank

<xdomea:Aussonderung.Aussonderung.0503 xmlns:xdomea="urn:xoev-de:xdomea:schema:2.3.0">

This line only contains a namespace declaration and no schema association.

Does your document contain an xsi:schemaLocation attribute? Then this can be taken into account for validation, see [1].

Suppose the schema location had the same URN as the namespace, I’d expect a document like this:

xsi:schemaLocation="urn:xoev-de:xdomea:schema:2.3.0 urn:xoev-de:xdomea:schema:2.3.0">

The xsi:schemaLocation attribute contains first the namespace, then the schema location (accidentally the same URIs). Only the latter is subject to catalog resolution.

Suppose you have a catalog

<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
  <uri name="urn:xoev-de:xdomea:schema:2.3.0" uri="foobar.xsd"/>

and the XSD foobar.xsd (in the same directory as the catalog):

<xs:schema xmlns:xs="";
  <xs:element name="Aussonderung.Aussonderung.0503"/>

Then oXygen, for example, will honor the catalog’s mapping and validate against foobar.xsl.

But I just found out that BaseX’s XSD validator will not use the catalog in order to resolve the schema location’s URI.

I think BaseX uses catalogs only for two things: When importing files into a database and, recently, for the XSLT processor [2].

It doesn’t seem to use it for doc(), either, so reading doc('urn:xoev-de:xdomea:schema:2.3.0'), which should resolve to foobar.xsd, doesn’t work.

This means if you use BaseX, you need to access the schema in another way. You can put all the XOEV schemas in a database and validate like this:

db:open('xoev-schema', 'foobar.xsd'))

assuming that xoev-schema is the name of the database and foobar.xsd the relative path of the schema, relative to where you imported it from.

You can also refer to an actual location in the file system, with the base path optionally declared by an external variable, in order not to make it too dependent on the given directory structure.

declare namespace xs = '';
declare variable $basedir-uri external := file:path-to-uri(Q{org.basex.util.Prop}HOMEDIR()) || 'xoev/xsd/';

doc($basedir-uri || 'foobar.xsd'))

This lets users supply a value for $basedir-uri (using the $x button in the GUI) if they don’t have the schemas in the default location, which is the user’s home directory plus 'xoev/xsd/' in this example.

Please let me know where I lost you on the way.



Gerrit Imsieke
Geschäftsführer / Managing Director
le-tex publishing services GmbH
Weissenfelser Str. 84, 04229 Leipzig, Germany
Phone +49 341 355356 110, Fax +49 341 355356 510,

Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930

Geschäftsführer / Managing Directors:
Gerrit Imsieke, Svea Jelonek, Thomas Schmidt

Reply via email to