[an error occurred while processing this directive]
XML Conformance Tests
OASIS XML Conformance Subcommittee
Working Draft
12 July 1999
-
This version (normative at publishing time):
-
-
Current Normative Version:
-
-
Non-normative Renditions:
-
-
Available Stylesheets:
-
-
Comments:
-
-
Public Information Page:
-
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 Recommendation.
It is anticipated that this test suite will grow over time, and will
be expanded to test additional XML functionality as the set of XML
Recommendations evolve. The XML Conformance Test Suite is intended
to complement the W3C XML 1.0 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; . 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/xmltest/.
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 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 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 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.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, 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 entity holding a carriage return character
reference, which must be normalized to a newline before being
reported to the application.
There is an output test associated with this
input file.
|
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 |
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 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 [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 [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.
|
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 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 2.7 [18] |
Test ID:
|
empty |
Collection:
|
Sun Microsystems XML Tests |
|
Whitespace found in CDATA sections and entity references
works is treated like other optional whitespace
There is an output test associated with this
input file.
|
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 [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.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.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 [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.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.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 [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 |
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 [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.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.
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
valid-sa-011 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates mutliple Attibutes within the Start-tag.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.1 [40] [42] |
Test ID:
|
valid-sa-054 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
valid-sa-104 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
valid-sa-004 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a valid attribute specification within a Start-tag.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
valid-sa-006 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
valid-sa-003 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that whitespace is permitted after the tag name in an End-tag.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
valid-sa-023 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that Entity References are valid element content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
valid-sa-047 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that extra whitespace is normalized into single space character.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.1 [43] [44] |
Test ID:
|
o-p28pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Empty-element tag must be used for element which are declared EMPTY.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
valid-sa-034 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the correct syntax for an Empty element tag.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
valid-sa-035 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that whitespace is permissible after the name in an Empty element tag.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
valid-sa-044 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.1 4.1 [43] [66] |
Test ID:
|
valid-sa-024 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.1 4.1 [43] [68] |
Test ID:
|
valid-ext-sa-003 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.1 4.6 [43] |
Test ID:
|
valid-sa-007 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates numeric character references can be used for element content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
valid-sa-057 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates an element content model whose element can occur zero or more times.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.2.1 [48][49] |
Test ID:
|
valid-sa-112 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates shows the use of content particles within the element content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.2.1 [50] |
Test ID:
|
valid-sa-081 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.2.1 4.2.2 [48] [75] |
Test ID:
|
valid-ext-sa-005 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
valid-sa-001 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates an Element Type Declaration with Mixed Content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
dtd00 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests parsing of alternative forms of text-only mixed
content declaration.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid Mixed contentspec's.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
o-p45pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid element declarations
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
valid-sa-025 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
valid-sa-026 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates an Element Type Declaration and that EMPTY is a valid contentspec.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
valid-sa-027 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates an Element Type Declaration and that ANY is a valid contenspec.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.2 3.2.1 [45] [46] [47] |
Test ID:
|
o-p47pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.2 3.2.1 [45] [46] [47] |
Test ID:
|
o-p48pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.2 3.2.1 [45] [46] [47] |
Test ID:
|
o-p49pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.2 3.2.1 [45] [46] [47] |
Test ID:
|
o-p50pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.2 3.2.1 3.2.2 [45] [46] [47] [51] |
Test ID:
|
o-p46pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid use of contentspec, element content models, and mixed content within an element type declaration.
|
Sections [Rules]:
|
3.2 3.3 [46] [53] |
Test ID:
|
valid-sa-059 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3 |
Test ID:
|
valid-sa-043 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3 |
Test ID:
|
valid-sa-097 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.1 [54] |
Test ID:
|
o-p54pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
the three kinds of attribute types
|
Sections [Rules]:
|
3.3.1 [55] |
Test ID:
|
o-p55pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
StringType = "CDATA"
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
o-p56pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
the 7 tokenized attribute types
|
Sections [Rules]:
|
3.3.1 [57] |
Test ID:
|
o-p57pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
enumerated types are NMTOKEN or NOTATION lists
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
NOTATION enumeration has on or more items
|
Sections [Rules]:
|
3.3.1 [59] |
Test ID:
|
v-sgml01 |
Collection:
|
Sun Microsystems XML Tests |
|
XML permits token reuse, while SGML does not.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.1 [59] |
Test ID:
|
o-p59pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
NMTOKEN enumerations haveon or more items
|
Sections [Rules]:
|
3.3.1 4.1 [54] [66] |
Test ID:
|
valid-sa-041 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.1 4.1 [54] [66] |
Test ID:
|
valid-sa-042 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.1 4.1 [54] [66] |
Test ID:
|
valid-sa-056 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
valid-sa-076 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
valid-sa-090 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
valid-sa-091 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.2 [60] |
Test ID:
|
required00 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the #REQUIRED attribute declaration syntax, and
the associated validity constraint.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.2 [60] |
Test ID:
|
o-p60pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
the four types of default values
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-058 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-095 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-096 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-102 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that a CDATA attribute can pass a double quote as its value.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-103 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an attribute can pass a less than sign as its value.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-105 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-106 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
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.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-107 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Basically an output test, this requires a CDATA attribute
with a return character to be passed through as one space.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-110 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Basically an output test, this requires that a CDATA
attribute with a CRLF be normalized to one space.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-111 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character references expanding to spaces doesn't affect
treatment of attributes.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-sa-115 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an entity reference is processed by recursively processing the replacement text of the entity.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3.3 |
Test ID:
|
valid-ext-sa-013 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that whitespace is handled by adding a single whitespace to the normalized value in the attribute list.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
valid-sa-045 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests whether more than one definition can be provided for the same attribute of a given element type with the first declaration being binding.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
valid-sa-046 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that when more than one AttlistDecl is provided for a given element type, the contents of all those provided are merged.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
valid-not-sa-006 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that when more than one definition is provided for the same attribute of a given element type only the first declaration is binding.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
valid-not-sa-007 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of an Attribute list declaration within an external entity.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
valid-not-sa-010 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that when more that one definition is provided for the same attribute of a given element type only the first declaration is binding.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
valid-not-sa-026 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that when more that one definition is provided for the same attribute of a given element type only the first declaration is binding.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
o-p52pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid AttlistDecls: No AttDef's are required,
and the terminating
S is optional, multiple ATTLISTS per element are OK, and multiple
declarations of the same attribute are OK.
|
Sections [Rules]:
|
3.3 [52][53] |
Test ID:
|
valid-sa-113 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that it is not an error to have attributes declared for an element not itself declared.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
o-p53pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
a valid AttDef
|
Sections [Rules]:
|
3.3 3.3.1 [52] [54] |
Test ID:
|
valid-sa-040 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates an Attribute List declaration that uses a StringType as the AttType.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.1 [52] [54] |
Test ID:
|
valid-sa-077 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use an EnumeratedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.1 [52] [54] |
Test ID:
|
valid-sa-078 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use an StringType of CDATA within the Attribute type. The test also shows that REQUIRED is a valid DefaultDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.1 [52] [56] |
Test ID:
|
valid-sa-071 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use ID as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.1 [52] [56] |
Test ID:
|
valid-sa-072 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use IDREF as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.1 [52] [56] |
Test ID:
|
valid-sa-073 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use IDREFS as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.1 [52] [56] |
Test ID:
|
valid-sa-074 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use ENTITY as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.1 [52] [56] |
Test ID:
|
valid-sa-075 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use ENTITIES as the TokenizedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.2 [52] [60] |
Test ID:
|
valid-sa-079 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use an StringType of CDATA within the Attribute type. The test also shows that FIXED is a valid DefaultDecl and that a value can be given to the attribute in the Start-tag as well as the AttListDecl.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.3 3.3.2 [52] [60] |
Test ID:
|
valid-sa-080 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an AttlistDecl can use an StringType of CDATA within the Attribute type. The test also shows that FIXED is a valid DefaultDecl and that an value can be given to the attribute.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [61] |
Test ID:
|
o-p61pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid conditional sections are INCLUDE and IGNORE
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
valid-not-sa-013 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of the conditional section INCLUDE that will include its contents as part of the DTD.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
valid-not-sa-014 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of the conditional section INCLUDE that will include its contents as part of the DTD. The keyword is a parameter-entity reference.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
valid-not-sa-016 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of the conditional section INCLUDE that will include its contents as part of the DTD. The keyword is a parameter-entity reference.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
valid-not-sa-022 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of a parameter-entity reference as a keyword of a conditional section. The parameter entity must be replaced by its content before the processor decides whether to include the conditional section.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
valid-not-sa-028 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of the conditional section INCLUDE that will include its contents.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
valid-not-sa-029 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being used.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
valid-not-sa-030 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being used.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
o-p62pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid INCLUDE sections -- options S before and
after keyword, sections can nest
|
Sections [Rules]:
|
3.4 [63] |
Test ID:
|
valid-not-sa-015 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being part of the DTD. The keyword is a parameter-entity reference.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
3.4 [63] |
Test ID:
|
o-p63pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid IGNORE sections
|
Sections [Rules]:
|
3.4 [64] |
Test ID:
|
o-p64pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
IGNOREd sections ignore everything except section delimiters
|
Sections [Rules]:
|
3 3.2.1 [47] |
Test ID:
|
optional |
Collection:
|
Sun Microsystems XML Tests |
|
Tests declarations of "children" content models, and
the validity constraints associated with them.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4 |
Test ID:
|
valid-sa-085 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Parameter and General entities use different namespaces,
so there can be an entity of each type with a given name.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
valid-sa-060 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of decimal Character References within element content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
valid-sa-061 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of decimal Character References within element content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
valid-sa-062 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of hexadecimal Character References within element.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
valid-sa-064 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests in-line handling of two legal character references, which
each expand to a Unicode surrogate pair.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
valid-sa-066 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Expands a CDATA attribute with a character reference.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
valid-sa-067 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of decimal character references within element content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
valid-sa-089 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests entity expansion of three legal character references,
which each expand to a Unicode surrogate pair.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
o-p68pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid entity references. Also ensures that a charref to
'&' isn't interpreted as an entity reference open delimiter
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
valid-not-sa-003 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the expansion of an external parameter entity that declares an attribute.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
valid-not-sa-004 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Expands an external parameter entity in two different ways,
with one of them declaring an attribute.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
valid-not-sa-005 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the expansion of an external parameter entity that declares an attribute.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
valid-not-sa-027 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a parameter entity reference whose value is NULL.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
o-p69pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid PEReferences.
|
Sections [Rules]:
|
4.1 4.4.3 [68] |
Test ID:
|
valid-ext-sa-014 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates use of characters outside of normal ASCII range.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.1 4.2.2 |
Test ID:
|
valid-ext-sa-012 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates both internal and external entities and that processing of entity references may be required to produce the correct replacement text.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
valid-not-sa-001 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of an ExternalID within a document type definition.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
valid-not-sa-002 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of an ExternalID within a document type definition.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
valid-not-sa-008 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an external identifier may include a public identifier.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
valid-not-sa-009 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that an external identifier may include a public identifier.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
valid-not-sa-018 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates an EnternalID whose contents contain an parameter entity declaration and a attribute list definition.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.2 [76] |
Test ID:
|
o-p76pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid NDataDecls
|
Sections [Rules]:
|
4.2.2 4.3.3. 4.4.3 [75] [80] |
Test ID:
|
valid-ext-sa-008 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of external
entity and how replacement text is retrieved and processed. Also tests the use of an
EncodingDecl of UTF-16.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2.2 4.4.3 [75] |
Test ID:
|
valid-ext-sa-007 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the use of external entity and how replacement
text is retrieved and processed.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2 [70] |
Test ID:
|
o-p70pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
An EntityDecl is either a GEDecl or a PEDecl
|
Sections [Rules]:
|
4.2 [71] |
Test ID:
|
o-p71pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid GEDecls
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
valid-sa-082 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests that an external PE may be defined (but not referenced).
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
valid-sa-083 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests that an external PE may be defined (but not referenced).
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2 |
Test ID:
|
valid-sa-086 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests whether entities may be declared more than once,
with the first declaration being the binding one.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
valid-not-sa-017 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a parameter entity declaration that contains an attribute list declaration.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
valid-not-sa-021 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a parameter entity declaration that contains a partial attribute list declaration.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
o-p72pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid PEDecls
|
Sections [Rules]:
|
4.2 [73] |
Test ID:
|
o-p73pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
EntityDef is either Entity value or an external id,
with an optional NDataDecl
|
Sections [Rules]:
|
4.2 4.2.1 [72] [75] |
Test ID:
|
valid-not-sa-011 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a parameter entity declaration whose parameter entity definition is an ExternalID.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.2 |
Test ID:
|
valid-not-sa-025 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that when more that one definition is provided for the same entity only the first declaration is binding.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.3.1 [77] |
Test ID:
|
valid-not-sa-012 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates an enternal parsed entity that begins with a text declaration.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.3.1 4.3.2 [77] [78] |
Test ID:
|
ext01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests use of external parsed entities with and without content.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.3.2 [78] |
Test ID:
|
ext02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests use of external parsed entities with different
encodings than the base document.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
pr-xml-little |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for little-endian UTF-16 text
which relies on Japanese characters.
(Also requires ability to process a moderately complex DTD.)
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
pr-xml-utf-16 |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support UTF-16 text which relies on Japanese characters.
(Also requires ability to process a moderately complex DTD.)
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
pr-xml-utf-8 |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for UTF-8 text which relies on Japanese characters.
(Also requires ability to process a moderately complex DTD.)
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
weekly-little |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for little-endian UTF-16 encoding, and
XML names which contain Japanese characters.
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
weekly-utf-16 |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for UTF-16 encoding, and
XML names which contain Japanese characters.
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
weekly-utf-8 |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for UTF-8 encoding and
XML names which contain Japanese characters.
|
Sections [Rules]:
|
4.3.3 [80] |
Test ID:
|
valid-sa-031 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates a valid EncodingDecl within the prolog.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
valid-sa-099 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates the name of the encoding can be composed of lowercase characters.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.4.2 |
Test ID:
|
valid-sa-053 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests inclusion of a well-formed internal entity, which
holds an element required by the content model.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.4.8 |
Test ID:
|
valid-sa-070 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Verifies that internal parameter entities are correctly
expanded within the internal subset.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.4.8 |
Test ID:
|
valid-not-sa-019 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that a parameter entity will be expanded with spaces on either side.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.4.8 |
Test ID:
|
valid-not-sa-020 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Parameter entities expand with spaces on either side.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
valid-sa-065 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests ability to define an internal entity which can't
legally be expanded (contains an unquoted <).
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
valid-sa-087 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests whether character references in internal entities are
expanded early enough, by relying on correct handling to
make the entity be well formed.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
valid-sa-088 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests whether entity references in internal entities are
expanded late enough, by relying on correct handling to
make the expanded text be valid. (If it's expanded too
early, the entity will parse as an element that's not
valid in that context.)
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
valid-sa-101 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
This tests whether entity expansion is (incorrectly) done
while processing entity declarations; if it is, the entity
value literal will terminate prematurely.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
valid-sa-117 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that entity expansion is done while processing entity declarations.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
valid-sa-118 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Test demonstrates that entity expansion is done while processing entity declarations.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
v-pe00 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests construction of internal entity replacement text, using
an example in the XML specification.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
v-pe01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests construction of internal entity replacement text, using
an example in the XML specification.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
v-pe02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests construction of internal entity replacement text, using
a complex example in the XML specification.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.7 |
Test ID:
|
valid-sa-069 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Verifies that an XML parser will parse a NOTATION
declaration; the output phase of this test ensures that
it's reported to the application.
There is an output test associated with this
input file.
|
Sections [Rules]:
|
4.7 [82] |
Test ID:
|
notation01 |
Collection:
|
Sun Microsystems XML Tests |
|
NOTATION declarations don't need SYSTEM IDs; and
externally declared notations may be used to declare
unparsed entities in the internal DTD subset.
The notation must be reported to the application.
There is an output test associated with this
input file.
|
3.2 Invalid XML Documents
All conforming XML 1.0 Validating Processors
are required to report recoverable errors in the case
of documents which are Invalid. Such errors are
violations of some validity constraint (VC).
If a validating processor does not report an error when
given one of these test cases, or if the error reported is
a fatal error, it is not conformant. If the error reported
does not correspond to the problem listed in this test
description, that could also be a conformance problem; it
might instead be a faulty diagnostic.
All conforming XML 1.0 Nonvalidating Processors
should accept these documents, reporting no errors.
Sections [Rules]:
|
2.1 [1] |
Test ID:
|
o-p01pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no prolog
|
Sections [Rules]:
|
2.1 [1] |
Test ID:
|
o-p01pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Misc items after the document
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
o-p10pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid attribute values
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
all valid S characters
|
Sections [Rules]:
|
2.3 [4] |
Test ID:
|
o-p04pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
names with all valid ASCII characters, and one from each
other class in NameChar
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
o-p05pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
various valid Name constructions
|
Sections [Rules]:
|
2.3 [6] |
Test ID:
|
o-p06fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Requires at least one name.
|
Sections [Rules]:
|
2.3 [8] |
Test ID:
|
o-p08fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
at least one Nmtoken is required.
|
Sections [Rules]:
|
2.3 [8] |
Test ID:
|
o-p08fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
an invalid Nmtoken character.
|
Sections [Rules]:
|
2.4 [14] |
Test ID:
|
o-p14pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid CharData
|
Sections [Rules]:
|
2.5 [15] |
Test ID:
|
o-p15pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid comments
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
o-p16fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S after PITarget is required
|
Sections [Rules]:
|
2.6 [16] [17] |
Test ID:
|
o-p16pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
o-p16pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
o-p16pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid form of Processing Instruction. Shows that whitespace character data is valid before end of processing instruction.
|
Sections [Rules]:
|
2.7 [18] |
Test ID:
|
o-p18pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid CDSect's. Note that a CDStart in a CDSect is not
recognized as such
|
Sections [Rules]:
|
2.8 |
Test ID:
|
invalid--001 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the "Proper Declaration/PE Nesting" validity constraint by
fragmenting a comment between two parameter entities.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
invalid--003 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the "Proper Declaration/PE Nesting" validity constraint by
fragmenting an entity declaration between two parameter entities.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
invalid--004 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the "Proper Declaration/PE Nesting" validity constraint by
fragmenting an entity declaration between three parameter entities.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
invalid--005 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the "Proper Declaration/PE Nesting" validity constraint by
fragmenting an entity declaration between two parameter entities.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
invalid--006 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the "Proper Declaration/PE Nesting" validity constraint by
fragmenting an entity declaration between two parameter entities.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
root |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Root Element Type VC
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
o-p22pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
prolog can be empty
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
o-p22pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
XML declaration only
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
o-p22pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
XML decl and Misc
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows a valid XML declaration along with version info.
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows a valid XML declaration along with encoding declaration.
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows a valid XML declaration along with Standalone Document Declaration.
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23pass4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows a valid XML declaration, encoding declarationand Standalone Document Declaration.
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
o-p24pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows a prolog that has the VersionInfo delimited by double quotes.
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
o-p24pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows a prolog that has the VersionInfo delimited by single quotes.
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
o-p24pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows whitespace is allowed in prolog before version info.
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
o-p24pass4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows whitespace is allowed in prolog on both sides of equal sign.
|
Sections [Rules]:
|
2.8 [25] |
Test ID:
|
o-p25pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows whitespace is NOT necessary before or after equal sign of versioninfo.
|
Sections [Rules]:
|
2.8 [25] |
Test ID:
|
o-p25pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows whitespace can be used on both sides of equal sign of versioninfo.
|
Sections [Rules]:
|
2.8 [26] |
Test ID:
|
o-p26pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
The valid version number. We cannot test others because
a 1.0 processor is allowed to fail them.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
o-p27pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Comments are valid as the Misc part of the prolog.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
o-p27pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Processing Instructions are valid as the Misc part of the prolog.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
o-p27pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace is valid as the Misc part of the prolog.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
o-p27pass4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
A combination of comments, whitespaces and processing instructions are valid as the Misc part of the prolog.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
optional whitespace causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
attributes needing normalization cause a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa03 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
a reference to externally defined entity causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa04 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
attributes needing defaulting cause a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa05 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
a token attribute that needs normalization causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa06 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
a NOTATION attribute that needs normalization
causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa07 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
an NMTOKEN attribute needing normalization
causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa08 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
an NMTOKENS attribute needing normalization
causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa09 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
an ID attribute needing normalization causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa10 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
an IDREF attribute needing normalization causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa11 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
an IDREFS attribute needing normalization causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa12 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
an ENTITY attribute needing normalization causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa13 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
an ENTITIES attribute needing normalization causes a validity error.
|
Sections [Rules]:
|
2.9 |
Test ID:
|
inv-not-sa14 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Standalone Document Declaration VC, ensuring that
optional whitespace causes
a validity error (even if it's CDATA whitespace).
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
o-p32pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Double quotes can be used as delimeters for the value of a Standalone Document Declaration.
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
o-p32pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Single quotes can be used as delimeters for the value of a Standalone Document Declaration.
|
Sections [Rules]:
|
3 |
Test ID:
|
inv-dtd03 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Element Valid" VC (clause 2)
by omitting a required element.
|
Sections [Rules]:
|
3 |
Test ID:
|
el01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 4)
by including an undeclared child element.
|
Sections [Rules]:
|
3 |
Test ID:
|
el02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 1)
by including elements in an EMPTY content model.
|
Sections [Rules]:
|
3 |
Test ID:
|
el03 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 3) by including a child element
not permitted by a mixed content model.
|
Sections [Rules]:
|
3 |
Test ID:
|
el06 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 1),
using one of the predefined internal entities
inside an EMPTY content model.
|
Sections [Rules]:
|
3 |
Test ID:
|
optional01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing no children where
one is required.
|
Sections [Rules]:
|
3 |
Test ID:
|
optional02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
two children where one is required.
|
Sections [Rules]:
|
3 |
Test ID:
|
optional03 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where two are required.
|
Sections [Rules]:
|
3 |
Test ID:
|
optional04 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
three children where two are required.
|
Sections [Rules]:
|
3 |
Test ID:
|
optional05 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or two are
required (one construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional06 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or two are
required (a second construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional07 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or two are
required (a third construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional08 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or two are
required (a fourth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional09 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or two are
required (a fifth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional10 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
three children where one or two are
required (a basic construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional11 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
three children where one or two are
required (a second construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional12 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
three children where one or two are
required (a third construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional13 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
three children where one or two are
required (a fourth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional14 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
three children where one or two are
required (a fifth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional15 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a basic construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional16 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a second construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional17 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a third construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional18 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a fourth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional19 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a fifth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional20 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a sixth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional21 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a seventh construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional22 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (an eigth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional23 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a ninth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional24 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
no children where one or more are
required (a tenth construction of that model).
|
Sections [Rules]:
|
3 |
Test ID:
|
optional25 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Element Valid VC (clause 2) for one
instance of "children" content model, providing
text content where one or more elements are
required.
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
o-p40pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Elements content can be empty.
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
o-p40pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace is valid within a Start-tag.
|
Sections [Rules]:
|
3.1 [40] [41] |
Test ID:
|
o-p40pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Attributes are valid within a Start-tag.
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
o-p40pass4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace and Multiple Attributes are valid within a Start-tag.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
o-p41pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Attributes are valid within a Start-tag.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
o-p41pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace is valid within a Start-tags Attribute.
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
o-p42pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Test shows proper syntax for an End-tag.
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
o-p42pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace is valid after name in End-tag.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Valid display of an Empty Element Tag.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Empty Element Tags can contain an Attribute.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44pass3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace is valid in an Empty Element Tag following the end of the attribute value.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44pass4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace is valid after the name in an Empty Element Tag.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44pass5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace and Multiple Attributes are valid in an Empty Element Tag.
|
Sections [Rules]:
|
3.1 2.10 |
Test ID:
|
inv-required01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Attribute Value Type (declared)
VC for the xml:space attribute
|
Sections [Rules]:
|
3.1 2.12 |
Test ID:
|
inv-required02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Attribute Value Type (declared)
VC for the xml:lang attribute
|
Sections [Rules]:
|
3.2 |
Test ID:
|
el04 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Unique Element Type Declaration VC.
|
Sections [Rules]:
|
3.2.1 |
Test ID:
|
invalid--002 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the "Proper Group/PE Nesting" validity constraint by
fragmenting a content model between two parameter entities.
|
Sections [Rules]:
|
3.2.2 |
Test ID:
|
inv-dtd01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the No Duplicate Types VC
|
Sections [Rules]:
|
3.2.2 |
Test ID:
|
el05 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the No Duplicate Types VC.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the ID (is a Name) VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the ID (appears once) VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id03 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the One ID per Element Type VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id04 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the ID Attribute Default VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id05 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the ID Attribute Default VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id06 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the IDREF (is a Name) VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id07 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the IDREFS (is a Names) VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id08 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the IDREF (matches an ID) VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
id09 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the IDREF (IDREFS matches an ID) VC
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
attr01 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Entity Name" VC for the ENTITY attribute type.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
attr02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Entity Name" VC for the ENTITIES attribute type.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
attr03 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Notation Attributes" VC for the
NOTATION attribute type, first clause: value must be one
of the ones that's declared.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
attr04 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Notation Attributes" VC for the
NOTATION attribute type, second clause: the names in the
declaration must all be declared.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
attr05 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Name Token" VC for the NMTOKEN attribute type.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
attr06 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Name Token" VC for the NMTOKENS attribute type.
|
Sections [Rules]:
|
3.3.1 |
Test ID:
|
attr07 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Enumeration" VC by providing
a value which wasn't one of the choices.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
inv-required00 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the Required Attribute VC.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr08 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Fixed Attribute Default" VC by
providing the wrong value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr09 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal IDREF value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr10 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal IDREFS value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr11 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal ENTITY value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr12 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal ENTITIES value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr13 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal NMTOKEN value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr14 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal NMTOKENS value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr15 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal NOTATIONS value.
|
Sections [Rules]:
|
3.3.2 |
Test ID:
|
attr16 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Attribute Default Legal" VC by
providing an illegal enumeration value.
|
Sections [Rules]:
|
3 3.1 [39] [43] |
Test ID:
|
o-p39pass2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Character data is valid element content.
|
Sections [Rules]:
|
3 3.1 [39] [44] |
Test ID:
|
o-p39pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Empty element tag may be used for any element which has no content.
|
Sections [Rules]:
|
4.1 |
Test ID:
|
not-wf-not-sa-005 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the Entity Declared VC by referring to an
undefined parameter entity within an external entity.
|
Sections [Rules]:
|
4.1 |
Test ID:
|
inv-dtd06 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests "Entity Declared" VC for a parameter entity. NOTE: there
are both VCs and WFCs with this name, which is a specification issue
in that it is both confusing and in some ways self-contradictory.
The WFC does not apply to PEs, and even the clause which might
seem to suggest it could is ruled out in this test.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
o-p66pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid character references
|
Sections [Rules]:
|
4.2.2 |
Test ID:
|
inv-dtd02 |
Collection:
|
Sun Microsystems XML Tests |
|
Tests the "Notation Declared" VC by using an undeclared
notation name.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
o-p75pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
valid external identifiers
|
Sections [Rules]:
|
4.2 [74] |
Test ID:
|
o-p74pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
PEDef is either an entity value or an external id
|
Sections [Rules]:
|
4.3.3 2.8 |
Test ID:
|
utf16b |
Collection:
|
Sun Microsystems XML Tests |
|
Tests reading an invalid "big endian" UTF-16 document
|
Sections [Rules]:
|
4.3.3 2.8 |
Test ID:
|
utf16l |
Collection:
|
Sun Microsystems XML Tests |
|
Tests reading an invalid "little endian" UTF-16 document
|
3.3 Documents that are Not Well Formed
All conforming XML 1.0 Processors are required to
report fatal errors in the case of documents which are not
Well Formed. Such errors are basically of two types:
(a) the document violates the XML grammar; or else
(b) it violates a well formedness constraint
(WFC). There is a single exception to that
requirement: nonvalidating processors which do not read
certain types of external entities are not required to detect
(and hence report) these errors.
If a processor does not report a fatal error when given
one of these test cases, it is not conformant. If the error
reported does not correspond to the problem listed in this
test description, that could also be a conformance problem;
it might instead be a faulty diagnostic.
Sections [Rules]:
|
2.1 [1] |
Test ID:
|
not-wf-sa-050 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Empty document, with no root element.
|
Sections [Rules]:
|
2.1 [1] |
Test ID:
|
o-p01fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S cannot occur before the prolog
|
Sections [Rules]:
|
2.1 [1] |
Test ID:
|
o-p01fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
comments cannot occur before the prolog
|
Sections [Rules]:
|
2.1 [1] |
Test ID:
|
o-p01fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only one document element
|
Sections [Rules]:
|
2.1 [1] |
Test ID:
|
o-p01fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
document element must be complete.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-030 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
A form feed is not a legal XML character.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-031 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
A form feed is not a legal XML character.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-032 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
A form feed is not a legal XML character.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-033 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
An ESC (octal 033) is not a legal XML character.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-034 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
A form feed is not a legal XML character.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-142 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character #x0000 is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-143 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character #x001F is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-144 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character #xFFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-145 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character #xD800 is not legal anywhere in an XML document. (If it
appeared in a UTF-16 surrogate pair, it'd represent half of a UCS-4
character and so wouldn't really be in the document.)
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-146 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character references must also refer to legal XML characters;
#x00110000 is one more than the largest legal character.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-166 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-167 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFE is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-168 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
An unpaired surrogate (D800) is not legal anywhere
in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-169 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
An unpaired surrogate (DC00) is not legal anywhere
in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-170 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Four byte UTF-8 encodings can encode UCS-4 characters
which are beyond the range of legal XML characters
(and can't be expressed in Unicode surrogate pairs).
This document holds such a character.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-171 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-172 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-173 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-174 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-175 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
not-wf-sa-177 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character FFFF is not legal anywhere in an XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail10 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail11 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail12 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail13 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail14 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail15 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail16 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail17 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail18 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail19 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail20 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail21 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail22 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail23 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail24 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail25 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail26 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail27 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail28 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail29 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail30 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail31 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail6 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail7 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail8 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.2 [2] |
Test ID:
|
o-p02fail9 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
not-wf-sa-012 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
SGML-ism: attribute values must be quoted in all cases.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
not-wf-sa-013 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
The quotes on both ends of an attribute value must match.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
not-wf-sa-014 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attribute values may not contain literal '<' characters.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
not-wf-sa-020 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attribute values may not contain literal '&'
characters except as part of an entity reference.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
not-wf-sa-021 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attribute values may not contain literal '&'
characters except as part of an entity reference.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
not-wf-sa-088 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attribute values are terminated by literal quote characters,
and any entity expansion is done afterwards.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
not-wf-sa-090 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attributes may not contain a literal "<" character;
this one has one because of reference expansion.
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
o-p10fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
attribute values exclude '<'
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
o-p10fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
attribute values exclude '&'
|
Sections [Rules]:
|
2.3 [10] |
Test ID:
|
o-p10fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.3 [11] |
Test ID:
|
o-p11fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.3 [11] |
Test ID:
|
o-p11fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
cannot contain delimiting quotes
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
pubid01 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal entity ref in public ID
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
pubid02 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal characters in public ID
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
pubid03 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal characters in public ID
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
pubid04 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal characters in public ID
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
pubid05 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML-ism: public ID without system ID
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
o-p12fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
'"' excluded
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
o-p12fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
'\' excluded
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
o-p12fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
entity references excluded
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
o-p12fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
'>' excluded
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
o-p12fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
'<' excluded
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
o-p12fail6 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
built-in entity refs excluded
|
Sections [Rules]:
|
2.3 [12] |
Test ID:
|
o-p12fail7 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
|
Sections [Rules]:
|
2.3 [13] |
Test ID:
|
not-wf-sa-085 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Public IDs may not contain "[".
|
Sections [Rules]:
|
2.3 [13] |
Test ID:
|
not-wf-sa-086 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Public IDs may not contain "[".
|
Sections [Rules]:
|
2.3 [13] |
Test ID:
|
not-wf-sa-087 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Public IDs may not contain "[".
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail10 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail11 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail12 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail13 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail14 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail15 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail16 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail17 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail18 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail19 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail20 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail21 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail22 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail23 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail24 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail25 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail26 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail27 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail28 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail29 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail7 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail8 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [3] |
Test ID:
|
o-p03fail9 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Use of illegal character within XML document.
|
Sections [Rules]:
|
2.3 [4] |
Test ID:
|
not-wf-sa-002 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Names may not start with "."; it's not a Letter.
|
Sections [Rules]:
|
2.3 [4] |
Test ID:
|
not-wf-sa-140 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character '゚' is a CombiningChar, not a
Letter, and so may not begin a name.
|
Sections [Rules]:
|
2.3 [4] |
Test ID:
|
o-p04fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Name contains invalid character.
|
Sections [Rules]:
|
2.3 [4] |
Test ID:
|
o-p04fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Name contains invalid character.
|
Sections [Rules]:
|
2.3 [4] |
Test ID:
|
o-p04fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Name contains invalid character.
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
not-wf-sa-008 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Entity references must include names, which don't begin
with '.' (it's not a Letter or other name start character).
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
not-wf-sa-023 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Digits are not valid name start characters.
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
not-wf-sa-024 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Digits are not valid name start characters.
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
not-wf-sa-141 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character #x0E5C is not legal in XML names.
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
o-p05fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
a Name cannot start with a digit
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
o-p05fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
a Name cannot start with a '.'
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
o-p05fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
a Name cannot start with a "-"
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
o-p05fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
a Name cannot start with a CombiningChar
|
Sections [Rules]:
|
2.3 [5] |
Test ID:
|
o-p05fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
a Name cannot start with an Extender
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
not-wf-sa-113 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Parameter entity values must use valid reference syntax;
this reference is malformed.
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
not-wf-sa-114 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
General entity values must use valid reference syntax;
this reference is malformed.
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
not-wf-sa-159 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Uses '&' unquoted in an entity declaration,
which is illegal syntax for an entity reference.
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
o-p09fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
EntityValue excludes '%'
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
o-p09fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
EntityValue excludes '&'
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
o-p09fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
incomplete character reference
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
o-p09fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.3 [9] |
Test ID:
|
o-p09fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.4 [14] |
Test ID:
|
not-wf-sa-025 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Text may not contain a literal ']]>' sequence.
|
Sections [Rules]:
|
2.4 [14] |
Test ID:
|
not-wf-sa-026 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Text may not contain a literal ']]>' sequence.
|
Sections [Rules]:
|
2.4 [14] |
Test ID:
|
not-wf-sa-029 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Text may not contain a literal ']]>' sequence.
|
Sections [Rules]:
|
2.4 [14] |
Test ID:
|
o-p14fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
'<' excluded
|
Sections [Rules]:
|
2.4 [14] |
Test ID:
|
o-p14fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
'&' excluded
|
Sections [Rules]:
|
2.4 [14] |
Test ID:
|
o-p14fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
"]]>" excluded
|
Sections [Rules]:
|
2.5 [15] |
Test ID:
|
not-wf-sa-027 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Comments must be terminated with "-->".
|
Sections [Rules]:
|
2.5 [15] |
Test ID:
|
sgml03 |
Collection:
|
Sun Microsystems XML Tests |
|
Comments may not contain "--"
|
Sections [Rules]:
|
2.5 [15] |
Test ID:
|
o-p15fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
comments can't end in '-'
|
Sections [Rules]:
|
2.5 [15] |
Test ID:
|
o-p15fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
one comment per comment (contrasted with SGML)
|
Sections [Rules]:
|
2.5 [15] |
Test ID:
|
o-p15fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
can't include 2 or more adjacent '-'s
|
Sections [Rules]:
|
2.5 [16] |
Test ID:
|
not-wf-sa-006 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML comments may not contain "--"
|
Sections [Rules]:
|
2.5 [16] |
Test ID:
|
not-wf-sa-070 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML comments may not contain "--"
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
not-wf-sa-003 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Processing Instruction target name is required.
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
not-wf-sa-004 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
SGML-ism: processing instructions end in '?>' not '>'.
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
not-wf-sa-005 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Processing instructions end in '?>' not '?'.
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
not-wf-sa-028 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Processing instructions must end with '?>'.
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
pi |
Collection:
|
Sun Microsystems XML Tests |
|
No space between PI target name and data
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
o-p16fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
"xml" is an invalid PITarget
|
Sections [Rules]:
|
2.6 [16] |
Test ID:
|
o-p16fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
a PITarget must be present
|
Sections [Rules]:
|
2.6 [17] |
Test ID:
|
not-wf-sa-157 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
'<?xmL ...?>' is not a legal processing instruction
target name.
|
Sections [Rules]:
|
2.6 [17] |
Test ID:
|
not-wf-not-sa-002 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Processing instruction target names may not be "XML"
in any combination of cases.
|
Sections [Rules]:
|
2.6 [17] |
Test ID:
|
not-wf-ext-sa-003 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Only one text declaration is permitted; a second one
looks like an illegal processing instruction (target names
of "xml" in any case are not allowed).
|
Sections [Rules]:
|
2.7 |
Test ID:
|
not-wf-sa-105 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid placement of CDATA section.
|
Sections [Rules]:
|
2.7 [18] |
Test ID:
|
not-wf-sa-017 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
CDATA sections need a terminating ']]>'.
|
Sections [Rules]:
|
2.7 [18] |
Test ID:
|
not-wf-sa-051 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
CDATA is invalid at top level of document.
|
Sections [Rules]:
|
2.7 [18] |
Test ID:
|
not-wf-sa-128 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid CDATA syntax.
|
Sections [Rules]:
|
2.7 [18] |
Test ID:
|
o-p18fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no space before "CDATA"
|
Sections [Rules]:
|
2.7 [18] |
Test ID:
|
o-p18fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no space after "CDATA"
|
Sections [Rules]:
|
2.7 [18] |
Test ID:
|
o-p18fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
CDSect's can't nest
|
Sections [Rules]:
|
2.7 [19] |
Test ID:
|
not-wf-sa-018 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
CDATA sections begin with a literal '<![CDATA[', no space.
|
Sections [Rules]:
|
2.7 [19] |
Test ID:
|
not-wf-sa-108 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
No space in '<![CDATA['.
|
Sections [Rules]:
|
2.7 [19] |
Test ID:
|
not-wf-sa-112 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
CDATA sections start '<![CDATA[', not '<!cdata['.
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
not-wf-sa-147 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML Declaration may not be preceded by whitespace.
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
not-wf-sa-148 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML Declaration may not be preceded by comments or whitespace.
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
not-wf-sa-152 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML declarations must include the "version=..." string.
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
o-p22fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
prolog must start with XML decl
|
Sections [Rules]:
|
2.8 [22] |
Test ID:
|
o-p22fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
prolog must start with XML decl
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
not-wf-sa-095 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
VersionInfo must come before EncodingDecl.
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
not-wf-sa-098 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Only one "version=..." string may appear in an XML declaration.
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
not-wf-sa-099 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Only three pseudo-attributes are in the XML declaration,
and "valid=..." is not one of them.
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
"xml" must be lower-case
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
VersionInfo must be supplied
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
VersionInfo must come first
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
SDDecl must come last
|
Sections [Rules]:
|
2.8 [23] |
Test ID:
|
o-p23fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no SGML-type PIs
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
not-wf-sa-094 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Prolog VERSION must be lowercase.
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
not-wf-sa-097 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Both quotes surrounding VersionNum must be the same.
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
o-p24fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.8 [24] |
Test ID:
|
o-p24fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.8 [25] |
Test ID:
|
o-p25fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Comment is illegal in VersionInfo.
|
Sections [Rules]:
|
2.8 [26] |
Test ID:
|
not-wf-sa-102 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Provides an illegal XML version number; spaces are illegal.
|
Sections [Rules]:
|
2.8 [26] |
Test ID:
|
o-p26fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal character in VersionNum.
|
Sections [Rules]:
|
2.8 [26] |
Test ID:
|
o-p26fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal character in VersionNum.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-036 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Text may not appear after the root element.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-037 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character references may not appear after the root element.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-040 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Provides two document elements.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-041 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Provides two document elements.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-043 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Provides #PCDATA text after the document element.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-044 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Provides two document elements.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-048 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Provides a CDATA section after the roor element.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
not-wf-sa-151 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML declarations may not follow document content.
|
Sections [Rules]:
|
2.8 [27] |
Test ID:
|
o-p27fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
References aren't allowed in Misc,
even if they would resolve to valid Misc.
|
Sections [Rules]:
|
2.8 [28] |
Test ID:
|
not-wf-sa-055 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid Document Type Definition format.
|
Sections [Rules]:
|
2.8 [28] |
Test ID:
|
not-wf-sa-056 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid Document Type Definition format - misplaced comment.
|
Sections [Rules]:
|
2.8 [28] |
Test ID:
|
not-wf-sa-107 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid document type declaration. CDATA alone is invalid.
|
Sections [Rules]:
|
2.8 [28] |
Test ID:
|
not-wf-sa-149 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML Declaration may not be within a DTD.
|
Sections [Rules]:
|
2.8 [28] |
Test ID:
|
o-p28fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only declarations in DTD.
|
Sections [Rules]:
|
2.8 [29] |
Test ID:
|
not-wf-sa-063 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Conditional sections may only appear in the external
DTD subset.
|
Sections [Rules]:
|
2.8 [29] |
Test ID:
|
o-p29fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
A processor must not pass unknown declaration types.
|
Sections [Rules]:
|
2.8 [30] |
Test ID:
|
o-p30fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
An XML declaration is not the same as a TextDecl
|
Sections [Rules]:
|
2.8 [31] |
Test ID:
|
o-p31fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
external subset excludes doctypedecl
|
Sections [Rules]:
|
2.8 2.6 [23, 17] |
Test ID:
|
not-wf-sa-154 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
'<?XML ...?>' is neither an XML declaration
nor a legal processing instruction target name.
|
Sections [Rules]:
|
2.8 2.6 [23, 17] |
Test ID:
|
not-wf-sa-155 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
'<?xmL ...?>' is neither an XML declaration
nor a legal processing instruction target name.
|
Sections [Rules]:
|
2.8 2.6 [23, 17] |
Test ID:
|
not-wf-sa-156 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
'<?xMl ...?>' is neither an XML declaration
nor a legal processing instruction target name.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
not-wf-sa-160 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Violates the PEs in Internal Subset WFC
by using a PE reference within a declaration.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
not-wf-sa-161 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Violates the PEs in Internal Subset WFC
by using a PE reference within a declaration.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
not-wf-sa-162 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Violates the PEs in Internal Subset WFC
by using a PE reference within a declaration.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
valid-sa-094 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
This refers to an undefined parameter entity reference within
a markup declaration in the internal DTD subset, violating
the PEs in Internal Subset WFC.
|
Sections [Rules]:
|
2.8 |
Test ID:
|
sgml02 |
Collection:
|
Sun Microsystems XML Tests |
|
XML declaration must be at the very beginning of a document;
it"s not a processing instruction
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
not-wf-sa-096 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is required before the standalone declaration.
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
not-wf-sa-100 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Only "yes" and "no" are permitted as values of "standalone".
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
o-p32fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
o-p32fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quote types must match
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
o-p32fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
initial S is required
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
o-p32fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quotes are required
|
Sections [Rules]:
|
2.9 [32] |
Test ID:
|
o-p32fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
yes or no must be lower case
|
Sections [Rules]:
|
3 |
Test ID:
|
not-wf-sa-039 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the Element Type Match WFC - end tag name must
match start tag name.
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
not-wf-sa-046 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
This start (or empty element) tag was not terminated correctly.
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
not-wf-sa-049 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Missing start tag
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
attlist10 |
Collection:
|
Sun Microsystems XML Tests |
|
Whitespace required between attributes
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
o-p40fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required between attributes
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
o-p40fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
tags start with names, not nmtokens
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
o-p40fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
tags start with names, not nmtokens
|
Sections [Rules]:
|
3.1 [40] |
Test ID:
|
o-p40fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no space before name
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
not-wf-sa-001 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attribute values must start with attribute names, not "?".
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
not-wf-sa-011 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
SGML-ism: attribute values must be explicitly assigned a
value, it can't act as a boolean toggle.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
not-wf-sa-015 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attribute values need a value, not just an equals sign.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
not-wf-sa-016 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Attribute values need an associated name.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
not-wf-sa-178 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax matching double quote is missing.
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
o-p41fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
quotes are required (contrast with SGML)
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
o-p41fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
attribute name is required (contrast with SGML)
|
Sections [Rules]:
|
3.1 [41] |
Test ID:
|
o-p41fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Eq required
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
not-wf-sa-019 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
End tags may not be abbreviated as '</>'.
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
not-wf-sa-042 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid End Tag
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
not-wf-sa-053 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
End tag does not match start tag.
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
element00 |
Collection:
|
Sun Microsystems XML Tests |
|
EOF in middle of incomplete ETAG
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
element01 |
Collection:
|
Sun Microsystems XML Tests |
|
EOF in middle of incomplete ETAG
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
o-p42fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no space before name
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
o-p42fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
cannot end with "/>"
|
Sections [Rules]:
|
3.1 [42] |
Test ID:
|
o-p42fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no NET (contrast with SGML)
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
not-wf-sa-035 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
The '<' character is a markup delimiter and must
start an element, CDATA section, PI, or comment.
|
Sections [Rules]:
|
3.1 |
Test ID:
|
not-wf-sa-038 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the "Unique Att Spec" WF constraint by providing
multiple values for an attribute.
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
not-wf-sa-150 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
XML declarations may not be within element content.
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
element02 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal markup (<%@ ... %>)
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
element03 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal markup (<% ... %>)
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
element04 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal markup (<!ELEMENT ... >)
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
o-p43fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no non-comment declarations
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
o-p43fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no conditional sections
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
o-p43fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no conditional sections
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
not-wf-sa-045 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid Empty Element Tag
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
not-wf-sa-047 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid empty element tag invalid whitespace
|
Sections [Rules]:
|
3.1 |
Test ID:
|
not-wf-sa-081 |
Entities:
|
general
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
This tests the No External Entity References WFC,
since the entity is referred to within an attribute.
|
Sections [Rules]:
|
3.1 |
Test ID:
|
not-wf-sa-082 |
Entities:
|
general
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
This tests the No External Entity References WFC,
since the entity is referred to within an attribute.
|
Sections [Rules]:
|
3.1 [43] |
Test ID:
|
not-wf-sa-111 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Entiry reference must be in content of element not Start-tag.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
not-wf-sa-186 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Whitespace is required between attribute/value pairs.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
attlist11 |
Collection:
|
Sun Microsystems XML Tests |
|
Whitespace required between attributes
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal space before Empty element tag.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal space after Empty element tag.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal comment in Empty element tag.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Whitespace required between attributes.
|
Sections [Rules]:
|
3.1 [44] |
Test ID:
|
o-p44fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Duplicate attribute name is illegal.
|
Sections [Rules]:
|
3.2.1 [46] |
Test ID:
|
not-wf-sa-139 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
The element-content model should not be empty.
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
not-wf-sa-122 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax mixed connectors are used.
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
sgml13 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML Unordered content models not allowed
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
o-p47fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Invalid operator '|' must match previous operator ','
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
o-p47fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal character '-' in Element-content model
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
o-p47fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Optional character must follow a name or list
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
o-p47fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal space before optional character
|
Sections [Rules]:
|
3.2.1 [48] |
Test ID:
|
not-wf-sa-123 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax mismatched parenthesis.
|
Sections [Rules]:
|
3.2.1 [48] |
Test ID:
|
not-wf-sa-138 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax for content particle.
|
Sections [Rules]:
|
3.2.1 [48] |
Test ID:
|
content01 |
Collection:
|
Sun Microsystems XML Tests |
|
No whitespace before "?" in content model
|
Sections [Rules]:
|
3.2.1 [48] |
Test ID:
|
content02 |
Collection:
|
Sun Microsystems XML Tests |
|
No whitespace before "*" in content model
|
Sections [Rules]:
|
3.2.1 [48] |
Test ID:
|
content03 |
Collection:
|
Sun Microsystems XML Tests |
|
No whitespace before "+" in content model
|
Sections [Rules]:
|
3.2.1 [48] |
Test ID:
|
o-p48fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal space before optional character
|
Sections [Rules]:
|
3.2.1 [48] |
Test ID:
|
o-p48fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Illegal space before optional character
|
Sections [Rules]:
|
3.2.1 [49] |
Test ID:
|
o-p49fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
connectors must match
|
Sections [Rules]:
|
3.2.1 [50] |
Test ID:
|
not-wf-sa-132 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax mixed connectors used.
|
Sections [Rules]:
|
3.2.1 |
Test ID:
|
not-wf-sa-133 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Illegal whitespace before optional character causes syntax error.
|
Sections [Rules]:
|
3.2.1 |
Test ID:
|
not-wf-sa-134 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Illegal whitespace before optional character causes syntax error.
|
Sections [Rules]:
|
3.2.1 [47] |
Test ID:
|
not-wf-sa-135 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid character used as connector.
|
Sections [Rules]:
|
3.2.1 [50] |
Test ID:
|
o-p50fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
connectors must match
|
Sections [Rules]:
|
3.2.1 [55] |
Test ID:
|
nwf-dtd00 |
Collection:
|
Sun Microsystems XML Tests |
|
Comma mandatory in content model
|
Sections [Rules]:
|
3.2.1 [55] |
Test ID:
|
nwf-dtd01 |
Collection:
|
Sun Microsystems XML Tests |
|
Can't mix comma and vertical bar in content models
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
not-wf-sa-124 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid format of Mixed-content declaration.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
not-wf-sa-125 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax extra set of parenthesis not necessary.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
not-wf-sa-126 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax Mixed-content must be defined as zero or more.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
not-wf-sa-127 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax Mixed-content must be defined as zero or more.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
not-wf-sa-183 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Mixed content declarations may not include content particles.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
not-wf-sa-184 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
In mixed content models, element names must not be
parenthesized.
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
occurrence on #PCDATA group must be *
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
occurrence on #PCDATA group must be *
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
#PCDATA must come first
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
occurrence on #PCDATA group must be *
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only '|' connectors
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51fail6 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Only '|' connectors and occurrence on #PCDATA group must be *
|
Sections [Rules]:
|
3.2.2 [51] |
Test ID:
|
o-p51fail7 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no nested groups
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
not-wf-sa-057 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
This isn't SGML; comments can't exist in declarations.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
not-wf-sa-129 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax for Element Type Declaration.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
not-wf-sa-130 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax for Element Type Declaration.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
not-wf-sa-131 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax for Element Type Declaration.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
not-wf-sa-136 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tag omission is invalid in XML.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
not-wf-sa-137 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is required before a content model.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
sgml05 |
Collection:
|
Sun Microsystems XML Tests |
|
ELEMENT declarations apply to only one element, unlike SGML
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
sgml07 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML Tag minimization specifications are not allowed
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
sgml08 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML Tag minimization specifications are not allowed
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
sgml09 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML Content model exception specifications are not allowed
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
sgml10 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML Content model exception specifications are not allowed
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
o-p45fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
ELEMENT must be upper case.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
o-p45fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S before contentspec is required.
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
o-p45fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only one content spec
|
Sections [Rules]:
|
3.2 [45] |
Test ID:
|
o-p45fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no comments in declarations (contrast with SGML)
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
sgml11 |
Collection:
|
Sun Microsystems XML Tests |
|
CDATA is not a valid content model spec
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
sgml12 |
Collection:
|
Sun Microsystems XML Tests |
|
RCDATA is not a valid content model spec
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
o-p46fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no parens on declared content
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
o-p46fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no inclusions (contrast with SGML)
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
o-p46fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no exclusions (contrast with SGML)
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
o-p46fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no space before occurrence
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
o-p46fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
single group
|
Sections [Rules]:
|
3.2 [46] |
Test ID:
|
o-p46fail6 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
can't be both declared and modeled
|
Sections [Rules]:
|
3.3.1 [54] |
Test ID:
|
not-wf-sa-058 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid character , in ATTLIST enumeration
|
Sections [Rules]:
|
3.3.1 [54] |
Test ID:
|
o-p54fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
don't pass unknown attribute types
|
Sections [Rules]:
|
3.3.1 [55] |
Test ID:
|
o-p55fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
must be upper case
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
not-wf-sa-060 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid type NAME defined in ATTLIST.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist01 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's NUTOKEN is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist02 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's NUTOKENS attribute type is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist04 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's NUMBER attribute type is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist05 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's NUMBERS attribute type is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist06 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's NAME attribute type is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist07 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's NAMES attribute type is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist08 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's #CURRENT is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
attlist09 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML's #CONREF is not allowed.
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
o-p56fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no IDS type
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
o-p56fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no NUMBER type
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
o-p56fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no NAME type
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
o-p56fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no ENTITYS type
- types must be upper case
|
Sections [Rules]:
|
3.3.1 [56] |
Test ID:
|
o-p56fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
types must be upper case
|
Sections [Rules]:
|
3.3.1 [57] |
Test ID:
|
o-p57fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no keyword for NMTOKEN enumeration
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
not-wf-sa-068 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is required between NOTATION keyword and list of
enumerated choices in <!ATTLIST...> declarations.
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
at least one value required
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
separator must be '|'
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
notations are NAMEs, not NMTOKENs -- note:
Leaving the invalid
notation undeclared would cause a validating parser to fail without
checking the name syntax, so the notation is declared with an
invalid name. A parser that reports error positions should report
an error at the AttlistDecl on line 6, before reaching the notation
declaration.
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
NOTATION must be upper case
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S after keyword is required
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail6 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
parentheses are require
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail7 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
values are unquoted
|
Sections [Rules]:
|
3.3.1 [58] |
Test ID:
|
o-p58fail8 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
values are unquoted
|
Sections [Rules]:
|
3.3.1 [59] |
Test ID:
|
not-wf-sa-059 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
String literal must be in quotes.
|
Sections [Rules]:
|
3.3.1 [59] |
Test ID:
|
attlist03 |
Collection:
|
Sun Microsystems XML Tests |
|
Comma doesn't separate enumerations, unlike in SGML.
|
Sections [Rules]:
|
3.3.1 [59] |
Test ID:
|
o-p59fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
at least one required
|
Sections [Rules]:
|
3.3.1 [59] |
Test ID:
|
o-p59fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
separator must be ","
|
Sections [Rules]:
|
3.3.1 [59] |
Test ID:
|
o-p59fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
values are unquoted
|
Sections [Rules]:
|
3.3.2 [60] |
Test ID:
|
o-p60fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
keywords must be upper case
|
Sections [Rules]:
|
3.3.2 [60] |
Test ID:
|
o-p60fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required after #FIXED
|
Sections [Rules]:
|
3.3.2 [60] |
Test ID:
|
o-p60fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only #FIXED has both keyword and value
|
Sections [Rules]:
|
3.3.2 [60] |
Test ID:
|
o-p60fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
#FIXED required value
|
Sections [Rules]:
|
3.3.2 [60] |
Test ID:
|
o-p60fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only one default type
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
not-wf-sa-066 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Required whitespace is missing.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
not-wf-sa-158 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
SGML-ism: "#NOTATION gif" can't have attributes.
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
sgml04 |
Collection:
|
Sun Microsystems XML Tests |
|
ATTLIST declarations apply to only one element, unlike SGML
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
sgml06 |
Collection:
|
Sun Microsystems XML Tests |
|
ATTLIST declarations are never global, unlike in SGML
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
o-p52fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
A name is required
|
Sections [Rules]:
|
3.3 [52] |
Test ID:
|
o-p52fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
A name is required
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
not-wf-sa-064 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is required between attribute type and default values
in <!ATTLIST...> declarations.
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
not-wf-sa-065 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is required between attribute name and type
in <!ATTLIST...> declarations.
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
not-wf-sa-067 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is required between attribute type and default values
in <!ATTLIST...> declarations.
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
o-p53fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required before default
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
o-p53fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required before type
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
o-p53fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
type is required
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
o-p53fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
default is required
|
Sections [Rules]:
|
3.3 [53] |
Test ID:
|
o-p53fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
name is requried
|
Sections [Rules]:
|
3.4 [61] |
Test ID:
|
cond01 |
Collection:
|
Sun Microsystems XML Tests |
|
Only INCLUDE and IGNORE are conditional section keywords
|
Sections [Rules]:
|
3.4 [61] |
Test ID:
|
cond02 |
Collection:
|
Sun Microsystems XML Tests |
|
Must have keyword in conditional sections
|
Sections [Rules]:
|
3.4 [61] |
Test ID:
|
o-p61fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no other types, including TEMP, which is valid in SGML
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
not-wf-not-sa-001 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Conditional sections must be properly terminated ("]>" used
instead of "]]>").
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
not-wf-not-sa-003 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Conditional sections must be properly terminated ("]]>" omitted).
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
not-wf-not-sa-004 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Conditional sections must be properly terminated ("]]>" omitted).
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
not-wf-not-sa-006 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Conditional sections need a '[' after the INCLUDE or IGNORE.
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
o-p62fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
INCLUDE must be upper case
|
Sections [Rules]:
|
3.4 [62] |
Test ID:
|
o-p62fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no spaces in terminating delimiter
|
Sections [Rules]:
|
3.4 [63] |
Test ID:
|
o-p63fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
IGNORE must be upper case
|
Sections [Rules]:
|
3.4 [63] |
Test ID:
|
o-p63fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
delimiters must be balanced
|
Sections [Rules]:
|
3.4 [64] |
Test ID:
|
o-p64fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
section delimiters must balance
|
Sections [Rules]:
|
3.4 [64] |
Test ID:
|
o-p64fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
section delimiters must balance
|
Sections [Rules]:
|
3 [39] |
Test ID:
|
not-wf-sa-176 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Start tags must have matching end tags.
|
Sections [Rules]:
|
3 [39] |
Test ID:
|
sgml01 |
Collection:
|
Sun Microsystems XML Tests |
|
SGML-ism: omitted end tag for EMPTY content
|
Sections [Rules]:
|
3 [39] |
Test ID:
|
o-p39fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
start-tag requires end-tag
|
Sections [Rules]:
|
3 [39] |
Test ID:
|
o-p39fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
end-tag requires start-tag
|
Sections [Rules]:
|
3 [39] |
Test ID:
|
o-p39fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
XML documents contain one or more elements
|
Sections [Rules]:
|
3 [39] |
Test ID:
|
o-p39fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
|
Sections [Rules]:
|
3 [39] |
Test ID:
|
o-p39fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
not-wf-sa-009 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character references may have only decimal or numeric strings.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
not-wf-sa-022 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character references end with semicolons, always!
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
not-wf-sa-052 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid character reference.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
not-wf-sa-093 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Hexadecimal character references may not use the uppercase 'X'.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
not-wf-sa-179 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid syntax matching double quote is missing.
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
o-p66fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
terminating ';' is required
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
o-p66fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no S after '&#'
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
o-p66fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no hex digits in numeric reference
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
o-p66fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only hex digits in hex references
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
o-p66fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no references to non-characters
|
Sections [Rules]:
|
4.1 [66] |
Test ID:
|
o-p66fail6 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no references to non-characters
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-007 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
General entity references have no whitespace after the
entity name and before the semicolon.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-010 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Ampersand may only appear as part of a general entity reference.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-071 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
ENTITY can't reference itself directly or indirectly.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-072 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Undefined ENTITY foo.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-073 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Undefined ENTITY f.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-075 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
ENTITY can't reference itself directly or indirectly.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-076 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Undefined ENTITY foo.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-078 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Undefined ENTITY foo.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-079 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
ENTITY can't reference itself directly or indirectly.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-080 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
ENTITY can't reference itself directly or indirectly.
|
Sections [Rules]:
|
4.1 |
Test ID:
|
not-wf-sa-084 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the Parsed Entity WFC by referring to an
unparsed entity. (This precedes the error of not declaring
that entity's notation, which may be detected any time before
the DTD parsing is completed.)
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-110 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Entity reference must be in content of element.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-118 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Entity reference expansion is not recursive.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
not-wf-sa-121 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
A name of an ENTITY was started with an invalid character.
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
o-p68fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
terminating ';' is required
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
o-p68fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no S after '&'
|
Sections [Rules]:
|
4.1 [68] |
Test ID:
|
o-p68fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no S before ';'
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
not-wf-sa-163 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid placement of Parameter entity reference.
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
not-wf-sa-164 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid placement of Parameter entity reference.
|
Sections [Rules]:
|
4.1 |
Test ID:
|
not-wf-sa-180 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
The Entity Declared WFC requires entities to be declared
before they are used in an attribute list declaration.
|
Sections [Rules]:
|
4.1 |
Test ID:
|
not-wf-sa-185 |
Entities:
|
parameter
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the Entity Declared WFC.
Note: a nonvalidating parser is permitted not to report
this WFC violation, since it would need to read an external
parameter entity to distinguish it from a violation of
the Standalone Declaration VC.
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
not-wf-not-sa-008 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
In DTDs, the '%' character must be part of a parameter
entity reference.
|
Sections [Rules]:
|
4.1 |
Test ID:
|
not-wf-ext-sa-001 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tests the No Recursion WFC by having an external general
entity be self-recursive.
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
dtd02 |
Collection:
|
Sun Microsystems XML Tests |
|
PE name immediately after "%"
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
dtd03 |
Collection:
|
Sun Microsystems XML Tests |
|
PE name immediately followed by ";"
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
o-p69fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
terminating ';' is required
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
o-p69fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no S after '%'
|
Sections [Rules]:
|
4.1 [69] |
Test ID:
|
o-p69fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no S before ';'
|
Sections [Rules]:
|
4.2 |
Test ID:
|
not-wf-sa-106 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Invalid placement of entity declaration.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
not-wf-sa-054 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
PUBLIC requires two literals.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
not-wf-sa-061 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
External entity declarations require whitespace between public
and system IDs.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
dtd04 |
Collection:
|
Sun Microsystems XML Tests |
|
PUBLIC literal must be quoted
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
dtd05 |
Collection:
|
Sun Microsystems XML Tests |
|
SYSTEM identifier must be quoted
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
o-p75fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S required after "PUBLIC"
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
o-p75fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S required after "SYSTEM"
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
o-p75fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S required between literals
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
o-p75fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
"SYSTEM" implies only one literal
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
o-p75fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only one keyword
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
o-p75fail6 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
"PUBLIC" requires two literals (contrast with SGML)
|
Sections [Rules]:
|
4.2.2 [76] |
Test ID:
|
not-wf-sa-069 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is required before an NDATA entity annotation.
|
Sections [Rules]:
|
4.2.2 [76] |
Test ID:
|
not-wf-sa-083 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Undefined NOTATION n.
|
Sections [Rules]:
|
4.2.2 [76] |
Test ID:
|
o-p76fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required before "NDATA"
|
Sections [Rules]:
|
4.2.2 [76] |
Test ID:
|
o-p76fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
"NDATA" is upper-case
|
Sections [Rules]:
|
4.2.2 [76] |
Test ID:
|
o-p76fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
notation name is required
|
Sections [Rules]:
|
4.2.2 [76] |
Test ID:
|
o-p76fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
notation names are Names
|
Sections [Rules]:
|
4.2 [70] |
Test ID:
|
not-wf-sa-109 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Tags invalid within EntityDecl.
|
Sections [Rules]:
|
4.2 [70] |
Test ID:
|
o-p70fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
This is neither
|
Sections [Rules]:
|
4.2 [71] |
Test ID:
|
not-wf-sa-062 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Entity declarations need space after the entity name.
|
Sections [Rules]:
|
4.2 [71] |
Test ID:
|
o-p71fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required before EntityDef
|
Sections [Rules]:
|
4.2 [71] |
Test ID:
|
o-p71fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Entity name is a Name, not an NMToken
|
Sections [Rules]:
|
4.2 [71] |
Test ID:
|
o-p71fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no S after "<!"
|
Sections [Rules]:
|
4.2 [71] |
Test ID:
|
o-p71fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required after "<!ENTITY"
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
not-wf-sa-165 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Parameter entity declarations must have a space before
the '%'.
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
o-p72fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required after "<!ENTITY"
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
o-p72fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required after '%'
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
o-p72fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
S is required after name
|
Sections [Rules]:
|
4.2 [72] |
Test ID:
|
o-p72fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Entity name is a name, not an NMToken
|
Sections [Rules]:
|
4.2 [73] |
Test ID:
|
o-p73fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
No typed replacement text
|
Sections [Rules]:
|
4.2 [73] |
Test ID:
|
o-p73fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Only one replacement value
|
Sections [Rules]:
|
4.2 [73] |
Test ID:
|
o-p73fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
No NDataDecl on replacement text
|
Sections [Rules]:
|
4.2 [73] |
Test ID:
|
o-p73fail4 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
Value is required
|
Sections [Rules]:
|
4.2 [73] |
Test ID:
|
o-p73fail5 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
No NDataDecl without value
|
Sections [Rules]:
|
4.2 [74] |
Test ID:
|
not-wf-sa-089 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Parameter entities "are" always parsed; NDATA annotations
are not permitted.
|
Sections [Rules]:
|
4.2 [74] |
Test ID:
|
not-wf-sa-091 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Parameter entities "are" always parsed; NDATA annotations
are not permitted.
|
Sections [Rules]:
|
4.2 [74] |
Test ID:
|
o-p74fail1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
no NDataDecls on parameter entities
|
Sections [Rules]:
|
4.2 [74] |
Test ID:
|
o-p74fail2 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
value is required
|
Sections [Rules]:
|
4.2 [74] |
Test ID:
|
o-p74fail3 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
only one value
|
Sections [Rules]:
|
4.3.1 [77] |
Test ID:
|
decl01 |
Entities:
|
parameter
|
Collection:
|
Sun Microsystems XML Tests |
|
External entities may not have standalone decls.
|
Sections [Rules]:
|
4.3.1 [77] |
Test ID:
|
dtd07 |
Collection:
|
Sun Microsystems XML Tests |
|
Text declarations (which optionally begin any external entity)
are required to have "encoding=...".
|
Sections [Rules]:
|
4.3.1 [77] |
Test ID:
|
encoding07 |
Collection:
|
Sun Microsystems XML Tests |
|
Text declarations (which optionally begin any external entity)
are required to have "encoding=...".
|
Sections [Rules]:
|
4.3.1 4.3.2 [77, 78] |
Test ID:
|
not-wf-ext-sa-002 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
External entities have "text declarations", which do
not permit the "standalone=..." attribute that's allowed
in XML declarations.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-074 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Internal general parsed entities are only well formed if
they match the "content" production.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-103 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
End-tag required for element foo.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-104 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Internal general parsed entities are only well formed if
they match the "content" production.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-116 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Internal general parsed entities are only well formed if
they match the "content" production. This is a partial
character reference, not a full one.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-117 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Internal general parsed entities are only well formed if
they match the "content" production. This is a partial
character reference, not a full one.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-119 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Internal general parsed entities are only well formed if
they match the "content" production. This is a partial
character reference, not a full one.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-153 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Text declarations may not begin internal parsed entities;
they may only appear at the beginning of external parsed
(parameter or general) entities.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-181 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Internal parsed entities must match the content
production to be well formed.
|
Sections [Rules]:
|
4.3.2 |
Test ID:
|
not-wf-sa-182 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Internal parsed entities must match the content
production to be well formed.
|
Sections [Rules]:
|
4.3.2 [79] |
Test ID:
|
not-wf-not-sa-007 |
Entities:
|
both
|
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
A <!DOCTYPE ...> declaration may not begin any external
entity; it's only found once, in the document entity.
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
not-wf-sa-101 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Space is not permitted in an encoding name.
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
encoding01 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal character " " in encoding name
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
encoding02 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal character "/" in encoding name
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
encoding03 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal character reference in encoding name
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
encoding04 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal character ":" in encoding name
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
encoding05 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal character "@" in encoding name
|
Sections [Rules]:
|
4.3.3 [81] |
Test ID:
|
encoding06 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal character "+" in encoding name
|
Sections [Rules]:
|
4.5 |
Test ID:
|
not-wf-sa-092 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
The replacement text of this entity has an illegal reference,
because the character reference is expanded immediately.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
not-wf-sa-115 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
The replacement text of this entity is an illegal character
reference, which must be rejected when it is parsed in the
context of an attribute value.
|
Sections [Rules]:
|
4.5 |
Test ID:
|
not-wf-sa-120 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Character references are expanded in the replacement text of
an internal entity, which is then parsed as usual. Accordingly,
& must be doubly quoted - encoded either as &
or as &#38;.
|
Sections [Rules]:
|
41. [68] |
Test ID:
|
not-wf-sa-077 |
Collection:
|
James Clark XMLTEST cases, 18-Nov-1998 |
|
Undefined ENTITY bar.
|
3.4 XML Documents with Optional Errors
Conforming XML 1.0 Processors are permitted to ignore
certain errors, or to report them at user option. In this
section of this test report are found descriptions of
test cases which fit into this category.
Processor behavior on such test cases does not affect
conformance to the XML 1.0 Recommendation, except as noted.
Sections [Rules]:
|
2.11 [33] |
Test ID:
|
lang01 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal language identification
|
Sections [Rules]:
|
2.11 [33] |
Test ID:
|
lang02 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal language identification
|
Sections [Rules]:
|
2.11 [33] |
Test ID:
|
lang03 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal language identification
|
Sections [Rules]:
|
2.11 [33] |
Test ID:
|
lang04 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal language identification
|
Sections [Rules]:
|
2.11 [33] |
Test ID:
|
lang05 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal language identification
|
Sections [Rules]:
|
2.11 [33] |
Test ID:
|
lang06 |
Collection:
|
Sun Microsystems XML Tests |
|
Illegal language identification
|
Sections [Rules]:
|
2.3, 4.2.2 [11] |
Test ID:
|
o-p11pass1 |
Collection:
|
OASIS/NIST TESTS, 1-Nov-1998 |
|
system literals may not contain
URI fragments
|
Sections [Rules]:
|
2.8 |
Test ID:
|
pe01 |
Collection:
|
Sun Microsystems XML Tests |
|
Parameter entities must consist of a series of complete markup
declarations of the types allowed by the nonterminal
markupdecl, interespersed with whitespace or PERefs.
|
Sections [Rules]:
|
4.2.2 [75] |
Test ID:
|
uri01 |
Collection:
|
Sun Microsystems XML Tests |
|
SYSTEM ids may not have URI fragments
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
pr-xml-euc-jp |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for the EUC-JP encoding, and for text
which relies on Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
(Also requires ability to process a moderately complex DTD.)
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
pr-xml-iso-2022-jp |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for the ISO-2022-JP encoding, and for text
which relies on Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
(Also requires ability to process a moderately complex DTD.)
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
pr-xml-shift_jis |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for the Shift_JIS encoding, and for text
which relies on Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
(Also requires ability to process a moderately complex DTD.)
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
weekly-euc-jp |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for EUC-JP encoding, and
XML names which contain Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
weekly-iso-2022-jp |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for ISO-2022-JP encoding, and
XML names which contain Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
|
Sections [Rules]:
|
4.3.3 [4,84] |
Test ID:
|
weekly-shift_jis |
Collection:
|
Fuji Xerox Japanese Text Tests |
|
Test support for Shift_JIS encoding, and
XML names which contain Japanese characters.
If a processor does not support this encoding, it must
report a fatal error.
|
4. Contributors (Non-normative)
A team of volunteer members have participated in the
development of this work. Contributions have come from:
- Murry Altheim, Sun Microsystems
- Mary Brady, NIST
- Tim Boland, NIST
- David Brownell, Sun Microsystems
- James Clark
- Karin Donker, IBM
- Irina Golfman, Inera Incorporated
- Tony Graham, Mulberry Technologies
- G. Ken Holman, Crane Softwrights Ltd
- Alex Milowski, Veo Systems, Inc
- Makota Murata, Fuji Xerox
- Miles O'Reilly, Microstar Software, Ltd
- Matt Timmermans, Microstar Software, Ltd
- Richard Rivello, NIST
- Lynne Rosenthal, NIST
- Brian Schellar, Chrystal Software
- Bill Smith, Sun Microsystems
- Trevor Veary, Software AG
End
[an error occurred while processing this directive]