[Mono-list] Issues in XmlSchema.XmlSchemaElement

Atsushi Eno atsushi@ximian.com
Wed, 07 Jan 2004 12:52:18 +0900


Please keep up your effort which would be a great chance to improve 
schema compilation and validation feature.

The best thing at this point is to file it to bugzilla, with
the means we can reproduce the error. In this case, I could not find 
this problem on any of the schema file provided in the url David Sheldon 
indicated, only getting other simple type compilation error (I haven't 
look into that detail).

Atsushi Eno

Tom Cabanski wrote:

> In general, it would appear the Mono compile is doing some 
 > extra checks that, although logical, may not be in line with
 > the W3C standards; they are certainly not in line with the
> Microsoft and Xerces implementations.  One that represents 
 > the issue takes place in
> XmlSchemaElement.ValidateUniqueParticleAttribution.  
> This routine fails on the CIP4 JDF schema with the error 
 > "Ambiguous element label which is contained by -any- particle
 > was detected".  I know it fails because of the way, the
 > admittedly bizarre way, that this schema uses the any element.
> As far as I can tell, it is legal in xml schema to allow any 
 > in the way they are doing so even though it makes for ambiguity
> as the error points out.  Essentially, children qualify under 
 > the any rule as well as a specific rule.  I'd like to chat with
 > the developer(s) that are most knowledgeable on the SOM
 > implementation in Mono so I can determine the best way to proceed.