One final comment on our use case: When doing XSD validation, you have to be able to tell the validator which XSD to use. We have 130+ namespaces and 300-400 XSDs. For every type of XML instance document, we had to have a piece of configuration that told us which XSD that document maps to. That XSD, in turn, had to have valid schemaLocations for all its includes & imports.
One of the reasons we liked the misguided notion of XSD public IDs being the namespace of the XSD was because it made validation easier. We had created an XML catalog mapping between the namespace and a top-level XSD that transitively includes all other XSDs in that namespace. The validator could then automatically figure out which XSD to use based on the namespace encountered in the instance document. I didn't mention it before, but we had already implemented his suggested custom XMLCatalogResolver. There's some implementation stuff I don't like about it (we have to parse the XSD to figure out the namespace), but it may be something we keep. Thanks again for all the response! -- View this message in context: http://old.nabble.com/JAXP-XML-Catalog-Resolver-for-Public-IDs-tp32654884p32668429.html Sent from the Xerces - J - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
