cvc-elt.3.1: when an element's declaration is not nillable, the xsi:nil attribute is forbidden entirely, whatever its value. PureXML only rejected xsi:nil="true" on a non-nillable element, so xsi:nil="false" slipped through. ComplexValidator.nilErrors now flags the presence of any xsi:nil on a non-nillable element via the new nilAttributeValue helper, while a nillable element still accepts xsi:nil="false" (explicitly not nilled, valid empty-or-content per its type). XSTS invalid-instances-accepted 28 -> 26 (both xsi:nil-on-non-nillable cases), no other bucket moved (valid-schemas-rejected and valid-instances-rejected held at 0 across all 14383 groups). 1452 unit tests pass. |
||
|---|---|---|
| .. | ||
| design | ||
| plans | ||
| rules | ||
| benchmarks.md | ||
| onboarding-antigravity.md | ||
| production-readiness.md | ||
| release-hurdles.md | ||
| roadmap.md | ||
| schema-validity-burndown.md | ||
| validation-coverage-registry.txt | ||
| validation-field-registry.txt | ||
| xsts-deviations.md | ||