Say I have a "diverse" topology in my CVS source tree:
 file:/Users/leon/Documents/MyCode/Development/MyProjectABC/com.myorg.tools/tools/ContainerCT.xml
file:/Users/leon/Documents/MyCode/Development/MyProjectABC/com.myorg.uber/uberUI/UberCodeCT.xml

Say both ContainerCT.xml and UberCodeCT.xml rely on an XML Schema,
component.xsd, that is to be "shared" at the MyProjectABC level.

Currently I must define a local User Catalog for each file, pointing to the
shared  component.xsd.  That means every new file in my project that references
the component.xsd will require that I create a local User Catalog entry pointing
to the shared component.xsd.

I would prefer a wildcard / pattern matching approach such that a single local
User Catalog reference such as:

  file:/Users/leon/Documents/MyCode/Development/MyProjectABC/*/component.xsd

Pointing to the shared component.xsd at:

  file:/Users/leon/Documents/MyCode/Development/MyProjectABC_Schema/component.xsd

Would result in matches for component.xsd for all files below
file:/Users/leon/Documents/MyCode/Development/MyProjectABC/*

This alters the current behavior such that if the following file is not found:

  
file:/Users/leon/Documents/MyCode/Development/MyProjectABC/com.myorg.tools/tools/component.xsd


while validating this file:
  
file:/Users/leon/Documents/MyCode/Development/MyProjectABC/com.myorg.tools/tools/ContainerCT.xml,

then this "shared" file would be used (per wildcard) to satisfy the
component.xsd reference:

file:/Users/leon/Documents/MyCode/Development/MyProjectABC_Schema/component.xsd

The above change would save a tremendous amount of time spent configuring
multiple XSD "aliases" -- it would instead allow a project level XSD "alias" for
finding schema definitions.