I thought I had all of this
namespace stuff down pat...then I tried something new.
I'm not sure if it's my schema/XML
document or the tool that's the problem.
Here's what I've done in the
schema:
(1) I have declared a target
namespace with a namespace prefix ("abc" for our purposes here)
(2) I have a global declaration of
an element "MyElement1", which is a complex type
(3) I also have a local declaration
of "MyElement1", because this second declaration has a different set of
subelements; in the local declaration, I have not namespace-qualified the
element name as it would clash with the global declaration. This is the
only local element in the schema.
(4) I've set elementFormDefault to
"qualified"
I realized that I could not have a
default namespace in the XML instance document, because the XML processor
would consider both "MyELement1" elements as belonging to the same target
namespace, and an error would result due to the clash in declarations.
Therefore, in the XML instance document, I have namespace-prefixed all
elements _except the locally declared "MyElement1"_.
The tool I am using doesn't like
this - is there something that I'm not seeing?
TIA,
Joe Chiusano
LMI
**************************************************************************
Joseph M.
Chiusano
Logistics Management Institute
2000 Corporate Ridge
McLean, VA 22102
Email: jchiusano@lmi.org
Tel: 571.633.7722
**************************************************************************
