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

来源：互联网发布：淘宝利润怎么算编辑：程序博客网时间：2024/06/07 17:20

This document is the output of an XML test harness. It reportson the conformance of the following XML 1.0 processor configuration,as reported through the Java version of the SAX (SimpleAPI forXML) parser interface. For SAX 2.0 (alpha)processors, the processing mode and entity handling values couldbe non-default values, if such a feature is supported by thatprocessor. For SAX 1.0 processors, those values were as reportedto the test harness by its operator.

XML ProcessorSun TR2SAX Parser Classcom.sun.xml.parser.ParserProcessing ModeNon-ValidatingGeneral EntitiesincludedParameter Entitiesincluded

The test harness and execution environment was:

Test Run DateTue Sep 07 07:57:59 PDT 1999Harness and Versionorg.brownell.xml.conformance.Driver
(alpha; 3-September-1999)Java VM Infobuild JDK-1.2.1-A, native threads, symcjitSuite of TestcasesOASIS 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 testto make sure it failed for the right reason. That examination may cause thecounts of failed tests to increase, changing a provisional "conforms"status to a "does not conform".

StatusCONFORMS (provisionally)Total Passed Tests (provisional)1065Passed Negative Tests (provisional)498Failed Tests (provisional)0Tests Skipped0

Sections of this report are:Explanation of Tables;Positive Tests, cases where this processor shouldreport no errors;Negative Tests, documents for which this processormust report the known errors; andInformative Tests, documents with errors whichprocessors 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 theOASIS/NIST site and to operate this test harness. Accordingly, treat theseresults as preliminary.

Explanation of Tables

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

(fatal): The diagnostic was reported as a fatal error. Such errors areprimarily well-formedness errors, such as the violation of XML 1.0syntax rules or of well formedness constraints.
(error): The diagnostic was reported as a recoverable error. Sucherrors primarily used to report validation errors, which are allviolations of validity constraints, but some other errors are alsoclassed as nonfatal.
(warning): The diagnostic was reported as a warning; warnings are purelyinformative and may be emitted in a number of cases identified bythe XML 1.0 specification (as well as in other cases).
(thrown classname) ... abnormal: The named exception was directly thrown. If the exceptionis a SAXException (or a subclass thereof) this suggests an error inthe parser (violating the SAX API specification) since it shouldnormally have used the SAX ErrorHandler instead.
(odd classname) ... abnormal: After the identified exception was reported through theErrorHandler, 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 isrequired to be continuable, or else it did not pass the exceptionthrown 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 withsevere bugs which completely prevented handling the test case,typically because the parser seems to "hang" by entering aninfinite loop.

In all cases, negative tests that appear to pass (diagnostics presentedwith a white background) must be individually examined in the report below.The diagnostic provided by the processor must correspond to the descriptionof 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 couldnot detect or report. That error is either a conformance bug, or an errorin the diagnostic being produced, or sometimes both.

Nonvalidating processors may skip some tests if the tests requireprocessing a class of external entities (general, parameter, or both)which that processor is known not to handle. If processor handling ofentities is not known, all such tests are skipped, in order to preventmisreporting.

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 theyopen. When running this test harness with large numbers of tests, failuresat the end of this report could reflect such bugs in SAX conformance morethan bugs in XML processor conformance.

Positive Tests

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

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

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

Valid Documents

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

Section and [Rules]Test IDDescriptionDiagnostic2.9not-sa02A non-standalone document is valid if declared as such.(warning) Using original entity definition for "&internal;".2.9not-sa04A non-standalone document is valid if declared as such.(warning) Using original entity definition for "&internal;".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.(warning) Using original entity definition for "&internal;".2.9 [32]sa04Like 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.2valid-sa-086Tests 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-littleTest support for little-endian UTF-16 textwhich 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-16Test 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-littleTest support for little-endian UTF-16 encoding, andXML names which contain Japanese characters.(warning) Using original entity definition for "<".4.3.3 [4,84]weekly-utf-16Test support for UTF-16 encoding, andXML names which contain Japanese characters.(warning) Using original entity definition for "<".

Output Tests

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

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

Test IDDiagnosticNothing to report!

Invalid Documents

As noted above, nonvalidating processors must accept all documentswhich are well formed, but invalid. This same behavior would be deliveredby a validating processor, if the application chose to continue processingafter receiving each report of a validity error, and not report suchvalidity errors. (These tests are run as "negative" tests for validatingprocessors, since in those cases it is important that the correct validityerrors be reported and that they be fully continuable.)

Section and [Rules]Test IDDescriptionDiagnostic2.9inv-not-sa02Tests the Standalone Document Declaration VC, ensuring that attributes needing normalization cause a validity error.(warning) Using original entity definition for "&internal;".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.(warning) Reference to undefined parameter entity "%undefined;".4.1not-wf-not-sa-005Tests the Entity Declared VC by referring to an undefined parameter entity within an external entity.(warning) Reference to undefined parameter entity "%e;".

Negative Tests

All conformant XML 1.0 processors must reject documents which are notwell-formed. In addition, validating processorsmust report the validity errors for invalid documents.These are calledNegative Tests because the test is intendedto establish that errors are reported when they should be.

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

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

For this processor, 498 diagnostics must beexamined to get an accurate evaluation of its negative test status.

Documents which are not Well-Formed

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

Section and [Rules]Test IDDescriptionDiagnostic2.1 [1]not-wf-sa-050Empty document, with no root element.(fatal) Document root element is missing.2.1 [1]o-p01fail1S cannot occur before the prolog(fatal) XML declaration may only begin entities.2.1 [1]o-p01fail2comments cannot occur before the prolog(fatal) XML declaration may only begin entities.2.1 [1]o-p01fail3only one document element(fatal) Illegal character at end of document, <.2.1 [1]o-p01fail4document element must be complete.(fatal) End of entity not allowed; an end tag is missing.2.2 [2]not-wf-sa-030A form feed is not a legal XML character.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-031A form feed is not a legal XML character.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-032A form feed is not a legal XML character.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-033An ESC (octal 033) is not a legal XML character.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-034A form feed is not a legal XML character.(fatal) Whitespace required before attributes.2.2 [2]not-wf-sa-142Character #x0000 is not legal anywhere in an XML document.(fatal) Illegal XML character 2.2 [2]not-wf-sa-143Character #x001F is not legal anywhere in an XML document.(fatal) Illegal XML character 2.2 [2]not-wf-sa-144Character #xFFFF is not legal anywhere in an XML document.(fatal) Illegal XML character 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) Illegal XML character &#xd800;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) Illegal XML character &#x110000;2.2 [2]not-wf-sa-166Character FFFF is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-167Character FFFE is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-168An unpaired surrogate (D800) is not legal anywhere in an XML document.(fatal) Illegal Unicode surrogate pair: &#xd800; <2.2 [2]not-wf-sa-169An unpaired surrogate (DC00) is not legal anywhere in an XML document.(fatal) Illegal Unicode surrogate pair: &#xdc00; <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) Character conversion error: "UTF-8 encoding of character0x001c0000 can't be converted to Unicode." (line number may be too low).2.2 [2]not-wf-sa-171Character FFFF is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-172Character FFFF is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-173Character FFFF is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-174Character FFFF is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-175Character FFFF is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]not-wf-sa-177Character FFFF is not legal anywhere in an XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail1Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail10Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail11Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail12Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail13Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail14Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail15Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail16Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail17Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail18Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail19Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail2Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail20Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail21Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail22Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail23Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail24Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail25Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail26Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail27Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail28Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail29Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail3Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail30Use of illegal character within XML document.(fatal) Character conversion error: "Reversed byte-order mark" (line number may be too low).2.2 [2]o-p02fail31Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail4Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail5Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail6Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail7Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail8Use of illegal character within XML document.(fatal) Illegal XML character: .2.2 [2]o-p02fail9Use of illegal character within XML document.(fatal) Illegal XML character: .2.3 [10]not-wf-sa-012SGML-ism: attribute values must be quoted in all cases.(fatal) Value must be quoted.2.3 [10]not-wf-sa-013The quotes on both ends of an attribute value must match.(fatal) Use "<" for "<" in attribute values.2.3 [10]not-wf-sa-014Attribute values may not contain literal '<' characters.(fatal) Use "<" for "<" in attribute values.2.3 [10]not-wf-sa-020Attribute 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-021Attribute 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-088Attribute values are terminated by literal quote characters, and any entity expansion is done afterwards.(fatal) Use "<" for "<" in attribute values.2.3 [10]not-wf-sa-090Attributes may not contain a literal "<" character; this one has one because of reference expansion.(fatal) Use "<" for "<" in attribute values.2.3 [10]o-p10fail1attribute values exclude '<'(fatal) Use "<" for "<" in attribute values.2.3 [10]o-p10fail2attribute values exclude '&'(fatal) Illegal character or entity reference syntax.2.3 [10]o-p10fail3quote types must match(fatal) Premature end of input.2.3 [11]o-p11fail1quote types must match(fatal) Premature end of input.2.3 [11]o-p11fail2cannot 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-p12fail3entity 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-p12fail6built-in entity refs excluded(fatal) Illegal character in PUBLIC identifier: "&".2.3 [12]o-p12fail7 (fatal) Illegal character in PUBLIC identifier: " ".2.3 [12]pubid01Illegal entity ref in public ID(fatal) Illegal character in PUBLIC identifier: "&".2.3 [12]pubid02Illegal characters in public ID(fatal) Illegal character in PUBLIC identifier: "<".2.3 [12]pubid03Illegal characters in public ID(fatal) Illegal character in PUBLIC identifier: "[".2.3 [12]pubid04Illegal characters in public ID(fatal) Illegal character in PUBLIC identifier: "{".2.3 [12]pubid05SGML-ism: public ID without system ID(fatal) Missing whitespace before SYSTEM literal URI.2.3 [13]not-wf-sa-085Public IDs may not contain "[".(fatal) Illegal character in PUBLIC identifier: "[".2.3 [13]not-wf-sa-086Public IDs may not contain "[".(fatal) Illegal character in PUBLIC identifier: "[".2.3 [13]not-wf-sa-087Public IDs may not contain "[".(fatal) Illegal character in PUBLIC identifier: "[".2.3 [3]o-p03fail1Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail10Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail11Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail12Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail13Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail14Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail15Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail16Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail17Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail18Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail19Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail2Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail20Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail21Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail22Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail23Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail24Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail25Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail26Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail27Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail28Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail29Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail3Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail4Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail5Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail7Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail8Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [3]o-p03fail9Use of illegal character within XML document.(fatal) Document root element is missing.2.3 [4]not-wf-sa-002Names 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-140Character '゚' 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-p04fail1Name contains invalid character.(fatal) Whitespace required before attributes.2.3 [4]o-p04fail2Name contains invalid character.(fatal) Whitespace required before attributes.2.3 [4]o-p04fail3Name contains invalid character.(fatal) Whitespace required before attributes.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) Illegal character or entity reference syntax.2.3 [5]not-wf-sa-023Digits are not valid name start characters.(fatal) Attribute names must not start with "1" characters.2.3 [5]not-wf-sa-024Digits are not valid name start characters.(fatal) The content beginning "<1" is not legal markup. Perhaps the "1" () character should be a letter.2.3 [5]not-wf-sa-141Character #x0E5C is not legal in XML names.(fatal) Whitespace required before attributes.2.3 [5]o-p05fail1a Name cannot start with a digit(fatal) Document root element is missing.2.3 [5]o-p05fail2a Name cannot start with a '.'(fatal) Document root element is missing.2.3 [5]o-p05fail3a Name cannot start with a "-"(fatal) Document root element is missing.2.3 [5]o-p05fail4a Name cannot start with a CombiningChar(fatal) Document root element is missing.2.3 [5]o-p05fail5a Name cannot start with an Extender(fatal) Document root element is missing.2.3 [9]not-wf-sa-113Parameter entity values must use valid reference syntax; this reference is malformed.(fatal) Illegal character or entity reference syntax.2.3 [9]not-wf-sa-114General entity values must use valid reference syntax; this reference is malformed.(fatal) Illegal character or entity reference syntax.2.3 [9]not-wf-sa-159Uses '&' unquoted in an entity declaration, which is illegal syntax for an entity reference.(fatal) Illegal character or entity reference syntax.2.3 [9]o-p09fail1EntityValue excludes '%'(fatal) Illegal parameter entity reference syntax.2.3 [9]o-p09fail2EntityValue excludes '&'(fatal) Illegal character or entity reference syntax.2.3 [9]o-p09fail3incomplete character reference(fatal) Illegal decimal character reference.2.3 [9]o-p09fail4quote types must match(fatal) Premature end of input.2.3 [9]o-p09fail5quote types must match(fatal) Premature end of input.2.4 [14]not-wf-sa-025Text may not contain a literal ']]>' sequence.(fatal) Character data cannot have "]]>".2.4 [14]not-wf-sa-026Text may not contain a literal ']]>' sequence.(fatal) Character data cannot have "]]>".2.4 [14]not-wf-sa-029Text 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 " " () 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-027Comments must be terminated with "-->".(fatal) End of entity while processing comment.2.5 [15]o-p15fail1comments can't end in '-'(fatal) Next character must be ">" terminating comment .2.5 [15]o-p15fail2one comment per comment (contrasted with SGML)(fatal) Next character must be ">" terminating comment .2.5 [15]o-p15fail3can't include 2 or more adjacent '-'s(fatal) Next character must be ">" terminating comment .2.5 [15]sgml03Comments may not contain "--"(fatal) Next character must be ">" terminating comment .2.5 [16]not-wf-sa-006XML comments may not contain "--"(fatal) Next character must be ">" terminating comment .2.5 [16]not-wf-sa-070XML comments may not contain "--"(fatal) Next character must be ">" terminating comment .2.6 [16]not-wf-sa-003Processing Instruction target name is required.(fatal) Processing instruction target is missing.2.6 [16]not-wf-sa-004SGML-ism: processing instructions end in '?>' not '>'.(fatal) End of input inside processing instruction.2.6 [16]not-wf-sa-005Processing instructions end in '?>' not '?'.(fatal) End of input inside processing instruction.2.6 [16]not-wf-sa-028Processing 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-p16fail2a PITarget must be present(fatal) Processing instruction target is missing.2.6 [16]piNo space between PI target name and data(fatal) Illegal processing instruction name, or missing whitespace.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) Expected "encoding=...".2.6 [17]not-wf-not-sa-002Processing 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.7not-wf-sa-105Invalid placement of CDATA section.(fatal) Document root element is missing.2.7 [18]not-wf-sa-017CDATA sections need a terminating ']]>'.(fatal) EOF while parsing <![CDATA[ section.2.7 [18]not-wf-sa-051CDATA is invalid at top level of document.(fatal) Document root element is missing.2.7 [18]not-wf-sa-128Invalid CDATA syntax.(fatal) Next character must be "(" starting content model for element "doc".2.7 [18]o-p18fail1no space before "CDATA"(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.2.7 [18]o-p18fail2no space after "CDATA"(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.2.7 [18]o-p18fail3CDSect's can't nest(fatal) Character data cannot have "]]>".2.7 [19]not-wf-sa-018CDATA sections begin with a literal '<![CDATA[', no space.(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.2.7 [19]not-wf-sa-108No space in '<![CDATA['.(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.2.7 [19]not-wf-sa-112CDATA sections start '<![CDATA[', not '<!cdata['.(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.2.8not-wf-sa-160Violates 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.8not-wf-sa-161Violates 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.8not-wf-sa-162Violates 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.8valid-sa-094This 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.8sgml02XML 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-147XML Declaration may not be preceded by whitespace.(fatal) XML declaration may only begin entities.2.8 [22]not-wf-sa-148XML Declaration may not be preceded by comments or whitespace.(fatal) XML declaration may only begin entities.2.8 [22]not-wf-sa-152XML declarations must include the "version=..." string.(fatal) Expected "version=...".2.8 [22]o-p22fail1prolog must start with XML decl(fatal) XML declaration may only begin entities.2.8 [22]o-p22fail2prolog must start with XML decl(fatal) XML declaration may only begin entities.2.8 [23]not-wf-sa-095VersionInfo must come before EncodingDecl.(fatal) Expected "version=...".2.8 [23]not-wf-sa-098Only one "version=..." string may appear in an XML declaration.(fatal) Illegal character "v" (v) at end of XML Declaration.2.8 [23]not-wf-sa-099Only three pseudo-attributes are in the XML declaration, and "valid=..." is not one of them.(fatal) Illegal character "v" (v) at end of XML Declaration.2.8 [23]o-p23fail1"xml" must be lower-case(fatal) Illegal processing instruction target: "XML".2.8 [23]o-p23fail2VersionInfo must be supplied(fatal) Expected "version=...".2.8 [23]o-p23fail3VersionInfo must come first(fatal) Expected "version=...".2.8 [23]o-p23fail4SDDecl must come last(fatal) Illegal character "e" (e) at end of XML Declaration.2.8 [23]o-p23fail5no SGML-type PIs(fatal) Illegal character ">" (>) at end of XML Declaration.2.8 [24]not-wf-sa-094Prolog VERSION must be lowercase.(fatal) Expected "version=...".2.8 [24]not-wf-sa-097Both quotes surrounding VersionNum must be the same.(fatal) Illegal XML version string "1.0' encoding=".2.8 [24]o-p24fail1quote types must match(fatal) Premature end of input.2.8 [24]o-p24fail2quote types must match(fatal) Premature end of input.2.8 [25]o-p25fail1Comment is illegal in VersionInfo.(fatal) Next character must be "=" in XML Declaration .2.8 [26]not-wf-sa-102Provides an illegal XML version number; spaces are illegal.(fatal) Illegal XML version string "1.0 ".2.8 [26]o-p26fail1Illegal character in VersionNum.(fatal) Illegal XML version string "1.0?".2.8 [26]o-p26fail2Illegal character in VersionNum.(fatal) Illegal XML version string "1.0^".2.8 [27]not-wf-sa-036Text may not appear after the root element.(fatal) Illegal character at end of document, I.2.8 [27]not-wf-sa-037Character references may not appear after the root element.(fatal) Illegal character at end of document, &.2.8 [27]not-wf-sa-040Provides two document elements.(fatal) Illegal character at end of document, <.2.8 [27]not-wf-sa-041Provides two document elements.(fatal) Illegal character at end of document, <.2.8 [27]not-wf-sa-043Provides #PCDATA text after the document element.(fatal) Illegal character at end of document, I.2.8 [27]not-wf-sa-044Provides two document elements.(fatal) Illegal character at end of document, <.2.8 [27]not-wf-sa-048Provides a CDATA section after the roor element.(fatal) Illegal character at end of document, <.2.8 [27]not-wf-sa-151XML declarations may not follow document content.(fatal) XML declaration may only begin entities.2.8 [27]o-p27fail1References 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-055Invalid Document Type Definition format.(fatal) Next character must be "]" terminating internal DTD subset .2.8 [28]not-wf-sa-056Invalid Document Type Definition format - misplaced comment.(fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration .2.8 [28]not-wf-sa-107Invalid document type declaration. CDATA alone is invalid.(fatal) Internal DTD subset must not have "<![..." constructs.2.8 [28]not-wf-sa-149XML Declaration may not be within a DTD.(fatal) XML declaration may only begin entities.2.8 [28]o-p28fail1only declarations in DTD.(fatal) Next character must be "]" terminating internal DTD subset .2.8 [29]not-wf-sa-063Conditional sections may only appear in the external DTD subset.(fatal) Internal DTD subset must not have "<![..." constructs.2.8 [29]o-p29fail1A processor must not pass unknown declaration types.(fatal) Next character must be "]" terminating internal DTD subset .2.8 [30]o-p30fail1An XML declaration is not the same as a TextDecl(fatal) Need "?>" to terminate XML declaration.2.8 [31]o-p31fail1external subset excludes doctypedecl(fatal) External parameter entity "%(DOCTYPE);" has characters after markup.2.9 [32]not-wf-sa-096Space is required before the standalone declaration.(fatal) Illegal character "e" (e) at end of XML Declaration.2.9 [32]not-wf-sa-100Only "yes" and "no" are permitted as values of "standalone".(fatal) Standalone declaration must be "yes" or "no", not "YES".2.9 [32]o-p32fail1quote types must match(fatal) Premature end of input.2.9 [32]o-p32fail2quote types must match(fatal) Premature end of input.2.9 [32]o-p32fail3initial S is required(fatal) Illegal character "s" (s) at end of XML Declaration.2.9 [32]o-p32fail4quotes are required(fatal) Expecting quoted value for attribute value standalone.2.9 [32]o-p32fail5yes or no must be lower case(fatal) Standalone declaration must be "yes" or "no", not "YES".3not-wf-sa-039Tests 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-176Start tags must have matching end tags.(fatal) End of entity not allowed; an end tag is missing.3 [39]o-p39fail1start-tag requires end-tag(fatal) End of entity not allowed; an end tag is missing.3 [39]o-p39fail2end-tag requires start-tag(fatal) Expected "</doc>" to terminate element starting on line 1.3 [39]o-p39fail3XML documents contain one or more elements(fatal) Document root element is missing.3 [39]o-p39fail4 (fatal) Illegal character ">" (>) at end of XML Declaration.3 [39]o-p39fail5 (fatal) Illegal character ">" (>) at end of XML Declaration.3 [39]sgml01SGML-ism: omitted end tag for EMPTY content(fatal) End of entity not allowed; an end tag is missing.3.1not-wf-sa-038Tests the "Unique Att Spec" WF constraint by providing multiple values for an attribute.(fatal) Attribute "x" already appeared in this tag.3.1not-wf-sa-081This 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.1not-wf-sa-082This 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]attlist10Whitespace required between attributes(fatal) Whitespace required before attributes.3.1 [40]not-wf-sa-046This start (or empty element) tag was not terminated correctly.(fatal) Next character must be ">" terminating element "a".3.1 [40]not-wf-sa-049Missing start tag(fatal) Expected "</doc>" to terminate element starting on line 1.3.1 [40]o-p40fail1S is required between attributes(fatal) Whitespace required before attributes.3.1 [40]o-p40fail2tags start with names, not nmtokens(fatal) Document root element is missing.3.1 [40]o-p40fail3tags start with names, not nmtokens(fatal) Document root element is missing.3.1 [40]o-p40fail4no space before name(fatal) Document root element is missing.3.1 [41]not-wf-sa-001Attribute values must start with attribute names, not "?".(fatal) Attribute names must not start with "?" characters.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) Next character must be "=" after attribute name "a1".3.1 [41]not-wf-sa-015Attribute values need a value, not just an equals sign.(fatal) Value must be quoted.3.1 [41]not-wf-sa-016Attribute values need an associated name.(fatal) Attribute names must not start with """ characters.3.1 [41]not-wf-sa-178Invalid syntax matching double quote is missing.(fatal) Use "<" for "<" in attribute values.3.1 [41]o-p41fail1quotes are required (contrast with SGML)(fatal) Next character must be "(" starting content model for element "doc".3.1 [41]o-p41fail2attribute name is required (contrast with SGML)(fatal) Next character must be "(" starting content model for element "doc".3.1 [41]o-p41fail3Eq required(fatal) Next character must be "=" after attribute name "att".3.1 [42]element00EOF in middle of incomplete ETAG(fatal) Expected "</root>" to terminate element starting on line 1.3.1 [42]element01EOF in middle of incomplete ETAG(fatal) Next character must be ">" terminating element "root".3.1 [42]not-wf-sa-019End tags may not be abbreviated as '</>'.(fatal) Expected "</doc>" to terminate element starting on line 1.3.1 [42]not-wf-sa-042Invalid End Tag(fatal) Illegal character at end of document, <.3.1 [42]not-wf-sa-053End tag does not match start tag.(fatal) Expected "</doc>" to terminate element starting on line 1.3.1 [42]o-p42fail1no space before name(fatal) Expected "</doc>" to terminate element starting on line 1.3.1 [42]o-p42fail2cannot end with "/>"(fatal) Next character must be ">" terminating element "doc".3.1 [42]o-p42fail3no NET (contrast with SGML)(fatal) Next character must be ">" terminating element "doc".3.1 [43]element02Illegal markup (<%@ ... %>)(fatal) The content beginning "<%" is not legal markup. Perhaps the "%" () character should be a letter.3.1 [43]element03Illegal markup (<% ... %>)(fatal) The content beginning "<%" is not legal markup. Perhaps the "%" () character should be a letter.3.1 [43]element04Illegal markup (<!ELEMENT ... >)(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.3.1 [43]not-wf-sa-035The '<' character is a markup delimiter and must start an element, CDATA section, PI, or comment.(fatal) The content beginning "< " is not legal markup. Perhaps the " " () character should be a letter.3.1 [43]not-wf-sa-111Entiry reference must be in content of element not Start-tag.(fatal) Attribute names must not start with "&" characters.3.1 [43]not-wf-sa-150XML declarations may not be within element content.(fatal) XML declaration may only begin entities.3.1 [43]o-p43fail1no non-comment declarations(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.3.1 [43]o-p43fail2no conditional sections(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.3.1 [43]o-p43fail3no conditional sections(fatal) The content beginning "<!" is not legal markup. Perhaps the "!" () character should be a letter.3.1 [44]attlist11Whitespace required between attributes(fatal) Whitespace required before attributes.3.1 [44]not-wf-sa-045Invalid Empty Element Tag(fatal) Next character must be ">" terminating element "a".3.1 [44]not-wf-sa-047Invalid empty element tag invalid whitespace(fatal) Next character must be ">" terminating element "a".3.1 [44]not-wf-sa-186Whitespace is required between attribute/value pairs.(fatal) Whitespace required before attributes.3.1 [44]o-p44fail1Illegal space before Empty element tag.(fatal) Document root element is missing.3.1 [44]o-p44fail2Illegal space after Empty element tag.(fatal) Next character must be ">" terminating element "doc".3.1 [44]o-p44fail3Illegal comment in Empty element tag.(fatal) Attribute names must not start with "-" characters.3.1 [44]o-p44fail4Whitespace required between attributes.(fatal) Whitespace required before attributes.3.1 [44]o-p44fail5Duplicate attribute name is illegal.(fatal) Attribute "att" already appeared in this tag.3.2 [45]not-wf-sa-057This isn't SGML; comments can't exist in declarations.(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "e".3.2 [45]not-wf-sa-129Invalid syntax for Element Type Declaration.(fatal) Next character must be "(" starting content model for element "doc".3.2 [45]not-wf-sa-130Invalid syntax for Element Type Declaration.(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "+".3.2 [45]not-wf-sa-131Invalid syntax for Element Type Declaration.(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "-".3.2 [45]not-wf-sa-136Tag omission is invalid in XML.(fatal) Next character must be "(" starting content model for element "doc".3.2 [45]not-wf-sa-137Space is required before a content model.(fatal) Missing whitespace after element name declaration.3.2 [45]o-p45fail1ELEMENT must be upper case.(fatal) Next character must be "]" terminating internal DTD subset .3.2 [45]o-p45fail2S before contentspec is required.(fatal) Missing whitespace after element name declaration.3.2 [45]o-p45fail3only one content spec(fatal) Only whitespace allowed before name in <!ELEMENT declaration.3.2 [45]o-p45fail4no comments in declarations (contrast with SGML)(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "-".3.2 [45]sgml05ELEMENT declarations apply to only one element, unlike SGML(fatal) Only whitespace allowed before name in <!ELEMENT declaration.3.2 [45]sgml07SGML Tag minimization specifications are not allowed(fatal) Next character must be "(" starting content model for element "root".3.2 [45]sgml08SGML Tag minimization specifications are not allowed(fatal) Next character must be "(" starting content model for element "root".3.2 [45]sgml09SGML Content model exception specifications are not allowed(fatal) ">" must terminate <!ELEMENT footnote ...> declaration, not "-".3.2 [45]sgml10SGML Content model exception specifications are not allowed(fatal) ">" must terminate <!ELEMENT section ...> declaration, not "+".3.2 [46]o-p46fail1no parens on declared content(fatal) No content model may contain "#".3.2 [46]o-p46fail2no inclusions (contrast with SGML)(fatal) ">" must terminate <!ELEMENT a ...> declaration, not "+".3.2 [46]o-p46fail3no exclusions (contrast with SGML)(fatal) ">" must terminate <!ELEMENT a ...> declaration, not "-".3.2 [46]o-p46fail4no space before occurrence(fatal) ">" must terminate <!ELEMENT a ...> declaration, not "+".3.2 [46]o-p46fail5single group(fatal) ">" must terminate <!ELEMENT a ...> declaration, not "(".3.2 [46]o-p46fail6can't be both declared and modeled(fatal) ">" must terminate <!ELEMENT a ...> declaration, not "(".3.2 [46]sgml11CDATA is not a valid content model spec(fatal) Next character must be "(" starting content model for element "ROOT".3.2 [46]sgml12RCDATA is not a valid content model spec(fatal) Next character must be "(" starting content model for element "ROOT".3.2.1not-wf-sa-133Illegal whitespace before optional character causes syntax error.(fatal) Choice content model must not contain "*".3.2.1not-wf-sa-134Illegal whitespace before optional character causes syntax error.(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "*".3.2.1 [46]not-wf-sa-139The element-content model should not be empty.(fatal) No content model may contain ")".3.2.1 [47]not-wf-sa-122Invalid syntax mixed connectors are used.(fatal) Need right parenthesis or "," in content model, not "|".3.2.1 [47]not-wf-sa-135Invalid character used as connector.(fatal) Choice content model must not contain "&".3.2.1 [47]o-p47fail1Invalid operator '|' must match previous operator ','(fatal) Need right parenthesis or "," in content model, not "|".3.2.1 [47]o-p47fail2Illegal character '-' in Element-content model(fatal) ">" must terminate <!ELEMENT a ...> declaration, not "-".3.2.1 [47]o-p47fail3Optional character must follow a name or list(fatal) Next character must be "(" starting content model for element "a".3.2.1 [47]o-p47fail4Illegal space before optional character(fatal) ">" must terminate <!ELEMENT a ...> declaration, not "?".3.2.1 [47]sgml13SGML Unordered content models not allowed(fatal) Choice content model must not contain "&".3.2.1 [48]content01No whitespace before "?" in content model(fatal) Choice content model must not contain "?".3.2.1 [48]content02No whitespace before "*" in content model(fatal) Choice content model must not contain "*".3.2.1 [48]content03No whitespace before "+" in content model(fatal) Choice content model must not contain "+".3.2.1 [48]not-wf-sa-123Invalid syntax mismatched parenthesis.(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not ")".3.2.1 [48]not-wf-sa-138Invalid syntax for content particle.(fatal) Choice content model must not contain "?".3.2.1 [48]o-p48fail1Illegal space before optional character(fatal) Choice content model must not contain "*".3.2.1 [48]o-p48fail2Illegal space before optional character(fatal) Choice content model must not contain "+".3.2.1 [49]o-p49fail1connectors must match(fatal) Need right parenthesis or "|" in content model, not ",".3.2.1 [50]not-wf-sa-132Invalid syntax mixed connectors used.(fatal) Need right parenthesis or "," in content model, not "|".3.2.1 [50]o-p50fail1connectors must match(fatal) Need right parenthesis or "," in content model, not "|".3.2.1 [55]nwf-dtd00Comma mandatory in content model(fatal) Need right parenthesis or "," in content model, not "f".3.2.1 [55]nwf-dtd01Can'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-124Invalid format of Mixed-content declaration.(fatal) Choice content model must not contain "#".3.2.2 [51]not-wf-sa-125Invalid syntax extra set of parenthesis not necessary.(fatal) No content model may contain "#".3.2.2 [51]not-wf-sa-126Invalid syntax Mixed-content must be defined as zero or more.(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "+".3.2.2 [51]not-wf-sa-127Invalid syntax Mixed-content must be defined as zero or more.(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "?".3.2.2 [51]not-wf-sa-183Mixed content declarations may not include content particles.(fatal) Mixed content model for "doc" must end with ")*", not "*".3.2.2 [51]not-wf-sa-184In mixed content models, element names must not be parenthesized.(fatal) Illegal mixed content model for "doc", next char = (.3.2.2 [51]o-p51fail1occurrence on #PCDATA group must be *(fatal) ">" must terminate <!ELEMENT doc ...> declaration, not "?".3.2.2 [51]o-p51fail2occurrence 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-p51fail4occurrence on #PCDATA group must be *(fatal) Mixed content model for "a" must end with ")*", not ")".3.2.2 [51]o-p51fail5only '|' connectors(fatal) Mixed content model for "a" must end with ")*", not ",".3.2.2 [51]o-p51fail6Only '|' connectors and occurrence on #PCDATA group must be *(fatal) Mixed content model for "a" must end with ")*", not ",".3.2.2 [51]o-p51fail7no nested groups(fatal) Illegal mixed content model for "a", next char = (.3.3 [52]not-wf-sa-066Required whitespace is missing.(fatal) Missing whitespace between attribute type and default value.3.3 [52]not-wf-sa-158SGML-ism: "#NOTATION gif" can't have attributes.(fatal) Only whitespace allowed before name in <!ATTLIST declaration.3.3 [52]o-p52fail1A name is required(fatal) Only whitespace allowed before name in <!ATTLIST declaration.3.3 [52]o-p52fail2A name is required(fatal) Missing whitespace before name in <!ATTLIST declaration.3.3 [52]sgml04ATTLIST declarations apply to only one element, unlike SGML(fatal) Only whitespace allowed before name in <!ATTLIST declaration.3.3 [52]sgml06ATTLIST declarations are never global, unlike in SGML(fatal) Only whitespace allowed before name in <!ATTLIST declaration.3.3 [53]not-wf-sa-064Space 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-065Space is required between attribute name and type in <!ATTLIST...> declarations.(fatal) Missing whitespace between attribute name and type.3.3 [53]not-wf-sa-067Space is required between attribute type and default values in <!ATTLIST...> declarations.(fatal) Missing whitespace between attribute type and default value.3.3 [53]o-p53fail1S is required before default(fatal) Missing whitespace between attribute type and default value.3.3 [53]o-p53fail2S is required before type(fatal) Missing whitespace between attribute name and type.3.3 [53]o-p53fail3type is required(fatal) Illegal type (starts with "#") for attribute "att".3.3 [53]o-p53fail4default is required(fatal) Missing whitespace between attribute type and default value.3.3 [53]o-p53fail5name is requried(fatal) Either an attribute declaration or ">" is expected, not "(".3.3.1 [54]not-wf-sa-058Invalid character , in ATTLIST enumeration(fatal) Name tokens must not start with "," characters.3.3.1 [54]o-p54fail1don't pass unknown attribute types(fatal) Illegal type (starts with "D") for attribute "att".3.3.1 [55]o-p55fail1must be upper case(fatal) Illegal type (starts with "c") for attribute "att".3.3.1 [56]attlist01SGML's NUTOKEN is not allowed.(fatal) Illegal type (starts with "N") for attribute "number".3.3.1 [56]attlist02SGML's NUTOKENS attribute type is not allowed.(fatal) Illegal type (starts with "N") for attribute "number".3.3.1 [56]attlist04SGML's NUMBER attribute type is not allowed.(fatal) Illegal type (starts with "N") for attribute "number".3.3.1 [56]attlist05SGML's NUMBERS attribute type is not allowed.(fatal) Illegal type (starts with "N") for attribute "numbers".3.3.1 [56]attlist06SGML's NAME attribute type is not allowed.(fatal) Illegal type (starts with "N") for attribute "number".3.3.1 [56]attlist07SGML's NAMES attribute type is not allowed.(fatal) Illegal type (starts with "N") for attribute "number".3.3.1 [56]attlist08SGML's #CURRENT is not allowed.(fatal) Value must be quoted.3.3.1 [56]attlist09SGML's #CONREF is not allowed.(fatal) Value must be quoted.3.3.1 [56]not-wf-sa-060Invalid type NAME defined in ATTLIST.(fatal) Illegal type (starts with "N") for attribute "a1".3.3.1 [56]o-p56fail1no IDS type(fatal) Missing whitespace between attribute type and default value.3.3.1 [56]o-p56fail2no NUMBER type(fatal) Illegal type (starts with "N") for attribute "att".3.3.1 [56]o-p56fail3no NAME type(fatal) Illegal type (starts with "N") for attribute "att".3.3.1 [56]o-p56fail4no ENTITYS type- types must be upper case(fatal) Missing whitespace between attribute type and default value.3.3.1 [56]o-p56fail5types must be upper case(fatal) Illegal type (starts with "i") for attribute "att".3.3.1 [57]o-p57fail1no keyword for NMTOKEN enumeration(fatal) Value must be quoted.3.3.1 [58]not-wf-sa-068Space 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-p58fail1at least one value required(fatal) Notation name is required.3.3.1 [58]o-p58fail2separator must be '|'(fatal) Notation name is required.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) Notation name is required.3.3.1 [58]o-p58fail4NOTATION must be upper case(fatal) Illegal type (starts with "n") for attribute "att".3.3.1 [58]o-p58fail5S after keyword is required(fatal) Missing whitespace after NOTATION type name.3.3.1 [58]o-p58fail6parentheses are require(fatal) Next character must be "(" starting list of attribute NOTATIONS .3.3.1 [58]o-p58fail7values are unquoted(fatal) Next character must be "(" starting list of attribute NOTATIONS .3.3.1 [58]o-p58fail8values are unquoted(fatal) Notation name is required.3.3.1 [59]attlist03Comma doesn't separate enumerations, unlike in SGML.(fatal) Name tokens must not start with "," characters.3.3.1 [59]not-wf-sa-059String literal must be in quotes.(fatal) Value must be quoted.3.3.1 [59]o-p59fail1at least one required(fatal) Name tokens must not start with ")" characters.3.3.1 [59]o-p59fail2separator must be ","(fatal) Name tokens must not start with "," characters.3.3.1 [59]o-p59fail3values are unquoted(fatal) Name tokens must not start with """ characters.3.3.2 [60]o-p60fail1keywords must be upper case(fatal) Value must be quoted.3.3.2 [60]o-p60fail2S is required after #FIXED(fatal) Missing whitespace after #FIXED.3.3.2 [60]o-p60fail3only #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-p60fail5only one default type(fatal) Either an attribute declaration or ">" is expected, not "#".3.4 [61]cond01Only INCLUDE and IGNORE are conditional section keywords(fatal) Only INCLUDE and IGNORE are allowed, not "CDATA".3.4 [61]cond02Must have keyword in conditional sections(fatal) Need keyword in conditional DTD section.3.4 [61]o-p61fail1no 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-001Conditional sections must be properly terminated ("]>" used instead of "]]>").(fatal) Unterminated conditional DTD section.3.4 [62]not-wf-not-sa-003Conditional sections must be properly terminated ("]]>" omitted).(fatal) Expansion of entity "&(DOCTYPE);" is not well formed.3.4 [62]not-wf-not-sa-004Conditional sections must be properly terminated ("]]>" omitted).(fatal) Unterminated conditional DTD section.3.4 [62]not-wf-not-sa-006Conditional sections need a '[' after the INCLUDE or IGNORE.(fatal) Next character must be "[" beginning condition DTD subset .3.4 [62]o-p62fail1INCLUDE must be upper case(fatal) Only INCLUDE and IGNORE are allowed, not "include".3.4 [62]o-p62fail2no spaces in terminating delimiter(fatal) Unterminated conditional DTD section.3.4 [63]o-p63fail1IGNORE must be upper case(fatal) Only INCLUDE and IGNORE are allowed, not "ignore".3.4 [63]o-p63fail2delimiters must be balanced(fatal) Expansion of entity "&(DOCTYPE);" is not well formed.3.4 [64]o-p64fail1section delimiters must balance(fatal) External parameter entity "%(DOCTYPE);" has characters after markup.3.4 [64]o-p64fail2section delimiters must balance(fatal) Expansion of entity "&(DOCTYPE);" is not well formed.4.1not-wf-ext-sa-001Tests the No Recursion WFC by having an external general entity be self-recursive.(fatal) Expansion of entity "e" is recursive.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) Illegal reference to external entity "&e;" in attribute.4.1not-wf-sa-180The Entity Declared WFC requires entities to be declared before they are used in an attribute list declaration.(fatal) Reference to undefined entity "&e;".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) Reference to undefined entity "&e;".4.1 [66]not-wf-sa-009Character references may have only decimal or numeric strings.(fatal) Illegal decimal character reference.4.1 [66]not-wf-sa-022Character references end with semicolons, always!(fatal) Illegal decimal character reference.4.1 [66]not-wf-sa-052Invalid character reference.(fatal) Document root element is missing.4.1 [66]not-wf-sa-093Hexadecimal character references may not use the uppercase 'X'.(fatal) Illegal decimal character reference.4.1 [66]not-wf-sa-179Invalid syntax matching double quote is missing.(fatal) Premature end of input.4.1 [66]o-p66fail1terminating ';' is required(fatal) Illegal decimal character reference.4.1 [66]o-p66fail2no S after '&#'(fatal) Illegal decimal character reference.4.1 [66]o-p66fail3no hex digits in numeric reference(fatal) Illegal decimal character reference.4.1 [66]o-p66fail4only hex digits in hex references(fatal) Illegal hexadecimal character reference.4.1 [66]o-p66fail5no references to non-characters(fatal) Illegal XML character 4.1 [66]o-p66fail6no references to non-characters(fatal) Illegal XML character &#xd802;4.1 [68]not-wf-sa-007General 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-010Ampersand may only appear as part of a general entity reference.(fatal) Illegal character or entity reference syntax.4.1 [68]not-wf-sa-071ENTITY can't reference itself directly or indirectly.(fatal) Expansion of entity "e1" is recursive.4.1 [68]not-wf-sa-072Undefined ENTITY foo.(fatal) Reference to undefined entity "&foo;".4.1 [68]not-wf-sa-073Undefined ENTITY f.(fatal) Reference to undefined entity "&f;".4.1 [68]not-wf-sa-075ENTITY can't reference itself directly or indirectly.(fatal) Expansion of entity "e1" is recursive.4.1 [68]not-wf-sa-076Undefined ENTITY foo.(fatal) Reference to undefined entity "&foo;".4.1 [68]not-wf-sa-078Undefined ENTITY foo.(fatal) Reference to undefined entity "&foo;".4.1 [68]not-wf-sa-079ENTITY can't reference itself directly or indirectly.(fatal) Expansion of entity "e1" is recursive.4.1 [68]not-wf-sa-080ENTITY can't reference itself directly or indirectly.(fatal) Expansion of entity "e1" is recursive.4.1 [68]not-wf-sa-110Entity reference must be in content of element.(fatal) Illegal character at end of document, &.4.1 [68]not-wf-sa-118Entity reference expansion is not recursive.(fatal) Illegal character or entity reference syntax.4.1 [68]not-wf-sa-121A name of an ENTITY was started with an invalid character.(fatal) Only whitespace allowed before name in <!ENTITY declaration.4.1 [68]o-p68fail1terminating ';' is required(fatal) Next character must be ";" terminating reference to entity "ent".4.1 [68]o-p68fail2no S after '&'(fatal) Illegal character or entity reference syntax.4.1 [68]o-p68fail3no S before ';'(fatal) Next character must be ";" terminating reference to entity "ent".4.1 [69]dtd02PE name immediately after "%"(fatal) Illegal parameter entity reference syntax.4.1 [69]dtd03PE name immediately followed by ";"(fatal) Next character must be ";" terminating reference to parameter entity "foo".4.1 [69]not-wf-not-sa-008In DTDs, the '%' character must be part of a parameter entity reference.(fatal) Illegal parameter entity reference syntax.4.1 [69]not-wf-sa-163Invalid placement of Parameter entity reference.(fatal) Document root element is missing.4.1 [69]not-wf-sa-164Invalid placement of Parameter entity reference.(fatal) Next character must be ">" terminating <!DOCTYPE ...> declaration .4.1 [69]o-p69fail1terminating ';' is required(fatal) Next character must be ";" terminating reference to parameter entity "pe".4.1 [69]o-p69fail2no S after '%'(fatal) Illegal parameter entity reference syntax.4.1 [69]o-p69fail3no S before ';'(fatal) Next character must be ";" terminating reference to parameter entity "pe".4.2not-wf-sa-106Invalid placement of entity declaration.(fatal) Document root element is missing.4.2 [70]not-wf-sa-109Tags invalid within EntityDecl.(fatal) Document root element is missing.4.2 [70]o-p70fail1This is neither(fatal) Only whitespace allowed before name in <!ENTITY declaration.4.2 [71]not-wf-sa-062Entity declarations need space after the entity name.(fatal) Missing whitespace after entity name.4.2 [71]o-p71fail1S is required before EntityDef(fatal) Missing whitespace after entity name.4.2 [71]o-p71fail2Entity name is a Name, not an NMToken(fatal) Only whitespace allowed before name in <!ENTITY declaration.4.2 [71]o-p71fail3no S after "<!"(fatal) Next character must be "]" terminating internal DTD subset .4.2 [71]o-p71fail4S is required after "<!ENTITY"(fatal) Missing whitespace after <!ENTITY declaration.4.2 [72]not-wf-sa-165Parameter entity declarations must have a space before the '%'.(fatal) Missing whitespace after <!ENTITY declaration.4.2 [72]o-p72fail1S is required after "<!ENTITY"(fatal) Missing whitespace after <!ENTITY declaration.4.2 [72]o-p72fail2S is required after '%'(fatal) Missing whitespace after % in parameter entity declaration.4.2 [72]o-p72fail3S is required after name(fatal) Missing whitespace after entity name.4.2 [72]o-p72fail4Entity name is a name, not an NMToken(fatal) Only whitespace allowed before name in <!ENTITY declaration.4.2 [73]o-p73fail1No typed replacement text(fatal) Value must be quoted.4.2 [73]o-p73fail2Only one replacement value(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "ge".4.2 [73]o-p73fail3No NDataDecl on replacement text(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "ge".4.2 [73]o-p73fail4Value is required(fatal) Value must be quoted.4.2 [73]o-p73fail5No NDataDecl without value(fatal) Value must be quoted.4.2 [74]not-wf-sa-089Parameter entities "are" always parsed; NDATA annotations are not permitted.(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "foo".4.2 [74]not-wf-sa-091Parameter entities "are" always parsed; NDATA annotations are not permitted.(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "foo".4.2 [74]o-p74fail1no NDataDecls on parameter entities(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "pe".4.2 [74]o-p74fail2value is required(fatal) Missing whitespace after entity name.4.2 [74]o-p74fail3only one value(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "pe".4.2.2 [75]dtd04PUBLIC literal must be quoted(fatal) Expecting quoted value for PUBLIC identifier.4.2.2 [75]dtd05SYSTEM identifier must be quoted(fatal) Expecting quoted value for SYSTEM identifier.4.2.2 [75]not-wf-sa-054PUBLIC requires two literals.(fatal) Missing whitespace before SYSTEM literal URI.4.2.2 [75]not-wf-sa-061External entity declarations require whitespace between public and system IDs.(fatal) Missing whitespace before SYSTEM literal URI.4.2.2 [75]o-p75fail1S required after "PUBLIC"(fatal) Missing whitespace after PUBLIC keyword.4.2.2 [75]o-p75fail2S required after "SYSTEM"(fatal) Missing whitespace before SYSTEM literal URI.4.2.2 [75]o-p75fail3S 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-p75fail5only 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-069Space is required before an NDATA entity annotation.(fatal) Next character must be ">" terminating <!ENTITY ...> declaration "foo".4.2.2 [76]not-wf-sa-083Undefined NOTATION n.(fatal) Unparsed entities such as "&e;" must not be included.4.2.2 [76]o-p76fail1S 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-p76fail3notation name is required(fatal) Missing whitespace before NDATA notation name in <!ENTITY declaration.4.2.2 [76]o-p76fail4notation 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-002External entities have "text declarations", which do not permit the "standalone=..." attribute that's allowed in XML declarations.(fatal) Expected "encoding=...".4.3.1 [77]decl01External entities may not have standalone decls.(fatal) Need "?>" to terminate XML declaration.4.3.1 [77]dtd07Text declarations (which optionally begin any external entity) are required to have "encoding=...".(fatal) Expected "encoding=...".4.3.1 [77]encoding07Text declarations (which optionally begin any external entity) are required to have "encoding=...".(fatal) Expected "encoding=...".4.3.2not-wf-sa-074Internal general parsed entities are only well formed if they match the "content" production.(fatal) Internal entity "&e;" has characters after content.4.3.2not-wf-sa-103End-tag required for element foo.(fatal) End of entity not allowed; an end tag is missing.4.3.2not-wf-sa-104Internal 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.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) Expansion of entity "&e;" is not well formed.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) Expansion of entity "&e;" is not well formed.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) Expansion of entity "&e;" is not well formed.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) XML declaration may only begin entities.4.3.2not-wf-sa-181Internal parsed entities must match the content production to be well formed.(fatal) EOF while parsing <![CDATA[ section.4.3.2not-wf-sa-182Internal 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-007A <!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]encoding01Illegal character " " in encoding name(fatal) Illegal character " " in encoding name.4.3.3 [81]encoding02Illegal character "/" in encoding name(fatal) Illegal character "/" in encoding name.4.3.3 [81]encoding03Illegal character reference in encoding name(fatal) Illegal character "&" in encoding name.4.3.3 [81]encoding04Illegal character ":" in encoding name(fatal) Illegal character ":" in encoding name.4.3.3 [81]encoding05Illegal character "@" in encoding name(fatal) Illegal character "@" in encoding name.4.3.3 [81]encoding06Illegal character "+" in encoding name(fatal) Illegal character "+" in encoding name.4.3.3 [81]not-wf-sa-101Space is not permitted in an encoding name.(fatal) Illegal character " " in encoding name.4.5not-wf-sa-092The replacement text of this entity has an illegal reference, because the character reference is expanded immediately.(fatal) Illegal character or entity reference syntax.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) Expansion of entity "&e;" is not well formed.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 & or as &#38;.(fatal) Expansion of entity "&e;" is not well formed.41. [68]not-wf-sa-077Undefined ENTITY bar.(fatal) Reference to undefined entity "&bar;".

Informative Tests

Certain XML documents are specified to be errors, but the handlingof those documents is not fully determined by the XML 1.0 specification.As a rule, these errors may be reported in any manner whatsoever, orcompletely ignored, without consequence in terms of conformance to theXML 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 notall processors are required to parse them.

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

Section and [Rules]Test IDDescriptionDiagnostic2.11 [33]lang01Illegal language identification(error) Illegal xml:lang value "234".2.11 [33]lang02Illegal language identification(error) Illegal xml:lang value "ab234".2.11 [33]lang03Illegal language identification(error) Illegal xml:lang value "ab-".2.11 [33]lang04Illegal language identification(error) Illegal xml:lang value "ab-234".2.11 [33]lang05Illegal language identification(error) Illegal xml:lang value "i-en/us".2.11 [33]lang06Illegal language identification(error) Illegal xml:lang value "X-FR.ch".2.3, 4.2.2 [11]o-p11pass1system literals may not contain URI fragments(error) URI "file:/d:/xml/xmlconf/oasis/a%a&b&#0<!ELEMENT<!--<?</>?>//''" has a fragment ID.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.[diagnostic not provided]4.2.2 [75]uri01SYSTEM 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-jpTest support for the EUC-JP encoding, and for textwhich relies on Japanese characters.If a processor does not support this encoding, it mustreport 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-jpTest support for the ISO-2022-JP encoding, and for textwhich relies on Japanese characters.If a processor does not support this encoding, it mustreport 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_jisTest support for the Shift_JIS encoding, and for textwhich relies on Japanese characters.If a processor does not support this encoding, it mustreport 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-jpTest support for EUC-JP encoding, andXML names which contain Japanese characters.If a processor does not support this encoding, it mustreport a fatal error.(warning) Using original entity definition for "<".4.3.3 [4,84]weekly-iso-2022-jpTest support for ISO-2022-JP encoding, andXML names which contain Japanese characters.If a processor does not support this encoding, it mustreport a fatal error.(warning) Using original entity definition for "<".4.3.3 [4,84]weekly-shift_jisTest support for Shift_JIS encoding, andXML names which contain Japanese characters.If a processor does not support this encoding, it mustreport a fatal error.(warning) Using original entity definition for "<".