| A Joint Development Effort |
|
OASIS XML Conformance Subcommittee
XML 1.0 Test Suite, Second Edition
Working Draft
15 March 2001
-
This version:
-
-
Current Version:
-
-
Previous Version:
-
-
Test Archive:
-
-
OASIS XML Conformance Technical Committee:
-
-
Comments:
-
Table of Contents
-
Introduction
-
Test Matrix
-
Binary Tests
-
Output Tests
-
Test Case Descriptions
-
Valid Documents
-
Invalid Documents
-
Not-WF Documents
-
Optional Errors
-
Contributors
1. Introduction
The OASIS XML Conformance Subcommittee is concerned with
improving the quality of XML processors. The tests described in this
document provide an initial set of metrics to determine how well a
particular implementation conforms to the
W3C XML 1.0 (Second Edition) Recommendation.
The XML Conformance Test Suite is intended
to complement the W3C XML 1.0 (Second Edition) Recommendation. All interpretations
of this Recommendation are subject to confirmation by the
W3C XML Coordination
Group.
Conformance tests can be used by developers, content creators, and
users alike to increase their level of confidence in product quality. In
circumstances where interoperability is necessary, these tests can also
be used to determine that differing implementations support the same set
of features.
This report provides supporting documentation for all of the tests
contributed by members of the OASIS XML Conformance Subcommittee.
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; . Although the tests came from a variety of sources, the actual test
descriptions and references back to the specification were in many instances
added by members of this subcommittee. It is anticipated that this report
will supplement the actual tests, which are available from
http://www.oasis-open.org/committees/xml-conformance/xml-test-suite.html.
Comments/suggestions should be
forwarded to the XML Conformance Subcommittee Chair, Mary Brady
<mbrady@nist.gov>.
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 |
| 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 to ensure that the XML
processor provides the correct information.
The output of these tests is provided in one of two forms, as
described in SUN Microsystems XML
Canonical Forms. At present, the James Clark
collection provides corresponding output in First XML
Canonical Form, and the SUN Microsystems
collection provides corresponding output in Second XML
Canonical Form. When the
W3C XML Group finalizes its work on Canonical XML, these
output files will be updated.
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.
Note that the output format of this report is subject
to change. Also, since XSL does not currently support the
type of sorting rule necessary to make section numbers like
2.12 appear after 2.2, the ordering is not quite what is
desired.
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]: | 2.1 |
| Test ID: | ibm-valid-P01-ibm01v01.xml |
| 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.10 |
| Test ID: | valid-sa-084 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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, 3.3.3 |
| Test ID: | valid-sa-108 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| Collection: | IBM XML Conformance Test Suite - Production 2 |
|
Tests Char with 3 characters - 2 boundaries plus 1 in the middle - for
each range plus #x20 #x9 #xD #xA
|
| Sections [Rules]: | 2.2 [1] |
| Test ID: | o-p01pass2 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
various Misc items where they can occur
|
| Sections [Rules]: | 2.2 [2] |
| Test ID: | valid-sa-049 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 [12] |
| Test ID: | valid-sa-100 |
| 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 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
valid public IDs.
|
| Sections [Rules]: | 2.3 [4] |
| Test ID: | valid-sa-012 |
| 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 |
| 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 |
| 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 |
| 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 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
various satisfaction of an NMTOKENS attribute value.
|
| Sections [Rules]: | 2.3 [9] |
| Test ID: | o-p09pass1 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that PubidChar can be used for element content.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.3 4.1 [10] [69] |
| Test ID: | valid-not-sa-023 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of a parameter entity reference within an attribute list declaration.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.4 |
| Test ID: | ibm-valid-P14-ibm14v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 14 |
|
Testing CharData with empty string
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.4 |
| Test ID: | ibm-valid-P14-ibm14v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 14 |
|
Testing CharData with white space character
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.4 |
| Test ID: | ibm-valid-P14-ibm14v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 14 |
|
Testing CharData with a general text string
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.4 2.5 2.6 2.7 [15] [16] [18] |
| Test ID: | o-p43pass1 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid use of character data, comments, processing instructions and CDATA sections within the start and end tag.
|
| Sections [Rules]: | 2.4 3.1 [14] [43] |
| Test ID: | valid-sa-048 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that character data is valid element content.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.4 3.1 [43] |
| Test ID: | valid-sa-008 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates character references can be used for element content.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 |
| Test ID: | valid-sa-119 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Comments may contain any legal XML characters;
only the string "--" is disallowed.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 |
| Test ID: | ibm-valid-P15-ibm15v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 15 |
|
Tests empty comment
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 |
| Test ID: | ibm-valid-P15-ibm15v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 15 |
|
Tests comment with regular text
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 |
| Test ID: | ibm-valid-P15-ibm15v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 15 |
|
Tests comment with one dash inside
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 |
| Test ID: | ibm-valid-P15-ibm15v04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 15 |
|
Tests comment with more comprehensive content
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 [15] |
| Test ID: | dtd01 |
| Collection: | Sun Microsystems XML Tests |
|
Comments don't get parameter entity expansion
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 3.1 [15] [43] |
| Test ID: | valid-sa-021 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that comments are valid element content.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.5 3.1 [15] [43] |
| Test ID: | valid-sa-022 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.6 |
| Test ID: | ibm-valid-P16-ibm16v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 16 |
|
Tests PI definition with only PItarget name and nothing else
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.6 |
| Test ID: | ibm-valid-P16-ibm16v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 16 |
|
Tests PI definition with only PItarget name and a white space
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.6 |
| Test ID: | ibm-valid-P16-ibm16v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 16 |
|
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.
|
| Sections [Rules]: | 2.6 |
| Test ID: | ibm-valid-P17-ibm17v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 17 |
|
Tests PITarget name
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.6 [15] |
| Test ID: | valid-sa-037 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.6 [15] |
| Test ID: | valid-sa-038 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.6 [16] |
| Test ID: | valid-sa-036 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a valid processing instruction.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.6 [16] |
| Test ID: | valid-sa-039 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.6 2.10 [16] |
| Test ID: | valid-sa-055 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.6 2.10 [16] |
| Test ID: | valid-sa-098 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.6 3.1 [16] [43] |
| Test ID: | valid-sa-016 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that Processing Instructions are valid element content.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.6 3.1 [16] [43] |
| Test ID: | valid-sa-017 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.7 |
| Test ID: | valid-not-sa-031 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.7 |
| Test ID: | ibm-valid-P18-ibm18v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 18 |
|
Tests CDSect with CDStart CData CDEnd
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.7 |
| Test ID: | ibm-valid-P19-ibm19v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 19 |
|
Tests CDStart
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.7 |
| Test ID: | ibm-valid-P20-ibm20v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 20 |
|
Tests CDATA with empty string
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.7 |
| Test ID: | ibm-valid-P20-ibm20v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 20 |
|
Tests CDATA with regular content
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.7 |
| Test ID: | ibm-valid-P21-ibm21v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 21 |
|
Tests CDEnd
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.7 [20] |
| Test ID: | valid-sa-114 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.7 3.1 [18] [43] |
| Test ID: | valid-sa-018 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that CDATA sections are valid element content.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.7 3.1 [18] [43] |
| Test ID: | valid-sa-019 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.7 3.1 [18] [43] |
| Test ID: | valid-sa-020 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P22-ibm22v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 22 |
|
Tests prolog with XMLDecl and doctypedecl
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P22-ibm22v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 22 |
|
Tests prolog with doctypedecl
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P22-ibm22v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 22 |
|
Tests prolog with Misc doctypedecl
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P22-ibm22v04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 22 |
|
Tests prolog with doctypedecl Misc
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P22-ibm22v05.xml |
| Collection: | IBM XML Conformance Test Suite - Production 22 |
|
Tests prolog with XMLDecl Misc doctypedecl
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P22-ibm22v06.xml |
| Collection: | IBM XML Conformance Test Suite - Production 22 |
|
Tests prolog with XMLDecl doctypedecl Misc
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P22-ibm22v07.xml |
| Collection: | IBM XML Conformance Test Suite - Production 22 |
|
Tests prolog with XMLDecl Misc doctypedecl Misc
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P23-ibm23v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 23 |
|
Tests XMLDecl with VersionInfo only
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P23-ibm23v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 23 |
|
Tests XMLDecl with VersionInfo EncodingDecl
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P23-ibm23v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 23 |
|
Tests XMLDecl with VersionInfo SDDecl
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P23-ibm23v04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 23 |
|
Tests XMLDecl with VerstionInfo and a trailing whitespace char
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P23-ibm23v05.xml |
| Collection: | IBM XML Conformance Test Suite - Production 23 |
|
Tests XMLDecl with VersionInfo EncodingDecl SDDecl
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P23-ibm23v06.xml |
| Collection: | IBM XML Conformance Test Suite - Production 23 |
|
Tests XMLDecl with VersionInfo EncodingDecl SDDecl and a trailing whitespace
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P24-ibm24v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 24 |
|
Tests VersionInfo with single quote
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P24-ibm24v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 24 |
|
Tests VersionInfo with double quote
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P25-ibm25v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 25 |
|
Tests EQ with =
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P25-ibm25v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 25 |
|
Tests EQ with = and spaces on both sides
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P25-ibm25v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 25 |
|
Tests EQ with = and space in front of it
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P25-ibm25v04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 25 |
|
Tests EQ with = and space after it
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P26-ibm26v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 26 |
|
Tests VersionNum 1.0
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P27-ibm27v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 27 |
|
Tests Misc with comment
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P27-ibm27v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 27 |
|
Tests Misc with PI
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P27-ibm27v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 27 |
|
Tests Misc with white spaces
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P28-ibm28v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 28 |
|
Tests doctypedecl with internal DTD only
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P28-ibm28v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 28 |
|
Tests doctypedecl with external subset and combinations of different markup
declarations and PEReferences
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P29-ibm29v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 29 |
|
Tests markupdecl with combinations of elementdecl, AttlistDecl,EntityDecl,
NotationDecl, PI and comment
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P29-ibm29v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 29 |
|
Tests WFC: PE in internal subset as a positive test
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P30-ibm30v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 30 |
|
Tests extSubset with extSubsetDecl only in the dtd file
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P30-ibm30v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 30 |
|
Tests extSubset with TextDecl and extSubsetDecl in the dtd file
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 |
| Test ID: | ibm-valid-P31-ibm31v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 31 |
|
Tests extSubsetDecl with combinations of markupdecls, conditionalSects,
PEReferences and white spaces
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8, 4.1 [69] |
| Test ID: | valid-not-sa-024 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Constructs an <!ATTLIST...> declaration from several PEs.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 [22] |
| Test ID: | o-p22pass4 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
XML decl and doctypedecl
|
| Sections [Rules]: | 2.8 [22] |
| Test ID: | o-p22pass5 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
just doctypedecl
|
| Sections [Rules]: | 2.8 [22] |
| Test ID: | o-p22pass6 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
S between decls is not required
|
| Sections [Rules]: | 2.8 [23] |
| Test ID: | valid-sa-033 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that both a EncodingDecl and SDDecl are valid within the prolog.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 [24] |
| Test ID: | valid-sa-028 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a valid prolog that uses double quotes as delimeters around the VersionNum.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 [24] |
| Test ID: | valid-sa-029 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a valid prolog that uses single quotes as delimters around the VersionNum.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.8 [25] |
| Test ID: | valid-sa-030 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 2.8 [29] |
| Test ID: | o-p29pass1 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid types of markupdecl.
|
| Sections [Rules]: | 2.8 [31] |
| Test ID: | o-p31pass1 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
external subset can be empty
|
| Sections [Rules]: | 2.8 3.4 4.2.2 [31] [62] [63] [75] |
| Test ID: | o-p31pass2 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid doctypedecl with EXternalID as Enternal Entity. The external entity contains a parameter entity reference and condtional sections.
|
| Sections [Rules]: | 2.8 4.1 [28] [69] |
| Test ID: | o-p28pass3 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid doctypedecl with Parameter entity reference. The declaration of a parameter entity must precede any reference to it.
|
| Sections [Rules]: | 2.8 4.1 [28] [69] |
| Test ID: | o-p28pass5 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid doctypedecl with ExternalID as an External Entity. A parameter entity reference is also used.
|
| Sections [Rules]: | 2.8 4.2.2 [28] [75] |
| Test ID: | o-p28pass4 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid doctypedecl with ExternalID as an External Entity declaration.
|
| Sections [Rules]: | 2.8 4.2.2 [30] [75] |
| Test ID: | o-p30pass1 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid doctypedecl with ExternalID as an External Entity. The external entity has an element declaration.
|
| Sections [Rules]: | 2.8 4.2.2 4.3.1 [30] [75] [77] |
| Test ID: | o-p30pass2 |
| Collection: | OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid doctypedecl with ExternalID as an Enternal Entity. The external entity begins with a Text Declaration.
|
| Sections [Rules]: | 2.9 |
| Test ID: | not-sa01 |
| Collection: | Sun Microsystems XML Tests |
|
A non-standalone document is valid if declared as such.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.9 |
| Test ID: | not-sa02 |
| Collection: | Sun Microsystems XML Tests |
|
A non-standalone document is valid if declared as such.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.9 |
| Test ID: | not-sa03 |
| Collection: | Sun Microsystems XML Tests |
|
A non-standalone document is valid if declared as such.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.9 |
| Test ID: | not-sa04 |
| Collection: | Sun Microsystems XML Tests |
|
A non-standalone document is valid if declared as such.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.9 |
| Test ID: | ibm-valid-P32-ibm32v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 32 |
|
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.
|
| Sections [Rules]: | 2.9 |
| Test ID: | ibm-valid-P32-ibm32v02.xml |
| Collection: | IBM XML Conformance Test Suite - Production 32 |
|
Tests VC: Standalone Document Declaration with external entity reference
and standalone is no
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.9 |
| Test ID: | ibm-valid-P32-ibm32v03.xml |
| Collection: | IBM XML Conformance Test Suite - Production 32 |
|
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.
|
| Sections [Rules]: | 2.9 |
| Test ID: | ibm-valid-P32-ibm32v04.xml |
| Collection: | IBM XML Conformance Test Suite - Production 32 |
|
Tests VC: Standalone Document Declaration with whitespace in mixed content
and standalone is no
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.9 [32] |
| Test ID: | valid-sa-032 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a valid SDDecl within the prolog.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 2.9 [32] |
| Test ID: | sa01 |
| Collection: | Sun Microsystems XML Tests |
|
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.
|
| Sections [Rules]: | 2.9 [32] |
| Test ID: | sa02 |
| Collection: | Sun Microsystems XML Tests |
|
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.
|
| Sections [Rules]: | 2.9 [32] |
| Test ID: | sa03 |
| Collection: | Sun Microsystems XML Tests |
|
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.
|
| Sections [Rules]: | 2.9 [32] |
| Test ID: | sa04 |
| Collection: | Sun Microsystems XML Tests |
|
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.
|
| Sections [Rules]: | 2.9 [32] |
| Test ID: | sa05 |
| Collection: | Sun Microsystems XML Tests |
|
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.
|
| Sections [Rules]: | 3 |
| Test ID: | element |
| Collection: | Sun Microsystems XML Tests |
|
Tests clauses 1, 3, and 4 of the Element Valid
validity constraint.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 3 |
| Test ID: | ibm-valid-P39-ibm39v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 39 |
|
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.
|
| Sections [Rules]: | 3.1 |
| Test ID: | ibm-valid-P40-ibm40v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 40 |
|
Tests STag with possible combinations of its fields, also tests WFC:
Unique Att Spec.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 3.1 |
| Test ID: | ibm-valid-P41-ibm41v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 41 |
|
Tests Attribute with Name Eq AttValue and VC: Attribute Value Type
There is an output test associated with this
input file.
|
| Sections [Rules]: | 3.1 |
| Test ID: | ibm-valid-P42-ibm42v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 42 |
|
Tests ETag with possible combinations of its fields
There is an output test associated with this
input file.
|
| Sections [Rules]: | 3.1 |
| Test ID: | ibm-valid-P43-ibm43v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 43 |
|
Tests content with all possible constructs: element, CharData, Reference,
CDSect, Comment
There is an output test associated with this
input file.
|
| Sections [Rules]: | 3.1 |
| Test ID: | ibm-valid-P44-ibm44v01.xml |
| Collection: | IBM XML Conformance Test Suite - Production 44 |
|
Tests EmptyElemTag with possible combinations of its fields
There is an output test associated with this
input file.
|
| Sections [Rules]: | 3.1 [40] |
| Test ID: | valid-sa-002 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that whitespace is permitted after the tag name in a Start-tag.
There is an output test associated with this
input file.
|
| Sections [Rules]: | 3.1 [40] |
| Test ID: | valid-sa-005 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
| Sections [Rules]: | 3.1 [40] |
| Test ID: | valid-sa-010 |
| Collection: | James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that whitespace is valid after the Attribute in a Start-tag.
There is an output test associated with this
input file.
|
