This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The schema has base particle of sequence restricted to a derived particle of sequence. Within the restricted sequence, the particles are not valid restrictions with the corresponding particles in the base type. However, the spec says, "2.1 Each particle in the {particles} of R is a ·valid restriction· of the particle in the {particles} of B it maps to as defined by Particle Valid (Restriction) (§3.9.6)." Since the particles are not valid restrictions, the scenario used should be scenario that checks invalidity testcase affected: msData/particles/particlesW006.xsd
Personal response. In my view this is a case where the bug is in the spec, not in the test. This is an example of a situation where all instances of R are in fact valid instances of B (because of the maxOccurs="0"), but the algorithm in the spec fails to recognize the fact. In Schema 1.1 this will be a valid restriction. I don't think there is really much to be gained at this stage in testing conformance of products to rules that are known to be deficient. Nor is there much to be gained by patching up the Schema 1.0 rules.
Even if Mike's analysis is right, this should be changed to invalid, and some of us (e.g. XSV) will get it wrong
The WG believes this test is wrong for 1.0, but that behavior is less than desirable. A new test, properly defined, is required for 1.1.