XML Processor Conformance Report:
com.sun.xml.parser.ValidatingParser

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

XML Processor Sun TR2
SAX Parser Class com.sun.xml.parser.ValidatingParser
Processing Mode Validating
General Entities included
Parameter Entities included

The test harness and execution environment was:

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

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

Status CONFORMS (provisionally)
Total Passed Tests (provisional) 1065
Passed Negative Tests (provisional) 639
Failed Tests (provisional) 0
Tests Skipped 0

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

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

Explanation of Tables

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

(fatal)
The diagnostic was reported as a fatal error. Such errors are primarily well-formedness errors, such as the violation of XML 1.0 syntax rules or of well formedness constraints.
(error)
The diagnostic was reported as a recoverable error. Such errors primarily used to report validation errors, which are all violations of validity constraints, but some other errors are also classed as nonfatal.
(warning)
The diagnostic was reported as a warning; warnings are purely informative and may be emitted in a number of cases identified by the XML 1.0 specification (as well as in other cases).
(thrown classname) ... abnormal
The named exception was directly thrown. If the exception is a SAXException (or a subclass thereof) this suggests an error in the parser (violating the SAX API specification) since it should normally have used the SAX ErrorHandler instead.
(odd classname) ... abnormal
After the identified exception was reported through the ErrorHandler, an exception of the named class was thrown directly. This suggests an error in the parser, since the parser either failed to continue after an error (or warning) which is required to be continuable, or else it did not pass the exception thrown by the application back to the application.
(EXCEPTION - DIRECTED FAILURE) ... abnormal
This test case was explicitly failed by the test operator; the test was not run. This may be done in the case of parsers with severe bugs which completely prevented handling the test case, typically because the parser seems to "hang" by entering an infinite loop.

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

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

Positive Tests

All conformant XML 1.0 processors must accept "valid" input documents without reporting any errors, and moreover must report the correct output data to the application when processing those documents. Nonvalidating processors 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
2.9 not-sa02 A non-standalone document is valid if declared as such. (warning) Using original entity definition for "&internal;".
2.9 not-sa04 A non-standalone document is valid if declared as such. (warning) Using original entity definition for "&internal;".
2.9 [32] sa03 A document may be marked 'standalone' if any the defined entities need expanding are internal, and no attributes need defaulting or normalization. On output, requires notations to be correctly reported. (warning) Using original entity definition for "&internal;".
2.9 [32] sa04 Like sa03 but relies on attribute defaulting defined in the internal subset. On output, requires notations to be correctly reported. (warning) Using original entity definition for "&internal;".
4.2 valid-sa-086 Tests whether entities may be declared more than once, with the first declaration being the binding one. (warning) Using original entity definition for "&e;".
4.3.3 [4,84] pr-xml-little Test support for little-endian UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.) (warning) Using original entity definition for "&XML.version;".
4.3.3 [4,84] pr-xml-utf-16 Test support UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.) (warning) Using original entity definition for "&XML.version;".
4.3.3 [4,84] weekly-little Test support for little-endian UTF-16 encoding, and XML names which contain Japanese characters. (warning) Using original entity definition for "<".
4.3.3 [4,84] weekly-utf-16 Test support for UTF-16 encoding, and XML names which contain Japanese characters. (warning) Using original entity definition for "<".

Output Tests

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

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

As of this writing, no output tests address the additional requirements which validating processors must satisfy. That is, reporting which whitespace is ignorable, and reporting declarations of unparsed entities.

Test ID Diagnostic
Nothing to report!

Negative Tests

All conformant XML 1.0 processors must reject documents which are not well-formed. In addition, validating processors (such as this one) 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, 639 diagnostics must be examined to get an accurate evaluation of its negative test status.

Invalid Documents

Validating processors must correctly report "error" diagnostics for all documents which are well formed but invalid. Such errors must also be, "at user option", recoverable so that the validating parser may be used in a nonvalidating mode by ignoring all validity errors.

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

Documents which are not Well-Formed

All XML processors must correctly reject (with a "fatal" error) all XML documents which are not well-formed.

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

Informative Tests

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

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

Section and [Rules] Test ID Description Diagnostic
2.11 [33] lang01 Illegal language identification (error) Illegal xml:lang value "234".
2.11 [33] lang02 Illegal language identification (error) Illegal xml:lang value "ab234".
2.11 [33] lang03 Illegal language identification (error) Illegal xml:lang value "ab-".
2.11 [33] lang04 Illegal language identification (error) Illegal xml:lang value "ab-234".
2.11 [33] lang05 Illegal language identification (error) Illegal xml:lang value "i-en/us".
2.11 [33] lang06 Illegal language identification (error) Illegal xml:lang value "X-FR.ch".
2.3, 4.2.2 [11] o-p11pass1 system literals may not contain URI fragments (error) URI "file:/d:/xml/xmlconf/oasis/a%a&b&#0<!ELEMENT<!--<?</>?>/\''" has a fragment ID.
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 (error) URI "file:/d:/xml/xmlconf/sun/not-wf/foo#bar" has a fragment ID.
4.3.3 [4,84] pr-xml-euc-jp Test support for the EUC-JP encoding, and for text which relies on Japanese characters. If a processor does not support this encoding, it must report a fatal error. (Also requires ability to process a moderately complex DTD.) (warning) Using original entity definition for "&XML.version;".
4.3.3 [4,84] pr-xml-iso-2022-jp Test support for the ISO-2022-JP encoding, and for text which relies on Japanese characters. If a processor does not support this encoding, it must report a fatal error. (Also requires ability to process a moderately complex DTD.) (warning) Using original entity definition for "&XML.version;".
4.3.3 [4,84] pr-xml-shift_jis Test support for the Shift_JIS encoding, and for text which relies on Japanese characters. If a processor does not support this encoding, it must report a fatal error. (Also requires ability to process a moderately complex DTD.) (warning) Using original entity definition for "&XML.version;".
4.3.3 [4,84] weekly-euc-jp Test support for EUC-JP encoding, and XML names which contain Japanese characters. If a processor does not support this encoding, it must report a fatal error. (warning) Using original entity definition for "&lt;".
4.3.3 [4,84] weekly-iso-2022-jp Test support for ISO-2022-JP encoding, and XML names which contain Japanese characters. If a processor does not support this encoding, it must report a fatal error. (warning) Using original entity definition for "&lt;".
4.3.3 [4,84] weekly-shift_jis Test support for Shift_JIS encoding, and XML names which contain Japanese characters. If a processor does not support this encoding, it must report a fatal error. (warning) Using original entity definition for "&lt;".