XML Processor Conformance Report:
org.apache.xerces.parsers.SAXParser

This document is the output of an XML test harness. It reports on the conformance of the following XML 1.0 processor configuration:

XML Processor Xerces 2.0.1
Parser Class org.apache.xerces.parsers.SAXParser
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 Sat Apr 13 18:12:53 PDT 2002
Harness and Version xml.testing.Driver
($Date: 2001/11/06 19:54:11 $)
Runtime Environment Java HotSpot(TM) Client VM 1.4.0-b92 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) 2146
Passed Negative Tests (provisional) 1226
Failed Tests (provisional) 5
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.


Explanation of Tables

Sections presenting test results are composed largely of tables, with explanations focussing on exactly what those tables indicate. Diagnostics for failed tests are presented in italics, with a cherry colored background, to highlight the result. Diagnostics for succesful tests should as a rule only exist for negative tests. 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.

(fatal)
The diagnostic was reported as a fatal error. Such errors are primarily well-formedness errors, such as the violation of XML 1.0 syntax rules or of well formedness constraints. In some underfeatured parser APIs, this may be the only kind of error that gets reported.
(error)
The diagnostic was reported as a recoverable error. Such errors primarily used to report validation errors, which are all violations of validity constraints, but some other errors are also classed as nonfatal.
(warning)
The diagnostic was reported as a warning; warnings are purely informative and may be emitted in a number of cases identified by the XML 1.0 specification (as well as in other cases).

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.

(thrown classname) ... abnormal
The named exception was directly thrown. If the exception is a SAXException (or a subclass thereof) this suggests an error in the parser (violating the SAX API specification) since it should normally have used the SAX ErrorHandler instead.
(odd classname) ... abnormal
After the identified exception was reported through the ErrorHandler, an exception of the named class was thrown directly. This suggests an error in the parser, since the parser either failed to continue after an error (or warning) which is required to be continuable, or else it did not pass the exception thrown by the application back to the application.
(EXCEPTION - DIRECTED FAILURE) ... abnormal
This test case was explicitly failed by the test operator; the test was not run. This may be done in the case of parsers with severe bugs which completely prevented handling the test case, typically because the parser seems to "hang" by entering an infinite loop.

In all cases, negative tests that appear to pass (diagnostics presented with a white background) must be individually examined in the report below. The diagnostic provided by the processor must correspond to the description of the test provided; if the processor does not report the matching error, the seeming "pass" is in fact an error of a type the test harness could not detect or report. That error is either a conformance bug, or an error in the diagnostic being produced; or, 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.


Positive Tests

All conformant XML 1.0 processors must accept "valid" input documents without reporting any errors, and moreover must report the correct output data to the application when processing those documents. Nonvalidating processors (such as this one) must also accept "invalid" input documents without reporting any errors. These are called "Positive Tests" because they ensure that the processor just "does the right thing" without reporting any problems.

In the interest of brevity, the only tests listed here are those which produce diagnostics of some kind, such as test failures. In some cases, warnings may be reported when processing these documents, but these do not indicate failures.

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

Valid Documents

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

Section and [Rules] Test ID Description Diagnostic
Nothing to report!

Output Tests

The XML specification places requirements on the data which is reported by XML processors to applications. This data flows through the 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
Nothing to report!

Invalid Documents

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

Section and [Rules] Test ID Description Diagnostic
Nothing to report!

Negative Tests

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

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

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

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

Documents which are not Well-Formed

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

Section and [Rules] Test ID Description Diagnostic
2.1 ibm-not-wf-P01-ibm01n01.xml Tests a document with no element. A well-formed document should have at lease one elements. (odd SAXParseException) (fatal) Premature end of file.
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. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.1 ibm-not-wf-P01-ibm01n03.xml Tests a document with wrong combination of misc and element. One PI occurs between two elements. (odd SAXParseException) (fatal) The markup in the document following the root element must be well-formed. [line 8] [column 2]
2.1 [1] not-wf-sa-050 Empty document, with no root element. (odd SAXParseException) (fatal) Premature end of file.
2.1 [1] o-p01fail1 S cannot occur before the prolog (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.1 [1] o-p01fail2 comments cannot occur before the prolog (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 1] [column 24]
2.1 [1] o-p01fail3 only one document element (odd SAXParseException) (fatal) The markup in the document following the root element must be well-formed. [line 1] [column 8]
2.1 [1] o-p01fail4 document element must be complete. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 1] [column 6]
2.2 ibm-not-wf-P02-ibm02n01.xml Tests a comment which contains an illegal Char: #x00 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x0) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n02.xml Tests a comment which contains an illegal Char: #x01 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n03.xml Tests a comment which contains an illegal Char: #x02 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x2) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n04.xml Tests a comment which contains an illegal Char: #x03 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x3) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n05.xml Tests a comment which contains an illegal Char: #x04 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x4) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n06.xml Tests a comment which contains an illegal Char: #x05 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n07.xml Tests a comment which contains an illegal Char: #x06 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x6) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n08.xml Tests a comment which contains an illegal Char: #x07 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x7) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n09.xml Tests a comment which contains an illegal Char: #x08 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x8) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n10.xml Tests a comment which contains an illegal Char: #x0B (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xb) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n11.xml Tests a comment which contains an illegal Char: #x0C (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xc) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n12.xml Tests a comment which contains an illegal Char: #x0E (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xe) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n13.xml Tests a comment which contains an illegal Char: #x0F (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xf) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n14.xml Tests a comment which contains an illegal Char: #x10 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x10) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n15.xml Tests a comment which contains an illegal Char: #x11 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x11) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n16.xml Tests a comment which contains an illegal Char: #x12 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x12) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n17.xml Tests a comment which contains an illegal Char: #x13 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x13) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n18.xml Tests a comment which contains an illegal Char: #x14 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x14) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n19.xml Tests a comment which contains an illegal Char: #x15 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x15) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n20.xml Tests a comment which contains an illegal Char: #x16 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x16) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n21.xml Tests a comment which contains an illegal Char: #x17 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x17) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n22.xml Tests a comment which contains an illegal Char: #x18 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x18) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n23.xml Tests a comment which contains an illegal Char: #x19 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x19) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n24.xml Tests a comment which contains an illegal Char: #x1A (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1a) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n25.xml Tests a comment which contains an illegal Char: #x1B (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1b) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n26.xml Tests a comment which contains an illegal Char: #x1C (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1c) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n27.xml Tests a comment which contains an illegal Char: #x1D (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1d) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n28.xml Tests a comment which contains an illegal Char: #x1E (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1e) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n29.xml Tests a comment which contains an illegal Char: #x1F (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1f) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n30.xml Tests a comment which contains an illegal Char: #xD800 (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xd800) was found in the element content of the document. [line 5] [column 11]
2.2 ibm-not-wf-P02-ibm02n31.xml Tests a comment which contains an illegal Char: #xDFFF (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xdfff) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n32.xml Tests a comment which contains an illegal Char: #xFFFE (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xfffe) was found in the comment. [line 5] [column 10]
2.2 ibm-not-wf-P02-ibm02n33.xml Tests a comment which contains an illegal Char: #xFFFF (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xffff) was found in the comment. [line 5] [column 10]
2.2 ibm-valid-P02-ibm02v01.xml Contains malformed UTF-8 characters. (thrown IOException) invalid byte 4 of 4-byte UTF-8 sequence (0x80)
2.2 [2] not-wf-sa-030 A form feed is not a legal XML character. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xc) was found in the element content of the document. [line 1] [column 19]
2.2 [2] not-wf-sa-031 A form feed is not a legal XML character. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xc) was found in the processing instruction. [line 1] [column 24]
2.2 [2] not-wf-sa-032 A form feed is not a legal XML character. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xc) was found in the comment. [line 1] [column 24]
2.2 [2] not-wf-sa-033 An ESC (octal 033) is not a legal XML character. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1b) was found in the element content of the document. [line 1] [column 9]
2.2 [2] not-wf-sa-034 A form feed is not a legal XML character. (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 5]
2.2 [2] not-wf-sa-142 Character #x0000 is not legal anywhere in an XML document. (odd SAXParseException) (fatal) Character reference "&#0" is an invalid XML character. [line 4] [column 10]
2.2 [2] not-wf-sa-143 Character #x001F is not legal anywhere in an XML document. (odd SAXParseException) (fatal) Character reference "&#1f" is an invalid XML character. [line 4] [column 11]
2.2 [2] not-wf-sa-144 Character #xFFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) Character reference "&#ffff" is an invalid XML character. [line 4] [column 14]
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.) (odd SAXParseException) (fatal) Character reference "&#d800" is an invalid XML character. [line 4] [column 14]
2.2 [2] not-wf-sa-146 Character references must also refer to legal XML characters; #x00110000 is one more than the largest legal character. (odd SAXParseException) (fatal) Character reference "&#110000" is an invalid XML character. [line 4] [column 16]
2.2 [2] not-wf-sa-166 Character FFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xffff) was found in the element content of the document. [line 1] [column 6]
2.2 [2] not-wf-sa-167 Character FFFE is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xfffe) was found in the element content of the document. [line 1] [column 6]
2.2 [2] not-wf-sa-168 An unpaired surrogate (D800) is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xd800) was found in the element content of the document. [line 1] [column 7]
2.2 [2] not-wf-sa-169 An unpaired surrogate (DC00) is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xdc00) was found in the element content of the document. [line 1] [column 6]
2.2 [2] not-wf-sa-170 Four byte UTF-8 encodings can encode UCS-4 characters which are beyond the range of legal XML characters (and can't be expressed in Unicode surrogate pairs). This document holds such a character. (thrown IOException) high surrogate bits in UTF-8 sequence must not exceed 0x10 but found 0x1c
2.2 [2] not-wf-sa-171 Character FFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xffff) was found in the comment. [line 1] [column 6]
2.2 [2] not-wf-sa-172 Character FFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xffff) was found in the processing instruction. [line 1] [column 6]
2.2 [2] not-wf-sa-173 Character FFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x{2}) was found in the value of attribute "{1}". [line 1] [column 9]
2.2 [2] not-wf-sa-174 Character FFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xffff) was found in the CDATA section. [line 1] [column 15]
2.2 [2] not-wf-sa-175 Character FFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) InvalidCharInLiteral [line 3] [column 15]
2.2 [2] not-wf-sa-177 Character FFFF is not legal anywhere in an XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xffff) was found in the element content of the document. [line 4] [column 7]
2.2 [2] o-p02fail1 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x0) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail10 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xb) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail11 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xc) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail12 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xe) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail13 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xf) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail14 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x10) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail15 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x11) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail16 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x12) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail17 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x13) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail18 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x14) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail19 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x15) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail2 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail20 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x16) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail21 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x17) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail22 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x18) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail23 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x19) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail24 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1a) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail25 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1b) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail26 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1c) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail27 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1d) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail28 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1e) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail29 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x1f) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail3 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x2) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail30 Use of illegal character within XML document. (thrown IOException) Reversed byte-order mark
2.2 [2] o-p02fail31 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0xffff) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail4 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x3) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail5 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x4) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail6 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail7 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x6) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail8 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x7) was found in the element content of the document. [line 1] [column 6]
2.2 [2] o-p02fail9 Use of illegal character within XML document. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x8) was found in the element content of the document. [line 1] [column 6]
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". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x0) was found in the comment. [line 5] [column 11]
2.3 ibm-not-wf-P04-ibm04n01.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x21 (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n02.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x28 (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n03.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x29 (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n04.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2B (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n05.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2C (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n06.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2F (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n07.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3B (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n08.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3C (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n09.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3D (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n10.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3F (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n11.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5B (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 1] [column 28]
2.3 ibm-not-wf-P04-ibm04n12.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5C (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n13.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5D (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n14.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5E (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n15.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x60 (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n16.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7B (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n17.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7C (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
2.3 ibm-not-wf-P04-ibm04n18.xml Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7D (odd SAXParseException) (fatal) The document type declaration for root element type "IllegalNameChar" must end with '>'. [line 1] [column 26]
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.". (odd SAXParseException) (fatal) The root element type must appear after "<!DOCTYPE" in the document type declaration. [line 1] [column 11]
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-". (odd SAXParseException) (fatal) The root element type must appear after "<!DOCTYPE" in the document type declaration. [line 1] [column 11]
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". (odd SAXParseException) (fatal) The root element type must appear after "<!DOCTYPE" in the document type declaration. [line 1] [column 11]
2.3 ibm-not-wf-P09-ibm09n01.xml Tests an internal general entity with an invalid value. The entity "Fullname" contains "%". (odd SAXParseException) (fatal) The parameter entity reference "%Man;" must end with the ';' delimiter. [line 4] [column 30]
2.3 ibm-not-wf-P09-ibm09n02.xml Tests an internal general entity with an invalid value. The entity "Fullname" contains the ampersand character. (odd SAXParseException) (fatal) The reference to entity "Man" must end with the ';' delimiter. [line 4] [column 30]
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. (odd SAXParseException) (fatal) The declaration for the entity "FullName" must end with '>'. [line 4] [column 26]
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". (odd SAXParseException) (fatal) Premature end of file.
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". (odd SAXParseException) (fatal) The value of attribute "first" must not contain the '<' character. [line 14] [column 21]
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. (odd SAXParseException) (fatal) The reference to entity "Man" must end with the ';' delimiter. [line 14] [column 25]
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. (odd SAXParseException) (fatal) Element type "student" must be followed by either attribute specifications, ">" or "/>". [line 14] [column 22]
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". (odd SAXParseException) (fatal) The value of attribute "first" must not contain the '<' character. [line 14] [column 43]
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". (odd SAXParseException) (fatal) The value of attribute "first" must not contain the '<' character. [line 14] [column 21]
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. (odd SAXParseException) (fatal) The reference to entity "Man" must end with the ';' delimiter. [line 14] [column 25]
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. (odd SAXParseException) (fatal) Element type "student" must be followed by either attribute specifications, ">" or "/>". [line 14] [column 22]
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". (odd SAXParseException) (fatal) The value of attribute "first" must not contain the '<' character. [line 14] [column 43]
2.3 ibm-not-wf-P11-ibm11n01.xml Tests SystemLiteral. The systemLiteral for the element "student" has a double quote character in the middle. (odd SAXParseException) (fatal) The document type declaration for root element type "student" must end with '>'. [line 2] [column 35]
2.3 ibm-not-wf-P11-ibm11n02.xml Tests SystemLiteral. The systemLiteral for the element "student" has a single quote character in the middle. (odd SAXParseException) (fatal) The document type declaration for root element type "student" must end with '>'. [line 2] [column 35]
2.3 ibm-not-wf-P11-ibm11n03.xml Tests SystemLiteral. The closing bracket (double quote) is missing with the systemLiteral for the element "student". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 8] [column 1]
2.3 ibm-not-wf-P11-ibm11n04.xml Tests SystemLiteral. The closing bracket (single quote) is missing with the systemLiteral for the element "student". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 8] [column 1]
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". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5c) was found in the public identifier. [line 4] [column 27]
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.. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5c) was found in the public identifier. [line 4] [column 27]
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". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5c) was found in the public identifier. [line 4] [column 27]
2.3 ibm-not-wf-P13-ibm13n01.xml Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character "{". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x7b) was found in the public identifier. [line 3] [column 35]
2.3 ibm-not-wf-P13-ibm13n02.xml Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character "~". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x7e) was found in the public identifier. [line 3] [column 39]
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. (thrown IOException) invalid byte 2 of 3-byte UTF-8 sequence (0x20)
2.3 [10] not-wf-sa-012 SGML-ism: attribute values must be quoted in all cases. (odd SAXParseException) (fatal) Open quote is expected for attribute "a1|". [line 1] [column 9]
2.3 [10] not-wf-sa-013 The quotes on both ends of an attribute value must match. (odd SAXParseException) (fatal) The value of attribute "a1" must not contain the '<' character. [line 1] [column 14]
2.3 [10] not-wf-sa-014 Attribute values may not contain literal '<' characters. (odd SAXParseException) (fatal) The value of attribute "a1" must not contain the '<' character. [line 1] [column 10]
2.3 [10] not-wf-sa-020 Attribute values may not contain literal '&' characters except as part of an entity reference. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 1] [column 13]
2.3 [10] not-wf-sa-021 Attribute values may not contain literal '&' characters except as part of an entity reference. (odd SAXParseException) (fatal) The reference to entity "b" must end with the ';' delimiter. [line 1] [column 13]
2.3 [10] not-wf-sa-088 Attribute values are terminated by literal quote characters, and any entity expansion is done afterwards. (odd SAXParseException) (fatal) The value of attribute "a" must not contain the '<' character. [line 6] [column 13]
2.3 [10] not-wf-sa-090 Attributes may not contain a literal "<" character; this one has one because of reference expansion. (odd SAXParseException) (fatal) The value of attribute "a" must not contain the '<' character.
2.3 [10] o-p10fail1 attribute values exclude '<' (odd SAXParseException) (fatal) The value of attribute "a" must not contain the '<' character. [line 1] [column 11]
2.3 [10] o-p10fail2 attribute values exclude '&' (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 1] [column 12]
2.3 [10] o-p10fail3 quote types must match (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 2] [column 2]
2.3 [11] o-p11fail1 quote types must match (odd SAXParseException) (fatal) Premature end of file.
2.3 [11] o-p11fail2 cannot contain delimiting quotes (odd SAXParseException) (fatal) The declaration for the notation "not1" must end with '>'. [line 5] [column 26]
2.3 [12] o-p12fail1 '"' excluded (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x22) was found in the public identifier. [line 5] [column 26]
2.3 [12] o-p12fail2 '\' excluded (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5c) was found in the public identifier. [line 5] [column 26]
2.3 [12] o-p12fail3 entity references excluded (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x26) was found in the public identifier. [line 6] [column 26]
2.3 [12] o-p12fail4 '>' excluded (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x3e) was found in the public identifier. [line 5] [column 26]
2.3 [12] o-p12fail5 '<' excluded (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x3c) was found in the public identifier. [line 5] [column 26]
2.3 [12] o-p12fail6 built-in entity refs excluded (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x26) was found in the public identifier. [line 5] [column 26]
2.3 [12] pubid01 Illegal entity ref in public ID (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x26) was found in the public identifier. [line 6] [column 33]
2.3 [12] pubid02 Illegal characters in public ID (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x3c) was found in the public identifier. [line 6] [column 25]
2.3 [12] pubid03 Illegal characters in public ID (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5b) was found in the public identifier. [line 6] [column 25]
2.3 [12] pubid04 Illegal characters in public ID (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x7b) was found in the public identifier. [line 6] [column 25]
2.3 [12] pubid05 SGML-ism: public ID without system ID (odd SAXParseException) (fatal) White spaces are required between publicId and systemId. [line 5] [column 44]
2.3 [13] not-wf-sa-085 Public IDs may not contain "[". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5b) was found in the public identifier. [line 1] [column 24]
2.3 [13] not-wf-sa-086 Public IDs may not contain "[". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5b) was found in the public identifier. [line 2] [column 23]
2.3 [13] not-wf-sa-087 Public IDs may not contain "[". (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5b) was found in the public identifier. [line 2] [column 25]
2.3 [13] o-p12fail7 The public ID has a tab character, which is disallowed (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x9) was found in the public identifier. [line 5] [column 26]
2.3 [3] o-p03fail1 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail10 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail11 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail12 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail13 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail14 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail15 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail16 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail17 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail18 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail19 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail2 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail20 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail21 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail22 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail23 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail24 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail25 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail26 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail27 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail28 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail29 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail3 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail4 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail5 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail7 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail8 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [3] o-p03fail9 Use of illegal character within XML document. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 1]
2.3 [4] not-wf-sa-002 Names may not start with "."; it's not a Letter. (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 2] [column 2]
2.3 [4] not-wf-sa-140 Character '&#x309a;' is a CombiningChar, not a Letter, and so may not begin a name. (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup.
2.3 [4] o-p04fail1 Name contains invalid character. (odd SAXParseException) (fatal) Element type "A" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 3]
2.3 [4] o-p04fail2 Name contains invalid character. (odd SAXParseException) (fatal) Element type "A" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 3]
2.3 [4] o-p04fail3 Name contains invalid character. (odd SAXParseException) (fatal) Element type "A" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 3]
2.3 [5] not-wf-sa-008 Entity references must include names, which don't begin with '.' (it's not a Letter or other name start character). (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 1] [column 7]
2.3 [5] not-wf-sa-023 Digits are not valid name start characters. (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 6]
2.3 [5] not-wf-sa-024 Digits are not valid name start characters. (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 2] [column 2]
2.3 [5] not-wf-sa-141 Character #x0E5C is not legal in XML names. (odd SAXParseException) (fatal) Element type "X" must be followed by either attribute specifications, ">" or "/>".
2.3 [5] o-p05fail1 a Name cannot start with a digit (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
2.3 [5] o-p05fail2 a Name cannot start with a '.' (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
2.3 [5] o-p05fail3 a Name cannot start with a "-" (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
2.3 [5] o-p05fail4 a Name cannot start with a CombiningChar (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
2.3 [5] o-p05fail5 a Name cannot start with an Extender (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
2.3 [9] not-wf-sa-113 Parameter entity values must use valid reference syntax; this reference is malformed. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 2] [column 18]
2.3 [9] not-wf-sa-114 General entity values must use valid reference syntax; this reference is malformed. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 2] [column 16]
2.3 [9] not-wf-sa-159 Uses '&' unquoted in an entity declaration, which is illegal syntax for an entity reference. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 3] [column 27]
2.3 [9] o-p09fail1 EntityValue excludes '%' (odd SAXParseException) (fatal) The entity name must immediately follow the '%' in the parameter entity reference. [line 2] [column 23]
2.3 [9] o-p09fail2 EntityValue excludes '&' (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 2] [column 23]
2.3 [9] o-p09fail3 incomplete character reference (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 4] [column 26]
2.3 [9] o-p09fail4 quote types must match (odd SAXParseException) (fatal) Premature end of file.
2.3 [9] o-p09fail5 quote types must match (odd SAXParseException) (fatal) Premature end of file.
2.4 ibm-not-wf-P14-ibm14n01.xml Tests CharData. The content of the element "student" contains the character "[[>". (odd SAXParseException) (fatal) The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section. [line 9] [column 42]
2.4 ibm-not-wf-P14-ibm14n02.xml Tests CharData. The content of the element "student" contains the character "less than". (odd SAXParseException) (fatal) Element type "Man" must be followed by either attribute specifications, ">" or "/>". [line 9] [column 44]
2.4 ibm-not-wf-P14-ibm14n03.xml Tests CharData. The content of the element "student" contains the character ampersand. (odd SAXParseException) (fatal) The reference to entity "Man" must end with the ';' delimiter. [line 9] [column 42]
2.4 [14] not-wf-sa-025 Text may not contain a literal ']]>' sequence. (odd SAXParseException) (fatal) The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section. [line 1] [column 9]
2.4 [14] not-wf-sa-026 Text may not contain a literal ']]>' sequence. (odd SAXParseException) (fatal) The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section. [line 1] [column 10]
2.4 [14] not-wf-sa-029 Text may not contain a literal ']]>' sequence. (odd SAXParseException) (fatal) The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section. [line 1] [column 13]
2.4 [14] o-p14fail1 '<' excluded (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 1] [column 7]
2.4 [14] o-p14fail2 '&' excluded (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 1] [column 7]
2.4 [14] o-p14fail3 "]]>" excluded (odd SAXParseException) (fatal) The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section. [line 1] [column 10]
2.5 ibm-not-wf-P15-ibm15n01.xml Tests comment. The text of the second comment contains the character "-". (odd SAXParseException) (fatal) The string "--" is not permitted within comments. [line 7] [column 7]
2.5 ibm-not-wf-P15-ibm15n02.xml Tests comment. The second comment has a wrong closing sequence "-(greater than)". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 8] [column 40]
2.5 ibm-not-wf-P15-ibm15n03.xml Tests comment. The second comment has a wrong beginning sequence "(less than)!-". (odd SAXParseException) (fatal) Comment must start with "<!--". [line 7] [column 4]
2.5 ibm-not-wf-P15-ibm15n04.xml Tests comment. The closing sequence is missing with the second comment. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 8] [column 40]
2.5 [15] not-wf-sa-027 Comments must be terminated with "-->". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 4] [column 1]
2.5 [15] o-p15fail1 comments can't end in '-' (odd SAXParseException) (fatal) The string "--" is not permitted within comments. [line 1] [column 8]
2.5 [15] o-p15fail2 one comment per comment (contrasted with SGML) (odd SAXParseException) (fatal) The string "--" is not permitted within comments. [line 1] [column 8]
2.5 [15] o-p15fail3 can't include 2 or more adjacent '-'s (odd SAXParseException) (fatal) The string "--" is not permitted within comments. [line 1] [column 8]
2.5 [15] sgml03 Comments may not contain "--" (odd SAXParseException) (fatal) The string "--" is not permitted within comments. [line 3] [column 23]
2.5 [16] not-wf-sa-006 XML comments may not contain "--" (odd SAXParseException) (fatal) The string "--" is not permitted within comments. [line 1] [column 23]
2.5 [16] not-wf-sa-070 XML comments may not contain "--" (odd SAXParseException) (fatal) The string "--" is not permitted within comments. [line 1] [column 43]
2.6 ibm-not-wf-P16-ibm16n01.xml Tests PI. The content of the PI includes the sequence "(less than)?". (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 7] [column 25]
2.6 ibm-not-wf-P16-ibm16n02.xml Tests PI. The PITarget is missing in the PI. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 8] [column 3]
2.6 ibm-not-wf-P16-ibm16n03.xml Tests PI. The PI has a wrong closing sequence ">". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 9] [column 40]
2.6 ibm-not-wf-P16-ibm16n04.xml Tests PI. The closing sequence is missing in the PI. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 9] [column 40]
2.6 ibm-not-wf-P17-ibm17n01.xml Tests PITarget. The PITarget contains the string "XML". (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 8] [column 6]
2.6 ibm-not-wf-P17-ibm17n02.xml Tests PITarget. The PITarget contains the string "xML". (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 7] [column 6]
2.6 ibm-not-wf-P17-ibm17n03.xml Tests PITarget. The PITarget contains the string "xml". (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 7] [column 6]
2.6 ibm-not-wf-P17-ibm17n04.xml Tests PITarget. The PITarget contains the string "xmL". (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 7] [column 6]
2.6 [16] not-wf-sa-003 Processing Instruction target name is required. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 1] [column 8]
2.6 [16] not-wf-sa-004 SGML-ism: processing instructions end in '?>' not '>'. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 2] [column 1]
2.6 [16] not-wf-sa-005 Processing instructions end in '?>' not '?'. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 2] [column 1]
2.6 [16] not-wf-sa-028 Processing instructions must end with '?>'. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 5] [column 1]
2.6 [16] o-p16fail1 "xml" is an invalid PITarget (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.6 [16] o-p16fail2 a PITarget must be present (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 1] [column 3]
2.6 [16] pi No space between PI target name and data (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 4] [column 9]
2.6 [17] not-wf-ext-sa-003 Only one text declaration is permitted; a second one looks like an illegal processing instruction (target names of "xml" in any case are not allowed). (odd SAXParseException) (fatal) more pseudo attributes is expected. [line 1] [column 20]
2.6 [17] not-wf-not-sa-002 Processing instruction target names may not be "XML" in any combination of cases. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed.
2.6 [17] not-wf-sa-157 '<?xmL ...?>' is not a legal processing instruction target name. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.7 ibm-not-wf-P18-ibm18n01.xml Tests CDSect. The CDStart is missing in the CDSect in the content of element "student". (odd SAXParseException) (fatal) The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section. [line 7] [column 54]
2.7 ibm-not-wf-P18-ibm18n02.xml Tests CDSect. The CDEnd is missing in the CDSect in the content of element "student". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 7] [column 71]
2.7 ibm-not-wf-P19-ibm19n01.xml Tests CDStart. The CDStart contains a lower case string "cdata". (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 3]
2.7 ibm-not-wf-P19-ibm19n02.xml Tests CDStart. The CDStart contains an extra character "[". (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 3]
2.7 ibm-not-wf-P19-ibm19n03.xml Tests CDStart. The CDStart contains a wrong character "?". (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 7] [column 3]
2.7 ibm-not-wf-P20-ibm20n01.xml Tests CDATA with an illegal sequence. The CDATA contains the string "[[>". (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 3]
2.7 ibm-not-wf-P21-ibm21n01.xml Tests CDEnd. One "]" is missing in the CDEnd. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 3]
2.7 ibm-not-wf-P21-ibm21n02.xml Tests CDEnd. An extra "]" is placed in the CDEnd. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 3]
2.7 ibm-not-wf-P21-ibm21n03.xml Tests CDEnd. A wrong character ")" is placed in the CDEnd. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 3]
2.7 not-wf-sa-105 Invalid placement of CDATA section. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 2] [column 3]
2.7 [18] not-wf-sa-017 CDATA sections need a terminating ']]>'. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 2] [column 1]
2.7 [18] not-wf-sa-051 CDATA is invalid at top level of document. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 2] [column 3]
2.7 [18] not-wf-sa-128 Invalid CDATA syntax. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 2] [column 15]
2.7 [18] o-p18fail1 no space before "CDATA" (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 1] [column 8]
2.7 [18] o-p18fail2 no space after "CDATA" (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 1] [column 8]
2.7 [18] o-p18fail3 CDSect's can't nest (odd SAXParseException) (fatal) The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section. [line 4] [column 4]
2.7 [19] not-wf-sa-018 CDATA sections begin with a literal '<![CDATA[', no space. (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 1] [column 8]
2.7 [19] not-wf-sa-108 No space in '<![CDATA['. (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 2] [column 3]
2.7 [19] not-wf-sa-112 CDATA sections start '<![CDATA[', not '<!cdata['. (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 2] [column 3]
2.8 ibm-not-wf-P22-ibm22n01.xml Tests prolog with wrong field ordering. The XMLDecl occurs after the DTD. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 4] [column 6]
2.8 ibm-not-wf-P22-ibm22n02.xml Tests prolog with wrong field ordering. The Misc (comment) occurs before the XMLDecl. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
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. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 6] [column 6]
2.8 ibm-not-wf-P23-ibm23n01.xml Tests XMLDecl with a required field missing. The Versioninfo is missing in the XMLDecl. (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 23]
2.8 ibm-not-wf-P23-ibm23n02.xml Tests XMLDecl with wrong field ordering. The VersionInfo occurs after the EncodingDecl. (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 23]
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. (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 23]
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. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 1] [column 6]
2.8 ibm-not-wf-P23-ibm23n05.xml Tests XMLDecl with a wrong closing sequence ">". (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 55]
2.8 ibm-not-wf-P23-ibm23n06.xml Tests XMLDecl with a wrong opening sequence "(less than)!". (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 3]
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. (odd SAXParseException) (fatal) The value following "version" in the XML declaration must be a quoted string. [line 1] [column 16]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 1] [column 13]
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. (odd SAXParseException) (fatal) The ' = ' character must follow "version" in the XML declaration. [line 1] [column 14]
2.8 ibm-not-wf-P24-ibm24n04.xml Tests VersionInfo with wrong field ordering. The VersionNum occurs before "=" and "version". (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 7]
2.8 ibm-not-wf-P24-ibm24n05.xml Tests VersionInfo with wrong field ordering. The "=" occurs after "version" and the VersionNum. (odd SAXParseException) (fatal) The ' = ' character must follow "version" in the XML declaration. [line 1] [column 14]
2.8 ibm-not-wf-P24-ibm24n06.xml Tests VersionInfo with the wrong key word "Version". (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 20]
2.8 ibm-not-wf-P24-ibm24n07.xml Tests VersionInfo with the wrong key word "versioN". (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 20]
2.8 ibm-not-wf-P24-ibm24n08.xml Tests VersionInfo with mismatched quotes around the VersionNum. version = '1.0" is used as the VersionInfo. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 6] [column 41]
2.8 ibm-not-wf-P24-ibm24n09.xml Tests VersionInfo with mismatched quotes around the VersionNum. The closing bracket for the VersionNum is missing. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 6] [column 41]
2.8 ibm-not-wf-P25-ibm25n01.xml Tests eq with a wrong key word "==". (odd SAXParseException) (fatal) The value following "version" in the XML declaration must be a quoted string. [line 1] [column 15]
2.8 ibm-not-wf-P25-ibm25n02.xml Tests eq with a wrong key word "eq". (odd SAXParseException) (fatal) The ' = ' character must follow "version" in the XML declaration. [line 1] [column 15]
2.8 ibm-not-wf-P26-ibm26n01.xml Tests VersionNum with an illegal character "#". (odd SAXParseException) (fatal) XML version "_#1.0" is not supported, only XML 1.0 is supported. [line 1] [column 22]
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". (odd SAXParseException) (fatal) Comment must start with "<!--". [line 6] [column 3]
2.8 ibm-not-wf-P28-ibm28n01.xml Tests doctypedecl with a required field missing. The Name "animal" is missing in the doctypedecl. (odd SAXParseException) (fatal) The document type declaration for root element type "SYSTEM" must end with '>'. [line 2] [column 18]
2.8 ibm-not-wf-P28-ibm28n02.xml Tests doctypedecl with wrong field ordering. The Name "animal" occurs after the markup declarations inside the "[]". (odd SAXParseException) (fatal) The root element type must appear after "<!DOCTYPE" in the document type declaration. [line 2] [column 11]
2.8 ibm-not-wf-P28-ibm28n03.xml Tests doctypedecl with wrong field ordering. The Name "animal" occurs after the markup declarations inside the "[]". (odd SAXParseException) (fatal) The document type declaration for root element type "SYSTEM" must end with '>'. [line 2] [column 18]
2.8 ibm-not-wf-P28-ibm28n04.xml Tests doctypedecl with general entity reference.The "(ampersand)generalE" occurs in the DTD. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 5] [column 4]
2.8 ibm-not-wf-P28-ibm28n05.xml Tests doctypedecl with wrong key word. A wrong key word "DOCtYPE" occurs on line 2. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 2] [column 3]
2.8 ibm-not-wf-P28-ibm28n06.xml Tests doctypedecl with mismatched brackets. The closing bracket "]" of the DTD is missing. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 4] [column 1]
2.8 ibm-not-wf-P28-ibm28n07.xml Tests doctypedecl with wrong bracket. The opening bracket "}" occurs in the DTD. (odd SAXParseException) (fatal) The document type declaration for root element type "animal" must end with '>'. [line 2] [column 18]
2.8 ibm-not-wf-P28-ibm28n08.xml Tests doctypedecl with wrong opening sequence. The opening sequence "(less than)?DOCTYPE" occurs in the DTD. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 7] [column 1]
2.8 ibm-not-wf-P29-ibm29n01.xml Tests markupdecl with an illegal markup declaration. A XMLDecl occurs inside the DTD. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 9]
2.8 ibm-not-wf-P29-ibm29n02.xml Tests WFC "PEs in Internal Subset". A PE reference occurs inside an elementdecl in the DTD. (odd SAXParseException) (fatal) The element type is required in the element type declaration. [line 5] [column 14]
2.8 ibm-not-wf-P29-ibm29n03.xml Tests WFC "PEs in Internal Subset". A PE reference occurs inside an ATTlistDecl in the DTD. (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "animal". [line 5] [column 21]
2.8 ibm-not-wf-P29-ibm29n04.xml Tests WFC "PEs in Internal Subset". A PE reference occurs inside an EntityDecl in the DTD. (odd SAXParseException) (fatal) The parameter entity reference "%parameterE;" cannot occur within markup in the internal subset of the DTD. [line 5] [column 34]
2.8 ibm-not-wf-P29-ibm29n05.xml Tests WFC "PEs in Internal Subset". A PE reference occurs inside a PI in the DTD. (odd SAXParseException) (fatal) Premature end of file.
2.8 ibm-not-wf-P29-ibm29n06.xml Tests WFC "PEs in Internal Subset". A PE reference occurs inside a comment in the DTD. (odd SAXParseException) (fatal) Premature end of file.
2.8 ibm-not-wf-P29-ibm29n07.xml Tests WFC "PEs in Internal Subset". A PE reference occurs inside a NotationDecl in the DTD. (odd SAXParseException) (fatal) The name of the notation is required in the notation declaration. [line 5] [column 15]
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). (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.8 ibm-not-wf-P31-ibm31n01.xml Tests extSubsetDecl with an illegal field. A general entity reference occurs in file "ibm31n01.dtd". (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 4] [column 1]
2.8 not-wf-sa-160 Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. (odd SAXParseException) (fatal) The parameter entity reference "%e;" cannot occur within markup in the internal subset of the DTD. [line 4] [column 18]
2.8 not-wf-sa-161 Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 3] [column 16]
2.8 not-wf-sa-162 Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. (odd SAXParseException) (fatal) The parameter entity reference "%e1;" cannot occur within markup in the internal subset of the DTD. [line 4] [column 20]
2.8 sgml02 XML declaration must be at the very beginning of a document; it"s not a processing instruction (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 1] [column 7]
2.8 2.6 [23, 17] not-wf-sa-154 '<?XML ...?>' is neither an XML declaration nor a legal processing instruction target name. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 1] [column 6]
2.8 2.6 [23, 17] not-wf-sa-155 '<?xmL ...?>' is neither an XML declaration nor a legal processing instruction target name. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 1] [column 6]
2.8 2.6 [23, 17] not-wf-sa-156 '<?xMl ...?>' is neither an XML declaration nor a legal processing instruction target name. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.8 [22] not-wf-sa-147 XML Declaration may not be preceded by whitespace. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.8 [22] not-wf-sa-148 XML Declaration may not be preceded by comments or whitespace. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.8 [22] not-wf-sa-152 XML declarations must include the "version=..." string. (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 23]
2.8 [22] o-p22fail1 prolog must start with XML decl (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
2.8 [22] o-p22fail2 prolog must start with XML decl (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 4] [column 6]
2.8 [23] not-wf-sa-095 VersionInfo must come before EncodingDecl. (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 23]
2.8 [23] not-wf-sa-098 Only one "version=..." string may appear in an XML declaration. (odd SAXParseException) (fatal) The encoding declaration is required in the text declaration. [line 1] [column 34]
2.8 [23] not-wf-sa-099 Only three pseudo-attributes are in the XML declaration, and "valid=..." is not one of them. (odd SAXParseException) (fatal) The encoding declaration is required in the text declaration. [line 1] [column 31]
2.8 [23] o-p23fail1 "xml" must be lower-case (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 1] [column 6]
2.8 [23] o-p23fail2 VersionInfo must be supplied (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 23]
2.8 [23] o-p23fail3 VersionInfo must come first (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 23]
2.8 [23] o-p23fail4 SDDecl must come last (odd SAXParseException) (fatal) no more pseudo attributes is allowed. [line 1] [column 54]
2.8 [23] o-p23fail5 no SGML-type PIs (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 20]
2.8 [23] o-p39fail4 XML declarations must be correctly terminated (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 20]
2.8 [23] o-p39fail5 XML declarations must be correctly terminated (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 20]
2.8 [24] not-wf-sa-094 Prolog VERSION must be lowercase. (odd SAXParseException) (fatal) The version is required in the XML declaration. [line 1] [column 20]
2.8 [24] not-wf-sa-097 Both quotes surrounding VersionNum must be the same. (odd SAXParseException) (fatal) XML version "1.0' encoding=" is not supported, only XML 1.0 is supported. [line 1] [column 31]
2.8 [24] o-p24fail1 quote types must match (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 3] [column 1]
2.8 [24] o-p24fail2 quote types must match (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 3] [column 1]
2.8 [25] o-p25fail1 Comment is illegal in VersionInfo. (odd SAXParseException) (fatal) The ' = ' character must follow "version" in the XML declaration. [line 1] [column 15]
2.8 [26] not-wf-sa-102 Provides an illegal XML version number; spaces are illegal. (odd SAXParseException) (fatal) XML version "1.0 " is not supported, only XML 1.0 is supported. [line 1] [column 21]
2.8 [26] o-p26fail1 Illegal character in VersionNum. (odd SAXParseException) (fatal) XML version "1.0?" is not supported, only XML 1.0 is supported. [line 1] [column 21]
2.8 [26] o-p26fail2 Illegal character in VersionNum. (odd SAXParseException) (fatal) XML version "1.0^" is not supported, only XML 1.0 is supported. [line 1] [column 21]
2.8 [27] not-wf-sa-036 Text may not appear after the root element. (odd SAXParseException) (fatal) Content is not allowed in trailing section. [line 2] [column 1]
2.8 [27] not-wf-sa-037 Character references may not appear after the root element. (odd SAXParseException) (fatal) Content is not allowed in trailing section. [line 2] [column 1]
2.8 [27] not-wf-sa-040 Provides two document elements. (odd SAXParseException) (fatal) The markup in the document following the root element must be well-formed. [line 2] [column 2]
2.8 [27] not-wf-sa-041 Provides two document elements. (odd SAXParseException) (fatal) The markup in the document following the root element must be well-formed. [line 2] [column 2]
2.8 [27] not-wf-sa-043 Provides #PCDATA text after the document element. (odd SAXParseException) (fatal) Content is not allowed in trailing section. [line 2] [column 1]
2.8 [27] not-wf-sa-044 Provides two document elements. (odd SAXParseException) (fatal) The markup in the document following the root element must be well-formed. [line 1] [column 8]
2.8 [27] not-wf-sa-048 Provides a CDATA section after the roor element. (odd SAXParseException) (fatal) Comment must start with "<!--". [line 3] [column 3]
2.8 [27] not-wf-sa-151 XML declarations may not follow document content. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 3] [column 6]
2.8 [27] o-p27fail1 References aren't allowed in Misc, even if they would resolve to valid Misc. (odd SAXParseException) (fatal) Reference is not allowed in prolog. [line 2] [column 2]
2.8 [28] not-wf-sa-055 Invalid Document Type Definition format. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 2] [column 2]
2.8 [28] not-wf-sa-056 Invalid Document Type Definition format - misplaced comment. (odd SAXParseException) (fatal) The document type declaration for root element type "doc" must end with '>'. [line 1] [column 15]
2.8 [28] not-wf-sa-107 Invalid document type declaration. CDATA alone is invalid. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 2] [column 4]
2.8 [28] not-wf-sa-149 XML Declaration may not be within a DTD. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 3] [column 6]
2.8 [28] o-p28fail1 only declarations in DTD. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 2]
2.8 [29] not-wf-sa-063 Conditional sections may only appear in the external DTD subset. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 2] [column 4]
2.8 [29] o-p29fail1 A processor must not pass unknown declaration types. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 3]
2.8 [30] o-p30fail1 An XML declaration is not the same as a TextDecl (odd SAXParseException) (fatal) no more pseudo attributes is allowed. [line 1] [column 54]
2.8 [31] o-p31fail1 external subset excludes doctypedecl (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 1] [column 3]
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. (odd SAXParseException) (fatal) White space is required before the encoding pseudo attribute in the XML declaration. [line 1] [column 36]
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. (odd SAXParseException) (fatal) The ' = ' character must follow "standalone" in the XML declaration. [line 1] [column 31]
2.9 ibm-not-wf-P32-ibm32n03.xml Tests SDDecl with wrong key word. The word "Standalone" occurs in the SDDecl in the XMLDecl. (odd SAXParseException) (fatal) The encoding declaration is required in the text declaration. [line 1] [column 37]
2.9 ibm-not-wf-P32-ibm32n04.xml Tests SDDecl with wrong key word. The word "Yes" occurs in the SDDecl in the XMLDecl. (odd SAXParseException) (fatal) The standalone document declaration value must be "yes" or "no", not "{0}". [line 1] [column 37]
2.9 ibm-not-wf-P32-ibm32n05.xml Tests SDDecl with wrong key word. The word "YES" occurs in the SDDecl in the XMLDecl. (odd SAXParseException) (fatal) The standalone document declaration value must be "yes" or "no", not "{0}". [line 1] [column 37]
2.9 ibm-not-wf-P32-ibm32n06.xml Tests SDDecl with wrong key word. The word "No" occurs in the SDDecl in the XMLDecl. (odd SAXParseException) (fatal) The standalone document declaration value must be "yes" or "no", not "{0}". [line 1] [column 36]
2.9 ibm-not-wf-P32-ibm32n07.xml Tests SDDecl with wrong key word. The word "NO" occurs in the SDDecl in the XMLDecl. (odd SAXParseException) (fatal) The standalone document declaration value must be "yes" or "no", not "{0}". [line 1] [column 36]
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. (odd SAXParseException) (fatal) The ' = ' character must follow "standalone" in the XML declaration. [line 1] [column 31]
2.9 [32] not-wf-sa-096 Space is required before the standalone declaration. (odd SAXParseException) (fatal) White space is required before the encoding pseudo attribute in the XML declaration. [line 1] [column 36]
2.9 [32] not-wf-sa-100 Only "yes" and "no" are permitted as values of "standalone". (odd SAXParseException) (fatal) The standalone document declaration value must be "yes" or "no", not "{0}". [line 1] [column 37]
2.9 [32] o-p32fail1 quote types must match (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 3] [column 1]
2.9 [32] o-p32fail2 quote types must match (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 3] [column 1]
2.9 [32] o-p32fail3 initial S is required (odd SAXParseException) (fatal) White space is required before the encoding pseudo attribute in the XML declaration. [line 1] [column 36]
2.9 [32] o-p32fail4 quotes are required (odd SAXParseException) (fatal) The value following "standalone" in the XML declaration must be a quoted string. [line 1] [column 32]
2.9 [32] o-p32fail5 yes or no must be lower case (odd SAXParseException) (fatal) The standalone document declaration value must be "yes" or "no", not "{0}". [line 1] [column 37]
3 ibm-not-wf-P39-ibm39n01.xml Tests element with a required field missing. The ETag is missing for the element "root". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 7] [column 1]
3 ibm-not-wf-P39-ibm39n02.xml Tests element with a required field missing. The STag is missing for the element "root". (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 5] [column 1]
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". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 7] [column 1]
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". (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 5] [column 2]
3 ibm-not-wf-P39-ibm39n05.xml Tests element with wrong field ordering. The STag and the ETag are swapped in the element "root". (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 5] [column 2]
3 ibm-not-wf-P39-ibm39n06.xml Tests element with wrong field ordering. The content occurs after the ETag of the element "root". (odd SAXParseException) (fatal) Content is not allowed in trailing section. [line 5] [column 14]
3 not-wf-sa-039 Tests the Element Type Match WFC - end tag name must match start tag name. (odd SAXParseException) (fatal) The element type "a" must be terminated by the matching end-tag "</a>". [line 1] [column 14]
3 [39] not-wf-sa-176 Start tags must have matching end tags. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 5] [column 1]
3 [39] o-p39fail1 start-tag requires end-tag (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 1] [column 13]
3 [39] o-p39fail2 end-tag requires start-tag (odd SAXParseException) (fatal) The element type "doc" must be terminated by the matching end-tag "</doc>". [line 1] [column 17]
3 [39] o-p39fail3 XML documents contain one or more elements (odd SAXParseException) (fatal) Premature end of file.
3 [39] sgml01 SGML-ism: omitted end tag for EMPTY content (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 8] [column 1]
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". (odd SAXParseException) (fatal) Element type "attr1" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) Element type "rootattr1" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 11]
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". (odd SAXParseException) (fatal) Element type "attr1" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 3]
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". (odd SAXParseException) (fatal) Attribute "attr1" was already specified for element "root". [line 7] [column 26]
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". (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) Attribute name "root" must be followed by the ' = ' character. [line 7] [column 12]
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". (odd SAXParseException) (fatal) Open quote is expected for attribute "attr1|". [line 7] [column 14]
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". (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) Attribute name "root" must be followed by the ' = ' character. [line 7] [column 12]
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". (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) Attribute name "root" must be followed by the ' = ' character. [line 7] [column 12]
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". (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) The external entity reference "&aExternal;" is not permitted in an attribute value. [line 8] [column 25]
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". (odd SAXParseException) (fatal) The external entity reference "&aExternal;" is not permitted in an attribute value.
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". (odd SAXParseException) (fatal) The external entity reference "&aImage;" is not permitted in an attribute value. [line 9] [column 22]
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". (odd SAXParseException) (fatal) The value of attribute "attr1" must not contain the '<' character.
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. (odd SAXParseException) (fatal) The value of attribute "attr1" must not contain the '<' character.
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". (odd SAXParseException) (fatal) The element type "root" must be terminated by the matching end-tag "</root>". [line 6] [column 42]
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". (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 6] [column 52]
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". (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 7] [column 1]
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". (odd SAXParseException) (fatal) The end-tag for element type "null" must end with a '>' delimiter. [line 6] [column 60]
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"). (odd SAXParseException) (fatal) The end-tag for element type "root" must end with a '>' delimiter. [line 6] [column 33]
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". (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 8] [column 3]
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". (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 8] [column 3]
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". (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 8] [column 3]
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". (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 8] [column 3]
3.1 ibm-not-wf-P44-ibm44n01.xml Tests EmptyElemTag with a required field missing. The Name "root" is missing in the EmptyElemTag. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 7] [column 2]
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. (odd SAXParseException) (fatal) Element type "attr1" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 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". (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 7] [column 18]
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". (odd SAXParseException) (fatal) Attribute "attr1" was already specified for element "root". [line 7] [column 26]
3.1 not-wf-sa-038 Tests the "Unique Att Spec" WF constraint by providing multiple values for an attribute. (odd SAXParseException) (fatal) Attribute "x" was already specified for element "doc". [line 1] [column 24]
3.1 not-wf-sa-081 This tests the No External Entity References WFC, since the entity is referred to within an attribute. (odd SAXParseException) (fatal) The external entity reference "&e;" is not permitted in an attribute value. [line 4] [column 12]
3.1 not-wf-sa-082 This tests the No External Entity References WFC, since the entity is referred to within an attribute. (odd SAXParseException) (fatal) The external entity reference "&e;" is not permitted in an attribute value. [line 4] [column 27]
3.1 [40] attlist10 Whitespace required between attributes (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 6] [column 20]
3.1 [40] not-wf-sa-046 This start (or empty element) tag was not terminated correctly. (odd SAXParseException) (fatal) Element type "a" must be followed by either attribute specifications, ">" or "/>". [line 2] [column 4]
3.1 [40] not-wf-sa-049 Missing start tag (odd SAXParseException) (fatal) The element type "doc" must be terminated by the matching end-tag "</doc>". [line 3] [column 17]
3.1 [40] o-p40fail1 S is required between attributes (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 15]
3.1 [40] o-p40fail2 tags start with names, not nmtokens (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
3.1 [40] o-p40fail3 tags start with names, not nmtokens (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
3.1 [40] o-p40fail4 no space before name (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
3.1 [41] not-wf-sa-001 Attribute values must start with attribute names, not "?". (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 3] [column 1]
3.1 [41] not-wf-sa-011 SGML-ism: attribute values must be explicitly assigned a value, it can't act as a boolean toggle. (odd SAXParseException) (fatal) Attribute name "doc" must be followed by the ' = ' character. [line 1] [column 8]
3.1 [41] not-wf-sa-015 Attribute values need a value, not just an equals sign. (odd SAXParseException) (fatal) Open quote is expected for attribute "a1|". [line 1] [column 9]
3.1 [41] not-wf-sa-016 Attribute values need an associated name. (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 14]
3.1 [41] not-wf-sa-178 Invalid syntax matching double quote is missing. (odd SAXParseException) (fatal) The value of attribute "a" must not contain the '<' character. [line 5] [column 15]
3.1 [41] o-p41fail1 quotes are required (contrast with SGML) (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 3] [column 15]
3.1 [41] o-p41fail2 attribute name is required (contrast with SGML) (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 3] [column 15]
3.1 [41] o-p41fail3 Eq required (odd SAXParseException) (fatal) Attribute name "doc" must be followed by the ' = ' character. [line 1] [column 10]
3.1 [42] element00 EOF in middle of incomplete ETAG (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 3] [column 5]
3.1 [42] element01 EOF in middle of incomplete ETAG (odd SAXParseException) (fatal) XML document structures must start and end within the same entity. [line 3] [column 7]
3.1 [42] not-wf-sa-019 End tags may not be abbreviated as '</>'. (odd SAXParseException) (fatal) The element type "doc" must be terminated by the matching end-tag "</doc>". [line 1] [column 9]
3.1 [42] not-wf-sa-042 Invalid End Tag (odd SAXParseException) (fatal) The markup in the document following the root element must be well-formed. [line 1] [column 8]
3.1 [42] not-wf-sa-053 End tag does not match start tag. (odd SAXParseException) (fatal) The element type "doc" must be terminated by the matching end-tag "</doc>". [line 1] [column 12]
3.1 [42] o-p42fail1 no space before name (odd SAXParseException) (fatal) The end-tag for element type "null" must end with a '>' delimiter. [line 1] [column 9]
3.1 [42] o-p42fail2 cannot end with "/>" (odd SAXParseException) (fatal) The end-tag for element type "doc" must end with a '>' delimiter. [line 1] [column 11]
3.1 [42] o-p42fail3 no NET (contrast with SGML) (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 6]
3.1 [43] element02 Illegal markup (<%@ ... %>) (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 3] [column 6]
3.1 [43] element03 Illegal markup (<% ... %>) (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 3] [column 6]
3.1 [43] element04 Illegal markup (<!ELEMENT ... >) (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 3] [column 7]
3.1 [43] not-wf-sa-035 The '<' character is a markup delimiter and must start an element, CDATA section, PI, or comment. (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 1] [column 9]
3.1 [43] not-wf-sa-111 Entiry reference must be in content of element not Start-tag. (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 4] [column 6]
3.1 [43] not-wf-sa-150 XML declarations may not be within element content. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
3.1 [43] o-p43fail1 no non-comment declarations (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 7] [column 3]
3.1 [43] o-p43fail2 no conditional sections (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 7] [column 3]
3.1 [43] o-p43fail3 no conditional sections (odd SAXParseException) (fatal) The content of elements must consist of well-formed character data or markup. [line 7] [column 3]
3.1 [44] attlist11 Whitespace required between attributes (odd SAXParseException) (fatal) Element type "root" must be followed by either attribute specifications, ">" or "/>". [line 6] [column 20]
3.1 [44] not-wf-sa-045 Invalid Empty Element Tag (odd SAXParseException) (fatal) Element type "a" must be followed by either attribute specifications, ">" or "/>". [line 2] [column 4]
3.1 [44] not-wf-sa-047 Invalid empty element tag invalid whitespace (odd SAXParseException) (fatal) Element type "a" must be followed by either attribute specifications, ">" or "/>". [line 2] [column 5]
3.1 [44] not-wf-sa-186 Whitespace is required between attribute/value pairs. (odd SAXParseException) (fatal) Element type "a" must be followed by either attribute specifications, ">" or "/>". [line 5] [column 9]
3.1 [44] o-p44fail1 Illegal space before Empty element tag. (odd SAXParseException) (fatal) The markup in the document preceding the root element must be well-formed. [line 1] [column 2]
3.1 [44] o-p44fail2 Illegal space after Empty element tag. (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 6]
3.1 [44] o-p44fail3 Illegal comment in Empty element tag. (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 6]
3.1 [44] o-p44fail4 Whitespace required between attributes. (odd SAXParseException) (fatal) Element type "doc" must be followed by either attribute specifications, ">" or "/>". [line 1] [column 15]
3.1 [44] o-p44fail5 Duplicate attribute name is illegal. (odd SAXParseException) (fatal) Attribute "att" was already specified for element "doc". [line 1] [column 20]
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. (odd SAXParseException) (fatal) The element type is required in the element type declaration. [line 5] [column 11]
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. (odd SAXParseException) (fatal) White space is required after the element type "aEle" in the element type declaration. [line 5] [column 15]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "root". [line 5] [column 16]
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. (odd SAXParseException) (fatal) White space is required after the element type "root" in the element type declaration. [line 5] [column 15]
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. (odd SAXParseException) (fatal) The element type is required in the element type declaration. [line 5] [column 11]
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. (odd SAXParseException) (fatal) The element type is required in the element type declaration. [line 5] [column 11]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 5] [column 2]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 5] [column 3]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 5] [column 3]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
3.2 [45] not-wf-sa-057 This isn't SGML; comments can't exist in declarations. (odd SAXParseException) (fatal) The declaration for the entity "e" must end with '>'. [line 2] [column 23]
3.2 [45] not-wf-sa-129 Invalid syntax for Element Type Declaration. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 2] [column 15]
3.2 [45] not-wf-sa-130 Invalid syntax for Element Type Declaration. (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 2] [column 22]
3.2 [45] not-wf-sa-131 Invalid syntax for Element Type Declaration. (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 2] [column 22]
3.2 [45] not-wf-sa-136 Tag omission is invalid in XML. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 2] [column 15]
3.2 [45] not-wf-sa-137 Space is required before a content model. (odd SAXParseException) (fatal) White space is required after the element type "doc" in the element type declaration. [line 2] [column 14]
3.2 [45] o-p45fail1 ELEMENT must be upper case. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 3]
3.2 [45] o-p45fail2 S before contentspec is required. (odd SAXParseException) (fatal) White space is required after the element type "doc" in the element type declaration. [line 3] [column 14]
3.2 [45] o-p45fail3 only one content spec (odd SAXParseException) (fatal) The element type is required in the element type declaration. [line 3] [column 11]
3.2 [45] o-p45fail4 no comments in declarations (contrast with SGML) (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 3] [column 25]
3.2 [45] sgml05 ELEMENT declarations apply to only one element, unlike SGML (odd SAXParseException) (fatal) The element type is required in the element type declaration. [line 8] [column 15]
3.2 [45] sgml07 SGML Tag minimization specifications are not allowed (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "root". [line 3] [column 20]
3.2 [45] sgml08 SGML Tag minimization specifications are not allowed (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "root". [line 3] [column 20]
3.2 [45] sgml09 SGML Content model exception specifications are not allowed (odd SAXParseException) (fatal) The declaration for element type "footnote" must end with '>'. [line 4] [column 32]
3.2 [45] sgml10 SGML Content model exception specifications are not allowed (odd SAXParseException) (fatal) The declaration for element type "section" must end with '>'. [line 3] [column 48]
3.2 [46] o-p46fail1 no parens on declared content (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "a". [line 4] [column 14]
3.2 [46] o-p46fail2 no inclusions (contrast with SGML) (odd SAXParseException) (fatal) The declaration for element type "a" must end with '>'. [line 4] [column 23]
3.2 [46] o-p46fail3 no exclusions (contrast with SGML) (odd SAXParseException) (fatal) The declaration for element type "a" must end with '>'. [line 4] [column 23]
3.2 [46] o-p46fail4 no space before occurrence (odd SAXParseException) (fatal) The declaration for element type "a" must end with '>'. [line 4] [column 19]
3.2 [46] o-p46fail5 single group (odd SAXParseException) (fatal) The declaration for element type "a" must end with '>'. [line 4] [column 22]
3.2 [46] o-p46fail6 can't be both declared and modeled (odd SAXParseException) (fatal) The declaration for element type "a" must end with '>'. [line 4] [column 19]
3.2 [46] sgml11 CDATA is not a valid content model spec (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "ROOT". [line 3] [column 20]
3.2 [46] sgml12 RCDATA is not a valid content model spec (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "ROOT". [line 3] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 5] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 6] [column 20]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 20]
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. (odd SAXParseException) (fatal) The declaration for element type "aElement" must end with '>'. [line 6] [column 25]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 6] [column 27]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 6] [column 21]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 6] [column 21]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 6] [column 21]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 21]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 6] [column 24]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 6] [column 23]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 6] [column 21]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 26]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 22]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 23]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 24]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 26]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 21]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 25]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 24]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 23]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 27]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 27]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 25]
3.2.1 not-wf-sa-133 Illegal whitespace before optional character causes syntax error. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "doc". [line 2] [column 18]
3.2.1 not-wf-sa-134 Illegal whitespace before optional character causes syntax error. (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 2] [column 19]
3.2.1 [46] not-wf-sa-139 The element-content model should not be empty. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 2] [column 16]
3.2.1 [47] not-wf-sa-122 Invalid syntax mixed connectors are used. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "doc". [line 2] [column 23]
3.2.1 [47] not-wf-sa-135 Invalid character used as connector. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "doc". [line 2] [column 18]
3.2.1 [47] o-p47fail1 Invalid operator '|' must match previous operator ',' (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "a". [line 4] [column 20]
3.2.1 [47] o-p47fail2 Illegal character '-' in Element-content model (odd SAXParseException) (fatal) The declaration for element type "a" must end with '>'. [line 4] [column 18]
3.2.1 [47] o-p47fail3 Optional character must follow a name or list (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "a". [line 4] [column 13]
3.2.1 [47] o-p47fail4 Illegal space before optional character (odd SAXParseException) (fatal) The declaration for element type "a" must end with '>'. [line 4] [column 19]
3.2.1 [47] sgml13 SGML Unordered content models not allowed (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "ROOT". [line 3] [column 23]
3.2.1 [48] content01 No whitespace before "?" in content model (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "root". [line 3] [column 28]
3.2.1 [48] content02 No whitespace before "*" in content model (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "root". [line 3] [column 28]
3.2.1 [48] content03 No whitespace before "+" in content model (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "root". [line 3] [column 26]
3.2.1 [48] not-wf-sa-123 Invalid syntax mismatched parenthesis. (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 2] [column 23]
3.2.1 [48] not-wf-sa-138 Invalid syntax for content particle. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "doc". [line 2] [column 20]
3.2.1 [48] o-p48fail1 Illegal space before optional character (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "a". [line 4] [column 18]
3.2.1 [48] o-p48fail2 Illegal space before optional character (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "a". [line 4] [column 23]
3.2.1 [49] o-p49fail1 connectors must match (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "a". [line 4] [column 20]
3.2.1 [50] not-wf-sa-132 Invalid syntax mixed connectors used. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "doc". [line 2] [column 38]
3.2.1 [50] o-p50fail1 connectors must match (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "a". [line 4] [column 20]
3.2.1 [55] nwf-dtd00 Comma mandatory in content model (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "root". [line 2] [column 31]
3.2.1 [55] nwf-dtd01 Can't mix comma and vertical bar in content models (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "root". [line 2] [column 31]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 21]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 28]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 30]
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. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "aElement". [line 7] [column 21]
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. (odd SAXParseException) (fatal) The mixed content model "aElement" must end with ")*" when the types of child elements are constrained. [line 7] [column 34]
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. (odd SAXParseException) (fatal) The mixed content model "aElement" must end with ")*" when the types of child elements are constrained. [line 7] [column 34]
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. (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "aElement". [line 7] [column 30]
3.2.2 [51] not-wf-sa-124 Invalid format of Mixed-content declaration. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 2] [column 20]
3.2.2 [51] not-wf-sa-125 Invalid syntax extra set of parenthesis not necessary. (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "doc". [line 2] [column 17]
3.2.2 [51] not-wf-sa-126 Invalid syntax Mixed-content must be defined as zero or more. (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 2] [column 24]
3.2.2 [51] not-wf-sa-127 Invalid syntax Mixed-content must be defined as zero or more. (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 2] [column 24]
3.2.2 [51] not-wf-sa-183 Mixed content declarations may not include content particles. (odd SAXParseException) (fatal) The mixed content model "doc" must end with ")*" when the types of child elements are constrained. [line 2] [column 29]
3.2.2 [51] not-wf-sa-184 In mixed content models, element names must not be parenthesized. (odd SAXParseException) (fatal) An element type is required in the declaration of element type "doc". [line 2] [column 26]
3.2.2 [51] o-p51fail1 occurrence on #PCDATA group must be * (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 3] [column 24]
3.2.2 [51] o-p51fail2 occurrence on #PCDATA group must be * (odd SAXParseException) (fatal) The declaration for element type "doc" must end with '>'. [line 3] [column 24]
3.2.2 [51] o-p51fail3 #PCDATA must come first (odd SAXParseException) (fatal) A '(' character or an element type is required in the declaration of element type "a". [line 4] [column 18]
3.2.2 [51] o-p51fail4 occurrence on #PCDATA group must be * (odd SAXParseException) (fatal) The mixed content model "a" must end with ")*" when the types of child elements are constrained. [line 4] [column 25]
3.2.2 [51] o-p51fail5 only '|' connectors (odd SAXParseException) (fatal) The mixed content model "a" must end with ")*" when the types of child elements are constrained. [line 4] [column 25]
3.2.2 [51] o-p51fail6 Only '|' connectors and occurrence on #PCDATA group must be * (odd SAXParseException) (fatal) A ')' is required in the declaration of element type "a". [line 4] [column 21]
3.2.2 [51] o-p51fail7 no nested groups (odd SAXParseException) (fatal) An element type is required in the declaration of element type "a". [line 4] [column 22]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "CDATA" for element "attr1". [line 6] [column 24]
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. (odd SAXParseException) (fatal) White space is required after "<!ATTLIST" in the attribute-list declaration. [line 6] [column 10]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "CDATA" for element "attr1". [line 6] [column 24]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 6] [column 3]
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. (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "a". [line 7] [column 1]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 6] [column 2]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "attr1|". [line 6] [column 25]
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. (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "attr1" for element "a". [line 6] [column 28]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr1" for element "a". [line 6] [column 20]
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. (odd SAXParseException) (fatal) White space is required before the attribute type in the declaration of attribute "attr1" for element "a". [line 6] [column 18]
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. (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "a". [line 6] [column 13]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "attr2|". [line 6] [column 43]
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. (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "a". [line 6] [column 13]
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. (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "a". [line 6] [column 13]
3.3 [52] not-wf-sa-066 Required whitespace is missing. (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "a1" for element "doc". [line 3] [column 27]
3.3 [52] not-wf-sa-158 SGML-ism: "#NOTATION gif" can't have attributes. (odd SAXParseException) (fatal) The element type is required in the attribute-list declaration. [line 4] [column 11]
3.3 [52] o-p52fail1 A name is required (odd SAXParseException) (fatal) The element type is required in the attribute-list declaration. [line 4] [column 12]
3.3 [52] o-p52fail2 A name is required (odd SAXParseException) (fatal) White space is required after "<!ATTLIST" in the attribute-list declaration. [line 4] [column 10]
3.3 [52] sgml04 ATTLIST declarations apply to only one element, unlike SGML (odd SAXParseException) (fatal) The element type is required in the attribute-list declaration. [line 7] [column 15]
3.3 [52] sgml06 ATTLIST declarations are never global, unlike in SGML (odd SAXParseException) (fatal) The element type is required in the attribute-list declaration. [line 6] [column 15]
3.3 [53] not-wf-sa-064 Space is required between attribute type and default values in <!ATTLIST...> declarations. (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "a1" for element "e". [line 3] [column 21]
3.3 [53] not-wf-sa-065 Space is required between attribute name and type in <!ATTLIST...> declarations. (odd SAXParseException) (fatal) White space is required before the attribute type in the declaration of attribute "a1" for element "doc". [line 3] [column 17]
3.3 [53] not-wf-sa-067 Space is required between attribute type and default values in <!ATTLIST...> declarations. (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "a1" for element "doc". [line 3] [column 23]
3.3 [53] o-p53fail1 S is required before default (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "att" for element "doc". [line 4] [column 24]
3.3 [53] o-p53fail2 S is required before type (odd SAXParseException) (fatal) White space is required before the attribute type in the declaration of attribute "att" for element "doc". [line 4] [column 18]
3.3 [53] o-p53fail3 type is required (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "doc". [line 4] [column 20]
3.3 [53] o-p53fail4 default is required (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "att" for element "doc". [line 4] [column 24]
3.3 [53] o-p53fail5 name is requried (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "doc". [line 4] [column 15]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "a". [line 7] [column 18]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "a". [line 7] [column 18]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "a". [line 7] [column 18]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "a". [line 7] [column 18]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "a". [line 7] [column 18]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "a". [line 7] [column 19]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "a". [line 7] [column 19]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "a". [line 7] [column 19]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "a". [line 7] [column 19]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "a". [line 7] [column 19]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "a". [line 7] [column 19]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "a". [line 7] [column 19]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "att|". [line 6] [column 29]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "one". [line 8] [column 22]
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. (odd SAXParseException) (fatal) The '(' character must follow "NOTATION" in the "attr" attribute declaration. [line 8] [column 31]
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. (odd SAXParseException) (fatal) The notation name is required in the notation type list for the "attr" attribute declaration. [line 8] [column 31]
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. (odd SAXParseException) (fatal) The notation type list must end with ')' in the "attr" attribute declaration. [line 8] [column 37]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "attr|". [line 8] [column 28]
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. (odd SAXParseException) (fatal) The notation type list must end with ')' in the "attr" attribute declaration. [line 10] [column 38]
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. (odd SAXParseException) (fatal) White space must appear after "NOTATION" in the "attr" attribute declaration. [line 9] [column 31]
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. (odd SAXParseException) (fatal) The notation name is required in the notation type list for the "attr" attribute declaration. [line 9] [column 33]
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. (odd SAXParseException) (fatal) The name token is required in the enumerated type list for the "attr" attribute declaration. [line 8] [column 22]
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. (odd SAXParseException) (fatal) The enumerated type list must end with ')' in the "attr" attribute declaration. [line 8] [column 28]
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. (odd SAXParseException) (fatal) The enumerated type list must end with ')' in the "attr" attribute declaration. [line 9] [column 27]
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. (odd SAXParseException) (fatal) The name token is required in the enumerated type list for the "attr" attribute declaration. [line 8] [column 22]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "one". [line 8] [column 22]
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. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "attr" for element "one". [line 8] [column 22]
3.3.1 [54] not-wf-sa-058 Invalid character , in ATTLIST enumeration (odd SAXParseException) (fatal) The enumerated type list must end with ')' in the "a1" attribute declaration. [line 3] [column 23]
3.3.1 [54] o-p54fail1 don't pass unknown attribute types (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "doc". [line 4] [column 20]
3.3.1 [55] o-p55fail1 must be upper case (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "doc". [line 4] [column 20]
3.3.1 [56] attlist01 SGML's NUTOKEN is not allowed. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "number" for element "root". [line 7] [column 10]
3.3.1 [56] attlist02 SGML's NUTOKENS attribute type is not allowed. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "number" for element "root". [line 7] [column 10]
3.3.1 [56] attlist04 SGML's NUMBER attribute type is not allowed. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "number" for element "root". [line 7] [column 10]
3.3.1 [56] attlist05 SGML's NUMBERS attribute type is not allowed. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "numbers" for element "root". [line 7] [column 11]
3.3.1 [56] attlist06 SGML's NAME attribute type is not allowed. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "number" for element "root". [line 7] [column 10]
3.3.1 [56] attlist07 SGML's NAMES attribute type is not allowed. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "number" for element "root". [line 7] [column 10]
3.3.1 [56] attlist08 SGML's #CURRENT is not allowed. (odd SAXParseException) (fatal) Open quote is expected for attribute "language|". [line 7] [column 17]
3.3.1 [56] attlist09 SGML's #CONREF is not allowed. (odd SAXParseException) (fatal) Open quote is expected for attribute "language|". [line 5] [column 17]
3.3.1 [56] not-wf-sa-060 Invalid type NAME defined in ATTLIST. (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "a1" for element "doc". [line 3] [column 19]
3.3.1 [56] o-p56fail1 no IDS type (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "att" for element "doc". [line 4] [column 21]
3.3.1 [56] o-p56fail2 no NUMBER type (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "doc". [line 4] [column 20]
3.3.1 [56] o-p56fail3 no NAME type (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "doc". [line 4] [column 20]
3.3.1 [56] o-p56fail4 no ENTITYS type - types must be upper case (odd SAXParseException) (fatal) White space is required before the attribute default in the declaration of attribute "att" for element "doc". [line 4] [column 25]
3.3.1 [56] o-p56fail5 types must be upper case (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "doc". [line 4] [column 20]
3.3.1 [57] o-p57fail1 no keyword for NMTOKEN enumeration (odd SAXParseException) (fatal) Open quote is expected for attribute "att|". [line 4] [column 27]
3.3.1 [58] not-wf-sa-068 Space is required between NOTATION keyword and list of enumerated choices in <!ATTLIST...> declarations. (odd SAXParseException) (fatal) White space must appear after "NOTATION" in the "a1" attribute declaration. [line 3] [column 26]
3.3.1 [58] o-p58fail1 at least one value required (odd SAXParseException) (fatal) The notation name is required in the notation type list for the "att" attribute declaration. [line 6] [column 29]
3.3.1 [58] o-p58fail2 separator must be '|' (odd SAXParseException) (fatal) The notation type list must end with ')' in the "att" attribute declaration. [line 6] [column 31]
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. (odd SAXParseException) (fatal) The notation name is required in the notation type list for the "att" attribute declaration. [line 6] [column 31]
3.3.1 [58] o-p58fail4 NOTATION must be upper case (odd SAXParseException) (fatal) The attribute type is required in the declaration of attribute "att" for element "doc". [line 6] [column 20]
3.3.1 [58] o-p58fail5 S after keyword is required (odd SAXParseException) (fatal) White space must appear after "NOTATION" in the "att" attribute declaration. [line 6] [column 27]
3.3.1 [58] o-p58fail6 parentheses are require (odd SAXParseException) (fatal) The '(' character must follow "NOTATION" in the "att" attribute declaration. [line 5] [column 29]
3.3.1 [58] o-p58fail7 values are unquoted (odd SAXParseException) (fatal) The '(' character must follow "NOTATION" in the "att" attribute declaration. [line 5] [column 29]
3.3.1 [58] o-p58fail8 values are unquoted (odd SAXParseException) (fatal) The notation name is required in the notation type list for the "att" attribute declaration. [line 5] [column 29]
3.3.1 [59] attlist03 Comma doesn't separate enumerations, unlike in SGML. (odd SAXParseException) (fatal) The enumerated type list must end with ')' in the "choice" attribute declaration. [line 7] [column 12]
3.3.1 [59] not-wf-sa-059 String literal must be in quotes. (odd SAXParseException) (fatal) Open quote is expected for attribute "a1|". [line 3] [column 26]
3.3.1 [59] o-p59fail1 at least one required (odd SAXParseException) (fatal) The name token is required in the enumerated type list for the "att" attribute declaration. [line 4] [column 20]
3.3.1 [59] o-p59fail2 separator must be "," (odd SAXParseException) (fatal) The enumerated type list must end with ')' in the "att" attribute declaration. [line 4] [column 22]
3.3.1 [59] o-p59fail3 values are unquoted (odd SAXParseException) (fatal) The name token is required in the enumerated type list for the "att" attribute declaration. [line 4] [column 20]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "chapter|". [line 7] [column 30]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "chapter|". [line 7] [column 30]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "chapter|". [line 7] [column 30]
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. (odd SAXParseException) (fatal) Open quote is expected for attribute "chapter|". [line 7] [column 37]
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. (odd SAXParseException) (fatal) White space must appear after "FIXED" in the "chapter" attribute declaration. [line 7] [column 36]
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. (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "one". [line 7] [column 45]
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. (odd SAXParseException) (fatal) The value of attribute "chapter" must not contain the '<' character.
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. (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "one". [line 7] [column 40]
3.3.2 [60] o-p60fail1 keywords must be upper case (odd SAXParseException) (fatal) Open quote is expected for attribute "att|". [line 4] [column 25]
3.3.2 [60] o-p60fail2 S is required after #FIXED (odd SAXParseException) (fatal) White space must appear after "FIXED" in the "att" attribute declaration. [line 4] [column 31]
3.3.2 [60] o-p60fail3 only #FIXED has both keyword and value (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "doc". [line 4] [column 35]
3.3.2 [60] o-p60fail4 #FIXED required value (odd SAXParseException) (fatal) White space must appear after "FIXED" in the "att" attribute declaration. [line 4] [column 31]
3.3.2 [60] o-p60fail5 only one default type (odd SAXParseException) (fatal) The attribute name must be specified in the attribute-list declaration for element "doc". [line 4] [column 34]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 4]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 5]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 4]
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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 4]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 4] [column 1]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 4] [column 1]
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. (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 8] [column 33]
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. (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 6] [column 2]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 4]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 4]
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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 4]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 4] [column 1]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 4] [column 1]
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. (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 8] [column 34]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 8] [column 1]
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. (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 10] [column 48]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 8] [column 1]
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 (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 6] [column 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 (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 13] [column 59]
3.4 [61] cond01 Only INCLUDE and IGNORE are conditional section keywords (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 11]
3.4 [61] cond02 Must have keyword in conditional sections (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 3] [column 11]
3.4 [61] o-p61fail1 no other types, including TEMP, which is valid in SGML (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 2] [column 4]
3.4 [62] not-wf-not-sa-001 Conditional sections must be properly terminated ("]>" used instead of "]]>"). (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 3] [column 2]
3.4 [62] not-wf-not-sa-003 Conditional sections must be properly terminated ("]]>" omitted). (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 3] [column 2]
3.4 [62] not-wf-not-sa-004 Conditional sections must be properly terminated ("]]>" omitted). (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 3] [column 1]
3.4 [62] not-wf-not-sa-006 Conditional sections need a '[' after the INCLUDE or IGNORE. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 2] [column 1]
3.4 [62] o-p62fail1 INCLUDE must be upper case (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 1] [column 4]
3.4 [62] o-p62fail2 no spaces in terminating delimiter (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 3] [column 2]
3.4 [63] o-p63fail1 IGNORE must be upper case (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 2] [column 4]
3.4 [63] o-p63fail2 delimiters must be balanced (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 3] [column 2]
3.4 [64] o-p64fail1 section delimiters must balance (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 2] [column 33]
3.4 [64] o-p64fail2 section delimiters must balance (odd SAXParseException) (fatal) The included conditional section must end with "]]>". [line 3] [column 2]
4.1 ibm-invalid-P68-ibm68i01 Tests the Entity Declared WFC. The GE with the name "ge2" is not declared when it is referred to in an attribute default. FAIL [Document not WF; no error reported]
4.1 ibm-invalid-P68-ibm68i02.xml Tests the Entity Declared WFC. The GE with the name "ge1" is not declared when it is referred to in an attribute default. FAIL [Document not WF; no error reported]
4.1 ibm-invalid-P68-ibm68i03.xml Tests the Entity Declared WFC. The GE with the name "ge2" is not declared when it is referred to in an attribute default. FAIL [Document not WF; no error reported]
4.1 ibm-invalid-P68-ibm68i04 Tests the Entity Declared WFC. The GE with the name "ge1" is not declared when it is referred to in an attribute default. FAIL [Document not WF; no error reported]
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. (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 5] [column 46]
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". (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 7] [column 46]
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. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 5] [column 42]
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". (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 7] [column 40]
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. (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 5] [column 47]
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". (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 7] [column 43]
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. (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 5] [column 45]
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". (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 7] [column 41]
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. (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 5] [column 46]
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". (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 7] [column 42]
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. (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 5] [column 46]
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". (odd SAXParseException) (fatal) Character reference "&#0" is an invalid XML character. [line 7] [column 58]
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". (odd SAXParseException) (fatal) Character reference "&#1f" is an invalid XML character. [line 7] [column 48]
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". (odd SAXParseException) (fatal) Character reference "&#fffe" is an invalid XML character. [line 7] [column 49]
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". (odd SAXParseException) (fatal) Character reference "&#ffff" is an invalid XML character. [line 7] [column 48]
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". (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 7] [column 28]
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". (odd SAXParseException) (fatal) The reference to entity "aaa" must end with the ';' delimiter. [line 7] [column 16]
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". (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 7] [column 34]
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. (odd SAXParseException) (fatal) The entity "aAa" was referenced, but not declared. [line 7] [column 17]
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. (odd SAXParseException) (fatal) The entity "aaa" was referenced, but not declared. [line 6] [column 30]
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. (odd SAXParseException) (fatal) The entity "aaa" was referenced, but not declared. [line 6] [column 33]
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. (odd SAXParseException) (fatal) The unparsed entity reference "&aImage;" is not permitted. [line 9] [column 60]
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. (odd SAXParseException) (fatal) Recursive entity reference "aaa". (Reference path: aaa -> bbb -> aaa),
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. (odd SAXParseException) (fatal) Recursive entity reference "aaa". (Reference path: aaa -> bbb -> ccc -> ddd -> eee -> aaa),
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. (odd SAXParseException) (fatal) The entity name must immediately follow the '%' in the parameter entity reference. [line 6] [column 2]
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. (odd SAXParseException) (fatal) The parameter entity reference "%paaa;" must end with the ';' delimiter. [line 6] [column 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. (odd SAXParseException) (fatal) The parameter entity reference "%paaa;" must end with the ';' delimiter. [line 6] [column 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. (odd SAXParseException) (fatal) The entity name must immediately follow the '%' in the parameter entity reference. [line 6] [column 2]
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. (odd SAXParseException) (fatal) The parameter entity reference "%paaa;" cannot occur within markup in the internal subset of the DTD. [line 6] [column 21]
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. (odd SAXParseException) (fatal) The parameter entity reference "%paaa;" cannot occur within markup in the internal subset of the DTD. [line 9] [column 21]
4.1 not-wf-ext-sa-001 Tests the No Recursion WFC by having an external general entity be self-recursive. (odd SAXParseException) (fatal) Recursive entity reference "e". (Reference path: e -> e -> e), [line 1] [column 4]
4.1 not-wf-sa-084 Tests the Parsed Entity WFC by referring to an unparsed entity. (This precedes the error of not declaring that entity's notation, which may be detected any time before the DTD parsing is completed.) (odd SAXParseException) (fatal) The external entity reference "&e;" is not permitted in an attribute value. [line 4] [column 27]
4.1 not-wf-sa-180 The Entity Declared WFC requires entities to be declared before they are used in an attribute list declaration. (odd SAXParseException) (fatal) The entity "e" was referenced, but not declared. [line 3] [column 27]
4.1 not-wf-sa-185 Tests the Entity Declared WFC. Note: a nonvalidating parser is permitted not to report this WFC violation, since it would need to read an external parameter entity to distinguish it from a violation of the Standalone Declaration VC. (odd SAXParseException) (fatal) The entity "e" was referenced, but not declared. [line 3] [column 9]
4.1 [66] not-wf-sa-009 Character references may have only decimal or numeric strings. (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 1] [column 8]
4.1 [66] not-wf-sa-022 Character references end with semicolons, always! (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 1] [column 15]
4.1 [66] not-wf-sa-052 Invalid character reference. (odd SAXParseException) (fatal) Reference is not allowed in prolog. [line 2] [column 2]
4.1 [66] not-wf-sa-093 Hexadecimal character references may not use the uppercase 'X'. (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 1] [column 8]
4.1 [66] not-wf-sa-179 Invalid syntax matching double quote is missing. (odd SAXParseException) (fatal) Premature end of file.
4.1 [66] o-p66fail1 terminating ';' is required (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 1] [column 10]
4.1 [66] o-p66fail2 no S after '&#' (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 1] [column 8]
4.1 [66] o-p66fail3 no hex digits in numeric reference (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 1] [column 8]
4.1 [66] o-p66fail4 only hex digits in hex references (odd SAXParseException) (fatal) The character reference must end with the ';' delimiter. [line 1] [column 10]
4.1 [66] o-p66fail5 no references to non-characters (odd SAXParseException) (fatal) Character reference "&#5" is an invalid XML character. [line 1] [column 10]
4.1 [66] o-p66fail6 no references to non-characters (odd SAXParseException) (fatal) Character reference "&#d802" is an invalid XML character. [line 1] [column 14]
4.1 [68] not-wf-sa-007 General entity references have no whitespace after the entity name and before the semicolon. (odd SAXParseException) (fatal) The reference to entity "amp" must end with the ';' delimiter. [line 1] [column 10]
4.1 [68] not-wf-sa-010 Ampersand may only appear as part of a general entity reference. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 1] [column 9]
4.1 [68] not-wf-sa-071 ENTITY can't reference itself directly or indirectly. (odd SAXParseException) (fatal) Recursive entity reference "e1". (Reference path: e1 -> e2 -> e3 -> e1),
4.1 [68] not-wf-sa-072 Undefined ENTITY foo. (odd SAXParseException) (fatal) The entity "foo" was referenced, but not declared. [line 1] [column 11]
4.1 [68] not-wf-sa-073 Undefined ENTITY f. (odd SAXParseException) (fatal) The entity "f" was referenced, but not declared. [line 4] [column 9]
4.1 [68] not-wf-sa-075 ENTITY can't reference itself directly or indirectly. (odd SAXParseException) (fatal) Recursive entity reference "e1". (Reference path: e1 -> e2 -> e3 -> e1),
4.1 [68] not-wf-sa-076 Undefined ENTITY foo. (odd SAXParseException) (fatal) The entity "foo" was referenced, but not declared. [line 1] [column 14]
4.1 [68] not-wf-sa-078 Undefined ENTITY foo. (odd SAXParseException) (fatal) The entity "foo" was referenced, but not declared. [line 3] [column 29]
4.1 [68] not-wf-sa-079 ENTITY can't reference itself directly or indirectly. (odd SAXParseException) (fatal) Recursive entity reference "e1". (Reference path: e1 -> e2 -> e3 -> e1),
4.1 [68] not-wf-sa-080 ENTITY can't reference itself directly or indirectly. (odd SAXParseException) (fatal) Recursive entity reference "e1". (Reference path: e1 -> e2 -> e3 -> e1),
4.1 [68] not-wf-sa-110 Entity reference must be in content of element. (odd SAXParseException) (fatal) Content is not allowed in trailing section. [line 5] [column 1]
4.1 [68] not-wf-sa-118 Entity reference expansion is not recursive. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 4] [column 7]
4.1 [68] not-wf-sa-121 A name of an ENTITY was started with an invalid character. (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 2] [column 10]
4.1 [68] o-p68fail1 terminating ';' is required (odd SAXParseException) (fatal) The reference to entity "ent" must end with the ';' delimiter. [line 7] [column 5]
4.1 [68] o-p68fail2 no S after '&' (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 7] [column 2]
4.1 [68] o-p68fail3 no S before ';' (odd SAXParseException) (fatal) The reference to entity "ent" must end with the ';' delimiter. [line 7] [column 5]
4.1 [69] dtd02 PE name immediately after "%" (odd SAXParseException) (fatal) The entity name must immediately follow the '%' in the parameter entity reference. [line 5] [column 6]
4.1 [69] dtd03 PE name immediately followed by ";" (odd SAXParseException) (fatal) The parameter entity reference "%foo;" must end with the ';' delimiter. [line 5] [column 9]
4.1 [69] not-wf-not-sa-008 In DTDs, the '%' character must be part of a parameter entity reference. (odd SAXParseException) (fatal) The entity name must immediately follow the '%' in the parameter entity reference. [line 2] [column 17]
4.1 [69] not-wf-sa-163 Invalid placement of Parameter entity reference. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 5] [column 1]
4.1 [69] not-wf-sa-164 Invalid placement of Parameter entity reference. (odd SAXParseException) (fatal) The document type declaration for root element type "doc" must end with '>'. [line 4] [column 3]
4.1 [69] o-p69fail1 terminating ';' is required (odd SAXParseException) (fatal) The parameter entity reference "%pe;" must end with the ';' delimiter. [line 5] [column 4]
4.1 [69] o-p69fail2 no S after '%' (odd SAXParseException) (fatal) The entity name must immediately follow the '%' in the parameter entity reference. [line 5] [column 2]
4.1 [69] o-p69fail3 no S before ';' (odd SAXParseException) (fatal) The parameter entity reference "%pe;" must end with the ';' delimiter. [line 5] [column 4]
4.2 ibm-not-wf-P71-ibm70n01.xml Tests (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 7] [column 2]
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. (odd SAXParseException) (fatal) White space is required after "<!ENTITY" in the entity declaration. [line 6] [column 9]
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. (odd SAXParseException) (fatal) White space is required between the entity name "aaa" and the definition in the entity declaration. [line 6] [column 13]
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. (odd SAXParseException) (fatal) White space is required between the entity name "aaa" and the definition in the entity declaration. [line 6] [column 13]
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. (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 6] [column 10]
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. (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 6] [column 10]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 6] [column 3]
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. (odd SAXParseException) (fatal) The declaration for the entity "aaa" must end with '>'. [line 8] [column 1]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 6] [column 2]
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. (odd SAXParseException) (fatal) White space is required after "<!ENTITY" in the entity declaration. [line 6] [column 9]
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. (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 6] [column 12]
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. (odd SAXParseException) (fatal) White space is required between the entity name "paaa" and the definition in the entity declaration. [line 6] [column 16]
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. (odd SAXParseException) (fatal) White space is required between the entity name "paaa" and the definition in the entity declaration. [line 6] [column 16]
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. (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 6] [column 12]
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. (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 6] [column 10]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 6] [column 3]
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. (odd SAXParseException) (fatal) The declaration for the entity "paaa" must end with '>'. [line 7] [column 1]
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. (odd SAXParseException) (fatal) White space is required after "<!ENTITY" in the entity declaration. [line 6] [column 9]
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. (odd SAXParseException) (fatal) White space is required before "NDATA" in the declaration for the entity "aImage". [line 7] [column 22]
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. (odd SAXParseException) (fatal) White space is required before "NDATA" in the declaration for the entity "aImage". [line 7] [column 22]
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. (odd SAXParseException) (fatal) The declaration for the entity "pImage" must end with '>'. [line 7] [column 38]
4.2 not-wf-sa-106 Invalid placement of entity declaration. (odd SAXParseException) (fatal) Reference is not allowed in prolog. [line 2] [column 2]
4.2 [70] not-wf-sa-109 Tags invalid within EntityDecl. (odd SAXParseException) (fatal) Reference is not allowed in prolog. [line 4] [column 2]
4.2 [70] o-p70fail1 This is neither (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 4] [column 10]
4.2 [71] not-wf-sa-062 Entity declarations need space after the entity name. (odd SAXParseException) (fatal) White space is required between the entity name "foo" and the definition in the entity declaration. [line 2] [column 13]
4.2 [71] o-p71fail1 S is required before EntityDef (odd SAXParseException) (fatal) White space is required between the entity name "ge" and the definition in the entity declaration. [line 4] [column 12]
4.2 [71] o-p71fail2 Entity name is a Name, not an NMToken (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 4] [column 10]
4.2 [71] o-p71fail3 no S after "<!" (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 4] [column 3]
4.2 [71] o-p71fail4 S is required after "<!ENTITY" (odd SAXParseException) (fatal) White space is required after "<!ENTITY" in the entity declaration. [line 4] [column 9]
4.2 [72] not-wf-sa-165 Parameter entity declarations must have a space before the '%'. (odd SAXParseException) (fatal) White space is required after "<!ENTITY" in the entity declaration. [line 2] [column 9]
4.2 [72] o-p72fail1 S is required after "<!ENTITY" (odd SAXParseException) (fatal) White space is required after "<!ENTITY" in the entity declaration. [line 4] [column 9]
4.2 [72] o-p72fail2 S is required after '%' (odd SAXParseException) (fatal) White space is required after "<!ENTITY" in the entity declaration. [line 4] [column 11]
4.2 [72] o-p72fail3 S is required after name (odd SAXParseException) (fatal) White space is required between the entity name "pe" and the definition in the entity declaration. [line 4] [column 14]
4.2 [72] o-p72fail4 Entity name is a name, not an NMToken (odd SAXParseException) (fatal) The name of the entity is required in the entity declaration. [line 4] [column 12]
4.2 [73] o-p73fail1 No typed replacement text (odd SAXParseException) (fatal) OpenQuoteMissingInDecl [line 5] [column 14]
4.2 [73] o-p73fail2 Only one replacement value (odd SAXParseException) (fatal) The declaration for the entity "ge" must end with '>'. [line 5] [column 32]
4.2 [73] o-p73fail3 No NDataDecl on replacement text (odd SAXParseException) (fatal) The declaration for the entity "ge" must end with '>'. [line 5] [column 32]
4.2 [73] o-p73fail4 Value is required (odd SAXParseException) (fatal) OpenQuoteMissingInDecl [line 5] [column 14]
4.2 [73] o-p73fail5 No NDataDecl without value (odd SAXParseException) (fatal) White space is required before "NDATA" in the declaration for the entity "ge". [line 5] [column 18]
4.2 [74] not-wf-sa-089 Parameter entities "are" always parsed; NDATA annotations are not permitted. (odd SAXParseException) (fatal) The declaration for the entity "foo" must end with '>'. [line 2] [column 33]
4.2 [74] not-wf-sa-091 Parameter entities "are" always parsed; NDATA annotations are not permitted. (odd SAXParseException) (fatal) The declaration for the entity "foo" must end with '>'. [line 3] [column 33]
4.2 [74] o-p74fail1 no NDataDecls on parameter entities (odd SAXParseException) (fatal) The declaration for the entity "pe" must end with '>'. [line 4] [column 32]
4.2 [74] o-p74fail2 value is required (odd SAXParseException) (fatal) White space is required between the entity name "pe" and the definition in the entity declaration. [line 4] [column 14]
4.2 [74] o-p74fail3 only one value (odd SAXParseException) (fatal) The declaration for the entity "pe" must end with '>'. [line 3] [column 30]
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. (odd SAXParseException) (fatal) OpenQuoteMissingInDecl [line 6] [column 18]
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. (odd SAXParseException) (fatal) The document type declaration for root element type "root" must end with '>'. [line 4] [column 5]
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. (odd SAXParseException) (fatal) The document type declaration for root element type "root" must end with '>'. [line 4] [column 5]
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. (odd SAXParseException) (fatal) The document type declaration for root element type "root" must end with '>'. [line 4] [column 5]
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. (odd SAXParseException) (fatal) White space is required after keyword SYSTEM in DOCTYPE decl. [line 6] [column 23]
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. (odd SAXParseException) (fatal) The system identifier must begin with either a single or double quote character. [line 6] [column 24]
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. (odd SAXParseException) (fatal) White spaces are required between publicId and systemId. [line 4] [column 29]
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. (odd SAXParseException) (fatal) The document type declaration for root element type "root" must end with '>'. [line 4] [column 5]
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. (odd SAXParseException) (fatal) White spaces are required after keyword PUBLIC in DOCTYPE decl. [line 4] [column 11]
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. (odd SAXParseException) (fatal) An invalid XML character (Unicode: 0x5c) was found in the public identifier. [line 4] [column 15]
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. (odd SAXParseException) (fatal) The document type declaration for root element type "root" must end with '>'. [line 4] [column 5]
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. (odd SAXParseException) (fatal) The declaration for the entity "pImage" must end with '>'. [line 6] [column 29]
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. (odd SAXParseException) (fatal) The document type declaration for root element type "root" must end with '>'. [line 4] [column 5]
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. (odd SAXParseException) (fatal) The declaration for the entity "aImage" must end with '>'. [line 8] [column 36]
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. (odd SAXParseException) (fatal) The declaration for the entity "aImage" must end with '>'. [line 8] [column 36]
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. (odd SAXParseException) (fatal) White space is required before "NDATA" in the declaration for the entity "aImage". [line 8] [column 40]
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. (odd SAXParseException) (fatal) The declaration for the entity "aImage" must end with '>'. [line 8] [column 36]
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. (odd SAXParseException) (fatal) White space is required between "NDATA" and the notation name in the declaration for the entity "aImage". [line 8] [column 41]
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. (odd SAXParseException) (fatal) White space is required between "NDATA" and the notation name in the declaration for the entity "aImage". [line 8] [column 41]
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. (odd SAXParseException) (fatal) The declaration for the entity "aImage" must end with '>'. [line 8] [column 36]
4.2.2 [75] dtd04 PUBLIC literal must be quoted (odd SAXParseException) (fatal) The public identifier must begin with either a single or double quote character. [line 4] [column 26]
4.2.2 [75] dtd05 SYSTEM identifier must be quoted (odd SAXParseException) (fatal) The system identifier must begin with either a single or double quote character. [line 4] [column 25]
4.2.2 [75] not-wf-sa-054 PUBLIC requires two literals. (odd SAXParseException) (fatal) White spaces are required between publicId and systemId. [line 2] [column 37]
4.2.2 [75] not-wf-sa-061 External entity declarations require whitespace between public and system IDs. (odd SAXParseException) (fatal) White spaces are required between publicId and systemId. [line 2] [column 29]
4.2.2 [75] o-p75fail1 S required after "PUBLIC" (odd SAXParseException) (fatal) White spaces are required after keyword PUBLIC in DOCTYPE decl. [line 3] [column 20]
4.2.2 [75] o-p75fail2 S required after "SYSTEM" (odd SAXParseException) (fatal) White space is required after keyword SYSTEM in DOCTYPE decl. [line 3] [column 20]
4.2.2 [75] o-p75fail3 S required between literals (odd SAXParseException) (fatal) White spaces are required between publicId and systemId. [line 3] [column 31]
4.2.2 [75] o-p75fail4 "SYSTEM" implies only one literal (odd SAXParseException) (fatal) The declaration for the entity "ent" must end with '>'. [line 3] [column 32]
4.2.2 [75] o-p75fail5 only one keyword (odd SAXParseException) (fatal) The system identifier must begin with either a single or double quote character. [line 3] [column 32]
4.2.2 [75] o-p75fail6 "PUBLIC" requires two literals (contrast with SGML) (odd SAXParseException) (fatal) White spaces are required between publicId and systemId. [line 3] [column 31]
4.2.2 [76] not-wf-sa-069 Space is required before an NDATA entity annotation. (odd SAXParseException) (fatal) White space is required before "NDATA" in the declaration for the entity "foo". [line 4] [column 35]
4.2.2 [76] not-wf-sa-083 Undefined NOTATION n. (odd SAXParseException) (fatal) The unparsed entity reference "&e;" is not permitted. [line 4] [column 9]
4.2.2 [76] o-p76fail1 S is required before "NDATA" (odd SAXParseException) (fatal) White space is required before "NDATA" in the declaration for the entity "ge". [line 5] [column 34]
4.2.2 [76] o-p76fail2 "NDATA" is upper-case (odd SAXParseException) (fatal) The declaration for the entity "ge" must end with '>'. [line 5] [column 30]
4.2.2 [76] o-p76fail3 notation name is required (odd SAXParseException) (fatal) White space is required between "NDATA" and the notation name in the declaration for the entity "ge". [line 5] [column 35]
4.2.2 [76] o-p76fail4 notation names are Names (odd SAXParseException) (fatal) The notation name is required after "NDATA" in the declaration for the entity "ge". [line 6] [column 36]
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". (odd SAXParseException) (fatal) no more pseudo attributes is allowed. [line 1] [column 36]
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". (odd SAXParseException) (fatal) The reference to entity "aExternal" must end with the ';' delimiter. [line 8] [column 17]
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". (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 23]
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". (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 2] [column 1]
4.3.1 4.3.2 [77, 78] not-wf-ext-sa-002 External entities have "text declarations", which do not permit the "standalone=..." attribute that's allowed in XML declarations. (odd SAXParseException) (fatal) The encoding declaration is required in the text declaration. [line 1] [column 37]
4.3.1 [77] decl01 External entities may not have standalone decls. (odd SAXParseException) (fatal) no more pseudo attributes is allowed. [line 1] [column 59]
4.3.1 [77] dtd07 Text declarations (which optionally begin any external entity) are required to have "encoding=...". (odd SAXParseException) (fatal) more pseudo attributes is expected. [line 1] [column 20]
4.3.1 [77] encoding07 Text declarations (which optionally begin any external entity) are required to have "encoding=...". (odd SAXParseException) (fatal) more pseudo attributes is expected. [line 1] [column 20]
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. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 4] [column 6]
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. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
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. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 3] [column 6]
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. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 2] [column 6]
4.3.2 not-wf-sa-074 Internal general parsed entities are only well formed if they match the "content" production. (odd SAXParseException) (fatal) The element "foo" must start and end within the same entity.
4.3.2 not-wf-sa-103 End-tag required for element foo. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
4.3.2 not-wf-sa-104 Internal general parsed entities are only well formed if they match the "content" production. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
4.3.2 not-wf-sa-116 Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
4.3.2 not-wf-sa-117 Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
4.3.2 not-wf-sa-119 Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
4.3.2 not-wf-sa-153 Text declarations may not begin internal parsed entities; they may only appear at the beginning of external parsed (parameter or general) entities. (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed.
4.3.2 not-wf-sa-181 Internal parsed entities must match the content production to be well formed. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
4.3.2 not-wf-sa-182 Internal parsed entities must match the content production to be well formed. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
4.3.2 [79] not-wf-not-sa-007 A <!DOCTYPE ...> declaration may not begin any external entity; it's only found once, in the document entity. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 1] [column 3]
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.) (odd SAXParseException) (fatal) The processing instruction target matching "[xX][mM][lL]" is not allowed. [line 1] [column 7]
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. (odd SAXParseException) (fatal) White space is required before the encoding pseudo attribute in the XML declaration. [line 1] [column 36]
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. (odd SAXParseException) (fatal) The ' = ' character must follow "encoding" in the XML declaration. [line 1] [column 30]
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. (odd SAXParseException) (fatal) The value following "encoding" in the XML declaration must be a quoted string. [line 1] [column 31]
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. (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 21]
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. (odd SAXParseException) (fatal) a pseudo attribute name is expected. [line 1] [column 21]
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. (odd SAXParseException) (fatal) The encoding declaration is required in the text declaration. [line 1] [column 37]
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. (odd SAXParseException) (fatal) Invalid encoding name "_UTF-8". [line 1] [column 40]
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. (odd SAXParseException) (fatal) Invalid encoding name "-UTF-8". [line 1] [column 40]
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. (odd SAXParseException) (fatal) Invalid encoding name ".UTF-8". [line 1] [column 40]
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. (odd SAXParseException) (fatal) Invalid encoding name "8-UTF". [line 1] [column 39]
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. (odd SAXParseException) (fatal) Invalid encoding name "UTF~8". [line 1] [column 39]
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. (odd SAXParseException) (fatal) Invalid encoding name "UTF#8". [line 1] [column 39]
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. (odd SAXParseException) (fatal) Invalid encoding name "UTF:8". [line 1] [column 39]
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. (odd SAXParseException) (fatal) Invalid encoding name "UTF/8". [line 1] [column 39]
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. (odd SAXParseException) (fatal) Invalid encoding name "UTF;8". [line 1] [column 39]
4.3.3 [81] encoding01 Illegal character " " in encoding name (odd SAXParseException) (fatal) Invalid encoding name " utf-8". [line 1] [column 40]
4.3.3 [81] encoding02 Illegal character "/" in encoding name (odd SAXParseException) (fatal) Invalid encoding name "a/b". [line 1] [column 37]
4.3.3 [81] encoding03 Illegal character reference in encoding name (odd SAXParseException) (fatal) Invalid encoding name "just&#41;word". [line 1] [column 47]
4.3.3 [81] encoding04 Illegal character ":" in encoding name (odd SAXParseException) (fatal) Invalid encoding name "utf:8". [line 1] [column 39]
4.3.3 [81] encoding05 Illegal character "@" in encoding name (odd SAXParseException) (fatal) Invalid encoding name "@import(sys-encoding)". [line 1] [column 55]
4.3.3 [81] encoding06 Illegal character "+" in encoding name (odd SAXParseException) (fatal) Invalid encoding name "XYZ+999". [line 1] [column 41]
4.3.3 [81] not-wf-sa-101 Space is not permitted in an encoding name. (odd SAXParseException) (fatal) Invalid encoding name " UTF-8". [line 1] [column 40]
4.5 not-wf-sa-092 The replacement text of this entity has an illegal reference, because the character reference is expanded immediately. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference.
4.5 not-wf-sa-115 The replacement text of this entity is an illegal character reference, which must be rejected when it is parsed in the context of an attribute value. (odd SAXParseException) (fatal) The entity name must immediately follow the '&' in the entity reference. [line 4] [column 12]
4.5 not-wf-sa-120 Character references are expanded in the replacement text of an internal entity, which is then parsed as usual. Accordingly, & must be doubly quoted - encoded either as &amp; or as &#38;#38;. (odd SAXParseException) (fatal) XML document structures must start and end within the same entity.
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. (odd SAXParseException) (fatal) White space is required after "<!NOTATION" in the notation declaration. [line 7] [column 11]
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. (odd SAXParseException) (fatal) The declaration for the notation "PUBLIC" must include a system or public identifier. [line 7] [column 19]
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. (odd SAXParseException) (fatal) The declaration for the notation "JPGformat" must include a system or public identifier. [line 7] [column 22]
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. (odd SAXParseException) (fatal) The declaration for the notation "SYSTEM" must include a system or public identifier. [line 7] [column 19]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 7] [column 3]
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. (odd SAXParseException) (fatal) The declaration for the notation "JPGformat" must end with '>'. [line 8] [column 1]
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. (odd SAXParseException) (fatal) The markup declarations contained or pointed to by the document type declaration must be well-formed. [line 7] [column 2]
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. (odd SAXParseException) (fatal) The declaration for the notation "JPGformat" must end with '>'. [line 7] [column 40]
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. (odd SAXParseException) (fatal) The declaration for the notation "JPGformat" must include a system or public identifier. [line 7] [column 22]
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. (odd SAXParseException) (fatal) Content is not allowed in prolog. [line 1] [column 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. (odd SAXParseException) (fatal) The declaration for the notation "JPGformat" must include a system or public identifier. [line 7] [column 22]
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. (odd SAXParseException) (fatal) White spaces are required after keyword PUBLIC in DOCTYPE decl. [line 7] [column 28]
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. (odd SAXParseException) (fatal) The public identifier must begin with either a single or double quote character. [line 7] [column 30]
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. (odd SAXParseException) (fatal) The declaration for the notation "JPGformat" must include a system or public identifier. [line 7] [column 22]
41. [68] not-wf-sa-077 Undefined ENTITY bar. (odd SAXParseException) (fatal) The entity "bar" was referenced, but not declared.
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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) The processing instruction must begin with the name of the target. [line 3] [column 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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]
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. (odd SAXParseException) (fatal) White space is required between the processing instruction target and data. [line 3] [column 4]

Informative Tests

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

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

Section and [Rules] Test ID Description Diagnostic
2.3, 4.2.2 [11] o-p11pass1 system literals may not contain URI fragments [diagnostic not provided]
2.8 pe01 Parameter entities must consist of a series of complete markup declarations of the types allowed by the nonterminal markupdecl, interespersed with whitespace or PERefs. [diagnostic not provided]
4.2.2 [75] uri01 SYSTEM ids may not have URI fragments [diagnostic not provided]
4.3.3 [4,84] pr-xml-euc-jp Test support for the EUC-JP encoding, and for text which relies on Japanese characters. If a processor does not support this encoding, it must report a fatal error. (Also requires ability to process a moderately complex DTD.) [diagnostic not provided]
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.) [diagnostic not provided]
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.) [diagnostic not provided]
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. [diagnostic not provided]
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. [diagnostic not provided]
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. [diagnostic not provided]

This report was produced by Free Software from http://xmlconf.sourceforge.net, and you should be able to reproduce these results yourself.