This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
LC Draft section 6.3.2 Schema Validity Rules, bullet 2 says "if B has Schematron constraints defined on it then they are automatically copied to D and unioned with the Schematron constraints defined on D." these usages of "Schematron constraints defined on" are in contrast to the bullets surrounding it, indeed w/ the rest of the subsection, that carefully uses the well-defined {rules} notation. The existing text would appear to introduce the possibility that Schematron constraints might be attached to schema components other than via the SML-defined {rules} schema component property, which I do not think was our intent. This bullet seems to be fully redundant with 6.3.1 bullet 3.a, so it might be a simple matter of removing 6.3.2 bullet 2 entirely.
Resolution 6/19: Fix as follows. No needsReview necessary 6.3.2 bullet 2 Proposal (replace Schematron constraints w {rules} 2x): "If a complex type D is derived by restriction or extension from {base type definition} B and if B has {rules} defined on it then they are automatically copied to D and unioned with the {rules} defined on D."
fixed per resolution.