• To: priscilla@w..., xml-dev@l...
• Subject: RE: Unqualified Element without using xs:any
• From: "Don Hillsberry" <don_hillsberry@h...>
• Date: Mon, 07 Feb 2005 17:55:21 -0700
• Bcc:

Priscilla,
Thanks for your quick response...

The example you provided was the third attempt I had made when trying to 
solve this problem.
However, validating the instance document with XMLSpy 5.4 results in a 
validation error "Mandatory element 'bbb:C' expected in place of 'C'"

I am new to XML Schema validation, so I tried to research and identify the 
reason for error.  Assuming that I'm not dealing with a bug in XMLSpy, the 
closest I could get to an explaination had to do with the targetNamespace 
attribute in the "B" schema and the corresponding import with namespace 
attribute in the "A" schema.
Attempting to avoid this, is when I arrived at the only working solution I 
have found, the "xs:any"
However, "xs:any" causes issues downstream since this schema is being used 
by another comercial product that is unable to properly handle the "xs:any".

Is the <import namespace="urn:b" .../>  putting the local definitions of "C" 
and "D" into the urn:b namepsace?

If not, is there an explaination for this validation error other than a bug 
in XMLSpy?

What are your thoughts?

-
Don

• Follow-Ups:
  • RE: Unqualified Element without using xs:any
    • From: "Priscilla Walmsley" <priscilla@w...>
  • Re: Unqualified Element without using xs:any
    • From: Bob Foster <bob@o...>

• Prev by Date: Re: Re: Where does the "nothing left but toolkits" mythcome from?
• Next by Date: Re: Re: Where does the "nothing left but toolkits" myth come from?
• Previous by thread: Unqualified Element without using xs:any
• Next by thread: Re: Unqualified Element without using xs:any
• Index(es):
  • Date
  • Thread