skip to content »

Xmlreader non validating

Rather than relying on the parser to handle late binding to your own handlers, do it yourself.

xmlreader non validating-1xmlreader non validating-30

All XML processors must accept all valid documents.These are called "Positive Tests" because they ensure that the processor just "does the right thing" without reporting any problems.In the interest of brevity, the only tests listed here are those which produce diagnostics of some kind, such as test failures.This may be done in the case of parsers with severe bugs which completely prevented handling the test case, typically because the parser seems to "hang" by entering an infinite loop.In all cases, negative tests that appear to pass (diagnostics presented with a white background) must be individually examined in the report below.This SAX2 parser optionally layers a validator over the Ælfred2 SAX2 parser.

While this will not evaluate every XML validity constraint, it does support all the validity constraints that are of any real utility outside the strict SGML-compatible world.

Nonvalidating processors may skip some tests if the tests require processing a class of external entities (general, parameter, or both) which that processor is known not to handle.

If processor handling of entities is not known, all such tests are skipped, in order to prevent misreporting.

Some low-fidelity processor APIs don't expose recoverable errors, which can make validation work awkward.

The diagnostic was reported as a recoverable error.

The diagnostic provided by the processor must correspond to the description of the test provided; if the processor does not report the matching error, the seeming "pass" is in fact an error of a type the test harness could not detect or report.