XSTS methodology and results

pyxsd measures agreement with the W3C XML Schema Test Suite (XSTS) on catalogued schema and instance verdicts. This page defines the corpus, processor profiles, adapters, outcomes, and baseline gates behind the results. For the distinction between XML parsing, schema compilation, instance assessment, and binding, start with XML and XSD validation.

The headline is raw agreement on checked cases:

checked = pass + fail
agreement on checked cases = 100 * pass / checked

A known or disputed failure remains a failure in this calculation. There is no adjusted rate, best-of-profile result, or combined XSD 1.0/1.1 rate.

Corpus and case selection

The corpus is the tests/xsts/corpus git submodule, pinned to w3c/xsdtests revision 7bc3365c652a322f3d762021b3879eb92dae7e30. Only its main suite.xml supplies the headline cases. The catalogue emits 41,735 cases per profile: 15,378 schema cases and 26,357 instance cases, including cases that the selected profile cannot check. These are test cases, not a count of XSD features or unique schema documents.

The harness follows test-set references, groups, schema tests, and instance tests. A case ID is set/group/test; baseline keys add engine and kind: engine:set/group/test:schema or engine:set/group/test:instance. Non-applicable cases remain in the emitted inventory and outcome totals; they do not enter pass + fail.

Profiles and expectations

Profile

Claimed version tokens

pyxsd compilation

Full-XSTS xmlschema class

xsd11 (default)

1.1 only

xsd_version="1.1"

XMLSchema11

xsd10

1.0 only

xsd_version="1.0"

XMLSchema10

The selection rules are:

  1. At each test-set, group, and test level, an absent version list imposes no restriction. Tokens within a list are a disjunction: any claimed token suffices. Each enclosing level must also apply.

  2. On expected/@version, tokens are a conjunction: the profile must claim every listed token. Exactly one matching version-tagged expectation takes precedence over an unversioned expectation.

  3. If no tagged expectation matches, exactly one unversioned expectation is the fallback. If only unmatched tagged expectations exist, the case is not-applicable. Missing expectations or ambiguous matches are metadata-error, not guessed verdicts.

  4. valid means expected valid; invalid and invalid-latent mean expected invalid. Other values, including notKnown, indeterminate, implementation-defined, and implementation-dependent, are non-Boolean and therefore not-checkable when the adapter otherwise completes.

The profiles do not claim additional dimensions such as Unicode-version tokens or full-xpath-in-CTA. A case gated exclusively to an unclaimed dimension is not-applicable, not an omitted test. XML 1.0/1.1 parsing and XSD 1.0/1.1 processor modes are independent choices; see XML and XSD validation.

What the adapters execute

The pyxsd adapter uses ParseModes.NAMESPACED and compiles with the selected profile’s matching xsd_version. A schema case observes schema-phase error-severity findings. An instance case compiles its group schema and observes instance-phase error-severity findings after binding. Warnings alone do not make either phase invalid. A PyXSDError supplies an invalid verdict for the affected phase; an unexpected exception is a harness-level error, not evidence of invalidity.

An instance verdict requires a successfully compiled schema. If the group schema fails to compile, the instance result is adapter-gap, not a false accept or false reject. The separate schema case still tests schema legality. Malformed or unreadable instance input is treated as an invalid instance when the supplied schema compiles; the adapter probes the schema separately when necessary to distinguish those phases. See Validation for the reports that the adapter reduces to these verdicts.

Schema composition and synthesized context

  • One schema document: use its path directly.

  • Several schema documents: write an otherwise-empty driver schema that imports namespaced principal documents and includes no-target-namespace documents, preserving their listed order. Documents already composed by another listed member through include/import/redefine/override are not loaded twice. A composition cycle uses its first-listed member as the load representative. Absolute locations preserve each source document’s own relative-reference base.

  • No supplied schema: the reporting runner and PR gate enable pyxsd’s permissive-schema synthesis for instance-only groups. The wrapper normally declares the instance root as xs:anyType in its namespace, allowing xsi:type and built-in datatypes to be checked. If a resolvable instance schema hint already supplies that root declaration, the wrapper omits it to avoid a duplicate; hinted-schema compilation failures are not hidden. Synthesis is an adapter approximation, not an extra corpus schema case. The xmlschema adapter does not enable synthesis, so a no-schema group is an adapter-gap for that engine.

For pyxsd instance runs, schema-location hints are resolved relative to the instance and forwarded to compilation. If an advisory hint collides with a supplied schema that already declares the root, the adapter can retry a temporary copy without those hints. It does not strip hints from synthesized contexts. Missing resources or unrepresentable bundles can prevent adapter execution; they are not silently discarded from the report.

Synthetic loading context is not an authored import in another document. pyxsd audits cross-namespace XSD component references against the referencing document’s own direct imports and effective target namespace, with built-in vocabulary exemptions. Neither a driver’s import nor a caller mapping or instance hint satisfies that document’s import duty; a missing import is import-required. Wildcard notQName is intentionally not audited; annotation payloads, foreign markup, QName-valued defaults/fixed values, and XPath expressions are also excluded. A reference that resolves to no namespace is allowed regardless of authored imports, matching pyxsd’s lenient bare-name lookup, so no-namespace enforcement is incomplete. The audit leaves global component resolution unchanged, rather than isolating each document’s component table.

Time budgets

The reporting CLI defaults to --timeout 60; CI uses --timeout 180 for slower or loaded runners. Workers run batches in separate processes with separate scratch directories. Driver operations use wall-clock SIGALRM timers where available; this is not a process-killing sandbox or a portable hard limit on all setup work. Platforms without SIGALRM skip that timer. The xmlschema adapter times compilation and instance checking separately.

A reported timeout supplies no validity verdict. It remains outside the checked denominator and visible in the outcome totals. Investigate a budget crossing and record the timeout, machine, and worker count; do not silently change the budget to improve agreement. An unexpected error likewise does not become a verdict.

Outcome definitions

Every case has one outcome per selected engine:

Outcome

Meaning

In checked denominator?

pass

Observed Boolean verdict matches the selected corpus expectation.

Yes

fail

Observed Boolean verdict contradicts that expectation.

Yes

not-applicable

Version-token or expectation selection excludes the case for this profile.

No

not-checkable

Selected expectation is non-Boolean; it is not forced into valid/invalid.

No

adapter-gap

Adapter cannot drive the case, for example an unusable schema context or unsupported bundle.

No

metadata-error

Catalogue expectations are missing or ambiguous.

No

timeout

Driver reports that the operation exceeded its time budget.

No

error

Unexpected engine/harness exception, missing instance file, or absent required verdict.

No

Metadata errors are resolved before execution, then applicability. For an applicable case, adapter gaps, reported timeouts, and errors take precedence over expectation comparison. Only a completed, checkable Boolean comparison produces pass or fail.

A false accept is an observed valid verdict with an invalid expectation; a false reject is an observed invalid verdict with a valid expectation. These directions come from the selected expectation and observed verdict, never from a disposition or another engine’s answer.

Interpreting residual failures

The generated tables at the end of this page keep three facts separate:

  1. Observed outcome: the raw baseline pass, fail, or non-verdict outcome.

  2. Cross-profile expectation relation: how the corpus’s selected expectations relate under XSD 1.0 and 1.1, independent of observed outcomes.

  3. Disposition: reviewed explanatory metadata, such as an implementation gap, version-switch candidate, platform limit, queried corpus, spec-correct divergence, or adapter limitation. A case without reviewed classification remains visibly unclassified.

The generated cross-profile table separates intentional corpus version splits from same-expectation and reverse-split cases. An intentional split expects invalid in 1.0 and valid in 1.1 and is a candidate for version-specific implementation work. A same-expectation case cannot inherit that label merely because its observed outcomes differ. A reverse split needs its selected 1.0 verdict. Every case in these views remains a raw XSD 1.0 failure while it is listed.

The generated census lists explicit case IDs, classification counts, and unclassified cases. Disposition validation rejects nonexistent cases, duplicate claims, missing baseline results, and unsupported categories. It accepts a case whose outcome has improved; that case leaves the active census without a disposition edit. Classification neither changes applicability nor removes failures from pass + fail. Regenerate these tables after every reviewed baseline update so the published counts remain current.

Type-only document roots

The type-only-root cases define named types but no global element declaration matching the document root. Their xsi:type supplies a governing type. XSD 1.1 Structures §3.3.4.6 permits strict assessment against a known governing type even when there is no governing element declaration. This is not permission to accept every undeclared root.

The residual mechanism was an unknown-root error before pyxsd’s existing declared-root xsi:type dispatch could run, producing false rejects. Supporting this case shape requires type-only root assessment and binding without inventing element-declaration properties such as nillability or defaults. Ordinary xsi:type handling on declared roots is a different path. The generated census shows any cases that still fail in either profile.

DTD-dependent ENTITY and ENTITIES values

xs:ENTITY values must name unparsed entities declared in the instance document’s DTD; xs:ENTITIES is a nonempty list of those values. An NCName lexical check alone cannot establish that requirement. The earlier false accepts came from missing declaration information, not corpus errors. pyxsd now lazily collects unparsed-entity declarations from the instance prolog/internal subset when the compiled schema can validate these types, including derived types and defaults. Complete evidence rejects undeclared names; no DOCTYPE means an empty, complete set. Unrelated schemas skip the declaration-collection parse. An unparsed entity declaration names an external resource, but checking its name does not fetch it.

External subsets and external parameter entities remain unfetched and make the evidence incomplete: missing names stay lexical-only, with one advisory when a declaration check is skipped. Internal parameter entities are expanded, so declarations they carry are collected. Caller-supplied trees without pyxsd source provenance, custom-policy parser results, and non-seekable instance streams passed to top-level pyxsd.parse() remain lexical-only too, even with an explicit schema. Compiled Schema.parse() supports prolog replay for those streams. Document.revalidate() carries the original parse’s declaration evidence across the serialized reparse, so a declared value stays valid; a document parsed without evidence stays lexical-only. See Validation for provenance and reread limits. Collection preserves security handlers and the default, protected, and strict profiles. This is neither DTD validation nor a change to entity expansion or parser hardening; see XML and XSD validation and XML security and untrusted input. Resolved cases leave the generated active census automatically; remaining limitations are not claimed fixed.

Other reviewed mechanisms

Pattern-facet compilation now uses the selected processor version’s regex grammar, rejecting XSD 1.1-only forms in 1.0 mode. Direct pyxsd.facets.compile_pattern() calls still default to 1.1. Compare the 1.0 and 1.1 definitions; this fixes the reviewed grammar version-switch mechanism, not every regex disagreement. The queried astral-plane regex cases link to W3C bug 4113; challenged metadata is not permission to rewrite its expected verdict. The XML 1.1 cases reflect the Expat lexer limitation, independent of the XSD processor mode. Each mechanism keeps its recorded raw outcome; agreement by another engine does not settle a specification dispute.

Direct-import enforcement likewise does not fix adjacent composition defects. Cross-document duplicate globals, redefine/override merge and restriction gaps, import-target namespace mismatch (schF6), and no-namespace type binding (schF2.v, schG2.v) remain limitations. The generated census below is the source for current residual case IDs and counts, rather than a fixed total in this prose.

Why extra-suite.xml is separate

Upstream’s extra-suite.xml retains tests removed from the main suite. At the pinned revision it emits 215 case IDs: 92 duplicate the main introspection set, and 123 are distinct historical precisionDecimal cases (54 schema and 69 instance). Those unique cases are not XSD 1.0 cases; 122 apply under the current XSD 1.1 token rules.

precisionDecimal was removed before the final XSD 1.1 Recommendation and is described separately in a W3C Working Group Note as an implementation-defined datatype, not a required built-in type. These historical cases are outside every headline denominator. Their omission is neither deferred main-suite testing nor missing main-suite coverage. They stay optional unless a separate historical-compatibility goal emerges, with a separate report and no combined rate. The current reporting CLI selects suite.xml; it does not offer an --suite-file extra-suite.xml option.

Two distinct xmlschema roles

Here, oracle means a differential signal, not normative truth. The XSD Recommendations and case-specific specification analysis remain the authority.

Curated manifest differential oracle

tests/test_oracle.py compares pyxsd and xmlschema over 390 curated manifest cases, including 184 with instances and 122 marked XSD 1.1. It compares schema verdicts and, when both are available, instance verdicts. Required CI enables it with PYXSD_RUN_ORACLE=1. Only manifest cases marked xsd11 use XMLSchema11; the others use xmlschema’s XSD 1.0 class.

Fourteen case-specific divergences have written reasons and are skipped. Unexpected exceptions on either side are harness failures, never agreement. This suite detects unexpected implementation disagreement; it does not prove that either implementation satisfies the specification.

Full-XSTS comparison engine

The XSTS runner can instead score xmlschema against the same main-suite expectations and profile rules as pyxsd, with its own adapter outcomes. The XSD 1.1 baseline records both engines; the XSD 1.0 baseline records pyxsd only. An xmlschema disagreement with the corpus is an oracle-erratum candidate, not proof the corpus is wrong. Different adapter gaps also mean different checked denominators, shown explicitly below.

The PR gate checks recorded XSTS outcomes against the baseline; it does not require pyxsd to agree with xmlschema’s verdict on every case. The generated engine columns are scoped measurements, not an engine ranking.

See pyxsd compared with xmlschema for Python API and feature tradeoffs, and pyxsd compared with libxml2 for engine scope and a separately dated preliminary XSD 1.0 probe. That probe is not part of the generated pyxsd headline.

Reproducing reports and baseline gates

Run from the repository root after installing development dependencies and initializing the corpus submodule. Use a clean bytecode cache for measurements to avoid stale .pyc files after same-length source edits:

git submodule update --init tests/xsts/corpus
export PYTHONPYCACHEPREFIX=$(mktemp -d)

# Exploratory slice: not a full-profile measurement.
uv run python tests/report_xsts.py --profile xsd11 --limit 500

# Full comparison with every baseline change surfaced.
uv run python tests/report_xsts.py --profile xsd11 --engine both --timeout 180 \
    --baseline tests/xsts/baseline-xsd11.toml

# Dispatch-style regression gate, observing pyxsd only.
uv run python tests/report_xsts.py --profile xsd10 --engine pyxsd --timeout 180 \
    --baseline tests/xsts/baseline-xsd10.toml --enforce

# Check that committed documentation matches its source data; no engine run.
uv run python tests/report_xsts_docs.py --check
  • Ordinary local report: without a baseline, reports current outcomes and returns zero even when known failures exist. --filter, --limit, and --list-only support exploration; a slice is not the headline population.

  • Baseline diff: --baseline reports changed, new, and removed keys and exits 1 on any difference, including improvements and keys absent from a partial run. This is stricter than a regression-only gate.

  • Enforcement: --enforce requires --baseline. It exits 2 if a recorded pass no longer passes, or a newly observed key is fail, adapter-gap, timeout, or error; otherwise it exits zero. It ignores unobserved keys, improvements, and changes among existing non-pass outcomes. New metadata-error results are reported but do not themselves trigger this enforcement rule. A green enforcement run is not an all-pass claim.

  • Required XSD 1.1 PR gate: tests/test_xsts_suite.py runs with PYXSD_RUN_XSTS=1 and PYXSD_XSTS_TIMEOUT=180 after the coverage run in CI. It executes both engines and asserts an exact match to the XSD 1.1 baseline, including improvements. This is not the looser CLI --enforce rule.

  • Dispatch-only workflow: XSD 1.0 and on-demand XSD 1.1 reports/slices use .github/workflows/xsts.yml. Choose either profile or both and an optional limit. Each uses --engine pyxsd --enforce --timeout 180 against its own baseline and uploads JSON; “both” means separate profiles, not a combined rate.

Review baseline differences before accepting them. Regenerate XSD 1.1 with --engine both so the recorded xmlschema entries are retained; regenerate XSD 1.0 with --engine pyxsd. Exact commands and contributor details are in the harness README.

JSON reports carry run provenance, full per-engine outcomes, kind splits, failure directions, and baseline changes when a baseline is supplied. Run metadata records the suite file, profile, completeness, case count, revisions, versions, Python/platform, timeout, jobs, command, and completion timestamp. Filtered or limited runs record complete = false.

The tables below are generated from reviewed checked-in baselines, not a live run. Per-case baseline reviews do not establish that every entry came from a new full run. Full-run metadata, when present, retains that run’s provenance; absent provenance is explicitly reported as not recorded. The documentation generator never substitutes its own wall-clock timestamp.

Measurement limits

The upstream README limits XSTS to top-level validity outcomes. These results establish neither W3C certification nor complete XSD feature or interaction coverage, complete PSVI, diagnostic quality, API completeness, performance, security, or correctness on untested inputs. Parser policy, adapters, version selection, and non-verdict outcomes define the measurement’s scope. See XML and XSD validation for the concepts and XML security and untrusted input for handling untrusted XML.

Results below are generated from the pinned main suite.xml corpus and the checked-in pyxsd baselines. The optional extra-suite.xml is outside every denominator on this page. A checked case is pass + fail; agreement on checked cases is 100 * pass / (pass + fail), with no adjustment for dispositions and no combined XSD 1.0/1.1 rate.

Source data

Both checked-in baselines and the pinned main suite.xml are source data. The optional extra-suite.xml is not part of any denominator on this page.

Profile

Baseline

Suite file

Cases

XSD 1.1

tests/xsts/baseline-xsd11.toml

suite.xml

41,735

XSD 1.0

tests/xsts/baseline-xsd10.toml

suite.xml

41,735

Timestamps, revisions, versions, and commands below are read from baseline metadata, never from the generation time.

XSD 1.1

Field

Value

profile

xsd11

suite_file

suite.xml

case_count

41735

complete

true

engines

pyxsd, xmlschema

timeout_seconds

180.0

jobs

8

command

python tests/report_xsts.py –profile xsd11 –engine both –jobs 8 –timeout 180 –write-baseline tests/xsts/baseline-xsd11.toml

source_revision

544f45c9b06b704a09e45153793737fdd410421d

corpus_revision

7bc3365c652a322f3d762021b3879eb92dae7e30

python_version

3.11.16

platform

macOS-27.0.1-arm64-arm-64bit

engine_versions

elementpath==5.1.4, pyxsd==1.2.1, xmlschema==4.3.2

run_completed_at

2026-11-01T19:47:07.042972+00:00

XSD 1.0

Field

Value

profile

xsd10

suite_file

suite.xml

case_count

41735

complete

true

engines

pyxsd

timeout_seconds

180.0

jobs

8

command

python tests/report_xsts.py –profile xsd10 –engine pyxsd –jobs 8 –timeout 180 –write-baseline tests/xsts/baseline-xsd10.toml

source_revision

544f45c9b06b704a09e45153793737fdd410421d

corpus_revision

7bc3365c652a322f3d762021b3879eb92dae7e30

python_version

3.11.16

platform

macOS-27.0.1-arm64-arm-64bit

engine_versions

elementpath==5.1.4, pyxsd==1.2.1

run_completed_at

2026-11-01T19:48:03.456705+00:00

Outcomes and checked agreement

Counts are per profile and engine. Only pass and fail are checked verdicts; every other outcome is outside the checked denominator.

Outcome

XSD 1.1 pyxsd

XSD 1.1 xmlschema

XSD 1.0 pyxsd

pass

41,530

41,448

39,306

fail

75

105

132

not-applicable

107

107

2,258

not-checkable

14

14

15

adapter-gap

9

60

24

metadata-error

0

0

0

timeout

0

0

0

error

0

1

0

Total

41,735

41,735

41,735

Checked (pass + fail)

41,605

41,553

39,438

Agreement on checked

99.8197%

99.7473%

99.6653%

Schema and instance splits

Cases and checked verdicts within each emitted test kind.

Profile

Engine

Kind

Cases

pass

fail

Checked

Agreement

XSD 1.1

pyxsd

schema

15,378

15,314

20

15,334

99.8696%

XSD 1.1

pyxsd

instance

26,357

26,216

55

26,271

99.7906%

XSD 1.1

xmlschema

schema

15,378

15,317

17

15,334

99.8891%

XSD 1.1

xmlschema

instance

26,357

26,131

88

26,219

99.6644%

XSD 1.0

pyxsd

schema

15,378

14,321

72

14,393

99.4998%

XSD 1.0

pyxsd

instance

26,357

24,985

60

25,045

99.7604%

Failure directions

A false accept is an observed valid verdict where the corpus expects invalid; a false reject is the opposite. Direction comes only from the corpus expectation and the observed verdict, never from a disposition.

Profile

Engine

Kind

False accepts

False rejects

No direction

Failures

XSD 1.1

pyxsd

schema

18

2

0

20

XSD 1.1

pyxsd

instance

38

17

0

55

XSD 1.1

pyxsd

Total

56

19

0

75

XSD 1.1

xmlschema

schema

15

2

0

17

XSD 1.1

xmlschema

instance

68

20

0

88

XSD 1.1

xmlschema

Total

83

22

0

105

XSD 1.0

pyxsd

schema

56

16

0

72

XSD 1.0

pyxsd

instance

44

16

0

60

XSD 1.0

pyxsd

Total

100

32

0

132

Combined-profile applicability

Counts are for pyxsd across the two profiles. A case is checked when its pyxsd outcome is pass or fail; a non-verdict outcome or a case outside the main suite is not checked.

Category

Cases

Checked in both profiles

39,417

Checked only in XSD 1.1

2,188

Checked only in XSD 1.0

21

Checked in at least one profile

41,626

Checked in neither profile

109

Total main-suite cases

41,735

Cross-profile failure relationships

This view covers the checked pyxsd failures in XSD 1.0. The relation comes from each profile’s selected corpus expectations, never from an outcome.

Of the 132 checked XSD 1.0 failures, 66 pass under XSD 1.1, 61 fail, and 5 are not checked.

Relation

Pass in 1.1

Fail in 1.1

Not checked

Total

invalid-in-1.0-valid-in-1.1

55

0

0

55

same-valid

6

16

4

26

valid-in-1.0-invalid-in-1.1

5

0

0

5

same-invalid

0

45

0

45

not-comparable

0

0

1

1

Total

66

61

5

132

Intentional version-split failures

This view lists 55 checked XSD 1.0 failures with a corpus expectation that is invalid under XSD 1.0, valid under XSD 1.1, and a passing XSD 1.1 outcome. They remain raw failures, not accepted passes, and are candidates for version-specific implementation work. Same-expectation cases are never included here merely because their outcomes differ across profiles.

Case

Kind

Disposition

ElemDecl/idconstrdefs00301m/idConstrDefs00301m2_n

instance

xsd10-multiple-id-attributes

ElemDecl/valueconstraint01001m2/valueConstraint01001m2

schema

xsd10-id-value-constraints

ElemDecl/valueconstraint01001m3/valueConstraint01001m3

schema

xsd10-id-value-constraints

ElemDecl/valueconstraint01001m5/valueConstraint01001m5

schema

xsd10-id-value-constraints

ElemDecl/valueconstraint01001m6/valueConstraint01001m6

schema

xsd10-id-value-constraints

MGroup/particles00104m1/particles00104m1

schema

xsd10-all-group-relaxations

MS-Additional2006-07-15/addB078/addB078

schema

xsd10-id-value-constraints

MS-Additional2006-07-15/addB078A/addB078A

schema

xsd10-id-value-constraints

MS-Additional2006-07-15/addB078B/addB078B

schema

xsd10-id-value-constraints

MS-Additional2006-07-15/addB118/addB118

schema

xsd10-intensional-restriction

MS-Additional2006-07-15/addB121/addB121

schema

xsd10-wildcard-upa-relaxation

MS-Additional2006-07-15/addB153/addB153

schema

xsd10-wildcard-upa-relaxation

MS-Additional2006-07-15/addB156/addB156.i

instance

xsd10-inline-schema-composition

MS-Additional2006-07-15/addB158/addB158.i

instance

xsd10-inline-schema-composition

MS-Additional2006-07-15/isDefault060_2/isDefault060_2

schema

xsd10-id-value-constraints

MS-Additional2006-07-15/isDefault069/isDefault069

schema

xsd10-id-value-constraints

MS-Attribute2006-07-15/attZ013a/attZ013a

schema

xsd10-id-value-constraints

MS-Attribute2006-07-15/attZ013b/attZ013b

schema

xsd10-id-value-constraints

MS-Attribute2006-07-15/attZ014a/attZ014a.i

instance

xsd10-multiple-id-attributes

MS-Attribute2006-07-15/attZ014b/attZ014b.i

instance

xsd10-multiple-id-attributes

MS-AttributeGroup2006-07-15/attgC010/attgC010

schema

xsd10-attribute-group-circularity

MS-AttributeGroup2006-07-15/attgC020/attgC020

schema

xsd10-attribute-group-circularity

MS-AttributeGroup2006-07-15/attgC031/attgC031

schema

xsd10-attribute-group-circularity

MS-AttributeGroup2006-07-15/attgD015/attgD015

schema

xsd10-attribute-group-circularity

MS-ComplexType2006-07-15/ctM004/ctM004

schema

xsd10-multiple-id-attributes

MS-DataTypes2006-07-15/anyURI_a001_1336/anyURI_a001_1336

schema

xsd10-anyuri-value-space

MS-DataTypes2006-07-15/anyURI_a003_1338/anyURI_a003_1338

schema

xsd10-anyuri-value-space

MS-DataTypes2006-07-15/anyURI_b004_1354/anyURI_b004_1354

schema

xsd10-anyuri-value-space

MS-DataTypes2006-07-15/anyURI_b006_1356/anyURI_b006_1356

schema

xsd10-anyuri-value-space

MS-DataTypes2006-07-15/dateTime011_2008/dateTime011_2008.i

instance

xsd10-year-zero

MS-DataTypes2006-07-15/double018_1956/double018_1956.i

instance

xsd10-float-double-positive-inf

MS-DataTypes2006-07-15/dtZ107447_a_2245/dtZ107447_a_2245

schema

xsd10-id-value-constraints

MS-DataTypes2006-07-15/float018_1917/float018_1917.i

instance

xsd10-float-double-positive-inf

MS-Element2006-07-15/elemZ016/elemZ016.i

instance

xsd10-multiple-id-attributes

MS-Element2006-07-15/elemZ032a/elemZ032a

schema

xsd10-id-value-constraints

MS-Element2006-07-15/elemZ032b/elemZ032b

schema

xsd10-id-value-constraints

MS-Group2006-07-15/groupH021v/groupH021v

schema

xsd10-intensional-restriction

MS-IdentityConstraint2006-07-15/idZ011/idZ011

schema

xsd10-id-value-constraints

MS-ModelGroups2006-07-15/mgA016/mgA016

schema

xsd10-all-group-relaxations

MS-ModelGroups2006-07-15/mgO001/mgO001

schema

xsd10-all-group-relaxations

MS-ModelGroups2006-07-15/mgO018/mgO018

schema

xsd10-all-group-relaxations

MS-Particles2006-07-15/particlesFb003/particlesFb003

schema

xsd10-wildcard-upa-relaxation

MS-Particles2006-07-15/particlesHa161/particlesHa161

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesHb008/particlesHb008

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesHb011/particlesHb011

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesS002/particlesS002

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesT002/particlesT002

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesT009/particlesT009

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesZ001/particlesZ001.i

instance

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesZ023/particlesZ023

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesZ024/particlesZ024

schema

xsd10-intensional-restriction

MS-Particles2006-07-15/particlesZ028/particlesZ028

schema

xsd10-intensional-restriction

MS-Schema2006-07-15/schL3/schL3

schema

xsd10-all-group-relaxations

MS-Schema2006-07-15/schL5/schL5

schema

xsd10-intensional-restriction

MS-Wildcards2006-07-15/wildZ013/wildZ013

schema

xsd10-attribute-wildcard-errata

Residual dispositions

Dispositions are reviewed metadata. They never change pass, fail, or the checked denominator, and no adjusted agreement rate is computed from them. Entries and case counts below include only current failures; a case that starts passing leaves this view without a disposition edit.

Profile

Checked failures

Classified

Unclassified

XSD 1.1

75

48

27

XSD 1.0

132

84

48

Reviewed disposition entries

ID

Category

Profiles

Cases

Title

xsd10-all-group-relaxations

version-switch-candidate

XSD 1.0

5

XSD 1.0 xs:all restrictions are not enforced

xsd10-anyuri-value-space

version-switch-candidate

XSD 1.0

4

XSD 1.0 anyURI value space is not enforced

xsd10-attribute-group-circularity

version-switch-candidate

XSD 1.0

4

XSD 1.0 forbids circular attributeGroup references outside redefine

xsd10-attribute-wildcard-errata

version-switch-candidate

XSD 1.0

1

XSD 1.0 attribute wildcard intersection and union errata case

xsd10-complex-content-from-simple-content

version-switch-candidate

XSD 1.0

1

XSD 1.0 accepts an empty complexContent extension of a simpleContent base

xsd10-conditional-inclusion

version-switch-candidate

XSD 1.0

1

XSD 1.0 profile does not evaluate vc: conditional inclusion

xsd10-float-double-positive-inf

version-switch-candidate

XSD 1.0

2

XSD 1.0 float and double lexical spaces reject +INF

xsd10-id-value-constraints

version-switch-candidate

XSD 1.0

15

XSD 1.0 must reject value constraints on ID-typed elements and attributes

xsd10-inline-schema-composition

version-switch-candidate

XSD 1.0

2

XSD 1.0 rejects a schema location or inline schema seen after an item from its target namespace

xsd10-intensional-restriction

version-switch-candidate

XSD 1.0

13

XSD 1.0 intensional restriction rules are not enforced

xsd10-multiple-id-attributes

version-switch-candidate

XSD 1.0

5

XSD 1.0 must reject multiple ID-typed attributes and duplicate ID values

xsd10-unversioned-11-wildcard-vocabulary

spec-correct-divergence

XSD 1.0

5

XSD 1.0 profile rejects unversioned XSD 1.1-only wildcard vocabulary that the corpus expects valid

xsd10-valid-type-constructs

version-switch-candidate

XSD 1.0

4

XSD 1.0 mode rejects type constructs that XSD 1.0 accepts

xsd10-wildcard-upa-relaxation

version-switch-candidate

XSD 1.0

3

XSD 1.0 UPA rejects element and wildcard competition

xsd10-year-zero

version-switch-candidate

XSD 1.0

1

XSD 1.0 dateTime rejects year zero

xsts-astral-regex-queried

queried-corpus

XSD 1.1

22

Astral-plane XSD regex tests the corpus marks queried (W3C bug 4113)

xsts-circular-redefine-underspecified

queried-corpus

XSD 1.1, XSD 1.0

4

Circular redefine groups remain accepted where the corpus expects invalid instances

xsts-duplicate-global-attribute-group

implementation-gap

XSD 1.1, XSD 1.0

2

Duplicate global attributeGroup declarations from two imported documents are accepted

xsts-duplicate-global-element

implementation-gap

XSD 1.1, XSD 1.0

4

Duplicate global element declarations from two imported documents are accepted

xsts-identity-constraint-global-reference

implementation-gap

XSD 1.1, XSD 1.0

2

A keyref refer QName is not required to name a global key or unique

xsts-import-namespace-mismatch

implementation-gap

XSD 1.1, XSD 1.0

2

An import namespace that disagrees with the imported schema’s target namespace is accepted

xsts-no-namespace-type-reference

implementation-gap

XSD 1.1, XSD 1.0

4

Unprefixed type references in a no-namespace schema resolve to same-named types in another namespace

xsts-override-composition

implementation-gap

XSD 1.1

2

Circular and no-op xs:override documents are accepted

xsts-redefine-attribute-group-merge

implementation-gap

XSD 1.1, XSD 1.0

2

A self-referential redefined attribute group can introduce duplicate attribute uses

xsts-redefine-attribute-group-restriction

implementation-gap

XSD 1.1, XSD 1.0

2

A redefined attribute group is not checked as a valid restriction of the original

xsts-redefine-default-attributes-apply

implementation-gap

XSD 1.1

1

A base type’s default attribute group is not applied through a redefine extension

xsts-redefine-simple-type-enforcement

implementation-gap

XSD 1.1, XSD 1.0

2

A redefined simpleType’s restriction is not enforced on instances

xsts-type-only-root-xsi-type

implementation-gap

XSD 1.1, XSD 1.0

12

Document roots governed only by xsi:type have no global element declaration

xsts-xml11-lexer-floor

platform-limit

XSD 1.1

5

XML 1.1 documents cannot be lexed by the expat-based parser

Failure census

Every checked pyxsd failure appears below with its observed outcome, corpus expectation relation, and disposition. unclassified means no reviewed disposition claims the case.

Profile

Case

Kind

Observed

Expectation relation

Disposition

XSD 1.1

Assert/assert011/assert011.xsd

schema

fail

same-valid

unclassified

XSD 1.1

CTA/cta0010/cta0010.n01

instance

fail

same-invalid

unclassified

XSD 1.1

CTA/cta0013/cta0013.n02

instance

fail

same-invalid

unclassified

XSD 1.1

CType/targetns00101m/targetNS00101m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.1

Complex/complex017/complex017.xsd

schema

fail

same-invalid

unclassified

XSD 1.1

Complex/complex018/complex018.xsd

schema

fail

same-invalid

unclassified

XSD 1.1

ConditionalInclusion/s4_2_2si01/s4_2_2si01s

schema

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB142/addB142.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB159/addB159.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB161/addB161.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB162/addB162.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB164/addB164.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB166/addB166.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB181/addB181.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-Additional2006-07-15/addB187/addB187.v

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.1

MS-Additional2006-07-15/addB191/addB191.v

instance

fail

same-invalid

unclassified

XSD 1.1

MS-AttributeGroup2006-07-15/attgB013/attgB013

schema

fail

same-invalid

xsts-duplicate-global-attribute-group

XSD 1.1

MS-AttributeGroup2006-07-15/attgC028/attgC028

schema

fail

same-invalid

xsts-redefine-attribute-group-restriction

XSD 1.1

MS-AttributeGroup2006-07-15/attgD017/attgD017

schema

fail

same-invalid

xsts-redefine-attribute-group-merge

XSD 1.1

MS-DataTypes2006-07-15/anyURI_a004_1339/anyURI_a004_1339.i

instance

fail

same-invalid

unclassified

XSD 1.1

MS-DataTypes2006-07-15/gMonth002_2061/gMonth002_2061.v

instance

fail

same-valid

unclassified

XSD 1.1

MS-DataTypes2006-07-15/gMonth004_2063/gMonth004_2063.v

instance

fail

same-valid

unclassified

XSD 1.1

MS-Element2006-07-15/elemM002/elemM002

schema

fail

same-invalid

unclassified

XSD 1.1

MS-Element2006-07-15/elemZ026/elemZ026

schema

fail

same-invalid

unclassified

XSD 1.1

MS-IdentityConstraint2006-07-15/idB005/idB005

schema

fail

same-invalid

unclassified

XSD 1.1

MS-IdentityConstraint2006-07-15/idC019/idC019

schema

fail

same-invalid

xsts-identity-constraint-global-reference

XSD 1.1

MS-Regex2006-07-15/reJ11/reJ11.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ13/reJ13.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ19/reJ19.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ21/reJ21.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ23/reJ23.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ25/reJ25.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ29/reJ29.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ31/reJ31.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ33/reJ33.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ35/reJ35.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ61/reJ61.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ69/reJ69.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ75/reJ75.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reJ77/reJ77.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reL98/reL98.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reL99/reL99.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reM98/reM98.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reN99/reN99.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reS21/reS21.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reS42/reS42.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reT63/reT63.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Regex2006-07-15/reT84/reT84.i

instance

fail

same-invalid

xsts-astral-regex-queried

XSD 1.1

MS-Schema2006-07-15/schF2/schF2.v

instance

fail

same-valid

xsts-no-namespace-type-reference

XSD 1.1

MS-Schema2006-07-15/schF6/schF6

schema

fail

same-invalid

xsts-import-namespace-mismatch

XSD 1.1

MS-Schema2006-07-15/schG11/schG11

schema

fail

same-invalid

xsts-duplicate-global-element

XSD 1.1

MS-Schema2006-07-15/schG2/schG2.v

instance

fail

same-valid

xsts-no-namespace-type-reference

XSD 1.1

MS-Schema2006-07-15/schG6/schG6

schema

fail

same-invalid

xsts-duplicate-global-element

XSD 1.1

MS-Schema2006-07-15/schU4/schU4.i

instance

fail

same-invalid

xsts-circular-redefine-underspecified

XSD 1.1

MS-Schema2006-07-15/schU5/schU5.i

instance

fail

same-invalid

xsts-circular-redefine-underspecified

XSD 1.1

MS-SimpleType2006-07-15/stE012/stE012

schema

fail

same-invalid

unclassified

XSD 1.1

MS-SimpleType2006-07-15/stZ033/stZ033.i

instance

fail

same-invalid

xsts-redefine-simple-type-enforcement

XSD 1.1

MS-SimpleType2006-07-15/ste110/ste110

schema

fail

same-valid

unclassified

XSD 1.1

Override/over024/over024.bad.xsd

schema

fail

same-invalid

xsts-override-composition

XSD 1.1

Override/over026/over026.bad.xsd

schema

fail

same-invalid

xsts-override-composition

XSD 1.1

SType/st_name00401m/ST_name00401m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.1

SType/st_targetns00101m/ST_targetNS00101m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.1

SType/st_targetns00101m/ST_targetNS00101m2_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.1

SType/st_targetns00201m/ST_targetNS00201m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.1

Simple/simple012/simple012.v02.xml

instance

fail

same-valid

unclassified

XSD 1.1

Simple/simple093/simple093.xsd

schema

fail

same-invalid

unclassified

XSD 1.1

UnitsLength/d2_4_1_3si01/d2_4_1_3si01s

schema

fail

same-invalid

unclassified

XSD 1.1

XmlVersions/xv001/xv001.v01.xml

instance

fail

same-valid

xsts-xml11-lexer-floor

XSD 1.1

XmlVersions/xv003/xv003.v01.xml

instance

fail

same-valid

xsts-xml11-lexer-floor

XSD 1.1

XmlVersions/xv004/xv004.v01.xml

instance

fail

same-valid

xsts-xml11-lexer-floor

XSD 1.1

XmlVersions/xv006/xv006.v01.xml

instance

fail

same-valid

xsts-xml11-lexer-floor

XSD 1.1

XmlVersions/xv008/xv008.v01.xml

instance

fail

same-valid

xsts-xml11-lexer-floor

XSD 1.1

assertion/d4_3_15ii31/d4_3_15ii31i

instance

fail

same-invalid

unclassified

XSD 1.1

assertion/d4_3_15ii32/d4_3_15ii32i

instance

fail

same-invalid

unclassified

XSD 1.1

defaultAttributesApply/s3_4_2_4ii06/s3_4_2_4ii06i

instance

fail

same-valid

xsts-redefine-default-attributes-apply

XSD 1.0

CType/targetns00101m/targetNS00101m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.0

Complex/complex017/complex017.xsd

schema

fail

same-invalid

unclassified

XSD 1.0

ElemDecl/idconstrdefs00301m/idConstrDefs00301m2_n

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-multiple-id-attributes

XSD 1.0

ElemDecl/valueconstraint01001m2/valueConstraint01001m2

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

ElemDecl/valueconstraint01001m3/valueConstraint01001m3

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

ElemDecl/valueconstraint01001m5/valueConstraint01001m5

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

ElemDecl/valueconstraint01001m6/valueConstraint01001m6

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MGroup/particles00104m1/particles00104m1

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-all-group-relaxations

XSD 1.0

MS-Additional2006-07-15/addB078/addB078

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Additional2006-07-15/addB078A/addB078A

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Additional2006-07-15/addB078B/addB078B

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Additional2006-07-15/addB118/addB118

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Additional2006-07-15/addB121/addB121

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-wildcard-upa-relaxation

XSD 1.0

MS-Additional2006-07-15/addB142/addB142.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/addB153/addB153

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-wildcard-upa-relaxation

XSD 1.0

MS-Additional2006-07-15/addB156/addB156.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-inline-schema-composition

XSD 1.0

MS-Additional2006-07-15/addB158/addB158.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-inline-schema-composition

XSD 1.0

MS-Additional2006-07-15/addB159/addB159.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/addB161/addB161.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/addB162/addB162.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/addB164/addB164.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/addB166/addB166.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/addB181/addB181.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/addB187/addB187.v

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.0

MS-Additional2006-07-15/addB191/addB191.v

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Additional2006-07-15/isDefault060_2/isDefault060_2

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Additional2006-07-15/isDefault069/isDefault069

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Attribute2006-07-15/attP031/attP031.i

instance

fail

not-comparable

unclassified

XSD 1.0

MS-Attribute2006-07-15/attZ013a/attZ013a

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Attribute2006-07-15/attZ013b/attZ013b

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Attribute2006-07-15/attZ014a/attZ014a.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-multiple-id-attributes

XSD 1.0

MS-Attribute2006-07-15/attZ014b/attZ014b.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-multiple-id-attributes

XSD 1.0

MS-AttributeGroup2006-07-15/attgB013/attgB013

schema

fail

same-invalid

xsts-duplicate-global-attribute-group

XSD 1.0

MS-AttributeGroup2006-07-15/attgC010/attgC010

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-attribute-group-circularity

XSD 1.0

MS-AttributeGroup2006-07-15/attgC020/attgC020

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-attribute-group-circularity

XSD 1.0

MS-AttributeGroup2006-07-15/attgC028/attgC028

schema

fail

same-invalid

xsts-redefine-attribute-group-restriction

XSD 1.0

MS-AttributeGroup2006-07-15/attgC031/attgC031

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-attribute-group-circularity

XSD 1.0

MS-AttributeGroup2006-07-15/attgD015/attgD015

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-attribute-group-circularity

XSD 1.0

MS-AttributeGroup2006-07-15/attgD017/attgD017

schema

fail

same-invalid

xsts-redefine-attribute-group-merge

XSD 1.0

MS-ComplexType2006-07-15/ctM004/ctM004

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-multiple-id-attributes

XSD 1.0

MS-DataTypes2006-07-15/anyURI_a001_1336/anyURI_a001_1336

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-anyuri-value-space

XSD 1.0

MS-DataTypes2006-07-15/anyURI_a003_1338/anyURI_a003_1338

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-anyuri-value-space

XSD 1.0

MS-DataTypes2006-07-15/anyURI_a004_1339/anyURI_a004_1339.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-DataTypes2006-07-15/anyURI_b004_1354/anyURI_b004_1354

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-anyuri-value-space

XSD 1.0

MS-DataTypes2006-07-15/anyURI_b006_1356/anyURI_b006_1356

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-anyuri-value-space

XSD 1.0

MS-DataTypes2006-07-15/dateTime011_2008/dateTime011_2008.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-year-zero

XSD 1.0

MS-DataTypes2006-07-15/double018_1956/double018_1956.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-float-double-positive-inf

XSD 1.0

MS-DataTypes2006-07-15/dtZ107447_a_2245/dtZ107447_a_2245

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-DataTypes2006-07-15/float018_1917/float018_1917.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-float-double-positive-inf

XSD 1.0

MS-DataTypes2006-07-15/gMonth002_2061/gMonth002_2061.v

instance

fail

same-valid

unclassified

XSD 1.0

MS-DataTypes2006-07-15/gMonth004_2063/gMonth004_2063.v

instance

fail

same-valid

unclassified

XSD 1.0

MS-Element2006-07-15/elemM002/elemM002

schema

fail

same-invalid

unclassified

XSD 1.0

MS-Element2006-07-15/elemZ016/elemZ016.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-multiple-id-attributes

XSD 1.0

MS-Element2006-07-15/elemZ026/elemZ026

schema

fail

same-invalid

unclassified

XSD 1.0

MS-Element2006-07-15/elemZ032a/elemZ032a

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Element2006-07-15/elemZ032b/elemZ032b

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-Group2006-07-15/groupH021v/groupH021v

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-IdentityConstraint2006-07-15/idB005/idB005

schema

fail

same-invalid

unclassified

XSD 1.0

MS-IdentityConstraint2006-07-15/idC019/idC019

schema

fail

same-invalid

xsts-identity-constraint-global-reference

XSD 1.0

MS-IdentityConstraint2006-07-15/idZ011/idZ011

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-id-value-constraints

XSD 1.0

MS-ModelGroups2006-07-15/mgA016/mgA016

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-all-group-relaxations

XSD 1.0

MS-ModelGroups2006-07-15/mgO001/mgO001

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-all-group-relaxations

XSD 1.0

MS-ModelGroups2006-07-15/mgO018/mgO018

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-all-group-relaxations

XSD 1.0

MS-Particles2006-07-15/particlesFb003/particlesFb003

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-wildcard-upa-relaxation

XSD 1.0

MS-Particles2006-07-15/particlesHa161/particlesHa161

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesHb008/particlesHb008

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesHb011/particlesHb011

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesS002/particlesS002

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesT002/particlesT002

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesT009/particlesT009

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesZ001/particlesZ001.i

instance

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesZ023/particlesZ023

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesZ024/particlesZ024

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesZ028/particlesZ028

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Particles2006-07-15/particlesZ031/particlesZ031

schema

fail

valid-in-1.0-invalid-in-1.1

xsd10-complex-content-from-simple-content

XSD 1.0

MS-Regex2006-07-15/reJ11/reJ11.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ13/reJ13.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ19/reJ19.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ21/reJ21.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ23/reJ23.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ25/reJ25.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ29/reJ29.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ31/reJ31.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ33/reJ33.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ35/reJ35.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ61/reJ61.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ69/reJ69.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ75/reJ75.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reJ77/reJ77.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reL98/reL98.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reL99/reL99.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reM98/reM98.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reN99/reN99.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reS21/reS21.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reS42/reS42.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reT63/reT63.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Regex2006-07-15/reT84/reT84.i

instance

fail

same-invalid

unclassified

XSD 1.0

MS-Schema2006-07-15/schF2/schF2.v

instance

fail

same-valid

xsts-no-namespace-type-reference

XSD 1.0

MS-Schema2006-07-15/schF6/schF6

schema

fail

same-invalid

xsts-import-namespace-mismatch

XSD 1.0

MS-Schema2006-07-15/schG11/schG11

schema

fail

same-invalid

xsts-duplicate-global-element

XSD 1.0

MS-Schema2006-07-15/schG2/schG2.v

instance

fail

same-valid

xsts-no-namespace-type-reference

XSD 1.0

MS-Schema2006-07-15/schG6/schG6

schema

fail

same-invalid

xsts-duplicate-global-element

XSD 1.0

MS-Schema2006-07-15/schL3/schL3

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-all-group-relaxations

XSD 1.0

MS-Schema2006-07-15/schL5/schL5

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-intensional-restriction

XSD 1.0

MS-Schema2006-07-15/schU4/schU4.i

instance

fail

same-invalid

xsts-circular-redefine-underspecified

XSD 1.0

MS-Schema2006-07-15/schU5/schU5.i

instance

fail

same-invalid

xsts-circular-redefine-underspecified

XSD 1.0

MS-SimpleType2006-07-15/stE053/stE053

schema

fail

valid-in-1.0-invalid-in-1.1

xsd10-valid-type-constructs

XSD 1.0

MS-SimpleType2006-07-15/stZ007/stZ007

schema

fail

valid-in-1.0-invalid-in-1.1

xsd10-valid-type-constructs

XSD 1.0

MS-SimpleType2006-07-15/stZ033/stZ033.i

instance

fail

same-invalid

xsts-redefine-simple-type-enforcement

XSD 1.0

MS-SimpleType2006-07-15/stZ047/stZ047

schema

fail

valid-in-1.0-invalid-in-1.1

xsd10-valid-type-constructs

XSD 1.0

MS-SimpleType2006-07-15/stZ055/stZ055

schema

fail

valid-in-1.0-invalid-in-1.1

xsd10-valid-type-constructs

XSD 1.0

MS-SimpleType2006-07-15/ste110/ste110

schema

fail

same-valid

unclassified

XSD 1.0

MS-Wildcards2006-07-15/wildZ013/wildZ013

schema

fail

invalid-in-1.0-valid-in-1.1

xsd10-attribute-wildcard-errata

XSD 1.0

Missing/missing002/missing001.xsd

schema

fail

same-valid

unclassified

XSD 1.0

Missing/missing003/missing003.xsd

schema

fail

same-valid

unclassified

XSD 1.0

Missing/missing006/missing006.xsd

schema

fail

same-valid

unclassified

XSD 1.0

SType/st_name00401m/ST_name00401m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.0

SType/st_targetns00101m/ST_targetNS00101m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.0

SType/st_targetns00101m/ST_targetNS00101m2_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.0

SType/st_targetns00201m/ST_targetNS00201m1_p

instance

fail

same-valid

xsts-type-only-root-xsi-type

XSD 1.0

VC/vc024-11/vc024-11.xsd

schema

fail

same-valid

xsd10-conditional-inclusion

XSD 1.0

VC/vc902/vc902.xsd

schema

fail

same-valid

unclassified

XSD 1.0

XmlVersions/xv001/xv001.v01.xml

instance

fail

same-valid

unclassified

XSD 1.0

XmlVersions/xv003/xv003.v01.xml

instance

fail

same-valid

unclassified

XSD 1.0

XmlVersions/xv004/xv004.v01.xml

instance

fail

same-valid

unclassified

XSD 1.0

XmlVersions/xv006/xv006.v01.xml

instance

fail

same-valid

unclassified

XSD 1.0

XmlVersions/xv008/xv008.v01.xml

instance

fail

same-valid

unclassified

XSD 1.0

anyAttribute/s3_10_6ii01/s3_10_6v01s

schema

fail

same-valid

xsd10-unversioned-11-wildcard-vocabulary

XSD 1.0

anyAttribute/s3_10_6ii02/s3_10_6v02s

schema

fail

same-valid

xsd10-unversioned-11-wildcard-vocabulary

XSD 1.0

anyAttribute/s3_10_6ii04/s3_10_6v04s

schema

fail

same-valid

xsd10-unversioned-11-wildcard-vocabulary

XSD 1.0

wildcard/s3_10_1ii08/s3_10_1ii08s

schema

fail

same-valid

xsd10-unversioned-11-wildcard-vocabulary

XSD 1.0

wildcard/s3_10_1ii09/s3_10_1ii09s

schema

fail

same-valid

xsd10-unversioned-11-wildcard-vocabulary