This document is the output of an XML test harness. It reports on the conformance of the following XML 1.0 processor configuration:
| XML Processor | Jaxp |
| Parser Class | org.apache.crimson.parser.XMLReaderImpl |
| Processing Mode | Non-Validating |
| General Entities | included |
| Parameter Entities | included |
The results were as reported through the parser's API to this particular test harness and execution environment:
| Test Run Date | Thu Jan 31 10:00:18 EST 2002 |
| Harness and Version | xml.testing.Driver ($Date: 2002/09/30 15:09:10 $) |
| Runtime Environment | Java HotSpot(TM) Client VM 1.3.1-b24 Sun Microsystems Inc. |
| Host OS Info | Windows 2000/x86 5.0 |
| Suite of Testcases | OASIS draft v1.0 Second Edition; with patches and errata updates from http://xmlconf.sourceforge.net/ |
An summary of test results follows. To know the actual test status, someone must examine the result of each passed negative test (and informative test) to make sure it failed for the right reason. That examination may cause the counts of failed tests to increase (and passed tests to decrease), changing a provisional "conforms" status to a "does not conform".
| Status | DOES NOT CONFORM |
| Total Passed Tests (provisional) | 2126 |
| Passed Negative Tests (provisional) | 1218 |
| Failed Tests (provisional) | 26 |
| 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. In some cases, test cases may need to be reclassified; this would affect results attributed to parsers. 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. Initial parenthesized comments typically come from the test harness.
Some such comments indicate the reporting category defined in the XML specification. Some low-fidelity processor APIs don't expose recoverable errors, which can make validation work awkward.
Other such comments may indicate other categories of conformance issue. For example, some errors relate to problematic implementation of SAX; and in exceptional cases, the harness can be forced to report a failure on some test.
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, rarely, 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.
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.8 | valid-sa-094 | Attribute defaults with a DTD have special parsing rules, different from other strings. That means that characters found there may look like an undefined parameter entity reference "within a markup declaration", but they aren't ... so they can't be violating the PEs in Internal Subset WFC. | FAIL (fatal) Parameter entity references must not appear within markup declarations in the internal DTD subset. [line 4] |
| 2.9 | not-sa02 | A non-standalone document is valid if declared as such. | (warning) Using original entity definition for "&internal;". [line 29] |
| 2.9 | not-sa04 | A non-standalone document is valid if declared as such. | (warning) Using original entity definition for "&internal;". [line 29] |
| 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) Using original entity definition for "&internal;". [line 29] |
| 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) Using original entity definition for "&internal;". [line 29] |
| 4.2 | valid-sa-086 | Tests whether entities may be declared more than once, with the first declaration being the binding one. | (warning) Using original entity definition for "&e;". [line 4] |
| 4.3.3 | bomtest-entx | Tests conformance with XML 2nd Ed erratum E22. XML entities may now begin with a UTF-8 BOM. (This uses an entity with both a BOM and an encoding decl.) | FAIL (fatal) XML declaration may only begin entities. [line 1] |
| 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) Using original entity definition for "&XML.version;". [line 116] |
| 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) Using original entity definition for "&XML.version;". [line 116] |
| 4.3.3 [4,84] | pr-xml-utf-8 | Test support for UTF-8 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.) | (warning) Using original entity definition for "&XML.version;". [line 116] |
| 4.3.3 [4,84] | weekly-little | Test support for little-endian UTF-16 encoding, and XML names which contain Japanese characters. | (warning) Using original entity definition for "<". [line 54] |
| 4.3.3 [4,84] | weekly-utf-16 | Test support for UTF-16 encoding, and XML names which contain Japanese characters. | (warning) Using original entity definition for "<". [line 54] |
| 4.3.3 [4,84] | weekly-utf-8 | Test support for UTF-8 encoding and XML names which contain Japanese characters. | (warning) Using original entity definition for "<". [line 54] |
The XML specification places requirements on the data which is reported by XML processors to applications. This data flows through the processor API ... or it is not available, so the processor is in those respects nonconformant. For example, SAX1 did not report external entities which were not included; but SAX2 does. 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.
At this writing, the OASIS output tests have several categories of known omissions (or weak output test coverage). These include:
Note that output tests automatically fail in cases where the processor failed to parse the (valid) input document used to generate the output data.
In some test harnessses, the output tests are unreliable because they can't directly compare the parser output against reference data. Such issues should be noted in the documentation for that harness.
Also, and not a bug, in some cases these diagnostics may seem like they say two equivalent results are not equal. The issue is that some differences, often those in reported whitespace, aren't easily visible in this report. HTML hides many such differences (because it normalizes whitespace before displaying it), and the method used to display the differing results may also mask some issues.
| Test ID | Diagnostic |
| ibm-valid-P28-ibm28v02.xml | Output byte 76 has the wrong value; actual 0x66 should instead be 0x69 |
| ibm-valid-P29-ibm29v01.xml | Output byte 76 has the wrong value; actual 0x66 should instead be 0x69 |
| ibm-valid-P29-ibm29v02.xml | Output byte 76 has the wrong value; actual 0x66 should instead be 0x69 |
| valid-sa-094 | (Input failed, no output available) |
| ibm-valid-P57-ibm57v01.xml | Output byte 38 has the wrong value; actual 0x66 should instead be 0x61 |
| ibm-valid-P58-ibm58v01.xml | Output byte 41 has the wrong value; actual 0x66 should instead be 0x62 |
| ibm-valid-P58-ibm58v02.xml | Output byte 43 has the wrong value; actual 0x66 should instead be 0x6d |
| ibm-valid-P70-ibm70v01.xml | Output byte 46 has the wrong value; actual 0x66 should instead be 0x4a |
| bomtest-ent | Output byte 5 has the wrong value; actual 0xef should instead be 0x74 |
| bomtest-ent2 | Output byte 8 has the wrong value; actual 0xef should instead be 0x3c |
| bomtest-entx | (Input failed, no output available) |
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 reported at the correct level.)
| Section and [Rules] | Test ID | Description | Diagnostic |
| 2.9 | inv-not-sa02 | Tests the Standalone Document Declaration VC, ensuring that attributes needing normalization cause a validity error. | (warning) Using original entity definition for "&internal;". [line 29] |
| 4.1 | ibm-invalid-P68-ibm68i01.xml | Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with the name "ge2" is referred in the file ibm68i01.dtd", but not declared. | FAIL (fatal) Reference to undefined entity "&ge2;". [line 3] |
| 4.1 | ibm-invalid-P68-ibm68i02.xml | Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with the name "ge1" is referred before declared in the file ibm68i01.dtd". | FAIL (fatal) Reference to undefined entity "&ge1;". [line 2] |
| 4.1 | ibm-invalid-P68-ibm68i03.xml | Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with the name "ge2" is referred in the file ibm68i03.ent", but not declared. | FAIL (fatal) Reference to undefined entity "&ge2;". [line 3] |
| 4.1 | ibm-invalid-P68-ibm68i04.xml | Tests invalid EntityRef which is against P68 VC: Entity Declared. The GE with the name "ge1" is referred before declared in the file ibm68i04.ent". | FAIL (fatal) Reference to undefined entity "&ge1;". [line 2] |
| 4.1 | ibm-invalid-P69-ibm69i01.xml | Tests invalid PEReference which is against P69 VC: Entity Declared. The Name "pe2" in the PEReference in the file ibm69i01.dtd does not match the Name of any declared PE. | (warning) Reference to undefined parameter entity "%pe2;". [line 5] |
| 4.1 | ibm-invalid-P69-ibm69i02.xml | Tests invalid PEReference which is against P69 VC: Entity Declared. The PE with the name "pe1" is referred before declared in the file ibm69i02.dtd | (warning) Reference to undefined parameter entity "%pe1;". [line 4] |
| 4.1 | ibm-invalid-P69-ibm69i03.xml | Tests invalid PEReference which is against P69 VC: Entity Declared. The Name "pe3" in the PEReference in the file ibm69i03.ent does not match the Name of any declared PE. | (warning) Reference to undefined parameter entity "%pe3;". [line 5] |
| 4.1 | ibm-invalid-P69-ibm69i04.xml | Tests invalid PEReference which is against P69 VC: Entity Declared. The PE with the name "pe2" is referred before declared in the file ibm69i04.ent. | (warning) Reference to undefined parameter entity "%pe2;". [line 4] |
| 4.1 | ibm-not-wf-P69-ibm69n05.xml | Based on E29 substantial source: minutes XML-Syntax 1999-02-24 E38 in XML 1.0 Errata, this WFC does not apply to P69, but the VC Entity declared still apply. Tests PEReference which is against P69 WFC: Entity Declared. The PE with the name "paaa" is referred before declared in the DTD. | (warning) Reference to undefined parameter entity "%paaa;". [line 6] |
| 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. | (warning) Reference to undefined parameter entity "%undefined;". [line 3] |
| 4.1 | not-wf-not-sa-005 | Tests the Entity Declared VC by referring to an undefined parameter entity within an external entity. | (warning) Reference to undefined parameter entity "%e;". [line 2] |
| 4.3.3 | bomtest-doc | Tests conformance with XML 2nd Ed erratum E22. XML documents may now begin with a UTF-8 BOM. (This document includes a BOM.) | FAIL (fatal) Document root element is missing. [line 1] |
| 4.3.3 | bomtest-docx | Tests conformance with XML 2nd Ed erratum E22. XML documents may now begin with a UTF-8 BOM. (This document includes both a BOM and an encoding decl.) | FAIL (fatal) Document root element is missing. [line 1] |
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, 1218 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 | ibm-not-wf-P01-ibm01n01.xml | Tests a document with no element. A well-formed document should have at lease one elements. | (fatal) Document root element is missing. [line 5] |
| 2.1 | ibm-not-wf-P01-ibm01n02.xml | Tests a document with wrong ordering of its prolog and element. The element occurs before the xml declaration and the DTD. | (fatal) XML declaration may only begin entities. [line 2] |
| 2.1 | ibm-not-wf-P01-ibm01n03.xml | Tests a document with wrong combination of misc and element. One PI occurs between two elements. | (fatal) Illegal character at end of document, <. [line 8] |
| 2.1 [1] | not-wf-sa-050 | Empty document, with no root element. | (fatal) Document root element is missing. [line 1] |
| 2.1 [1] | o-p01fail1 | S cannot occur before the prolog | (fatal) XML declaration may only begin entities. [line 2] |
| 2.1 [1] | o-p01fail2 | comments cannot occur before the prolog | (fatal) XML declaration may only begin entities. [line 1] |
| 2.1 [1] | o-p01fail3 | only one document element | (fatal) Illegal character at end of document, <. [line 1] |
| 2.1 [1] | o-p01fail4 | document element must be complete. | (fatal) End of entity not allowed; an end tag is missing. [line 1] |
| 2.2 | ibm-not-wf-P02-ibm02n01.xml | Tests a comment which contains an illegal Char: #x00 | (fatal) Illegal XML character: �. [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n02.xml | Tests a comment which contains an illegal Char: #x01 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n03.xml | Tests a comment which contains an illegal Char: #x02 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n04.xml | Tests a comment which contains an illegal Char: #x03 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n05.xml | Tests a comment which contains an illegal Char: #x04 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n06.xml | Tests a comment which contains an illegal Char: #x05 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n07.xml | Tests a comment which contains an illegal Char: #x06 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n08.xml | Tests a comment which contains an illegal Char: #x07 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n09.xml | Tests a comment which contains an illegal Char: #x08 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n10.xml | Tests a comment which contains an illegal Char: #x0B | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n11.xml | Tests a comment which contains an illegal Char: #x0C | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n12.xml | Tests a comment which contains an illegal Char: #x0E | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n13.xml | Tests a comment which contains an illegal Char: #x0F | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n14.xml | Tests a comment which contains an illegal Char: #x10 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n15.xml | Tests a comment which contains an illegal Char: #x11 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n16.xml | Tests a comment which contains an illegal Char: #x12 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n17.xml | Tests a comment which contains an illegal Char: #x13 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n18.xml | Tests a comment which contains an illegal Char: #x14 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n19.xml | Tests a comment which contains an illegal Char: #x15 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n20.xml | Tests a comment which contains an illegal Char: #x16 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n21.xml | Tests a comment which contains an illegal Char: #x17 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n22.xml | Tests a comment which contains an illegal Char: #x18 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n23.xml | Tests a comment which contains an illegal Char: #x19 | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n24.xml | Tests a comment which contains an illegal Char: #x1A | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n25.xml | Tests a comment which contains an illegal Char: #x1B | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n26.xml | Tests a comment which contains an illegal Char: #x1C | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n27.xml | Tests a comment which contains an illegal Char: #x1D | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n28.xml | Tests a comment which contains an illegal Char: #x1E | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n29.xml | Tests a comment which contains an illegal Char: #x1F | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n30.xml | Tests a comment which contains an illegal Char: #xD800 | (fatal) Malformed second part of surrogate pair:  . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n31.xml | Tests a comment which contains an illegal Char: #xDFFF | (fatal) Illegal XML character: �. [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n32.xml | Tests a comment which contains an illegal Char: #xFFFE | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-not-wf-P02-ibm02n33.xml | Tests a comment which contains an illegal Char: #xFFFF | (fatal) Illegal XML character: . [line 5] |
| 2.2 | ibm-valid-P02-ibm02v01.xml | Contains malformed UTF-8 characters. | (fatal) Character conversion error: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (line number may be too low). [line 1] |
| 2.2 [2] | not-wf-sa-030 | A form feed is not a legal XML character. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-031 | A form feed is not a legal XML character. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-032 | A form feed is not a legal XML character. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-033 | An ESC (octal 033) is not a legal XML character. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-034 | A form feed is not a legal XML character. | (fatal) Whitespace required before attributes. [line 1] |
| 2.2 [2] | not-wf-sa-142 | Character #x0000 is not legal anywhere in an XML document. | (fatal) Illegal XML character � [line 4] |
| 2.2 [2] | not-wf-sa-143 | Character #x001F is not legal anywhere in an XML document. | (fatal) Illegal XML character  [line 4] |
| 2.2 [2] | not-wf-sa-144 | Character #xFFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character  [line 4] |
| 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 � [line 4] |
| 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 � [line 4] |
| 2.2 [2] | not-wf-sa-166 | Character FFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-167 | Character FFFE is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-168 | An unpaired surrogate (D800) is not legal anywhere in an XML document. | (fatal) Illegal Unicode surrogate pair: � < [line 1] |
| 2.2 [2] | not-wf-sa-169 | An unpaired surrogate (DC00) is not legal anywhere in an XML document. | (fatal) Illegal Unicode surrogate pair: � < [line 1] |
| 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) Character conversion error: "UTF-8 encoding of character 0x001c0000 can't be converted to Unicode." (line number may be too low). [line 1] |
| 2.2 [2] | not-wf-sa-171 | Character FFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-172 | Character FFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-173 | Character FFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-174 | Character FFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | not-wf-sa-175 | Character FFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 3] |
| 2.2 [2] | not-wf-sa-177 | Character FFFF is not legal anywhere in an XML document. | (fatal) Illegal XML character: . [line 4] |
| 2.2 [2] | o-p02fail1 | Use of illegal character within XML document. | (fatal) Illegal XML character: �. [line 1] |
| 2.2 [2] | o-p02fail10 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail11 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail12 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail13 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail14 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail15 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail16 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail17 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail18 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail19 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail2 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail20 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail21 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail22 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail23 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail24 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail25 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail26 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail27 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail28 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail29 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail3 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail30 | Use of illegal character within XML document. | (fatal) Character conversion error: "Reversed byte-order mark" (line number may be too low). [line 1] |
| 2.2 [2] | o-p02fail31 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail4 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail5 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail6 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail7 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail8 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.2 [2] | o-p02fail9 | Use of illegal character within XML document. | (fatal) Illegal XML character: . [line 1] |
| 2.3 | ibm-not-wf-P03-ibm03n01.xml | Tests an end tag which contains an illegal space character #x3000 which follows the element name "book". | (fatal) Character conversion error: "Unconvertible UTF-8 character beginning with 0xa0" (line number may be too low). [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n01.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x21 | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n02.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x28 | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n03.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x29 | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n04.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2B | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n05.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2C | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n06.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2F | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n07.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3B | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n08.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3C | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n09.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3D | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n10.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3F | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n11.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5B | (fatal) Next character must be "]" terminating internal DTD subset . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n12.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5C | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n13.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5D | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n14.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5E | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n15.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x60 | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n16.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7B | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n17.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7C | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P04-ibm04n18.xml | Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7D | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.3 | ibm-not-wf-P05-ibm05n01.xml | Tests an element name which has an illegal first character. An illegal first character "." is followed by "A_name-starts_with.". | (fatal) Only whitespace allowed before name in <!DOCTYPE declaration. [line 1] |
| 2.3 | ibm-not-wf-P05-ibm05n02.xml | Tests an element name which has an illegal first character. An illegal first character "-" is followed by "A_name-starts_with-". | (fatal) Only whitespace allowed before name in <!DOCTYPE declaration. [line 1] |
| 2.3 | ibm-not-wf-P05-ibm05n03.xml | Tests an element name which has an illegal first character. An illegal first character "5" is followed by "A_name-starts_with_digit". | (fatal) Only whitespace allowed before name in <!DOCTYPE declaration. [line 1] |
| 2.3 | ibm-not-wf-P09-ibm09n01.xml | Tests an internal general entity with an invalid value. The entity "Fullname" contains "%". | (fatal) Next character must be ";" terminating reference to parameter entity "Man". [line 4] |
| 2.3 | ibm-not-wf-P09-ibm09n02.xml | Tests an internal general entity with an invalid value. The entity "Fullname" contains the ampersand character. | (fatal) Next character must be ";" terminating reference to entity "Man". [line 4] |
| 2.3 | ibm-not-wf-P09-ibm09n03.xml | Tests an internal general entity with an invalid value. The entity "Fullname" contains the double quote character in the middle. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "FullName". [line 4] |
| 2.3 | ibm-not-wf-P09-ibm09n04.xml | Tests an internal general entity with an invalid value. The closing bracket (double quote) is missing with the value of the entity "FullName". | (fatal) Premature end of input. [line 9] |
| 2.3 | ibm-not-wf-P10-ibm10n01.xml | Tests an attribute with an invalid value. The value of the attribute "first" contains the character "less than". | (fatal) Use "<" for "<" in attribute values. [line 14] |
| 2.3 | ibm-not-wf-P10-ibm10n02.xml | Tests an attribute with an invalid value. The value of the attribute "first" contains the character ampersand. | (fatal) Next character must be ";" terminating reference to entity "Man". [line 14] |
| 2.3 | ibm-not-wf-P10-ibm10n03.xml | Tests an attribute with an invalid value. The value of the attribute "first" contains the double quote character in the middle. | (fatal) Whitespace required before attributes. [line 14] |
| 2.3 | ibm-not-wf-P10-ibm10n04.xml | Tests an attribute with an invalid value. The closing bracket (double quote) is missing with The value of the attribute "first". | (fatal) Use "<" for "<" in attribute values. [line 14] |
| 2.3 | ibm-not-wf-P10-ibm10n05.xml | Tests an attribute with an invalid value. The value of the attribute "first" contains the character "less than". | (fatal) Use "<" for "<" in attribute values. [line 14] |
| 2.3 | ibm-not-wf-P10-ibm10n06.xml | Tests an attribute with an invalid value. The value of the attribute "first" contains the character ampersand. | (fatal) Next character must be ";" terminating reference to entity "Man". [line 14] |
| 2.3 | ibm-not-wf-P10-ibm10n07.xml | Tests an attribute with an invalid value. The value of the attribute "first" contains the double quote character in the middle. | (fatal) Whitespace required before attributes. [line 14] |
| 2.3 | ibm-not-wf-P10-ibm10n08.xml | Tests an attribute with an invalid value. The closing bracket (single quote) is missing with the value of the attribute "first". | (fatal) Use "<" for "<" in attribute values. [line 14] |
| 2.3 | ibm-not-wf-P11-ibm11n01.xml | Tests SystemLiteral. The systemLiteral for the element "student" has a double quote character in the middle. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 2] |
| 2.3 | ibm-not-wf-P11-ibm11n02.xml | Tests SystemLiteral. The systemLiteral for the element "student" has a single quote character in the middle. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 2] |
| 2.3 | ibm-not-wf-P11-ibm11n03.xml | Tests SystemLiteral. The closing bracket (double quote) is missing with the systemLiteral for the element "student". | (fatal) Premature end of input. [line 8] |
| 2.3 | ibm-not-wf-P11-ibm11n04.xml | Tests SystemLiteral. The closing bracket (single quote) is missing with the systemLiteral for the element "student". | (fatal) Premature end of input. [line 8] |
| 2.3 | ibm-not-wf-P12-ibm12n01.xml | Tests PubidLiteral. The closing bracket (double quote) is missing with the value of the PubidLiteral for the entity "info". | (fatal) Premature end of input. [line 18] |
| 2.3 | ibm-not-wf-P12-ibm12n02.xml | Tests PubidLiteral. The value of the PubidLiteral for the entity "info" has a single quote character in the middle.. | (fatal) Illegal character in PUBLIC identifier: "\". [line 4] |
| 2.3 | ibm-not-wf-P12-ibm12n03.xml | Tests PubidLiteral. The closing bracket (single quote) is missing with the value of the PubidLiteral for the entity "info". | (fatal) Premature end of input. [line 8] |
| 2.3 | ibm-not-wf-P13-ibm13n01.xml | Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character "{". | (fatal) Illegal character in PUBLIC identifier: "{". [line 3] |
| 2.3 | ibm-not-wf-P13-ibm13n02.xml | Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character "~". | (fatal) Illegal character in PUBLIC identifier: "~". [line 3] |
| 2.3 | ibm-not-wf-P13-ibm13n03.xml | Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character double quote in the middle. | (fatal) Character conversion error: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (line number may be too low). [line 1] |
| 2.3 [10] | not-wf-sa-012 | SGML-ism: attribute values must be quoted in all cases. | (fatal) Value must be quoted. [line 1] |
| 2.3 [10] | not-wf-sa-013 | The quotes on both ends of an attribute value must match. | (fatal) Use "<" for "<" in attribute values. [line 1] |
| 2.3 [10] | not-wf-sa-014 | Attribute values may not contain literal '<' characters. | (fatal) Use "<" for "<" in attribute values. [line 1] |
| 2.3 [10] | not-wf-sa-020 | Attribute values may not contain literal '&' characters except as part of an entity reference. | (fatal) Illegal character or entity reference syntax. [line 1] |
| 2.3 [10] | not-wf-sa-021 | Attribute values may not contain literal '&' characters except as part of an entity reference. | (fatal) Next character must be ";" terminating reference to entity "b". [line 1] |
| 2.3 [10] | not-wf-sa-088 | Attribute values are terminated by literal quote characters, and any entity expansion is done afterwards. | (fatal) Use "<" for "<" in attribute values. [line 6] |
| 2.3 [10] | not-wf-sa-090 | Attributes may not contain a literal "<" character; this one has one because of reference expansion. | (fatal) Use "<" for "<" in attribute values. [line 4] |
| 2.3 [10] | o-p10fail1 | attribute values exclude '<' | (fatal) Use "<" for "<" in attribute values. [line 1] |
| 2.3 [10] | o-p10fail2 | attribute values exclude '&' | (fatal) Illegal character or entity reference syntax. [line 1] |
| 2.3 [10] | o-p10fail3 | quote types must match | (fatal) Premature end of input. [line 2] |
| 2.3 [11] | o-p11fail1 | quote types must match | (fatal) Premature end of input. [line 8] |
| 2.3 [11] | o-p11fail2 | cannot contain delimiting quotes | (fatal) Next character must be ">" terminating <!NOTATION ...> declaration "not1". [line 5] |
| 2.3 [12] | o-p12fail1 | '"' excluded | (fatal) Illegal character in PUBLIC identifier: """. [line 5] |
| 2.3 [12] | o-p12fail2 | '\' excluded | (fatal) Illegal character in PUBLIC identifier: "\". [line 5] |
| 2.3 [12] | o-p12fail3 | entity references excluded | (fatal) Illegal character in PUBLIC identifier: "&". [line 6] |
| 2.3 [12] | o-p12fail4 | '>' excluded | (fatal) Illegal character in PUBLIC identifier: ">". [line 5] |
| 2.3 [12] | o-p12fail5 | '<' excluded | (fatal) Illegal character in PUBLIC identifier: "<". [line 5] |
| 2.3 [12] | o-p12fail6 | built-in entity refs excluded | (fatal) Illegal character in PUBLIC identifier: "&". [line 5] |
| 2.3 [12] | pubid01 | Illegal entity ref in public ID | (fatal) Illegal character in PUBLIC identifier: "&". [line 6] |
| 2.3 [12] | pubid02 | Illegal characters in public ID | (fatal) Illegal character in PUBLIC identifier: "<". [line 6] |
| 2.3 [12] | pubid03 | Illegal characters in public ID | (fatal) Illegal character in PUBLIC identifier: "[". [line 6] |
| 2.3 [12] | pubid04 | Illegal characters in public ID | (fatal) Illegal character in PUBLIC identifier: "{". [line 6] |
| 2.3 [12] | pubid05 | SGML-ism: public ID without system ID | (fatal) Missing whitespace before SYSTEM literal URI. [line 5] |
| 2.3 [13] | not-wf-sa-085 | Public IDs may not contain "[". | (fatal) Illegal character in PUBLIC identifier: "[". [line 1] |
| 2.3 [13] | not-wf-sa-086 | Public IDs may not contain "[". | (fatal) Illegal character in PUBLIC identifier: "[". [line 2] |
| 2.3 [13] | not-wf-sa-087 | Public IDs may not contain "[". | (fatal) Illegal character in PUBLIC identifier: "[". [line 2] |
| 2.3 [13] | o-p12fail7 | The public ID has a tab character, which is disallowed | (fatal) Illegal character in PUBLIC identifier: " ". [line 5] |
| 2.3 [3] | o-p03fail1 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail10 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail11 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail12 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail13 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail14 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail15 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail16 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail17 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail18 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail19 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail2 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail20 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail21 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail22 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail23 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail24 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail25 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail26 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail27 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail28 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail29 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail3 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail4 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail5 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail7 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail8 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [3] | o-p03fail9 | Use of illegal character within XML document. | (fatal) Document root element is missing. [line 1] |
| 2.3 [4] | not-wf-sa-002 | Names may not start with "."; it's not a Letter. | (fatal) The content beginning "<." is not legal markup. Perhaps the "." (e;) character should be a letter. [line 2] |
| 2.3 [4] | not-wf-sa-140 | Character '゚' is a CombiningChar, not a Letter, and so may not begin a name. | (fatal) The content beginning "<゚" is not legal markup. Perhaps the "゚" (ĵa;) character should be a letter. [line 4] |
| 2.3 [4] | o-p04fail1 | Name contains invalid character. | (fatal) Whitespace required before attributes. [line 1] |
| 2.3 [4] | o-p04fail2 | Name contains invalid character. | (fatal) Whitespace required before attributes. [line 1] |
| 2.3 [4] | o-p04fail3 | Name contains invalid character. | (fatal) Whitespace required before attributes. [line 1] |
| 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) Illegal character or entity reference syntax. [line 1] |
| 2.3 [5] | not-wf-sa-023 | Digits are not valid name start characters. | (fatal) Attribute names must not start with "1" characters. [line 1] |
| 2.3 [5] | not-wf-sa-024 | Digits are not valid name start characters. | (fatal) The content beginning "<1" is not legal markup. Perhaps the "1" () character should be a letter. [line 2] |
| 2.3 [5] | not-wf-sa-141 | Character #x0E5C is not legal in XML names. | (fatal) Whitespace required before attributes. [line 4] |
| 2.3 [5] | o-p05fail1 | a Name cannot start with a digit | (fatal) Document root element is missing. [line 1] |
| 2.3 [5] | o-p05fail2 | a Name cannot start with a '.' | (fatal) Document root element is missing. [line 1] |
| 2.3 [5] | o-p05fail3 | a Name cannot start with a "-" | (fatal) Document root element is missing. [line 1] |
| 2.3 [5] | o-p05fail4 | a Name cannot start with a CombiningChar | (fatal) Document root element is missing. [line 1] |
| 2.3 [5] | o-p05fail5 | a Name cannot start with an Extender | (fatal) Document root element is missing. [line 1] |
| 2.3 [9] | not-wf-sa-113 | Parameter entity values must use valid reference syntax; this reference is malformed. | (fatal) Illegal character or entity reference syntax. [line 2] |
| 2.3 [9] | not-wf-sa-114 | General entity values must use valid reference syntax; this reference is malformed. | (fatal) Illegal character or entity reference syntax. [line 2] |
| 2.3 [9] | not-wf-sa-159 | Uses '&' unquoted in an entity declaration, which is illegal syntax for an entity reference. | (fatal) Illegal character or entity reference syntax. [line 3] |
| 2.3 [9] | o-p09fail1 | EntityValue excludes '%' | (fatal) Illegal parameter entity reference syntax. [line 2] |
| 2.3 [9] | o-p09fail2 | EntityValue excludes '&' | (fatal) Illegal character or entity reference syntax. [line 2] |
| 2.3 [9] | o-p09fail3 | incomplete character reference | (fatal) Illegal decimal character reference. [line 4] |
| 2.3 [9] | o-p09fail4 | quote types must match | (fatal) Premature end of input. [line 6] |
| 2.3 [9] | o-p09fail5 | quote types must match | (fatal) Premature end of input. [line 6] |
| 2.4 | ibm-not-wf-P14-ibm14n01.xml | Tests CharData. The content of the element "student" contains the character "[[>". | (fatal) Character data cannot have "]]>". [line 9] |
| 2.4 | ibm-not-wf-P14-ibm14n02.xml | Tests CharData. The content of the element "student" contains the character "less than". | (fatal) Attribute names must not start with "<" characters. [line 9] |
| 2.4 | ibm-not-wf-P14-ibm14n03.xml | Tests CharData. The content of the element "student" contains the character ampersand. | (fatal) Next character must be ";" terminating reference to entity "Man". [line 9] |
| 2.4 [14] | not-wf-sa-025 | Text may not contain a literal ']]>' sequence. | (fatal) Character data cannot have "]]>". [line 1] |
| 2.4 [14] | not-wf-sa-026 | Text may not contain a literal ']]>' sequence. | (fatal) Character data cannot have "]]>". [line 1] |
| 2.4 [14] | not-wf-sa-029 | Text may not contain a literal ']]>' sequence. | (fatal) Character data cannot have "]]>". [line 1] |
| 2.4 [14] | o-p14fail1 | '<' excluded | (fatal) The content beginning "< " is not legal markup. Perhaps the " " () character should be a letter. [line 1] |
| 2.4 [14] | o-p14fail2 | '&' excluded | (fatal) Illegal character or entity reference syntax. [line 1] |
| 2.4 [14] | o-p14fail3 | "]]>" excluded | (fatal) Character data cannot have "]]>". [line 1] |
| 2.5 | ibm-not-wf-P15-ibm15n01.xml | Tests comment. The text of the second comment contains the character "-". | (fatal) Next character must be ">" terminating comment . [line 7] |
| 2.5 | ibm-not-wf-P15-ibm15n02.xml | Tests comment. The second comment has a wrong closing sequence "-(greater than)". | (fatal) End of entity while processing comment. [line 8] |
| 2.5 | ibm-not-wf-P15-ibm15n03.xml | Tests comment. The second comment has a wrong beginning sequence "(less than)!-". | (fatal) Document root element is missing. [line 7] |
| 2.5 | ibm-not-wf-P15-ibm15n04.xml | Tests comment. The closing sequence is missing with the second comment. | (fatal) End of entity while processing comment. [line 8] |
| 2.5 [15] | not-wf-sa-027 | Comments must be terminated with "-->". | (fatal) End of entity while processing comment. [line 4] |
| 2.5 [15] | o-p15fail1 | comments can't end in '-' | (fatal) Next character must be ">" terminating comment . [line 1] |
| 2.5 [15] | o-p15fail2 | one comment per comment (contrasted with SGML) | (fatal) Next character must be ">" terminating comment . [line 1] |
| 2.5 [15] | o-p15fail3 | can't include 2 or more adjacent '-'s | (fatal) Next character must be ">" terminating comment . [line 1] |
| 2.5 [15] | sgml03 | Comments may not contain "--" | (fatal) Next character must be ">" terminating comment . [line 3] |
| 2.5 [16] | not-wf-sa-006 | XML comments may not contain "--" | (fatal) Next character must be ">" terminating comment . [line 1] |
| 2.5 [16] | not-wf-sa-070 | XML comments may not contain "--" | (fatal) Next character must be ">" terminating comment . [line 1] |
| 2.6 | ibm-not-wf-P16-ibm16n01.xml | Tests PI. The content of the PI includes the sequence "(less than)?". | (fatal) Document root element is missing. [line 7] |
| 2.6 | ibm-not-wf-P16-ibm16n02.xml | Tests PI. The PITarget is missing in the PI. | (fatal) Processing instruction target is missing. [line 8] |
| 2.6 | ibm-not-wf-P16-ibm16n03.xml | Tests PI. The PI has a wrong closing sequence ">". | (fatal) End of input inside processing instruction. [line 9] |
| 2.6 | ibm-not-wf-P16-ibm16n04.xml | Tests PI. The closing sequence is missing in the PI. | (fatal) End of input inside processing instruction. [line 9] |
| 2.6 | ibm-not-wf-P17-ibm17n01.xml | Tests PITarget. The PITarget contains the string "XML". | (fatal) Illegal processing instruction target: "XML". [line 8] |
| 2.6 | ibm-not-wf-P17-ibm17n02.xml | Tests PITarget. The PITarget contains the string "xML". | (fatal) Illegal processing instruction target: "xML". [line 7] |
| 2.6 | ibm-not-wf-P17-ibm17n03.xml | Tests PITarget. The PITarget contains the string "xml". | (fatal) XML declaration may only begin entities. [line 7] |
| 2.6 | ibm-not-wf-P17-ibm17n04.xml | Tests PITarget. The PITarget contains the string "xmL". | (fatal) Illegal processing instruction target: "xmL". [line 7] |
| 2.6 [16] | not-wf-sa-003 | Processing Instruction target name is required. | (fatal) Processing instruction target is missing. [line 1] |
| 2.6 [16] | not-wf-sa-004 | SGML-ism: processing instructions end in '?>' not '>'. | (fatal) End of input inside processing instruction. [line 2] |
| 2.6 [16] | not-wf-sa-005 | Processing instructions end in '?>' not '?'. | (fatal) End of input inside processing instruction. [line 2] |
| 2.6 [16] | not-wf-sa-028 | Processing instructions must end with '?>'. | (fatal) End of input inside processing instruction. [line 5] |
| 2.6 [16] | o-p16fail1 | "xml" is an invalid PITarget | (fatal) XML declaration may only begin entities. [line 2] |
| 2.6 [16] | o-p16fail2 | a PITarget must be present | (fatal) Processing instruction target is missing. [line 1] |
| 2.6 [16] | pi | No space between PI target name and data | (fatal) Illegal processing instruction name, or missing whitespace. [line 4] |
| 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) Expected "encoding=...". [line 1] |
| 2.6 [17] | not-wf-not-sa-002 | Processing instruction target names may not be "XML" in any combination of cases. | (fatal) XML declaration may only begin entities. [line 4] |
| 2.6 [17] | not-wf-sa-157 | '<?xmL ...?>' is not a legal processing instruction target name. | (fatal) Illegal processing instruction target: "xmL". [line 2] |
| 2.7 | ibm-not-wf-P18-ibm18n01.xml | Tests CDSect. The CDStart is missing in the CDSect in the content of element "student". | (fatal) Character data cannot have "]]>". [line 7] |
| 2.7 | ibm-not-wf-P18-ibm18n02.xml | Tests CDSect. The CDEnd is missing in the CDSect in the content of element "student". | (fatal) EOF while parsing <![CDATA[ section. [line 7] |
| 2.7 | ibm-not-wf-P19-ibm19n01.xml | Tests CDStart. The CDStart contains a lower case string "cdata". | (fatal) Document root element is missing. [line 7] |
| 2.7 | ibm-not-wf-P19-ibm19n02.xml | Tests CDStart. The CDStart contains an extra character "[". | (fatal) Document root element is missing. [line 7] |
| 2.7 | ibm-not-wf-P19-ibm19n03.xml | Tests CDStart. The CDStart contains a wrong character "?". | (fatal) Processing instruction target is missing. [line 7] |
| 2.7 | ibm-not-wf-P20-ibm20n01.xml | Tests CDATA with an illegal sequence. The CDATA contains the string "[[>". | (fatal) Document root element is missing. [line 7] |
| 2.7 | ibm-not-wf-P21-ibm21n01.xml | Tests CDEnd. One "]" is missing in the CDEnd. | (fatal) Document root element is missing. [line 7] |
| 2.7 | ibm-not-wf-P21-ibm21n02.xml | Tests CDEnd. An extra "]" is placed in the CDEnd. | (fatal) Document root element is missing. [line 7] |
| 2.7 | ibm-not-wf-P21-ibm21n03.xml | Tests CDEnd. A wrong character ")" is placed in the CDEnd. | (fatal) Document root element is missing. [line 7] |
| 2.7 | not-wf-sa-105 | Invalid placement of CDATA section. | (fatal) Document root element is missing. [line 2] |
| 2.7 [18] | not-wf-sa-017 | CDATA sections need a terminating ']]>'. | (fatal) EOF while parsing <![CDATA[ section. [line 2] |
| 2.7 [18] | not-wf-sa-051 | CDATA is invalid at top level of document. | (fatal) Document root element is missing. [line 2] |
| 2.7 [18] | not-wf-sa-128 | Invalid CDATA syntax. | (fatal) Next character must be "(" starting content model for element "doc". [line 2] |
| 2.7 [18] | o-p18fail1 | no space before "CDATA" | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 1] |
| 2.7 [18] | o-p18fail2 | no space after "CDATA" | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 1] |
| 2.7 [18] | o-p18fail3 | CDSect's can't nest | (fatal) Character data cannot have "]]>". [line 4] |
| 2.7 [19] | not-wf-sa-018 | CDATA sections begin with a literal '<![CDATA[', no space. | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 1] |
| 2.7 [19] | not-wf-sa-108 | No space in '<![CDATA['. | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 2] |
| 2.7 [19] | not-wf-sa-112 | CDATA sections start '<![CDATA[', not '<!cdata['. | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 2] |
| 2.8 | ibm-not-wf-P22-ibm22n01.xml | Tests prolog with wrong field ordering. The XMLDecl occurs after the DTD. | (fatal) XML declaration may only begin entities. [line 4] |
| 2.8 | ibm-not-wf-P22-ibm22n02.xml | Tests prolog with wrong field ordering. The Misc (comment) occurs before the XMLDecl. | (fatal) XML declaration may only begin entities. [line 2] |
| 2.8 | ibm-not-wf-P22-ibm22n03.xml | Tests prolog with wrong field ordering. The XMLDecl occurs after the DTD and a comment. The other comment occurs before the DTD. | (fatal) XML declaration may only begin entities. [line 6] |
| 2.8 | ibm-not-wf-P23-ibm23n01.xml | Tests XMLDecl with a required field missing. The Versioninfo is missing in the XMLDecl. | (fatal) Expected "version=...". [line 1] |
| 2.8 | ibm-not-wf-P23-ibm23n02.xml | Tests XMLDecl with wrong field ordering. The VersionInfo occurs after the EncodingDecl. | (fatal) Expected "version=...". [line 1] |
| 2.8 | ibm-not-wf-P23-ibm23n03.xml | Tests XMLDecl with wrong field ordering. The VersionInfo occurs after the SDDecl and the SDDecl occurs after the VersionInfo. | (fatal) Expected "version=...". [line 1] |
| 2.8 | ibm-not-wf-P23-ibm23n04.xml | Tests XMLDecl with wrong key word. An upper case string "XML" is used as the key word in the XMLDecl. | (fatal) Illegal processing instruction target: "XML". [line 1] |
| 2.8 | ibm-not-wf-P23-ibm23n05.xml | Tests XMLDecl with a wrong closing sequence ">". | (fatal) Illegal character ">" (>) at end of XML Declaration. [line 1] |
| 2.8 | ibm-not-wf-P23-ibm23n06.xml | Tests XMLDecl with a wrong opening sequence "(less than)!". | (fatal) Document root element is missing. [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n01.xml | Tests VersionInfo with a required field missing. The VersionNum is missing in the VersionInfo in the XMLDecl. | (fatal) Expecting quoted value for attribute value version. [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n02.xml | Tests VersionInfo with a required field missing. The white space is missing between the key word "xml" and the VersionInfo in the XMLDecl. | (fatal) Expected "version=...". [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n03.xml | Tests VersionInfo with a required field missing. The "=" (equal sign) is missing between the key word "version" and the VersionNum. | (fatal) Next character must be "=" in XML Declaration . [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n04.xml | Tests VersionInfo with wrong field ordering. The VersionNum occurs before "=" and "version". | (fatal) Expected "version=...". [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n05.xml | Tests VersionInfo with wrong field ordering. The "=" occurs after "version" and the VersionNum. | (fatal) Next character must be "=" in XML Declaration . [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n06.xml | Tests VersionInfo with the wrong key word "Version". | (fatal) Expected "version=...". [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n07.xml | Tests VersionInfo with the wrong key word "versioN". | (fatal) Expected "version=...". [line 1] |
| 2.8 | ibm-not-wf-P24-ibm24n08.xml | Tests VersionInfo with mismatched quotes around the VersionNum. version = '1.0" is used as the VersionInfo. | (fatal) Premature end of input. [line 6] |
| 2.8 | ibm-not-wf-P24-ibm24n09.xml | Tests VersionInfo with mismatched quotes around the VersionNum. The closing bracket for the VersionNum is missing. | (fatal) Premature end of input. [line 6] |
| 2.8 | ibm-not-wf-P25-ibm25n01.xml | Tests eq with a wrong key word "==". | (fatal) Expecting quoted value for attribute value version. [line 1] |
| 2.8 | ibm-not-wf-P25-ibm25n02.xml | Tests eq with a wrong key word "eq". | (fatal) Next character must be "=" in XML Declaration . [line 1] |
| 2.8 | ibm-not-wf-P26-ibm26n01.xml | Tests VersionNum with an illegal character "#". | (fatal) Illegal XML version string "_#1.0". [line 1] |
| 2.8 | ibm-not-wf-P27-ibm27n01.xml | Tests type of Misc. An element declaration is used as a type of Misc After the element "animal". | (fatal) Illegal character at end of document, <. [line 6] |
| 2.8 | ibm-not-wf-P28-ibm28n01.xml | Tests doctypedecl with a required field missing. The Name "animal" is missing in the doctypedecl. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 2] |
| 2.8 | ibm-not-wf-P28-ibm28n02.xml | Tests doctypedecl with wrong field ordering. The Name "animal" occurs after the markup declarations inside the "[]". | (fatal) Only whitespace allowed before name in <!DOCTYPE declaration. [line 2] |
| 2.8 | ibm-not-wf-P28-ibm28n03.xml | Tests doctypedecl with wrong field ordering. The Name "animal" occurs after the markup declarations inside the "[]". | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 2] |
| 2.8 | ibm-not-wf-P28-ibm28n04.xml | Tests doctypedecl with general entity reference.The "(ampersand)generalE" occurs in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 5] |
| 2.8 | ibm-not-wf-P28-ibm28n05.xml | Tests doctypedecl with wrong key word. A wrong key word "DOCtYPE" occurs on line 2. | (fatal) Document root element is missing. [line 2] |
| 2.8 | ibm-not-wf-P28-ibm28n06.xml | Tests doctypedecl with mismatched brackets. The closing bracket "]" of the DTD is missing. | (fatal) Next character must be "]" terminating internal DTD subset . [line 4] |
| 2.8 | ibm-not-wf-P28-ibm28n07.xml | Tests doctypedecl with wrong bracket. The opening bracket "}" occurs in the DTD. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 2] |
| 2.8 | ibm-not-wf-P28-ibm28n08.xml | Tests doctypedecl with wrong opening sequence. The opening sequence "(less than)?DOCTYPE" occurs in the DTD. | (fatal) End of input inside processing instruction. [line 7] |
| 2.8 | ibm-not-wf-P29-ibm29n01.xml | Tests markupdecl with an illegal markup declaration. A XMLDecl occurs inside the DTD. | (fatal) XML declaration may only begin entities. [line 2] |
| 2.8 | ibm-not-wf-P29-ibm29n02.xml | Tests WFC "PEs in Internal Subset". A PE reference occurs inside an elementdecl in the DTD. | (fatal) Parameter entity references must not appear within markup declarations in the internal DTD subset. [line 5] |
| 2.8 | ibm-not-wf-P29-ibm29n03.xml | Tests WFC "PEs in Internal Subset". A PE reference occurs inside an ATTlistDecl in the DTD. | (fatal) Parameter entity references must not appear within markup declarations in the internal DTD subset. [line 5] |
| 2.8 | ibm-not-wf-P29-ibm29n04.xml | Tests WFC "PEs in Internal Subset". A PE reference occurs inside an EntityDecl in the DTD. | (fatal) Only external parameter entities may use "%parameterE;" in entity values. [line 5] |
| 2.8 | ibm-not-wf-P29-ibm29n05.xml | Tests WFC "PEs in Internal Subset". A PE reference occurs inside a PI in the DTD. | (fatal) End of input inside processing instruction. [line 9] |
| 2.8 | ibm-not-wf-P29-ibm29n06.xml | Tests WFC "PEs in Internal Subset". A PE reference occurs inside a comment in the DTD. | (fatal) End of entity while processing comment. [line 9] |
| 2.8 | ibm-not-wf-P29-ibm29n07.xml | Tests WFC "PEs in Internal Subset". A PE reference occurs inside a NotationDecl in the DTD. | (fatal) Parameter entity references must not appear within markup declarations in the internal DTD subset. [line 5] |
| 2.8 | ibm-not-wf-P30-ibm30n01.xml | Tests extSubset with wrong field ordering. In the file "ibm30n01.dtd", the TextDecl occurs after the extSubsetDecl (the element declaration). | (fatal) XML declaration may only begin entities. [line 2] |
| 2.8 | ibm-not-wf-P31-ibm31n01.xml | Tests extSubsetDecl with an illegal field. A general entity reference occurs in file "ibm31n01.dtd". | (fatal) External parameter entity "%[dtd];" has characters after markup. [line 4] |
| 2.8 | not-wf-sa-160 | Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. | (fatal) Only external parameter entities may use "%e;" in entity values. [line 4] |
| 2.8 | not-wf-sa-161 | Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. | (fatal) Parameter entity references must not appear within markup declarations in the internal DTD subset. [line 3] |
| 2.8 | not-wf-sa-162 | Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. | (fatal) Only external parameter entities may use "%e1;" in entity values. [line 4] |
| 2.8 | sgml02 | XML declaration must be at the very beginning of a document; it"s not a processing instruction | (fatal) XML declaration may only begin entities. [line 1] |
| 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: "XML". [line 1] |
| 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: "xmL". [line 1] |
| 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: "xMl". [line 2] |
| 2.8 [22] | not-wf-sa-147 | XML Declaration may not be preceded by whitespace. | (fatal) XML declaration may only begin entities. [line 2] |
| 2.8 [22] | not-wf-sa-148 | XML Declaration may not be preceded by comments or whitespace. | (fatal) XML declaration may only begin entities. [line 2] |
| 2.8 [22] | not-wf-sa-152 | XML declarations must include the "version=..." string. | (fatal) Expected "version=...". [line 1] |
| 2.8 [22] | o-p22fail1 | prolog must start with XML decl | (fatal) XML declaration may only begin entities. [line 2] |
| 2.8 [22] | o-p22fail2 | prolog must start with XML decl | (fatal) XML declaration may only begin entities. [line 4] |
| 2.8 [23] | not-wf-sa-095 | VersionInfo must come before EncodingDecl. | (fatal) Expected "version=...". [line 1] |
| 2.8 [23] | not-wf-sa-098 | Only one "version=..." string may appear in an XML declaration. | (fatal) Illegal character "v" (v) at end of XML Declaration. [line 1] |
| 2.8 [23] | not-wf-sa-099 | Only three pseudo-attributes are in the XML declaration, and "valid=..." is not one of them. | (fatal) Illegal character "v" (v) at end of XML Declaration. [line 1] |
| 2.8 [23] | o-p23fail1 | "xml" must be lower-case | (fatal) Illegal processing instruction target: "XML". [line 1] |
| 2.8 [23] | o-p23fail2 | VersionInfo must be supplied | (fatal) Expected "version=...". [line 1] |
| 2.8 [23] | o-p23fail3 | VersionInfo must come first | (fatal) Expected "version=...". [line 1] |
| 2.8 [23] | o-p23fail4 | SDDecl must come last | (fatal) Illegal character "e" (e) at end of XML Declaration. [line 1] |
| 2.8 [23] | o-p23fail5 | no SGML-type PIs | (fatal) Illegal character ">" (>) at end of XML Declaration. [line 1] |
| 2.8 [23] | o-p39fail4 | XML declarations must be correctly terminated | (fatal) Illegal character ">" (>) at end of XML Declaration. [line 1] |
| 2.8 [23] | o-p39fail5 | XML declarations must be correctly terminated | (fatal) Illegal character ">" (>) at end of XML Declaration. [line 1] |
| 2.8 [24] | not-wf-sa-094 | Prolog VERSION must be lowercase. | (fatal) Expected "version=...". [line 1] |
| 2.8 [24] | not-wf-sa-097 | Both quotes surrounding VersionNum must be the same. | (fatal) Illegal XML version string "1.0' encoding=". [line 1] |
| 2.8 [24] | o-p24fail1 | quote types must match | (fatal) Premature end of input. [line 3] |
| 2.8 [24] | o-p24fail2 | quote types must match | (fatal) Premature end of input. [line 3] |
| 2.8 [25] | o-p25fail1 | Comment is illegal in VersionInfo. | (fatal) Next character must be "=" in XML Declaration . [line 1] |
| 2.8 [26] | not-wf-sa-102 | Provides an illegal XML version number; spaces are illegal. | (fatal) Illegal XML version string "1.0 ". [line 1] |
| 2.8 [26] | o-p26fail1 | Illegal character in VersionNum. | (fatal) Illegal XML version string "1.0?". [line 1] |
| 2.8 [26] | o-p26fail2 | Illegal character in VersionNum. | (fatal) Illegal XML version string "1.0^". [line 1] |
| 2.8 [27] | not-wf-sa-036 | Text may not appear after the root element. | (fatal) Illegal character at end of document, I. [line 2] |
| 2.8 [27] | not-wf-sa-037 | Character references may not appear after the root element. | (fatal) Illegal character at end of document, &. [line 2] |
| 2.8 [27] | not-wf-sa-040 | Provides two document elements. | (fatal) Illegal character at end of document, <. [line 2] |
| 2.8 [27] | not-wf-sa-041 | Provides two document elements. | (fatal) Illegal character at end of document, <. [line 2] |
| 2.8 [27] | not-wf-sa-043 | Provides #PCDATA text after the document element. | (fatal) Illegal character at end of document, I. [line 2] |
| 2.8 [27] | not-wf-sa-044 | Provides two document elements. | (fatal) Illegal character at end of document, <. [line 1] |
| 2.8 [27] | not-wf-sa-048 | Provides a CDATA section after the roor element. | (fatal) Illegal character at end of document, <. [line 3] |
| 2.8 [27] | not-wf-sa-151 | XML declarations may not follow document content. | (fatal) XML declaration may only begin entities. [line 3] |
| 2.8 [27] | o-p27fail1 | References aren't allowed in Misc, even if they would resolve to valid Misc. | (fatal) Document root element is missing. [line 2] |
| 2.8 [28] | not-wf-sa-055 | Invalid Document Type Definition format. | (fatal) Next character must be "]" terminating internal DTD subset . [line 2] |
| 2.8 [28] | not-wf-sa-056 | Invalid Document Type Definition format - misplaced comment. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 1] |
| 2.8 [28] | not-wf-sa-107 | Invalid document type declaration. CDATA alone is invalid. | (fatal) Internal DTD subset must not have "<![..." constructs. [line 2] |
| 2.8 [28] | not-wf-sa-149 | XML Declaration may not be within a DTD. | (fatal) XML declaration may only begin entities. [line 3] |
| 2.8 [28] | o-p28fail1 | only declarations in DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 3] |
| 2.8 [29] | not-wf-sa-063 | Conditional sections may only appear in the external DTD subset. | (fatal) Internal DTD subset must not have "<![..." constructs. [line 2] |
| 2.8 [29] | o-p29fail1 | A processor must not pass unknown declaration types. | (fatal) Next character must be "]" terminating internal DTD subset . [line 3] |
| 2.8 [30] | o-p30fail1 | An XML declaration is not the same as a TextDecl | (fatal) Need "?>" to terminate XML declaration. [line 1] |
| 2.8 [31] | o-p31fail1 | external subset excludes doctypedecl | (fatal) External parameter entity "%[dtd];" has characters after markup. [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n01.xml | Tests SDDecl with a required field missing. The leading white space is missing with the SDDecl in the XMLDecl. | (fatal) Illegal character "s" (s) at end of XML Declaration. [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n02.xml | Tests SDDecl with a required field missing. The "=" sign is missing in the SDDecl in the XMLDecl. | (fatal) Next character must be "=" in XML Declaration . [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n03.xml | Tests SDDecl with wrong key word. The word "Standalone" occurs in the SDDecl in the XMLDecl. | (fatal) Illegal character "S" (S) at end of XML Declaration. [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n04.xml | Tests SDDecl with wrong key word. The word "Yes" occurs in the SDDecl in the XMLDecl. | (fatal) Standalone declaration must be "yes" or "no", not "Yes". [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n05.xml | Tests SDDecl with wrong key word. The word "YES" occurs in the SDDecl in the XMLDecl. | (fatal) Standalone declaration must be "yes" or "no", not "YES". [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n06.xml | Tests SDDecl with wrong key word. The word "No" occurs in the SDDecl in the XMLDecl. | (fatal) Standalone declaration must be "yes" or "no", not "No". [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n07.xml | Tests SDDecl with wrong key word. The word "NO" occurs in the SDDecl in the XMLDecl. | (fatal) Standalone declaration must be "yes" or "no", not "NO". [line 1] |
| 2.9 | ibm-not-wf-P32-ibm32n08.xml | Tests SDDecl with wrong field ordering. The "=" sign occurs after the key word "yes" in the SDDecl in the XMLDecl. | (fatal) Next character must be "=" in XML Declaration . [line 1] |
| 2.9 [32] | not-wf-sa-096 | Space is required before the standalone declaration. | (fatal) Illegal character "e" (e) at end of XML Declaration. [line 1] |
| 2.9 [32] | not-wf-sa-100 | Only "yes" and "no" are permitted as values of "standalone". | (fatal) Standalone declaration must be "yes" or "no", not "YES". [line 1] |
| 2.9 [32] | o-p32fail1 | quote types must match | (fatal) Premature end of input. [line 3] |
| 2.9 [32] | o-p32fail2 | quote types must match | (fatal) Premature end of input. [line 3] |
| 2.9 [32] | o-p32fail3 | initial S is required | (fatal) Illegal character "s" (s) at end of XML Declaration. [line 1] |
| 2.9 [32] | o-p32fail4 | quotes are required | (fatal) Expecting quoted value for attribute value standalone. [line 1] |
| 2.9 [32] | o-p32fail5 | yes or no must be lower case | (fatal) Standalone declaration must be "yes" or "no", not "YES". [line 1] |
| 3 | ibm-not-wf-P39-ibm39n01.xml | Tests element with a required field missing. The ETag is missing for the element "root". | (fatal) End of entity not allowed; an end tag is missing. [line 7] |
| 3 | ibm-not-wf-P39-ibm39n02.xml | Tests element with a required field missing. The STag is missing for the element "root". | (fatal) Document root element is missing. [line 5] |
| 3 | ibm-not-wf-P39-ibm39n03.xml | Tests element with required fields missing. Both the content and the ETag are missing in the element "root". | (fatal) End of entity not allowed; an end tag is missing. [line 7] |
| 3 | ibm-not-wf-P39-ibm39n04.xml | Tests element with required fields missing. Both the content and the STag are missing in the element "root". | (fatal) Document root element is missing. [line 5] |
| 3 | ibm-not-wf-P39-ibm39n05.xml | Tests element with wrong field ordering. The STag and the ETag are swapped in the element "root". | (fatal) Document root element is missing. [line 5] |
| 3 | ibm-not-wf-P39-ibm39n06.xml | Tests element with wrong field ordering. The content occurs after the ETag of the element "root". | (fatal) Illegal character at end of document, c. [line 5] |
| 3 | not-wf-sa-039 | Tests the Element Type Match WFC - end tag name must match start tag name. | (fatal) Next character must be ">" terminating element "a". [line 1] |
| 3 [39] | not-wf-sa-176 | Start tags must have matching end tags. | (fatal) End of entity not allowed; an end tag is missing. [line 5] |
| 3 [39] | o-p39fail1 | start-tag requires end-tag | (fatal) End of entity not allowed; an end tag is missing. [line 1] |
| 3 [39] | o-p39fail2 | end-tag requires start-tag | (fatal) Expected "</doc>" to terminate element starting on line 1. [line 1] |
| 3 [39] | o-p39fail3 | XML documents contain one or more elements | (fatal) Document root element is missing. [line 1] |
| 3 [39] | sgml01 | SGML-ism: omitted end tag for EMPTY content | (fatal) End of entity not allowed; an end tag is missing. [line 8] |
| 3.1 | ibm-not-wf-P40-ibm40n01.xml | Tests STag with a required field missing. The Name "root" is in the STag of the element "root". | (fatal) Whitespace required before attributes. [line 7] |
| 3.1 | ibm-not-wf-P40-ibm40n02.xml | Tests STag with a required field missing. The white space between the Name "root" and the attribute "attr1" is missing in the STag of the element "root". | (fatal) Whitespace required before attributes. [line 7] |
| 3.1 | ibm-not-wf-P40-ibm40n03.xml | Tests STag with wrong field ordering. The Name "root" occurs after the attribute "attr1" in the STag of the element "root". | (fatal) Whitespace required before attributes. [line 7] |
| 3.1 | ibm-not-wf-P40-ibm40n04.xml | Tests STag with a wrong opening sequence. The string "(less than)!" is used as the opening sequence for the STag of the element "root". | (fatal) Document root element is missing. [line 7] |
| 3.1 | ibm-not-wf-P40-ibm40n05.xml | Tests STag with duplicate attribute names. The attribute name "attr1" occurs twice in the STag of the element "root". | (fatal) Attribute "attr1" already appeared in this tag. [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n01.xml | Tests Attribute with a required field missing. The attribute name is missing in the Attribute in the STag of the element "root". | (fatal) Attribute names must not start with "=" characters. [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n02.xml | Tests Attribute with a required field missing. The "=" is missing between the attribute name and the attribute value in the Attribute in the STag of the element "root". | (fatal) Next character must be "=" after attribute name "attr1". [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n03.xml | Tests Attribute with a required field missing. The AttValue is missing in the Attribute in the STag of the element "root". | (fatal) Value must be quoted. [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n04.xml | Tests Attribute with a required field missing. The Name and the "=" are missing in the Attribute in the STag of the element "root". | (fatal) Attribute names must not start with """ characters. [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n05.xml | Tests Attribute with a required field missing. The "=" and the AttValue are missing in the Attribute in the STag of the element "root". | (fatal) Next character must be "=" after attribute name "attr1". [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n06.xml | Tests Attribute with a required field missing. The Name and the AttValue are missing in the Attribute in the STag of the element "root". | (fatal) Attribute names must not start with "=" characters. [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n07.xml | Tests Attribute with wrong field ordering. The "=" occurs after the Name and the AttValue in the Attribute in the STag of the element "root". | (fatal) Next character must be "=" after attribute name "attr1". [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n08.xml | Tests Attribute with wrong field ordering. The Name and the AttValue are swapped in the Attribute in the STag of the element "root". | (fatal) Attribute names must not start with """ characters. [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n09.xml | Tests Attribute with wrong field ordering. The "=" occurs before the Name and the AttValue in the Attribute in the STag of the element "root". | (fatal) Attribute names must not start with "=" characters. [line 7] |
| 3.1 | ibm-not-wf-P41-ibm41n10.xml | Tests Attribute against WFC "no external entity references". A direct references to the external entity "aExternal" is contained in the value of the attribute "attr1". | (fatal) Illegal reference to external entity "&aExternal;" in attribute. [line 8] |
| 3.1 | ibm-not-wf-P41-ibm41n11.xml | Tests Attribute against WFC "no external entity references". A indirect references to the external entity "aExternal" is contained in the value of the attribute "attr1". | (fatal) Illegal reference to external entity "&aExternal;" in attribute. [line 9] |
| 3.1 | ibm-not-wf-P41-ibm41n12.xml | Tests Attribute against WFC "no external entity references". A direct references to the external unparsed entity "aImage" is contained in the value of the attribute "attr1". | (fatal) Illegal reference to external entity "&aImage;" in attribute. [line 9] |
| 3.1 | ibm-not-wf-P41-ibm41n13.xml | Tests Attribute against WFC "No (less that) character in Attribute Values". The character "less than" is contained in the value of the attribute "attr1". | (fatal) Use "<" for "<" in attribute values. [line 8] |
| 3.1 | ibm-not-wf-P41-ibm41n14.xml | Tests Attribute against WFC "No (less than) in Attribute Values". The character "less than" is contained in the value of the attribute "attr1" through indirect internal entity reference. | (fatal) Use "<" for "<" in attribute values. [line 9] |
| 3.1 | ibm-not-wf-P42-ibm42n01.xml | Tests ETag with a required field missing. The Name is missing in the ETag of the element "root". | (fatal) Expected "</root>" to terminate element starting on line 6. [line 6] |
| 3.1 | ibm-not-wf-P42-ibm42n02.xml | Tests ETag with a wrong beginning sequence. The string "(less than)\" is used as a beginning sequence of the ETag of the element "root". | (fatal) The content beginning "<\" is not legal markup. Perhaps the "\" (c;) character should be a letter. [line 6] |
| 3.1 | ibm-not-wf-P42-ibm42n03.xml | Tests ETag with a wrong beginning sequence. The string "less than" is used as a beginning sequence of the ETag of the element "root". | (fatal) End of entity not allowed; an end tag is missing. [line 7] |
| 3.1 | ibm-not-wf-P42-ibm42n04.xml | Tests ETag with a wrong structure. An white space occurs between The beginning sequence and the Name of the ETag of the element "root". | (fatal) Expected "</root>" to terminate element starting on line 6. [line 6] |
| 3.1 | ibm-not-wf-P42-ibm42n05.xml | Tests ETag with a wrong structure. The ETag of the element "root" contains an Attribute (attr1="any"). | (fatal) Next character must be ">" terminating element "root". [line 6] |
| 3.1 | ibm-not-wf-P43-ibm43n01.xml | Tests element content with a wrong option. A NotationDecl is used as the content of the element "root". | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 8] |
| 3.1 | ibm-not-wf-P43-ibm43n02.xml | Tests element content with a wrong option. A elementdecl is used as the content of the element "root". | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 8] |
| 3.1 | ibm-not-wf-P43-ibm43n04.xml | Tests element content with a wrong option. An elementdecl is used as the content of the element "root". | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 8] |
| 3.1 | ibm-not-wf-P43-ibm43n05.xml | Tests element content with a wrong option. An AttlistDecl is used as the content of the element "root". | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 8] |
| 3.1 | ibm-not-wf-P44-ibm44n01.xml | Tests EmptyElemTag with a required field missing. The Name "root" is missing in the EmptyElemTag. | (fatal) Document root element is missing. [line 7] |
| 3.1 | ibm-not-wf-P44-ibm44n02.xml | Tests EmptyElemTag with wrong field ordering. The Attribute (attri1 = "any") occurs before the name of the element "root" in the EmptyElemTag. | (fatal) Whitespace required before attributes. [line 7] |
| 3.1 | ibm-not-wf-P44-ibm44n03.xml | Tests EmptyElemTag with wrong closing sequence. The string "\>" is used as the closing sequence in the EmptyElemtag of the element "root". | (fatal) Whitespace required before attributes. [line 7] |
| 3.1 | ibm-not-wf-P44-ibm44n04.xml | Tests EmptyElemTag which against the WFC "Unique Att Spec". The attribute name "attr1" occurs twice in the EmptyElemTag of the element "root". | (fatal) Attribute "attr1" already appeared in this tag. [line 7] |
| 3.1 | not-wf-sa-038 | Tests the "Unique Att Spec" WF constraint by providing multiple values for an attribute. | (fatal) Attribute "x" already appeared in this tag. [line 1] |
| 3.1 | not-wf-sa-081 | This tests the No External Entity References WFC, since the entity is referred to within an attribute. | (fatal) Illegal reference to external entity "&e;" in attribute. [line 4] |
| 3.1 | not-wf-sa-082 | This tests the No External Entity References WFC, since the entity is referred to within an attribute. | (fatal) Illegal reference to external entity "&e;" in attribute. [line 4] |
| 3.1 [40] | attlist10 | Whitespace required between attributes | (fatal) Whitespace required before attributes. [line 6] |
| 3.1 [40] | not-wf-sa-046 | This start (or empty element) tag was not terminated correctly. | (fatal) Next character must be ">" terminating element "a". [line 2] |
| 3.1 [40] | not-wf-sa-049 | Missing start tag | (fatal) Expected "</doc>" to terminate element starting on line 1. [line 3] |
| 3.1 [40] | o-p40fail1 | S is required between attributes | (fatal) Whitespace required before attributes. [line 1] |
| 3.1 [40] | o-p40fail2 | tags start with names, not nmtokens | (fatal) Document root element is missing. [line 1] |
| 3.1 [40] | o-p40fail3 | tags start with names, not nmtokens | (fatal) Document root element is missing. [line 1] |
| 3.1 [40] | o-p40fail4 | no space before name | (fatal) Document root element is missing. [line 1] |
| 3.1 [41] | not-wf-sa-001 | Attribute values must start with attribute names, not "?". | (fatal) Attribute names must not start with "?" characters. [line 3] |
| 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) Next character must be "=" after attribute name "a1". [line 1] |
| 3.1 [41] | not-wf-sa-015 | Attribute values need a value, not just an equals sign. | (fatal) Value must be quoted. [line 1] |
| 3.1 [41] | not-wf-sa-016 | Attribute values need an associated name. | (fatal) Attribute names must not start with """ characters. [line 1] |
| 3.1 [41] | not-wf-sa-178 | Invalid syntax matching double quote is missing. | (fatal) Use "<" for "<" in attribute values. [line 5] |
| 3.1 [41] | o-p41fail1 | quotes are required (contrast with SGML) | (fatal) Next character must be "(" starting content model for element "doc". [line 3] |
| 3.1 [41] | o-p41fail2 | attribute name is required (contrast with SGML) | (fatal) Next character must be "(" starting content model for element "doc". [line 3] |
| 3.1 [41] | o-p41fail3 | Eq required | (fatal) Next character must be "=" after attribute name "att". [line 1] |
| 3.1 [42] | element00 | EOF in middle of incomplete ETAG | (fatal) Expected "</root>" to terminate element starting on line 1. [line 3] |
| 3.1 [42] | element01 | EOF in middle of incomplete ETAG | (fatal) Next character must be ">" terminating element "root". [line 3] |
| 3.1 [42] | not-wf-sa-019 | End tags may not be abbreviated as '</>'. | (fatal) Expected "</doc>" to terminate element starting on line 1. [line 1] |
| 3.1 [42] | not-wf-sa-042 | Invalid End Tag | (fatal) Illegal character at end of document, <. [line 1] |
| 3.1 [42] | not-wf-sa-053 | End tag does not match start tag. | (fatal) Expected "</doc>" to terminate element starting on line 1. [line 1] |
| 3.1 [42] | o-p42fail1 | no space before name | (fatal) Expected "</doc>" to terminate element starting on line 1. [line 1] |
| 3.1 [42] | o-p42fail2 | cannot end with "/>" | (fatal) Next character must be ">" terminating element "doc". [line 1] |
| 3.1 [42] | o-p42fail3 | no NET (contrast with SGML) | (fatal) Next character must be ">" terminating element "doc". [line 1] |
| 3.1 [43] | element02 | Illegal markup (<%@ ... %>) | (fatal) The content beginning "<%" is not legal markup. Perhaps the "%" () character should be a letter. [line 3] |
| 3.1 [43] | element03 | Illegal markup (<% ... %>) | (fatal) The content beginning "<%" is not legal markup. Perhaps the "%" () character should be a letter. [line 3] |
| 3.1 [43] | element04 | Illegal markup (<!ELEMENT ... >) | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 3] |
| 3.1 [43] | not-wf-sa-035 | The '<' character is a markup delimiter and must start an element, CDATA section, PI, or comment. | (fatal) The content beginning "< " is not legal markup. Perhaps the " " () character should be a letter. [line 1] |
| 3.1 [43] | not-wf-sa-111 | Entiry reference must be in content of element not Start-tag. | (fatal) Attribute names must not start with "&" characters. [line 4] |
| 3.1 [43] | not-wf-sa-150 | XML declarations may not be within element content. | (fatal) XML declaration may only begin entities. [line 2] |
| 3.1 [43] | o-p43fail1 | no non-comment declarations | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 7] |
| 3.1 [43] | o-p43fail2 | no conditional sections | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 7] |
| 3.1 [43] | o-p43fail3 | no conditional sections | (fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter. [line 7] |
| 3.1 [44] | attlist11 | Whitespace required between attributes | (fatal) Whitespace required before attributes. [line 6] |
| 3.1 [44] | not-wf-sa-045 | Invalid Empty Element Tag | (fatal) Next character must be ">" terminating element "a". [line 2] |
| 3.1 [44] | not-wf-sa-047 | Invalid empty element tag invalid whitespace | (fatal) Next character must be ">" terminating element "a". [line 2] |
| 3.1 [44] | not-wf-sa-186 | Whitespace is required between attribute/value pairs. | (fatal) Whitespace required before attributes. [line 5] |
| 3.1 [44] | o-p44fail1 | Illegal space before Empty element tag. | (fatal) Document root element is missing. [line 1] |
| 3.1 [44] | o-p44fail2 | Illegal space after Empty element tag. | (fatal) Next character must be ">" terminating element "doc". [line 1] |
| 3.1 [44] | o-p44fail3 | Illegal comment in Empty element tag. | (fatal) Attribute names must not start with "-" characters. [line 1] |
| 3.1 [44] | o-p44fail4 | Whitespace required between attributes. | (fatal) Whitespace required before attributes. [line 1] |
| 3.1 [44] | o-p44fail5 | Duplicate attribute name is illegal. | (fatal) Attribute "att" already appeared in this tag. [line 1] |
| 3.2 | ibm-not-wf-P45-ibm45n01.xml | Tests elementdecl with a required field missing. The Name is missing in the second elementdecl in the DTD. | (fatal) Only whitespace allowed before name in <!ELEMENT declaration. [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n02.xml | Tests elementdecl with a required field missing. The white space is missing between "aEle" and "(#PCDATA)" in the second elementdecl in the DTD. | (fatal) Missing whitespace after element name declaration. [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n03.xml | Tests elementdecl with a required field missing. The contentspec is missing in the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "root". [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n04.xml | Tests elementdecl with a required field missing. The contentspec and the white space is missing in the second elementdecl in the DTD. | (fatal) Missing whitespace after element name declaration. [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n05.xml | Tests elementdecl with a required field missing. The Name, the white space, and the contentspec are missing in the second elementdecl in the DTD. | (fatal) Only whitespace allowed before name in <!ELEMENT declaration. [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n06.xml | Tests elementdecl with wrong field ordering. The Name occurs after the contentspec in the second elementdecl in the DTD. | (fatal) Only whitespace allowed before name in <!ELEMENT declaration. [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n07.xml | Tests elementdecl with wrong beginning sequence. The string "(less than)ELEMENT" is used as the beginning sequence in the second elementdecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n08.xml | Tests elementdecl with wrong key word. The string "Element" is used as the key word in the second elementdecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 5] |
| 3.2 | ibm-not-wf-P45-ibm45n09.xml | Tests elementdecl with wrong key word. The string "element" is used as the key word in the second elementdecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 5] |
| 3.2 | ibm-not-wf-P46-ibm46n01.xml | Tests contentspec with wrong key word. the string "empty" is used as the key word in the contentspec of the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2 | ibm-not-wf-P46-ibm46n02.xml | Tests contentspec with wrong key word. the string "Empty" is used as the key word in the contentspec of the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2 | ibm-not-wf-P46-ibm46n03.xml | Tests contentspec with wrong key word. the string "Any" is used as the key word in the contentspec of the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2 | ibm-not-wf-P46-ibm46n04.xml | Tests contentspec with wrong key word. the string "any" is used as the key word in the contentspec of the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2 | ibm-not-wf-P46-ibm46n05.xml | Tests contentspec with a wrong option. The string "#CDATA" is used as the contentspec in the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2 [45] | not-wf-sa-057 | This isn't SGML; comments can't exist in declarations. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "e". [line 2] |
| 3.2 [45] | not-wf-sa-129 | Invalid syntax for Element Type Declaration. | (fatal) Next character must be "(" starting content model for element "doc". [line 2] |
| 3.2 [45] | not-wf-sa-130 | Invalid syntax for Element Type Declaration. | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "+". [line 2] |
| 3.2 [45] | not-wf-sa-131 | Invalid syntax for Element Type Declaration. | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "-". [line 2] |
| 3.2 [45] | not-wf-sa-136 | Tag omission is invalid in XML. | (fatal) Next character must be "(" starting content model for element "doc". [line 2] |
| 3.2 [45] | not-wf-sa-137 | Space is required before a content model. | (fatal) Missing whitespace after element name declaration. [line 2] |
| 3.2 [45] | o-p45fail1 | ELEMENT must be upper case. | (fatal) Next character must be "]" terminating internal DTD subset . [line 3] |
| 3.2 [45] | o-p45fail2 | S before contentspec is required. | (fatal) Missing whitespace after element name declaration. [line 3] |
| 3.2 [45] | o-p45fail3 | only one content spec | (fatal) Only whitespace allowed before name in <!ELEMENT declaration. [line 3] |
| 3.2 [45] | o-p45fail4 | no comments in declarations (contrast with SGML) | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "-". [line 3] |
| 3.2 [45] | sgml05 | ELEMENT declarations apply to only one element, unlike SGML | (fatal) Only whitespace allowed before name in <!ELEMENT declaration. [line 8] |
| 3.2 [45] | sgml07 | SGML Tag minimization specifications are not allowed | (fatal) Next character must be "(" starting content model for element "root". [line 3] |
| 3.2 [45] | sgml08 | SGML Tag minimization specifications are not allowed | (fatal) Next character must be "(" starting content model for element "root". [line 3] |
| 3.2 [45] | sgml09 | SGML Content model exception specifications are not allowed | (fatal) ">" must terminate <!ELEMENT footnote ...> declaration, not "-". [line 4] |
| 3.2 [45] | sgml10 | SGML Content model exception specifications are not allowed | (fatal) ">" must terminate <!ELEMENT section ...> declaration, not "+". [line 3] |
| 3.2 [46] | o-p46fail1 | no parens on declared content | (fatal) No content model may contain "#". [line 4] |
| 3.2 [46] | o-p46fail2 | no inclusions (contrast with SGML) | (fatal) ">" must terminate <!ELEMENT a ...> declaration, not "+". [line 4] |
| 3.2 [46] | o-p46fail3 | no exclusions (contrast with SGML) | (fatal) ">" must terminate <!ELEMENT a ...> declaration, not "-". [line 4] |
| 3.2 [46] | o-p46fail4 | no space before occurrence | (fatal) ">" must terminate <!ELEMENT a ...> declaration, not "+". [line 4] |
| 3.2 [46] | o-p46fail5 | single group | (fatal) ">" must terminate <!ELEMENT a ...> declaration, not "(". [line 4] |
| 3.2 [46] | o-p46fail6 | can't be both declared and modeled | (fatal) ">" must terminate <!ELEMENT a ...> declaration, not "(". [line 4] |
| 3.2 [46] | sgml11 | CDATA is not a valid content model spec | (fatal) Next character must be "(" starting content model for element "ROOT". [line 3] |
| 3.2 [46] | sgml12 | RCDATA is not a valid content model spec | (fatal) Next character must be "(" starting content model for element "ROOT". [line 3] |
| 3.2.1 | ibm-not-wf-P47-ibm47n01.xml | Tests children with a required field missing. The "+" is used as the choice or seq field in the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2.1 | ibm-not-wf-P47-ibm47n02.xml | Tests children with a required field missing. The "*" is used as the choice or seq field in the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2.1 | ibm-not-wf-P47-ibm47n03.xml | Tests children with a required field missing. The "?" is used as the choice or seq field in the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 5] |
| 3.2.1 | ibm-not-wf-P47-ibm47n04.xml | Tests children with wrong field ordering. The "*" occurs before the seq field (a,a) in the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 6] |
| 3.2.1 | ibm-not-wf-P47-ibm47n05.xml | Tests children with wrong field ordering. The "+" occurs before the choice field (a|a) in the second elementdecl in the DTD. | (fatal) Next character must be "(" starting content model for element "aElement". [line 7] |
| 3.2.1 | ibm-not-wf-P47-ibm47n06.xml | Tests children with wrong key word. The "^" occurs after the seq field in the second elementdecl in the DTD. | (fatal) ">" must terminate <!ELEMENT aElement ...> declaration, not "^". [line 6] |
| 3.2.1 | ibm-not-wf-P48-ibm48n01.xml | Tests cp with a required fields missing. The field Name|choice|seq is missing in the second cp in the choice field in the third elementdecl in the DTD. | (fatal) Choice content model must not contain "+". [line 6] |
| 3.2.1 | ibm-not-wf-P48-ibm48n02.xml | Tests cp with a required fields missing. The field Name|choice|seq is missing in the cp in the third elementdecl in the DTD. | (fatal) No content model may contain "*". [line 6] |
| 3.2.1 | ibm-not-wf-P48-ibm48n03.xml | Tests cp with a required fields missing. The field Name|choice|seq is missing in the first cp in the choice field in the third elementdecl in the DTD. | (fatal) No content model may contain "?". [line 6] |
| 3.2.1 | ibm-not-wf-P48-ibm48n04.xml | Tests cp with wrong field ordering. The "+" occurs before the seq (a,a) in the first cp in the choice field in the third elementdecl in the DTD. | (fatal) No content model may contain "+". [line 6] |
| 3.2.1 | ibm-not-wf-P48-ibm48n05.xml | Tests cp with wrong field ordering. The "*" occurs before the choice (a|b) in the first cp in the seq field in the third elementdecl in the DTD. | (fatal) No content model may contain "*". [line 7] |
| 3.2.1 | ibm-not-wf-P48-ibm48n06.xml | Tests cp with wrong field ordering. The "?" occurs before the Name "a" in the second cp in the seq field in the third elementdecl in the DTD. | (fatal) Sequence content model must not contain "?". [line 6] |
| 3.2.1 | ibm-not-wf-P48-ibm48n07.xml | Tests cp with wrong key word. The "^" occurs after the Name "a" in the first cp in the choice field in the third elementdecl in the DTD. | (fatal) Choice content model must not contain "^". [line 6] |
| 3.2.1 | ibm-not-wf-P49-ibm49n01.xml | Tests choice with a required field missing. The two cps are missing in the choice field in the third elementdecl in the DTD. | (fatal) No content model may contain "|". [line 6] |
| 3.2.1 | ibm-not-wf-P49-ibm49n02.xml | Tests choice with a required field missing. The third cp is missing in the choice field in the fourth elementdecl in the DTD. | FAIL [Document not WF; no error reported] |
| 3.2.1 | ibm-not-wf-P49-ibm49n03.xml | Tests choice with a wrong separator. The "!" is used as the separator in the choice field in the fourth elementdecl in the DTD. | (fatal) Choice content model must not contain "!". [line 7] |
| 3.2.1 | ibm-not-wf-P49-ibm49n04.xml | Tests choice with a required field missing. The separator "|" is missing in the choice field (a b)+ in the fourth elementdecl in the DTD. | FAIL [Document not WF; no error reported] |
| 3.2.1 | ibm-not-wf-P49-ibm49n05.xml | Tests choice with an extra separator. An extra "|" occurs between a and b in the choice field in the fourth elementdecl in the DTD. | (fatal) Choice content model must not contain "|". [line 7] |
| 3.2.1 | ibm-not-wf-P49-ibm49n06.xml | Tests choice with a required field missing. The closing bracket ")" is missing in the choice field (a |b * in the fourth elementdecl in the DTD. | (fatal) Need right parenthesis or "|" in content model, not "*". [line 7] |
| 3.2.1 | ibm-not-wf-P50-ibm50n01.xml | Tests seq with a required field missing. The two cps are missing in the seq field in the fourth elementdecl in the DTD. | (fatal) No content model may contain ",". [line 7] |
| 3.2.1 | ibm-not-wf-P50-ibm50n02.xml | Tests seq with a required field missing. The third cp is missing in the seq field in the fourth elementdecl in the DTD. | FAIL [Document not WF; no error reported] |
| 3.2.1 | ibm-not-wf-P50-ibm50n03.xml | Tests seq with a wrong separator. The "|" is used as the separator between a and b in the seq field in the fourth elementdecl in the DTD. | (fatal) Need right parenthesis or "," in content model, not "|". [line 7] |
| 3.2.1 | ibm-not-wf-P50-ibm50n04.xml | Tests seq with a wrong separator. The "." is used as the separator between a and b in the seq field in the fourth elementdecl in the DTD. | (fatal) Choice content model must not contain ".". [line 7] |
| 3.2.1 | ibm-not-wf-P50-ibm50n05.xml | Tests seq with an extra separator. An extra "," occurs between (a|b) and a in the seq field in the fourth elementdecl in the DTD. | (fatal) Sequence content model must not contain ",". [line 7] |
| 3.2.1 | ibm-not-wf-P50-ibm50n06.xml | Tests seq with a required field missing. The separator between (a|b) and (b|a) is missing in the seq field in the fourth elementdecl in the DTD. | FAIL [Document not WF; no error reported] |
| 3.2.1 | ibm-not-wf-P50-ibm50n07.xml | Tests seq with wrong closing bracket. The "]" is used as the closing bracket in the seq field in the fourth elementdecl in the DTD. | (fatal) Need right parenthesis or "," in content model, not "]". [line 7] |
| 3.2.1 | not-wf-sa-133 | Illegal whitespace before optional character causes syntax error. | (fatal) Choice content model must not contain "*". [line 2] |
| 3.2.1 | not-wf-sa-134 | Illegal whitespace before optional character causes syntax error. | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "*". [line 2] |
| 3.2.1 [46] | not-wf-sa-139 | The element-content model should not be empty. | (fatal) No content model may contain ")". [line 2] |
| 3.2.1 [47] | not-wf-sa-122 | Invalid syntax mixed connectors are used. | (fatal) Need right parenthesis or "," in content model, not "|". [line 2] |
| 3.2.1 [47] | not-wf-sa-135 | Invalid character used as connector. | (fatal) Choice content model must not contain "&". [line 2] |
| 3.2.1 [47] | o-p47fail1 | Invalid operator '|' must match previous operator ',' | (fatal) Need right parenthesis or "," in content model, not "|". [line 4] |
| 3.2.1 [47] | o-p47fail2 | Illegal character '-' in Element-content model | (fatal) ">" must terminate <!ELEMENT a ...> declaration, not "-". [line 4] |
| 3.2.1 [47] | o-p47fail3 | Optional character must follow a name or list | (fatal) Next character must be "(" starting content model for element "a". [line 4] |
| 3.2.1 [47] | o-p47fail4 | Illegal space before optional character | (fatal) ">" must terminate <!ELEMENT a ...> declaration, not "?". [line 4] |
| 3.2.1 [47] | sgml13 | SGML Unordered content models not allowed | (fatal) Choice content model must not contain "&". [line 3] |
| 3.2.1 [48] | content01 | No whitespace before "?" in content model | (fatal) Choice content model must not contain "?". [line 3] |
| 3.2.1 [48] | content02 | No whitespace before "*" in content model | (fatal) Choice content model must not contain "*". [line 3] |
| 3.2.1 [48] | content03 | No whitespace before "+" in content model | (fatal) Choice content model must not contain "+". [line 3] |
| 3.2.1 [48] | not-wf-sa-123 | Invalid syntax mismatched parenthesis. | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not ")". [line 2] |
| 3.2.1 [48] | not-wf-sa-138 | Invalid syntax for content particle. | (fatal) Choice content model must not contain "?". [line 2] |
| 3.2.1 [48] | o-p48fail1 | Illegal space before optional character | (fatal) Choice content model must not contain "*". [line 4] |
| 3.2.1 [48] | o-p48fail2 | Illegal space before optional character | (fatal) Choice content model must not contain "+". [line 4] |
| 3.2.1 [49] | o-p49fail1 | connectors must match | (fatal) Need right parenthesis or "|" in content model, not ",". [line 4] |
| 3.2.1 [50] | not-wf-sa-132 | Invalid syntax mixed connectors used. | (fatal) Need right parenthesis or "," in content model, not "|". [line 2] |
| 3.2.1 [50] | o-p50fail1 | connectors must match | (fatal) Need right parenthesis or "," in content model, not "|". [line 4] |
| 3.2.1 [55] | nwf-dtd00 | Comma mandatory in content model | (fatal) Need right parenthesis or "," in content model, not "f". [line 2] |
| 3.2.1 [55] | nwf-dtd01 | Can't mix comma and vertical bar in content models | (fatal) Need right parenthesis or "," in content model, not "|". [line 2] |
| 3.2.2 | ibm-not-wf-P51-ibm51n01.xml | Tests Mixed with a wrong key word. The string "#pcdata" is used as the key word in the Mixed field in the fourth elementdecl in the DTD. | (fatal) No content model may contain "#". [line 7] |
| 3.2.2 | ibm-not-wf-P51-ibm51n02.xml | Tests Mixed with wrong field ordering. The field #PCDATA does not occur as the first component in the Mixed field in the fourth elementdecl in the DTD. | (fatal) Choice content model must not contain "#". [line 7] |
| 3.2.2 | ibm-not-wf-P51-ibm51n03.xml | Tests Mixed with a separator missing. The separator "|" is missing in between #PCDATA and a in the Mixed field in the fourth elementdecl in the DTD. | (fatal) Mixed content model for "aElement" must end with ")*", not "a". [line 7] |
| 3.2.2 | ibm-not-wf-P51-ibm51n04.xml | Tests Mixed with a wrong key word. The string "#CDATA" is used as the key word in the Mixed field in the fourth elementdecl in the DTD. | (fatal) No content model may contain "#". [line 7] |
| 3.2.2 | ibm-not-wf-P51-ibm51n05.xml | Tests Mixed with a required field missing. The "*" is missing after the ")" in the Mixed field in the fourth elementdecl in the DTD. | (fatal) Mixed content model for "aElement" must end with ")*", not ")". [line 7] |
| 3.2.2 | ibm-not-wf-P51-ibm51n06.xml | Tests Mixed with wrong closing bracket. The "]" is used as the closing bracket in the Mixed field in the fourth elementdecl in the DTD. | (fatal) Mixed content model for "aElement" must end with ")*", not "]". [line 7] |
| 3.2.2 | ibm-not-wf-P51-ibm51n07.xml | Tests Mixed with a required field missing. The closing bracket ")" is missing after (#PCDATA in the Mixed field in the fourth elementdecl in the DTD. | (fatal) Mixed content model for "aElement" must end with ")*", not "*". [line 7] |
| 3.2.2 [51] | not-wf-sa-124 | Invalid format of Mixed-content declaration. | (fatal) Choice content model must not contain "#". [line 2] |
| 3.2.2 [51] | not-wf-sa-125 | Invalid syntax extra set of parenthesis not necessary. | (fatal) No content model may contain "#". [line 2] |
| 3.2.2 [51] | not-wf-sa-126 | Invalid syntax Mixed-content must be defined as zero or more. | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "+". [line 2] |
| 3.2.2 [51] | not-wf-sa-127 | Invalid syntax Mixed-content must be defined as zero or more. | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "?". [line 2] |
| 3.2.2 [51] | not-wf-sa-183 | Mixed content declarations may not include content particles. | (fatal) Mixed content model for "doc" must end with ")*", not "*". [line 2] |
| 3.2.2 [51] | not-wf-sa-184 | In mixed content models, element names must not be parenthesized. | (fatal) Illegal mixed content model for "doc", next char = (. [line 2] |
| 3.2.2 [51] | o-p51fail1 | occurrence on #PCDATA group must be * | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "?". [line 3] |
| 3.2.2 [51] | o-p51fail2 | occurrence on #PCDATA group must be * | (fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "+". [line 3] |
| 3.2.2 [51] | o-p51fail3 | #PCDATA must come first | (fatal) Choice content model must not contain "#". [line 4] |
| 3.2.2 [51] | o-p51fail4 | occurrence on #PCDATA group must be * | (fatal) Mixed content model for "a" must end with ")*", not ")". [line 4] |
| 3.2.2 [51] | o-p51fail5 | only '|' connectors | (fatal) Mixed content model for "a" must end with ")*", not ",". [line 4] |
| 3.2.2 [51] | o-p51fail6 | Only '|' connectors and occurrence on #PCDATA group must be * | (fatal) Mixed content model for "a" must end with ")*", not ",". [line 4] |
| 3.2.2 [51] | o-p51fail7 | no nested groups | (fatal) Illegal mixed content model for "a", next char = (. [line 4] |
| 3.3 | ibm-not-wf-P52-ibm52n01.xml | Tests AttlistDecl with a required field missing. The Name is missing in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "#") for attribute "CDATA". [line 6] |
| 3.3 | ibm-not-wf-P52-ibm52n02.xml | Tests AttlistDecl with a required field missing. The white space is missing between the beginning sequence and the name in the AttlistDecl in the DTD. | (fatal) Missing whitespace before name in <!ATTLIST declaration. [line 6] |
| 3.3 | ibm-not-wf-P52-ibm52n03.xml | Tests AttlistDecl with wrong field ordering. The Name "a" occurs after the first AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with """) for attribute "CDATA". [line 6] |
| 3.3 | ibm-not-wf-P52-ibm52n04.xml | Tests AttlistDecl with wrong key word. The string "Attlist" is used as the key word in the beginning sequence in the AttlistDecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 6] |
| 3.3 | ibm-not-wf-P52-ibm52n05.xml | Tests AttlistDecl with a required field missing. The closing bracket "greater than" is missing in the AttlistDecl in the DTD. | (fatal) Either an attribute declaration or ">" is expected, not "<". [line 7] |
| 3.3 | ibm-not-wf-P52-ibm52n06.xml | Tests AttlistDecl with wrong beginning sequence. The string "(less than)ATTLIST" is used as the beginning sequence in the AttlistDecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n01.xml | Tests AttDef with a required field missing. The DefaultDecl is missing in the AttDef for the name "attr1" in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n02.xml | Tests AttDef with a required field missing. The white space is missing between (abc|def) and "def" in the AttDef in the AttlistDecl in the DTD. | (fatal) Missing whitespace between attribute type and default value. [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n03.xml | Tests AttDef with a required field missing. The AttType is missing for "attr1" in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "#") for attribute "attr1". [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n04.xml | Tests AttDef with a required field missing. The white space is missing between "attr1" and (abc|def) in the AttDef in the AttlistDecl in the DTD. | (fatal) Missing whitespace between attribute name and type. [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n05.xml | Tests AttDef with a required field missing. The Name is missing in the AttDef in the AttlistDecl in the DTD. | (fatal) Either an attribute declaration or ">" is expected, not "(". [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n06.xml | Tests AttDef with a required field missing. The white space before the name "attr2" is missing in the AttDef in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n07.xml | Tests AttDef with wrong field ordering. The Name "attr1" occurs after the AttType in the AttDef in the AttlistDecl in the DTD. | (fatal) Either an attribute declaration or ">" is expected, not "(". [line 6] |
| 3.3 | ibm-not-wf-P53-ibm53n08.xml | Tests AttDef with wrong field ordering. The Name "attr1" occurs after the AttType and "default" occurs before the AttType in the AttDef in the AttlistDecl in the DTD. | (fatal) Either an attribute declaration or ">" is expected, not """. [line 6] |
| 3.3 [52] | not-wf-sa-066 | Required whitespace is missing. | (fatal) Missing whitespace between attribute type and default value. [line 3] |
| 3.3 [52] | not-wf-sa-158 | SGML-ism: "#NOTATION gif" can't have attributes. | (fatal) Only whitespace allowed before name in <!ATTLIST declaration. [line 4] |
| 3.3 [52] | o-p52fail1 | A name is required | (fatal) Only whitespace allowed before name in <!ATTLIST declaration. [line 4] |
| 3.3 [52] | o-p52fail2 | A name is required | (fatal) Missing whitespace before name in <!ATTLIST declaration. [line 4] |
| 3.3 [52] | sgml04 | ATTLIST declarations apply to only one element, unlike SGML | (fatal) Only whitespace allowed before name in <!ATTLIST declaration. [line 7] |
| 3.3 [52] | sgml06 | ATTLIST declarations are never global, unlike in SGML | (fatal) Only whitespace allowed before name in <!ATTLIST declaration. [line 6] |
| 3.3 [53] | not-wf-sa-064 | Space is required between attribute type and default values in <!ATTLIST...> declarations. | (fatal) Missing whitespace between attribute type and default value. [line 3] |
| 3.3 [53] | not-wf-sa-065 | Space is required between attribute name and type in <!ATTLIST...> declarations. | (fatal) Missing whitespace between attribute name and type. [line 3] |
| 3.3 [53] | not-wf-sa-067 | Space is required between attribute type and default values in <!ATTLIST...> declarations. | (fatal) Missing whitespace between attribute type and default value. [line 3] |
| 3.3 [53] | o-p53fail1 | S is required before default | (fatal) Missing whitespace between attribute type and default value. [line 4] |
| 3.3 [53] | o-p53fail2 | S is required before type | (fatal) Missing whitespace between attribute name and type. [line 4] |
| 3.3 [53] | o-p53fail3 | type is required | (fatal) Illegal type (starts with "#") for attribute "att". [line 4] |
| 3.3 [53] | o-p53fail4 | default is required | (fatal) Missing whitespace between attribute type and default value. [line 4] |
| 3.3 [53] | o-p53fail5 | name is requried | (fatal) Either an attribute declaration or ">" is expected, not "(". [line 4] |
| 3.3.1 | ibm-not-wf-P54-ibm54n01.xml | Tests AttType with a wrong option. The string "BOGUSATTR" is used as the AttType in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "B") for attribute "att". [line 7] |
| 3.3.1 | ibm-not-wf-P54-ibm54n02.xml | Tests AttType with a wrong option. The string "PCDATA" is used as the AttType in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "P") for attribute "att". [line 7] |
| 3.3.1 | ibm-not-wf-P55-ibm55n01.xml | Tests StringType with a wrong key word. The lower case string "cdata" is used as the StringType in the AttType in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "c") for attribute "att". [line 7] |
| 3.3.1 | ibm-not-wf-P55-ibm55n02.xml | Tests StringType with a wrong key word. The string "#CDATA" is used as the StringType in the AttType in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "#") for attribute "att". [line 7] |
| 3.3.1 | ibm-not-wf-P55-ibm55n03.xml | Tests StringType with a wrong key word. The string "CData" is used as the StringType in the AttType in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "C") for attribute "att". [line 7] |
| 3.3.1 | ibm-not-wf-P56-ibm56n01.xml | Tests TokenizedType with wrong key word. The "id" is used in the TokenizedType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "i") for attribute "attr". [line 7] |
| 3.3.1 | ibm-not-wf-P56-ibm56n02.xml | Tests TokenizedType with wrong key word. The "Idref" is used in the TokenizedType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "I") for attribute "attr". [line 7] |
| 3.3.1 | ibm-not-wf-P56-ibm56n03.xml | Tests TokenizedType with wrong key word. The "Idrefs" is used in the TokenizedType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "I") for attribute "attr". [line 7] |
| 3.3.1 | ibm-not-wf-P56-ibm56n04.xml | Tests TokenizedType with wrong key word. The "EntitY" is used in the TokenizedType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "E") for attribute "attr". [line 7] |
| 3.3.1 | ibm-not-wf-P56-ibm56n05.xml | Tests TokenizedType with wrong key word. The "nmTOKEN" is used in the TokenizedType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "n") for attribute "attr". [line 7] |
| 3.3.1 | ibm-not-wf-P56-ibm56n06.xml | Tests TokenizedType with wrong key word. The "NMtokens" is used in the TokenizedType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "N") for attribute "attr". [line 7] |
| 3.3.1 | ibm-not-wf-P56-ibm56n07.xml | Tests TokenizedType with wrong key word. The "#ID" is used in the TokenizedType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "#") for attribute "attr". [line 7] |
| 3.3.1 | ibm-not-wf-P57-ibm57n01.xml | Tests EnumeratedType with an illegal option. The "NMTOKEN (a|b)" is used in the EnumeratedType in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 6] |
| 3.3.1 | ibm-not-wf-P58-ibm58n01.xml | Tests NotationType with wrong key word. The lower case "notation" is used as the key word in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "n") for attribute "attr". [line 8] |
| 3.3.1 | ibm-not-wf-P58-ibm58n02.xml | Tests NotationType with a required field missing. The beginning bracket "(" is missing in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Next character must be "(" starting list of attribute NOTATIONS . [line 8] |
| 3.3.1 | ibm-not-wf-P58-ibm58n03.xml | Tests NotationType with a required field missing. The Name is missing in the "()" in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Notation name is required. [line 8] |
| 3.3.1 | ibm-not-wf-P58-ibm58n04.xml | Tests NotationType with a required field missing. The closing bracket is missing in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Notation name is required. [line 8] |
| 3.3.1 | ibm-not-wf-P58-ibm58n05.xml | Tests NotationType with wrong field ordering. The key word "NOTATION" occurs after "(this)" in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 8] |
| 3.3.1 | ibm-not-wf-P58-ibm58n06.xml | Tests NotationType with wrong separator. The "," is used as a separator between "this" and "that" in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Notation name is required. [line 10] |
| 3.3.1 | ibm-not-wf-P58-ibm58n07.xml | Tests NotationType with a required field missing. The white space is missing between "NOTATION" and "(this)" in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Missing whitespace after NOTATION type name. [line 9] |
| 3.3.1 | ibm-not-wf-P58-ibm58n08.xml | Tests NotationType with extra wrong characters. The double quote character occurs after "(" and before ")" in the NotationType in the AttDef in the AttlistDecl in the DTD. | (fatal) Notation name is required. [line 9] |
| 3.3.1 | ibm-not-wf-P59-ibm59n01.xml | Tests Enumeration with required fields missing. The Nmtokens and "|"s are missing in the AttDef in the AttlistDecl in the DTD. | (fatal) Name tokens must not start with ")" characters. [line 8] |
| 3.3.1 | ibm-not-wf-P59-ibm59n02.xml | Tests Enumeration with a required field missing. The closing bracket ")" is missing in the AttDef in the AttlistDecl in the DTD. | (fatal) Name tokens must not start with "#" characters. [line 8] |
| 3.3.1 | ibm-not-wf-P59-ibm59n03.xml | Tests Enumeration with wrong separator. The "," is used as the separator in the AttDef in the AttlistDecl in the DTD. | (fatal) Name tokens must not start with "," characters. [line 9] |
| 3.3.1 | ibm-not-wf-P59-ibm59n04.xml | Tests Enumeration with illegal presence. The double quotes occur around the Enumeration value in the AttDef in the AttlistDecl in the DTD. | (fatal) Name tokens must not start with """ characters. [line 8] |
| 3.3.1 | ibm-not-wf-P59-ibm59n05.xml | Tests Enumeration with a required field missing. The white space is missing between in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "e") for attribute "attr". [line 8] |
| 3.3.1 | ibm-not-wf-P59-ibm59n06.xml | Tests Enumeration with a required field missing. The beginning bracket "(" is missing in the AttDef in the AttlistDecl in the DTD. | (fatal) Illegal type (starts with "e") for attribute "attr". [line 8] |
| 3.3.1 [54] | not-wf-sa-058 | Invalid character , in ATTLIST enumeration | (fatal) Name tokens must not start with "," characters. [line 3] |
| 3.3.1 [54] | o-p54fail1 | don't pass unknown attribute types | (fatal) Illegal type (starts with "D") for attribute "att". [line 4] |
| 3.3.1 [55] | o-p55fail1 | must be upper case | (fatal) Illegal type (starts with "c") for attribute "att". [line 4] |
| 3.3.1 [56] | attlist01 | SGML's NUTOKEN is not allowed. | (fatal) Illegal type (starts with "N") for attribute "number". [line 7] |
| 3.3.1 [56] | attlist02 | SGML's NUTOKENS attribute type is not allowed. | (fatal) Illegal type (starts with "N") for attribute "number". [line 7] |
| 3.3.1 [56] | attlist04 | SGML's NUMBER attribute type is not allowed. | (fatal) Illegal type (starts with "N") for attribute "number". [line 7] |
| 3.3.1 [56] | attlist05 | SGML's NUMBERS attribute type is not allowed. | (fatal) Illegal type (starts with "N") for attribute "numbers". [line 7] |
| 3.3.1 [56] | attlist06 | SGML's NAME attribute type is not allowed. | (fatal) Illegal type (starts with "N") for attribute "number". [line 7] |
| 3.3.1 [56] | attlist07 | SGML's NAMES attribute type is not allowed. | (fatal) Illegal type (starts with "N") for attribute "number". [line 7] |
| 3.3.1 [56] | attlist08 | SGML's #CURRENT is not allowed. | (fatal) Value must be quoted. [line 7] |
| 3.3.1 [56] | attlist09 | SGML's #CONREF is not allowed. | (fatal) Value must be quoted. [line 5] |
| 3.3.1 [56] | not-wf-sa-060 | Invalid type NAME defined in ATTLIST. | (fatal) Illegal type (starts with "N") for attribute "a1". [line 3] |
| 3.3.1 [56] | o-p56fail1 | no IDS type | (fatal) Missing whitespace between attribute type and default value. [line 4] |
| 3.3.1 [56] | o-p56fail2 | no NUMBER type | (fatal) Illegal type (starts with "N") for attribute "att". [line 4] |
| 3.3.1 [56] | o-p56fail3 | no NAME type | (fatal) Illegal type (starts with "N") for attribute "att". [line 4] |
| 3.3.1 [56] | o-p56fail4 | no ENTITYS type - types must be upper case | (fatal) Missing whitespace between attribute type and default value. [line 4] |
| 3.3.1 [56] | o-p56fail5 | types must be upper case | (fatal) Illegal type (starts with "i") for attribute "att". [line 4] |
| 3.3.1 [57] | o-p57fail1 | no keyword for NMTOKEN enumeration | (fatal) Value must be quoted. [line 4] |
| 3.3.1 [58] | not-wf-sa-068 | Space is required between NOTATION keyword and list of enumerated choices in <!ATTLIST...> declarations. | (fatal) Missing whitespace after NOTATION type name. [line 3] |
| 3.3.1 [58] | o-p58fail1 | at least one value required | (fatal) Notation name is required. [line 6] |
| 3.3.1 [58] | o-p58fail2 | separator must be '|' | (fatal) Notation name is required. [line 6] |
| 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) Notation name is required. [line 6] |
| 3.3.1 [58] | o-p58fail4 | NOTATION must be upper case | (fatal) Illegal type (starts with "n") for attribute "att". [line 6] |
| 3.3.1 [58] | o-p58fail5 | S after keyword is required | (fatal) Missing whitespace after NOTATION type name. [line 6] |
| 3.3.1 [58] | o-p58fail6 | parentheses are require | (fatal) Next character must be "(" starting list of attribute NOTATIONS . [line 5] |
| 3.3.1 [58] | o-p58fail7 | values are unquoted | (fatal) Next character must be "(" starting list of attribute NOTATIONS . [line 5] |
| 3.3.1 [58] | o-p58fail8 | values are unquoted | (fatal) Notation name is required. [line 5] |
| 3.3.1 [59] | attlist03 | Comma doesn't separate enumerations, unlike in SGML. | (fatal) Name tokens must not start with "," characters. [line 7] |
| 3.3.1 [59] | not-wf-sa-059 | String literal must be in quotes. | (fatal) Value must be quoted. [line 3] |
| 3.3.1 [59] | o-p59fail1 | at least one required | (fatal) Name tokens must not start with ")" characters. [line 4] |
| 3.3.1 [59] | o-p59fail2 | separator must be "," | (fatal) Name tokens must not start with "," characters. [line 4] |
| 3.3.1 [59] | o-p59fail3 | values are unquoted | (fatal) Name tokens must not start with """ characters. [line 4] |
| 3.3.2 | ibm-not-wf-P60-ibm60n01.xml | Tests DefaultDecl with wrong key word. The string "#required" is used as the key word in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 7] |
| 3.3.2 | ibm-not-wf-P60-ibm60n02.xml | Tests DefaultDecl with wrong key word. The string "Implied" is used as the key word in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 7] |
| 3.3.2 | ibm-not-wf-P60-ibm60n03.xml | Tests DefaultDecl with wrong key word. The string "!IMPLIED" is used as the key word in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 7] |
| 3.3.2 | ibm-not-wf-P60-ibm60n04.xml | Tests DefaultDecl with a required field missing. There is no attribute value specified after the key word "#FIXED" in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Value must be quoted. [line 7] |
| 3.3.2 | ibm-not-wf-P60-ibm60n05.xml | Tests DefaultDecl with a required field missing. The white space is missing between the key word "#FIXED" and the attribute value in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Missing whitespace after #FIXED. [line 7] |
| 3.3.2 | ibm-not-wf-P60-ibm60n06.xml | Tests DefaultDecl with wrong field ordering. The key word "#FIXED" occurs after the attribute value "introduction" in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Either an attribute declaration or ">" is expected, not "#". [line 7] |
| 3.3.2 | ibm-not-wf-P60-ibm60n07.xml | Tests DefaultDecl against WFC of P60. The text replacement of the entity "avalue" contains the "less than" character in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Use "<" for "<" in attribute values. [line 11] |
| 3.3.2 | ibm-not-wf-P60-ibm60n08.xml | Tests DefaultDecl with more than one key word. The "#REQUIRED" and the "#IMPLIED" are used as the key words in the DefaultDecl in the AttDef in the AttlistDecl in the DTD. | (fatal) Either an attribute declaration or ">" is expected, not "#". [line 7] |
| 3.3.2 [60] | o-p60fail1 | keywords must be upper case | (fatal) Value must be quoted. [line 4] |
| 3.3.2 [60] | o-p60fail2 | S is required after #FIXED | (fatal) Missing whitespace after #FIXED. [line 4] |
| 3.3.2 [60] | o-p60fail3 | only #FIXED has both keyword and value | (fatal) Either an attribute declaration or ">" is expected, not """. [line 4] |
| 3.3.2 [60] | o-p60fail4 | #FIXED required value | (fatal) Missing whitespace after #FIXED. [line 4] |
| 3.3.2 [60] | o-p60fail5 | only one default type | (fatal) Either an attribute declaration or ">" is expected, not "#". [line 4] |
| 3.4 | ibm-not-wf-P61-ibm61n01.xml | Tests conditionalSect with a wrong option. The word "NOTINCLUDE" is used as part of an option which is wrong in the coditionalSect. | (fatal) Only INCLUDE and IGNORE are allowed, not "NOTINCLUDE". [line 3] |
| 3.4 | ibm-not-wf-P62-ibm62n01.xml | Tests includeSect with wrong key word. The string "include" is used as a key word in the beginning sequence in the includeSect in the file ibm62n01.dtd. | (fatal) Only INCLUDE and IGNORE are allowed, not "include". [line 3] |
| 3.4 | ibm-not-wf-P62-ibm62n02.xml | Tests includeSect with wrong beginning sequence. An extra "[" occurs in the beginning sequence in the includeSect in the file ibm62n02.dtd. | (fatal) Need keyword in conditional DTD section. [line 3] |
| 3.4 | ibm-not-wf-P62-ibm62n03.xml | Tests includeSect with wrong beginning sequence. A wrong character "?" occurs in the beginning sequence in the includeSect in the file ibm62n03.dtd. | (fatal) Processing instruction target is missing. [line 3] |
| 3.4 | ibm-not-wf-P62-ibm62n04.xml | Tests includeSect with a required field missing. The key word "INCLUDE" is missing in the includeSect in the file ibm62n04.dtd. | (fatal) Need keyword in conditional DTD section. [line 3] |
| 3.4 | ibm-not-wf-P62-ibm62n05.xml | Tests includeSect with a required field missing. The "]" is missing after the key word "INCLUDE" in the includeSect in the file ibm62n05.dtd. | (fatal) Next character must be "[" beginning condition DTD subset . [line 4] |
| 3.4 | ibm-not-wf-P62-ibm62n06.xml | Tests includeSect with wrong field ordering. The two external subset declarations occur before the key word "INCLUDE" in the includeSect in the file ibm62n06.dtd. | (fatal) Need keyword in conditional DTD section. [line 4] |
| 3.4 | ibm-not-wf-P62-ibm62n07.xml | Tests includeSect with a required field missing. The closing sequence "]](greater than)" is missing in the includeSect in the file ibm62n07.dtd. | (fatal) Unterminated conditional DTD section. [line 4] |
| 3.4 | ibm-not-wf-P62-ibm62n08.xml | Tests includeSect with a required field missing. One "]" is missing in the closing sequence in the includeSect in the file ibm62n08.dtd. | (fatal) Unterminated conditional DTD section. [line 6] |
| 3.4 | ibm-not-wf-P63-ibm63n01.xml | Tests ignoreSect with wrong key word. The string "ignore" is used as a key word in the beginning sequence in the ignoreSect in the file ibm63n01.dtd. | (fatal) Only INCLUDE and IGNORE are allowed, not "ignore". [line 3] |
| 3.4 | ibm-not-wf-P63-ibm63n02.xml | Tests ignoreSect with wrong beginning sequence. An extra "[" occurs in the beginning sequence in the ignoreSect in the file ibm63n02.dtd. | (fatal) Need keyword in conditional DTD section. [line 3] |
| 3.4 | ibm-not-wf-P63-ibm63n03.xml | Tests ignoreSect with wrong beginning sequence. A wrong character "?" occurs in the beginning sequence in the ignoreSect in the file ibm63n03.dtd. | (fatal) Processing instruction target is missing. [line 3] |
| 3.4 | ibm-not-wf-P63-ibm63n04.xml | Tests ignoreSect with a required field missing. The key word "IGNORE" is missing in the ignoreSect in the file ibm63n04.dtd. | (fatal) Need keyword in conditional DTD section. [line 3] |
| 3.4 | ibm-not-wf-P63-ibm63n05.xml | Tests ignoreSect with a required field missing. The "]" is missing after the key word "IGNORE" in the ignoreSect in the file ibm63n05.dtd. | (fatal) Next character must be "[" beginning condition DTD subset . [line 4] |
| 3.4 | ibm-not-wf-P63-ibm63n06.xml | Tests includeSect with wrong field ordering. The two external subset declarations occur before the key word "IGNORE" in the ignoreSect in the file ibm63n06.dtd. | (fatal) Need keyword in conditional DTD section. [line 4] |
| 3.4 | ibm-not-wf-P63-ibm63n07.xml | Tests ignoreSect with a required field missing. The closing sequence "]](greater than)" is missing in the ignoreSect in the file ibm63n07.dtd. | (fatal) Expansion of entity "&[dtd];" is not well formed. [line 8] |
| 3.4 | ibm-not-wf-P64-ibm64n01.xml | Tests ignoreSectContents with wrong beginning sequence. The "?" occurs in beginning sequence the ignoreSectContents in the file ibm64n01.dtd. | (fatal) External parameter entity "%[dtd];" has characters after markup. [line 8] |
| 3.4 | ibm-not-wf-P64-ibm64n02.xml | Tests ignoreSectContents with a required field missing.The closing sequence is missing in the ignoreSectContents in the file ibm64n02.dtd. | (fatal) Expansion of entity "&[dtd];" is not well formed. [line 6] |
| 3.4 | ibm-not-wf-P64-ibm64n03.xml | Tests ignoreSectContents with a required field missing.The beginning sequence is missing in the ignoreSectContents in the file ibm64n03.dtd. | (fatal) External parameter entity "%[dtd];" has characters after markup. [line 8] |
| 3.4 | ibm-not-wf-P65-ibm65n01.xml | Tests Ignore with illegal string included. The string "]](greater than)" is contained before "this" in the Ignore in the ignoreSectContents in the file ibm65n01.dtd | (fatal) External parameter entity "%[dtd];" has characters after markup. [line 6] |
| 3.4 | ibm-not-wf-P65-ibm65n02.xml | Tests Ignore with illegal string included. The string "(less than)![" is contained before "this" in the Ignore in the ignoreSectContents in the file ibm65n02.dtd | (fatal) Expansion of entity "&[dtd];" is not well formed. [line 6] |
| 3.4 [61] | cond01 | Only INCLUDE and IGNORE are conditional section keywords | (fatal) Only INCLUDE and IGNORE are allowed, not "CDATA". [line 3] |
| 3.4 [61] | cond02 | Must have keyword in conditional sections | (fatal) Need keyword in conditional DTD section. [line 3] |
| 3.4 [61] | o-p61fail1 | no other types, including TEMP, which is valid in SGML | (fatal) Only INCLUDE and IGNORE are allowed, not "TEMP". [line 2] |
| 3.4 [62] | not-wf-not-sa-001 | Conditional sections must be properly terminated ("]>" used instead of "]]>"). | (fatal) Unterminated conditional DTD section. [line 3] |
| 3.4 [62] | not-wf-not-sa-003 | Conditional sections must be properly terminated ("]]>" omitted). | (fatal) Expansion of entity "&[dtd];" is not well formed. [line 1] |
| 3.4 [62] | not-wf-not-sa-004 | Conditional sections must be properly terminated ("]]>" omitted). | (fatal) Unterminated conditional DTD section. [line 2] |
| 3.4 [62] | not-wf-not-sa-006 | Conditional sections need a '[' after the INCLUDE or IGNORE. | (fatal) Next character must be "[" beginning condition DTD subset . [line 2] |
| 3.4 [62] | o-p62fail1 | INCLUDE must be upper case | (fatal) Only INCLUDE and IGNORE are allowed, not "include". [line 1] |
| 3.4 [62] | o-p62fail2 | no spaces in terminating delimiter | (fatal) Unterminated conditional DTD section. [line 3] |
| 3.4 [63] | o-p63fail1 | IGNORE must be upper case | (fatal) Only INCLUDE and IGNORE are allowed, not "ignore". [line 2] |
| 3.4 [63] | o-p63fail2 | delimiters must be balanced | (fatal) Expansion of entity "&[dtd];" is not well formed. [line 1] |
| 3.4 [64] | o-p64fail1 | section delimiters must balance | (fatal) External parameter entity "%[dtd];" has characters after markup. [line 2] |
| 3.4 [64] | o-p64fail2 | section delimiters must balance | (fatal) Expansion of entity "&[dtd];" is not well formed. [line 1] |
| 4.1 | ibm-not-wf-P66-ibm66n01.xml | Tests CharRef with an illegal character referred to. The "#002f" is used as the referred character in the CharRef in the EntityDecl in the DTD. | (fatal) Illegal decimal character reference. [line 5] |
| 4.1 | ibm-not-wf-P66-ibm66n02.xml | Tests CharRef with the semicolon character missing. The semicolon character is missing at the end of the CharRef in the attribute value in the STag of element "root". | (fatal) Illegal hexadecimal character reference. [line 7] |
| 4.1 | ibm-not-wf-P66-ibm66n03.xml | Tests CharRef with an illegal character referred to. The "49" is used as the referred character in the CharRef in the EntityDecl in the DTD. | (fatal) Illegal character or entity reference syntax. [line 5] |
| 4.1 | ibm-not-wf-P66-ibm66n04.xml | Tests CharRef with an illegal character referred to. The "#5~0" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | (fatal) Illegal decimal character reference. [line 7] |
| 4.1 | ibm-not-wf-P66-ibm66n05.xml | Tests CharRef with an illegal character referred to. The "#x002g" is used as the referred character in the CharRef in the EntityDecl in the DTD. | (fatal) Illegal hexadecimal character reference. [line 5] |
| 4.1 | ibm-not-wf-P66-ibm66n06.xml | Tests CharRef with an illegal character referred to. The "#x006G" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | (fatal) Illegal hexadecimal character reference. [line 7] |
| 4.1 | ibm-not-wf-P66-ibm66n07.xml | Tests CharRef with an illegal character referred to. The "#0=2f" is used as the referred character in the CharRef in the EntityDecl in the DTD. | (fatal) Illegal hexadecimal character reference. [line 5] |
| 4.1 | ibm-not-wf-P66-ibm66n08.xml | Tests CharRef with an illegal character referred to. The "#56.0" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | (fatal) Illegal decimal character reference. [line 7] |
| 4.1 | ibm-not-wf-P66-ibm66n09.xml | Tests CharRef with an illegal character referred to. The "#x00/2f" is used as the referred character in the CharRef in the EntityDecl in the DTD. | (fatal) Illegal hexadecimal character reference. [line 5] |
| 4.1 | ibm-not-wf-P66-ibm66n10.xml | Tests CharRef with an illegal character referred to. The "#51)" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | (fatal) Illegal decimal character reference. [line 7] |
| 4.1 | ibm-not-wf-P66-ibm66n11.xml | Tests CharRef with an illegal character referred to. The "#00 2f" is used as the referred character in the CharRef in the EntityDecl in the DTD. | (fatal) Illegal hexadecimal character reference. [line 5] |
| 4.1 | ibm-not-wf-P66-ibm66n12.xml | Tests CharRef with an illegal character referred to. The "#x0000" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | FAIL [Document not WF; no error reported] |
| 4.1 | ibm-not-wf-P66-ibm66n13.xml | Tests CharRef with an illegal character referred to. The "#x001f" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | FAIL [Document not WF; no error reported] |
| 4.1 | ibm-not-wf-P66-ibm66n14.xml | Tests CharRef with an illegal character referred to. The "#xfffe" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | FAIL [Document not WF; no error reported] |
| 4.1 | ibm-not-wf-P66-ibm66n15.xml | Tests CharRef with an illegal character referred to. The "#xffff" is used as the referred character in the attribute value in the EmptyElemTag of the element "root". | FAIL [Document not WF; no error reported] |
| 4.1 | ibm-not-wf-P68-ibm68n01.xml | Tests EntityRef with a required field missing. The Name is missing in the EntityRef in the content of the element "root". | (fatal) Illegal character or entity reference syntax. [line 7] |
| 4.1 | ibm-not-wf-P68-ibm68n02.xml | Tests EntityRef with a required field missing. The semicolon is missing in the EntityRef in the attribute value in the element "root". | (fatal) Next character must be ";" terminating reference to entity "aaa". [line 7] |
| 4.1 | ibm-not-wf-P68-ibm68n03.xml | Tests EntityRef with an extra white space. A white space occurs after the ampersand in the EntityRef in the content of the element "root". | (fatal) Illegal character or entity reference syntax. [line 7] |
| 4.1 | ibm-not-wf-P68-ibm68n04.xml | Tests EntityRef which is against P68 WFC: Entity Declared. The name "aAa" in the EntityRef in the AttValue in the STage of the element "root" does not match the Name of any declared entity in the DTD. | (fatal) Reference to undefined entity "&aAa;". [line 7] |
| 4.1 | ibm-not-wf-P68-ibm68n05.xml | Tests EntityRef which is against P68 WFC: Entity Declared. The entity with the name "aaa" in the EntityRef in the AttValue in the STag of the element "root" is not declared. | (fatal) Reference to undefined entity "&aaa;". [line 6] |
| 4.1 | ibm-not-wf-P68-ibm68n06.xml | Tests EntityRef which is against P68 WFC: Entity Declared. The entity with the name "aaa" in the EntityRef in the AttValue in the STag of the element "root" is externally declared, but standalone is "yes". | FAIL [Document not WF; no error reported] |
| 4.1 | ibm-not-wf-P68-ibm68n07.xml | Tests EntityRef which is against P68 WFC: Entity Declared. The entity with the name "aaa" in the EntityRef in the AttValue in the STag of the element "root" is referred before declared. | (fatal) Reference to undefined entity "&aaa;". [line 6] |
| 4.1 | ibm-not-wf-P68-ibm68n08.xml | Tests EntityRef which is against P68 WFC: Parsed Entity. The EntityRef in the AttValue in the STag of the element "root" contains the name "aImage" of an unparsed entity. | (fatal) Unparsed entities such as "&aImage;" must not be included. [line 9] |
| 4.1 | ibm-not-wf-P68-ibm68n09.xml | Tests EntityRef which is against P68 WFC: No Recursion. The recursive entity reference occurs with the entity declarations for "aaa" and "bbb" in the DTD. | (fatal) Expansion of entity "aaa" is recursive. [line 9] |
| 4.1 | ibm-not-wf-P68-ibm68n10.xml | Tests EntityRef which is against P68 WFC: No Recursion. The indirect recursive entity reference occurs with the entity declarations for "aaa", "bbb", "ccc", "ddd", and "eee" in the DTD. | (fatal) Expansion of entity "aaa" is recursive. [line 12] |
| 4.1 | ibm-not-wf-P69-ibm69n01.xml | Tests PEReference with a required field missing. The Name "paaa" is missing in the PEReference in the DTD. | (fatal) Illegal parameter entity reference syntax. [line 6] |
| 4.1 | ibm-not-wf-P69-ibm69n02.xml | Tests PEReference with a required field missing. The semicolon is missing in the PEReference "%paaa" in the DTD. | (fatal) Next character must be ";" terminating reference to parameter entity "paaa". [line 6] |
| 4.1 | ibm-not-wf-P69-ibm69n03.xml | Tests PEReference with an extra white space. There is an extra white space occurs before ";" in the PEReference in the DTD. | (fatal) Next character must be ";" terminating reference to parameter entity "paaa". [line 6] |
| 4.1 | ibm-not-wf-P69-ibm69n04.xml | Tests PEReference with an extra white space. There is an extra white space occurs after "%" in the PEReference in the DTD. | (fatal) Illegal parameter entity reference syntax. [line 6] |
| 4.1 | ibm-not-wf-P69-ibm69n06.xml | Tests PEReference which is against P69 WFC: No Recursion. The recursive PE reference occurs with the entity declarations for "paaa" and "bbb" in the DTD. | (fatal) Only external parameter entities may use "%paaa;" in entity values. [line 6] |
| 4.1 | ibm-not-wf-P69-ibm69n07.xml | Tests PEReference which is against P69 WFC: No Recursion. The indirect recursive PE reference occurs with the entity declarations for "paaa", "bbb", "ccc", "ddd", and "eee" in the DTD. | (fatal) Only external parameter entities may use "%paaa;" in entity values. [line 9] |
| 4.1 | not-wf-ext-sa-001 | Tests the No Recursion WFC by having an external general entity be self-recursive. | (fatal) Expansion of entity "e" is recursive. [line 1] |
| 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) Illegal reference to external entity "&e;" in attribute. [line 4] |
| 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) Reference to undefined entity "&e;". [line 3] |
| 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 undefined entity "&e;". [line 3] |
| 4.1 [66] | not-wf-sa-009 | Character references may have only decimal or numeric strings. | (fatal) Illegal decimal character reference. [line 1] |
| 4.1 [66] | not-wf-sa-022 | Character references end with semicolons, always! | (fatal) Illegal decimal character reference. [line 1] |
| 4.1 [66] | not-wf-sa-052 | Invalid character reference. | (fatal) Document root element is missing. [line 2] |
| 4.1 [66] | not-wf-sa-093 | Hexadecimal character references may not use the uppercase 'X'. | (fatal) Illegal decimal character reference. [line 1] |
| 4.1 [66] | not-wf-sa-179 | Invalid syntax matching double quote is missing. | (fatal) Premature end of input. [line 5] |
| 4.1 [66] | o-p66fail1 | terminating ';' is required | (fatal) Illegal decimal character reference. [line 1] |
| 4.1 [66] | o-p66fail2 | no S after '&#' | (fatal) Illegal decimal character reference. [line 1] |
| 4.1 [66] | o-p66fail3 | no hex digits in numeric reference | (fatal) Illegal decimal character reference. [line 1] |
| 4.1 [66] | o-p66fail4 | only hex digits in hex references | (fatal) Illegal hexadecimal character reference. [line 1] |
| 4.1 [66] | o-p66fail5 | no references to non-characters | (fatal) Illegal XML character  [line 1] |
| 4.1 [66] | o-p66fail6 | no references to non-characters | (fatal) Illegal XML character � [line 1] |
| 4.1 [68] | not-wf-sa-007 | General entity references have no whitespace after the entity name and before the semicolon. | (fatal) Next character must be ";" terminating reference to entity "amp". [line 1] |
| 4.1 [68] | not-wf-sa-010 | Ampersand may only appear as part of a general entity reference. | (fatal) Illegal character or entity reference syntax. [line 1] |
| 4.1 [68] | not-wf-sa-071 | ENTITY can't reference itself directly or indirectly. | (fatal) Expansion of entity "e1" is recursive. [line 6] |
| 4.1 [68] | not-wf-sa-072 | Undefined ENTITY foo. | (fatal) Reference to undefined entity "&foo;". [line 1] |
| 4.1 [68] | not-wf-sa-073 | Undefined ENTITY f. | (fatal) Reference to undefined entity "&f;". [line 4] |
| 4.1 [68] | not-wf-sa-075 | ENTITY can't reference itself directly or indirectly. | (fatal) Expansion of entity "e1" is recursive. [line 6] |
| 4.1 [68] | not-wf-sa-076 | Undefined ENTITY foo. | (fatal) Reference to undefined entity "&foo;". [line 1] |
| 4.1 [68] | not-wf-sa-078 | Undefined ENTITY foo. | (fatal) Reference to undefined entity "&foo;". [line 3] |
| 4.1 [68] | not-wf-sa-079 | ENTITY can't reference itself directly or indirectly. | (fatal) Expansion of entity "e1" is recursive. [line 6] |
| 4.1 [68] | not-wf-sa-080 | ENTITY can't reference itself directly or indirectly. | (fatal) Expansion of entity "e1" is recursive. [line 6] |
| 4.1 [68] | not-wf-sa-110 | Entity reference must be in content of element. | (fatal) Illegal character at end of document, &. [line 5] |
| 4.1 [68] | not-wf-sa-118 | Entity reference expansion is not recursive. | (fatal) Illegal character or entity reference syntax. [line 4] |
| 4.1 [68] | not-wf-sa-121 | A name of an ENTITY was started with an invalid character. | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 2] |
| 4.1 [68] | o-p68fail1 | terminating ';' is required | (fatal) Next character must be ";" terminating reference to entity "ent". [line 7] |
| 4.1 [68] | o-p68fail2 | no S after '&' | (fatal) Illegal character or entity reference syntax. [line 7] |
| 4.1 [68] | o-p68fail3 | no S before ';' | (fatal) Next character must be ";" terminating reference to entity "ent". [line 7] |
| 4.1 [69] | dtd02 | PE name immediately after "%" | (fatal) Illegal parameter entity reference syntax. [line 5] |
| 4.1 [69] | dtd03 | PE name immediately followed by ";" | (fatal) Next character must be ";" terminating reference to parameter entity "foo". [line 5] |
| 4.1 [69] | not-wf-not-sa-008 | In DTDs, the '%' character must be part of a parameter entity reference. | (fatal) Illegal parameter entity reference syntax. [line 2] |
| 4.1 [69] | not-wf-sa-163 | Invalid placement of Parameter entity reference. | (fatal) Document root element is missing. [line 5] |
| 4.1 [69] | not-wf-sa-164 | Invalid placement of Parameter entity reference. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 4] |
| 4.1 [69] | o-p69fail1 | terminating ';' is required | (fatal) Next character must be ";" terminating reference to parameter entity "pe". [line 5] |
| 4.1 [69] | o-p69fail2 | no S after '%' | (fatal) Illegal parameter entity reference syntax. [line 5] |
| 4.1 [69] | o-p69fail3 | no S before ';' | (fatal) Next character must be ";" terminating reference to parameter entity "pe". [line 5] |
| 4.2 | ibm-not-wf-P71-ibm70n01.xml | Tests | (fatal) Next character must be "]" terminating internal DTD subset . [line 7] |
| 4.2 | ibm-not-wf-P71-ibm71n01.xml | Tests EntityDecl with a required field missing. The white space is missing between the beginning sequence and the Name "aaa" in the EntityDecl in the DTD. | (fatal) Missing whitespace after <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P71-ibm71n02.xml | Tests EntityDecl with a required field missing. The white space is missing between the Name "aaa" and the EntityDef "aString" in the EntityDecl in the DTD. | (fatal) Missing whitespace after entity name. [line 6] |
| 4.2 | ibm-not-wf-P71-ibm71n03.xml | Tests EntityDecl with a required field missing. The EntityDef is missing in the EntityDecl with the Name "aaa" in the DTD. | (fatal) Missing whitespace after entity name. [line 6] |
| 4.2 | ibm-not-wf-P71-ibm71n04.xml | Tests EntityDecl with a required field missing. The Name is missing in the EntityDecl with the EntityDef "aString" in the DTD. | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P71-ibm71n05.xml | Tests EntityDecl with wrong ordering. The Name "aaa" occurs after the EntityDef in the EntityDecl in the DTD. | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P71-ibm71n06.xml | Tests EntityDecl with wrong key word. The string "entity" is used as the key word in the beginning sequence in the EntityDecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 6] |
| 4.2 | ibm-not-wf-P71-ibm71n07.xml | Tests EntityDecl with a required field missing. The closing bracket (greater than) is missing in the EntityDecl in the DTD. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "aaa". [line 8] |
| 4.2 | ibm-not-wf-P71-ibm71n08.xml | Tests EntityDecl with a required field missing. The exclamation mark is missing in the beginning sequence in the EntityDecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n01.xml | Tests PEdecl with a required field missing. The white space is missing between the beginning sequence and the "%" in the PEDecl in the DTD. | (fatal) Missing whitespace after <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n02.xml | Tests PEdecl with a required field missing. The Name is missing in the PEDecl in the DTD. | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n03.xml | Tests PEdecl with a required field missing. The white space is missing between the Name and the PEDef in the PEDecl in the DTD. | (fatal) Missing whitespace after entity name. [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n04.xml | Tests PEdecl with a required field missing. The PEDef is missing after the Name "paaa" in the PEDecl in the DTD. | (fatal) Missing whitespace after entity name. [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n05.xml | Tests PEdecl with wrong field ordering. The Name "paaa" occurs after the PEDef in the PEDecl in the DTD. | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n06.xml | Tests PEdecl with wrong field ordering. The "%" and the Name "paaa" occurs after the PEDef in the PEDecl in the DTD. | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n07.xml | Tests PEdecl with wrong key word. The string "entity" is used as the key word in the beginning sequence in the PEDecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 6] |
| 4.2 | ibm-not-wf-P72-ibm72n08.xml | Tests PEdecl with a required field missing. The closing bracket (greater than) is missing in the PEDecl in the DTD. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "%paaa". [line 7] |
| 4.2 | ibm-not-wf-P72-ibm72n09.xml | Tests PEdecl with wrong closing sequence. The string "!(greater than)" is used as the closing sequence in the PEDecl in the DTD. | (fatal) Missing whitespace after <!ENTITY declaration. [line 6] |
| 4.2 | ibm-not-wf-P73-ibm73n01.xml | Tests EntityDef with wrong field ordering. The NDataDecl "NDATA JPGformat" occurs before the ExternalID in the EntityDef in the EntityDecl. | (fatal) Value must be quoted. [line 7] |
| 4.2 | ibm-not-wf-P73-ibm73n03.xml | Tests EntityDef with a required field missing. The ExternalID is missing before the NDataDecl in the EntityDef in the EntityDecl. | (fatal) Value must be quoted. [line 7] |
| 4.2 | ibm-not-wf-P74-ibm74n01.xml | Tests PEDef with extra fields. The NDataDecl occurs after the ExternalID in the PEDef in the PEDecl in the DTD. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "%pImage". [line 7] |
| 4.2 | not-wf-sa-106 | Invalid placement of entity declaration. | (fatal) Document root element is missing. [line 2] |
| 4.2 [70] | not-wf-sa-109 | Tags invalid within EntityDecl. | (fatal) Document root element is missing. [line 4] |
| 4.2 [70] | o-p70fail1 | This is neither | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 4] |
| 4.2 [71] | not-wf-sa-062 | Entity declarations need space after the entity name. | (fatal) Missing whitespace after entity name. [line 2] |
| 4.2 [71] | o-p71fail1 | S is required before EntityDef | (fatal) Missing whitespace after entity name. [line 4] |
| 4.2 [71] | o-p71fail2 | Entity name is a Name, not an NMToken | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 4] |
| 4.2 [71] | o-p71fail3 | no S after "<!" | (fatal) Next character must be "]" terminating internal DTD subset . [line 4] |
| 4.2 [71] | o-p71fail4 | S is required after "<!ENTITY" | (fatal) Missing whitespace after <!ENTITY declaration. [line 4] |
| 4.2 [72] | not-wf-sa-165 | Parameter entity declarations must have a space before the '%'. | (fatal) Missing whitespace after <!ENTITY declaration. [line 2] |
| 4.2 [72] | o-p72fail1 | S is required after "<!ENTITY" | (fatal) Missing whitespace after <!ENTITY declaration. [line 4] |
| 4.2 [72] | o-p72fail2 | S is required after '%' | (fatal) Missing whitespace after % in parameter entity declaration. [line 4] |
| 4.2 [72] | o-p72fail3 | S is required after name | (fatal) Missing whitespace after entity name. [line 4] |
| 4.2 [72] | o-p72fail4 | Entity name is a name, not an NMToken | (fatal) Only whitespace allowed before name in <!ENTITY declaration. [line 4] |
| 4.2 [73] | o-p73fail1 | No typed replacement text | (fatal) Value must be quoted. [line 5] |
| 4.2 [73] | o-p73fail2 | Only one replacement value | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "ge". [line 5] |
| 4.2 [73] | o-p73fail3 | No NDataDecl on replacement text | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "ge". [line 5] |
| 4.2 [73] | o-p73fail4 | Value is required | (fatal) Value must be quoted. [line 5] |
| 4.2 [73] | o-p73fail5 | No NDataDecl without value | (fatal) Value must be quoted. [line 5] |
| 4.2 [74] | not-wf-sa-089 | Parameter entities "are" always parsed; NDATA annotations are not permitted. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "%foo". [line 2] |
| 4.2 [74] | not-wf-sa-091 | Parameter entities "are" always parsed; NDATA annotations are not permitted. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "%foo". [line 3] |
| 4.2 [74] | o-p74fail1 | no NDataDecls on parameter entities | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "%pe". [line 4] |
| 4.2 [74] | o-p74fail2 | value is required | (fatal) Missing whitespace after entity name. [line 4] |
| 4.2 [74] | o-p74fail3 | only one value | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "%pe". [line 3] |
| 4.2.2 | ibm-not-wf-P75-ibm75n01.xml | Tests ExternalID with wrong key word. The string "system" is used as the key word in the ExternalID in the EntityDef in the EntityDecl. | (fatal) Value must be quoted. [line 6] |
| 4.2.2 | ibm-not-wf-P75-ibm75n02.xml | Tests ExternalID with wrong key word. The string "public" is used as the key word in the ExternalID in the doctypedecl. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n03.xml | Tests ExternalID with wrong key word. The string "Public" is used as the key word in the ExternalID in the doctypedecl. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n04.xml | Tests ExternalID with wrong field ordering. The key word "PUBLIC" occurs after the PublicLiteral and the SystemLiteral in the ExternalID in the doctypedecl. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n05.xml | Tests ExternalID with a required field missing. The white space between "SYSTEM" and the Systemliteral is missing in the ExternalID in the EntityDef in the EntityDecl in the DTD. | (fatal) Missing whitespace before SYSTEM literal URI. [line 6] |
| 4.2.2 | ibm-not-wf-P75-ibm75n06.xml | Tests ExternalID with a required field missing. The Systemliteral is missing after "SYSTEM" in the ExternalID in the EntityDef in the EntityDecl in the DTD. | (fatal) Expecting quoted value for SYSTEM identifier. [line 6] |
| 4.2.2 | ibm-not-wf-P75-ibm75n07.xml | Tests ExternalID with a required field missing. The white space between the PublicLiteral and the Systemliteral is missing in the ExternalID in the doctypedecl. | (fatal) Missing whitespace before SYSTEM literal URI. [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n08.xml | Tests ExternalID with a required field missing. The key word "PUBLIC" is missing in the ExternalID in the doctypedecl. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n09.xml | Tests ExternalID with a required field missing. The white space between "PUBLIC" and the PublicLiteral is missing in the ExternalID in the doctypedecl. | (fatal) Missing whitespace after PUBLIC keyword. [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n10.xml | Tests ExternalID with a required field missing. The PublicLiteral is missing in the ExternalID in the doctypedecl. | (fatal) Illegal character in PUBLIC identifier: "\". [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n11.xml | Tests ExternalID with a required field missing. The PublicLiteral is missing in the ExternalID in the doctypedecl. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 4] |
| 4.2.2 | ibm-not-wf-P75-ibm75n12.xml | Tests ExternalID with a required field missing. The SystemLiteral is missing in the ExternalID in the doctypedecl. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "pImage". [line 6] |
| 4.2.2 | ibm-not-wf-P75-ibm75n13.xml | Tests ExternalID with wrong field ordering. The key word "PUBLIC" occurs after the PublicLiteral in the ExternalID in the doctypedecl. | (fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration . [line 4] |
| 4.2.2 | ibm-not-wf-P76-ibm76n01.xml | Tests NDataDecl with wrong key word. The string "ndata" is used as the key word in the NDataDecl in the EntityDef in the GEDecl. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "aImage". [line 8] |
| 4.2.2 | ibm-not-wf-P76-ibm76n02.xml | Tests NDataDecl with wrong key word. The string "NData" is used as the key word in the NDataDecl in the EntityDef in the GEDecl. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "aImage". [line 8] |
| 4.2.2 | ibm-not-wf-P76-ibm76n03.xml | Tests NDataDecl with a required field missing. The leading white space is missing in the NDataDecl in the EntityDef in the GEDecl. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "aImage". [line 8] |
| 4.2.2 | ibm-not-wf-P76-ibm76n04.xml | Tests NDataDecl with a required field missing. The key word "NDATA" is missing in the NDataDecl in the EntityDef in the GEDecl. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "aImage". [line 8] |
| 4.2.2 | ibm-not-wf-P76-ibm76n05.xml | Tests NDataDecl with a required field missing. The Name after the key word "NDATA" is missing in the NDataDecl in the EntityDef in the GEDecl. | (fatal) Missing whitespace before NDATA notation name in <!ENTITY declaration. [line 8] |
| 4.2.2 | ibm-not-wf-P76-ibm76n06.xml | Tests NDataDecl with a required field missing. The white space between "NDATA" and the Name is missing in the NDataDecl in the EntityDef in the GEDecl. | (fatal) Missing whitespace before NDATA notation name in <!ENTITY declaration. [line 8] |
| 4.2.2 | ibm-not-wf-P76-ibm76n07.xml | Tests NDataDecl with wrong field ordering. The key word "NDATA" occurs after the Name in the NDataDecl in the EntityDef in the GEDecl. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "aImage". [line 8] |
| 4.2.2 [75] | dtd04 | PUBLIC literal must be quoted | (fatal) Expecting quoted value for PUBLIC identifier. [line 4] |
| 4.2.2 [75] | dtd05 | SYSTEM identifier must be quoted | (fatal) Expecting quoted value for SYSTEM identifier. [line 4] |
| 4.2.2 [75] | not-wf-sa-054 | PUBLIC requires two literals. | (fatal) Missing whitespace before SYSTEM literal URI. [line 2] |
| 4.2.2 [75] | not-wf-sa-061 | External entity declarations require whitespace between public and system IDs. | (fatal) Missing whitespace before SYSTEM literal URI. [line 2] |
| 4.2.2 [75] | o-p75fail1 | S required after "PUBLIC" | (fatal) Missing whitespace after PUBLIC keyword. [line 3] |
| 4.2.2 [75] | o-p75fail2 | S required after "SYSTEM" | (fatal) Missing whitespace before SYSTEM literal URI. [line 3] |
| 4.2.2 [75] | o-p75fail3 | S required between literals | (fatal) Missing whitespace before SYSTEM literal URI. [line 3] |
| 4.2.2 [75] | o-p75fail4 | "SYSTEM" implies only one literal | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "ent". [line 3] |
| 4.2.2 [75] | o-p75fail5 | only one keyword | (fatal) Expecting quoted value for SYSTEM identifier. [line 3] |
| 4.2.2 [75] | o-p75fail6 | "PUBLIC" requires two literals (contrast with SGML) | (fatal) Missing whitespace before SYSTEM literal URI. [line 3] |
| 4.2.2 [76] | not-wf-sa-069 | Space is required before an NDATA entity annotation. | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "foo". [line 4] |
| 4.2.2 [76] | not-wf-sa-083 | Undefined NOTATION n. | (fatal) Unparsed entities such as "&e;" must not be included. [line 4] |
| 4.2.2 [76] | o-p76fail1 | S is required before "NDATA" | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "ge". [line 5] |
| 4.2.2 [76] | o-p76fail2 | "NDATA" is upper-case | (fatal) Next character must be ">" terminating <!ENTITY ...> declaration "ge". [line 5] |
| 4.2.2 [76] | o-p76fail3 | notation name is required | (fatal) Missing whitespace before NDATA notation name in <!ENTITY declaration. [line 5] |
| 4.2.2 [76] | o-p76fail4 | notation names are Names | (fatal) Only whitespace allowed before NDATA notation name in <!ENTITY declaration. [line 6] |
| 4.3.1 | ibm-not-wf-P77-ibm77n01.xml | Tests TextDecl with wrong field ordering. The VersionInfo occurs after the EncodingDecl in the TextDecl in the file "ibm77n01.ent". | (fatal) Need "?>" to terminate XML declaration. [line 1] |
| 4.3.1 | ibm-not-wf-P77-ibm77n02.xml | Tests TextDecl with wrong key word. The string "XML" is used in the beginning sequence in the TextDecl in the file "ibm77n02.ent". | (fatal) Next character must be ";" terminating reference to entity "aExternal". [line 8] |
| 4.3.1 | ibm-not-wf-P77-ibm77n03.xml | Tests TextDecl with wrong closing sequence. The character "greater than" is used as the closing sequence in the TextDecl in the file "ibm77n03.ent". | (fatal) Need "?>" to terminate XML declaration. [line 1] |
| 4.3.1 | ibm-not-wf-P77-ibm77n04.xml | Tests TextDecl with a required field missing. The closing sequence is missing in the TextDecl in the file "ibm77n04.ent". | (fatal) Need "?>" to terminate XML declaration. [line 2] |
| 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) Expected "encoding=...". [line 1] |
| 4.3.1 [77] | decl01 | External entities may not have standalone decls. | (fatal) Need "?>" to terminate XML declaration. [line 1] |
| 4.3.1 [77] | dtd07 | Text declarations (which optionally begin any external entity) are required to have "encoding=...". | (fatal) Expected "encoding=...". [line 1] |
| 4.3.1 [77] | encoding07 | Text declarations (which optionally begin any external entity) are required to have "encoding=...". | (fatal) Expected "encoding=...". [line 1] |
| 4.3.2 | ibm-not-wf-P78-ibm78n01.xml | Tests extParsedEnt with wrong field ordering. The TextDecl occurs after the content in the file ibm78n01.ent. | (fatal) XML declaration may only begin entities. [line 4] |
| 4.3.2 | ibm-not-wf-P78-ibm78n02.xml | Tests extParsedEnt with extra field. A blank line occurs before the TextDecl in the file ibm78n02.ent. | (fatal) XML declaration may only begin entities. [line 2] |
| 4.3.2 | ibm-not-wf-P79-ibm79n01.xml | Tests extPE with wrong field ordering. The TextDecl occurs after the extSubsetDecl (the white space and the comment) in the file ibm79n01.ent. | (fatal) XML declaration may only begin entities. [line 3] |
| 4.3.2 | ibm-not-wf-P79-ibm79n02.xml | Tests extPE with extra field. A blank line occurs before the TextDecl in the file ibm78n02.ent. | (fatal) XML declaration may only begin entities. [line 2] |
| 4.3.2 | not-wf-sa-074 | Internal general parsed entities are only well formed if they match the "content" production. | (fatal) Internal entity "&e;" has characters after content. [line 5] |
| 4.3.2 | not-wf-sa-103 | End-tag required for element foo. | (fatal) End of entity not allowed; an end tag is missing. [line 4] |
| 4.3.2 | not-wf-sa-104 | Internal general parsed entities are only well formed if they match the "content" production. | (fatal) End of entity not allowed; an end tag is missing. [line 4] |
| 4.3.2 | not-wf-sa-116 | Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. | (fatal) Expansion of entity "&e;" is not well formed. [line 4] |
| 4.3.2 | not-wf-sa-117 | Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. | (fatal) Expansion of entity "&e;" is not well formed. [line 4] |
| 4.3.2 | not-wf-sa-119 | Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. | (fatal) Expansion of entity "&e;" is not well formed. [line 5] |
| 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) XML declaration may only begin entities. [line 5] |
| 4.3.2 | not-wf-sa-181 | Internal parsed entities must match the content production to be well formed. | (fatal) EOF while parsing <![CDATA[ section. [line 5] |
| 4.3.2 | not-wf-sa-182 | Internal parsed entities must match the content production to be well formed. | (fatal) End of entity while processing comment. [line 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. | (fatal) External parameter entity "%[dtd];" has characters after markup. [line 1] |
| 4.3.3 | bomtest-ent2x | Tests conformance with XML 2nd Ed erratum E22. XML entities may now begin with a UTF-8 BOM. (This uses an entity with a BOM and a Zero-width nonbreaking space, followed by an illegal processing instruction that resembles a text decl.) | (fatal) XML declaration may only begin entities. [line 1] |
| 4.3.3 | ibm-not-wf-P80-ibm80n01.xml | Tests EncodingDecl with a required field missing. The leading white space is missing in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "e" (e) at end of XML Declaration. [line 1] |
| 4.3.3 | ibm-not-wf-P80-ibm80n02.xml | Tests EncodingDecl with a required field missing. The "=" sign is missing in the EncodingDecl in the XMLDecl. | (fatal) Next character must be "=" in XML Declaration . [line 1] |
| 4.3.3 | ibm-not-wf-P80-ibm80n03.xml | Tests EncodingDecl with a required field missing. The double quoted EncName are missing in the EncodingDecl in the XMLDecl. | (fatal) Expecting quoted value for attribute value encoding. [line 1] |
| 4.3.3 | ibm-not-wf-P80-ibm80n04.xml | Tests EncodingDecl with wrong field ordering. The string "encoding=" occurs after the double quoted EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character """ (") at end of XML Declaration. [line 1] |
| 4.3.3 | ibm-not-wf-P80-ibm80n05.xml | Tests EncodingDecl with wrong field ordering. The "encoding" occurs after the double quoted EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character """ (") at end of XML Declaration. [line 1] |
| 4.3.3 | ibm-not-wf-P80-ibm80n06.xml | Tests EncodingDecl with wrong key word. The string "Encoding" is used as the key word in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "E" (E) at end of XML Declaration. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n01.xml | Tests EncName with an illegal character. The "_" is used as the first character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "_" in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n02.xml | Tests EncName with an illegal character. The "-" is used as the first character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "-" in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n03.xml | Tests EncName with an illegal character. The "." is used as the first character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "." in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n04.xml | Tests EncName with illegal characters. The "8-" is used as the initial characters in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "8" in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n05.xml | Tests EncName with an illegal character. The "~" is used as one character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "~" in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n06.xml | Tests EncName with an illegal character. The "#" is used as one character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "#" in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n07.xml | Tests EncName with an illegal character. The ":" is used as one character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character ":" in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n08.xml | Tests EncName with an illegal character. The "/" is used as one character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character "/" in encoding name. [line 1] |
| 4.3.3 | ibm-not-wf-P81-ibm81n09.xml | Tests EncName with an illegal character. The ";" is used as one character in the EncName in the EncodingDecl in the XMLDecl. | (fatal) Illegal character ";" in encoding name. [line 1] |
| 4.3.3 [81] | encoding01 | Illegal character " " in encoding name | (fatal) Illegal character " " in encoding name. [line 1] |
| 4.3.3 [81] | encoding02 | Illegal character "/" in encoding name | (fatal) Illegal character "/" in encoding name. [line 1] |
| 4.3.3 [81] | encoding03 | Illegal character reference in encoding name | (fatal) Illegal character "&" in encoding name. [line 1] |
| 4.3.3 [81] | encoding04 | Illegal character ":" in encoding name | (fatal) Illegal character ":" in encoding name. [line 1] |
| 4.3.3 [81] | encoding05 | Illegal character "@" in encoding name | (fatal) Illegal character "@" in encoding name. [line 1] |
| 4.3.3 [81] | encoding06 | Illegal character "+" in encoding name | (fatal) Illegal character "+" in encoding name. [line 1] |
| 4.3.3 [81] | not-wf-sa-101 | Space is not permitted in an encoding name. | (fatal) Illegal character " " in encoding name. [line 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) Illegal character or entity reference syntax. [line 4] |
| 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) Expansion of entity "&e;" is not well formed. [line 4] |
| 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;. | (fatal) Expansion of entity "&e;" is not well formed. [line 5] |
| 4.7 | ibm-not-wf-P82-ibm82n01.xml | Tests NotationDecl with a required field missing. The white space after the beginning sequence of the NotationDecl is missing in the DTD. | (fatal) Missing whitespace before name in <!NOTATION declaration. [line 7] |
| 4.7 | ibm-not-wf-P82-ibm82n02.xml | Tests NotationDecl with a required field missing. The Name in the NotationDecl is missing in the DTD. | (fatal) Notation must be PUBLIC or SYSTEM. [line 7] |
| 4.7 | ibm-not-wf-P82-ibm82n03.xml | Tests NotationDecl with a required field missing. The externalID or the PublicID is missing in the NotationDecl in the DTD. | (fatal) Notation must be PUBLIC or SYSTEM. [line 7] |
| 4.7 | ibm-not-wf-P82-ibm82n04.xml | Tests NotationDecl with wrong field ordering. The Name occurs after the "SYSTEM" and the externalID in the NotationDecl in the DTD. | (fatal) Notation must be PUBLIC or SYSTEM. [line 7] |
| 4.7 | ibm-not-wf-P82-ibm82n05.xml | Tests NotationDecl with wrong key word. The string "notation" is used as a key word in the NotationDecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 7] |
| 4.7 | ibm-not-wf-P82-ibm82n06.xml | Tests NotationDecl with a required field missing. The closing bracket (the greater than character) is missing in the NotationDecl. | (fatal) Expecting quoted value for SYSTEM identifier. [line 8] |
| 4.7 | ibm-not-wf-P82-ibm82n07.xml | Tests NotationDecl with wrong beginning sequence. The "!" is missing in the beginning sequence in the NotationDecl in the DTD. | (fatal) Next character must be "]" terminating internal DTD subset . [line 7] |
| 4.7 | ibm-not-wf-P82-ibm82n08.xml | Tests NotationDecl with wrong closing sequence. The extra "!" occurs in the closing sequence in the NotationDecl in the DTD. | (fatal) Next character must be ">" terminating <!NOTATION ...> declaration "JPGformat". [line 7] |
| 4.7 | ibm-not-wf-P83-ibm83n01.xml | Tests PublicID with wrong key word. The string "public" is used as the key word in the PublicID in the NotationDcl in the DTD. | (fatal) Notation must be PUBLIC or SYSTEM. [line 7] |
| 4.7 | ibm-not-wf-P83-ibm83n02.xml | Tests PublicID with wrong key word. The string "Public" is used as the key word in the PublicID in the NotationDcl in the DTD. | (fatal) Document root element is missing. [line 1] |
| 4.7 | ibm-not-wf-P83-ibm83n03.xml | Tests PublicID with a required field missing. The key word "PUBLIC" is missing in the PublicID in the NotationDcl in the DTD. | (fatal) Notation must be PUBLIC or SYSTEM. [line 7] |
| 4.7 | ibm-not-wf-P83-ibm83n04.xml | Tests PublicID with a required field missing. The white space between the "PUBLIC" and the PubidLiteral is missing in the PublicID in the NotationDcl in the DTD. | (fatal) Missing whitespace after PUBLIC keyword. [line 7] |
| 4.7 | ibm-not-wf-P83-ibm83n05.xml | Tests PublicID with a required field missing. The PubidLiteral is missing in the PublicID in the NotationDcl in the DTD. | (fatal) Expecting quoted value for PUBLIC identifier. [line 7] |
| 4.7 | ibm-not-wf-P83-ibm83n06.xml | Tests PublicID with wrong field ordering. The key word "PUBLIC" occurs after the PubidLiteral in the PublicID in the NotationDcl. | (fatal) Notation must be PUBLIC or SYSTEM. [line 7] |
| 41. [68] | not-wf-sa-077 | Undefined ENTITY bar. | (fatal) Reference to undefined entity "&bar;". [line 4] |
| B. | ibm-not-wf-P85-ibm85n01.xml | Tests BaseChar with an illegal character. The character #x00D7 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n02.xml | Tests BaseChar with an illegal character. The character #x00F7 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n03.xml | Tests BaseChar with an illegal character. The character #x0132 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n04.xml | Tests BaseChar with an illegal character. The character #x0133 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n05.xml | Tests BaseChar with an illegal character. The character #x013F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n06.xml | Tests BaseChar with an illegal character. The character #x0140 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n07.xml | Tests BaseChar with an illegal character. The character #x0149 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n08.xml | Tests BaseChar with an illegal character. The character #x017F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n09.xml | Tests BaseChar with an illegal character. The character #x01c4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n10.xml | Tests BaseChar with an illegal character. The character #x01CC occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n100.xml | Tests BaseChar with an illegal character. The character #x0BB6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n101.xml | Tests BaseChar with an illegal character. The character #x0BBA occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n102.xml | Tests BaseChar with an illegal character. The character #x0C0D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n103.xml | Tests BaseChar with an illegal character. The character #x0C11 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n104.xml | Tests BaseChar with an illegal character. The character #x0C29 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n105.xml | Tests BaseChar with an illegal character. The character #x0C34 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n106.xml | Tests BaseChar with an illegal character. The character #x0C5F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n107.xml | Tests BaseChar with an illegal character. The character #x0C62 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n108.xml | Tests BaseChar with an illegal character. The character #x0C8D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n109.xml | Tests BaseChar with an illegal character. The character #x0C91 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n11.xml | Tests BaseChar with an illegal character. The character #x01F1 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n110.xml | Tests BaseChar with an illegal character. The character #x0CA9 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n111.xml | Tests BaseChar with an illegal character. The character #x0CB4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n112.xml | Tests BaseChar with an illegal character. The character #x0CBA occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n113.xml | Tests BaseChar with an illegal character. The character #x0CDF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n114.xml | Tests BaseChar with an illegal character. The character #x0CE2 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n115.xml | Tests BaseChar with an illegal character. The character #x0D0D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n116.xml | Tests BaseChar with an illegal character. The character #x0D11 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n117.xml | Tests BaseChar with an illegal character. The character #x0D29 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n118.xml | Tests BaseChar with an illegal character. The character #x0D3A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n119.xml | Tests BaseChar with an illegal character. The character #x0D62 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n12.xml | Tests BaseChar with an illegal character. The character #x01F3 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n120.xml | Tests BaseChar with an illegal character. The character #x0E2F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n121.xml | Tests BaseChar with an illegal character. The character #x0E31 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n122.xml | Tests BaseChar with an illegal character. The character #x0E34 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n123.xml | Tests BaseChar with an illegal character. The character #x0E46 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n124.xml | Tests BaseChar with an illegal character. The character #x0E83 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n125.xml | Tests BaseChar with an illegal character. The character #x0E85 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n126.xml | Tests BaseChar with an illegal character. The character #x0E89 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n127.xml | Tests BaseChar with an illegal character. The character #x0E8B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n128.xml | Tests BaseChar with an illegal character. The character #x0E8E occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n129.xml | Tests BaseChar with an illegal character. The character #x0E98 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n13.xml | Tests BaseChar with an illegal character. The character #x01F6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n130.xml | Tests BaseChar with an illegal character. The character #x0EA0 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n131.xml | Tests BaseChar with an illegal character. The character #x0EA4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n132.xml | Tests BaseChar with an illegal character. The character #x0EA6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n133.xml | Tests BaseChar with an illegal character. The character #x0EA8 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n134.xml | Tests BaseChar with an illegal character. The character #x0EAC occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n135.xml | Tests BaseChar with an illegal character. The character #x0EAF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n136.xml | Tests BaseChar with an illegal character. The character #x0EB1 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n137.xml | Tests BaseChar with an illegal character. The character #x0EB4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n138.xml | Tests BaseChar with an illegal character. The character #x0EBE occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n139.xml | Tests BaseChar with an illegal character. The character #x0EC5 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n14.xml | Tests BaseChar with an illegal character. The character #x01F9 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n140.xml | Tests BaseChar with an illegal character. The character #x0F48 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n141.xml | Tests BaseChar with an illegal character. The character #x0F6A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n142.xml | Tests BaseChar with an illegal character. The character #x10C6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n143.xml | Tests BaseChar with an illegal character. The character #x10F7 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n144.xml | Tests BaseChar with an illegal character. The character #x1011 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n145.xml | Tests BaseChar with an illegal character. The character #x1104 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n146.xml | Tests BaseChar with an illegal character. The character #x1108 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n147.xml | Tests BaseChar with an illegal character. The character #x110A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n148.xml | Tests BaseChar with an illegal character. The character #x110D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n149.xml | Tests BaseChar with an illegal character. The character #x113B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n15.xml | Tests BaseChar with an illegal character. The character #x01F9 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n150.xml | Tests BaseChar with an illegal character. The character #x113F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n151.xml | Tests BaseChar with an illegal character. The character #x1141 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n152.xml | Tests BaseChar with an illegal character. The character #x114D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n153.xml | Tests BaseChar with an illegal character. The character #x114f occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n154.xml | Tests BaseChar with an illegal character. The character #x1151 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n155.xml | Tests BaseChar with an illegal character. The character #x1156 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n156.xml | Tests BaseChar with an illegal character. The character #x115A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n157.xml | Tests BaseChar with an illegal character. The character #x1162 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n158.xml | Tests BaseChar with an illegal character. The character #x1164 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n159.xml | Tests BaseChar with an illegal character. The character #x1166 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n16.xml | Tests BaseChar with an illegal character. The character #x0230 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n160.xml | Tests BaseChar with an illegal character. The character #x116B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n161.xml | Tests BaseChar with an illegal character. The character #x116F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n162.xml | Tests BaseChar with an illegal character. The character #x1174 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n163.xml | Tests BaseChar with an illegal character. The character #x119F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n164.xml | Tests BaseChar with an illegal character. The character #x11AC occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n165.xml | Tests BaseChar with an illegal character. The character #x11B6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n166.xml | Tests BaseChar with an illegal character. The character #x11B9 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n167.xml | Tests BaseChar with an illegal character. The character #x11BB occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n168.xml | Tests BaseChar with an illegal character. The character #x11C3 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n169.xml | Tests BaseChar with an illegal character. The character #x11F1 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n17.xml | Tests BaseChar with an illegal character. The character #x02AF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n170.xml | Tests BaseChar with an illegal character. The character #x11FA occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n171.xml | Tests BaseChar with an illegal character. The character #x1E9C occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n172.xml | Tests BaseChar with an illegal character. The character #x1EFA occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n173.xml | Tests BaseChar with an illegal character. The character #x1F16 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n174.xml | Tests BaseChar with an illegal character. The character #x1F1E occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n175.xml | Tests BaseChar with an illegal character. The character #x1F46 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n176.xml | Tests BaseChar with an illegal character. The character #x1F4F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n177.xml | Tests BaseChar with an illegal character. The character #x1F58 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n178.xml | Tests BaseChar with an illegal character. The character #x1F5A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n179.xml | Tests BaseChar with an illegal character. The character #x1F5C occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n18.xml | Tests BaseChar with an illegal character. The character #x02CF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n180.xml | Tests BaseChar with an illegal character. The character #x1F5E occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n181.xml | Tests BaseChar with an illegal character. The character #xF17E occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n182.xml | Tests BaseChar with an illegal character. The character #x1FB5 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n183.xml | Tests BaseChar with an illegal character. The character #x1FBD occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n184.xml | Tests BaseChar with an illegal character. The character #x1FBF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n185.xml | Tests BaseChar with an illegal character. The character #x1FC5 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n186.xml | Tests BaseChar with an illegal character. The character #x1FCD occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n187.xml | Tests BaseChar with an illegal character. The character #x1FD5 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n188.xml | Tests BaseChar with an illegal character. The character #x1FDC occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n189.xml | Tests BaseChar with an illegal character. The character #x1FED occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n19.xml | Tests BaseChar with an illegal character. The character #x0387 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n190.xml | Tests BaseChar with an illegal character. The character #x1FF5 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n191.xml | Tests BaseChar with an illegal character. The character #x1FFD occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n192.xml | Tests BaseChar with an illegal character. The character #x2127 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n193.xml | Tests BaseChar with an illegal character. The character #x212F occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n194.xml | Tests BaseChar with an illegal character. The character #x2183 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n195.xml | Tests BaseChar with an illegal character. The character #x3095 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n196.xml | Tests BaseChar with an illegal character. The character #x30FB occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n197.xml | Tests BaseChar with an illegal character. The character #x312D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n198.xml | Tests BaseChar with an illegal character. The character #xD7A4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n20.xml | Tests BaseChar with an illegal character. The character #x038B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n21.xml | Tests BaseChar with an illegal character. The character #x03A2 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n22.xml | Tests BaseChar with an illegal character. The character #x03CF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n23.xml | Tests BaseChar with an illegal character. The character #x03D7 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n24.xml | Tests BaseChar with an illegal character. The character #x03DD occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n25.xml | Tests BaseChar with an illegal character. The character #x03E1 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n26.xml | Tests BaseChar with an illegal character. The character #x03F4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n27.xml | Tests BaseChar with an illegal character. The character #x040D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n28.xml | Tests BaseChar with an illegal character. The character #x0450 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n29.xml | Tests BaseChar with an illegal character. The character #x045D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n30.xml | Tests BaseChar with an illegal character. The character #x0482 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n31.xml | Tests BaseChar with an illegal character. The character #x04C5 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n32.xml | Tests BaseChar with an illegal character. The character #x04C6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n33.xml | Tests BaseChar with an illegal character. The character #x04C9 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n34.xml | Tests BaseChar with an illegal character. The character #x04EC occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n35.xml | Tests BaseChar with an illegal character. The character #x04ED occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n36.xml | Tests BaseChar with an illegal character. The character #x04F6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n37.xml | Tests BaseChar with an illegal character. The character #x04FA occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n38.xml | Tests BaseChar with an illegal character. The character #x0557 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n39.xml | Tests BaseChar with an illegal character. The character #x0558 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n40.xml | Tests BaseChar with an illegal character. The character #x0587 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n41.xml | Tests BaseChar with an illegal character. The character #x05EB occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n42.xml | Tests BaseChar with an illegal character. The character #x05F3 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n43.xml | Tests BaseChar with an illegal character. The character #x0620 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n44.xml | Tests BaseChar with an illegal character. The character #x063B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n45.xml | Tests BaseChar with an illegal character. The character #x064B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n46.xml | Tests BaseChar with an illegal character. The character #x06B8 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n47.xml | Tests BaseChar with an illegal character. The character #x06BF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n48.xml | Tests BaseChar with an illegal character. The character #x06CF occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n49.xml | Tests BaseChar with an illegal character. The character #x06D4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n50.xml | Tests BaseChar with an illegal character. The character #x06D6 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n51.xml | Tests BaseChar with an illegal character. The character #x06E7 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n52.xml | Tests BaseChar with an illegal character. The character #x093A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n53.xml | Tests BaseChar with an illegal character. The character #x093E occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n54.xml | Tests BaseChar with an illegal character. The character #x0962 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n55.xml | Tests BaseChar with an illegal character. The character #x098D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n56.xml | Tests BaseChar with an illegal character. The character #x0991 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n57.xml | Tests BaseChar with an illegal character. The character #x0992 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n58.xml | Tests BaseChar with an illegal character. The character #x09A9 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n59.xml | Tests BaseChar with an illegal character. The character #x09B1 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n60.xml | Tests BaseChar with an illegal character. The character #x09B5 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n61.xml | Tests BaseChar with an illegal character. The character #x09BA occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n62.xml | Tests BaseChar with an illegal character. The character #x09DE occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n63.xml | Tests BaseChar with an illegal character. The character #x09E2 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n64.xml | Tests BaseChar with an illegal character. The character #x09F2 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n65.xml | Tests BaseChar with an illegal character. The character #x0A0B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n66.xml | Tests BaseChar with an illegal character. The character #x0A11 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n67.xml | Tests BaseChar with an illegal character. The character #x0A29 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n68.xml | Tests BaseChar with an illegal character. The character #x0A31 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n69.xml | Tests BaseChar with an illegal character. The character #x0A34 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n70.xml | Tests BaseChar with an illegal character. The character #x0A37 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n71.xml | Tests BaseChar with an illegal character. The character #x0A3A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n72.xml | Tests BaseChar with an illegal character. The character #x0A5B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n73.xml | Tests BaseChar with an illegal character. The character #x0A70 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n74.xml | Tests BaseChar with an illegal character. The character #x0A75 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n75.xml | Tests BaseChar with an illegal character. The character #x occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n76.xml | Tests BaseChar with an illegal character. The character #x0ABC occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n77.xml | Tests BaseChar with an illegal character. The character #x0A92 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n78.xml | Tests BaseChar with an illegal character. The character #x0AA9 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n79.xml | Tests BaseChar with an illegal character. The character #x0AB1 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n80.xml | Tests BaseChar with an illegal character. The character #x0AB4 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n81.xml | Tests BaseChar with an illegal character. The character #x0ABA occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n82.xml | Tests BaseChar with an illegal character. The character #x0B04 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n83.xml | Tests BaseChar with an illegal character. The character #x0B0D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n84.xml | Tests BaseChar with an illegal character. The character #x0B11 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n85.xml | Tests BaseChar with an illegal character. The character #x0B29 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n86.xml | Tests BaseChar with an illegal character. The character #x0B31 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n87.xml | Tests BaseChar with an illegal character. The character #x0B34 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n88.xml | Tests BaseChar with an illegal character. The character #x0B3A occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n89.xml | Tests BaseChar with an illegal character. The character #x0B3E occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n90.xml | Tests BaseChar with an illegal character. The character #x0B5E occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n91.xml | Tests BaseChar with an illegal character. The character #x0B62 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n92.xml | Tests BaseChar with an illegal character. The character #x0B8B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n93.xml | Tests BaseChar with an illegal character. The character #x0B91 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n94.xml | Tests BaseChar with an illegal character. The character #x0B98 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n95.xml | Tests BaseChar with an illegal character. The character #x0B9B occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n96.xml | Tests BaseChar with an illegal character. The character #x0B9D occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n97.xml | Tests BaseChar with an illegal character. The character #x0BA0 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n98.xml | Tests BaseChar with an illegal character. The character #x0BA7 occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P85-ibm85n99.xml | Tests BaseChar with an illegal character. The character #x0BAB occurs as the first character of the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P86-ibm86n01.xml | Tests Ideographic with an illegal character. The character #x4CFF occurs as the first character in the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P86-ibm86n02.xml | Tests Ideographic with an illegal character. The character #x9FA6 occurs as the first character in the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P86-ibm86n03.xml | Tests Ideographic with an illegal character. The character #x3008 occurs as the first character in the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P86-ibm86n04.xml | Tests Ideographic with an illegal character. The character #x302A occurs as the first character in the PITarget in the PI in the DTD. | (fatal) Processing instruction target is missing. [line 3] |
| B. | ibm-not-wf-P87-ibm87n01.xml | Tests CombiningChar with an illegal character. The character #x02FF occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n02.xml | Tests CombiningChar with an illegal character. The character #x0346 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n03.xml | Tests CombiningChar with an illegal character. The character #x0362 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n04.xml | Tests CombiningChar with an illegal character. The character #x0487 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n05.xml | Tests CombiningChar with an illegal character. The character #x05A2 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n06.xml | Tests CombiningChar with an illegal character. The character #x05BA occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n07.xml | Tests CombiningChar with an illegal character. The character #x05BE occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n08.xml | Tests CombiningChar with an illegal character. The character #x05C0 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n09.xml | Tests CombiningChar with an illegal character. The character #x05C3 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n10.xml | Tests CombiningChar with an illegal character. The character #x0653 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n11.xml | Tests CombiningChar with an illegal character. The character #x06B8 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n12.xml | Tests CombiningChar with an illegal character. The character #x06B9 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n13.xml | Tests CombiningChar with an illegal character. The character #x06E9 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n14.xml | Tests CombiningChar with an illegal character. The character #x06EE occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n15.xml | Tests CombiningChar with an illegal character. The character #x0904 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n16.xml | Tests CombiningChar with an illegal character. The character #x093B occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n17.xml | Tests CombiningChar with an illegal character. The character #x094E occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n18.xml | Tests CombiningChar with an illegal character. The character #x0955 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n19.xml | Tests CombiningChar with an illegal character. The character #x0964 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n20.xml | Tests CombiningChar with an illegal character. The character #x0984 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n21.xml | Tests CombiningChar with an illegal character. The character #x09C5 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n22.xml | Tests CombiningChar with an illegal character. The character #x09C9 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n23.xml | Tests CombiningChar with an illegal character. The character #x09CE occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n24.xml | Tests CombiningChar with an illegal character. The character #x09D8 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n25.xml | Tests CombiningChar with an illegal character. The character #x09E4 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n26.xml | Tests CombiningChar with an illegal character. The character #x0A03 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n27.xml | Tests CombiningChar with an illegal character. The character #x0A3D occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n28.xml | Tests CombiningChar with an illegal character. The character #x0A46 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n29.xml | Tests CombiningChar with an illegal character. The character #x0A49 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n30.xml | Tests CombiningChar with an illegal character. The character #x0A4E occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n31.xml | Tests CombiningChar with an illegal character. The character #x0A80 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n32.xml | Tests CombiningChar with an illegal character. The character #x0A84 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n33.xml | Tests CombiningChar with an illegal character. The character #x0ABB occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n34.xml | Tests CombiningChar with an illegal character. The character #x0AC6 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n35.xml | Tests CombiningChar with an illegal character. The character #x0ACA occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n36.xml | Tests CombiningChar with an illegal character. The character #x0ACE occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n37.xml | Tests CombiningChar with an illegal character. The character #x0B04 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n38.xml | Tests CombiningChar with an illegal character. The character #x0B3B occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n39.xml | Tests CombiningChar with an illegal character. The character #x0B44 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n40.xml | Tests CombiningChar with an illegal character. The character #x0B4A occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n41.xml | Tests CombiningChar with an illegal character. The character #x0B4E occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n42.xml | Tests CombiningChar with an illegal character. The character #x0B58 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n43.xml | Tests CombiningChar with an illegal character. The character #x0B84 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n44.xml | Tests CombiningChar with an illegal character. The character #x0BC3 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n45.xml | Tests CombiningChar with an illegal character. The character #x0BC9 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n46.xml | Tests CombiningChar with an illegal character. The character #x0BD6 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n47.xml | Tests CombiningChar with an illegal character. The character #x0C0D occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n48.xml | Tests CombiningChar with an illegal character. The character #x0C45 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n49.xml | Tests CombiningChar with an illegal character. The character #x0C49 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n50.xml | Tests CombiningChar with an illegal character. The character #x0C54 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n51.xml | Tests CombiningChar with an illegal character. The character #x0C81 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n52.xml | Tests CombiningChar with an illegal character. The character #x0C84 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n53.xml | Tests CombiningChar with an illegal character. The character #x0CC5 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n54.xml | Tests CombiningChar with an illegal character. The character #x0CC9 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n55.xml | Tests CombiningChar with an illegal character. The character #x0CD4 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n56.xml | Tests CombiningChar with an illegal character. The character #x0CD7 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n57.xml | Tests CombiningChar with an illegal character. The character #x0D04 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n58.xml | Tests CombiningChar with an illegal character. The character #x0D45 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n59.xml | Tests CombiningChar with an illegal character. The character #x0D49 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n60.xml | Tests CombiningChar with an illegal character. The character #x0D4E occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n61.xml | Tests CombiningChar with an illegal character. The character #x0D58 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n62.xml | Tests CombiningChar with an illegal character. The character #x0E3F occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n63.xml | Tests CombiningChar with an illegal character. The character #x0E3B occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n64.xml | Tests CombiningChar with an illegal character. The character #x0E4F occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n66.xml | Tests CombiningChar with an illegal character. The character #x0EBA occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n67.xml | Tests CombiningChar with an illegal character. The character #x0EBE occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n68.xml | Tests CombiningChar with an illegal character. The character #x0ECE occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n69.xml | Tests CombiningChar with an illegal character. The character #x0F1A occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n70.xml | Tests CombiningChar with an illegal character. The character #x0F36 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n71.xml | Tests CombiningChar with an illegal character. The character #x0F38 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n72.xml | Tests CombiningChar with an illegal character. The character #x0F3B occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n73.xml | Tests CombiningChar with an illegal character. The character #x0F3A occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n74.xml | Tests CombiningChar with an illegal character. The character #x0F70 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n75.xml | Tests CombiningChar with an illegal character. The character #x0F85 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n76.xml | Tests CombiningChar with an illegal character. The character #x0F8C occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n77.xml | Tests CombiningChar with an illegal character. The character #x0F96 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n78.xml | Tests CombiningChar with an illegal character. The character #x0F98 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n79.xml | Tests CombiningChar with an illegal character. The character #x0FB0 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n80.xml | Tests CombiningChar with an illegal character. The character #x0FB8 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n81.xml | Tests CombiningChar with an illegal character. The character #x0FBA occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n82.xml | Tests CombiningChar with an illegal character. The character #x20DD occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n83.xml | Tests CombiningChar with an illegal character. The character #x20E2 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n84.xml | Tests CombiningChar with an illegal character. The character #x3030 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P87-ibm87n85.xml | Tests CombiningChar with an illegal character. The character #x309B occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n01.xml | Tests Digit with an illegal character. The character #x0029 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n02.xml | Tests Digit with an illegal character. The character #x003B occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n03.xml | Tests Digit with an illegal character. The character #x066A occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n04.xml | Tests Digit with an illegal character. The character #x06FA occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n05.xml | Tests Digit with an illegal character. The character #x0970 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n06.xml | Tests Digit with an illegal character. The character #x09F2 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n08.xml | Tests Digit with an illegal character. The character #x0AF0 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n09.xml | Tests Digit with an illegal character. The character #x0B70 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n10.xml | Tests Digit with an illegal character. The character #x0C65 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n11.xml | Tests Digit with an illegal character. The character #x0CE5 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n12.xml | Tests Digit with an illegal character. The character #x0CF0 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n13.xml | Tests Digit with an illegal character. The character #x0D70 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n14.xml | Tests Digit with an illegal character. The character #x0E5A occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n15.xml | Tests Digit with an illegal character. The character #x0EDA occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P88-ibm88n16.xml | Tests Digit with an illegal character. The character #x0F2A occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n01.xml | Tests Extender with an illegal character. The character #x00B6 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n02.xml | Tests Extender with an illegal character. The character #x00B8 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n03.xml | Tests Extender with an illegal character. The character #x02D2 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n04.xml | Tests Extender with an illegal character. The character #x03FE occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n05.xml | Tests Extender with an illegal character. The character #x065F occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n06.xml | Tests Extender with an illegal character. The character #x0EC7 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n07.xml | Tests Extender with an illegal character. The character #x3006 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n08.xml | Tests Extender with an illegal character. The character #x3030 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n09.xml | Tests Extender with an illegal character. The character #x3036 occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n10.xml | Tests Extender with an illegal character. The character #x309C occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n11.xml | Tests Extender with an illegal character. The character #x309F occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
| B. | ibm-not-wf-P89-ibm89n12.xml | Tests Extender with an illegal character. The character #x30FF occurs as the second character in the PITarget in the PI in the DTD. | (fatal) Illegal processing instruction name, or missing whitespace. [line 3] |
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 | (error) URI "file:/c:/cygwin/home/administrator/xml-test-suite/xmlconf/oasis/a%a&b�<!ELEMENT<!--<?</>?>/\''" has a fragment ID. [line 5] |
| 2.8 | pe01 | Parameter entities must consist of a series of complete markup declarations of the types allowed by the nonterminal markupdecl, interespersed with whitespace or PERefs. | (fatal) Next character must be ";" terminating reference to parameter entity "not-pe". [line 4] |
| 4.2.2 [75] | uri01 | SYSTEM ids may not have URI fragments | (error) URI "file:/c:/cygwin/home/administrator/xml-test-suite/xmlconf/sun/not-wf/foo#bar" has a fragment ID. [line 4] |
| 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) Using original entity definition for "&XML.version;". [line 116] |
| 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) Using original entity definition for "&XML.version;". [line 116] |
| 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) Using original entity definition for "&XML.version;". [line 116] |
| 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. | (warning) Using original entity definition for "<". [line 55] |
| 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. | (warning) Using original entity definition for "<". [line 55] |
| 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. | (warning) Using original entity definition for "<". [line 55] |
This report was produced by Free Software from http://xmlconf.sourceforge.net, and you should be able to reproduce these results yourself.