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