Can OSB schema validate via a catalog?

Question

I have an OSB 11.1.4 question regarding XML schema validation.
I've created an XML Schema model for dealing with Party Relationships that, in a nutshell involves a schema that is considered Core and is generic (covers the core to/from links between two Parties, and the role names in the relationship for the parties and has an optional abstract content component to allow for relationship type specific content).  This allows business domain specific specialisations of the "relationship specific content" which live in their own schema and import the generic schema.  In other words specific relationship types import the Core relationship schema.
Now in an XML editor such as XMLSpy or Oxygen if I want to create an document with say relationships from two business domains I'd specify the schema location of these specialisations in the document declaration as follows:
<relationshipList xmlns="urn:ird.govt.nz:ebo:party.relationship.Core"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="urn:ird.govt.nz:ebo:party.relationship.ChildSupport file:/.../ebo/party.relationship.ChildSupport_1.0.xsd
                                    urn:ird.govt.nz:ebo:party.relationship.TaxAgent file:/.../ebo/party.relationship.TaxAgent_1.0.xsd">
    <relationship>
        ... etc
The idea in the above is that relationshipList exists in the Core schema and specialisations can extend parts o fit in a flexible way.
This all works nicely in XMLSpy or Oxygen but of course OSB ignores schema location in the document instance and within a proxy validate action I have to choose a specific resource to validate against.  The problem here is that if I reference only the Core schema then it complains about the specialised content.  If instead I choose a business domain then that domains extensions work fine but no other business extensions validate.
I can overcome this problem with a couple of hacks.  One is to include business specific imports into the Core schema so that the validator can find the other schemas but this is undesirable since it creates a dependency from the generic to the specific.   I can also do something similar in the web service schema but this not really any better as it moves the dependency from the Core Schema to the web service schema and now the web service schema has to anticipate all possible business specific schemas that might be needed.
What I really need is a "catalog" so that the validator can locate any/all of the business domain extensions that are needed.  Is this possible in OSB 11.1.4 or any other version?
regards

Answer 1

You would need to import all releated schemas in OSB as resource (you can easily import them as zipped resourced) and resolve any dependency conflicts that might arise. Once you have all the dependencies sorted out and session activated, you can validate against the generic schema and it will also validate against any referenced schemas as required.