XML Conformance Tests

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.

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 entity holding a carriage return character reference, which must be normalized to a newline before being reported to the application.

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.

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.

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.

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.

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.

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.

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.

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

Whitespace found in CDATA sections and entity references works is treated like other optional whitespace

There is an output test associated with this input file.

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 don't get parameter entity expansion

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 may contain any legal XML characters; only the string "--" is disallowed.

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.

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 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.

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.

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.

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

There is an output test associated with this input file.

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

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 External Entity declaration.

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

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

Test demonstrates a valid SDDecl within the prolog.

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.

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.

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 Start-tags and End-tags are nomalized into single spaces.

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 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.

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 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.

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 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.

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.

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, 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, and mixed content within an element type declaration.

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.

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.

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

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.

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 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 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

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.

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 a parameter-entity reference as a keyword of a conditional section. The parameter entity must be replaced by its content before the processor decides whether to include the conditional section.

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

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

There is an output test associated with this input file.

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.

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.

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.

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.

Test demonstrates use of characters outside of normal ASCII range.

There is an output test associated with this input file.

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 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

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.

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.

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 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 a parameter entity declaration whose parameter entity definition is an ExternalID.

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.

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

There is an output test associated with this input file.

Tests use of external parsed entities with and without content.

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.

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.

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.

no prolog

Misc items after the document

valid attribute values

all valid S characters

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

various valid Name constructions

Requires at least one name.

at least one Nmtoken is required.

an invalid Nmtoken character.

valid CharData

valid comments

S after PITarget is required

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 a comment between two parameter entities.

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

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

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

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

Tests the Root Element Type VC

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 a reference to externally defined entity causes 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.

Tests the Standalone Document Declaration VC, ensuring that optional whitespace causes a validity error (even if it's CDATA whitespace).

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.

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 basic 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 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 more 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 more 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 more 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.

Elements content can be empty.

Whitespace is valid within a Start-tag.

Attributes are valid within a Start-tag.

Whitespace and Multiple 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 Attribute Value Type (declared) VC for the xml:space attribute

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

Tests the Unique Element Type Declaration VC.

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

Tests the No Duplicate Types VC

Tests the No Duplicate Types VC.

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 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.

Character data is valid element content.

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

Tests the Entity Declared VC by referring to an undefined parameter entity within an external entity.

Tests "Entity Declared" VC for a parameter entity. NOTE: there are both VCs and WFCs with this name, which is a specification issue in that it is both confusing and in some ways self-contradictory. The WFC does not apply to PEs, and even the clause which might seem to suggest it could is ruled out in this test.

valid character references

Tests the "Notation Declared" VC by using an undeclared notation name.