Page 1 of 1

Master Files vs. catalog files and validation scenarios

Posted: Thu Jan 12, 2017 1:00 am
by EarlMorton
My project uses a set of a few dozen XML Schema files organized in a folder hierarchy. They are interrelated with <include> and <import> elements. Each folder in the hierarchy contains a catalog.xml file that lists the schema files in that folder, and another catalog.xml in the top folder references all the lower-level catalog.xml files. An oXygen validation scenario references that top-level catalog.xml, so instance documents validate correctly through the whole set of schemas.

We are considering using oXygen's Master File feature. How does it compare with what we already have with the catalog.xml files? Are there advantages or disadvantages either way?

Re: Master Files vs. catalog files and validation scenarios

Posted: Fri Jan 13, 2017 7:06 pm
by adrian
Hi,

An oXygen validation scenario references that top-level catalog.xml, so instance documents validate correctly through the whole set of schemas.
I'm guessing you meant to say that the scenario references the top level schema.

We are considering using oXygen's Master File feature. How does it compare with what we already have with the catalog.xml files? Are there advantages or disadvantages either way?
It's not the same thing. The Master Files Support is meant to be used to ease the validation of a hierarchy of imported/included modules (replaces validation scenarios for modules). The Master Files support is far easier to set up than validation scenarios. You just enable the support and add the top level schema (or detect it) to the list of master files. Oxygen's default validation determines if a schema being validated is part of the hierarchy (a module) of that master (schema) file and validates that master instead.
e.g.
A master XML schema file allows for easier XML schema module validation.
A master XML file allows for easier XML module (XInclude) validation.

The Master Files support does not replace the functionality of XML catalogs. Note that it does not facilitate the validation of instance documents (XML files) with a hierarchy of XML schemas. You still need an XML catalog to redirect the URI/namespace to the correct schema file. We will probably improve this support in the future and use the namespace of the master schema for this purpose.

Regards,
Adrian