Re: [Bug report] XSV Restriction Error

"Martin Thomson" <martin.thomson@nortel.com> writes:


 Base:

>           <xsd:any namespace="##any" processContents="strict"
>                    minOccurs="0" maxOccurs="unbounded"/>

 Restriction:

>           <xsd:element name="element" type="xsd:token"/>

Not really a bug, but a feature -- because the base is strict, and
there are no elt declarations in the schema, that wildcard accepts
nothing.

So the base, which does accept something, can't be a restriction of
it.

Remember (:-) that XSV already implements the expected Schema 1.1
approach of restriction as subsumption/subset pretty much literally,
and this is one of the few cases where that bites.

ht
-- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]