Lists Home |
Date Index |
We have been asked to work with some schemas where the definition of a
namespace is split between several schema documents, each defining a
subset of the namespace. An example of what I mean is:
schemaA.xsd defines namespaceA, and imports both schemaB.xsd and
schemaC.xsd into namespaceB. It then defines an element of each of the
types defined in schemas B and C, in namespaceB.
These files can be downloaded from
Xerces (J and C) only uses the first <xsd:import> for each namespace. It
ignores subsequent ones, leading to problems if you, as in this example,
have multiple schemas together defining elements in a schema without a
root schema for the element.
Having reported this as a bug in Xerces J, it was pointed out that
the spec makes supporting multiple imports into the same namespace up to
the processor. Further the comment made was that they believed that they
were encouraging better Schema authoring practice by disallowing this.
What do people here think? Can anyone suggest a way of validating
documents against these schemas?
David Sheldon, Client Services DecisionSoft Ltd.
Telephone: +44-1865-203192 http://www.decisionsoft.com