Validation scenarios

[EarlMorton]

I am trying to understand validation scenarios.

In a set of XML Schemas that I'm working with, one of the schema modules (I'll call it A) contains a type definition that is needed by three other modules (X, Y, and Z), so each of them uses <xs:include> to make the type definition available. But A's type definition references another type that X, Y, and Z each define, but they each define it differently.

Right now I have set up a validation scenario that is applied to A, but lists all three X, Y, and Z in the "Edit scenario" dialog box. At this point, all of them validate.

But I don't understand if the sequence of X, Y, and Z in the validation scenario is significant. Does oXygen validate A three times, once for each X, Y, and Z? Does it validate it against the first one on the list and ignore the others? Does it matter what order they are in? I guess I'm assuming that I need to list all three of them, but don't even know that for certain.

I'd appreciate any help understanding how this works.

Thanks!

[Radu]

Hi Earl,

With the validation scenario you have set up, Oxygen sequentially validates X, then validates Y then validates Z. As A is imported from the main XML Schemas it will also be indirectly validated because validating an XML Schema also checks that all XML Schemas referenced directly or indirectly from it are valid.

Regards,
Radu

[EarlMorton]

Very good--thanks, Radu!