RE: multiple namespaces

> 
> Ahh ok.  Would there be three instances then: A -> B -> A 
> (two instances of A, so no circular definition) ?

No, the system has to work out when it sees "import A" that it already knows
about A and doesn't need to load it again - just like import in Java. (This
can cause complications if you give a location hint that doesn't match the
URI where the existing A components were loaded from - are you referring to
another copy of the same schema document, or to another schema document for
different components in the same namespace? So it's best to stick to a
one-to-one relationship between schema documents and namespaces if you can.)

Michael Kay
http://www.saxonica.com/