XML Processor Conformance Report:
com.ibm.xml.parsers.SAXParser

This document is the output of an XML test harness. It reports on the conformance of the following XML 1.0 processor configuration, as reported through the Java version of the SAX (Simple API for XML) parser interface. For SAX 2.0 (alpha) processors, the processing mode and entity handling values could be non-default values, if such a feature is supported by that processor. For SAX 1.0 processors, those values were as reported to the test harness by its operator.

XML Processor IBM XML4J v2.0.15
SAX Parser Class com.ibm.xml.parsers.SAXParser
Processing Mode Non-Validating
General Entities included
Parameter Entities included

The test harness and execution environment was:

Test Run Date Tue Sep 07 07:57:08 PDT 1999
Harness and Version org.brownell.xml.conformance.Driver
(alpha; 3-September-1999)
Java VM Info build JDK-1.2.1-A, native threads, symcjit
Suite of Testcases OASIS Conformance Tests, v1.0

An summary of test results follows. To know the actual test status, someone must examine the result of each passed negative test to make sure it failed for the right reason. That examination may cause the counts of failed tests to increase, changing a provisional "conforms" status to a "does not conform".

Status DOES NOT CONFORM
Total Passed Tests (provisional) 902
Passed Negative Tests (provisional) 498
Failed Tests (provisional) 163
Tests Skipped 0

Sections of this report are: Explanation of Tables; Positive Tests, cases where this processor should report no errors; Negative Tests, documents for which this processor must report the known errors; and Informative Tests, documents with errors which processors are not required to report.

NOTE: The OASIS/NIST test suite is currently in draft state, and can't actually be used without modifications to the configuration file, which is used both to generate the test documentation published at the OASIS/NIST site and to operate this test harness. Accordingly, treat these results as preliminary.


Explanation of Tables

Sections presenting test results are composed largely of tables, with explanations focussing on exactly what those tables indicate. Diagnostics for failed tests are presented in italics, with a cherry colored background, to highlight the result. Diagnostics for succesful tests should as a rule only exist for negative tests. Diagnostics with parenthesized comments indicate the reporting path:

(fatal)
The diagnostic was reported as a fatal error. Such errors are primarily well-formedness errors, such as the violation of XML 1.0 syntax rules or of well formedness constraints.
(error)
The diagnostic was reported as a recoverable error. Such errors primarily used to report validation errors, which are all violations of validity constraints, but some other errors are also classed as nonfatal.
(warning)
The diagnostic was reported as a warning; warnings are purely informative and may be emitted in a number of cases identified by the XML 1.0 specification (as well as in other cases).
(thrown classname) ... abnormal
The named exception was directly thrown. If the exception is a SAXException (or a subclass thereof) this suggests an error in the parser (violating the SAX API specification) since it should normally have used the SAX ErrorHandler instead.
(odd classname) ... abnormal
After the identified exception was reported through the ErrorHandler, an exception of the named class was thrown directly. This suggests an error in the parser, since the parser either failed to continue after an error (or warning) which is required to be continuable, or else it did not pass the exception thrown by the application back to the application.
(EXCEPTION - DIRECTED FAILURE) ... abnormal
This test case was explicitly failed by the test operator; the test was not run. 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. 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. That error is either a conformance bug, or an error in the diagnostic being produced, or sometimes both.

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.

Note also that some SAX processors (or drivers for non-SAX processors) appear to have a bug wherein they don't close all of the files which they open. When running this test harness with large numbers of tests, failures at the end of this report could reflect such bugs in SAX conformance more than bugs in XML processor conformance.


Positive Tests

All conformant XML 1.0 processors must accept "valid" input documents without reporting any errors, and moreover must report the correct output data to the application when processing those documents. Nonvalidating processors (such as this one) must also accept "invalid" input documents without reporting any errors. 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. In some cases, warnings may be reported when processing these documents, but these do not indicate failures.

No interpretation of these results is necessary; every "error" or "fatal" message presented here is an XML conformance failure. Maintainers of an XML processor will generally want to fix their software so that it conforms fully to the XML specification.

Valid Documents

All XML processors must accept all valid documents. This group of tests must accordingly produce no test failures.

Section and [Rules] Test ID Description Diagnostic
4.3.3 [4,84] pr-xml-little Test support for little-endian UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.) FAIL (fatal) Document must start with "<?xml".
4.3.3 [4,84] pr-xml-utf-16 Test support UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.) FAIL (fatal) Document must start with "<?xml".
4.3.3 [4,84] weekly-little Test support for little-endian UTF-16 encoding, and XML names which contain Japanese characters. FAIL (fatal) "</null>" expected.
4.3.3 [4,84] weekly-utf-16 Test support for UTF-16 encoding, and XML names which contain Japanese characters. FAIL (fatal) "</null>" expected.
4.3.3 [80] valid-sa-031 Test demonstrates a valid EncodingDecl within the prolog. FAIL (fatal) "</null>" expected.
4.3.3 [81] valid-sa-099 Test demonstrates the name of the encoding can be composed of lowercase characters. FAIL (fatal) "</null>" expected.
4.4.2 valid-sa-053 Tests inclusion of a well-formed internal entity, which holds an element required by the content model. FAIL (fatal) "</null>" expected.
4.4.8 valid-not-sa-019 Test demonstrates that a parameter entity will be expanded with spaces on either side. FAIL (fatal) "</null>" expected.
4.4.8 valid-not-sa-020 Parameter entities expand with spaces on either side. FAIL (fatal) "</null>" expected.
4.4.8 valid-sa-070 Verifies that internal parameter entities are correctly expanded within the internal subset. FAIL (fatal) "</null>" expected.
4.5 v-pe00 Tests construction of internal entity replacement text, using an example in the XML specification. FAIL (fatal) "</null>" expected.
4.5 v-pe01 Tests construction of internal entity replacement text, using an example in the XML specification. FAIL (fatal) "</null>" expected.
4.5 v-pe02 Tests construction of internal entity replacement text, using a complex example in the XML specification. FAIL (fatal) "</null>" expected.
4.5 valid-sa-065 Tests ability to define an internal entity which can't legally be expanded (contains an unquoted <). FAIL (fatal) "</null>" expected.
4.5 valid-sa-087 Tests whether character references in internal entities are expanded early enough, by relying on correct handling to make the entity be well formed. FAIL (fatal) "</null>" expected.
4.5 valid-sa-088 Tests whether entity references in internal entities are expanded late enough, by relying on correct handling to make the expanded text be valid. (If it's expanded too early, the entity will parse as an element that's not valid in that context.) FAIL (fatal) "</null>" expected.
4.5 valid-sa-101 This tests whether entity expansion is (incorrectly) done while processing entity declarations; if it is, the entity value literal will terminate prematurely. FAIL (fatal) "</null>" expected.
4.5 valid-sa-117 Test demonstrates that entity expansion is done while processing entity declarations. FAIL (fatal) "</null>" expected.
4.5 valid-sa-118 Test demonstrates that entity expansion is done while processing entity declarations. FAIL (fatal) "</null>" expected.
4.7 valid-sa-069 Verifies that an XML parser will parse a NOTATION declaration; the output phase of this test ensures that it's reported to the application. FAIL (fatal) "</null>" expected.
4.7 [82] notation01 NOTATION declarations don't need SYSTEM IDs; and externally declared notations may be used to declare unparsed entities in the internal DTD subset. The notation must be reported to the application. FAIL (fatal) "</null>" expected.

Output Tests

The XML specification places requirements on the data which is reported by XML processors to applications. This data flows through the SAX API (with one minor omission: reporting external entities which are not included). These output tests verify conformance with the specification by recording that data and comparing it with what is required for conformance with the XML 1.0 specification.

Note that output tests automatically fail in cases where the processor failed to parse the (valid) input document used to generate the output data.

Test ID Diagnostic
valid-sa-016 Output byte 10 has the wrong value; actual 0x6e should instead be 0x3f
pr-xml-little (Input failed, no output available)
pr-xml-utf-16 (Input failed, no output available)
weekly-little (Input failed, no output available)
weekly-utf-16 (Input failed, no output available)
valid-sa-031 (Input failed, no output available)
valid-sa-099 (Input failed, no output available)
valid-sa-053 (Input failed, no output available)
valid-not-sa-019 (Input failed, no output available)
valid-not-sa-020 (Input failed, no output available)
valid-sa-070 (Input failed, no output available)
v-pe00 (Input failed, no output available)
v-pe01 (Input failed, no output available)
v-pe02 (Input failed, no output available)
valid-sa-065 (Input failed, no output available)
valid-sa-087 (Input failed, no output available)
valid-sa-088 (Input failed, no output available)
valid-sa-101 (Input failed, no output available)
valid-sa-117 (Input failed, no output available)
valid-sa-118 (Input failed, no output available)
valid-sa-069 (Input failed, no output available)
notation01 (Input failed, no output available)

Invalid Documents

As noted above, nonvalidating processors must accept all documents which are well formed, but invalid. This same behavior would be delivered by a validating processor, if the application chose to continue processing after receiving each report of a validity error, and not report such validity errors. (These tests are run as "negative" tests for validating processors, since in those cases it is important that the correct validity errors be reported and that they be fully continuable.)

Section and [Rules] Test ID Description Diagnostic
2.1 [1] o-p01pass1 no prolog FAIL (fatal) "</null>" expected.
2.1 [1] o-p01pass3 Misc items after the document FAIL (fatal) "</null>" expected.
2.3 [10] o-p10pass1 valid attribute values FAIL (fatal) "</null>" expected.
2.3 [3] o-p03pass1 all valid S characters FAIL (fatal) "</null>" expected.
2.3 [4] o-p04pass1 names with all valid ASCII characters, and one from each other class in NameChar FAIL (fatal) "</null>" expected.
2.3 [5] o-p05pass1 various valid Name constructions FAIL (fatal) "</null>" expected.
2.3 [6] o-p06fail1 Requires at least one name. FAIL (fatal) Attribute, "refs", value expected.
2.3 [8] o-p08fail1 at least one Nmtoken is required. FAIL (fatal) Attribute, "att", value expected.
2.3 [8] o-p08fail2 an invalid Nmtoken character. FAIL (fatal) Invalid XML character. (Unicode: 0x2f)
2.4 [14] o-p14pass1 valid CharData FAIL (fatal) "</doc>" expected.
2.5 [15] o-p15pass1 valid comments FAIL (fatal) "</doc>" expected.
2.6 [16] o-p16fail3 S after PITarget is required FAIL (fatal) "</pitarget...>" expected.
2.6 [16] o-p16pass2 Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction. FAIL (fatal) "</pitarget>" expected.
2.6 [16] o-p16pass3 Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction. FAIL (fatal) "</pitarget>" expected.
2.6 [16] [17] o-p16pass1 Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction. FAIL (fatal) "</pitarget>" expected.
2.7 [18] o-p18pass1 valid CDSect's. Note that a CDStart in a CDSect is not recognized as such FAIL (fatal) "</doc>" expected.
2.8 invalid--001 Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting a comment between two parameter entities. FAIL (fatal) Parameter entity replacement text must include declarations or proper pairs of '<' and '>'. (entity: "%e;")
2.8 invalid--003 Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an entity declaration between two parameter entities. FAIL (fatal) Recursive reference "%e;". (Reference path: (top-level)-%e;-%e;)
2.8 invalid--004 Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an entity declaration between three parameter entities. FAIL (fatal) Recursive reference "%e1;". (Reference path: (top-level)-%e1;-%e1;)
2.8 invalid--005 Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an entity declaration between two parameter entities. FAIL (fatal) Recursive reference "%e;". (Reference path: (top-level)-%e;-%e;)
2.8 invalid--006 Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an entity declaration between two parameter entities. FAIL (fatal) Recursive reference "%e;". (Reference path: (top-level)-%e;-%e;)
2.8 root Tests the Root Element Type VC FAIL (fatal) "</xml>" expected.
2.8 [22] o-p22pass1 prolog can be empty FAIL (fatal) "</doc>" expected.
2.8 [22] o-p22pass2 XML declaration only FAIL (fatal) "</xml>" expected.
2.8 [22] o-p22pass3 XML decl and Misc FAIL (fatal) "</xml>" expected.
2.8 [23] o-p23pass1 Test shows a valid XML declaration along with version info. FAIL (fatal) "</xml>" expected.
2.8 [23] o-p23pass2 Test shows a valid XML declaration along with encoding declaration. FAIL (fatal) "</xml>" expected.
2.8 [23] o-p23pass3 Test shows a valid XML declaration along with Standalone Document Declaration. FAIL (fatal) "</xml>" expected.
2.8 [23] o-p23pass4 Test shows a valid XML declaration, encoding declarationand Standalone Document Declaration. FAIL (fatal) "</xml>" expected.
2.8 [24] o-p24pass1 Test shows a prolog that has the VersionInfo delimited by double quotes. FAIL (fatal) "</xml>" expected.
2.8 [24] o-p24pass2 Test shows a prolog that has the VersionInfo delimited by single quotes. FAIL (fatal) "</xml>" expected.
2.8 [24] o-p24pass3 Test shows whitespace is allowed in prolog before version info. FAIL (fatal) "</xml>" expected.
2.8 [24] o-p24pass4 Test shows whitespace is allowed in prolog on both sides of equal sign. FAIL (fatal) "</xml>" expected.
2.8 [25] o-p25pass1 Test shows whitespace is NOT necessary before or after equal sign of versioninfo. FAIL (fatal) "</xml>" expected.
2.8 [25] o-p25pass2 Test shows whitespace can be used on both sides of equal sign of versioninfo. FAIL (fatal) "</xml>" expected.
2.8 [26] o-p26pass1 The valid version number. We cannot test others because a 1.0 processor is allowed to fail them. FAIL (fatal) "</xml>" expected.
2.8 [27] o-p27pass1 Comments are valid as the Misc part of the prolog. FAIL (fatal) "</xml>" expected.
2.8 [27] o-p27pass2 Processing Instructions are valid as the Misc part of the prolog. FAIL (fatal) "</xml>" expected.
2.8 [27] o-p27pass3 Whitespace is valid as the Misc part of the prolog. FAIL (fatal) "</xml>" expected.
2.8 [27] o-p27pass4 A combination of comments, whitespaces and processing instructions are valid as the Misc part of the prolog. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa01 Tests the Standalone Document Declaration VC, ensuring that optional whitespace causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa02 Tests the Standalone Document Declaration VC, ensuring that attributes needing normalization cause a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa03 Tests the Standalone Document Declaration VC, ensuring that a reference to externally defined entity causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa04 Tests the Standalone Document Declaration VC, ensuring that attributes needing defaulting cause a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa05 Tests the Standalone Document Declaration VC, ensuring that a token attribute that needs normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa06 Tests the Standalone Document Declaration VC, ensuring that a NOTATION attribute that needs normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa07 Tests the Standalone Document Declaration VC, ensuring that an NMTOKEN attribute needing normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa08 Tests the Standalone Document Declaration VC, ensuring that an NMTOKENS attribute needing normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa09 Tests the Standalone Document Declaration VC, ensuring that an ID attribute needing normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa10 Tests the Standalone Document Declaration VC, ensuring that an IDREF attribute needing normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa11 Tests the Standalone Document Declaration VC, ensuring that an IDREFS attribute needing normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa12 Tests the Standalone Document Declaration VC, ensuring that an ENTITY attribute needing normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa13 Tests the Standalone Document Declaration VC, ensuring that an ENTITIES attribute needing normalization causes a validity error. FAIL (fatal) "</xml>" expected.
2.9 inv-not-sa14 Tests the Standalone Document Declaration VC, ensuring that optional whitespace causes a validity error (even if it's CDATA whitespace). FAIL (fatal) "</xml>" expected.
2.9 [32] o-p32pass1 Double quotes can be used as delimeters for the value of a Standalone Document Declaration. FAIL (fatal) "</xml>" expected.
2.9 [32] o-p32pass2 Single quotes can be used as delimeters for the value of a Standalone Document Declaration. FAIL (fatal) "</xml>" expected.
3 el01 Tests the Element Valid VC (clause 4) by including an undeclared child element. FAIL (fatal) "</root>" expected.
3 el02 Tests the Element Valid VC (clause 1) by including elements in an EMPTY content model. FAIL (fatal) "</root>" expected.
3 el03 Tests the Element Valid VC (clause 3) by including a child element not permitted by a mixed content model. FAIL (fatal) "</root>" expected.
3 el06 Tests the Element Valid VC (clause 1), using one of the predefined internal entities inside an EMPTY content model. FAIL (fatal) "</root>" expected.
3 inv-dtd03 Tests the "Element Valid" VC (clause 2) by omitting a required element. FAIL (fatal) "</violation>" expected.
3 optional01 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one is required. FAIL (fatal) "</root>" expected.
3 optional02 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing two children where one is required. FAIL (fatal) "</root>" expected.
3 optional03 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where two are required. FAIL (fatal) "</root>" expected.
3 optional04 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where two are required. FAIL (fatal) "</root>" expected.
3 optional05 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (one construction of that model). FAIL (fatal) "</root>" expected.
3 optional06 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a second construction of that model). FAIL (fatal) "</root>" expected.
3 optional07 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a third construction of that model). FAIL (fatal) "</root>" expected.
3 optional08 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a fourth construction of that model). FAIL (fatal) "</root>" expected.
3 optional09 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a fifth construction of that model). FAIL (fatal) "</root>" expected.
3 optional10 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a basic construction of that model). FAIL (fatal) "</root>" expected.
3 optional11 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a second construction of that model). FAIL (fatal) "</root>" expected.
3 optional12 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a third construction of that model). FAIL (fatal) "</root>" expected.
3 optional13 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a fourth construction of that model). FAIL (fatal) "</root>" expected.
3 optional14 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a fifth construction of that model). FAIL (fatal) "</root>" expected.
3 optional15 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a basic construction of that model). FAIL (fatal) "</root>" expected.
3 optional16 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a second construction of that model). FAIL (fatal) "</root>" expected.
3 optional17 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a third construction of that model). FAIL (fatal) "</root>" expected.
3 optional18 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a fourth construction of that model). FAIL (fatal) "</root>" expected.
3 optional19 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a fifth construction of that model). FAIL (fatal) "</root>" expected.
3 optional20 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a sixth construction of that model). FAIL (fatal) "</root>" expected.
3 optional21 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a seventh construction of that model). FAIL (fatal) "</root>" expected.
3 optional22 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (an eigth construction of that model). FAIL (fatal) "</root>" expected.
3 optional23 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a ninth construction of that model). FAIL (fatal) "</root>" expected.
3 optional24 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a tenth construction of that model). FAIL (fatal) "</root>" expected.
3 optional25 Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing text content where one or more elements are required. FAIL (fatal) "</root>" expected.
3 3.1 [39] [43] o-p39pass2 Character data is valid element content. FAIL (fatal) "</doc>" expected.
3 3.1 [39] [44] o-p39pass1 Empty element tag may be used for any element which has no content. FAIL (fatal) "</doc>" expected.
3.1 2.10 inv-required01 Tests the Attribute Value Type (declared) VC for the xml:space attribute FAIL (fatal) "</root>" expected.
3.1 2.12 inv-required02 Tests the Attribute Value Type (declared) VC for the xml:lang attribute FAIL (fatal) "</root>" expected.
3.1 [40] o-p40pass1 Elements content can be empty. FAIL (fatal) "</doc>" expected.
3.1 [40] o-p40pass2 Whitespace is valid within a Start-tag. FAIL (fatal) "</doc>" expected.
3.1 [40] o-p40pass4 Whitespace and Multiple Attributes are valid within a Start-tag. FAIL (fatal) "</doc>" expected.
3.1 [40] [41] o-p40pass3 Attributes are valid within a Start-tag. FAIL (fatal) "</doc>" expected.
3.1 [41] o-p41pass1 Attributes are valid within a Start-tag. FAIL (fatal) "</doc>" expected.
3.1 [41] o-p41pass2 Whitespace is valid within a Start-tags Attribute. FAIL (fatal) "</doc>" expected.
3.1 [42] o-p42pass1 Test shows proper syntax for an End-tag. FAIL (fatal) "</doc>" expected.
3.1 [42] o-p42pass2 Whitespace is valid after name in End-tag. FAIL (fatal) "</doc>" expected.
3.1 [44] o-p44pass1 Valid display of an Empty Element Tag. FAIL (fatal) "</doc>" expected.
3.1 [44] o-p44pass2 Empty Element Tags can contain an Attribute. FAIL (fatal) "</doc>" expected.
3.1 [44] o-p44pass3 Whitespace is valid in an Empty Element Tag following the end of the attribute value. FAIL (fatal) "</doc>" expected.
3.1 [44] o-p44pass4 Whitespace is valid after the name in an Empty Element Tag. FAIL (fatal) "</doc>" expected.
3.1 [44] o-p44pass5 Whitespace and Multiple Attributes are valid in an Empty Element Tag. FAIL (fatal) "</doc>" expected.
3.2 el04 Tests the Unique Element Type Declaration VC. FAIL (fatal) "</root>" expected.
3.2.1 invalid--002 Tests the "Proper Group/PE Nesting" validity constraint by fragmenting a content model between two parameter entities. FAIL (fatal) Recursive reference "%e;". (Reference path: (top-level)-%e;-%e;)
3.2.2 el05 Tests the No Duplicate Types VC. FAIL (fatal) "</root>" expected.
3.2.2 inv-dtd01 Tests the No Duplicate Types VC FAIL (fatal) "</root>" expected.
3.3.1 attr01 Tests the "Entity Name" VC for the ENTITY attribute type. FAIL (fatal) "</root>" expected.
3.3.1 attr02 Tests the "Entity Name" VC for the ENTITIES attribute type. FAIL (fatal) "</root>" expected.
3.3.1 attr03 Tests the "Notation Attributes" VC for the NOTATION attribute type, first clause: value must be one of the ones that's declared. FAIL (fatal) "</root>" expected.
3.3.1 attr04 Tests the "Notation Attributes" VC for the NOTATION attribute type, second clause: the names in the declaration must all be declared. FAIL (fatal) "</root>" expected.
3.3.1 attr05 Tests the "Name Token" VC for the NMTOKEN attribute type. FAIL (fatal) Invalid XML character. (Unicode: 0x40)
3.3.1 attr06 Tests the "Name Token" VC for the NMTOKENS attribute type. FAIL (fatal) Invalid XML character. (Unicode: 0x69)
3.3.1 attr07 Tests the "Enumeration" VC by providing a value which wasn't one of the choices. FAIL (fatal) "</arbor>" expected.
3.3.1 id01 Tests the ID (is a Name) VC FAIL (fatal) Invalid XML character. (Unicode: 0x34)
3.3.1 id02 Tests the ID (appears once) VC FAIL (fatal) "</root>" expected.
3.3.1 id03 Tests the One ID per Element Type VC FAIL (fatal) "</root>" expected.
3.3.1 id04 Tests the ID Attribute Default VC FAIL (fatal) "</root>" expected.
3.3.1 id05 Tests the ID Attribute Default VC FAIL (fatal) "</root>" expected.
3.3.1 id06 Tests the IDREF (is a Name) VC FAIL (fatal) Invalid XML character. (Unicode: 0x33)
3.3.1 id07 Tests the IDREFS (is a Names) VC FAIL (fatal) Invalid XML character. (Unicode: 0x33)
3.3.1 id08 Tests the IDREF (matches an ID) VC FAIL (fatal) "</root>" expected.
3.3.1 id09 Tests the IDREF (IDREFS matches an ID) VC FAIL (fatal) "</root>" expected.
3.3.2 attr08 Tests the "Fixed Attribute Default" VC by providing the wrong value. FAIL (fatal) "</palimpest>" expected.
3.3.2 attr09 Tests the "Attribute Default Legal" VC by providing an illegal IDREF value. FAIL (fatal) Invalid XML character. (Unicode: 0x34)
3.3.2 attr10 Tests the "Attribute Default Legal" VC by providing an illegal IDREFS value. FAIL (fatal) Invalid XML character. (Unicode: 0x34)
3.3.2 attr11 Tests the "Attribute Default Legal" VC by providing an illegal ENTITY value. FAIL (fatal) "</reference>" expected.
3.3.2 attr12 Tests the "Attribute Default Legal" VC by providing an illegal ENTITIES value. FAIL (fatal) "</references>" expected.
3.3.2 attr13 Tests the "Attribute Default Legal" VC by providing an illegal NMTOKEN value. FAIL (fatal) Invalid XML character. (Unicode: 0x2f)
3.3.2 attr14 Tests the "Attribute Default Legal" VC by providing an illegal NMTOKENS value. FAIL (fatal) Invalid XML character. (Unicode: 0x24)
3.3.2 attr15 Tests the "Attribute Default Legal" VC by providing an illegal NOTATIONS value. FAIL (fatal) "</reference>" expected.
3.3.2 attr16 Tests the "Attribute Default Legal" VC by providing an illegal enumeration value. FAIL (fatal) "</root>" expected.
3.3.2 inv-required00 Tests the Required Attribute VC. FAIL (fatal) "</root>" expected.
4.1 inv-dtd06 Tests "Entity Declared" VC for a parameter entity. NOTE: there are both VCs and WFCs with this name, which is a specification issue in that it is both confusing and in some ways self-contradictory. The WFC does not apply to PEs, and even the clause which might seem to suggest it could is ruled out in this test. FAIL (fatal) "</root>" expected.
4.1 not-wf-not-sa-005 Tests the Entity Declared VC by referring to an undefined parameter entity within an external entity. FAIL (fatal) "</doc>" expected.
4.1 [66] o-p66pass1 valid character references FAIL (fatal) "</doc>" expected.
4.2 [74] o-p74pass1 PEDef is either an entity value or an external id FAIL (fatal) Recursive reference "%pe2;". (Reference path: (top-level)-%pe2;-%pe2;)
4.2.2 inv-dtd02 Tests the "Notation Declared" VC by using an undeclared notation name. FAIL (fatal) "</paper>" expected.
4.2.2 [75] o-p75pass1 valid external identifiers FAIL (fatal) "</doc>" expected.
4.3.3 2.8 utf16b Tests reading an invalid "big endian" UTF-16 document FAIL (fatal) "</xml>" expected.
4.3.3 2.8 utf16l Tests reading an invalid "little endian" UTF-16 document FAIL (fatal) "</xml>" expected.

Negative Tests

All conformant XML 1.0 processors must reject documents which are not well-formed. In addition, validating processors must report the validity errors for invalid documents. These are called Negative Tests because the test is intended to establish that errors are reported when they should be.

Moreover, the processor must both fail for the appropriate reason (given by the parser diagnostic) and must report an error at the right level ("error" or "fatal"). If both criteria were not considered, a processor which failed frequently (such as by failing to parse any document at all) would appear to pass a large number of conformance tests Unfortunately, the test driver can only tell whether the error was reported at the right level. It can't determine whether the processor failed for the right reason.

That's where a person to interpret these test results is critical. Such a person analyses the diagnostics, reported here, for negative tests not already known to be failures (for not reporting an error, or reporting one at the wrong level). If the diagnostic reported for such tests doesn't match the failure from the test description, there is an error in the diagnostic or in the processor's XML conformance (or sometimes in both).

For this processor, 498 diagnostics must be examined to get an accurate evaluation of its negative test status.

Documents which are not Well-Formed

All XML processors must correctly reject (with a "fatal" error) all XML documents which are not well-formed. (Nonvalidating processors may skip some of these tests, if they require handling of a type of external entity which the processor ignores. Such skipped tests are not reported.)

Section and [Rules] Test ID Description Diagnostic
2.1 [1] not-wf-sa-050 Empty document, with no root element. (thrown SAXException) [no exception message]
2.1 [1] o-p01fail1 S cannot occur before the prolog (fatal) Document must start with "<?xml".
2.1 [1] o-p01fail2 comments cannot occur before the prolog (fatal) Document must start with "<?xml".
2.1 [1] o-p01fail3 only one document element (fatal) "</doc>" expected.
2.1 [1] o-p01fail4 document element must be complete. (fatal) "</doc>" expected.
2.2 [2] not-wf-sa-030 A form feed is not a legal XML character. (fatal) Invalid XML character. (Unicode: 0xc)
2.2 [2] not-wf-sa-031 A form feed is not a legal XML character. (fatal) Invalid XML character. (Unicode: 0xc)
2.2 [2] not-wf-sa-032 A form feed is not a legal XML character. (fatal) Invalid XML character. (Unicode: 0xc)
2.2 [2] not-wf-sa-033 An ESC (octal 033) is not a legal XML character. (fatal) Invalid XML character. (Unicode: 0x1b)
2.2 [2] not-wf-sa-034 A form feed is not a legal XML character. (fatal) "/>" or '>' expected.
2.2 [2] not-wf-sa-142 Character #x0000 is not legal anywhere in an XML document. (fatal) Character reference, "&#0;", is out of range.
2.2 [2] not-wf-sa-143 Character #x001F is not legal anywhere in an XML document. (fatal) Character reference, "&#31;", is out of range.
2.2 [2] not-wf-sa-144 Character #xFFFF is not legal anywhere in an XML document. (fatal) Character reference, "&#xFFFF", is out of range.
2.2 [2] not-wf-sa-145 Character #xD800 is not legal anywhere in an XML document. (If it appeared in a UTF-16 surrogate pair, it'd represent half of a UCS-4 character and so wouldn't really be in the document.) (fatal) Character reference, "&#xD800", is out of range.
2.2 [2] not-wf-sa-146 Character references must also refer to legal XML characters; #x00110000 is one more than the largest legal character. (fatal) Character reference, "&#x110000", is out of range.
2.2 [2] not-wf-sa-166 Character FFFF is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] not-wf-sa-167 Character FFFE is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xfffe)
2.2 [2] not-wf-sa-168 An unpaired surrogate (D800) is not legal anywhere in an XML document. (fatal) "</doc>" expected.
2.2 [2] not-wf-sa-169 An unpaired surrogate (DC00) is not legal anywhere in an XML document. (fatal) "</doc>" expected.
2.2 [2] not-wf-sa-170 Four byte UTF-8 encodings can encode UCS-4 characters which are beyond the range of legal XML characters (and can't be expressed in Unicode surrogate pairs). This document holds such a character. (fatal) "</doc>" expected.
2.2 [2] not-wf-sa-171 Character FFFF is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] not-wf-sa-172 Character FFFF is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] not-wf-sa-173 Character FFFF is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] not-wf-sa-174 Character FFFF is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] not-wf-sa-175 Character FFFF is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] not-wf-sa-177 Character FFFF is not legal anywhere in an XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] o-p02fail1 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x0)
2.2 [2] o-p02fail10 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0xb)
2.2 [2] o-p02fail11 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0xc)
2.2 [2] o-p02fail12 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0xe)
2.2 [2] o-p02fail13 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0xf)
2.2 [2] o-p02fail14 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x10)
2.2 [2] o-p02fail15 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x11)
2.2 [2] o-p02fail16 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x12)
2.2 [2] o-p02fail17 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x13)
2.2 [2] o-p02fail18 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x14)
2.2 [2] o-p02fail19 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x15)
2.2 [2] o-p02fail2 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x1)
2.2 [2] o-p02fail20 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x16)
2.2 [2] o-p02fail21 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x17)
2.2 [2] o-p02fail22 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x18)
2.2 [2] o-p02fail23 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x19)
2.2 [2] o-p02fail24 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x1a)
2.2 [2] o-p02fail25 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x1b)
2.2 [2] o-p02fail26 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x1c)
2.2 [2] o-p02fail27 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x1d)
2.2 [2] o-p02fail28 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x1e)
2.2 [2] o-p02fail29 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x1f)
2.2 [2] o-p02fail3 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x2)
2.2 [2] o-p02fail30 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0xfffe)
2.2 [2] o-p02fail31 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0xffff)
2.2 [2] o-p02fail4 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x3)
2.2 [2] o-p02fail5 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x4)
2.2 [2] o-p02fail6 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x5)
2.2 [2] o-p02fail7 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x6)
2.2 [2] o-p02fail8 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x7)
2.2 [2] o-p02fail9 Use of illegal character within XML document. (fatal) Invalid XML character. (Unicode: 0x8)
2.3 [10] not-wf-sa-012 SGML-ism: attribute values must be quoted in all cases. (fatal) ' or " expected. Attribute value must be quoted.
2.3 [10] not-wf-sa-013 The quotes on both ends of an attribute value must match. (fatal) Attribute value must not contain '<'.
2.3 [10] not-wf-sa-014 Attribute values may not contain literal '<' characters. (fatal) Attribute value must not contain '<'.
2.3 [10] not-wf-sa-020 Attribute values may not contain literal '&' characters except as part of an entity reference. (fatal) Invalid character, ' ', in reference.
2.3 [10] not-wf-sa-021 Attribute values may not contain literal '&' characters except as part of an entity reference. (fatal) Reference must end with ';'.
2.3 [10] not-wf-sa-088 Attribute values are terminated by literal quote characters, and any entity expansion is done afterwards. (fatal) Attribute value must not contain '<'.
2.3 [10] not-wf-sa-090 Attributes may not contain a literal "<" character; this one has one because of reference expansion. (fatal) Attribute value must not contain '<'.
2.3 [10] o-p10fail1 attribute values exclude '<' (fatal) Attribute value must not contain '<'.
2.3 [10] o-p10fail2 attribute values exclude '&' (fatal) Invalid character, '"', in reference.
2.3 [10] o-p10fail3 quote types must match (fatal) "</doc>" expected.
2.3 [11] o-p11fail1 quote types must match (fatal) "</doc>" expected.
2.3 [11] o-p11fail2 cannot contain delimiting quotes (fatal) '>' expected.
2.3 [12] o-p12fail1 '"' excluded (fatal) Invalid character, '"', in public identifier.
2.3 [12] o-p12fail2 '\' excluded (fatal) Invalid character, '\', in public identifier.
2.3 [12] o-p12fail3 entity references excluded (fatal) Recursive reference, "&x;". (reference path: (top-level)-%null;-%x;-&x;-&x;)
2.3 [12] o-p12fail4 '>' excluded (fatal) Invalid character, '>', in public identifier.
2.3 [12] o-p12fail5 '<' excluded (fatal) Invalid character, '<', in public identifier.
2.3 [12] o-p12fail6 built-in entity refs excluded (fatal) Invalid character, '&', in public identifier.
2.3 [12] o-p12fail7 (fatal) "</doc>" expected.
2.3 [12] pubid01 Illegal entity ref in public ID (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [12] pubid02 Illegal characters in public ID (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [12] pubid03 Illegal characters in public ID (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [12] pubid04 Illegal characters in public ID (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [12] pubid05 SGML-ism: public ID without system ID (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [13] not-wf-sa-085 Public IDs may not contain "[". (fatal) Invalid character, '[', in public identifier.
2.3 [13] not-wf-sa-086 Public IDs may not contain "[". (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-&foo;)
2.3 [13] not-wf-sa-087 Public IDs may not contain "[". (fatal) Invalid character, '[', in public identifier.
2.3 [3] o-p03fail1 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail10 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail11 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail12 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail13 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail14 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail15 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail16 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail17 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail18 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail19 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail2 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail20 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail21 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail22 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail23 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail24 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail25 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail26 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail27 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail28 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail29 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail3 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail4 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail5 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail7 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail8 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [3] o-p03fail9 Use of illegal character within XML document. (fatal) Invalid document structure.
2.3 [4] not-wf-sa-002 Names may not start with "."; it's not a Letter. (fatal) Element name expected.
2.3 [4] not-wf-sa-140 Character '&#x309a;' is a CombiningChar, not a Letter, and so may not begin a name. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [4] o-p04fail1 Name contains invalid character. (fatal) "/>" or '>' expected.
2.3 [4] o-p04fail2 Name contains invalid character. (fatal) "/>" or '>' expected.
2.3 [4] o-p04fail3 Name contains invalid character. (fatal) "/>" or '>' expected.
2.3 [5] not-wf-sa-008 Entity references must include names, which don't begin with '.' (it's not a Letter or other name start character). (fatal) Invalid character, '.', in reference.
2.3 [5] not-wf-sa-023 Digits are not valid name start characters. (fatal) "/>" or '>' expected.
2.3 [5] not-wf-sa-024 Digits are not valid name start characters. (fatal) Element name expected.
2.3 [5] not-wf-sa-141 Character #x0E5C is not legal in XML names. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [5] o-p05fail1 a Name cannot start with a digit (fatal) Element name expected.
2.3 [5] o-p05fail2 a Name cannot start with a '.' (fatal) Element name expected.
2.3 [5] o-p05fail3 a Name cannot start with a "-" (fatal) Element name expected.
2.3 [5] o-p05fail4 a Name cannot start with a CombiningChar (fatal) Element name expected.
2.3 [5] o-p05fail5 a Name cannot start with an Extender (fatal) Element name expected.
2.3 [9] not-wf-sa-113 Parameter entity values must use valid reference syntax; this reference is malformed. (fatal) Recursive reference "%foo;". (Reference path: (top-level)-%null;-%foo;-&foo;-%foo;)
2.3 [9] not-wf-sa-114 General entity values must use valid reference syntax; this reference is malformed. (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-&foo;)
2.3 [9] not-wf-sa-159 Uses '&' unquoted in an entity declaration, which is illegal syntax for an entity reference. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.3 [9] o-p09fail1 EntityValue excludes '%' (fatal) Recursive reference "%ent1;". (Reference path: (top-level)-%ent1;-%p09fail1.dtd;-&p09fail1.dtd;-%ent1;)
2.3 [9] o-p09fail2 EntityValue excludes '&' (fatal) Recursive reference "%ent1;". (Reference path: (top-level)-%ent1;-%p09fail2.dtd;-&p09fail2.dtd;-%ent1;)
2.3 [9] o-p09fail3 incomplete character reference (fatal) Recursive reference "%ent1;". (Reference path: (top-level)-%null;-%ent1;-&ent1;-%ent1;)
2.3 [9] o-p09fail4 quote types must match (fatal) Recursive reference "%ent1;". (Reference path: (top-level)-%null;-%ent1;-&ent1;-%ent1;)
2.3 [9] o-p09fail5 quote types must match (fatal) Recursive reference "%ent1;". (Reference path: (top-level)-%null;-%ent1;-&ent1;-%ent1;)
2.4 [14] not-wf-sa-025 Text may not contain a literal ']]>' sequence. (fatal) Text must not contain "]]>".
2.4 [14] not-wf-sa-026 Text may not contain a literal ']]>' sequence. (fatal) Text must not contain "]]>".
2.4 [14] not-wf-sa-029 Text may not contain a literal ']]>' sequence. (fatal) Text must not contain "]]>".
2.4 [14] o-p14fail1 '<' excluded (fatal) Element name expected.
2.4 [14] o-p14fail2 '&' excluded (fatal) Invalid character, ' ', in reference.
2.4 [14] o-p14fail3 "]]>" excluded (fatal) Text must not contain "]]>".
2.5 [15] not-wf-sa-027 Comments must be terminated with "-->". (fatal) "</doc>" expected.
2.5 [15] o-p15fail1 comments can't end in '-' (fatal) Comment must end with "-->".
2.5 [15] o-p15fail2 one comment per comment (contrasted with SGML) (fatal) Comment must not contain "--".
2.5 [15] o-p15fail3 can't include 2 or more adjacent '-'s (fatal) Comment must not contain "--".
2.5 [15] sgml03 Comments may not contain "--" (fatal) Comment must not contain "--".
2.5 [16] not-wf-sa-006 XML comments may not contain "--" (fatal) Comment must not contain "--".
2.5 [16] not-wf-sa-070 XML comments may not contain "--" (fatal) Comment must end with "-->".
2.6 [16] not-wf-sa-003 Processing Instruction target name is required. (fatal) Processing instruction name expected.
2.6 [16] not-wf-sa-004 SGML-ism: processing instructions end in '?>' not '>'. (fatal) "</doc>" expected.
2.6 [16] not-wf-sa-005 Processing instructions end in '?>' not '?'. (fatal) "</doc>" expected.
2.6 [16] not-wf-sa-028 Processing instructions must end with '?>'. (fatal) "</doc>" expected.
2.6 [16] o-p16fail1 "xml" is an invalid PITarget (fatal) A processing instruction target matching "[xX][mM][lL]" is not allowed.
2.6 [16] o-p16fail2 a PITarget must be present (fatal) Processing instruction name expected.
2.6 [16] pi No space between PI target name and data (fatal) "?>" expected.
2.6 [17] not-wf-ext-sa-003 Only one text declaration is permitted; a second one looks like an illegal processing instruction (target names of "xml" in any case are not allowed). (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
2.6 [17] not-wf-not-sa-002 Processing instruction target names may not be "XML" in any combination of cases. (fatal) Recursive reference "%e;". (Reference path: (top-level)-%null;-%e;-&e;-%e;)
2.6 [17] not-wf-sa-157 '<?xmL ...?>' is not a legal processing instruction target name. (fatal) A processing instruction target matching "[xX][mM][lL]" is not allowed.
2.7 not-wf-sa-105 Invalid placement of CDATA section. (fatal) "<!--" or "<!DOCTYPE" expected.
2.7 [18] not-wf-sa-017 CDATA sections need a terminating ']]>'. (fatal) "<![CDATA[" must end with "]]>".
2.7 [18] not-wf-sa-051 CDATA is invalid at top level of document. (fatal) "<!--" or "<!DOCTYPE" expected.
2.7 [18] not-wf-sa-128 Invalid CDATA syntax. (fatal) "EMPTY", "ANY", or '(' expected.
2.7 [18] o-p18fail1 no space before "CDATA" (fatal) "<!--" or "<![CDATA[" expected.
2.7 [18] o-p18fail2 no space after "CDATA" (fatal) "<!--" or "<![CDATA[" expected.
2.7 [18] o-p18fail3 CDSect's can't nest (fatal) Text must not contain "]]>".
2.7 [19] not-wf-sa-018 CDATA sections begin with a literal '<![CDATA[', no space. (fatal) "<!--" or "<![CDATA[" expected.
2.7 [19] not-wf-sa-108 No space in '<![CDATA['. (fatal) "<!--" or "<![CDATA[" expected.
2.7 [19] not-wf-sa-112 CDATA sections start '<![CDATA[', not '<!cdata['. (fatal) "<!--" or "<![CDATA[" expected.
2.8 not-wf-sa-160 Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. (fatal) Recursive reference "%e;". (Reference path: (top-level)-%null;-%e;-&e;-%e;)
2.8 not-wf-sa-161 Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. (fatal) Recursive reference "%e;". (Reference path: (top-level)-%null;-%e;-&e;-%e;)
2.8 not-wf-sa-162 Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. (fatal) Recursive reference "%e1;". (Reference path: (top-level)-%null;-%e1;-&e1;-%e1;)
2.8 valid-sa-094 This contains a parameter entity reference within a markup declaration in the internal DTD subset, violating the PEs in Internal Subset WFC. (fatal) Recursive reference "%e;". (Reference path: (top-level)-%null;-%e;-&e;-%e;)
2.8 sgml02 XML declaration must be at the very beginning of a document; it"s not a processing instruction (fatal) Document must start with "<?xml".
2.8 2.6 [23, 17] not-wf-sa-154 '<?XML ...?>' is neither an XML declaration nor a legal processing instruction target name. (fatal) A processing instruction target matching "[xX][mM][lL]" is not allowed.
2.8 2.6 [23, 17] not-wf-sa-155 '<?xmL ...?>' is neither an XML declaration nor a legal processing instruction target name. (fatal) A processing instruction target matching "[xX][mM][lL]" is not allowed.
2.8 2.6 [23, 17] not-wf-sa-156 '<?xMl ...?>' is neither an XML declaration nor a legal processing instruction target name. (fatal) A processing instruction target matching "[xX][mM][lL]" is not allowed.
2.8 [22] not-wf-sa-147 XML Declaration may not be preceded by whitespace. (fatal) Document must start with "<?xml".
2.8 [22] not-wf-sa-148 XML Declaration may not be preceded by comments or whitespace. (fatal) Document must start with "<?xml".
2.8 [22] not-wf-sa-152 XML declarations must include the "version=..." string. (fatal) Attribute, "version", is required.
2.8 [22] o-p22fail1 prolog must start with XML decl (fatal) Document must start with "<?xml".
2.8 [22] o-p22fail2 prolog must start with XML decl (fatal) Document must start with "<?xml".
2.8 [23] not-wf-sa-095 VersionInfo must come before EncodingDecl. (fatal) Attribute, "version", is required.
2.8 [23] not-wf-sa-098 Only one "version=..." string may appear in an XML declaration. (fatal) "?>" expected.
2.8 [23] not-wf-sa-099 Only three pseudo-attributes are in the XML declaration, and "valid=..." is not one of them. (fatal) "?>" expected.
2.8 [23] o-p23fail1 "xml" must be lower-case (fatal) A processing instruction target matching "[xX][mM][lL]" is not allowed.
2.8 [23] o-p23fail2 VersionInfo must be supplied (fatal) Attribute, "version", is required.
2.8 [23] o-p23fail3 VersionInfo must come first (fatal) Attribute, "version", is required.
2.8 [23] o-p23fail4 SDDecl must come last (fatal) "?>" expected.
2.8 [23] o-p23fail5 no SGML-type PIs (fatal) "?>" expected.
2.8 [24] not-wf-sa-094 Prolog VERSION must be lowercase. (fatal) Attribute, "version", is required.
2.8 [24] not-wf-sa-097 Both quotes surrounding VersionNum must be the same. (fatal) Invalid XML version format, "1.0' encoding=".
2.8 [24] o-p24fail1 quote types must match (fatal) Attribute value must not contain '<'.
2.8 [24] o-p24fail2 quote types must match (fatal) Attribute value must not contain '<'.
2.8 [25] o-p25fail1 Comment is illegal in VersionInfo. (fatal) '=' expected after attribute name, "version".
2.8 [26] not-wf-sa-102 Provides an illegal XML version number; spaces are illegal. (fatal) Invalid XML version format, "1.0 ".
2.8 [26] o-p26fail1 Illegal character in VersionNum. (fatal) Invalid XML version format, "1.0?".
2.8 [26] o-p26fail2 Illegal character in VersionNum. (fatal) Invalid XML version format, "1.0^".
2.8 [27] not-wf-sa-036 Text may not appear after the root element. (fatal) "</doc>" expected.
2.8 [27] not-wf-sa-037 Character references may not appear after the root element. (fatal) "</doc>" expected.
2.8 [27] not-wf-sa-040 Provides two document elements. (fatal) "</doc>" expected.
2.8 [27] not-wf-sa-041 Provides two document elements. (fatal) "</doc>" expected.
2.8 [27] not-wf-sa-043 Provides #PCDATA text after the document element. (fatal) "</doc>" expected.
2.8 [27] not-wf-sa-044 Provides two document elements. (fatal) "</doc>" expected.
2.8 [27] not-wf-sa-048 Provides a CDATA section after the roor element. (fatal) "</doc>" expected.
2.8 [27] not-wf-sa-151 XML declarations may not follow document content. (fatal) Document must start with "<?xml".
2.8 [27] o-p27fail1 References aren't allowed in Misc, even if they would resolve to valid Misc. (fatal) Invalid document structure.
2.8 [28] not-wf-sa-055 Invalid Document Type Definition format. (fatal) "<?" or "<!" expected.
2.8 [28] not-wf-sa-056 Invalid Document Type Definition format - misplaced comment. (fatal) Unknown external identifier, "--". "SYSTEM" or "PUBLIC" expected.
2.8 [28] not-wf-sa-107 Invalid document type declaration. CDATA alone is invalid. (fatal) Conditional section only allowed in external subset.
2.8 [28] not-wf-sa-149 XML Declaration may not be within a DTD. (fatal) Document must start with "<?xml".
2.8 [28] o-p28fail1 only declarations in DTD. (fatal) "<?" or "<!" expected.
2.8 [29] not-wf-sa-063 Conditional sections may only appear in the external DTD subset. (fatal) Conditional section only allowed in external subset.
2.8 [29] o-p29fail1 A processor must not pass unknown declaration types. (fatal) Declaration type expected. Must be "ELEMENT", "ATTLIST", "ENTITY", or "NOTATION".
2.8 [30] o-p30fail1 An XML declaration is not the same as a TextDecl (fatal) "?>" expected.
2.8 [31] o-p31fail1 external subset excludes doctypedecl (fatal) Declaration type expected. Must be "ELEMENT", "ATTLIST", "ENTITY", or "NOTATION".
2.9 [32] not-wf-sa-096 Space is required before the standalone declaration. (fatal) "?>" expected.
2.9 [32] not-wf-sa-100 Only "yes" and "no" are permitted as values of "standalone". (fatal) Invalid encoding name, "YES".
2.9 [32] o-p32fail1 quote types must match (fatal) Attribute value must not contain '<'.
2.9 [32] o-p32fail2 quote types must match (fatal) Attribute value must not contain '<'.
2.9 [32] o-p32fail3 initial S is required (fatal) "?>" expected.
2.9 [32] o-p32fail4 quotes are required (fatal) ' or " expected. Attribute value must be quoted.
2.9 [32] o-p32fail5 yes or no must be lower case (fatal) Invalid encoding name, "YES".
3 not-wf-sa-039 Tests the Element Type Match WFC - end tag name must match start tag name. (fatal) "</a>" expected.
3 [39] not-wf-sa-176 Start tags must have matching end tags. (fatal) "</doc>" expected.
3 [39] o-p39fail1 start-tag requires end-tag (fatal) "</doc>" expected.
3 [39] o-p39fail2 end-tag requires start-tag (fatal) "</doc>" expected.
3 [39] o-p39fail3 XML documents contain one or more elements (thrown SAXException) [no exception message]
3 [39] o-p39fail4 (fatal) "?>" expected.
3 [39] o-p39fail5 (fatal) "?>" expected.
3 [39] sgml01 SGML-ism: omitted end tag for EMPTY content (fatal) "</root>" expected.
3.1 not-wf-sa-038 Tests the "Unique Att Spec" WF constraint by providing multiple values for an attribute. (fatal) Duplicate attribute name, "x".
3.1 not-wf-sa-081 This tests the No External Entity References WFC, since the entity is referred to within an attribute. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
3.1 not-wf-sa-082 This tests the No External Entity References WFC, since the entity is referred to within an attribute. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
3.1 [40] attlist10 Whitespace required between attributes (fatal) "</root>" expected.
3.1 [40] not-wf-sa-046 This start (or empty element) tag was not terminated correctly. (fatal) "/>" or '>' expected.
3.1 [40] not-wf-sa-049 Missing start tag (fatal) "</doc>" expected.
3.1 [40] o-p40fail1 S is required between attributes (fatal) "</doc>" expected.
3.1 [40] o-p40fail2 tags start with names, not nmtokens (fatal) Element name expected.
3.1 [40] o-p40fail3 tags start with names, not nmtokens (fatal) Element name expected.
3.1 [40] o-p40fail4 no space before name (fatal) Element name expected.
3.1 [41] not-wf-sa-001 Attribute values must start with attribute names, not "?". (fatal) "/>" or '>' expected.
3.1 [41] not-wf-sa-011 SGML-ism: attribute values must be explicitly assigned a value, it can't act as a boolean toggle. (fatal) '=' expected after attribute name, "a1".
3.1 [41] not-wf-sa-015 Attribute values need a value, not just an equals sign. (fatal) ' or " expected. Attribute value must be quoted.
3.1 [41] not-wf-sa-016 Attribute values need an associated name. (fatal) "/>" or '>' expected.
3.1 [41] not-wf-sa-178 Invalid syntax matching double quote is missing. (fatal) Attribute value must not contain '<'.
3.1 [41] o-p41fail1 quotes are required (contrast with SGML) (fatal) "EMPTY", "ANY", or '(' expected.
3.1 [41] o-p41fail2 attribute name is required (contrast with SGML) (fatal) "EMPTY", "ANY", or '(' expected.
3.1 [41] o-p41fail3 Eq required (fatal) '=' expected after attribute name, "att".
3.1 [42] element00 EOF in middle of incomplete ETAG (fatal) "</root>" expected.
3.1 [42] element01 EOF in middle of incomplete ETAG (fatal) "</root>" expected.
3.1 [42] not-wf-sa-019 End tags may not be abbreviated as '</>'. (fatal) "</doc>" expected.
3.1 [42] not-wf-sa-042 Invalid End Tag (fatal) > expected.
3.1 [42] not-wf-sa-053 End tag does not match start tag. (fatal) "</doc>" expected.
3.1 [42] o-p42fail1 no space before name (fatal) "</doc>" expected.
3.1 [42] o-p42fail2 cannot end with "/>" (fatal) > expected.
3.1 [42] o-p42fail3 no NET (contrast with SGML) (fatal) "/>" or '>' expected.
3.1 [43] element02 Illegal markup (<%@ ... %>) (fatal) Element name expected.
3.1 [43] element03 Illegal markup (<% ... %>) (fatal) Element name expected.
3.1 [43] element04 Illegal markup (<!ELEMENT ... >) (fatal) "<!--" or "<![CDATA[" expected.
3.1 [43] not-wf-sa-035 The '<' character is a markup delimiter and must start an element, CDATA section, PI, or comment. (fatal) Element name expected.
3.1 [43] not-wf-sa-111 Entiry reference must be in content of element not Start-tag. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
3.1 [43] not-wf-sa-150 XML declarations may not be within element content. (fatal) Document must start with "<?xml".
3.1 [43] o-p43fail1 no non-comment declarations (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-&ent;)
3.1 [43] o-p43fail2 no conditional sections (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-&ent;)
3.1 [43] o-p43fail3 no conditional sections (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-&ent;)
3.1 [44] attlist11 Whitespace required between attributes (fatal) "</root>" expected.
3.1 [44] not-wf-sa-045 Invalid Empty Element Tag (fatal) "/>" or '>' expected.
3.1 [44] not-wf-sa-047 Invalid empty element tag invalid whitespace (fatal) "/>" or '>' expected.
3.1 [44] not-wf-sa-186 Whitespace is required between attribute/value pairs. (fatal) "</a>" expected.
3.1 [44] o-p44fail1 Illegal space before Empty element tag. (fatal) Element name expected.
3.1 [44] o-p44fail2 Illegal space after Empty element tag. (fatal) "/>" or '>' expected.
3.1 [44] o-p44fail3 Illegal comment in Empty element tag. (fatal) "/>" or '>' expected.
3.1 [44] o-p44fail4 Whitespace required between attributes. (fatal) "</doc>" expected.
3.1 [44] o-p44fail5 Duplicate attribute name is illegal. (fatal) Duplicate attribute name, "att".
3.2 [45] not-wf-sa-057 This isn't SGML; comments can't exist in declarations. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-&e;)
3.2 [45] not-wf-sa-129 Invalid syntax for Element Type Declaration. (fatal) "EMPTY", "ANY", or '(' expected.
3.2 [45] not-wf-sa-130 Invalid syntax for Element Type Declaration. (fatal) '>' expected.
3.2 [45] not-wf-sa-131 Invalid syntax for Element Type Declaration. (fatal) '>' expected.
3.2 [45] not-wf-sa-136 Tag omission is invalid in XML. (fatal) "EMPTY", "ANY", or '(' expected.
3.2 [45] not-wf-sa-137 Space is required before a content model. (fatal) Whitespace expected.
3.2 [45] o-p45fail1 ELEMENT must be upper case. (fatal) Declaration type expected. Must be "ELEMENT", "ATTLIST", "ENTITY", or "NOTATION".
3.2 [45] o-p45fail2 S before contentspec is required. (fatal) Whitespace expected.
3.2 [45] o-p45fail3 only one content spec (fatal) Element name expected.
3.2 [45] o-p45fail4 no comments in declarations (contrast with SGML) (fatal) '>' expected.
3.2 [45] sgml05 ELEMENT declarations apply to only one element, unlike SGML (fatal) Element name expected.
3.2 [45] sgml07 SGML Tag minimization specifications are not allowed (fatal) "EMPTY", "ANY", or '(' expected.
3.2 [45] sgml08 SGML Tag minimization specifications are not allowed (fatal) "EMPTY", "ANY", or '(' expected.
3.2 [45] sgml09 SGML Content model exception specifications are not allowed (fatal) '>' expected.
3.2 [45] sgml10 SGML Content model exception specifications are not allowed (fatal) '>' expected.
3.2 [46] o-p46fail1 no parens on declared content (fatal) '(' or element name expected.
3.2 [46] o-p46fail2 no inclusions (contrast with SGML) (fatal) '>' expected.
3.2 [46] o-p46fail3 no exclusions (contrast with SGML) (fatal) '>' expected.
3.2 [46] o-p46fail4 no space before occurrence (fatal) '>' expected.
3.2 [46] o-p46fail5 single group (fatal) '>' expected.
3.2 [46] o-p46fail6 can't be both declared and modeled (fatal) '>' expected.
3.2 [46] sgml11 CDATA is not a valid content model spec (fatal) "EMPTY", "ANY", or '(' expected.
3.2 [46] sgml12 RCDATA is not a valid content model spec (fatal) "EMPTY", "ANY", or '(' expected.
3.2.1 not-wf-sa-133 Illegal whitespace before optional character causes syntax error. (fatal) ')' expected.
3.2.1 not-wf-sa-134 Illegal whitespace before optional character causes syntax error. (fatal) '>' expected.
3.2.1 [46] not-wf-sa-139 The element-content model should not be empty. (fatal) '(' or element name expected.
3.2.1 [47] not-wf-sa-122 Invalid syntax mixed connectors are used. (fatal) Invalid operator, '|'. (Previous operator was ','.)
3.2.1 [47] not-wf-sa-135 Invalid character used as connector. (fatal) ')' expected.
3.2.1 [47] o-p47fail1 Invalid operator '|' must match previous operator ',' (fatal) Invalid operator, '|'. (Previous operator was ','.)
3.2.1 [47] o-p47fail2 Illegal character '-' in Element-content model (fatal) '>' expected.
3.2.1 [47] o-p47fail3 Optional character must follow a name or list (fatal) "EMPTY", "ANY", or '(' expected.
3.2.1 [47] o-p47fail4 Illegal space before optional character (fatal) '>' expected.
3.2.1 [47] sgml13 SGML Unordered content models not allowed (fatal) ')' expected.
3.2.1 [48] content01 No whitespace before "?" in content model (fatal) ')' expected.
3.2.1 [48] content02 No whitespace before "*" in content model (fatal) ')' expected.
3.2.1 [48] content03 No whitespace before "+" in content model (fatal) ')' expected.
3.2.1 [48] not-wf-sa-123 Invalid syntax mismatched parenthesis. (fatal) '>' expected.
3.2.1 [48] not-wf-sa-138 Invalid syntax for content particle. (fatal) ')' expected.
3.2.1 [48] o-p48fail1 Illegal space before optional character (fatal) ')' expected.
3.2.1 [48] o-p48fail2 Illegal space before optional character (fatal) ')' expected.
3.2.1 [49] o-p49fail1 connectors must match (fatal) Invalid operator, ','. (Previous operator was '|'.)
3.2.1 [50] not-wf-sa-132 Invalid syntax mixed connectors used. (fatal) Invalid operator, '|'. (Previous operator was ','.)
3.2.1 [50] o-p50fail1 connectors must match (fatal) Invalid operator, '|'. (Previous operator was ','.)
3.2.1 [55] nwf-dtd00 Comma mandatory in content model (fatal) ')' expected.
3.2.1 [55] nwf-dtd01 Can't mix comma and vertical bar in content models (fatal) Invalid operator, '|'. (Previous operator was ','.)
3.2.2 [51] not-wf-sa-124 Invalid format of Mixed-content declaration. (fatal) '(' or element name expected.
3.2.2 [51] not-wf-sa-125 Invalid syntax extra set of parenthesis not necessary. (fatal) '(' or element name expected.
3.2.2 [51] not-wf-sa-126 Invalid syntax Mixed-content must be defined as zero or more. (fatal) '>' expected.
3.2.2 [51] not-wf-sa-127 Invalid syntax Mixed-content must be defined as zero or more. (fatal) '>' expected.
3.2.2 [51] not-wf-sa-183 Mixed content declarations may not include content particles. (fatal) ')' expected.
3.2.2 [51] not-wf-sa-184 In mixed content models, element names must not be parenthesized. (fatal) '(' or element name expected.
3.2.2 [51] o-p51fail1 occurrence on #PCDATA group must be * (fatal) '>' expected.
3.2.2 [51] o-p51fail2 occurrence on #PCDATA group must be * (fatal) '>' expected.
3.2.2 [51] o-p51fail3 #PCDATA must come first (fatal) '(' or element name expected.
3.2.2 [51] o-p51fail4 occurrence on #PCDATA group must be * (fatal) Content model, "(#PCDATA|doc)", must match the mixed model "(#PCDATA|foo|...|bar)*".
3.2.2 [51] o-p51fail5 only '|' connectors (fatal) ')' expected.
3.2.2 [51] o-p51fail6 Only '|' connectors and occurrence on #PCDATA group must be * (fatal) ')' expected.
3.2.2 [51] o-p51fail7 no nested groups (fatal) '(' or element name expected.
3.3 [52] not-wf-sa-066 Required whitespace is missing. (fatal) Whitespace expected.
3.3 [52] not-wf-sa-158 SGML-ism: "#NOTATION gif" can't have attributes. (fatal) Element name expected.
3.3 [52] o-p52fail1 A name is required (fatal) Element name expected.
3.3 [52] o-p52fail2 A name is required (fatal) Whitespace expected.
3.3 [52] sgml04 ATTLIST declarations apply to only one element, unlike SGML (fatal) Element name expected.
3.3 [52] sgml06 ATTLIST declarations are never global, unlike in SGML (fatal) Element name expected.
3.3 [53] not-wf-sa-064 Space is required between attribute type and default values in <!ATTLIST...> declarations. (fatal) Whitespace expected.
3.3 [53] not-wf-sa-065 Space is required between attribute name and type in <!ATTLIST...> declarations. (fatal) Whitespace expected.
3.3 [53] not-wf-sa-067 Space is required between attribute type and default values in <!ATTLIST...> declarations. (fatal) Whitespace expected.
3.3 [53] o-p53fail1 S is required before default (fatal) Whitespace expected.
3.3 [53] o-p53fail2 S is required before type (fatal) Whitespace expected.
3.3 [53] o-p53fail3 type is required (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3 [53] o-p53fail4 default is required (fatal) Whitespace expected.
3.3 [53] o-p53fail5 name is requried (fatal) Attribute name expected.
3.3.1 [54] not-wf-sa-058 Invalid character , in ATTLIST enumeration (fatal) '|' or ')' expected.
3.3.1 [54] o-p54fail1 don't pass unknown attribute types (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [55] o-p55fail1 must be upper case (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] attlist01 SGML's NUTOKEN is not allowed. (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] attlist02 SGML's NUTOKENS attribute type is not allowed. (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] attlist04 SGML's NUMBER attribute type is not allowed. (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] attlist05 SGML's NUMBERS attribute type is not allowed. (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] attlist06 SGML's NAME attribute type is not allowed. (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] attlist07 SGML's NAMES attribute type is not allowed. (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] attlist08 SGML's #CURRENT is not allowed. (fatal) ' or " expected. Attribute value must be quoted.
3.3.1 [56] attlist09 SGML's #CONREF is not allowed. (fatal) ' or " expected. Attribute value must be quoted.
3.3.1 [56] not-wf-sa-060 Invalid type NAME defined in ATTLIST. (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] o-p56fail1 no IDS type (fatal) Whitespace expected.
3.3.1 [56] o-p56fail2 no NUMBER type (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] o-p56fail3 no NAME type (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [56] o-p56fail4 no ENTITYS type - types must be upper case (fatal) Whitespace expected.
3.3.1 [56] o-p56fail5 types must be upper case (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [57] o-p57fail1 no keyword for NMTOKEN enumeration (fatal) Invalid default value for attribute declaration
3.3.1 [58] not-wf-sa-068 Space is required between NOTATION keyword and list of enumerated choices in <!ATTLIST...> declarations. (fatal) Whitespace expected.
3.3.1 [58] o-p58fail1 at least one value required (fatal) Invalid name enumeration, "(Name | Name | ...)".
3.3.1 [58] o-p58fail2 separator must be '|' (fatal) '|' or ')' expected.
3.3.1 [58] o-p58fail3 notations are NAMEs, not NMTOKENs -- note: Leaving the invalid notation undeclared would cause a validating parser to fail without checking the name syntax, so the notation is declared with an invalid name. A parser that reports error positions should report an error at the AttlistDecl on line 6, before reaching the notation declaration. (fatal) Invalid name enumeration, "(Name | Name | ...)".
3.3.1 [58] o-p58fail4 NOTATION must be upper case (fatal) Attribute type expected. (e.g. "CDATA", "ID", "ENTITY", etc.)
3.3.1 [58] o-p58fail5 S after keyword is required (fatal) Whitespace expected.
3.3.1 [58] o-p58fail6 parentheses are require (fatal) ')' expected.
3.3.1 [58] o-p58fail7 values are unquoted (fatal) ')' expected.
3.3.1 [58] o-p58fail8 values are unquoted (fatal) Invalid name enumeration, "(Name | Name | ...)".
3.3.1 [59] attlist03 Comma doesn't separate enumerations, unlike in SGML. (fatal) '|' or ')' expected.
3.3.1 [59] not-wf-sa-059 String literal must be in quotes. (fatal) Invalid default value for attribute declaration
3.3.1 [59] o-p59fail1 at least one required (fatal) Invalid name token enumeration, "(Nmtoken | Nmtoken | ...)".
3.3.1 [59] o-p59fail2 separator must be "," (fatal) '|' or ')' expected.
3.3.1 [59] o-p59fail3 values are unquoted (fatal) Invalid name token enumeration, "(Nmtoken | Nmtoken | ...)".
3.3.2 [60] o-p60fail1 keywords must be upper case (fatal) ' or " expected. Attribute value must be quoted.
3.3.2 [60] o-p60fail2 S is required after #FIXED (fatal) Whitespace expected.
3.3.2 [60] o-p60fail3 only #FIXED has both keyword and value (fatal) Attribute name expected.
3.3.2 [60] o-p60fail4 #FIXED required value (fatal) Whitespace expected.
3.3.2 [60] o-p60fail5 only one default type (fatal) Attribute name expected.
3.4 [61] cond01 Only INCLUDE and IGNORE are conditional section keywords (fatal) "<![INCLUDE[" or "<![IGNORE[" expected.
3.4 [61] cond02 Must have keyword in conditional sections (fatal) Recursive reference "%MAYBE;". (Reference path: (top-level)-%null;-%cond.dtd;-&cond.dtd;-%MAYBE;-%MAYBE;)
3.4 [61] o-p61fail1 no other types, including TEMP, which is valid in SGML (fatal) "<![INCLUDE[" or "<![IGNORE[" expected.
3.4 [62] not-wf-not-sa-001 Conditional sections must be properly terminated ("]>" used instead of "]]>"). (fatal) "<![INCLUDE[" or "<![IGNORE[" must end with "]]>".
3.4 [62] not-wf-not-sa-003 Conditional sections must be properly terminated ("]]>" omitted). (fatal) "<![INCLUDE[" or "<![IGNORE[" must end with "]]>".
3.4 [62] not-wf-not-sa-004 Conditional sections must be properly terminated ("]]>" omitted). (fatal) "<![INCLUDE[" or "<![IGNORE[" must end with "]]>".
3.4 [62] not-wf-not-sa-006 Conditional sections need a '[' after the INCLUDE or IGNORE. (fatal) "<![INCLUDE[" or "<![IGNORE[" expected.
3.4 [62] o-p62fail1 INCLUDE must be upper case (fatal) "<![INCLUDE[" or "<![IGNORE[" expected.
3.4 [62] o-p62fail2 no spaces in terminating delimiter (fatal) "<![INCLUDE[" or "<![IGNORE[" must end with "]]>".
3.4 [63] o-p63fail1 IGNORE must be upper case (fatal) "<![INCLUDE[" or "<![IGNORE[" expected.
3.4 [63] o-p63fail2 delimiters must be balanced (fatal) "<![INCLUDE[" or "<![IGNORE[" must end with "]]>".
3.4 [64] o-p64fail1 section delimiters must balance (fatal) Invalid document structure.
3.4 [64] o-p64fail2 section delimiters must balance (fatal) "<![INCLUDE[" or "<![IGNORE[" must end with "]]>".
4.1 not-wf-ext-sa-001 Tests the No Recursion WFC by having an external general entity be self-recursive. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&e;)
4.1 not-wf-sa-084 Tests the Parsed Entity WFC by referring to an unparsed entity. (This precedes the error of not declaring that entity's notation, which may be detected any time before the DTD parsing is completed.) (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&e;)
4.1 not-wf-sa-180 The Entity Declared WFC requires entities to be declared before they are used in an attribute list declaration. (fatal) Undefined entity, "e".
4.1 not-wf-sa-185 Tests the Entity Declared WFC. Note: a nonvalidating parser is permitted not to report this WFC violation, since it would need to read an external parameter entity to distinguish it from a violation of the Standalone Declaration VC. (fatal) Undefined entity, "e".
4.1 [66] not-wf-sa-009 Character references may have only decimal or numeric strings. (fatal) Invalid character, 'R', in reference.
4.1 [66] not-wf-sa-022 Character references end with semicolons, always! (fatal) Reference must end with ';'.
4.1 [66] not-wf-sa-052 Invalid character reference. (fatal) Invalid document structure.
4.1 [66] not-wf-sa-093 Hexadecimal character references may not use the uppercase 'X'. (fatal) Invalid character, 'X', in reference.
4.1 [66] not-wf-sa-179 Invalid syntax matching double quote is missing. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&e;)
4.1 [66] o-p66fail1 terminating ';' is required (fatal) Reference must end with ';'.
4.1 [66] o-p66fail2 no S after '&#' (fatal) Invalid character, ' ', in reference.
4.1 [66] o-p66fail3 no hex digits in numeric reference (fatal) Invalid character, 'A', in reference.
4.1 [66] o-p66fail4 only hex digits in hex references (fatal) Reference must end with ';'.
4.1 [66] o-p66fail5 no references to non-characters (fatal) Character reference, "&#5;", is out of range.
4.1 [66] o-p66fail6 no references to non-characters (fatal) Character reference, "&#xd802", is out of range.
4.1 [68] not-wf-sa-007 General entity references have no whitespace after the entity name and before the semicolon. (fatal) Reference must end with ';'.
4.1 [68] not-wf-sa-010 Ampersand may only appear as part of a general entity reference. (fatal) Invalid character, ' ', in reference.
4.1 [68] not-wf-sa-071 ENTITY can't reference itself directly or indirectly. (fatal) Recursive reference, "&e1;". (reference path: (top-level)-%null;-%e1;-&e1;-%null;-&e1;)
4.1 [68] not-wf-sa-072 Undefined ENTITY foo. (fatal) Undefined entity, "foo".
4.1 [68] not-wf-sa-073 Undefined ENTITY f. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&e;)
4.1 [68] not-wf-sa-075 ENTITY can't reference itself directly or indirectly. (fatal) Recursive reference, "&e1;". (reference path: (top-level)-%null;-%e1;-&e1;-%null;-&e1;)
4.1 [68] not-wf-sa-076 Undefined ENTITY foo. (fatal) Undefined entity, "foo".
4.1 [68] not-wf-sa-078 Undefined ENTITY foo. (fatal) Undefined entity, "foo".
4.1 [68] not-wf-sa-079 ENTITY can't reference itself directly or indirectly. (fatal) Recursive reference, "&e1;". (reference path: (top-level)-%null;-%e1;-&e1;-%null;-&e1;)
4.1 [68] not-wf-sa-080 ENTITY can't reference itself directly or indirectly. (fatal) Recursive reference, "&e1;". (reference path: (top-level)-%null;-%e1;-&e1;-%null;-&e1;)
4.1 [68] not-wf-sa-110 Entity reference must be in content of element. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&e;)
4.1 [68] not-wf-sa-118 Entity reference expansion is not recursive. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&e;)
4.1 [68] not-wf-sa-121 A name of an ENTITY was started with an invalid character. (fatal) Invalid ENTITY declaration. Name expected.
4.1 [68] o-p68fail1 terminating ';' is required (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&ent;)
4.1 [68] o-p68fail2 no S after '&' (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&ent;)
4.1 [68] o-p68fail3 no S before ';' (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&ent;)
4.1 [69] dtd02 PE name immediately after "%" (fatal) Recursive reference "%foo;". (Reference path: (top-level)-%null;-%foo;-&foo;-%null;-%foo;)
4.1 [69] dtd03 PE name immediately followed by ";" (fatal) Recursive reference "%foo;". (Reference path: (top-level)-%null;-%foo;-&foo;-%null;-%foo;)
4.1 [69] not-wf-not-sa-008 In DTDs, the '%' character must be part of a parameter entity reference. (fatal) Parameter entity name expected.
4.1 [69] not-wf-sa-163 Invalid placement of Parameter entity reference. (fatal) Recursive reference "%e;". (Reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-%e;)
4.1 [69] not-wf-sa-164 Invalid placement of Parameter entity reference. (fatal) Recursive reference "%e;". (Reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-%e;)
4.1 [69] o-p69fail1 terminating ';' is required (fatal) Recursive reference "%pe;". (Reference path: (top-level)-%null;-%pe;-&pe;-%null;-&null;-%pe;)
4.1 [69] o-p69fail2 no S after '%' (fatal) Recursive reference "%pe;". (Reference path: (top-level)-%null;-%pe;-&pe;-%null;-&null;-%pe;)
4.1 [69] o-p69fail3 no S before ';' (fatal) Recursive reference "%pe;". (Reference path: (top-level)-%null;-%pe;-&pe;-%null;-&null;-%pe;)
4.2 not-wf-sa-106 Invalid placement of entity declaration. (fatal) Invalid document structure.
4.2 [70] not-wf-sa-109 Tags invalid within EntityDecl. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.2 [70] o-p70fail1 This is neither (fatal) Invalid ENTITY declaration. Name expected.
4.2 [71] not-wf-sa-062 Entity declarations need space after the entity name. (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-%null;-&null;-&foo;)
4.2 [71] o-p71fail1 S is required before EntityDef (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%null;-%ge;-&ge;-%null;-&null;-&ge;)
4.2 [71] o-p71fail2 Entity name is a Name, not an NMToken (fatal) Invalid ENTITY declaration. Name expected.
4.2 [71] o-p71fail3 no S after "<!" (fatal) Declaration type expected. Must be "ELEMENT", "ATTLIST", "ENTITY", or "NOTATION".
4.2 [71] o-p71fail4 S is required after "<!ENTITY" (fatal) Whitespace expected.
4.2 [72] not-wf-sa-165 Parameter entity declarations must have a space before the '%'. (fatal) Whitespace expected.
4.2 [72] o-p72fail1 S is required after "<!ENTITY" (fatal) Whitespace expected.
4.2 [72] o-p72fail2 S is required after '%' (fatal) Whitespace expected.
4.2 [72] o-p72fail3 S is required after name (fatal) Recursive reference "%pe;". (Reference path: (top-level)-%null;-%pe;-&pe;-%null;-&null;-%pe;)
4.2 [72] o-p72fail4 Entity name is a name, not an NMToken (fatal) Invalid ENTITY declaration. Name expected.
4.2 [73] o-p73fail1 No typed replacement text (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2 [73] o-p73fail2 Only one replacement value (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2 [73] o-p73fail3 No NDataDecl on replacement text (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2 [73] o-p73fail4 Value is required (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2 [73] o-p73fail5 No NDataDecl without value (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2 [74] not-wf-sa-089 Parameter entities "are" always parsed; NDATA annotations are not permitted. (fatal) Recursive reference "%foo;". (Reference path: (top-level)-%null;-%foo;-&foo;-%null;-&null;-%foo;)
4.2 [74] not-wf-sa-091 Parameter entities "are" always parsed; NDATA annotations are not permitted. (fatal) Recursive reference "%foo;". (Reference path: (top-level)-%foo;-%n;-&n;-%n;-&foo;-%foo;)
4.2 [74] o-p74fail1 no NDataDecls on parameter entities (fatal) Recursive reference "%pe;". (Reference path: (top-level)-%pe;-%unknot;-&unknot;-%Unknown;-&pe;-%pe;)
4.2 [74] o-p74fail2 value is required (fatal) Recursive reference "%pe;". (Reference path: (top-level)-%pe;-%unknot;-&unknot;-%Unknown;-&pe;-%pe;)
4.2 [74] o-p74fail3 only one value (fatal) Recursive reference "%pe;". (Reference path: (top-level)-%null;-%pe;-&pe;-%null;-&null;-%pe;)
4.2.2 [75] dtd04 PUBLIC literal must be quoted (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-%null;-&null;-&foo;)
4.2.2 [75] dtd05 SYSTEM identifier must be quoted (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-%null;-&null;-&foo;)
4.2.2 [75] not-wf-sa-054 PUBLIC requires two literals. (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-%null;-&null;-&foo;)
4.2.2 [75] not-wf-sa-061 External entity declarations require whitespace between public and system IDs. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.2.2 [75] o-p75fail1 S required after "PUBLIC" (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&null;-&ent;)
4.2.2 [75] o-p75fail2 S required after "SYSTEM" (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&null;-&ent;)
4.2.2 [75] o-p75fail3 S required between literals (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&null;-&ent;)
4.2.2 [75] o-p75fail4 "SYSTEM" implies only one literal (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&null;-&ent;)
4.2.2 [75] o-p75fail5 only one keyword (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&null;-&ent;)
4.2.2 [75] o-p75fail6 "PUBLIC" requires two literals (contrast with SGML) (fatal) Recursive reference, "&ent;". (reference path: (top-level)-%null;-%ent;-&ent;-%null;-&null;-&ent;)
4.2.2 [76] not-wf-sa-069 Space is required before an NDATA entity annotation. (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%foo;-%eps;-&eps;-%eps.exe;-&foo;-&foo;)
4.2.2 [76] not-wf-sa-083 Undefined NOTATION n. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.2.2 [76] o-p76fail1 S is required before "NDATA" (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2.2 [76] o-p76fail2 "NDATA" is upper-case (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2.2 [76] o-p76fail3 notation name is required (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.2.2 [76] o-p76fail4 notation names are Names (fatal) Recursive reference, "&ge;". (reference path: (top-level)-%ge;-%unknot;-&unknot;-%Unknown;-&ge;-&ge;)
4.3.1 4.3.2 [77, 78] not-wf-ext-sa-002 External entities have "text declarations", which do not permit the "standalone=..." attribute that's allowed in XML declarations. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.1 [77] decl01 External entities may not have standalone decls. (fatal) Recursive reference "%ent01;". (Reference path: (top-level)-%null;-%ent01;-&ent01;-%null;-&null;-%ent01;)
4.3.1 [77] dtd07 Text declarations (which optionally begin any external entity) are required to have "encoding=...". (fatal) Whitespace expected.
4.3.1 [77] encoding07 Text declarations (which optionally begin any external entity) are required to have "encoding=...". (fatal) Recursive reference, "&empty;". (reference path: (top-level)-%null;-%empty;-&empty;-%null;-&null;-&empty;)
4.3.2 not-wf-sa-074 Internal general parsed entities are only well formed if they match the "content" production. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-103 End-tag required for element foo. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-104 Internal general parsed entities are only well formed if they match the "content" production. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-116 Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-117 Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-119 Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-153 Text declarations may not begin internal parsed entities; they may only appear at the beginning of external parsed (parameter or general) entities. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-181 Internal parsed entities must match the content production to be well formed. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 not-wf-sa-182 Internal parsed entities must match the content production to be well formed. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.3.2 [79] not-wf-not-sa-007 A <!DOCTYPE ...> declaration may not begin any external entity; it's only found once, in the document entity. (fatal) Declaration type expected. Must be "ELEMENT", "ATTLIST", "ENTITY", or "NOTATION".
4.3.3 [81] encoding01 Illegal character " " in encoding name (fatal) Invalid encoding name, " utf-8".
4.3.3 [81] encoding02 Illegal character "/" in encoding name (fatal) Invalid encoding name, "a/b".
4.3.3 [81] encoding03 Illegal character reference in encoding name (fatal) Invalid encoding name, "just&#41;word".
4.3.3 [81] encoding04 Illegal character ":" in encoding name (fatal) Invalid encoding name, "utf:8".
4.3.3 [81] encoding05 Illegal character "@" in encoding name (fatal) Invalid encoding name, "@import(sys-encoding)".
4.3.3 [81] encoding06 Illegal character "+" in encoding name (fatal) Invalid encoding name, "XYZ+999".
4.3.3 [81] not-wf-sa-101 Space is not permitted in an encoding name. (fatal) Invalid encoding name, " UTF-8".
4.5 not-wf-sa-092 The replacement text of this entity has an illegal reference, because the character reference is expanded immediately. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.5 not-wf-sa-115 The replacement text of this entity is an illegal character reference, which must be rejected when it is parsed in the context of an attribute value. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
4.5 not-wf-sa-120 Character references are expanded in the replacement text of an internal entity, which is then parsed as usual. Accordingly, & must be doubly quoted - encoded either as &amp; or as &#38;#38;. (fatal) Recursive reference, "&e;". (reference path: (top-level)-%null;-%e;-&e;-%null;-&null;-&e;)
41. [68] not-wf-sa-077 Undefined ENTITY bar. (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-%null;-&null;-&foo;)

Informative Tests

Certain XML documents are specified to be errors, but the handling of those documents is not fully determined by the XML 1.0 specification. As a rule, these errors may be reported in any manner whatsoever, or completely ignored, without consequence in terms of conformance to the XML 1.0 specification. And some of these documents don't have errors; documents in encodings other than UTF-8 and UTF-16 are legal, but not all processors are required to parse them.

Such "optional" errors are listed here for informational purposes, since processors which ignore such errors may cause document creators to create documents which are not accepted by all conformant XML 1.0 processors. (And of course, processors which produce incorrect diagnostics for such cases should be avoided.)

Section and [Rules] Test ID Description Diagnostic
2.11 [33] lang01 Illegal language identification (fatal) "</root>" expected.
2.11 [33] lang02 Illegal language identification (fatal) "</root>" expected.
2.11 [33] lang03 Illegal language identification (fatal) "</root>" expected.
2.11 [33] lang04 Illegal language identification (fatal) "</root>" expected.
2.11 [33] lang05 Illegal language identification (fatal) "</root>" expected.
2.11 [33] lang06 Illegal language identification (fatal) "</root>" expected.
2.3, 4.2.2 [11] o-p11pass1 system literals may not contain URI fragments (fatal) "</doc>" expected.
2.8 pe01 Parameter entities must consist of a series of complete markup declarations of the types allowed by the nonterminal markupdecl, interespersed with whitespace or PERefs. (fatal) Recursive reference "%bad-pe;". (Reference path: (top-level)-%bad-pe;-%pe01.dtd;-&pe01.dtd;-%file:/d:/xml/xmlconf/sun/invalid/pe01.dtd;-&bad-pe;-%bad-pe;)
4.2.2 [75] uri01 SYSTEM ids may not have URI fragments (fatal) Recursive reference, "&foo;". (reference path: (top-level)-%null;-%foo;-&foo;-%null;-&null;-&foo;)
4.3.3 [4,84] pr-xml-euc-jp Test support for the EUC-JP encoding, and for text which relies on Japanese characters. If a processor does not support this encoding, it must report a fatal error. (Also requires ability to process a moderately complex DTD.) (fatal) Recursive reference, "&TR-or-Rec;". (reference path: (top-level)-%TR-or-Rec;-%spec.dtd;-&spec.dtd;-%spec;-&TR-or-Rec;-&TR-or-Rec;)
4.3.3 [4,84] pr-xml-iso-2022-jp Test support for the ISO-2022-JP encoding, and for text which relies on Japanese characters. If a processor does not support this encoding, it must report a fatal error. (Also requires ability to process a moderately complex DTD.) (fatal) Recursive reference, "&TR-or-Rec;". (reference path: (top-level)-%TR-or-Rec;-%spec.dtd;-&spec.dtd;-%spec;-&TR-or-Rec;-&TR-or-Rec;)
4.3.3 [4,84] pr-xml-shift_jis Test support for the Shift_JIS encoding, and for text which relies on Japanese characters. If a processor does not support this encoding, it must report a fatal error. (Also requires ability to process a moderately complex DTD.) (fatal) Recursive reference, "&TR-or-Rec;". (reference path: (top-level)-%TR-or-Rec;-%spec.dtd;-&spec.dtd;-%spec;-&TR-or-Rec;-&TR-or-Rec;)
4.3.3 [4,84] weekly-euc-jp Test support for EUC-JP encoding, and XML names which contain Japanese characters. If a processor does not support this encoding, it must report a fatal error. (fatal) "</xml>" expected.
4.3.3 [4,84] weekly-iso-2022-jp Test support for ISO-2022-JP encoding, and XML names which contain Japanese characters. If a processor does not support this encoding, it must report a fatal error. (fatal) "</xml>" expected.
4.3.3 [4,84] weekly-shift_jis Test support for Shift_JIS encoding, and XML names which contain Japanese characters. If a processor does not support this encoding, it must report a fatal error. (fatal) "</xml>" expected.