Re: [xml] current state of validating against Schemas

[Frans Englich <frans englich telia com>]

On Monday 27 June 2005 09:04, Kasimier Buchcik wrote:
> Hi,
>
> On Sun, 2005-06-26 at 17:51 -0400, Daniel Veillard wrote:
> > On Sun, Jun 26, 2005 at 02:47:45PM -0500, Rob Benton wrote:
> > > Hey guys I have been looking through a lot of the old messages in the
> > > archive about validation using schemas.  I wanted to see what the
> > > current state of that is.  Is it still incomplete?
> >
> >   Mostly complete, but there are bugs left, depends how "hard" your
> > schemas are I guess.
>
> To summarise it a bit:
>
> 1. We don't support <redefine>s yet.
> 2. <any> with a namespace of "##other" does only work if
>    minOccurs/maxOccurs both are 1 [1].
> 3. We don't support ID/IDREF yet [2] - use identity-constraints instead
> 4. The complex content model cannot be built in some cases [3]
> 5. The subset of XPath for identity-constraints is not checked yet, so
>    be careful what expressions you use
> 6. Complex type <restriction>s are not checked for being a valid
>    restriction. I recommend using an other XS processor if you need a
>    teacher for valid restrictions.
> 7. The data-type section seems to work pretty well, except for
>    float and double values, where we don't support the whole range of
>    values (extremely low/high values)
>
> We have still some failures in the W3C test suite, mostly on the
> MS side; many of the failures are due to the tests itself being
> broken, but some of them might reveal some new bugs. I'm already a
> bit burned out by looking at every single test and compare the results
> with Xerces and XSV - there are simply too many of them (about > 7K).
> The W3C schema test suite is currently under revision by the W3C
> people, so we should get more accurate/assured results soon.
>
> If you need exact knowledge of the missing parts, search for "TODO" in
> xmlschemas.c. Many of the TODOs should be internal, but some of them
> are directly related to missing parts in the spec.

A follow up question: how does xmllint's current schema state relate to the  
Schema for Schemas?[1] With xmllint 2.6.19 it fails to compile for me, error 
message below[2].

Are the obstacles for making it work relatively minor or is support for the 
Schema for Schemas far away?

(assuming I got the facts right)


Cheers,

                Frans

1.
http://www.w3.org/2001/XMLSchema.xsd

2.

bash-2.05b$ xmllint --schema http://www.w3.org/2001/XMLSchema.xsd  tests.xml
http://www.w3.org/2001/XMLSchema.xsd:1359: element simpleType: Schemas parser 
error : simple type 'string': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:1832: element simpleType: Schemas parser 
error : simple type 'normalizedString': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:1843: element simpleType: Schemas parser 
error : simple type 'token': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:1968: element simpleType: Schemas parser 
error : simple type 'Name': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:1985: element simpleType: Schemas parser 
error : simple type 'NCName': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:2010: element simpleType: Schemas parser 
error : simple type 'IDREF': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:1892: element simpleType: Schemas parser 
error : simple type: The item type '{http://www.w3.org/2001/XMLSchema}IDREF' 
does not have a variety of atomic or union.
http://www.w3.org/2001/XMLSchema.xsd:2018: element simpleType: Schemas parser 
error : simple type 'ENTITY': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:1918: element simpleType: Schemas parser 
error : simple type: The item type '{http://www.w3.org/2001/XMLSchema}ENTITY' 
does not have a variety of atomic or union.
http://www.w3.org/2001/XMLSchema.xsd:1925: element simpleType: Schemas parser 
error : simple type 'NMTOKEN': The variety is absent.
http://www.w3.org/2001/XMLSchema.xsd:1961: element simpleType: Schemas parser 
error : simple type: The item type 
'{http://www.w3.org/2001/XMLSchema}NMTOKEN' does not have a variety of atomic 
or union.
WXS schema http://www.w3.org/2001/XMLSchema.xsd failed to compile