Lists Home |
Date Index |
If you have elementFormDefault="unqualified" in your B schema document, then
it looks like a bug in XMLSpy. I tested my schemas with your instance using
both Xerces-J 2.6.2 and XSV, and it validated correctly.
Hope that helps,
> -----Original Message-----
> From: Don Hillsberry [mailto:firstname.lastname@example.org]
> Sent: Monday, February 07, 2005 7:55 PM
> To: email@example.com; firstname.lastname@example.org
> Subject: RE: [xml-dev] Unqualified Element without using xs:any
> 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
> attribute in the "B" schema and the corresponding import with
> 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?