Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Can XML schema prevent additional unspecified elements?

From: "Joe Fawcett" <joefawcett@---------.------>
To: NULL
Date: 7/8/2008 8:57:00 AM

"J.A." <jonathan_armstrong@r...> wrote in message 
news:56e1827d-cffc-4550-82ea-d214869d9073@2......
> The funny thing is, I created a "dummy" XSD and wrote a corresponding
> XML file with  an additional unspecified element. Lo and behold, this
> time the parser (correctly) failed validation.
>
> I'm using .Net parser, as part of a basic .Net Windows XML Schema
> validation application.
>
> The problem must be something to do with the actual XSD and XML file I
> am using. The problem is that the XSD file is 2000 lines long, and the
> XML file is 81Mb. I will spare you these, and will have to do some
> more investigation....
Good luck. We probably don't need the XML though and just the part of the 
XSD that deals with the container element forr your problem section and any 
types it references.

-- 

Joe Fawcett (MVP - XML)

http://joe.fawcett.name




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent