XML Processor Conformance Report:
Xerces.DOMDocument

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

XML Processor Xerces/COM v.current
Parser Class Xerces.DOMDocument
Processing Mode Validating
General Entities included
Parameter Entities included

The results were as reported through the parser's API to this particular test harness and execution environment:

Test Run Date Sun, 16 Jul 2000 20:26:50 UTC
Harness and Version ECMAScript version
$Id: harness.js,v 1.3 2000/07/16 14:05:28 dbrownell Exp $
Runtime Environment Microsoft JScript Version 5.5.5207
Host OS Info Undetermined version of MS-Windows
Suite of Testcases OASIS draft v1.0; (with 5 Feb 2000 updates by David Brownell)

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

Status DOES NOT CONFORM
Total Passed Tests (provisional) 1055
Passed Negative Tests (provisional) 636
Failed Tests (provisional) 17
Tests Skipped 0

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

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


Explanation of Tables

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

Some such comments indicate the reporting category defined in the XML specification. Some low-fidelity processor APIs don't expose recoverable errors, which can make validation work awkward.

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

Other such comments may indicate other categories of conformance issue. For example, some errors relate to problematic implementation of SAX; and in exceptional cases, the harness can be forced to report a failure on some test.

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

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


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 [32]sa02A document may be marked 'standalone' if any attributes that need normalization are defined within the internal DTD subset.(fatal) Bad standalone declaration
2.9 [32]sa03A 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.(fatal) Bad standalone declaration
2.9 [32]sa04Like sa03 but relies on attribute defaulting defined in the internal subset. On output, requires notations to be correctly reported.(fatal) Bad standalone declaration

Output Tests

The XML specification places requirements on the data which is reported by XML processors to applications. This data flows through the processor API ... or it is not available, so the processor is in those respects nonconformant. For example, SAX1 did not report external entities which were not included; but SAX2 does. These output tests verify conformance with the specification by recording that data and comparing it with what is required for conformance with the XML 1.0 specification.

At this writing, the OASIS output tests have several categories of known omissions (or weak output test coverage). These include:

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

In some test harnessses, the output tests are unreliable because they can't directly compare the parser output against reference data. Such issues should be noted in the documentation for that harness.

Also, and not a bug, in some cases these diagnostics may seem like they say two equivalent results are not equal. The issue is that some differences, often those in reported whitespace, aren't easily visible in this report. HTML hides many such differences (because it normalizes whitespace before displaying it), and the method used to display the differing results may also mask some issues.

Test ID Diagnostic
notation01incorrect notation decl: GIF
sa02[ input failed, no output to test ]
sa03[ input failed, no output to test ]
sa04[ input failed, no output to test ]

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, 636 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. Some parser APIs do not support recoverability. Such issues should be noted in the documentation for the API, and for its test harness.

Section and [Rules] Test ID Description Diagnostic
4.1not-wf-not-sa-005Tests the Entity Declared VC by referring to an undefined parameter entity within an external entity.(fatal) Entity 'e' was not found
2.8invalid--001Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting a comment between two parameter entities.(fatal) Partial markup in entity value
3.2.1invalid--002Tests the "Proper Group/PE Nesting" validity constraint by fragmenting a content model between two parameter entities.(fatal) Partial markup in entity value
2.8invalid--003Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between two parameter entities.(fatal) Partial markup in entity value
2.8invalid--004Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between three parameter entities.(fatal) Partial markup in entity value
2.8invalid--005Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between two parameter entities.(fatal) Partial markup in entity value
2.8invalid--006Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between two parameter entities.(fatal) Partial markup in entity value
2.4 2.7 [18]emptyWhitespace found in CDATA sections (and entity references?) is unlike other whitespace[wrongly accepted]
3.2.2inv-dtd01Tests the No Duplicate Types VC(fatal) Element types cannot be duplicated in Mixed content models
4.2.2inv-dtd02Tests the "Notation Declared" VC by using an undeclared notation name.(fatal) Notation 'Encyclopaedia' was referenced but never declared
3inv-dtd03Tests the "Element Valid" VC (clause 2) by omitting a required element.(fatal) Element 'b' is not valid for content model: '(a,a,a,b)'
4.1inv-dtd06Tests "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.(fatal) Entity 'undefined' was not found
3el01Tests the Element Valid VC (clause 4) by including an undeclared child element.(fatal) Unknown element 'undeclared'
3el02Tests the Element Valid VC (clause 1) by including elements in an EMPTY content model.(fatal) Element 'root' is not valid for content model: 'EMPTY'
3el03Tests the Element Valid VC (clause 3) by including a child element not permitted by a mixed content model.(fatal) Element 'exception' is not valid for content model: '(#PCDATA|root)*'
3.2el04Tests the Unique Element Type Declaration VC.(fatal) Element 'exception' has already been declared
3.2.2el05Tests the No Duplicate Types VC.(fatal) Element types cannot be duplicated in Mixed content models
3el06Tests the Element Valid VC (clause 1), using one of the predefined internal entities inside an EMPTY content model.(fatal) No character data is allowed by content model
3.3.1id01Tests the ID (is a Name) VC(fatal) The values for attribute 'id' must be names or name tokens
3.3.1id02Tests the ID (appears once) VC(fatal) ID 'a42' has already been used
3.3.1id03Tests the One ID per Element Type VC(fatal) Element 'attributes' has more than one ID attribute
3.3.1id04Tests the ID Attribute Default VC(fatal) ID attributes must be #IMPLIED or #REQUIRED
3.3.1id05Tests the ID Attribute Default VC(fatal) ID attributes must be #IMPLIED or #REQUIRED
3.3.1id06Tests the IDREF (is a Name) VC(fatal) The values for attribute 'idref' must be names or name tokens
3.3.1id07Tests the IDREFS (is a Names) VC(fatal) The values for attribute 'idrefs' must be names or name tokens
3.3.1id08Tests the IDREF (matches an ID) VC(fatal) ID attribute 'd36d' was referenced but never declared
3.3.1id09Tests the IDREF (IDREFS matches an ID) VC(fatal) ID attribute 'ee38' was referenced but never declared
2.9inv-not-sa01Tests the Standalone Document Declaration VC, ensuring that optional whitespace causes a validity error.[wrongly accepted]
2.9inv-not-sa02Tests the Standalone Document Declaration VC, ensuring that attributes needing normalization cause a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa03Tests the Standalone Document Declaration VC, ensuring that a reference to externally defined entity causes a validity error.(fatal) Reference to external declaration in standalone document. Entity=number
2.9inv-not-sa04Tests the Standalone Document Declaration VC, ensuring that attributes needing defaulting cause a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa05Tests the Standalone Document Declaration VC, ensuring that a token attribute that needs normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa06Tests the Standalone Document Declaration VC, ensuring that a NOTATION attribute that needs normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa07Tests the Standalone Document Declaration VC, ensuring that an NMTOKEN attribute needing normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa08Tests the Standalone Document Declaration VC, ensuring that an NMTOKENS attribute needing normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa09Tests the Standalone Document Declaration VC, ensuring that an ID attribute needing normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa10Tests the Standalone Document Declaration VC, ensuring that an IDREF attribute needing normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa11Tests the Standalone Document Declaration VC, ensuring that an IDREFS attribute needing normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa12Tests the Standalone Document Declaration VC, ensuring that an ENTITY attribute needing normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa13Tests the Standalone Document Declaration VC, ensuring that an ENTITIES attribute needing normalization causes a validity error.(fatal) Bad standalone declaration
2.9inv-not-sa14Tests the Standalone Document Declaration VC, ensuring that optional whitespace causes a validity error (even if it's CDATA whitespace).(fatal) Bad standalone declaration
3optional01Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one is required.(fatal) Empty content not valid for content model: '(e)'
3optional02Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing two children where one is required.(fatal) Element 'e' is not valid for content model: '(e)'
3optional03Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where two are required.(fatal) Empty content not valid for content model: '(e,e)'
3optional04Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where two are required.(fatal) Element 'e' is not valid for content model: '(e,e)'
3optional05Tests 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).(fatal) Empty content not valid for content model: '(e,e?)'
3optional06Tests 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).(fatal) Empty content not valid for content model: '(e,e?)'
3optional07Tests 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).(fatal) Empty content not valid for content model: '(e,e?)'
3optional08Tests 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).(fatal) Empty content not valid for content model: '(e,e?)'
3optional09Tests 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).(fatal) Empty content not valid for content model: '(e,e?)'
3optional10Tests 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).(fatal) Element 'e' is not valid for content model: '(e,e?)'
3optional11Tests 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).(fatal) Element 'e' is not valid for content model: '(e,e?)'
3optional12Tests 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).(fatal) Element 'e' is not valid for content model: '(e,e?)'
3optional13Tests 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).(fatal) Element 'e' is not valid for content model: '(e,e?)'
3optional14Tests 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).(fatal) Element 'e' is not valid for content model: '(e,e?)'
3optional15Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional16Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional17Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional18Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional19Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional20Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional21Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional22Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional23Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional24Tests 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).(fatal) Empty content not valid for content model: '(e,e?,e*)'
3optional25Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing text content where one or more elements are required.(fatal) No character data is allowed by content model
3.3.2inv-required00Tests the Required Attribute VC.(fatal) Required attribute 'req' was not provided
3.1 2.10inv-required01Tests the Attribute Value Type (declared) VC for the xml:space attribute(fatal) Attribute 'xml:space' is not declared for element 'root'
3.1 2.12inv-required02Tests the Attribute Value Type (declared) VC for the xml:lang attribute(fatal) Attribute 'xml:lang' is not declared for element 'root'
2.8rootTests the Root Element Type VC(fatal) Root element different from DOCTYPE
3.3.1attr01Tests the "Entity Name" VC for the ENTITY attribute type.(fatal) Attribute 'affiliated' refers to an unknown entity 'food'
3.3.1attr02Tests the "Entity Name" VC for the ENTITIES attribute type.(fatal) Attribute 'affiliated' refers to an unknown entity 'food'
3.3.1attr03Tests the "Notation Attributes" VC for the NOTATION attribute type, first clause: value must be one of the ones that's declared.(fatal) Attribute 'type' does not match its defined enumeration or notation list
3.3.1attr04Tests the "Notation Attributes" VC for the NOTATION attribute type, second clause: the names in the declaration must all be declared.(fatal) Attribute 'type' refers to an unknown notation 'vegetable'
3.3.1attr05Tests the "Name Token" VC for the NMTOKEN attribute type.(fatal) The values for attribute 'token' must be names or name tokens
3.3.1attr06Tests the "Name Token" VC for the NMTOKENS attribute type.(fatal) Attribute 'token' does not support multiple values
3.3.1attr07Tests the "Enumeration" VC by providing a value which wasn't one of the choices.(fatal) Attribute 'type' does not match its defined enumeration or notation list
3.3.2attr08Tests the "Fixed Attribute Default" VC by providing the wrong value.(fatal) Attribute 'xmlns' has a value, 'http://over.the.rainbow.com/somewhere', that does not match its #FIXED value, 'http://java.sun.com/historical'
3.3.2attr09Tests the "Attribute Default Legal" VC by providing an illegal IDREF value.(fatal) The values for attribute 'value' must be names or name tokens
3.3.2attr10Tests the "Attribute Default Legal" VC by providing an illegal IDREFS value.(fatal) The values for attribute 'value' must be names or name tokens
3.3.2attr11Tests the "Attribute Default Legal" VC by providing an illegal ENTITY value.(fatal) Attributes of type ENTITY/ENTITIES must refer to an external, unparsed entity
3.3.2attr12Tests the "Attribute Default Legal" VC by providing an illegal ENTITIES value.(fatal) Attributes of type ENTITY/ENTITIES must refer to an external, unparsed entity
3.3.2attr13Tests the "Attribute Default Legal" VC by providing an illegal NMTOKEN value.(fatal) The values for attribute 'value' must be names or name tokens
3.3.2attr14Tests the "Attribute Default Legal" VC by providing an illegal NMTOKENS value.(fatal) The values for attribute 'value' must be names or name tokens
3.3.2attr15Tests the "Attribute Default Legal" VC by providing an illegal NOTATIONS value.(fatal) Attribute 'source' does not match its defined enumeration or notation list
3.3.2attr16Tests the "Attribute Default Legal" VC by providing an illegal enumeration value.(fatal) Attribute 'value' does not match its defined enumeration or notation list
4.3.3 2.8utf16bTests reading an invalid "big endian" UTF-16 document(fatal) Unknown element 'root'
4.3.3 2.8utf16lTests reading an invalid "little endian" UTF-16 document(fatal) Unknown element 'root'
2.11 [33]lang01Tests the "Valid xml:lang" Validity Constraint. Illegal language identification[wrongly accepted]
2.11 [33]lang02Tests the "Valid xml:lang" Validity Constraint. Illegal language identification[wrongly accepted]
2.11 [33]lang03Tests the "Valid xml:lang" Validity Constraint. Illegal language identification[wrongly accepted]
2.11 [33]lang04Tests the "Valid xml:lang" Validity Constraint. Illegal language identification[wrongly accepted]
2.11 [33]lang05Tests the "Valid xml:lang" Validity Constraint. Illegal language identification[wrongly accepted]
2.11 [33]lang06Tests the "Valid xml:lang" Validity Constraint. Illegal language identification[wrongly accepted]
2.1 [1]o-p01pass1no prolog(fatal) Unknown element 'doc'
2.1 [1]o-p01pass3Misc items after the document(fatal) Unknown element 'doc'
2.3 [3]o-p03pass1all valid S characters(fatal) Unknown element 'doc'
2.3 [4]o-p04pass1names with all valid ASCII characters, and one from each other class in NameChar(fatal) Unknown element 'doc'
2.3 [5]o-p05pass1various valid Name constructions(fatal) Unknown element 'doc'
2.3 [6]o-p06fail1Requires at least one name.(fatal) This type of attribute cannot have an empty value
2.3 [8]o-p08fail1at least one Nmtoken is required.(fatal) This type of attribute cannot have an empty value
2.3 [8]o-p08fail2an invalid Nmtoken character.(fatal) The values for attribute 'att' must be names or name tokens
2.3 [10]o-p10pass1valid attribute values(fatal) Unknown element 'doc'
2.4 [14]o-p14pass1valid CharData(fatal) Unknown element 'doc'
2.5 [15]o-p15pass1valid comments(fatal) Unknown element 'doc'
2.6 [16]o-p16fail3S after PITarget is required(fatal) Unknown element 'doc'
2.6 [16] [17]o-p16pass1Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.(fatal) Unknown element 'doc'
2.6 [16]o-p16pass2Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.(fatal) Unknown element 'doc'
2.6 [16]o-p16pass3Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.(fatal) Unknown element 'doc'
2.7 [18]o-p18pass1valid CDSect's. Note that a CDStart in a CDSect is not recognized as such(fatal) Unknown element 'doc'
2.8 [22]o-p22pass1prolog can be empty(fatal) Unknown element 'doc'
2.8 [22]o-p22pass2XML declaration only(fatal) Unknown element 'doc'
2.8 [22]o-p22pass3XML decl and Misc(fatal) Unknown element 'doc'
2.8 [23]o-p23pass1Test shows a valid XML declaration along with version info.(fatal) Unknown element 'doc'
2.8 [23]o-p23pass2Test shows a valid XML declaration along with encoding declaration.(fatal) Unknown element 'doc'
2.8 [23]o-p23pass3Test shows a valid XML declaration along with Standalone Document Declaration.(fatal) Unknown element 'doc'
2.8 [23]o-p23pass4Test shows a valid XML declaration, encoding declarationand Standalone Document Declaration.(fatal) Unknown element 'doc'
2.8 [24]o-p24pass1Test shows a prolog that has the VersionInfo delimited by double quotes.(fatal) Unknown element 'doc'
2.8 [24]o-p24pass2Test shows a prolog that has the VersionInfo delimited by single quotes.(fatal) Unknown element 'doc'
2.8 [24]o-p24pass3Test shows whitespace is allowed in prolog before version info.(fatal) No processing instruction starts with 'xml'
2.8 [24]o-p24pass4Test shows whitespace is allowed in prolog on both sides of equal sign.(fatal) Unknown element 'doc'
2.8 [25]o-p25pass1Test shows whitespace is NOT necessary before or after equal sign of versioninfo.(fatal) Unknown element 'doc'
2.8 [25]o-p25pass2Test shows whitespace can be used on both sides of equal sign of versioninfo.(fatal) Unknown element 'doc'
2.8 [26]o-p26pass1The valid version number. We cannot test others because a 1.0 processor is allowed to fail them.(fatal) Unknown element 'doc'
2.8 [27]o-p27pass1Comments are valid as the Misc part of the prolog.(fatal) Unknown element 'doc'
2.8 [27]o-p27pass2Processing Instructions are valid as the Misc part of the prolog.(fatal) Unknown element 'doc'
2.8 [27]o-p27pass3Whitespace is valid as the Misc part of the prolog.(fatal) Unknown element 'doc'
2.8 [27]o-p27pass4A combination of comments, whitespaces and processing instructions are valid as the Misc part of the prolog.(fatal) Unknown element 'doc'
2.9 [32]o-p32pass1Double quotes can be used as delimeters for the value of a Standalone Document Declaration.(fatal) Unknown element 'doc'
2.9 [32]o-p32pass2Single quotes can be used as delimeters for the value of a Standalone Document Declaration.(fatal) Unknown element 'doc'
3 3.1 [39] [44]o-p39pass1Empty element tag may be used for any element which has no content.(fatal) Unknown element 'doc'
3 3.1 [39] [43]o-p39pass2Character data is valid element content.(fatal) Unknown element 'doc'
3.1 [40]o-p40pass1Elements content can be empty.(fatal) Unknown element 'doc'
3.1 [40]o-p40pass2Whitespace is valid within a Start-tag.(fatal) Unknown element 'doc'
3.1 [40] [41]o-p40pass3Attributes are valid within a Start-tag.(fatal) Unknown element 'doc'
3.1 [40]o-p40pass4Whitespace and Multiple Attributes are valid within a Start-tag.(fatal) Unknown element 'doc'
3.1 [41]o-p41pass1Attributes are valid within a Start-tag.(fatal) Unknown element 'doc'
3.1 [41]o-p41pass2Whitespace is valid within a Start-tags Attribute.(fatal) Unknown element 'doc'
3.1 [42]o-p42pass1Test shows proper syntax for an End-tag.(fatal) Unknown element 'doc'
3.1 [42]o-p42pass2Whitespace is valid after name in End-tag.(fatal) Unknown element 'doc'
3.1 [44]o-p44pass1Valid display of an Empty Element Tag.(fatal) Unknown element 'doc'
3.1 [44]o-p44pass2Empty Element Tags can contain an Attribute.(fatal) Unknown element 'doc'
3.1 [44]o-p44pass3Whitespace is valid in an Empty Element Tag following the end of the attribute value.(fatal) Unknown element 'doc'
3.1 [44]o-p44pass4Whitespace is valid after the name in an Empty Element Tag.(fatal) Unknown element 'doc'
3.1 [44]o-p44pass5Whitespace and Multiple Attributes are valid in an Empty Element Tag.(fatal) Unknown element 'doc'
4.1 [66]o-p66pass1valid character references(fatal) Unknown element 'doc'
4.2 [74]o-p74pass1PEDef is either an entity value or an external id(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.2.2 [75]o-p75pass1valid external identifiers(fatal) Element 'doc' was used in the DOCTYPE but never 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
3.1 [41]not-wf-sa-001Attribute values must start with attribute names, not "?".(fatal) Unknown element 'doc'
2.3 [4]not-wf-sa-002Names may not start with "."; it's not a Letter.(fatal) Unknown element 'doc'
2.6 [16]not-wf-sa-003Processing Instruction target name is required.(fatal) Unknown element 'doc'
2.6 [16]not-wf-sa-004SGML-ism: processing instructions end in '?>' not '>'.(fatal) Unknown element 'doc'
2.6 [16]not-wf-sa-005Processing instructions end in '?>' not '?'.(fatal) Unknown element 'doc'
2.5 [16]not-wf-sa-006XML comments may not contain "--"(fatal) Unknown element 'doc'
4.1 [68]not-wf-sa-007General entity references have no whitespace after the entity name and before the semicolon.(fatal) Unknown element 'doc'
2.3 [5]not-wf-sa-008Entity references must include names, which don't begin with '.' (it's not a Letter or other name start character).(fatal) Unknown element 'doc'
4.1 [66]not-wf-sa-009Character references may have only decimal or numeric strings.(fatal) Unknown element 'doc'
4.1 [68]not-wf-sa-010Ampersand may only appear as part of a general entity reference.(fatal) Unknown element 'doc'
3.1 [41]not-wf-sa-011SGML-ism: attribute values must be explicitly assigned a value, it can't act as a boolean toggle.(fatal) Unknown element 'doc'
2.3 [10]not-wf-sa-012SGML-ism: attribute values must be quoted in all cases.(fatal) Unknown element 'doc'
2.3 [10]not-wf-sa-013The quotes on both ends of an attribute value must match.(fatal) Unknown element 'doc'
2.3 [10]not-wf-sa-014Attribute values may not contain literal '<' characters.(fatal) Unknown element 'doc'
3.1 [41]not-wf-sa-015Attribute values need a value, not just an equals sign.(fatal) Unknown element 'doc'
3.1 [41]not-wf-sa-016Attribute values need an associated name.(fatal) Unknown element 'doc'
2.7 [18]not-wf-sa-017CDATA sections need a terminating ']]>'.(fatal) Unknown element 'doc'
2.7 [19]not-wf-sa-018CDATA sections begin with a literal '<![CDATA[', no space.(fatal) Unknown element 'doc'
3.1 [42]not-wf-sa-019End tags may not be abbreviated as '</>'.(fatal) Unknown element 'doc'
2.3 [10]not-wf-sa-020Attribute values may not contain literal '&' characters except as part of an entity reference.(fatal) Unknown element 'doc'
2.3 [10]not-wf-sa-021Attribute values may not contain literal '&' characters except as part of an entity reference.(fatal) Unknown element 'doc'
4.1 [66]not-wf-sa-022Character references end with semicolons, always!(fatal) Unknown element 'doc'
2.3 [5]not-wf-sa-023Digits are not valid name start characters.(fatal) Unknown element 'doc'
2.3 [5]not-wf-sa-024Digits are not valid name start characters.(fatal) Unknown element 'doc'
2.4 [14]not-wf-sa-025Text may not contain a literal ']]>' sequence.(fatal) Unknown element 'doc'
2.4 [14]not-wf-sa-026Text may not contain a literal ']]>' sequence.(fatal) Unknown element 'doc'
2.5 [15]not-wf-sa-027Comments must be terminated with "-->".(fatal) Unknown element 'doc'
2.6 [16]not-wf-sa-028Processing instructions must end with '?>'.(fatal) Unknown element 'doc'
2.4 [14]not-wf-sa-029Text may not contain a literal ']]>' sequence.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-030A form feed is not a legal XML character.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-031A form feed is not a legal XML character.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-032A form feed is not a legal XML character.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-033An ESC (octal 033) is not a legal XML character.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-034A form feed is not a legal XML character.(fatal) Unknown element 'doc'
3.1 [43]not-wf-sa-035The '<' character is a markup delimiter and must start an element, CDATA section, PI, or comment.(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-036Text may not appear after the root element.(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-037Character references may not appear after the root element.(fatal) Unknown element 'doc'
3.1not-wf-sa-038Tests the "Unique Att Spec" WF constraint by providing multiple values for an attribute.(fatal) Unknown element 'doc'
3not-wf-sa-039Tests the Element Type Match WFC - end tag name must match start tag name.(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-040Provides two document elements.(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-041Provides two document elements.(fatal) Unknown element 'doc'
3.1 [42]not-wf-sa-042Invalid End Tag(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-043Provides #PCDATA text after the document element.(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-044Provides two document elements.(fatal) Unknown element 'doc'
3.1 [44]not-wf-sa-045Invalid Empty Element Tag(fatal) Unknown element 'doc'
3.1 [40]not-wf-sa-046This start (or empty element) tag was not terminated correctly.(fatal) Unknown element 'doc'
3.1 [44]not-wf-sa-047Invalid empty element tag invalid whitespace(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-048Provides a CDATA section after the roor element.(fatal) Unknown element 'doc'
3.1 [40]not-wf-sa-049Missing start tag(fatal) Unknown element 'doc'
2.1 [1]not-wf-sa-050Empty document, with no root element.(fatal) The main XML document cannot be empty
2.7 [18]not-wf-sa-051CDATA is invalid at top level of document.(fatal) CDATA is not allowed outside the root element
4.1 [66]not-wf-sa-052Invalid character reference.(fatal) Invalid document structure
3.1 [42]not-wf-sa-053End tag does not match start tag.(fatal) Unknown element 'doc'
4.2.2 [75]not-wf-sa-054PUBLIC requires two literals.(fatal) Expected whitespace
2.8 [28]not-wf-sa-055Invalid Document Type Definition format.(fatal) Expected a markup declaration
2.8 [28]not-wf-sa-056Invalid Document Type Definition format - misplaced comment.(fatal) Expected system or public id
3.2 [45]not-wf-sa-057This isn't SGML; comments can't exist in declarations.(fatal) Unterminated entity declaration, 'e'
3.3.1 [54]not-wf-sa-058Invalid character , in ATTLIST enumeration(fatal) Expected | enumeration separator, or closing paren
3.3.1 [59]not-wf-sa-059String literal must be in quotes.(fatal) Expected default attribute declaration, assuming #IMPLIED
3.3.1 [56]not-wf-sa-060Invalid type NAME defined in ATTLIST.(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'a1' of element 'doc'
4.2.2 [75]not-wf-sa-061External entity declarations require whitespace between public and system IDs.(fatal) Expected whitespace
4.2 [71]not-wf-sa-062Entity declarations need space after the entity name.(fatal) Expected whitespace
2.8 [29]not-wf-sa-063Conditional sections may only appear in the external DTD subset.(fatal) Conditional section in internal subset
3.3 [53]not-wf-sa-064Space is required between attribute type and default values in <!ATTLIST...> declarations.(fatal) Expected whitespace
3.3 [53]not-wf-sa-065Space is required between attribute name and type in <!ATTLIST...> declarations.(fatal) Expected whitespace
3.3 [52]not-wf-sa-066Required whitespace is missing.(fatal) Expected whitespace
3.3 [53]not-wf-sa-067Space is required between attribute type and default values in <!ATTLIST...> declarations.(fatal) Expected whitespace
3.3.1 [58]not-wf-sa-068Space is required between NOTATION keyword and list of enumerated choices in <!ATTLIST...> declarations.(fatal) Expected whitespace
4.2.2 [76]not-wf-sa-069Space is required before an NDATA entity annotation.(fatal) Expected whitespace
2.5 [16]not-wf-sa-070XML comments may not contain "--"(fatal) Illegal sequence '--' in comment
4.1 [68]not-wf-sa-071ENTITY can't reference itself directly or indirectly.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1 [68]not-wf-sa-072Undefined ENTITY foo.(fatal) Unknown element 'doc'
4.1 [68]not-wf-sa-073Undefined ENTITY f.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.3.2not-wf-sa-074Internal general parsed entities are only well formed if they match the "content" production.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1 [68]not-wf-sa-075ENTITY can't reference itself directly or indirectly.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1 [68]not-wf-sa-076Undefined ENTITY foo.(fatal) Unknown element 'doc'
41. [68]not-wf-sa-077Undefined ENTITY bar.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1 [68]not-wf-sa-078Undefined ENTITY foo.(fatal) Entity 'foo' was not found
4.1 [68]not-wf-sa-079ENTITY can't reference itself directly or indirectly.(fatal) Recursive entity expansion
4.1 [68]not-wf-sa-080ENTITY can't reference itself directly or indirectly.(fatal) Recursive entity expansion
3.1not-wf-sa-081This tests the No External Entity References WFC, since the entity is referred to within an attribute.(fatal) Element 'doc' was used in the DOCTYPE but never declared
3.1not-wf-sa-082This tests the No External Entity References WFC, since the entity is referred to within an attribute.(fatal) External entities cannot be referred to from attribute values
4.2.2 [76]not-wf-sa-083Undefined NOTATION n.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1not-wf-sa-084Tests 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) Unparsed entitty references, 'e', not valid here
2.3 [13]not-wf-sa-085Public IDs may not contain "[".(fatal) Invalid character in public id (Unicode: 0x5B)
2.3 [13]not-wf-sa-086Public IDs may not contain "[".(fatal) Invalid character in public id (Unicode: 0x5B)
2.3 [13]not-wf-sa-087Public IDs may not contain "[".(fatal) Invalid character in public id (Unicode: 0x5B)
2.3 [10]not-wf-sa-088Attribute values are terminated by literal quote characters, and any entity expansion is done afterwards.(fatal) A '<' character cannot be used in attribute 'a', except through &lt;
4.2 [74]not-wf-sa-089Parameter entities "are" always parsed; NDATA annotations are not permitted.(fatal) NDATA is not legal for parameter entities
2.3 [10]not-wf-sa-090Attributes may not contain a literal "<" character; this one has one because of reference expansion.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.2 [74]not-wf-sa-091Parameter entities "are" always parsed; NDATA annotations are not permitted.(fatal) NDATA is not legal for parameter entities
4.5not-wf-sa-092The replacement text of this entity has an illegal reference, because the character reference is expanded immediately.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1 [66]not-wf-sa-093Hexadecimal character references may not use the uppercase 'X'.(fatal) Unknown element 'doc'
2.8 [24]not-wf-sa-094Prolog VERSION must be lowercase.(fatal) Expected a 'version=', 'encoding=', or 'standalone='
2.8 [23]not-wf-sa-095VersionInfo must come before EncodingDecl.(fatal) The XMLDecl strings must be in the order: version, encoding, standalone
2.9 [32]not-wf-sa-096Space is required before the standalone declaration.(fatal) Expected whitespace
2.8 [24]not-wf-sa-097Both quotes surrounding VersionNum must be the same.(fatal) Unsupported XML version, '1.0' encoding='
2.8 [23]not-wf-sa-098Only one "version=..." string may appear in an XML declaration.(fatal) 'version' has already been set. Ignoring redundant setting
2.8 [23]not-wf-sa-099Only three pseudo-attributes are in the XML declaration, and "valid=..." is not one of them.(fatal) Expected a 'version=', 'encoding=', or 'standalone='
2.9 [32]not-wf-sa-100Only "yes" and "no" are permitted as values of "standalone".(fatal) Bad standalone declaration
4.3.3 [81]not-wf-sa-101Space is not permitted in an encoding name.(fatal) An exception occured! Type:TranscodingException, Message:Could not create a converter for encoding: UTF-8
2.8 [26]not-wf-sa-102Provides an illegal XML version number; spaces are illegal.(fatal) Unsupported XML version, '1.0 '
4.3.2not-wf-sa-103End-tag required for element foo.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.3.2not-wf-sa-104Internal general parsed entities are only well formed if they match the "content" production.(fatal) Element 'doc' was used in the DOCTYPE but never declared
2.7 not-wf-sa-105Invalid placement of CDATA section.(fatal) CDATA is not allowed outside the root element
4.2not-wf-sa-106Invalid placement of entity declaration.(fatal) Invalid document structure
2.8 [28]not-wf-sa-107Invalid document type declaration. CDATA alone is invalid.(fatal) Conditional section in internal subset
2.7 [19]not-wf-sa-108No space in '<![CDATA['.(fatal) Unknown element 'doc'
4.2 [70]not-wf-sa-109Tags invalid within EntityDecl.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1 [68]not-wf-sa-110Entity reference must be in content of element.(fatal) Element 'doc' was used in the DOCTYPE but never declared
3.1 [43]not-wf-sa-111Entiry reference must be in content of element not Start-tag.(fatal) Element 'doc' was used in the DOCTYPE but never declared
2.7 [19]not-wf-sa-112CDATA sections start '<![CDATA[', not '<!cdata['.(fatal) Unknown element 'doc'
2.3 [9]not-wf-sa-113Parameter entity values must use valid reference syntax; this reference is malformed.(fatal) Expected entity name for reference
2.3 [9]not-wf-sa-114General entity values must use valid reference syntax; this reference is malformed.(fatal) Expected entity name for reference
4.5not-wf-sa-115The 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) Element 'doc' was used in the DOCTYPE but never declared
4.3.2not-wf-sa-116Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.3.2not-wf-sa-117Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.1 [68]not-wf-sa-118Entity reference expansion is not recursive.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.3.2not-wf-sa-119Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.5not-wf-sa-120Character 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) Element 'doc' was used in the DOCTYPE but never declared
4.1 [68]not-wf-sa-121A name of an ENTITY was started with an invalid character.(fatal) Expected parameter entity name
3.2.1 [47]not-wf-sa-122Invalid syntax mixed connectors are used.(fatal) Expected '|' or ')' characters
3.2.1 [48]not-wf-sa-123Invalid syntax mismatched parenthesis.(fatal) Unterminated element declaration, 'doc'
3.2.2 [51]not-wf-sa-124Invalid format of Mixed-content declaration.(fatal) Expected an element name
3.2.2 [51]not-wf-sa-125Invalid syntax extra set of parenthesis not necessary.(fatal) Expected an element name
3.2.2 [51]not-wf-sa-126Invalid syntax Mixed-content must be defined as zero or more.(fatal) Unterminated element declaration, 'doc'
3.2.2 [51]not-wf-sa-127Invalid syntax Mixed-content must be defined as zero or more.(fatal) Unterminated element declaration, 'doc'
2.7 [18]not-wf-sa-128Invalid CDATA syntax.(fatal) Expected content specification expression for element 'doc'
3.2 [45]not-wf-sa-129Invalid syntax for Element Type Declaration.(fatal) Expected content specification expression for element 'doc'
3.2 [45]not-wf-sa-130Invalid syntax for Element Type Declaration.(fatal) Unterminated element declaration, 'doc'
3.2 [45]not-wf-sa-131Invalid syntax for Element Type Declaration.(fatal) Unterminated element declaration, 'doc'
3.2.1 [50]not-wf-sa-132Invalid syntax mixed connectors used.(fatal) Expected '|' or ')' characters
3.2.1not-wf-sa-133Illegal whitespace before optional character causes syntax error.(fatal) Unexpected whitespace
3.2.1not-wf-sa-134Illegal whitespace before optional character causes syntax error.(fatal) Unterminated element declaration, 'doc'
3.2.1 [47]not-wf-sa-135Invalid character used as connector.(fatal) Expected ',', '|', or ')' characters
3.2 [45]not-wf-sa-136Tag omission is invalid in XML.(fatal) Expected content specification expression for element 'doc'
3.2 [45]not-wf-sa-137Space is required before a content model.(fatal) Expected whitespace
3.2.1 [48]not-wf-sa-138Invalid syntax for content particle.(fatal) Expected ',', '|', or ')' characters
3.2.1 [46]not-wf-sa-139The element-content model should not be empty.(fatal) Expected an element name
2.3 [4]not-wf-sa-140Character '&#x309a;' is a CombiningChar, not a Letter, and so may not begin a name.(fatal) Element 'doc' was used in the DOCTYPE but never declared
2.3 [5]not-wf-sa-141Character #x0E5C is not legal in XML names.(fatal) Element 'doc' was used in the DOCTYPE but never declared
2.2 [2]not-wf-sa-142Character #x0000 is not legal anywhere in an XML document.(fatal) Invalid character reference
2.2 [2]not-wf-sa-143Character #x001F is not legal anywhere in an XML document.(fatal) Invalid character reference
2.2 [2]not-wf-sa-144Character #xFFFF is not legal anywhere in an XML document.(fatal) Invalid character reference
2.2 [2]not-wf-sa-145Character #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) Invalid character reference
2.2 [2]not-wf-sa-146Character references must also refer to legal XML characters; #x00110000 is one more than the largest legal character.(fatal) Invalid character reference
2.8 [22]not-wf-sa-147XML Declaration may not be preceded by whitespace.(fatal) The XML or Text declaration must start at line/column 1/1
2.8 [22]not-wf-sa-148XML Declaration may not be preceded by comments or whitespace.(fatal) The XML or Text declaration must start at line/column 1/1
2.8 [28]not-wf-sa-149XML Declaration may not be within a DTD.(fatal) Text declaration not legal here
3.1 [43]not-wf-sa-150XML declarations may not be within element content.(fatal) Unknown element 'doc'
2.8 [27]not-wf-sa-151XML declarations may not follow document content.(fatal) Unknown element 'doc'
2.8 [22]not-wf-sa-152XML declarations must include the "version=..." string.(fatal) The 'version=' string is required in an XMLDecl
4.3.2not-wf-sa-153Text declarations may not begin internal parsed entities; they may only appear at the beginning of external parsed (parameter or general) entities.(fatal) No processing instruction starts with 'xml'
2.8 2.6 [23, 17]not-wf-sa-154'<?XML ...?>' is neither an XML declaration nor a legal processing instruction target name.(fatal) No processing instruction starts with '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) No processing instruction starts with '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) Unknown element 'doc'
2.6 [17]not-wf-sa-157'<?xmL ...?>' is not a legal processing instruction target name.(fatal) Unknown element 'doc'
3.3 [52]not-wf-sa-158SGML-ism: "#NOTATION gif" can't have attributes.(fatal) Expected an element name
2.3 [9]not-wf-sa-159Uses '&' unquoted in an entity declaration, which is illegal syntax for an entity reference.(fatal) Expected entity name for reference
2.8not-wf-sa-160Violates the PEs in Internal Subset WFC by using a PE reference within a declaration.(fatal) PE refs are not allowed inside markup in the internal subset
2.8not-wf-sa-161Violates the PEs in Internal Subset WFC by using a PE reference within a declaration.(fatal) PE refs are not allowed inside markup in the internal subset
2.8not-wf-sa-162Violates the PEs in Internal Subset WFC by using a PE reference within a declaration.(fatal) PE refs are not allowed inside markup in the internal subset
4.1 [69]not-wf-sa-163Invalid placement of Parameter entity reference.(fatal) Invalid document structure
4.1 [69]not-wf-sa-164Invalid placement of Parameter entity reference.(fatal) Unterminated DOCTYPE declaration
4.2 [72]not-wf-sa-165Parameter entity declarations must have a space before the '%'.(fatal) Expected whitespace
2.2 [2]not-wf-sa-166Character FFFF is not legal anywhere in an XML document.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-167Character FFFE is not legal anywhere in an XML document.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-168An unpaired surrogate (D800) is not legal anywhere in an XML document.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-169An unpaired surrogate (DC00) is not legal anywhere in an XML document.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-170Four 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) An exception occured! Type:TranscodingException, Message:An invalid multi-byte source text sequence was encountered
2.2 [2]not-wf-sa-171Character FFFF is not legal anywhere in an XML document.(fatal) Invalid character (Unicode: 0xFFFF)
2.2 [2]not-wf-sa-172Character FFFF is not legal anywhere in an XML document.(fatal) Invalid character (Unicode: 0xFFFF)
2.2 [2]not-wf-sa-173Character FFFF is not legal anywhere in an XML document.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-174Character FFFF is not legal anywhere in an XML document.(fatal) Unknown element 'doc'
2.2 [2]not-wf-sa-175Character FFFF is not legal anywhere in an XML document.(fatal) Invalid character (Unicode: 0xFFFF)
3 [39]not-wf-sa-176Start tags must have matching end tags.(fatal) The input ended before all started tags were ended. Last tag started was 'doc'
2.2 [2]not-wf-sa-177Character FFFF is not legal anywhere in an XML document.(fatal) Invalid character (Unicode: 0xFFFF)
3.1 [41]not-wf-sa-178Invalid syntax matching double quote is missing.(fatal) A '<' character cannot be used in attribute 'a', except through &lt;
4.1 [66]not-wf-sa-179Invalid syntax matching double quote is missing.(fatal) Unterminated entity literal
4.1not-wf-sa-180The Entity Declared WFC requires entities to be declared before they are used in an attribute list declaration.(fatal) Entity 'e' was not found
4.3.2not-wf-sa-181Internal parsed entities must match the content production to be well formed.(fatal) Partial markup in entity value
4.3.2not-wf-sa-182Internal parsed entities must match the content production to be well formed.(fatal) Partial markup in entity value
3.2.2 [51]not-wf-sa-183Mixed content declarations may not include content particles.(fatal) Repetition of individual elements is not legal for mixed content models
3.2.2 [51]not-wf-sa-184In mixed content models, element names must not be parenthesized.(fatal) Expected an element name
4.1not-wf-sa-185Tests 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) Entity 'e' was not found
3.1 [44]not-wf-sa-186Whitespace is required between attribute/value pairs.(fatal) Expected whitespace
3.4 [62]not-wf-not-sa-001Conditional sections must be properly terminated ("]>" used instead of "]]>").(fatal) Expected ']]>' to end a conditional section
2.6 [17]not-wf-not-sa-002Processing instruction target names may not be "XML" in any combination of cases.(fatal) Text declaration not legal here
3.4 [62]not-wf-not-sa-003Conditional sections must be properly terminated ("]]>" omitted).(fatal) Partial markup in entity value
3.4 [62]not-wf-not-sa-004Conditional sections must be properly terminated ("]]>" omitted).(fatal) Partial markup in entity value
3.4 [62]not-wf-not-sa-006Conditional sections need a '[' after the INCLUDE or IGNORE.(fatal) Expected [ to follow INCLUDE or IGNORE
4.3.2 [79]not-wf-not-sa-007A <!DOCTYPE ...> declaration may not begin any external entity; it's only found once, in the document entity.(fatal) Expected a markup declaration
4.1 [69]not-wf-not-sa-008In DTDs, the '%' character must be part of a parameter entity reference.(fatal) Expected parameter entity name
4.1not-wf-ext-sa-001Tests the No Recursion WFC by having an external general entity be self-recursive.(fatal) Element 'doc' was used in the DOCTYPE but never declared
4.3.1 4.3.2 [77, 78]not-wf-ext-sa-002External entities have "text declarations", which do not permit the "standalone=..." attribute that's allowed in XML declarations.(fatal) The 'standalone=' string is only allowed in the main XML entity
2.6 [17]not-wf-ext-sa-003Only 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) No processing instruction starts with 'xml'
2.8valid-sa-094This refers to an undefined parameter entity reference within a markup declaration in the internal DTD subset, violating the PEs in Internal Subset WFC.[wrongly accepted]
3.3.1 [56]attlist01SGML's NUTOKEN is not allowed.(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'number' of element 'root'
3.3.1 [56]attlist02SGML's NUTOKENS attribute type is not allowed.(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'number' of element 'root'
3.3.1 [59]attlist03Comma doesn't separate enumerations, unlike in SGML.(fatal) Expected | enumeration separator, or closing paren
3.3.1 [56]attlist04SGML's NUMBER attribute type is not allowed.(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'number' of element 'root'
3.3.1 [56]attlist05SGML's NUMBERS attribute type is not allowed.(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'numbers' of element 'root'
3.3.1 [56]attlist06SGML's NAME attribute type is not allowed.(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'number' of element 'root'
3.3.1 [56]attlist07SGML's NAMES attribute type is not allowed.(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'number' of element 'root'
3.3.1 [56]attlist08SGML's #CURRENT is not allowed.(fatal) Expected default attribute declaration, assuming #IMPLIED
3.3.1 [56]attlist09SGML's #CONREF is not allowed.(fatal) Expected default attribute declaration, assuming #IMPLIED
3.1 [40]attlist10Whitespace required between attributes(fatal) Expected whitespace
3.1 [44]attlist11Whitespace required between attributes(fatal) Expected whitespace
3.4 [61]cond01Only INCLUDE and IGNORE are conditional section keywords(fatal) Expected INCLUDE or IGNORE here
3.4 [61]cond02Must have keyword in conditional sections(fatal) Expected INCLUDE or IGNORE here
3.2.1 [48]content01No whitespace before "?" in content model(fatal) Expected ',', '|', or ')' characters
3.2.1 [48]content02No whitespace before "*" in content model(fatal) Expected ',', '|', or ')' characters
3.2.1 [48]content03No whitespace before "+" in content model(fatal) Unexpected whitespace
4.3.1 [77]decl01External entities may not have standalone decls.(fatal) Unterminated XML decl
3.2.1 [55]nwf-dtd00Comma mandatory in content model(fatal) Expected '|' or ')' characters
3.2.1 [55]nwf-dtd01Can't mix comma and vertical bar in content models(fatal) Expected '|' or ')' characters
4.1 [69]dtd02PE name immediately after "%"(fatal) Expected parameter entity name
4.1 [69]dtd03PE name immediately followed by ";"(fatal) Unterminated entity reference
4.2.2 [75]dtd04PUBLIC literal must be quoted(fatal) Expected public id
4.2.2 [75]dtd05SYSTEM identifier must be quoted(fatal) Expected a literal entity value or PUBLIC/SYSTEM id
4.3.1 [77]dtd07Text declarations (which optionally begin any external entity) are required to have "encoding=...".(fatal) Bad XML encoding declaration, '{0}'
3.1 [42]element00EOF in middle of incomplete ETAG(fatal) Unknown element 'root'
3.1 [42]element01EOF in middle of incomplete ETAG(fatal) Unknown element 'root'
3.1 [43]element02Illegal markup (<%@ ... %>)(fatal) Expected an element name
3.1 [43]element03Illegal markup (<% ... %>)(fatal) Expected an element name
3.1 [43]element04Illegal markup (<!ELEMENT ... >)(fatal) Expected comment or CDATA
4.3.3 [81]encoding01Illegal character " " in encoding name(fatal) An exception occured! Type:TranscodingException, Message:Could not create a converter for encoding: utf-8
4.3.3 [81]encoding02Illegal character "/" in encoding name(fatal) An exception occured! Type:TranscodingException, Message:Could not create a converter for encoding: a/b
4.3.3 [81]encoding03Illegal character reference in encoding name(fatal) An exception occured! Type:TranscodingException, Message:Could not create a converter for encoding: just&#41;word
4.3.3 [81]encoding04Illegal character ":" in encoding name(fatal) An exception occured! Type:TranscodingException, Message:Could not create a converter for encoding: utf:8
4.3.3 [81]encoding05Illegal character "@" in encoding name(fatal) An exception occured! Type:TranscodingException, Message:Could not create a converter for encoding: @import(sys-encoding)
4.3.3 [81]encoding06Illegal character "+" in encoding name(fatal) An exception occured! Type:TranscodingException, Message:Could not create a converter for encoding: XYZ+999
4.3.1 [77]encoding07Text declarations (which optionally begin any external entity) are required to have "encoding=...".(fatal) No character data is allowed by content model
2.6 [16]piNo space between PI target name and data(fatal) Unterminated processing instruction
2.3 [12]pubid01Illegal entity ref in public ID(fatal) Invalid character in public id (Unicode: 0x26)
2.3 [12]pubid02Illegal characters in public ID(fatal) Invalid character in public id (Unicode: 0x3C)
2.3 [12]pubid03Illegal characters in public ID(fatal) Invalid character in public id (Unicode: 0x5B)
2.3 [12]pubid04Illegal characters in public ID(fatal) Invalid character in public id (Unicode: 0x7B)
2.3 [12]pubid05SGML-ism: public ID without system ID(fatal) Expected whitespace
3 [39]sgml01SGML-ism: omitted end tag for EMPTY content(fatal) No character data is allowed by content model
2.8 sgml02XML declaration must be at the very beginning of a document; it"s not a processing instruction(fatal) The XML or Text declaration must start at line/column 1/1
2.5 [15]sgml03Comments may not contain "--"(fatal) Illegal sequence '--' in comment
3.3 [52]sgml04ATTLIST declarations apply to only one element, unlike SGML(fatal) Expected an element name
3.2 [45]sgml05ELEMENT declarations apply to only one element, unlike SGML(fatal) Expected an element name
3.3 [52]sgml06ATTLIST declarations are never global, unlike in SGML(fatal) Expected an element name
3.2 [45]sgml07SGML Tag minimization specifications are not allowed(fatal) Expected content specification expression for element 'root'
3.2 [45]sgml08SGML Tag minimization specifications are not allowed(fatal) Expected content specification expression for element 'root'
3.2 [45]sgml09SGML Content model exception specifications are not allowed(fatal) Unterminated element declaration, 'footnote'
3.2 [45]sgml10SGML Content model exception specifications are not allowed(fatal) Unterminated element declaration, 'section'
3.2 [46]sgml11CDATA is not a valid content model spec(fatal) Expected content specification expression for element 'ROOT'
3.2 [46]sgml12RCDATA is not a valid content model spec(fatal) Expected content specification expression for element 'ROOT'
3.2.1 [47]sgml13SGML Unordered content models not allowed(fatal) Expected ',', '|', or ')' characters
2.1 [1]o-p01fail1S cannot occur before the prolog(fatal) The XML or Text declaration must start at line/column 1/1
2.1 [1]o-p01fail2comments cannot occur before the prolog(fatal) The XML or Text declaration must start at line/column 1/1
2.1 [1]o-p01fail3only one document element(fatal) Unknown element 'doc'
2.1 [1]o-p01fail4document element must be complete.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail1Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail10Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail11Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail12Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail13Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail14Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail15Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail16Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail17Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail18Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail19Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail2Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail20Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail21Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail22Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail23Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail24Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail25Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail26Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail27Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail28Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail29Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail3Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail30Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail31Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail4Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail5Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail6Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail7Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail8Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.2 [2]o-p02fail9Use of illegal character within XML document.(fatal) Unknown element 'doc'
2.3 [3]o-p03fail1Use of illegal character within XML document.[wrongly accepted]
2.3 [3]o-p03fail10Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail11Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail12Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail13Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail14Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail15Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail16Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail17Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail18Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail19Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail2Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail20Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail21Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail22Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail23Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail24Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail25Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail26Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail27Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail28Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail29Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail3Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail4Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail5Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail7Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail8Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [3]o-p03fail9Use of illegal character within XML document.(fatal) Invalid document structure
2.3 [4]o-p04fail1Name contains invalid character.(fatal) Unknown element 'A'
2.3 [4]o-p04fail2Name contains invalid character.(fatal) Unknown element 'A'
2.3 [4]o-p04fail3Name contains invalid character.(fatal) Unknown element 'A'
2.3 [5]o-p05fail1a Name cannot start with a digit(fatal) Expected an element name
2.3 [5]o-p05fail2a Name cannot start with a '.'(fatal) Expected an element name
2.3 [5]o-p05fail3a Name cannot start with a "-"(fatal) Expected an element name
2.3 [5]o-p05fail4a Name cannot start with a CombiningChar(fatal) Expected an element name
2.3 [5]o-p05fail5a Name cannot start with an Extender(fatal) Expected an element name
2.3 [9]o-p09fail1EntityValue excludes '%'(fatal) Expected parameter entity name
2.3 [9]o-p09fail2EntityValue excludes '&'(fatal) Expected entity name for reference
2.3 [9]o-p09fail3incomplete character reference(fatal) Unterminated character reference
2.3 [9]o-p09fail4quote types must match(fatal) Unterminated entity literal
2.3 [9]o-p09fail5quote types must match(fatal) Unterminated entity literal
2.3 [10]o-p10fail1attribute values exclude '<'(fatal) Unknown element 'doc'
2.3 [10]o-p10fail2attribute values exclude '&'(fatal) Unknown element 'doc'
2.3 [10]o-p10fail3quote types must match(fatal) Unknown element 'doc'
2.3 [11]o-p11fail1quote types must match(fatal) An exception occured! Type:UnexpectedEOFException, Message:The end of input was not expected
2.3 [11]o-p11fail2cannot contain delimiting quotes(fatal) Unterminated notation declaration
2.3 [12]o-p12fail1'"' excluded(fatal) Invalid character in public id (Unicode: 0x22)
2.3 [12]o-p12fail2'\' excluded(fatal) Invalid character in public id (Unicode: 0x5C)
2.3 [12]o-p12fail3entity references excluded(fatal) Invalid character in public id (Unicode: 0x26)
2.3 [12]o-p12fail4'>' excluded(fatal) Invalid character in public id (Unicode: 0x3e)
2.3 [12]o-p12fail5'<' excluded(fatal) Invalid character in public id (Unicode: 0x3C)
2.3 [12]o-p12fail6built-in entity refs excluded(fatal) Invalid character in public id (Unicode: 0x26)
2.3 [13]o-p12fail7publid IDs may not contain the "tab" character(fatal) Invalid character in public id (Unicode: 0x9)
2.4 [14]o-p14fail1'<' excluded(fatal) Unknown element 'doc'
2.4 [14]o-p14fail2'&' excluded(fatal) Unknown element 'doc'
2.4 [14]o-p14fail3"]]>" excluded(fatal) Unknown element 'doc'
2.5 [15]o-p15fail1comments can't end in '-'(fatal) Illegal sequence '--' in comment
2.5 [15]o-p15fail2one comment per comment (contrasted with SGML)(fatal) Illegal sequence '--' in comment
2.5 [15]o-p15fail3can't include 2 or more adjacent '-'s(fatal) Illegal sequence '--' in comment
2.6 [16]o-p16fail1"xml" is an invalid PITarget(fatal) No processing instruction starts with 'xml'
2.6 [16]o-p16fail2a PITarget must be present(fatal) Processing instruction name expected
2.7 [18]o-p18fail1no space before "CDATA"(fatal) Unknown element 'doc'
2.7 [18]o-p18fail2no space after "CDATA"(fatal) Unknown element 'doc'
2.7 [18]o-p18fail3CDSect's can't nest(fatal) Unknown element 'doc'
2.8 [22]o-p22fail1prolog must start with XML decl(fatal) The XML or Text declaration must start at line/column 1/1
2.8 [22]o-p22fail2prolog must start with XML decl(fatal) The XML or Text declaration must start at line/column 1/1
2.8 [23]o-p23fail1"xml" must be lower-case(fatal) No processing instruction starts with 'xml'
2.8 [23]o-p23fail2VersionInfo must be supplied(fatal) The 'version=' string is required in an XMLDecl
2.8 [23]o-p23fail3VersionInfo must come first(fatal) The XMLDecl strings must be in the order: version, encoding, standalone
2.8 [23]o-p23fail4SDDecl must come last(fatal) The XMLDecl strings must be in the order: version, encoding, standalone
2.8 [23]o-p23fail5no SGML-type PIs(fatal) Expected whitespace
2.8 [24]o-p24fail1quote types must match(fatal) Expected quoted string
2.8 [24]o-p24fail2quote types must match(fatal) Expected quoted string
2.8 [25]o-p25fail1Comment is illegal in VersionInfo.(fatal) Expected equal sign
2.8 [26]o-p26fail1Illegal character in VersionNum.(fatal) Unsupported XML version, '1.0?'
2.8 [26]o-p26fail2Illegal character in VersionNum.(fatal) Unsupported XML version, '1.0^'
2.8 [27]o-p27fail1References aren't allowed in Misc, even if they would resolve to valid Misc.(fatal) Invalid document structure
2.8 [28]o-p28fail1only declarations in DTD.(fatal) Expected a markup declaration
2.8 [29]o-p29fail1A processor must not pass unknown declaration types.(fatal) Expected a markup declaration
2.8 [30]o-p30fail1An XML declaration is not the same as a TextDecl(fatal) Unterminated XML decl
2.8 [31]o-p31fail1external subset excludes doctypedecl(fatal) Expected a markup declaration
2.9 [32]o-p32fail1quote types must match(fatal) Expected quoted string
2.9 [32]o-p32fail2quote types must match(fatal) Expected quoted string
2.9 [32]o-p32fail3initial S is required(fatal) Expected whitespace
2.9 [32]o-p32fail4quotes are required(fatal) Expected quoted string
2.9 [32]o-p32fail5yes or no must be lower case(fatal) Bad standalone declaration
3 [39]o-p39fail1start-tag requires end-tag(fatal) Unknown element 'doc'
3 [39]o-p39fail2end-tag requires start-tag(fatal) Unknown element 'doc'
3 [39]o-p39fail3XML documents contain one or more elements(fatal) The main XML document cannot be empty
2.8 [23]o-p39fail4XML declarations must be correctly terminated(fatal) Expected whitespace
2.8 [23]o-p39fail5XML declarations must be correctly terminated(fatal) Expected whitespace
3.1 [40]o-p40fail1S is required between attributes(fatal) Unknown element 'doc'
3.1 [40]o-p40fail2tags start with names, not nmtokens(fatal) Expected an element name
3.1 [40]o-p40fail3tags start with names, not nmtokens(fatal) Expected an element name
3.1 [40]o-p40fail4no space before name(fatal) Expected an element name
3.1 [41]o-p41fail1quotes are required (contrast with SGML)(fatal) Expected content specification expression for element 'doc'
3.1 [41]o-p41fail2attribute name is required (contrast with SGML)(fatal) Expected content specification expression for element 'doc'
3.1 [41]o-p41fail3Eq required(fatal) Unknown element 'doc'
3.1 [42]o-p42fail1no space before name(fatal) Unknown element 'doc'
3.1 [42]o-p42fail2cannot end with "/>"(fatal) Unknown element 'doc'
3.1 [42]o-p42fail3no NET (contrast with SGML)(fatal) Unknown element 'doc'
3.1 [43]o-p43fail1no non-comment declarations(fatal) Expected comment or CDATA
3.1 [43]o-p43fail2no conditional sections(fatal) Expected comment or CDATA
3.1 [43]o-p43fail3no conditional sections(fatal) Expected comment or CDATA
3.1 [44]o-p44fail1Illegal space before Empty element tag.(fatal) Expected an element name
3.1 [44]o-p44fail2Illegal space after Empty element tag.(fatal) Unknown element 'doc'
3.1 [44]o-p44fail3Illegal comment in Empty element tag.(fatal) Unknown element 'doc'
3.1 [44]o-p44fail4Whitespace required between attributes.(fatal) Unknown element 'doc'
3.1 [44]o-p44fail5Duplicate attribute name is illegal.(fatal) Unknown element 'doc'
3.2 [45]o-p45fail1ELEMENT must be upper case.(fatal) Expected a markup declaration
3.2 [45]o-p45fail2S before contentspec is required.(fatal) Expected whitespace
3.2 [45]o-p45fail3only one content spec(fatal) Expected an element name
3.2 [45]o-p45fail4no comments in declarations (contrast with SGML)(fatal) Unterminated element declaration, 'doc'
3.2 [46]o-p46fail1no parens on declared content(fatal) Expected an element name
3.2 [46]o-p46fail2no inclusions (contrast with SGML)(fatal) Unterminated element declaration, 'a'
3.2 [46]o-p46fail3no exclusions (contrast with SGML)(fatal) Unterminated element declaration, 'a'
3.2 [46]o-p46fail4no space before occurrence(fatal) Unterminated element declaration, 'a'
3.2 [46]o-p46fail5single group(fatal) Unterminated element declaration, 'a'
3.2 [46]o-p46fail6can't be both declared and modeled(fatal) Unterminated element declaration, 'a'
3.2.1 [47]o-p47fail1Invalid operator '|' must match previous operator ','(fatal) Expected '|' or ')' characters
3.2.1 [47]o-p47fail2Illegal character '-' in Element-content model(fatal) Unterminated element declaration, 'a'
3.2.1 [47]o-p47fail3Optional character must follow a name or list(fatal) Expected content specification expression for element 'a'
3.2.1 [47]o-p47fail4Illegal space before optional character(fatal) Unterminated element declaration, 'a'
3.2.1 [48]o-p48fail1Illegal space before optional character(fatal) Unexpected whitespace
3.2.1 [48]o-p48fail2Illegal space before optional character(fatal) Expected ',', '|', or ')' characters
3.2.1 [49]o-p49fail1connectors must match(fatal) Expected ',' or ')' characters or close parenthesis in content model of element 'a'
3.2.1 [50]o-p50fail1connectors must match(fatal) Expected '|' or ')' characters
3.2.2 [51]o-p51fail1occurrence on #PCDATA group must be *(fatal) Unterminated element declaration, 'doc'
3.2.2 [51]o-p51fail2occurrence on #PCDATA group must be *(fatal) Unterminated element declaration, 'doc'
3.2.2 [51]o-p51fail3#PCDATA must come first(fatal) Expected an element name
3.2.2 [51]o-p51fail4occurrence on #PCDATA group must be *(fatal) Expected asterisk
3.2.2 [51]o-p51fail5only '|' connectors(fatal) Unterminated Content model
3.2.2 [51]o-p51fail6Only '|' connectors and occurrence on #PCDATA group must be *(fatal) Unterminated Content model
3.2.2 [51]o-p51fail7no nested groups(fatal) Expected an element name
3.3 [52]o-p52fail1A name is required(fatal) Expected an element name
3.3 [52]o-p52fail2A name is required(fatal) Expected whitespace
3.3 [53]o-p53fail1S is required before default(fatal) Expected whitespace
3.3 [53]o-p53fail2S is required before type(fatal) Expected whitespace
3.3 [53]o-p53fail3type is required(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'att' of element 'doc'
3.3 [53]o-p53fail4default is required(fatal) Expected whitespace
3.3 [53]o-p53fail5name is requried(fatal) Expected an attribute name
3.3.1 [54]o-p54fail1don't pass unknown attribute types(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'att' of element 'doc'
3.3.1 [55]o-p55fail1must be upper case(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'att' of element 'doc'
3.3.1 [56]o-p56fail1no IDS type(fatal) Expected whitespace
3.3.1 [56]o-p56fail2no NUMBER type(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'att' of element 'doc'
3.3.1 [56]o-p56fail3no NAME type(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'att' of element 'doc'
3.3.1 [56]o-p56fail4no ENTITYS type - types must be upper case(fatal) Expected whitespace
3.3.1 [56]o-p56fail5types must be upper case(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'att' of element 'doc'
3.3.1 [57]o-p57fail1no keyword for NMTOKEN enumeration(fatal) Expected default attribute declaration, assuming #IMPLIED
3.3.1 [58]o-p58fail1at least one value required(fatal) Expected enumeration value for attribute 'att'
3.3.1 [58]o-p58fail2separator must be '|'(fatal) Expected | enumeration separator, or closing paren
3.3.1 [58]o-p58fail3notations 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) Expected enumeration value for attribute 'att'
3.3.1 [58]o-p58fail4NOTATION must be upper case(fatal) Expected type (CDATA, ID, NMTOKEN, ..), for attribute 'att' of element 'doc'
3.3.1 [58]o-p58fail5S after keyword is required(fatal) Expected whitespace
3.3.1 [58]o-p58fail6parentheses are require(fatal) Expected an open parenthesis
3.3.1 [58]o-p58fail7values are unquoted(fatal) Expected an open parenthesis
3.3.1 [58]o-p58fail8values are unquoted(fatal) Expected enumeration value for attribute 'att'
3.3.1 [59]o-p59fail1at least one required(fatal) Expected enumeration value for attribute 'att'
3.3.1 [59]o-p59fail2separator must be ","(fatal) Expected | enumeration separator, or closing paren
3.3.1 [59]o-p59fail3values are unquoted(fatal) Expected enumeration value for attribute 'att'
3.3.2 [60]o-p60fail1keywords must be upper case(fatal) Expected default attribute declaration, assuming #IMPLIED
3.3.2 [60]o-p60fail2S is required after #FIXED(fatal) Expected whitespace
3.3.2 [60]o-p60fail3only #FIXED has both keyword and value(fatal) Expected an attribute name
3.3.2 [60]o-p60fail4#FIXED required value(fatal) Expected whitespace
3.3.2 [60]o-p60fail5only one default type(fatal) Expected an attribute name
3.4 [61]o-p61fail1no other types, including TEMP, which is valid in SGML(fatal) Expected INCLUDE or IGNORE here
3.4 [62]o-p62fail1INCLUDE must be upper case(fatal) Expected INCLUDE or IGNORE here
3.4 [62]o-p62fail2no spaces in terminating delimiter(fatal) Expected ']]>' to end a conditional section
3.4 [63]o-p63fail1IGNORE must be upper case(fatal) Expected INCLUDE or IGNORE here
3.4 [63]o-p63fail2delimiters must be balanced(fatal) Partial markup in entity value
3.4 [64]o-p64fail1section delimiters must balance(fatal) Invalid document structure
3.4 [64]o-p64fail2section delimiters must balance(fatal) Partial markup in entity value
4.1 [66]o-p66fail1terminating ';' is required(fatal) Unknown element 'doc'
4.1 [66]o-p66fail2no S after '&#'(fatal) Unknown element 'doc'
4.1 [66]o-p66fail3no hex digits in numeric reference(fatal) Unknown element 'doc'
4.1 [66]o-p66fail4only hex digits in hex references(fatal) Unknown element 'doc'
4.1 [66]o-p66fail5no references to non-characters(fatal) Unknown element 'doc'
4.1 [66]o-p66fail6no references to non-characters(fatal) Unknown element 'doc'
4.1 [68]o-p68fail1terminating ';' is required(fatal) Unterminated entity reference
4.1 [68]o-p68fail2no S after '&'(fatal) Expected entity name for reference
4.1 [68]o-p68fail3no S before ';'(fatal) Unterminated entity reference
4.1 [69]o-p69fail1terminating ';' is required(fatal) Unterminated entity reference
4.1 [69]o-p69fail2no S after '%'(fatal) Expected parameter entity name
4.1 [69]o-p69fail3no S before ';'(fatal) Unterminated entity reference
4.2 [70]o-p70fail1This is neither(fatal) Expected parameter entity name
4.2 [71]o-p71fail1S is required before EntityDef(fatal) Expected whitespace
4.2 [71]o-p71fail2Entity name is a Name, not an NMToken(fatal) Expected parameter entity name
4.2 [71]o-p71fail3no S after "<!"(fatal) Expected a markup declaration
4.2 [71]o-p71fail4S is required after "<!ENTITY"(fatal) Expected whitespace
4.2 [72]o-p72fail1S is required after "<!ENTITY"(fatal) Expected whitespace
4.2 [72]o-p72fail2S is required after '%'(fatal) Expected whitespace
4.2 [72]o-p72fail3S is required after name(fatal) Expected whitespace
4.2 [72]o-p72fail4Entity name is a name, not an NMToken(fatal) Expected parameter entity name
4.2 [73]o-p73fail1No typed replacement text(fatal) Expected a literal entity value or PUBLIC/SYSTEM id
4.2 [73]o-p73fail2Only one replacement value(fatal) Unterminated entity declaration, 'ge'
4.2 [73]o-p73fail3No NDataDecl on replacement text(fatal) Unterminated entity declaration, 'ge'
4.2 [73]o-p73fail4Value is required(fatal) Expected a literal entity value or PUBLIC/SYSTEM id
4.2 [73]o-p73fail5No NDataDecl without value(fatal) Expected a literal entity value or PUBLIC/SYSTEM id
4.2 [74]o-p74fail1no NDataDecls on parameter entities(fatal) NDATA is not legal for parameter entities
4.2 [74]o-p74fail2value is required(fatal) Expected whitespace
4.2 [74]o-p74fail3only one value(fatal) Unterminated entity declaration, 'pe'
4.2.2 [75]o-p75fail1S required after "PUBLIC"(fatal) Expected whitespace
4.2.2 [75]o-p75fail2S required after "SYSTEM"(fatal) Expected whitespace
4.2.2 [75]o-p75fail3S required between literals(fatal) Expected whitespace
4.2.2 [75]o-p75fail4"SYSTEM" implies only one literal(fatal) Expected NDATA
4.2.2 [75]o-p75fail5only one keyword(fatal) Expected system id
4.2.2 [75]o-p75fail6"PUBLIC" requires two literals (contrast with SGML)(fatal) Expected whitespace
4.2.2 [76]o-p76fail1S is required before "NDATA"(fatal) Expected whitespace
4.2.2 [76]o-p76fail2"NDATA" is upper-case(fatal) Expected NDATA
4.2.2 [76]o-p76fail3notation name is required(fatal) Expected whitespace
4.2.2 [76]o-p76fail4notation names are Names(fatal) Expected a notation name

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
4.3.3 [4,84]pr-xml-euc-jpTest 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.)An exception occured! Type:TranscodingException, Message:An invalid multi-byte source text sequence was encountered
4.3.3 [4,84]pr-xml-iso-2022-jpTest 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.)Invalid character (Unicode: 0x1B)
4.3.3 [4,84]pr-xml-shift_jisTest 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.)
4.3.3 [4,84]weekly-euc-jpTest 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.An exception occured! Type:TranscodingException, Message:An invalid multi-byte source text sequence was encountered
4.3.3 [4,84]weekly-iso-2022-jpTest 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.No root element in DOCTYPE
4.3.3 [4,84]weekly-shift_jisTest 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.
2.8pe01Parameter entities must consist of a series of complete markup declarations of the types allowed by the nonterminal markupdecl, interespersed with whitespace or PERefs.
4.2.2 [75]uri01SYSTEM ids may not have URI fragments
2.3, 4.2.2 [11]o-p11pass1system literals may not contain URI fragments

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