Interesting question: is this a bug in the SOM or the Schema...
what schema?
You didn't post any part of a schema.
You say that the schema came from an international body. Can you contact
them about the fact that their schema won't parse on .NET?
The fact is that a schema is a structure that is used to validate an XML
file using basic rules. In many cases, it is possible to represent the
rules with more than one schema. In other words, it may be possible for the
schema to be re-coded so that it will work with the Microsoft SOM.
Or, perhaps not.
Clearly, one of the main goals of publishing a schema is interoperability.
If the schema that is published won't work with the largest commercial
development platform on the planet, then the international body didn't
achieve their goal. If you point out that minor changes, made early, using
the XML versioning standard, may be able to repair the problem, then you may
get some traction.
Otherwise, I'd suggest that you may want to get about three-dozen instance
documents, run them through XSD.EXE to generate some schemas, and then, by
hand, work out a schema that will work in .NET.
If you simply cannot get one to work, then read the XML as a well-formed
document, and parse it yourself... hopefully into a format that .NET *can*
read.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"rox.scott" <ro******@discussions.microsoft.com> wrote in message
news:0C**********************************@microsof t.com...
The following article says the .NET SOM will not allow what it calls
"non-deterministic" schemas:
http://msdn.microsoft.com/library/de...sticschema.asp
** Is this a bug in the SOM or in the schema ? **
Is it something that will be resolved in a future release?
Actually, it is not my schema, but one that has been given to me by an
international body, and validates on many different parsers. So what do I
do here, when the .NET parser tells me "Content model must be deterministic"?