Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.w3.org/XML/Test/xmlconf-20080827.html below:

XML Conformance Tests

XML

This version:

• http://www.w3.org/XML/Test/xmlconf-20080827.html

Current Version:

• http://www.w3.org/XML/Test/xmlconf-20080827.html

Previous Versions:

• http://www.w3.org/XML/Test/xmlconf-20080205.html

• http://www.w3.org/XML/Test/xmlconf-20031210.html

Test Archive:

• http://www.w3.org/XML/Test/xmlts20080827.tar.gz

• http://www.w3.org/XML/Test/xmlts20080827.zip

• http://www.w3.org/XML/Test/xmlts20080827.tar

W3C XML Core Working Group:

• http://www.w3.org/XML/Core/

Comments:

• Henry S. Thompson, W3C public-xml-testsuite@w3.org

1. Introduction
2. Test Matrix
   1. Binary Tests
   2. Output Tests
3. Test Case Descriptions
   1. Valid Documents
   2. Invalid Documents
   3. Not-WF Documents
   4. Optional Errors
4. Contributors

The tests described in this document provide an initial set of metrics to determine how well a particular implementation conforms to the following recommendations:

• W3C XML 1.0 Recommendation
• Extensible Markup Language (XML) 1.0 (Second Edition)
• Extensible Markup Language (XML) 1.0 (Third Edition)
• Extensibl e Markup Language (XML) 1.1
• Extensible Markup Language (XML) 1.0 (Fourth Edition)
• Extensibl e Markup Language (XML) 1.1 (Second Edition)
• Proposed Extensible Markup Language (XML) 1.0 (Fifth Edition)
• Names paces in XML 1.0
• Names paces in XML 1.0 (Second Edition)
• Nam espaces in XML 1.1
• Nam espaces in XML 1.1 (Second Edition)

The report properly identifies the tests associated with each recommendati on. All interpretations of these Recommendations are subject to confirmation by the W3C XML Core Working Group .

Conformance tests can be used by developers, content creators, and users alike to increase their level of confidence in product quality. In circumstances where interoperability is necessary, these tests can also be used to determine that differing implementations support the same set of features.

The XML Test Suite was transferred from OASIS to W3C and is being augmented to reflect the current work of the W3C XML Core Working Group, This report prov ides supporting documentation for all the tests included in the test suite. Sour ces from which these tests have been collected include: James Clark XMLTEST cases, 18-Nov-1998; Fuji Xerox Japanese Text Tests; Sun Microsystems XML Tests; OASIS/NIST TESTS, 1-Nov-1998; IBM XML Tests; Richard Tobin's XML 1.0 2nd edition errata test suite 21 Jul 2003; Richard Tobin's XML 1.1 test suite 13 Feb 2003; Richard Tobin's XML Namespaces 1.0 test suite 14 Feb 2003; Richard Tobin's XML N amespaces 1.1 test suite 14 Feb 2003; Richard Tobin's XML 1.0 3rd edition errata test suite 1 June 2006; Richard Tobin's XML Namespaces 1.0 errata test suite 1 June 2006; University of Edinburgh's XML 1.0 4th edition errata test suite 27 August 2008.

Two basic types of test are presented here. These are respectively Binary Tests and Output Tests .

Binary conformance tests are documents which are grouped into one of four categories. Given a document in a given category, each kind of XML parser must treat it consistently and either accept it (a positive test) or reject it (a negative test). It is in that sense that the tests are termed "binary". The XML 1.0 (Second Edition) Recommendation talks in terms of two types of XML processor: validating ones, and nonvalidating ones. There are two differences between these types of processors:

1. Validating processors check special productions that nonvalidating parsers don't, called validity constraints. (Both must check a basic set of productions, requiring XML documents to be well formed.)
2. Nonvalidating processors are permitted to not include external entities, such as files with text. Accordingly, they may not report errors which would have been detected had those entities been read.

There are two types of such entity, parameter entities holding definitions which affect validation and other processing; and general entities which hold marked up text. It will be appreciated that there are then five kinds of XML processor: validating processors, and four kinds of nonvalidating processor based on the combinations of external entity which they include.

At this time, the XML community primarily uses parsers which are in the rightmost two columns of this table, calling them Well Formed XML Parsers (or "WF Parsers") and Validating XML Parsers. A second test matrix could be defined to address the variations in the types of of XML processor which do not read all external entities. That additional matrix is not provided here at this time.

The XML 1.0 (Second Edition) Recommendation places a number of requirements on XML processors, to ensure that they report information to applications as needed. Such requirements are testable. Validating processors are required to report slightly more information than nonvalidating ones, so some tests will require separate output files. Some of the information that must be reported will not be reportable without reading all the external entities in a particular test. Many of the tests for valid documents are paired with an output file as the canonical representation of the input file, to ensure that the XML processor provides the correct information.

This section of this report contains descriptions of test cases, each of which fits into the categories noted above. Each test case includes a document of one of the types in the binary test matrix above (e.g. valid or invalid documents).

In some cases, an output file , as described in Section 2.2, will also be associated with a valid document, which is used for output testing. If such a file exists, it will be noted at the end of the description of the input document.

The description for each test case is presented as a two part table. The right part describes what the test does. This description is intended to have enough detail to evaluate diagnostic messages. The left part includes:

• An entry describing the Sections and/or Rules from the XML 1.0 (Second Edition) Recommendation which this case excercises.
• The unique Test ID within a given Collection for this test.
• The Collection from which this test originated. Given the Test ID and the Collection, each test can be uniquely identified.
• Some tests may have a field identifying the kinds of external Entities a nonvalidating processor must include (parameter, general, or both) to be able to detect any errors in that test case.

All conforming XML 1.0 Processors are required to accept valid documents, reporting no errors. In this section of this test report are found descriptions of test cases which fit into this category.

Namespace inequality test: different capitalization

Namespace inequality test: different escaping

Namespace name test: a perfectly good http URI

Namespace name test: a syntactically plausible URI with a fictitious scheme

Namespace name test: a perfectly good http URI with a fragment

Tests with a xml document consisting of prolog followed by element then Misc

There is an output test associated with this input file.

Namespace name test: a perfectly good http IRI that is not a URI

Test whether non-Latin-1 characters are accepted in IRIs, and whether they are correctly distinguished

Test demonstrates that although whitespace can be used to set apart markup for greater readability it is not necessary.

There is an output test associated with this input file.

Test demonstrates that extra whitespace is not intended for inclusion in the delivered version of the document.

There is an output test associated with this input file.

Test demonstrates that a line break within CDATA will be normalized.

There is an output test associated with this input file.

A combination of carriage return line feed in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

A carriage return (also CRLF) in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

A carriage return (also CRLF) in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

A carriage return (also CRLF) in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

The two character sequence #x0D #x85 in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

The single character sequence #x85 in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

The two character sequence #x0D #x85 in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

The single character sequence #x85 in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

The two character sequence #x0D #x85 in a document entity must be normalized to a single newline.

There is an output test associated with this input file.

The single character sequence #x85 in a document entity must be normalized to a single newline.

There is an output test associated with this input file.

The single character sequence #x2028 in a document entity must be normalized to a single newline.

There is an output test associated with this input file.

The single character sequence #x85 in the XMLDecl must be normalized to a single newline.

There is an output test associated with this input file.

The single character sequence #x2028 in the XMLDecl must be normalized to a single newline. (This test is questionable)

There is an output test associated with this input file.

Has a NEL character; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1

There is an output test associated with this input file.

Has a NEL character; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1

There is an output test associated with this input file.

Has an LSEP character; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1

There is an output test associated with this input file.

Has an LSEP character; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1

There is an output test associated with this input file.

Has CR-NEL; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1

There is an output test associated with this input file.

Has CR-NEL; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1

There is an output test associated with this input file.

Has CR-LSEP; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1. Note that CR and LSEP are not combined into a single LF

There is an output test associated with this input file.

Has CR-LSEP; legal in both XML 1.0 and 1.1, but different canonical output because of normalization in 1.1

There is an output test associated with this input file.

Has a NEL character in an NMTOKENS attribute; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

Has an LSEP character in an NMTOKENS attribute; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

Has a NEL character in element content whitespace; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

has an LSEP character in element content whitespace; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

Test demonstrates the use of optional character and content particles within mixed element content. The test also shows the use of an external entity and that a carriage control line feed in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

Test demonstrates the use of a public identifier with and external entity. The test also show that a carriage control line feed combination in an external entity must be normalized to a single newline.

There is an output test associated with this input file.

This tests normalization of end-of-line characters (CRLF) within entities to LF, primarily as an output test.

There is an output test associated with this input file.

Tests definition of an internal entity holding a carriage return character reference, which must not be normalized before reporting to the application. Line break normalization only occurs when parsing external parsed entities.

There is an output test associated with this input file.

Tests LanguageID with Langcode - Subcode

There is an output test associated with this input file.

Duplicate Test as ibm33v01.xml

There is an output test associated with this input file.

Tests ISO639Code

There is an output test associated with this input file.

Tests IanaCode

There is an output test associated with this input file.

Tests UserCode

There is an output test associated with this input file.

Tests SubCode

There is an output test associated with this input file.

Tests a lowercase ISO language code.

There is an output test associated with this input file.

Tests a ISO language code with a subcode.

There is an output test associated with this input file.

Tests an uppercase ISO language code.

There is an output test associated with this input file.

Tests a IANA language code with a subcode.

There is an output test associated with this input file.

Tests a user language code with a subcode.

There is an output test associated with this input file.

Tests a user language code.

There is an output test associated with this input file.

This test case covers legal character ranges plus discrete legal characters for production 02.

This test case covers legal character ranges plus discrete legal characters for production 02 of the XML1.1 sepcification.

Contains a C1 control, legal in XML 1.0, illegal in XML 1.1

There is an output test associated with this input file.

Contains a DEL, legal in XML 1.0, illegal in XML 1.1

There is an output test associated with this input file.

Contains a C1 control character (partial line up), legal in XML 1.0 but not 1.1

There is an output test associated with this input file.

various Misc items where they can occur

Test demonstrates that characters outside of normal ascii range can be used as element content.

There is an output test associated with this input file.

Test demonstrates that characters outside of normal ascii range can be used as element content.

There is an output test associated with this input file.

The document is encoded in UTF-16 and uses some name characters well outside of the normal ASCII range.

There is an output test associated with this input file.

The document is encoded in UTF-8 and the text inside the root element uses two non-ASCII characters, encoded in UTF-8 and each of which expands to a Unicode surrogate pair.

There is an output test associated with this input file.

This test case covers control characters x1 to x1F and x7F to x9F which should only appear as character references.

This test case covers control characters x1 to x1F and x7F to x9F which appear as character references as an entity's replacement text.

This test case contains embeded whitespace characters some form the range 1 - 1F.

This test case contains valid char references that match the char production.

This test case contains valid char references in the CDATA section, comment and processing instruction of an external entity that match the char production.

Tests all 4 legal white space characters - #x20 #x9 #xD #xA

Empty EntityValue is legal

There is an output test associated with this input file.

Tests a normal EnitityValue

There is an output test associated with this input file.

Tests EnitityValue referencing a Parameter Entity

There is an output test associated with this input file.

Tests EnitityValue referencing a General Entity

There is an output test associated with this input file.

Tests EnitityValue with combination of GE, PE and text, the GE used is declared in the student.dtd

There is an output test associated with this input file.

Tests empty AttValue with double quotes as the delimiters

There is an output test associated with this input file.

Tests empty AttValue with single quotes as the delimiters

There is an output test associated with this input file.

Test AttValue with double quotes as the delimiters and single quote inside

There is an output test associated with this input file.

Test AttValue with single quotes as the delimiters and double quote inside

There is an output test associated with this input file.

Test AttValue with a GE reference and double quotes as the delimiters

There is an output test associated with this input file.

Test AttValue with a GE reference and single quotes as the delimiters

There is an output test associated with this input file.

testing AttValue with mixed references and text content in double quotes

There is an output test associated with this input file.

testing AttValue with mixed references and text content in single quotes

There is an output test associated with this input file.

Tests empty systemliteral using the double quotes

There is an output test associated with this input file.

Tests empty systemliteral using the single quotes

There is an output test associated with this input file.

Tests regular systemliteral using the single quotes

There is an output test associated with this input file.

Tests regular systemliteral using the double quotes

There is an output test associated with this input file.

Tests empty systemliteral using the double quotes

There is an output test associated with this input file.

Tests empty systemliteral using the single quotes

There is an output test associated with this input file.

Tests regular systemliteral using the double quotes

There is an output test associated with this input file.

Tests regular systemliteral using the single quotes

There is an output test associated with this input file.

Testing PubidChar with all legal PubidChar in a PubidLiteral

There is an output test associated with this input file.

This test case covers legal NameStartChars character ranges plus discrete legal characters for production 04.

This test case covers legal NameChars character ranges plus discrete legal characters for production 04a.

This test case covers legal Element Names as per production 5.

This test case covers legal PITarget (Names) as per production 5.

This test case covers legal Attribute (Names) as per production 5.

This test case covers legal ID/IDREF (Names) as per production 5.

This test case covers legal ENTITY (Names) as per production 5.

This test case covers legal NMTOKEN Name character ranges plus discrete legal characters for production 7.

Has an NMTOKENS attribute containing a CR character that comes from a character reference in an internal entity. Because CR is in the S production, this is valid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Has an NMTOKENS attribute containing a CR character that comes from a character reference in an internal entity. Because CR is in the S production, this is valid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Has element content whitespace containing a CR character that comes from a character reference in an internal entity. Because CR is in the S production, this is valid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Has element content whitespace containing a CR character that comes from a character reference in an internal entity. Because CR is in the S production, this is valid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Namespace inequality test: different escaping of non-ascii letter

This test case covers legal NameStartChars character ranges plus discrete legal characters for production 04.

This test case covers legal NameChars character ranges plus discrete legal characters for production 04a.

This test case covers legal Element Names as per production 5.

This test case covers legal PITarget (Names) as per production 5.

This test case covers legal Attribute (Names) as per production 5.

This test case covers legal ID/IDREF (Names) as per production 5.

This test case covers legal ENTITY (Names) as per production 5.

This test case covers legal NMTOKEN Name character ranges plus discrete legal characters for production 7.

Test demostrates that extra whitespace is normalized into a single space character.

There is an output test associated with this input file.

Test demonstrates that an attribute can have a null value.

There is an output test associated with this input file.

Test demonstrates that the Attribute in a Start-tag can consist of numerals along with special characters.

There is an output test associated with this input file.

Test demonstrates that all lower case letters are valid for the Attribute in a Start-tag.

There is an output test associated with this input file.

Test demonstrates that all upper case letters are valid for the Attribute in a Start-tag.

There is an output test associated with this input file.

Test demonstrates that PubidChar can be used for element content.

There is an output test associated with this input file.

Test demonstrates the use of a parameter entity reference within an attribute list declaration.

There is an output test associated with this input file.

Makes sure that PUBLIC identifiers may have some strange characters. NOTE: The XML editors have said that the XML specification errata will specify that parameter entity expansion does not occur in PUBLIC identifiers, so that the '%' character will not flag a malformed parameter entity reference.

There is an output test associated with this input file.

valid public IDs.

Uses a legal XML 1.0 name consisting of a single colon character (disallowed by the latest XML Namespaces draft).

There is an output test associated with this input file.

The document is encoded in UTF-8 and the name of the root element type uses non-ASCII characters.

There is an output test associated with this input file.

various satisfactions of the Names production in a NAMES attribute

various valid Nmtoken 's in an attribute list declaration.

various satisfaction of an NMTOKENS attribute value.

valid EntityValue's. Except for entity references, markup is not recognized.

Testing CharData with empty string

There is an output test associated with this input file.

Testing CharData with white space character

There is an output test associated with this input file.

Testing CharData with a general text string

There is an output test associated with this input file.

Valid use of character data, comments, processing instructions and CDATA sections within the start and end tag.

Test demonstrates that character data is valid element content.

There is an output test associated with this input file.

Test demonstrates character references can be used for element content.

There is an output test associated with this input file.

Comments may contain any legal XML characters; only the string "--" is disallowed.

There is an output test associated with this input file.

Tests empty comment

There is an output test associated with this input file.

Tests comment with regular text

There is an output test associated with this input file.

Tests comment with one dash inside

There is an output test associated with this input file.

Tests comment with more comprehensive content

There is an output test associated with this input file.

Test demonstrates that comments are valid element content.

There is an output test associated with this input file.

Test demonstrates that comments are valid element content and that all characters before the double-hypen right angle combination are considered part of thecomment.

There is an output test associated with this input file.

Comments don't get parameter entity expansion

There is an output test associated with this input file.

Tests PI definition with only PItarget name and nothing else

There is an output test associated with this input file.

Tests PI definition with only PItarget name and a white space

There is an output test associated with this input file.

Tests PI definition with PItarget name and text that contains question mark and right angle

There is an output test associated with this input file.

Tests PITarget name

There is an output test associated with this input file.

Test demonstrates that extra whitespace within a processing instruction willnormalized into s single space character.

There is an output test associated with this input file.

Test demonstrates that extra whitespace within a processing instruction is converted into a single space character.

There is an output test associated with this input file.

Test demonstrates that Processing Instructions are valid element content.

There is an output test associated with this input file.

Test demonstrates that Processing Instructions are valid element content and there can be more than one.

There is an output test associated with this input file.

Test demonstrates a valid comment and that it may appear anywhere in the document including at the end.

There is an output test associated with this input file.

Test demonstrates a valid comment and that it may appear anywhere in the document including the beginning.

There is an output test associated with this input file.

Test demonstrates a valid processing instruction.

There is an output test associated with this input file.

Test demonstrates a valid processing instruction and that it may appear at the beginning of the document.

There is an output test associated with this input file.

Expands a general entity which contains a CDATA section with what looks like a markup declaration (but is just text since it's in a CDATA section).

There is an output test associated with this input file.

Tests CDSect with CDStart CData CDEnd

There is an output test associated with this input file.

Tests CDStart

There is an output test associated with this input file.

Tests CDATA with empty string

There is an output test associated with this input file.

Tests CDATA with regular content

There is an output test associated with this input file.

Tests CDEnd

There is an output test associated with this input file.

Test demonstrates that CDATA sections are valid element content.

There is an output test associated with this input file.

Test demonstrates that CDATA sections are valid element content and that ampersands may occur in their literal form.

There is an output test associated with this input file.

Test demonstractes that CDATA sections are valid element content and that everyting between the CDStart and CDEnd is recognized as character data not markup.

There is an output test associated with this input file.

Test demonstrates that all text within a valid CDATA section is considered text and not recognized as markup.

There is an output test associated with this input file.

Attribute defaults with a DTD have special parsing rules, different from other strings. That means that characters found there may look like an undefined parameter entity reference "within a markup declaration", but they aren't ... so they can't be violating the PEs in Internal Subset WFC.

There is an output test associated with this input file.

Parameter entities references are NOT RECOGNIZED in default attribute values.

Tests prolog with XMLDecl and doctypedecl

There is an output test associated with this input file.

Tests prolog with doctypedecl

There is an output test associated with this input file.

Tests prolog with Misc doctypedecl

There is an output test associated with this input file.

Tests prolog with doctypedecl Misc

There is an output test associated with this input file.

Tests prolog with XMLDecl Misc doctypedecl

There is an output test associated with this input file.

Tests prolog with XMLDecl doctypedecl Misc

There is an output test associated with this input file.

Tests prolog with XMLDecl Misc doctypedecl Misc

There is an output test associated with this input file.

Tests XMLDecl with VersionInfo only

There is an output test associated with this input file.

Tests XMLDecl with VersionInfo EncodingDecl

There is an output test associated with this input file.

Tests XMLDecl with VersionInfo SDDecl

There is an output test associated with this input file.

Tests XMLDecl with VerstionInfo and a trailing whitespace char

There is an output test associated with this input file.

Tests XMLDecl with VersionInfo EncodingDecl SDDecl

There is an output test associated with this input file.

Tests XMLDecl with VersionInfo EncodingDecl SDDecl and a trailing whitespace

There is an output test associated with this input file.

Tests VersionInfo with single quote

There is an output test associated with this input file.

Tests VersionInfo with double quote

There is an output test associated with this input file.

Tests EQ with =

There is an output test associated with this input file.

Tests EQ with = and spaces on both sides

There is an output test associated with this input file.

Tests EQ with = and space in front of it

There is an output test associated with this input file.

Tests EQ with = and space after it

There is an output test associated with this input file.

Tests VersionNum 1.0

There is an output test associated with this input file.

Tests Misc with comment

There is an output test associated with this input file.

Tests Misc with PI

There is an output test associated with this input file.

Tests Misc with white spaces

There is an output test associated with this input file.

Tests doctypedecl with internal DTD only

There is an output test associated with this input file.

Tests doctypedecl with external subset and combinations of different markup declarations and PEReferences

There is an output test associated with this input file.

Tests markupdecl with combinations of elementdecl, AttlistDecl,EntityDecl, NotationDecl, PI and comment

There is an output test associated with this input file.

Tests WFC: PE in internal subset as a positive test

There is an output test associated with this input file.

Tests extSubset with extSubsetDecl only in the dtd file

There is an output test associated with this input file.

Tests extSubset with TextDecl and extSubsetDecl in the dtd file

There is an output test associated with this input file.

Tests extSubsetDecl with combinations of markupdecls, conditionalSects, PEReferences and white spaces

There is an output test associated with this input file.

Valid doctypedecl with EXternalID as Enternal Entity. The external entity contains a parameter entity reference and condtional sections.

Valid doctypedecl with Parameter entity reference. The declaration of a parameter entity must precede any reference to it.

Valid doctypedecl with ExternalID as an External Entity. A parameter entity reference is also used.

Valid doctypedecl with ExternalID as an Enternal Entity. The external entity begins with a Text Declaration.

Valid doctypedecl with ExternalID as an External Entity declaration.

Valid doctypedecl with ExternalID as an External Entity. The external entity has an element declaration.

Second-level external general entity has later version number than first-level, but not later than document, so not an error.

There is an output test associated with this input file.

A vanilla XML 1.1 document

There is an output test associated with this input file.

a document with version=1.7, legal in XML 1.0 from 5th edition

XML decl and doctypedecl

just doctypedecl

S between decls is not required

Test demonstrates that both a EncodingDecl and SDDecl are valid within the prolog.

There is an output test associated with this input file.

Test demonstrates a valid prolog that uses double quotes as delimeters around the VersionNum.

There is an output test associated with this input file.

Test demonstrates a valid prolog that uses single quotes as delimters around the VersionNum.

There is an output test associated with this input file.

Test demonstrates a valid prolog that contains whitespace on both sides of the equal sign in the VersionInfo.

There is an output test associated with this input file.

Valid types of markupdecl.

external subset can be empty

Constructs an <!ATTLIST...> declaration from several PEs.

There is an output test associated with this input file.

A non-standalone document is valid if declared as such.

There is an output test associated with this input file.

A non-standalone document is valid if declared as such.

There is an output test associated with this input file.

A non-standalone document is valid if declared as such.

There is an output test associated with this input file.

A non-standalone document is valid if declared as such.

There is an output test associated with this input file.

Tests VC: Standalone Document Declaration with absent attribute that has default value and standalone is no

There is an output test associated with this input file.

Tests VC: Standalone Document Declaration with external entity reference and standalone is no

There is an output test associated with this input file.

Tests VC: Standalone Document Declaration with attribute values that need to be normalized and standalone is no

There is an output test associated with this input file.

Tests VC: Standalone Document Declaration with whitespace in mixed content and standalone is no

There is an output test associated with this input file.

Test demonstrates a valid SDDecl within the prolog.

There is an output test associated with this input file.

A document may be marked 'standalone' if any optional whitespace is defined within the internal DTD subset.

There is an output test associated with this input file.

A document may be marked 'standalone' if any attributes that need normalization are defined within the internal DTD subset.

There is an output test associated with this input file.

A document may be marked 'standalone' if any the defined entities need expanding are internal, and no attributes need defaulting or normalization. On output, requires notations to be correctly reported.

There is an output test associated with this input file.

Like sa03 but relies on attribute defaulting defined in the internal subset. On output, requires notations to be correctly reported.

There is an output test associated with this input file.

Like sa01 but this document is standalone since it has no optional whitespace. On output, requires notations to be correctly reported.

There is an output test associated with this input file.

Tests clauses 1, 3, and 4 of the Element Valid validity constraint.

There is an output test associated with this input file.

Tests element with EmptyElemTag and STag content Etag, also tests the VC: Element Valid with elements that have children, Mixed and ANY contents

There is an output test associated with this input file.

Tests declarations of "children" content models, and the validity constraints associated with them.

There is an output test associated with this input file.

Tests STag with possible combinations of its fields, also tests WFC: Unique Att Spec.

There is an output test associated with this input file.

Tests Attribute with Name Eq AttValue and VC: Attribute Value Type

There is an output test associated with this input file.

Tests ETag with possible combinations of its fields

There is an output test associated with this input file.

Tests content with all possible constructs: element, CharData, Reference, CDSect, Comment

There is an output test associated with this input file.

Tests EmptyElemTag with possible combinations of its fields

There is an output test associated with this input file.

Test demonstrates that Entity References are valid element content and also demonstrates a valid Entity Declaration.

There is an output test associated with this input file.

Test demonstrates that the content of an element can be empty. In this case the external entity is an empty file.

There is an output test associated with this input file.

Test demonstrates numeric character references can be used for element content.

There is an output test associated with this input file.

Test demonstrates that whitespace is permitted after the tag name in a Start-tag.

There is an output test associated with this input file.

Test demonstrates a valid attribute specification within a Start-tag that contains whitespace on both sides of the equal sign.

There is an output test associated with this input file.

Test demonstrates that whitespace is valid after the Attribute in a Start-tag.

There is an output test associated with this input file.

Test demonstrates mutliple Attibutes within the Start-tag.

There is an output test associated with this input file.

Test demonstrates that extra whitespace within an Attribute of a Start-tag is normalized to a single space character.

There is an output test associated with this input file.

Test demonstrates that extra whitespace within Start-tags and End-tags are nomalized into single spaces.

There is an output test associated with this input file.

Test demonstrates a valid attribute specification within a Start-tag.

There is an output test associated with this input file.

Test demonstrates that the AttValue within a Start-tag can use a single quote as a delimter.

There is an output test associated with this input file.

Test demonstrates that whitespace is permitted after the tag name in an End-tag.

There is an output test associated with this input file.

Test demonstrates that Entity References are valid element content.

There is an output test associated with this input file.

Test demonstrates that extra whitespace is normalized into single space character.

There is an output test associated with this input file.

Empty-element tag must be used for element which are declared EMPTY.

Test demonstrates the correct syntax for an Empty element tag.

There is an output test associated with this input file.

Test demonstrates that whitespace is permissible after the name in an Empty element tag.

There is an output test associated with this input file.

Test demonstrates that the empty-element tag must be use for an elements that are declared EMPTY.

There is an output test associated with this input file.

Tests both P45 elementDecl and P46 contentspec with possible combinations of their constructs

There is an output test associated with this input file.

Valid use of contentspec, element content models, and mixed content within an element type declaration.

Valid use of contentspec, element content models, choices, sequences and content particles within an element type declaration. The optional character following a name or list governs the number of times the element or content particle may appear.

Valid use of contentspec, element content models, choices, and content particles within an element type declaration. The optional character following a name or list governs the number of times the element or content particle may appear. Whitespace is also valid between choices.

Valid use of contentspec, element content models, sequences and content particles within an element type declaration. The optional character following a name or list governs the number of times the element or content particle may appear. Whitespace is also valid between sequences.

Valid use of contentspec, element content models, choices, sequences and content particles within an element type declaration. The optional character following a name or list governs the number of times the element or content particle may appear.

Test demonstrates an Element Type Declaration that uses the contentspec of EMPTY. The element cannot have any contents and must always appear as an empty element in the document. The test also shows an Attribute-list declaration with multiple AttDef's.

There is an output test associated with this input file.

valid element declarations

Test demonstrates an Element Type Declaration and that the contentspec can be of mixed content.

There is an output test associated with this input file.

Test demonstrates an Element Type Declaration and that EMPTY is a valid contentspec.

There is an output test associated with this input file.

Test demonstrates an Element Type Declaration and that ANY is a valid contenspec.

There is an output test associated with this input file.

Tests all possible children,cp,choice,seq patterns in P47,P48,P49,P50

There is an output test associated with this input file.

Tests VC:Proper Group/PE Nesting with PEs of choices that are properly nested with parenthesized groups in external subsets

There is an output test associated with this input file.

Tests VC:Proper Group/PE Nesting with PEs of seq that are properly nested with parenthesized groups in external subsets

There is an output test associated with this input file.

Test demonstrates the use of optional character and content particles within an element content. The test also show the use of external entity.

There is an output test associated with this input file.

Test demonstrates an element content model whose element can occur zero or more times.

There is an output test associated with this input file.

Test demonstrates shows the use of content particles within the element content.

There is an output test associated with this input file.

Test demonstrates the use of the optional character following a name or list to govern the number of times an element or content particles in the list occur.

There is an output test associated with this input file.

Tests Mixed with possible combinations of its fields amd VC: No Duplicate Types

There is an output test associated with this input file.

Tests VC:Proper Group/PE Nesting with PEs of Mixed that are properly nested with parenthesized groups in external subsets

There is an output test associated with this input file.

Test demonstrates an Element Type Declaration with Mixed Content.

There is an output test associated with this input file.

Tests parsing of alternative forms of text-only mixed content declaration.

There is an output test associated with this input file.

valid Mixed contentspec's.

An element's attributes may be declared before its content model; and attribute values may contain newlines.

There is an output test associated with this input file.

Basically an output test, this tests whether an externally defined attribute declaration (with a default) takes proper precedence over a subsequent internal declaration.

There is an output test associated with this input file.

Tests all AttlistDecl and AttDef Patterns in P52 and P53

There is an output test associated with this input file.

Test demonstrates an Attribute List declaration that uses a StringType as the AttType.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use an EnumeratedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use an StringType of CDATA within the Attribute type. The test also shows that REQUIRED is a valid DefaultDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use ID as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use IDREF as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use IDREFS as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use ENTITY as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use ENTITIES as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use an StringType of CDATA within the Attribute type. The test also shows that FIXED is a valid DefaultDecl and that a value can be given to the attribute in the Start-tag as well as the AttListDecl.

There is an output test associated with this input file.

Test demonstrates that an AttlistDecl can use an StringType of CDATA within the Attribute type. The test also shows that FIXED is a valid DefaultDecl and that an value can be given to the attribute.

There is an output test associated with this input file.

Tests whether more than one definition can be provided for the same attribute of a given element type with the first declaration being binding.

There is an output test associated with this input file.

Test demonstrates that when more than one AttlistDecl is provided for a given element type, the contents of all those provided are merged.

There is an output test associated with this input file.

Test demonstrates that when more than one definition is provided for the same attribute of a given element type only the first declaration is binding.

There is an output test associated with this input file.

Test demonstrates the use of an Attribute list declaration within an external entity.

There is an output test associated with this input file.

Test demonstrates that when more that one definition is provided for the same attribute of a given element type only the first declaration is binding.

There is an output test associated with this input file.

Test demonstrates that when more that one definition is provided for the same attribute of a given element type only the first declaration is binding.

There is an output test associated with this input file.

valid AttlistDecls: No AttDef's are required, and the terminating S is optional, multiple ATTLISTS per element are OK, and multiple declarations of the same attribute are OK.

Test demonstrates that it is not an error to have attributes declared for an element not itself declared.

There is an output test associated with this input file.

a valid AttDef

Verifies that an XML parser will parse a NOTATION attribute; the output phase of this test ensures that both notations are reported to the application.

There is an output test associated with this input file.

Verifies that an XML parser will parse a NOTATION attribute; the output phase of this test ensures that the notation is reported to the application.

There is an output test associated with this input file.

Verifies that an XML parser will parse an ENTITY attribute; the output phase of this test ensures that the notation is reported to the application, and for validating parsers it further tests that the entity is so reported.

There is an output test associated with this input file.

Tests all AttTypes : StringType, TokenizedTypes, EnumeratedTypes in P55,P56,P57,P58,P59. Also tests all DefaultDecls in P60.

Tests all AttTypes : StringType, TokenizedType, EnumeratedTypes in P55,P56,P57.

There is an output test associated with this input file.

Tests AttTypes with StringType in P55.

There is an output test associated with this input file.

Tests StringType for P55. The "CDATA" occurs in the StringType for the attribute "att" for the element "a".

There is an output test associated with this input file.

Tests TokenizedType for P56. The "ID", "IDREF", "IDREFS", "ENTITY", "ENTITIES", "NMTOKEN", and "NMTOKENS" occur in the TokenizedType for the attribute "attr".

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: ID Attribute Default. The value "AC1999" is assigned to the ID attribute "attr" with "#REQUIRED" in the DeaultDecl.

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: ID Attribute Default. The value "AC1999" is assigned to the ID attribute "attr" with "#IMPLIED" in the DeaultDecl.

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: ID. The ID attribute "UniqueName" appears only once in the document.

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: One ID per element type. The element "a" or "b" has only one ID attribute.

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: IDREF. The IDREF value "AC456" matches the value assigned to an ID attribute "UniqueName".

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: IDREF. The IDREFS value "AC456 Q123" matches the values assigned to the ID attribute "UniqueName" and "Uname".

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: Entity Name. The value "image" of the ENTITY attribute "sun" matches the name of an unparsed entity declared.

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: Name Token. The value of the NMTOKEN attribute "thistoken" matches the Nmtoken production.

There is an output test associated with this input file.

Tests TokenizedType for P56 VC: Name Token. The value of the NMTOKENS attribute "thistoken" matches the Nmtoken production.

There is an output test associated with this input file.

Tests EnumeratedType in the AttType. The attribute "att" has a type (a|b) with the element "a". the

There is an output test associated with this input file.

Tests NotationType for P58. It shows different patterns fro the NOTATION attribute "attr".

There is an output test associated with this input file.

Tests NotationType for P58: Notation Attributes. The value "base64" of the NOTATION attribute "attr" matches one of the notation names declared.

There is an output test associated with this input file.

Tests Enumeration in the EnumeratedType for P59. It shows different patterns for the Enumeration attribute "attr".

There is an output test associated with this input file.

Tests Enumeration for P59 VC: Enumeration. The value "one" of the Enumeration attribute "attr" matches one of the element names declared.

There is an output test associated with this input file.

Test demonstrates an Attribute List declaration that uses a StringType as the AttType and also expands the CDATA attribute with a character reference.

There is an output test associated with this input file.

Test demonstrates an Attribute List declaration that uses a StringType as the AttType and also expands the CDATA attribute with a character reference. The test also shows that the leading zeros in the character reference are ignored.

There is an output test associated with this input file.

Test demonstrates an Attribute List declaration that uses a StringType as the AttType and also expands the CDATA attribute with a character reference. The test also shows that the leading zeros in the character reference are ignored.

There is an output test associated with this input file.

the three kinds of attribute types

StringType = "CDATA"

the 7 tokenized attribute types

enumerated types are NMTOKEN or NOTATION lists

NOTATION enumeration has on or more items

XML permits token reuse, while SGML does not.

There is an output test associated with this input file.

NMTOKEN enumerations haveon or more items

Tests DefaultDecl for P60. It shows different options "#REQUIRED", "#FIXED", "#IMPLIED", and default for the attribute "chapter".

There is an output test associated with this input file.

Tests DefaultDecl for P60 VC: Required Attribute. In the element "one" and "two" the value of the #REQUIRED attribute "chapter" is given.

There is an output test associated with this input file.

Tests DefaultDecl for P60 VC: Fixed Attribute Default. The value of the #FIXED attribute "chapter" is exactly the same as the default value.

There is an output test associated with this input file.

Tests DefaultDecl for P60 VC: Attribute Default Legal. The default value specified for the attribute "attr" meets the lexical constraints of the declared attribute type.

There is an output test associated with this input file.

Tests the #REQUIRED attribute declaration syntax, and the associated validity constraint.

There is an output test associated with this input file.

the four types of default values

Test demonstrates that extra whitespace be normalized into a single space character in an attribute of type NMTOKENS.

There is an output test associated with this input file.

Basically an output test, this requires extra whitespace to be normalized into a single space character in an attribute of type NMTOKENS.

There is an output test associated with this input file.

Test demonstrates that extra whitespace is normalized into a single space character in an attribute of type NMTOKENS.

There is an output test associated with this input file.

Test demonstrates that a CDATA attribute can pass a double quote as its value.

There is an output test associated with this input file.

Test demonstrates that an attribute can pass a less than sign as its value.

There is an output test associated with this input file.

Basically an output test, this requires a CDATA attribute with a tab character to be passed through as one space.

There is an output test associated with this input file.

Basically an output test, this requires a CDATA attribute with a newline character to be passed through as one space.

There is an output test associated with this input file.

Basically an output test, this requires a CDATA attribute with a return character to be passed through as one space.

There is an output test associated with this input file.

Basically an output test, this requires that a CDATA attribute with a CRLF be normalized to one space.

There is an output test associated with this input file.

Character references expanding to spaces doesn't affect treatment of attributes.

There is an output test associated with this input file.

Test demonstrates that an entity reference is processed by recursively processing the replacement text of the entity.

There is an output test associated with this input file.

Test demonstrates that whitespace is handled by adding a single whitespace to the normalized value in the attribute list.

There is an output test associated with this input file.

Tests conditionalSect for P61. It takes the option "invludeSect" in the file ibm61v01.dtd.

There is an output test associated with this input file.

Tests conditionalSect for P61. It takes the option "ignoreSect" in the file ibm61v02.dtd.

There is an output test associated with this input file.

Tests includeSect for P62. The white space is not included before the key word "INCLUDE" in the beginning sequence.

There is an output test associated with this input file.

Tests includeSect for P62. The white space is not included after the key word "INCLUDE" in the beginning sequence.

There is an output test associated with this input file.

Tests includeSect for P62. The white space is included after the key word "INCLUDE" in the beginning sequence.

There is an output test associated with this input file.

Tests includeSect for P62. The white space is included before the key word "INCLUDE" in the beginning sequence.

There is an output test associated with this input file.

Tests includeSect for P62. The extSubsetDecl is not included.

There is an output test associated with this input file.

Tests ignoreSect for P63. The white space is not included before the key word "IGNORE" in the beginning sequence.

There is an output test associated with this input file.

Tests ignoreSect for P63. The white space is not included after the key word "IGNORE" in the beginning sequence.

There is an output test associated with this input file.

Tests ignoreSect for P63. The white space is included after the key word "IGNORE" in the beginning sequence.

There is an output test associated with this input file.

Tests ignoreSect for P63. The ignireSectContents is included.

There is an output test associated with this input file.

Tests ignoreSect for P63. The white space is included before and after the key word "IGNORE" in the beginning sequence.

There is an output test associated with this input file.

Tests ignoreSectContents for P64. One "ignore" field is included.

There is an output test associated with this input file.

Tests ignoreSectContents for P64. Two "ignore" and one "ignoreSectContents" fields are included.

There is an output test associated with this input file.

Tests ignoreSectContents for P64. Four "ignore" and three "ignoreSectContents" fields are included.

There is an output test associated with this input file.

Tests Ignore for P65. An empty string occurs in the Ignore filed.

There is an output test associated with this input file.

Tests Ignore for P65. An string not including the brackets occurs in each of the Ignore filed.

There is an output test associated with this input file.

valid conditional sections are INCLUDE and IGNORE

Test demonstrates the use of the conditional section INCLUDE that will include its contents as part of the DTD.

There is an output test associated with this input file.

Test demonstrates the use of the conditional section INCLUDE that will include its contents as part of the DTD. The keyword is a parameter-entity reference.

There is an output test associated with this input file.

Test demonstrates the use of the conditional section INCLUDE that will include its contents as part of the DTD. The keyword is a parameter-entity reference.

There is an output test associated with this input file.

Test demonstrates the use of the conditional section INCLUDE that will include its contents.

There is an output test associated with this input file.

Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being used.

There is an output test associated with this input file.

Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being used.

There is an output test associated with this input file.

valid INCLUDE sections -- options S before and after keyword, sections can nest

Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being part of the DTD. The keyword is a parameter-entity reference.

There is an output test associated with this input file.

valid IGNORE sections

IGNOREd sections ignore everything except section delimiters

Parameter and General entities use different namespaces, so there can be an entity of each type with a given name.

There is an output test associated with this input file.

Tests all legal CharRef's.

There is an output test associated with this input file.

Tests Reference could be EntityRef or CharRef.

There is an output test associated with this input file.

Tests P68 VC:Entity Declared with Entities in External Subset , standalone is no

There is an output test associated with this input file.

Tests P68 VC:Entity Declared with Entities in External Parameter Entities , standalone is no

There is an output test associated with this input file.

Tests P68 VC:Entity Declared with Parameter Entities in External Subset , standalone is no

There is an output test associated with this input file.

Tests P68 VC:Entity Declared with Parameter Entities in External Parameter Entities, standalone is no

There is an output test associated with this input file.

Contains a character reference to a C0 control character (form-feed), legal in XML 1.1 but not 1.0

There is an output test associated with this input file.

Contains a character reference to a C1 control character (partial line up), legal in both XML 1.0 and 1.1 (but for different reasons)

There is an output test associated with this input file.

Contains a character reference to a C1 control character (partial line up), legal in both XML 1.0 and 1.1 (but for different reasons)

There is an output test associated with this input file.

Test demonstrates use of characters outside of normal ASCII range.

There is an output test associated with this input file.

Test demonstrates the use of decimal Character References within element content.

There is an output test associated with this input file.

Test demonstrates the use of decimal Character References within element content.

There is an output test associated with this input file.

Test demonstrates the use of hexadecimal Character References within element.

There is an output test associated with this input file.

Tests in-line handling of two legal character references, which each expand to a Unicode surrogate pair.

There is an output test associated with this input file.

Expands a CDATA attribute with a character reference.

There is an output test associated with this input file.

Test demonstrates the use of decimal character references within element content.

There is an output test associated with this input file.

Tests entity expansion of three legal character references, which each expand to a Unicode surrogate pair.

There is an output test associated with this input file.

Valid entity references. Also ensures that a charref to '&' isn't interpreted as an entity reference open delimiter

Test demonstrates the expansion of an external parameter entity that declares an attribute.

There is an output test associated with this input file.

Expands an external parameter entity in two different ways, with one of them declaring an attribute.

There is an output test associated with this input file.

Test demonstrates the expansion of an external parameter entity that declares an attribute.

There is an output test associated with this input file.

Test demonstrates a parameter entity reference whose value is NULL.

There is an output test associated with this input file.

Valid PEReferences.

Tests whether entities may be declared more than once, with the first declaration being the binding one.

There is an output test associated with this input file.

Test demonstrates that when more that one definition is provided for the same entity only the first declaration is binding.

There is an output test associated with this input file.

Tests all legal GEDecls and PEDecls constructs derived from P70-76

There is an output test associated with this input file.

Test demonstrates a parameter entity declaration whose parameter entity definition is an ExternalID.

There is an output test associated with this input file.

An EntityDecl is either a GEDecl or a PEDecl

Valid GEDecls

Tests that an external PE may be defined (but not referenced).

There is an output test associated with this input file.

Tests that an external PE may be defined (but not referenced).

There is an output test associated with this input file.

Test demonstrates a parameter entity declaration that contains an attribute list declaration.

There is an output test associated with this input file.

Test demonstrates a parameter entity declaration that contains a partial attribute list declaration.

There is an output test associated with this input file.

Valid PEDecls

EntityDef is either Entity value or an external id, with an optional NDataDecl

Test demonstrates both internal and external entities and that processing of entity references may be required to produce the correct replacement text.

There is an output test associated with this input file.

Test demonstrates the use of external entity and how replacement text is retrieved and processed. Also tests the use of an EncodingDecl of UTF-16.

There is an output test associated with this input file.

Test demonstrates the use of external entity and how replacement text is retrieved and processed.

There is an output test associated with this input file.

Test demonstrates the use of an ExternalID within a document type definition.

There is an output test associated with this input file.

Test demonstrates the use of an ExternalID within a document type definition.

There is an output test associated with this input file.

Test demonstrates that an external identifier may include a public identifier.

There is an output test associated with this input file.

Test demonstrates that an external identifier may include a public identifier.

There is an output test associated with this input file.

Test demonstrates an EnternalID whose contents contain an parameter entity declaration and a attribute list definition.

There is an output test associated with this input file.

valid NDataDecls

Tests use of external parsed entities with and without content.

There is an output test associated with this input file.

Test demonstrates an enternal parsed entity that begins with a text declaration.

There is an output test associated with this input file.

Tests ExtParsedEnt, also TextDecl in P77 and EncodingDecl in P80

There is an output test associated with this input file.

Tests extPE

Contains a character reference to a C0 control character (form-feed) in an entity value. This will be legal (in XML 1.1) when the entity declaration is parsed, but what about when it is used? According to the grammar in the CR spec, it should be illegal (because the replacement text must match "content"), but this is probably not intended. This will be fixed in the PR version.

There is an output test associated with this input file.

Tests use of external parsed entities with different encodings than the base document.

There is an output test associated with this input file.

Test support for little-endian UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.)

Test support UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.)

Test support for UTF-8 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.)

Test support for little-endian UTF-16 encoding, and XML names which contain Japanese characters.

Test support for UTF-16 encoding, and XML names which contain Japanese characters.

Test support for UTF-8 encoding and XML names which contain Japanese characters.

Test demonstrates a valid EncodingDecl within the prolog.

There is an output test associated with this input file.

Test demonstrates the name of the encoding can be composed of lowercase characters.

There is an output test associated with this input file.

The VersionNum of the document entity is 1.1 whereas the VersionNum of the external DTD is 1.0. The character #xC0 which is a valid XML 1.1 but an invalid XML 1.0 character is present in both documents.

The VersionNum of the document entity is 1.1 whereas the VersionNum of the external DTD is 1.0. The character #x1FFF which is a valid XML 1.1 but an invalid XML 1.0 character is present in both documents.

The VersionNum of the document entity is 1.1 whereas the VersionNum of the external DTD is 1.0. The character #xF901 which is a valid XML 1.1 but an invalid XML 1.0 character is present in both documents.

The VersionNum of the document entity is 1.1 whereas the VersionNum of the external entity is 1.0. The character #xD6 which is a valid XML 1.1 but an invalid XML 1.0 character is present in both documents.

The VersionNum of the document entity is 1.1 whereas the VersionNum of the external entity is 1.0. The character #x1FFF which is a valid XML 1.1 but an invalid XML 1.0 character is present in both documents.

The VersionNum of the document entity is 1.1 whereas the VersionNum of the external entity is 1.0. The character #xF901 which is a valid XML 1.1 but an invalid XML 1.0 character is present in both documents.

The VersionNum of the document and external dtd is 1.1 and both contain the valid XML1.1 but invalid XML1.0 character #xD8.

The VersionNum of the document and external dtd is 1.1 and both contain the valid XML1.1 but invalid XML1.0 character #x1FFF.

The VersionNum of the document and external dtd is 1.1 and both contain the valid XML1.1 but invalid XML1.0 character #xF901.

The VersionNum of the document and external entity is 1.1 and both contain the valid XML1.1 but invalid XML1.0 character #xF6.

The VersionNum of the document and external entity is 1.1 and both contain the valid XML1.1 but invalid XML1.0 character #x1FFF.

The VersionNum of the document and external entity is 1.1 and both contain the valid XML1.1 but invalid XML1.0 character #xF901.

The VersionNum of the document entity is 1.1 but the external dtd does not contain a textDecl and both contain the valid XML1.1 but invalid XML1.0 character #xF8.

The VersionNum of the document entity is 1.1 but the external dtd does not contain a textDecl and both contain the valid XML1.1 but invalid XML1.0 character #x1FFF.

The VersionNum of the document entity is 1.1 but the external dtd does not contain a textDecl and both contain the valid XML1.1 but invalid XML1.0 character #xF901.

The VersionNum of the document entity is 1.1 but the external entity does not contain a textDecl and both contain the valid XML1.1 but invalid XML1.0 character #x2FF.

The VersionNum of the document entity is 1.1 but the external entity does not contain a textDecl and both contain the valid XML1.1 but invalid XML1.0 character #x1FFF.

The VersionNum of the document entity is 1.1 but the external entity does not contain a textDecl and both contain the valid XML1.1 but invalid XML1.0 character #xF901.

The VersionNum of the document and external dtd is 1.1. The replacement text of an entity declared in the external DTD contains a reference to the character #x7F. This entity is not referenced in the document entity.

The VersionNum of the document and external dtd is 1.1. The replacement text of an entity declared in the external DTD contains a reference to the character #x80. This entity is not referenced in the document entity.

The VersionNum of the document and external dtd is 1.1. The replacement text of an entity declared in the external DTD contains a reference to the character #x9F. This entity is not referenced in the document entity.

The VersionNum of the document and the external entity is 1.1. The entity contains a reference to the character #x7F.

The VersionNum of the document and the external entity is 1.1. The entity contains a reference to the character #x80.

The VersionNum of the document and the external entity is 1.1. The entity contains a reference to the character #x9F.

The VersionNum of the document is 1.1 and the textDecl is missing in the external DTD. The replacement text of an entity declared in the external DTD contains a reference to the character #x7F, #x8F. This entity is not referenced in the document entity.

The VersionNum of the document is 1.1 and the textDecl is missing in the external DTD. The replacement text of an entity declared in the external DTD contains a reference to the character #x80, #x90. This entity is not referenced in the document entity.

The VersionNum of the document is 1.1 and the textDecl is missing in the external DTD. The replacement text of an entity declared in the external DTD contains a reference to the character #x81, #x9F. This entity is not referenced in the document entity.

The VersionNum of the document is 1.1 and the textDecl is missing in the external entity. The replacement text of an entity declared in the external DTD contains a reference to the character #x7F, #x80, #x9F.

The VersionNum of the document is 1.1 and the textDecl is missing in the external entity. The replacement text of an entity declared in the external DTD contains a reference to the character #x85, #x8F.

The VersionNum of the document is 1.1 and the textDecl is missing in the external entity. The replacement text of an entity declared in the external DTD contains a reference to the character #x1, #x7F.

Tests inclusion of a well-formed internal entity, which holds an element required by the content model.

There is an output test associated with this input file.

Verifies that internal parameter entities are correctly expanded within the internal subset.

There is an output test associated with this input file.

Test demonstrates that a parameter entity will be expanded with spaces on either side.

There is an output test associated with this input file.

Parameter entities expand with spaces on either side.

There is an output test associated with this input file.

Tests ability to define an internal entity which can't legally be expanded (contains an unquoted <).

There is an output test associated with this input file.

Tests whether character references in internal entities are expanded early enough, by relying on correct handling to make the entity be well formed.

There is an output test associated with this input file.

Tests whether entity references in internal entities are expanded late enough, by relying on correct handling to make the expanded text be valid. (If it's expanded too early, the entity will parse as an element that's not valid in that context.)

There is an output test associated with this input file.

This tests whether entity expansion is (incorrectly) done while processing entity declarations; if it is, the entity value literal will terminate prematurely.

There is an output test associated with this input file.

Test demonstrates that entity expansion is done while processing entity declarations.

There is an output test associated with this input file.

Test demonstrates that entity expansion is done while processing entity declarations.

There is an output test associated with this input file.

Tests construction of internal entity replacement text, using an example in the XML specification.

There is an output test associated with this input file.

Tests construction of internal entity replacement text, using an example in the XML specification.

There is an output test associated with this input file.

Tests construction of internal entity replacement text, using a complex example in the XML specification.

There is an output test associated with this input file.

Verifies that an XML parser will parse a NOTATION declaration; the output phase of this test ensures that it's reported to the application.

There is an output test associated with this input file.

Tests NotationDecl in P82 and PublicID in P83

There is an output test associated with this input file.

NOTATION declarations don't need SYSTEM IDs; and externally declared notations may be used to declare unparsed entities in the internal DTD subset. The notation must be reported to the application.

There is an output test associated with this input file.

This test case covers 149 legal character ranges plus 51 single legal characters for BaseChar in P85 using a PI target Name

This test case covers 2 legal character ranges plus 1 single legal characters for IdeoGraphic in P86 using a PI target Name

This test case covers 65 legal character ranges plus 30 single legal characters for CombiningChar in P87 using a PI target Name

This test case covers 15 legal character ranges for Digit in P88 using a PI target Name

This test case covers 3 legal character ranges plus 8 single legal characters for Extender in P89 using a PI target Name

Tests BaseChar with an only legal per 5th edition character. The character #x0132 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0133 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x013F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0140 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0149 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x017F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x01c4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x01CC occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0BB6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0BBA occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C0D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C11 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C29 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C34 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C5F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C62 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C8D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0C91 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x01F1 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0CA9 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0CB4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0CBA occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0CDF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0CE2 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0D0D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0D11 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0D29 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0D3A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0D62 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x01F3 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E2F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E31 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E34 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E46 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E83 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E85 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E89 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E8B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E8E occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0E98 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x01F6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EA0 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EA4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EA6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EA8 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EAC occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EAF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EB1 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EB4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EBE occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0EC5 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x01F9 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0F48 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0F6A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x10C6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x10F7 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1011 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1104 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1108 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x110A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x110D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x113B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x01F9 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x113F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1141 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x114D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x114f occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1151 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1156 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x115A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1162 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1164 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1166 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0230 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x116B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x116F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1174 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x119F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x11AC occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x11B6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x11B9 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x11BB occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x11C3 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x11F1 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x02AF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x11FA occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1E9C occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1EFA occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F16 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F1E occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F46 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F4F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F58 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F5A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F5C occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x02CF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F5E occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1F7E occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FB5 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FBD occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FBF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FC5 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FCD occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FD5 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FDC occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FED occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0387 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FF5 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x1FFD occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x2127 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x212F occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x2183 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x3095 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x30FB occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x312D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #xD7A4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x038B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x03A2 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x03CF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x03D7 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x03DD occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x03E1 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x03F4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x040D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0450 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x045D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0482 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x04C5 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x04C6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x04C9 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x04EC occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x04ED occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x04F6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x04FA occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0557 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0558 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0587 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x05EB occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x05F3 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0620 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x063B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x064B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x06B8 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x06BF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x06CF occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x06D4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x06D6 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x06E7 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x093A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x093E occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0962 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x098D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0991 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0992 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x09A9 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x09B1 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x09B5 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x09BA occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x09DE occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x09E2 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x09F2 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A0B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A11 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A29 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A31 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A34 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A37 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A3A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A5D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A70 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A75 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #xA84 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0ABC occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0A92 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0AA9 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0AB1 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0AB4 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0ABA occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B04 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B0D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B11 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B29 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B31 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B34 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B3A occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B3E occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B5E occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B62 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B8B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B91 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B98 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B9B occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0B9D occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0BA0 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0BA7 occurs as the first character of the PITarget in the PI in the DTD.

Tests BaseChar with an only legal per 5th edition character. The character #x0BAB occurs as the first character of the PITarget in the PI in the DTD.

Tests Ideographic with an only legal per 5th edition character. The character #x4CFF occurs as the first character in the PITarget in the PI in the DTD.

Tests Ideographic with an only legal per 5th edition character. The character #x9FA6 occurs as the first character in the PITarget in the PI in the DTD.

Tests Ideographic with an only legal per 5th edition character. The character #x3008 occurs as the first character in the PITarget in the PI in the DTD.

Tests Ideographic with an only legal per 5th edition character. The character #x302A occurs as the first character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x02FF occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0346 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0362 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0487 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x05A2 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x05BA occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x05BE occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x05C0 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x05C3 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0653 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x06B8 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x06B9 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x06E9 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x06EE occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0904 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x093B occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x094E occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0955 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0964 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0984 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x09C5 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x09C9 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x09CE occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x09D8 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x09E4 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0A03 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0A3D occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0A46 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0A49 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0A4E occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0A80 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0A84 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0ABB occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0AC6 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0ACA occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0ACE occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0B04 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0B3B occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0B44 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0B4A occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0B4E occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0B58 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0B84 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0BC3 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0BC9 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0BD6 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0C0D occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0C45 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0C49 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0C54 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0C81 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0C84 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0CC5 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0CC9 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0CD4 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0CD7 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0D04 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0D45 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0D49 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0D4E occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0D58 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0E3F occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0E3B occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0E4F occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0EBA occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0EBE occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0ECE occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F1A occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F36 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F38 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F3B occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F3A occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F70 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F85 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F8C occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F96 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0F98 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0FB0 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0FB8 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x0FBA occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x20DD occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x20E2 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x3030 occurs as the second character in the PITarget in the PI in the DTD.

Tests CombiningChar with an only legal per 5th edition character. The character #x309B occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x066A occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x06FA occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0970 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x09F2 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0AF0 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0B70 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0C65 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0CE5 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0CF0 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0D70 occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0E5A occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0EDA occurs as the second character in the PITarget in the PI in the DTD.

Tests Digit with an only legal per 5th edition character. The character #x0F2A occurs as the second character in the PITarget in the PI in the DTD.

Tests Extender with an only legal per 5th edition character. The character #x02D2 occurs as the second character in the PITarget in the PI in the DTD.

Tests Extender with an only legal per 5th edition character. The character #x03FE occurs as the second character in the PITarget in the PI in the DTD.

Tests Extender with an only legal per 5th edition character. The character #x065F occurs as the second character in the PITarget in the PI in the DTD.

CDATA sections may occur in Mixed content.

CDATA sections, comments and PIs may occur in ANY content.

Non-syntactic validity errors in default attributes only happen if the attribute is in fact defaulted.

Element content can contain entity reference if replacement text is whitespace

Element content can contain entity reference if replacement text is whitespace, even if it came from a character reference in the literal entity value

Element content can contain a comment

Element content can contain a PI

Mixed content can contain a comment

Mixed content can contain a PI

External entity containing start of entity declaration is base URI for system identifier

There is an output test associated with this input file.

Parameter entities and character references are included-in-literal, but general entities are bypassed.

There is an output test associated with this input file.

UTF-8 entities may start with a BOM

Either the built-in entity or a character reference can be used to represent greater-than after two close-square-brackets

Three-letter language codes are allowed

An external ATTLIST declaration does not make a document non-standalone if the normalization would have been the same without the declaration

An xml:lang attribute may be empty

ANY content allows character data

All line-ends are normalized, even those not passed to the application. NB this can only be tested effectively in XML 1.1, since CR is in the S production; in 1.1 we can use NEL which isn't.

Conditional sections are allowed in external parameter entities referred to from the internal subset.

An unused attribute default need only be syntactically correct

All conforming XML 1.0 Validating Processors are required to report recoverable errors in the case of documents which are Invalid. Such errors are violations of some validity constraint (VC).

If a validating processor does not report an error when given one of these test cases, or if the error reported is a fatal error, it is not conformant. If the error reported does not correspond to the problem listed in this test description, that could also be a conformance problem; it might instead be a faulty diagnostic.

All conforming XML 1.0 Nonvalidating Processors should accept these documents, reporting no errors.

Simple legal case: no namespaces

Reserved prefixes and namespaces: using the xml prefix undeclared

no prolog

Misc items after the document

Has a NEL character in an NMTOKENS attribute; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

Has an LSEP character in an NMTOKENS attribute; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

Has a NEL character in element content whitespace; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

Has an LSEP character in element content whitespace; well-formed in both XML 1.0 and 1.1, but valid only in 1.1

There is an output test associated with this input file.

Has a "long s" in a name, legal in XML 1.1, illegal in XML 1.0 thru 4th edition

There is an output test associated with this input file.

Has a Byzantine Musical Symbol Kratimata in a name, legal in XML 1.1, illegal in XML 1.0 thru 4th edition

There is an output test associated with this input file.

Has the last legal namechar in XML 1.1, illegal in XML 1.0 thru 4th edition

There is an output test associated with this input file.

Has an NMTOKENS attribute containing a NEL character that comes from a character reference in an internal entity. Because NEL is not in the S production (even though real NELs are converted to LF on input), this is invalid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Has an NMTOKENS attribute containing a NEL character that comes from a character reference in an internal entity. Because NEL is not in the S production (even though real NELs are converted to LF on input), this is invalid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Has element content whitespace containing a NEL character that comes from a character reference in an internal entity. Because NEL is not in the S production (even though real NELs are converted to LF on input), this is invalid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Has element content whitespace containing a NEL character that comes from a character reference in an internal entity. Because NEL is not in the S production (even though real NELs are converted to LF on input), this is invalid in both XML 1.0 and 1.1.

There is an output test associated with this input file.

Has a "long s" in a name, legal in XML 1.1, legal in XML 1.0 5th edition

Has a Byzantine Musical Symbol Kratimata in a name, legal in XML 1.1, legal in XML 1.0 5th edition

Has the last legal namechar in XML 1.1, legal in XML 1.0 5th edition

valid attribute values

all valid S characters

names with all valid ASCII characters, and one from each other class in NameChar

Character '&#x309a;' is a CombiningChar, not a Letter, but as of 5th edition, may begin a name (c.f. xmltest/not-wf/sa/140.xml).

various valid Name constructions

As of 5th edition, character #x0E5C is legal in XML names (c.f. xmltest/not-wf/sa/141.xml).

Requires at least one name.

at least one Nmtoken is required.

an invalid Nmtoken character.

CDATA section containing only white space does not match the nonterminal S, and cannot appear in these positions.

valid CharData

valid comments

Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.

Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.

Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.

valid CDSect's. Note that a CDStart in a CDSect is not recognized as such

Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between two parameter entities.

Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between two parameter entities.

Tests the Root Element Type VC

The test violates VC:Root Element Type in P28. The Name in the document type declaration does not match the element type of the root element.

There is an output test associated with this input file.

prolog can be empty

XML declaration only

XML decl and Misc

Test shows a valid XML declaration along with version info.

Test shows a valid XML declaration along with encoding declaration.

Test shows a valid XML declaration along with Standalone Document Declaration.

Test shows a valid XML declaration, encoding declarationand Standalone Document Declaration.

Test shows a prolog that has the VersionInfo delimited by double quotes.

Test shows a prolog that has the VersionInfo delimited by single quotes.

Test shows whitespace is allowed in prolog before version info.

Test shows whitespace is allowed in prolog on both sides of equal sign.

Test shows whitespace is NOT necessary before or after equal sign of versioninfo.

Test shows whitespace can be used on both sides of equal sign of versioninfo.

The valid version number. We cannot test others because a 1.0 processor is allowed to fail them.

Comments are valid as the Misc part of the prolog.

Processing Instructions are valid as the Misc part of the prolog.

Whitespace is valid as the Misc part of the prolog.

A combination of comments, whitespaces and processing instructions are valid as the Misc part of the prolog.

Tests the Standalone Document Declaration VC, ensuring that optional whitespace causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that attributes needing normalization cause a validity error.

Tests the Standalone Document Declaration VC, ensuring that attributes needing defaulting cause a validity error.

Tests the Standalone Document Declaration VC, ensuring that a token attribute that needs normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that a NOTATION attribute that needs normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that an NMTOKEN attribute needing normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that an NMTOKENS attribute needing normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that an ID attribute needing normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that an IDREF attribute needing normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that an IDREFS attribute needing normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that an ENTITY attribute needing normalization causes a validity error.

Tests the Standalone Document Declaration VC, ensuring that an ENTITIES attribute needing normalization causes a validity error.

This test violates VC: Standalone Document Declaration in P32. The standalone document declaration has the value yes, BUT there is an external markup declaration of attributes with default values, and the associated element appears in the document with specified values for those attributes.

There is an output test associated with this input file.

This test violates VC: Standalone Document Declaration in P32. The standalone document declaration has the value yes, BUT there is an external markup declaration of attributes with values that will change if normalized.

There is an output test associated with this input file.

This test violates VC: Standalone Document Declaration in P32. The standalone document declaration has the value yes, BUT there is an external markup declaration of element with element content, and white space occurs directly within the mixed content.

There is an output test associated with this input file.

Double quotes can be used as delimeters for the value of a Standalone Document Declaration.

Single quotes can be used as delimeters for the value of a Standalone Document Declaration.

Tests the "Element Valid" VC (clause 2) by omitting a required element.

Tests the Element Valid VC (clause 4) by including an undeclared child element.

Tests the Element Valid VC (clause 1) by including elements in an EMPTY content model.

Tests the Element Valid VC (clause 3) by including a child element not permitted by a mixed content model.

Tests the Element Valid VC (clause 1), using one of the predefined internal entities inside an EMPTY content model.

CDATA sections containing only whitespace do not match the nonterminal S, and cannot appear in these positions.

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one is required.

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing two children where one is required.

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where two are required.

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where two are required.

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (one construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a second construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a third construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a fourth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or two are required (a fifth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a basic construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a second construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a third construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a fourth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing three children where one or two are required (a fifth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a sixth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a seventh construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (an eigth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a ninth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing no children where one or more are required (a tenth construction of that model).

Tests the Element Valid VC (clause 2) for one instance of "children" content model, providing text content where one or more elements are required.

This test violates VC: Element Valid in P39. Element a is declared empty in DTD, but has content in the document.

There is an output test associated with this input file.

This test violates VC: Element Valid in P39. root is declared only having element children in DTD, but have text content in the document.

There is an output test associated with this input file.

This test violates VC: Element Valid in P39. Illegal elements are inserted in b's content of Mixed type.

There is an output test associated with this input file.

This test violates VC: Element Valid in P39. Element c has undeclared element as its content of ANY type

There is an output test associated with this input file.

Character data is valid element content.

Empty element tag may be used for any element which has no content.

This test violates VC: Attribute Value Type in P41. attr1 for Element b is not declared.

There is an output test associated with this input file.

This test violates VC: Attribute Value Type in P41. attr3 for Element b is given a value that does not match the declaration in the DTD.

There is an output test associated with this input file.

Tests the Attribute Value Type (declared) VC for the xml:space attribute

Tests the Attribute Value Type (declared) VC for the xml:lang attribute

Elements content can be empty.

Whitespace is valid within a Start-tag.

Whitespace and Multiple Attributes are valid within a Start-tag.

Attributes are valid within a Start-tag.

Attributes are valid within a Start-tag.

Whitespace is valid within a Start-tags Attribute.

Test shows proper syntax for an End-tag.

Whitespace is valid after name in End-tag.

Valid display of an Empty Element Tag.

Empty Element Tags can contain an Attribute.

Whitespace is valid in an Empty Element Tag following the end of the attribute value.

Whitespace is valid after the name in an Empty Element Tag.

Whitespace and Multiple Attributes are valid in an Empty Element Tag.

Tests the Unique Element Type Declaration VC.

This test violates VC: Unique Element Type Declaration. Element not_unique has been declared 3 time in the DTD.

There is an output test associated with this input file.

Tests the "Proper Group/PE Nesting" validity constraint by fragmenting a content model between two parameter entities.

Violates VC:Proper Group/PE Nesting in P49. Open and close parenthesis for a choice content model are in different PE replace Texts.

There is an output test associated with this input file.

Violates VC:Proper Group/PE Nesting in P50. Open and close parenthesis for a seq content model are in different PE replace Texts.

There is an output test associated with this input file.

An element with Element-Only content contains the character #x85 (NEL not a whitespace character as defined by S).

An element with Element-Only content contains the character #x2028 (LESP not a whitespace character as defined by S).

Tests the No Duplicate Types VC

Tests the No Duplicate Types VC.

Violates VC:Proper Group/PE Nesting in P51. Open and close parenthesis for a Mixed content model are in different PE replace Texts.

There is an output test associated with this input file.

Violates VC:No Duplicate Types in P51. Element a appears twice in the Mixed content model of Element e.

There is an output test associated with this input file.

Tests the ID (is a Name) VC

Tests the ID (appears once) VC

Tests the One ID per Element Type VC

Tests the ID Attribute Default VC

Tests the ID Attribute Default VC

Tests the IDREF (is a Name) VC

Tests the IDREFS (is a Names) VC

Tests the IDREF (matches an ID) VC

Tests the IDREF (IDREFS matches an ID) VC

Tests the "Entity Name" VC for the ENTITY attribute type.

Tests the "Entity Name" VC for the ENTITIES attribute type.

Tests the "Notation Attributes" VC for the NOTATION attribute type, first clause: value must be one of the ones that's declared.

Tests the "Notation Attributes" VC for the NOTATION attribute type, second clause: the names in the declaration must all be declared.

Tests the "Name Token" VC for the NMTOKEN attribute type.

Tests the "Name Token" VC for the NMTOKENS attribute type.

Tests the "Enumeration" VC by providing a value which wasn't one of the choices.

Tests invalid TokenizedType which is against P56 VC: ID. The value of the ID attribute "UniqueName" is "@999" which does not meet the Name production.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: ID. The two ID attributes "attr" and "UniqueName" have the same value "Ac999" for the element "b" and the element "tokenizer".

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: ID Attribute Default. The "#FIXED" occurs in the DefaultDecl for the ID attribute "UniqueName".

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: ID Attribute Default. The constant string "BOGUS" occurs in the DefaultDecl for the ID attribute "UniqueName".

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: One ID per Element Type. The element "a" has two ID attributes "first" and "second".

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: IDREF. The value of the IDREF attribute "reference" is "@456" which does not meet the Name production.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: IDREF. The value of the IDREF attribute "reference" is "BC456" which does not match the value assigned to any ID attributes.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: IDREFS. The value of the IDREFS attribute "reference" is "AC456 #567" which does not meet the Names production.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: IDREFS. The value of the IDREFS attribute "reference" is "EF456 DE355" which does not match the values assigned to two ID attributes.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: Entity Name. The value of the ENTITY attribute "sun" is "ima ge" which does not meet the Name production.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: Entity Name. The value of the ENTITY attribute "sun" is "notimage" which does not match the name of any unparsed entity declared.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: Entity Name. The value of the ENTITY attribute "sun" is "parsedentity" which matches the name of a parsed entity instead of an unparsed entity declared.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: Entity Name. The value of the ENTITIES attribute "sun" is "#image1 @image" which does not meet the Names production.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: ENTITIES. The value of the ENTITIES attribute "sun" is "image3 image4" which does not match the names of two unparsed entities declared.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: ENTITIES. The value of the ENTITIES attribute "sun" is "parsedentity1 parsedentity2" which matches the names of two parsed entities instead of two unparsed entities declared.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: Name Token. The value of the NMTOKEN attribute "thistoken" is "x : image" which does not meet the Nmtoken production.

There is an output test associated with this input file.

Tests invalid TokenizedType which is against P56 VC: Name Token. The value of the NMTOKENS attribute "thistoken" is "@lang y: #country" which does not meet the Nmtokens production.

There is an output test associated with this input file.

Tests invalid NotationType which is against P58 VC: Notation Attributes. The attribute "content-encoding" with value "raw" is not a value from the list "(base64|uuencode)".

There is an output test associated with this input file.

Tests invalid NotationType which is against P58 VC: Notation Attributes. The attribute "content-encoding" with value "raw" is a value from the list "(base64|uuencode|raw|ascii)", but "raw" is not a declared notation.

There is an output test associated with this input file.

Tests invalid Enumeration which is against P59 VC: Enumeration. The value of the attribute is "ONE" which matches neither "one" nor "two" as declared in the Enumeration in the AttDef in the AttlistDecl.

There is an output test associated with this input file.

Validity Constraint: No duplicate tokens

Tests the Required Attribute VC.

Tests the "Fixed Attribute Default" VC by providing the wrong value.

Tests the "Attribute Default Legal" VC by providing an illegal IDREF value.

Tests the "Attribute Default Legal" VC by providing an illegal IDREFS value.

Tests the "Attribute Default Legal" VC by providing an illegal ENTITY value.

Tests the "Attribute Default Legal" VC by providing an illegal ENTITIES value.

Tests the "Attribute Default Legal" VC by providing an illegal NMTOKEN value.

Tests the "Attribute Default Legal" VC by providing an illegal NMTOKENS value.

Tests the "Attribute Default Legal" VC by providing an illegal NOTATIONS value.

Tests the "Attribute Default Legal" VC by providing an illegal enumeration value.

Tests invalid DefaultDecl which is against P60 VC: Required Attribute. The attribute "chapter" for the element "two" is declared as #REQUIRED in the DefaultDecl in the AttlistDecl, but the value of this attribute is not given.

There is an output test associated with this input file.

Tests invalid DefaultDecl which is against P60 VC: Fixed Attribute Default.. The attribute "chapter" for the element "one" is declared as #FIXED with the given value "Introduction" in the DefaultDecl in the AttlistDecl, but the value of a instance of this attribute is assigned to "JavaBeans".

There is an output test associated with this input file.

Tests invalid DefaultDecl which is against P60 VC: Attribute Default Legal. The declared default value "c" is not legal for the type (a|b) in the AttDef in the AttlistDecl.

There is an output test associated with this input file.

Tests invalid DefaultDecl which is against P60 VC: Attribute Default Legal. The declared default value "@#$" is not legal for the type NMTOKEN the AttDef in the AttlistDecl.

There is an output test associated with this input file.

Test the "Proper Conditional Section/ PE Nesting" validity constraint.

There is an output test associated with this input file.

Simple legal case: prefixed element

Simple legal case: prefixed attribute

valid character references

PEDef is either an entity value or an external id

Tests the "Notation Declared" VC by using an undeclared notation name.

Tests invalid NDataDecl which is against P76 VC: Notation declared. The Name "JPGformat" in the NDataDecl in the EntityDecl for "ge2" does not match the Name of any declared notation.

There is an output test associated with this input file.

valid external identifiers

Byte order mark in general entity should go away (big-endian)

There is an output test associated with this input file.

Byte order mark in general entity should go away (little-endian)

There is an output test associated with this input file.

Byte order mark in general entity should go away (utf-8)

There is an output test associated with this input file.

Two byte order marks in general entity produce only one (big-endian)

There is an output test associated with this input file.

Two byte order marks in general entity produce only one (little-endian)

There is an output test associated with this input file.

Two byte order marks in general entity produce only one (utf-8)

There is an output test associated with this input file.

Tests reading an invalid "big endian" UTF-16 document

Tests reading an invalid "little endian" UTF-16 document

Simple legal case: prefix rebinding

Simple legal case: default namespace

Simple legal case: default namespace and unbinding

Simple legal case: default namespace and rebinding

Attribute uniqueness: different attributes with same local name

Attribute uniqueness: prefixed and unprefixed attributes with same local name

Attribute uniqueness: prefixed and unprefixed attributes with same local name, with default namespace

Attribute uniqueness: prefixed and unprefixed attributes with same local name, with default namespace and element in default namespace

Attribute uniqueness: prefixed and unprefixed attributes with same local name, element in same namespace as prefixed attribute

1.1 style prefix unbinding

1.1 style prefix unbinding and rebinding

Tests Extender with an only legal per 5th edition character. The character #x0EC7 occurs as the second character in the PITarget in the PI in the prolog, and in an element name.

Tests Extender with an only legal per 5th edition character. The character #x3006 occurs as the second character in the PITarget in the PI in the prolog, and in an element name.

Tests Extender with an only legal per 5th edition character. The character #x3030 occurs as the second character in the PITarget in the PI in the prolog, and in an element name.

Tests Extender with an only legal per 5th edition character. The character #x3036 occurs as the second character in the PITarget in the PI in the prolog, and in an element name.

Tests Extender with an only legal per 5th edition character. The character #x309C occurs as the second character in the PITarget in the PI in the prolog, and in an element name.

Tests Extender with an only legal per 5th edition character. The character #x309F occurs as the second character in the PITarget in the PI in the prolog, and in an element name.

Tests Extender with an only legal per 5th edition character. The character #x30FF occurs as the second character in the PITarget in the PI in the prolog, and in an element name.

Default values for IDREF attributes must match Name.

Default values for ENTITY attributes must match Name.

Default values for IDREFS attributes must match Names.

Default values for ENTITIES attributes must match Names.

Default values for NMTOKEN attributes must match Nmtoken.

Default values for NMTOKENS attributes must match Nmtokens.

Default values for NOTATION attributes must match one of the enumerated values.

Default values for enumerated attributes must match one of the enumerated values.

Even internal parameter entity references are enough to make undeclared entities into mere validity errors rather than well-formedness errors.

Declarations mis-nested wrt parameter entities are just validity errors (but note that some parsers treat some such errors as fatal)

Empty content can't contain an entity reference

Empty content can't contain a comment

Empty content can't contain a PI

Empty content can't contain whitespace

Element content can't contain character reference to whitespace

Element content can't contain entity reference if replacement text is character reference to whitespace

Duplicate token in enumerated attribute declaration

Duplicate token in NOTATION attribute declaration

Tokens, after normalization, must be separated by space, not other whitespace characters

An attribute default must be syntactically correct even if unused

Reserved prefixes and namespaces: declaring the xml prefix correctly

Reserved prefixes and namespaces: binding a reserved prefix

Colon in ID attribute name

Colon in ID attribute name

All conforming XML 1.0 Processors are required to report fatal errors in the case of documents which are not Well Formed. Such errors are basically of two types: (a) the document violates the XML grammar; or else (b) it violates a well formedness constraint (WFC). There is a single exception to that requirement: nonvalidating processors which do not read certain types of external entities are not required to detect (and hence report) these errors.

If a processor does not report a fatal error when given one of these test cases, it is not conformant. If the error reported does not correspond to the problem listed in this test description, that could also be a conformance problem; it might instead be a faulty diagnostic.

Namespace equality test: plain repetition

Namespace equality test: use of character reference

Namespace equality test: use of entity reference

Namespace inequality test: equal after attribute value normalization

Bad QName syntax: xmlns:

Illegal use of 1.1-style prefix unbinding in 1.0 document

Tests a document with no element. A well-formed document should have at lease one elements.

Tests a document with wrong ordering of its prolog and element. The element occurs before the xml declaration and the DTD.

Tests a document with wrong combination of misc and element. One PI occurs between two elements.

Empty document, with no root element.

S cannot occur before the prolog

comments cannot occur before the prolog

only one document element

document element must be complete.

Tests a comment which contains an illegal Char: #x00

Tests a comment which contains an illegal Char: #x01

Tests a comment which contains an illegal Char: #x02

Tests a comment which contains an illegal Char: #x03

Tests a comment which contains an illegal Char: #x04

Tests a comment which contains an illegal Char: #x05

Tests a comment which contains an illegal Char: #x06

Tests a comment which contains an illegal Char: #x07

Tests a comment which contains an illegal Char: #x08

Tests a comment which contains an illegal Char: #x0B

Tests a comment which contains an illegal Char: #x0C

Tests a comment which contains an illegal Char: #x0E

Tests a comment which contains an illegal Char: #x0F

Tests a comment which contains an illegal Char: #x10

Tests a comment which contains an illegal Char: #x11

Tests a comment which contains an illegal Char: #x12

Tests a comment which contains an illegal Char: #x13

Tests a comment which contains an illegal Char: #x14

Tests a comment which contains an illegal Char: #x15

Tests a comment which contains an illegal Char: #x16

Tests a comment which contains an illegal Char: #x17

Tests a comment which contains an illegal Char: #x18

Tests a comment which contains an illegal Char: #x19

Tests a comment which contains an illegal Char: #x1A

Tests a comment which contains an illegal Char: #x1B

Tests a comment which contains an illegal Char: #x1C

Tests a comment which contains an illegal Char: #x1D

Tests a comment which contains an illegal Char: #x1E

Tests a comment which contains an illegal Char: #x1F

Tests a comment which contains an illegal Char: #xD800

Tests a comment which contains an illegal Char: #xDFFF

Tests a comment which contains an illegal Char: #xFFFE

Tests a comment which contains an illegal Char: #xFFFF

Contains a C1 control, legal in XML 1.0, illegal in XML 1.1

Contains a DEL, legal in XML 1.0, illegal in XML 1.1

Contains a C0 control character (form-feed), illegal in both XML 1.0 and 1.1

Contains a C0 control character (form-feed), illegal in both XML 1.0 and 1.1

Contains a C1 control character (partial line up), legal in XML 1.0 but not 1.1

A form feed is not a legal XML character.

A form feed is not a legal XML character.

A form feed is not a legal XML character.

An ESC (octal 033) is not a legal XML character.

A form feed is not a legal XML character.

Character #x0000 is not legal anywhere in an XML document.

Character #x001F is not legal anywhere in an XML document.

Character #xFFFF is not legal anywhere in an XML document.

Character #xD800 is not legal anywhere in an XML document. (If it appeared in a UTF-16 surrogate pair, it'd represent half of a UCS-4 character and so wouldn't really be in the document.)

Character references must also refer to legal XML characters; #x00110000 is one more than the largest legal character.

Character FFFF is not legal anywhere in an XML document.

Character FFFE is not legal anywhere in an XML document.

An unpaired surrogate (D800) is not legal anywhere in an XML document.

An unpaired surrogate (DC00) is not legal anywhere in an XML document.

Four byte UTF-8 encodings can encode UCS-4 characters which are beyond the range of legal XML characters (and can't be expressed in Unicode surrogate pairs). This document holds such a character.

Character FFFF is not legal anywhere in an XML document.

Character FFFF is not legal anywhere in an XML document.

Character FFFF is not legal anywhere in an XML document.

Character FFFF is not legal anywhere in an XML document.

Character FFFF is not legal anywhere in an XML document.

Character FFFF is not legal anywhere in an XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

This test contains embeded control character 0x1.

This test contains embeded control character 0x2.

This test contains embeded control character 0x3.

This test contains embeded control character 0x4.

This test contains embeded control character 0x5.

This test contains embeded control character 0x6.

This test contains embeded control character 0x7.

This test contains embeded control character 0x8.

This test contains embeded control character 0x0.

This test contains embeded control character 0x100.

This test contains embeded control character 0x0B.

This test contains embeded control character 0x0C.

This test contains embeded control character 0x0E.

This test contains embeded control character 0x0F.

This test contains embeded control character 0x10.

This test contains embeded control character 0x11.

This test contains embeded control character 0x12.

This test contains embeded control character 0x13.

This test contains embeded control character 0x14.

This test contains embeded control character 0x15.

This test contains embeded control character 0x16.

This test contains embeded control character 0x17.

This test contains embeded control character 0x18.

This test contains embeded control character 0x19.

This test contains embeded control character 0x1A.

This test contains embeded control character 0x1B.

This test contains embeded control character 0x1C.

This test contains embeded control character 0x1D.

This test contains embeded control character 0x1E.

This test contains embeded control character 0x1F.

This test contains embeded control character 0x7F.

This test contains embeded control character 0x80.

This test contains embeded control character 0x81.

This test contains embeded control character 0x82.

This test contains embeded control character 0x83.

This test contains embeded control character 0x84.

This test contains embeded control characters x82, x83 and x84.

This test contains embeded control character 0x86.

This test contains embeded control character 0x87.

This test contains embeded control character 0x88.

This test contains embeded control character 0x89.

This test contains embeded control character 0x8A.

This test contains embeded control character 0x8B.

This test contains embeded control character 0x8C.

This test contains embeded control character 0x8D.

This test contains embeded control character 0x8E.

This test contains embeded control character 0x8F.

This test contains embeded control character 0x90.

This test contains embeded control character 0x91.

This test contains embeded control character 0x92.

This test contains embeded control character 0x93.

This test contains embeded control character 0x94.

This test contains embeded control character 0x95.

This test contains embeded control character 0x96.

This test contains embeded control character 0x97.

This test contains embeded control character 0x98.

This test contains embeded control character 0x99.

This test contains embeded control character 0x9A.

This test contains embeded control character 0x9B.

This test contains embeded control character 0x9C.

This test contains embeded control character 0x9D.

This test contains embeded control character 0x9E.

This test contains embeded control characters present in an external entity.

This test contains embeded control characters present in an external entity.

This test contains embeded control characters present in an external entity.

This test contains embeded character 0xD800. (Invalid UTF8 sequence)

This test contains embeded character 0xFFFE.

This test contains embeded character 0xFFFF.

This test contains a reference to character 0xFFFE.

This test contains a reference to character 0xFFFF.

Tests an end tag which contains an illegal space character #x3000 which follows the element name "book".

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x21

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x28

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x29

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2B

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2C

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x2F

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3B

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3C

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3D

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x3F

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5B

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5C

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5D

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x5E

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x60

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7B

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7C

Tests an element name which contains an illegal ASCII NameChar. "IllegalNameChar" is followed by #x7D

Tests an element name which has an illegal first character. An illegal first character "." is followed by "A_name-starts_with.".

Tests an element name which has an illegal first character. An illegal first character "-" is followed by "A_name-starts_with-".

Tests an element name which has an illegal first character. An illegal first character "5" is followed by "A_name-starts_with_digit".

Tests an internal general entity with an invalid value. The entity "Fullname" contains "%".

Tests an internal general entity with an invalid value. The entity "Fullname" contains the ampersand character.

Tests an internal general entity with an invalid value. The entity "Fullname" contains the double quote character in the middle.

Tests an internal general entity with an invalid value. The closing bracket (double quote) is missing with the value of the entity "FullName".

Tests an attribute with an invalid value. The value of the attribute "first" contains the character "less than".

Tests an attribute with an invalid value. The value of the attribute "first" contains the character ampersand.

Tests an attribute with an invalid value. The value of the attribute "first" contains the double quote character in the middle.

Tests an attribute with an invalid value. The closing bracket (double quote) is missing with The value of the attribute "first".

Tests an attribute with an invalid value. The value of the attribute "first" contains the character "less than".

Tests an attribute with an invalid value. The value of the attribute "first" contains the character ampersand.

Tests an attribute with an invalid value. The value of the attribute "first" contains the double quote character in the middle.

Tests an attribute with an invalid value. The closing bracket (single quote) is missing with the value of the attribute "first".

Tests SystemLiteral. The systemLiteral for the element "student" has a double quote character in the middle.

Tests SystemLiteral. The systemLiteral for the element "student" has a single quote character in the middle.

Tests SystemLiteral. The closing bracket (double quote) is missing with the systemLiteral for the element "student".

Tests SystemLiteral. The closing bracket (single quote) is missing with the systemLiteral for the element "student".

Tests PubidLiteral. The closing bracket (double quote) is missing with the value of the PubidLiteral for the entity "info".

Tests PubidLiteral. The value of the PubidLiteral for the entity "info" has a single quote character in the middle..

Tests PubidLiteral. The closing bracket (single quote) is missing with the value of the PubidLiteral for the entity "info".

Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character "{".

Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character "~".

Tests PubidChar. The pubidChar of the PubidLiteral for the entity "info" contains the character double quote in the middle.

Tests an element with an illegal NameStartChar: #x300

Tests an element with an illegal NameStartChar: #0x333

Tests an element with an illegal NameStartChar: #0x369

Tests an element with an illegal NameStartChar: #0x37E

Tests an element with an illegal NameStartChar: #0x2000

Tests an element with an illegal NameStartChar: #0x2001

Tests an element with an illegal NameStartChar: #0x2002

Tests an element with an illegal NameStartChar: #0x2005

Tests an element with an illegal NameStartChar: #0x200B

Tests an element with an illegal NameStartChar: #0x200E

Tests an element with an illegal NameStartChar: #0x200F

Tests an element with an illegal NameStartChar: #0x2069

Tests an element with an illegal NameStartChar: #0x2190

Tests an element with an illegal NameStartChar: #0x23FF

Tests an element with an illegal NameStartChar: #0x280F

Tests an element with an illegal NameStartChar: #0x2A00

Tests an element with an illegal NameStartChar: #0x2EDC

Tests an element with an illegal NameStartChar: #0x2B00

Tests an element with an illegal NameStartChar: #0x2BFF

Tests an element with an illegal NameStartChar: #0x3000

Tests an element with an illegal NameStartChar: #0xD800

Tests an element with an illegal NameStartChar: #0xD801

Tests an element with an illegal NameStartChar: #0xDAFF

Tests an element with an illegal NameStartChar: #0xDFFF

Tests an element with an illegal NameStartChar: #0xEFFF

Tests an element with an illegal NameStartChar: #0xF1FF

Tests an element with an illegal NameStartChar: #0xF8FF

Tests an element with an illegal NameStartChar: #0xFFFFF

Tests an element with an illegal NameChar: #xB8

Tests an element with an illegal NameChar: #0xA1

Tests an element with an illegal NameChar: #0xAF

Tests an element with an illegal NameChar: #0x37E

Tests an element with an illegal NameChar: #0x2000

Tests an element with an illegal NameChar: #0x2001

Tests an element with an illegal NameChar: #0x2002

Tests an element with an illegal NameChar: #0x2005

Tests an element with an illegal NameChar: #0x200B

Tests an element with an illegal NameChar: #0x200E

Tests an element with an illegal NameChar: #0x2038

Tests an element with an illegal NameChar: #0x2041

Tests an element with an illegal NameChar: #0x2190

Tests an element with an illegal NameChar: #0x23FF

Tests an element with an illegal NameChar: #0x280F

Tests an element with an illegal NameChar: #0x2A00

Tests an element with an illegal NameChar: #0xFDD0

Tests an element with an illegal NameChar: #0xFDEF

Tests an element with an illegal NameChar: #0x2FFF

Tests an element with an illegal NameChar: #0x3000

Tests an element with an illegal NameChar: #0xD800

Tests an element with an illegal NameChar: #0xD801

Tests an element with an illegal NameChar: #0xDAFF

Tests an element with an illegal NameChar: #0xDFFF

Tests an element with an illegal NameChar: #0xEFFF

Tests an element with an illegal NameChar: #0xF1FF

Tests an element with an illegal NameChar: #0xF8FF

Tests an element with an illegal NameChar: #0xFFFFF

Tests an element with an illegal Name containing #0x0B

Tests an element with an illegal Name containing #0x300

Tests an element with an illegal Name containing #0x36F

Tests an element with an illegal Name containing #0x203F

Tests an element with an illegal Name containing #x2040

Tests an element with an illegal Name containing #0xB7

Has a "long s" in a name, legal in XML 1.1, illegal in XML 1.0 thru 4th edition

Has a Byzantine Musical Symbol Kratimata in a name, legal in XML 1.1, illegal in XML 1.0 thru 4th edition

Has the last legal namechar in XML 1.1, illegal in XML 1.0 thru 4th edition

Has the first character after the last legal namechar in XML 1.1, illegal in both XML 1.0 and 1.1

Has the first character after the last legal namechar in XML 1.1, illegal in both XML 1.0 and 1.1

Tests an element with an illegal NameStartChar: #0x333

Tests an element with an illegal NameStartChar: #0x369

Tests an element with an illegal NameStartChar: #0x37E

Tests an element with an illegal NameStartChar: #0x2000

Tests an element with an illegal NameStartChar: #0x2001

Tests an element with an illegal NameStartChar: #0x2002

Tests an element with an illegal NameStartChar: #0x2005

Tests an element with an illegal NameStartChar: #0x200B

Tests an element with an illegal NameStartChar: #0x200E

Tests an element with an illegal NameStartChar: #0x200F

Tests an element with an illegal NameStartChar: #0x2069

Tests an element with an illegal NameStartChar: #0x2190

Tests an element with an illegal NameStartChar: #0x23FF

Tests an element with an illegal NameStartChar: #0x280F

Tests an element with an illegal NameStartChar: #0x2A00

Tests an element with an illegal NameStartChar: #0x2EDC

Tests an element with an illegal NameStartChar: #0x2B00

Tests an element with an illegal NameStartChar: #0x2BFF

Tests an element with an illegal NameStartChar: #0x3000

Tests an element with an illegal NameStartChar: #0xD800

Tests an element with an illegal NameStartChar: #0xD801

Tests an element with an illegal NameStartChar: #0xDAFF

Tests an element with an illegal NameStartChar: #0xDFFF

Tests an element with an illegal NameStartChar: #0xEFFF

Tests an element with an illegal NameStartChar: #0xF1FF

Tests an element with an illegal NameStartChar: #0xF8FF

Tests an element with an illegal NameStartChar: #0xFFFFF

Tests an element with an illegal NameChar: #xB8

Tests an element with an illegal NameChar: #0xA1

Tests an element with an illegal NameChar: #0xAF

Tests an element with an illegal NameChar: #0x37E

Tests an element with an illegal NameChar: #0x2000

Tests an element with an illegal NameChar: #0x2001

Tests an element with an illegal NameChar: #0x2002

Tests an element with an illegal NameChar: #0x2005

Tests an element with an illegal NameChar: #0x200B

Tests an element with an illegal NameChar: #0x200E

Tests an element with an illegal NameChar: #0x2038

Tests an element with an illegal NameChar: #0x2041

Tests an element with an illegal NameChar: #0x2190

Tests an element with an illegal NameChar: #0x23FF

Tests an element with an illegal NameChar: #0x280F

Tests an element with an illegal NameChar: #0x2A00

Tests an element with an illegal NameChar: #0xFDD0

Tests an element with an illegal NameChar: #0xFDEF

Tests an element with an illegal NameChar: #0x2FFF

Tests an element with an illegal NameChar: #0x3000

Tests an element with an illegal NameChar: #0xD800

Tests an element with an illegal NameChar: #0xD801

Tests an element with an illegal NameChar: #0xDAFF

Tests an element with an illegal NameChar: #0xDFFF

Tests an element with an illegal NameChar: #0xEFFF

Tests an element with an illegal NameChar: #0xF1FF

Tests an element with an illegal NameChar: #0xF8FF

Tests an element with an illegal NameChar: #0xFFFFF

Tests an element with an illegal Name containing #0x0B

Tests an element with an illegal Name containing #0x300

Tests an element with an illegal Name containing #0x36F

Tests an element with an illegal Name containing #0x203F

Tests an element with an illegal Name containing #x2040

Tests an element with an illegal Name containing #0xB7

SGML-ism: attribute values must be quoted in all cases.

The quotes on both ends of an attribute value must match.

Attribute values may not contain literal '<' characters.

Attribute values may not contain literal '&' characters except as part of an entity reference.

Attribute values may not contain literal '&' characters except as part of an entity reference.

Attribute values are terminated by literal quote characters, and any entity expansion is done afterwards.

Attributes may not contain a literal "<" character; this one has one because of reference expansion.

attribute values exclude '<'

attribute values exclude '&'

quote types must match

quote types must match

cannot contain delimiting quotes

Illegal entity ref in public ID

Illegal characters in public ID

Illegal characters in public ID

Illegal characters in public ID

SGML-ism: public ID without system ID

'"' excluded

'\' excluded

entity references excluded

'>' excluded

'<' excluded

built-in entity refs excluded

Public IDs may not contain "[".

Public IDs may not contain "[".

Public IDs may not contain "[".

The public ID has a tab character, which is disallowed

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Use of illegal character within XML document.

Names may not start with "."; it's not a Letter.

Character '&#x309a;' is a CombiningChar, not a Letter, and so may not begin a name.

Name contains invalid character.

Name contains invalid character.

Name contains invalid character.

Entity references must include names, which don't begin with '.' (it's not a Letter or other name start character).

Digits are not valid name start characters.

Digits are not valid name start characters.

Character #x0E5C is not legal in XML names.

a Name cannot start with a digit

a Name cannot start with a '.'

a Name cannot start with a "-"

a Name cannot start with a CombiningChar

a Name cannot start with an Extender

Parameter entity values must use valid reference syntax; this reference is malformed.

General entity values must use valid reference syntax; this reference is malformed.

Uses '&' unquoted in an entity declaration, which is illegal syntax for an entity reference.

EntityValue excludes '%'

EntityValue excludes '&'

incomplete character reference