[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Unqualified Element without using xs:any
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
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|