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 provides supporting documentation for all the tests included in the test suite. Sources 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 Namespaces 1.1 test suite 14 Feb 2003; .

2. Test Matrix

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

2.1 Binary 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:

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

**Basic XML Parsing Test Matrix**
Test Document Type v. Parser Type
	Nonvalidating		Validating
	External Entities Ignored (3 cases)	External Entities Read	Validating
Valid Documents	accept	accept	accept
Invalid Documents	accept	accept	reject
Non-WF Documents	reject	reject	reject
WF Errors tied to External Entity	accept (varies)	reject	reject
Documents with Optional Errors	(not specified)	(not specified)	(not specified)

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.

2.2 Output Tests

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.

3. Test Case Descriptions

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.

3.1 Valid XML Documents

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.

Sections [Rules]:	1
Test ID:	rmt-ns10-007
RECOMMENDATION:	NS1.0
Collection:	Richard Tobin's XML Namespaces 1.0 test suite 14 Feb 2003

Namespace inequality test: different capitalization

Sections [Rules]:	1
Test ID:	rmt-ns10-008
RECOMMENDATION:	NS1.0
Collection:	Richard Tobin's XML Namespaces 1.0 test suite 14 Feb 2003

Namespace inequality test: different escaping

Sections [Rules]:	2
Test ID:	rmt-ns10-001
RECOMMENDATION:	NS1.0
Collection:	Richard Tobin's XML Namespaces 1.0 test suite 14 Feb 2003

Namespace name test: a perfectly good http URI

Sections [Rules]:	2
Test ID:	rmt-ns10-002
RECOMMENDATION:	NS1.0
Collection:	Richard Tobin's XML Namespaces 1.0 test suite 14 Feb 2003

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

Sections [Rules]:	2
Test ID:	rmt-ns10-003
RECOMMENDATION:	NS1.0
Collection:	Richard Tobin's XML Namespaces 1.0 test suite 14 Feb 2003

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

Sections [Rules]:	2.1
Test ID:	ibm-valid-P01-ibm01v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 1

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

There is an output test associated with this input file.

Sections [Rules]:	2.1
Test ID:	rmt-ns11-001
RECOMMENDATION:	NS1.1
Collection:	Richard Tobin's XML Namespaces 1.1 test suite 14 Feb 2003

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

Sections [Rules]:	2.1
Test ID:	rmt-ns11-006
RECOMMENDATION:	NS1.1
Collection:	Richard Tobin's XML Namespaces 1.1 test suite 14 Feb 2003

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

Sections [Rules]:	2.10
Test ID:	valid-sa-084
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.10
Test ID:	valid-sa-093
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11
Test ID:	valid-sa-116
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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

There is an output test associated with this input file.

Sections [Rules]:	2.11
Test ID:	valid-ext-sa-001
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11
Test ID:	valid-ext-sa-002
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11
Test ID:	valid-ext-sa-004
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11
Test ID:	valid-ext-sa-009
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v01.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v02.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v03.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v04.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v05.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v06.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v07.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v08.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	ibm-1-1-valid-P03-ibm03v09.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 3

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.

Sections [Rules]:	2.11
Test ID:	rmt-022
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-023
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-024
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-025
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-026
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-027
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-028
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-029
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-031
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-033
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-047
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11
Test ID:	rmt-049
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.11, 3.3.3
Test ID:	valid-sa-108
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11, 4.5
Test ID:	valid-sa-068
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11 3.2.1 3.2.2 4.2.2 [48] [51] [75]
Test ID:	valid-ext-sa-006
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.11 4.2.2 [75]
Test ID:	valid-ext-sa-011
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.12
Test ID:	ibm-valid-P33-ibm33v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 33

Tests LanguageID with Langcode - Subcode

There is an output test associated with this input file.

Sections [Rules]:	2.12
Test ID:	ibm-valid-P34-ibm34v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 34

Duplicate Test as ibm33v01.xml

There is an output test associated with this input file.

Sections [Rules]:	2.12
Test ID:	ibm-valid-P35-ibm35v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 35

Tests ISO639Code

There is an output test associated with this input file.

Sections [Rules]:	2.12
Test ID:	ibm-valid-P36-ibm36v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 36

Tests IanaCode

There is an output test associated with this input file.

Sections [Rules]:	2.12
Test ID:	ibm-valid-P37-ibm37v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 37

Tests UserCode

There is an output test associated with this input file.

Sections [Rules]:	2.12
Test ID:	ibm-valid-P38-ibm38v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 38

Tests SubCode

There is an output test associated with this input file.

Sections [Rules]:	2.12 [35]
Test ID:	v-lang01
RECOMMENDATION:	XML1.0
Collection:	Sun Microsystems XML Tests

Tests a lowercase ISO language code.

There is an output test associated with this input file.

Sections [Rules]:	2.12 [35]
Test ID:	v-lang02
RECOMMENDATION:	XML1.0
Collection:	Sun Microsystems XML Tests

Tests a ISO language code with a subcode.

There is an output test associated with this input file.

Sections [Rules]:	2.12 [35]
Test ID:	v-lang05
RECOMMENDATION:	XML1.0
Collection:	Sun Microsystems XML Tests

Tests an uppercase ISO language code.

There is an output test associated with this input file.

Sections [Rules]:	2.12 [36]
Test ID:	v-lang03
RECOMMENDATION:	XML1.0
Collection:	Sun Microsystems XML Tests

Tests a IANA language code with a subcode.

There is an output test associated with this input file.

Sections [Rules]:	2.12 [37]
Test ID:	v-lang04
RECOMMENDATION:	XML1.0
Collection:	Sun Microsystems XML Tests

Tests a user language code with a subcode.

There is an output test associated with this input file.

Sections [Rules]:	2.12 [37]
Test ID:	v-lang06
RECOMMENDATION:	XML1.0
Collection:	Sun Microsystems XML Tests

Tests a user language code.

There is an output test associated with this input file.

Sections [Rules]:	2.2
Test ID:	ibm-valid-P02-ibm02v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 2

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

Sections [Rules]:	2.2
Test ID:	ibm-1-1-valid-P02-ibm02v01.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 2

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

Sections [Rules]:	2.2
Test ID:	rmt-010
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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

There is an output test associated with this input file.

Sections [Rules]:	2.2
Test ID:	rmt-012
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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

There is an output test associated with this input file.

Sections [Rules]:	2.2
Test ID:	rmt-040
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.2,4.1
Test ID:	ibm-1-1-valid-P02-ibm02v02.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 2

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

Sections [Rules]:	2.2,4.1
Test ID:	ibm-1-1-valid-P02-ibm02v03.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 2

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

Sections [Rules]:	2.2,4.1
Test ID:	ibm-1-1-valid-P02-ibm02v04.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 2

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

Sections [Rules]:	2.2,4.1
Test ID:	ibm-1-1-valid-P02-ibm02v05.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 2

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

Sections [Rules]:	2.2,4.1
Test ID:	ibm-1-1-valid-P02-ibm02v06.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 2

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

Sections [Rules]:	2.2 [1]
Test ID:	o-p01pass2
RECOMMENDATION:	XML1.0
Collection:	OASIS/NIST TESTS, 1-Nov-1998

various Misc items where they can occur

Sections [Rules]:	2.2 [2]
Test ID:	valid-sa-049
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.2 [2]
Test ID:	valid-sa-050
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.2 [2]
Test ID:	valid-sa-051
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.2 [2]
Test ID:	valid-sa-052
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P03-ibm03v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 3

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

Sections [Rules]:	2.3
Test ID:	ibm-valid-P09-ibm09v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 9

Empty EntityValue is legal

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P09-ibm09v02.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 9

Tests a normal EnitityValue

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P09-ibm09v03.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 9

Tests EnitityValue referencing a Parameter Entity

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P09-ibm09v04.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 9

Tests EnitityValue referencing a General Entity

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P09-ibm09v05.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 9

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.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

Tests empty AttValue with double quotes as the delimiters

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v02.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

Tests empty AttValue with single quotes as the delimiters

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v03.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

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

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v04.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

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

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v05.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

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

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v06.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

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

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v07.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

testing AttValue with mixed references and text content in double quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P10-ibm10v08.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 10

testing AttValue with mixed references and text content in single quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P11-ibm11v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 11

Tests empty systemliteral using the double quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P11-ibm11v02.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 11

Tests empty systemliteral using the single quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P11-ibm11v03.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 11

Tests regular systemliteral using the single quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P11-ibm11v04.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 11

Tests regular systemliteral using the double quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P12-ibm12v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 12

Tests empty systemliteral using the double quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P12-ibm12v02.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 12

Tests empty systemliteral using the single quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P12-ibm12v03.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 12

Tests regular systemliteral using the double quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P12-ibm12v04.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 12

Tests regular systemliteral using the single quotes

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-valid-P13-ibm13v01.xml
RECOMMENDATION:	XML1.0
Collection:	IBM XML Conformance Test Suite - Production 13

Testing PubidChar with all legal PubidChar in a PubidLiteral

There is an output test associated with this input file.

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P04-ibm04v01.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 4

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

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P04-ibm04av01.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 4a

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

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P05-ibm05v01.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 5

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

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P05-ibm05v02.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 5

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

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P05-ibm05v03.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 5

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

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P05-ibm05v04.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 5

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

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P05-ibm05v05.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 5

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

Sections [Rules]:	2.3
Test ID:	ibm-1-1-valid-P047-ibm07v01.xml
RECOMMENDATION:	XML1.1
Collection:	IBM XML Conformance Test Suite - Production 7

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

Sections [Rules]:	2.3
Test ID:	rmt-034
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.3
Test ID:	rmt-035
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.3
Test ID:	rmt-050
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.3
Test ID:	rmt-051
RECOMMENDATION:	XML1.1
Collection:	Richard Tobin's XML 1.1 test suite 13 Feb 2003

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.

Sections [Rules]:	2.3
Test ID:	rmt-ns11-002
RECOMMENDATION:	NS1.1
Collection:	Richard Tobin's XML Namespaces 1.1 test suite 14 Feb 2003

Namespace inequality test: different escaping of non-ascii letter

Sections [Rules]:	2.3 [12]
Test ID:	valid-sa-100
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.3 [12]
Test ID:	o-p12pass1
RECOMMENDATION:	XML1.0
Collection:	OASIS/NIST TESTS, 1-Nov-1998

valid public IDs.

Sections [Rules]:	2.3 [4]
Test ID:	valid-sa-012
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.3 [5]
Test ID:	valid-sa-063
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.3 [6]
Test ID:	o-p06pass1
RECOMMENDATION:	XML1.0
Collection:	OASIS/NIST TESTS, 1-Nov-1998

various satisfactions of the Names production in a NAMES attribute

Sections [Rules]:	2.3 [7]
Test ID:	o-p07pass1
RECOMMENDATION:	XML1.0
Collection:	OASIS/NIST TESTS, 1-Nov-1998

various valid Nmtoken 's in an attribute list declaration.

Sections [Rules]:	2.3 [8]
Test ID:	o-p08pass1
RECOMMENDATION:	XML1.0
Collection:	OASIS/NIST TESTS, 1-Nov-1998

various satisfaction of an NMTOKENS attribute value.

Sections [Rules]:	2.3 [9]
Test ID:	o-p09pass1
RECOMMENDATION:	XML1.0
Collection:	OASIS/NIST TESTS, 1-Nov-1998

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

Sections [Rules]:	2.3 2.10
Test ID:	valid-sa-092
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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

There is an output test associated with this input file.

Sections [Rules]:	2.3 3.1 [10][40][41]
Test ID:	valid-sa-109
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

Test demonstrates that an attribute can have a null value.

There is an output test associated with this input file.

Sections [Rules]:	2.3 3.1 [13] [40]
Test ID:	valid-sa-013
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.3 3.1 [13] [40]
Test ID:	valid-sa-014
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.3 3.1 [13] [40]
Test ID:	valid-sa-015
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

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.

Sections [Rules]:	2.3 3.1 [43]
Test ID:	valid-sa-009
RECOMMENDATION:	XML1.0
Collection:	James Clark XMLTEST cases, 18-Nov-1998

Test demonstrates that PubidChar can be used for element content.

There is

XML W3C Conformance Test Suite

10 December 2003

Table of Contents

1. Introduction

2. Test Matrix

2.1 Binary Tests

2.2 Output Tests

3. Test Case Descriptions

3.1 Valid XML Documents