Thanks for the update. Just for reference, a colleague uses an Altova alternative product, and that application throws a message about "re-writing the schema" (or some such) and this normalises the model in to one which is more generally accepted across multiple products.

This still appears to be an issue inversion 19.1 - is there any update on a fix? I am working with schemas and a WSDL that are auto generated from a .NET web service, and these define many prefixes only at the element level. This makes for a lot of refactoring before the models display correctly in ...