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.

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.

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.

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.

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.

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.

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.

Namespace inequality test: different escaping of non-ascii letter

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.

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.

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.

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.

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

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

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.

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.

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

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.

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

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

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.

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

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.

Tests all AttlistDecl and AttDef Patterns in P52 and P53

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

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.

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.