XML Processor Conformance Report:
org.brownell.xml.aelfred2.SAXDriver

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 SAX2beta processors, the processing mode and entity handling values could be non-default values, if such a feature is supported by that processor. SAX1 processors were wrapped in an adapter, and those values were as reported to the test harness by its operator.

XML Processor AElfred 2
SAX2 Parser Class org.brownell.xml.aelfred2.SAXDriver
Processing Mode Non-Validating
General Entities included
Parameter Entities included

The test harness and execution environment was:

Test Run Date Sun Apr 23 13:48:12 PDT 2000
Harness and Version org.brownell.xml.conformance.Driver
($Date: 2000/04/23 11:49:46 $)
Java VM Info java 1.2.2 Sun Microsystems Inc.
Host OS Info Linux/i386 2.3.99-pre6
Suite of Testcases OASIS draft v1.0; with 5 Feb 2000 updates by David Brownell)

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) 1062
Passed Negative Tests (provisional) 488
Failed Tests (provisional) 10
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
Nothing to report!

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
Nothing to report!

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
Nothing to report!

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, 488 diagnostics must be examined to get an accurate evaluation of its negative test status. These have been reported as provisionally passed tests.

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

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.3, 4.2.2 [11] o-p11pass1 system literals may not contain URI fragments [diagnostic not provided]
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. [diagnostic not provided]
4.2.2 [75] uri01 SYSTEM ids may not have URI fragments [diagnostic not provided]
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) unsupported ASCII-derived encoding (found "EUC-JP") (expected "UTF-8, US-ASCII, or ISO-8859-1")
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) unsupported ASCII-derived encoding (found "ISO-2022-JP") (expected "UTF-8, US-ASCII, or ISO-8859-1")
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) unsupported ASCII-derived encoding (found "SHIFT_JIS") (expected "UTF-8, US-ASCII, or ISO-8859-1")
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) unsupported ASCII-derived encoding (found "EUC-JP") (expected "UTF-8, US-ASCII, or ISO-8859-1")
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) unsupported ASCII-derived encoding (found "ISO-2022-JP") (expected "UTF-8, US-ASCII, or ISO-8859-1")
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) unsupported ASCII-derived encoding (found "SHIFT_JIS") (expected "UTF-8, US-ASCII, or ISO-8859-1")