XSD with imports and namespaces?

If you aren't using namespaces or your schemas share the same namespaces, you would be much better off using xs:include rather than xs:import. Schema A can include schema B if B either has the same namespace as A or has no namespace declared (if the latter is the case, B 'adopts' the includer's namespace when included). So... something like: xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" xmlns:xs="w3.org/2001/XMLSchema" xmlns="example.com.

If you aren't using namespaces or your schemas share the same namespaces, you would be much better off using xs:include rather than xs:import. Schema A can include schema B if B either has the same namespace as A or has no namespace declared (if the latter is the case, B 'adopts' the includer's namespace when included). So... something like.

Ahhh right! Thanks – cbp May 27 '09 at 23:26.

I would think you need to set your elementFormDefault to "unqualified" if you want to avoid the prefixes on your XML elements. The rest should be fine, I think - the namespace is the same between your master and your imported XSD - that's fine. You specify the xmlns= without a prefix - that's fine.

You should be good to go. Marc.

Thanks, you're right - I was closer than I thought. However I am finding that when I create my XML document, elements that are defined in the imported XSD require that the namespace be specified (even though both the imported XSD and the actual XSD each have elementFormDefault set to 'unqualified'). – cbp May 27 '09 at 5:32.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.