This document is the output of an XML test harness. It reports on the conformance of the following XML 1.0 processor configuration, as reported through the Java version of the SAX (Simple API for XML) parser interface. For SAX 2.0 (alpha) processors, the processing mode and entity handling values could be non-default values, if such a feature is supported by that processor. For SAX 1.0 processors, those values were as reported to the test harness by its operator.
| XML Processor | Datachannel DCXJP (Version 15-Apr-99) |
| SAX Parser Class | com.datachannel.xml.sax.SAXDriver |
| Processing Mode | Non-Validating |
| General Entities | included |
| Parameter Entities | included |
The test harness and execution environment was:
| Test Run Date | Tue Sep 07 07:58:22 PDT 1999 |
| Harness and Version | org.brownell.xml.conformance.Driver (alpha; 3-September-1999) |
| Java VM Info | build JDK-1.2.1-A, native threads, symcjit |
| Suite of Testcases | OASIS Conformance Tests, v1.0 |
An summary of test results follows. To know the actual test status, someone must examine the result of each passed negative test to make sure it failed for the right reason. That examination may cause the counts of failed tests to increase, changing a provisional "conforms" status to a "does not conform".
| Status | DOES NOT CONFORM |
| Total Passed Tests (provisional) | 627 |
| Passed Negative Tests (provisional) | 390 |
| Failed Tests (provisional) | 438 |
| Tests Skipped | 0 |
Sections of this report are: Explanation of Tables; Positive Tests, cases where this processor should report no errors; Negative Tests, documents for which this processor must report the known errors; and Informative Tests, documents with errors which processors are not required to report.
NOTE: The OASIS/NIST test suite is currently in draft state, and can't actually be used without modifications to the configuration file, which is used both to generate the test documentation published at the OASIS/NIST site and to operate this test harness. Accordingly, treat these results as preliminary.
Sections presenting test results are composed largely of tables, with explanations focussing on exactly what those tables indicate. Diagnostics for failed tests are presented in italics, with a cherry colored background, to highlight the result. Diagnostics for succesful tests should as a rule only exist for negative tests. Diagnostics with parenthesized comments indicate the reporting path:
In all cases, negative tests that appear to pass (diagnostics presented with a white background) must be individually examined in the report below. The diagnostic provided by the processor must correspond to the description of the test provided; if the processor does not report the matching error, the seeming "pass" is in fact an error of a type the test harness could not detect or report. That error is either a conformance bug, or an error in the diagnostic being produced, or sometimes both.
Nonvalidating processors may skip some tests if the tests require processing a class of external entities (general, parameter, or both) which that processor is known not to handle. If processor handling of entities is not known, all such tests are skipped, in order to prevent misreporting.
Note also that some SAX processors (or drivers for non-SAX processors) appear to have a bug wherein they don't close all of the files which they open. When running this test harness with large numbers of tests, failures at the end of this report could reflect such bugs in SAX conformance more than bugs in XML processor conformance.
All conformant XML 1.0 processors must accept "valid" input documents without reporting any errors, and moreover must report the correct output data to the application when processing those documents. Nonvalidating processors (such as this one) must also accept "invalid" input documents without reporting any errors. These are called "Positive Tests" because they ensure that the processor just "does the right thing" without reporting any problems.
In the interest of brevity, the only tests listed here are those which produce diagnostics of some kind, such as test failures. In some cases, warnings may be reported when processing these documents, but these do not indicate failures.
No interpretation of these results is necessary; every "error" or "fatal" message presented here is an XML conformance failure. Maintainers of an XML processor will generally want to fix their software so that it conforms fully to the XML specification.
All XML processors must accept all valid documents. This group of tests must accordingly produce no test failures.
| Section and [Rules] | Test ID | Description | Diagnostic |
| 2.10 | valid-sa-093 | Test demonstrates that extra whitespace is not intended for inclusion in the delivered version of the document. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/093.xml) |
| 2.11 | valid-ext-sa-001 | A combination of carriage return line feed in an external entity must be normalized to a single newline. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/001.xml) |
| 2.11 | valid-ext-sa-002 | A carriage return (also CRLF) in an external entity must be normalized to a single newline. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/002.xml) |
| 2.11 | valid-ext-sa-004 | A carriage return (also CRLF) in an external entity must be normalized to a single newline. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/004.xml) |
| 2.11 | valid-ext-sa-009 | A carriage return (also CRLF) in an external entity must be normalized to a single newline. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/009.xml) |
| 2.11 | valid-sa-116 | Test demonstrates that a line break within CDATA will be normalized. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/116.xml) |
| 2.11 3.2.1 3.2.2 4.2.2 [48] [51] [75] | valid-ext-sa-006 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/006.xml) |
| 2.11 4.2.2 [75] | valid-ext-sa-011 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/011.xml) |
| 2.11, 3.3.3 | valid-sa-108 | This tests normalization of end-of-line characters (CRLF) within entities to LF, primarily as an output test. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/108.xml) |
| 2.11, 4.5 | valid-sa-068 | Tests definition of an entity holding a carriage return character reference, which must be normalized to a newline before being reported to the application. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/068.xml) |
| 2.12 [35] | v-lang01 | Tests a lowercase ISO language code. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/v-lang01.xml) |
| 2.12 [35] | v-lang02 | Tests a ISO language code with a subcode. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/v-lang02.xml) |
| 2.12 [35] | v-lang05 | Tests an uppercase ISO language code. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/v-lang05.xml) |
| 2.12 [36] | v-lang03 | Tests a IANA language code with a subcode. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/v-lang03.xml) |
| 2.12 [37] | v-lang04 | Tests a user language code with a subcode. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/v-lang04.xml) |
| 2.12 [37] | v-lang06 | Tests a user language code. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/v-lang06.xml) |
| 2.2 [1] | o-p01pass2 | various Misc items where they can occur | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 8, position 4, file:/d:/xml/xmlconf/oasis/p01pass2.xml) |
| 2.2 [2] | valid-sa-049 | Test demonstrates that characters outside of normal ascii range can be used as element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/049.xml) |
| 2.2 [2] | valid-sa-050 | Test demonstrates that characters outside of normal ascii range can be used as element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/050.xml) |
| 2.2 [2] | valid-sa-051 | The document is encoded in UTF-16 and uses some name characters well outside of the normal ASCII range. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/051.xml) |
| 2.2 [2] | valid-sa-052 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/052.xml) |
| 2.3 2.10 | valid-sa-092 | Test demostrates that extra whitespace is normalized into a single space character. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/092.xml) |
| 2.3 3.1 [10][40][41] | valid-sa-109 | Test demonstrates that an attribute can have a null value. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/109.xml) |
| 2.3 3.1 [13] [40] | valid-sa-013 | Test demonstrates that the Attribute in a Start-tag can consist of numerals along with special characters. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/013.xml) |
| 2.3 3.1 [13] [40] | valid-sa-014 | Test demonstrates that all lower case letters are valid for the Attribute in a Start-tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/014.xml) |
| 2.3 3.1 [13] [40] | valid-sa-015 | Test demonstrates that all upper case letters are valid for the Attribute in a Start-tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/015.xml) |
| 2.3 3.1 [43] | valid-sa-009 | Test demonstrates that PubidChar can be used for element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/009.xml) |
| 2.3 4.1 [10] [69] | valid-not-sa-023 | Test demonstrates the use of a parameter entity reference within an attribute list declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/023.xml) |
| 2.3 [12] | o-p12pass1 | valid public IDs. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/oasis/p12pass1.xml) |
| 2.3 [12] | valid-sa-100 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/100.xml) |
| 2.3 [4] | valid-sa-012 | Uses a legal XML 1.0 name consisting of a single colon character (disallowed by the latest XML Namespaces draft). | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/012.xml) |
| 2.3 [5] | valid-sa-063 | The document is encoded in UTF-8 and the name of the root element type uses non-ASCII characters. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/063.xml) |
| 2.3 [6] | o-p06pass1 | various satisfactions of the Names production in a NAMES attribute | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p06pass1.xml) |
| 2.3 [7] | o-p07pass1 | various valid Nmtoken 's in an attribute list declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p07pass1.xml) |
| 2.3 [8] | o-p08pass1 | various satisfaction of an NMTOKENS attribute value. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p08pass1.xml) |
| 2.3 [9] | o-p09pass1 | valid EntityValue's. Except for entity references, markup is not recognized. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p09pass1.xml) |
| 2.4 2.5 2.6 2.7 [15] [16] [18] | o-p43pass1 | Valid use of character data, comments, processing instructions and CDATA sections within the start and end tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p43pass1.xml) |
| 2.4 2.7 [18] | empty | Whitespace found in CDATA sections and entity references works is treated like other optional whitespace | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 8, position 4, file:/d:/xml/xmlconf/sun/valid/empty.xml) |
| 2.4 3.1 [14] [43] | valid-sa-048 | Test demonstrates that character data is valid element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/048.xml) |
| 2.4 3.1 [43] | valid-sa-008 | Test demonstrates character references can be used for element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/008.xml) |
| 2.5 | valid-sa-119 | Comments may contain any legal XML characters; only the string "--" is disallowed. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/119.xml) |
| 2.5 3.1 [15] [43] | valid-sa-021 | Test demonstrates that comments are valid element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/021.xml) |
| 2.5 3.1 [15] [43] | valid-sa-022 | Test demonstrates that comments are valid element content and that all characters before the double-hypen right angle combination are considered part of thecomment. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/022.xml) |
| 2.5 [15] | dtd01 | Comments don't get parameter entity expansion | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/dtd01.xml) |
| 2.6 2.10 [16] | valid-sa-055 | Test demonstrates that extra whitespace within a processing instruction willnormalized into s single space character. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/055.xml) |
| 2.6 2.10 [16] | valid-sa-098 | Test demonstrates that extra whitespace within a processing instruction is converted into a single space character. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/098.xml) |
| 2.6 3.1 [16] [43] | valid-sa-016 | Test demonstrates that Processing Instructions are valid element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/016.xml) |
| 2.6 3.1 [16] [43] | valid-sa-017 | Test demonstrates that Processing Instructions are valid element content and there can be more than one. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/017.xml) |
| 2.6 [15] | valid-sa-037 | Test demonstrates a valid comment and that it may appear anywhere in the document including at the end. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/037.xml) |
| 2.6 [15] | valid-sa-038 | Test demonstrates a valid comment and that it may appear anywhere in the document including the beginning. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/038.xml) |
| 2.6 [16] | valid-sa-036 | Test demonstrates a valid processing instruction. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/036.xml) |
| 2.6 [16] | valid-sa-039 | Test demonstrates a valid processing instruction and that it may appear at the beginning of the document. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/039.xml) |
| 2.7 | valid-not-sa-031 | 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). | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/031.xml) |
| 2.7 3.1 [18] [43] | valid-sa-018 | Test demonstrates that CDATA sections are valid element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/018.xml) |
| 2.7 3.1 [18] [43] | valid-sa-019 | Test demonstrates that CDATA sections are valid element content and that ampersands may occur in their literal form. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/019.xml) |
| 2.7 3.1 [18] [43] | valid-sa-020 | Test demonstractes that CDATA sections are valid element content and that everyting between the CDStart and CDEnd is recognized as character data not markup. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/020.xml) |
| 2.7 [20] | valid-sa-114 | Test demonstrates that all text within a valid CDATA section is considered text and not recognized as markup. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/114.xml) |
| 2.8 3.4 4.2.2 [31] [62] [63] [75] | o-p31pass2 | Valid doctypedecl with EXternalID as Enternal Entity. The external entity contains a parameter entity reference and condtional sections. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p31pass2.xml) |
| 2.8 4.1 [28] [69] | o-p28pass3 | Valid doctypedecl with Parameter entity reference. The declaration of a parameter entity must precede any reference to it. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p28pass3.xml) |
| 2.8 4.1 [28] [69] | o-p28pass5 | Valid doctypedecl with ExternalID as an External Entity. A parameter entity reference is also used. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p28pass5.xml) |
| 2.8 4.2.2 4.3.1 [30] [75] [77] | o-p30pass2 | Valid doctypedecl with ExternalID as an Enternal Entity. The external entity begins with a Text Declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p30pass2.xml) |
| 2.8 4.2.2 [28] [75] | o-p28pass4 | Valid doctypedecl with ExternalID as an External Entity declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p28pass4.xml) |
| 2.8 4.2.2 [30] [75] | o-p30pass1 | Valid doctypedecl with ExternalID as an External Entity. The external entity has an element declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p30pass1.xml) |
| 2.8 [22] | o-p22pass4 | XML decl and doctypedecl | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/oasis/p22pass4.xml) |
| 2.8 [22] | o-p22pass5 | just doctypedecl | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/oasis/p22pass5.xml) |
| 2.8 [22] | o-p22pass6 | S between decls is not required | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 26, file:/d:/xml/xmlconf/oasis/p22pass6.xml) |
| 2.8 [23] | valid-sa-033 | Test demonstrates that both a EncodingDecl and SDDecl are valid within the prolog. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/033.xml) |
| 2.8 [24] | valid-sa-028 | Test demonstrates a valid prolog that uses double quotes as delimeters around the VersionNum. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/028.xml) |
| 2.8 [24] | valid-sa-029 | Test demonstrates a valid prolog that uses single quotes as delimters around the VersionNum. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/029.xml) |
| 2.8 [25] | valid-sa-030 | Test demonstrates a valid prolog that contains whitespace on both sides of the equal sign in the VersionInfo. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/030.xml) |
| 2.8 [29] | o-p29pass1 | Valid types of markupdecl. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p29pass1.xml) |
| 2.8 [31] | o-p31pass1 | external subset can be empty | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p31pass1.xml) |
| 2.8, 4.1 [69] | valid-not-sa-024 | Constructs an <!ATTLIST...> declaration from several PEs. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/024.xml) |
| 2.9 | not-sa01 | A non-standalone document is valid if declared as such. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/not-sa01.xml) |
| 2.9 | not-sa02 | A non-standalone document is valid if declared as such. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/not-sa02.xml) |
| 2.9 | not-sa03 | A non-standalone document is valid if declared as such. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/not-sa03.xml) |
| 2.9 | not-sa04 | A non-standalone document is valid if declared as such. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/not-sa04.xml) |
| 2.9 [32] | sa01 | A document may be marked 'standalone' if any optional whitespace is defined within the internal DTD subset. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/sa01.xml) |
| 2.9 [32] | sa02 | A document may be marked 'standalone' if any attributes that need normalization are defined within the internal DTD subset. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/sa02.xml) |
| 2.9 [32] | sa03 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/sa03.xml) |
| 2.9 [32] | sa04 | Like sa03 but relies on attribute defaulting defined in the internal subset. On output, requires notations to be correctly reported. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/sa04.xml) |
| 2.9 [32] | sa05 | Like sa01 but this document is standalone since it has no optional whitespace. On output, requires notations to be correctly reported. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 3, position 4, file:/d:/xml/xmlconf/sun/valid/sa05.xml) |
| 2.9 [32] | valid-sa-032 | Test demonstrates a valid SDDecl within the prolog. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/032.xml) |
| 3 | element | Tests clauses 1, 3, and 4 of the Element Valid validity constraint. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/element.xml) |
| 3 3.2.1 [47] | optional | Tests declarations of "children" content models, and the validity constraints associated with them. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/optional.xml) |
| 3.1 4.1 [43] [66] | valid-sa-024 | Test demonstrates that Entity References are valid element content and also demonstrates a valid Entity Declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/024.xml) |
| 3.1 4.1 [43] [68] | valid-ext-sa-003 | Test demonstrates that the content of an element can be empty. In this case the external entity is an empty file. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/003.xml) |
| 3.1 4.6 [43] | valid-sa-007 | Test demonstrates numeric character references can be used for element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/007.xml) |
| 3.1 [40] | valid-sa-002 | Test demonstrates that whitespace is permitted after the tag name in a Start-tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/002.xml) |
| 3.1 [40] | valid-sa-005 | Test demonstrates a valid attribute specification within a Start-tag that contains whitespace on both sides of the equal sign. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/005.xml) |
| 3.1 [40] | valid-sa-010 | Test demonstrates that whitespace is valid after the Attribute in a Start-tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/010.xml) |
| 3.1 [40] | valid-sa-011 | Test demonstrates mutliple Attibutes within the Start-tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/011.xml) |
| 3.1 [40] | valid-sa-104 | Test demonstrates that extra whitespace within an Attribute of a Start-tag is normalized to a single space character. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/104.xml) |
| 3.1 [40] [42] | valid-sa-054 | Test demonstrates that extra whitespace within Start-tags and End-tags are nomalized into single spaces. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/054.xml) |
| 3.1 [41] | valid-sa-004 | Test demonstrates a valid attribute specification within a Start-tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/004.xml) |
| 3.1 [41] | valid-sa-006 | Test demonstrates that the AttValue within a Start-tag can use a single quote as a delimter. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/006.xml) |
| 3.1 [42] | valid-sa-003 | Test demonstrates that whitespace is permitted after the tag name in an End-tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/003.xml) |
| 3.1 [43] | valid-sa-023 | Test demonstrates that Entity References are valid element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/023.xml) |
| 3.1 [43] | valid-sa-047 | Test demonstrates that extra whitespace is normalized into single space character. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/047.xml) |
| 3.1 [43] [44] | o-p28pass1 | Empty-element tag must be used for element which are declared EMPTY. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p28pass1.xml) |
| 3.1 [44] | valid-sa-034 | Test demonstrates the correct syntax for an Empty element tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/034.xml) |
| 3.1 [44] | valid-sa-035 | Test demonstrates that whitespace is permissible after the name in an Empty element tag. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/035.xml) |
| 3.1 [44] | valid-sa-044 | Test demonstrates that the empty-element tag must be use for an elements that are declared EMPTY. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/044.xml) |
| 3.2 3.2.1 3.2.2 [45] [46] [47] [51] | o-p46pass1 | Valid use of contentspec, element content models, and mixed content within an element type declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p46pass1.xml) |
| 3.2 3.2.1 [45] [46] [47] | o-p48pass1 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p48pass1.xml) |
| 3.2 3.2.1 [45] [46] [47] | o-p49pass1 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p49pass1.xml) |
| 3.2 3.2.1 [45] [46] [47] | o-p50pass1 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p50pass1.xml) |
| 3.2 3.2.1 [45] [46] [47] | o-p47pass1 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p47pass1.xml) |
| 3.2 3.3 [46] [53] | valid-sa-059 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/059.xml) |
| 3.2 [45] | o-p45pass1 | valid element declarations | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p45pass1.xml) |
| 3.2 [46] | valid-sa-025 | Test demonstrates an Element Type Declaration and that the contentspec can be of mixed content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/025.xml) |
| 3.2 [46] | valid-sa-026 | Test demonstrates an Element Type Declaration and that EMPTY is a valid contentspec. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/026.xml) |
| 3.2 [46] | valid-sa-027 | Test demonstrates an Element Type Declaration and that ANY is a valid contenspec. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/027.xml) |
| 3.2.1 4.2.2 [48] [75] | valid-ext-sa-005 | Test demonstrates the use of optional character and content particles within an element content. The test also show the use of external entity. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/005.xml) |
| 3.2.1 [47] | valid-sa-057 | Test demonstrates an element content model whose element can occur zero or more times. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/057.xml) |
| 3.2.1 [48][49] | valid-sa-112 | Test demonstrates shows the use of content particles within the element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/112.xml) |
| 3.2.1 [50] | valid-sa-081 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/081.xml) |
| 3.2.2 [51] | dtd00 | Tests parsing of alternative forms of text-only mixed content declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/dtd00.xml) |
| 3.2.2 [51] | o-p51pass1 | valid Mixed contentspec's. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p51pass1.xml) |
| 3.2.2 [51] | valid-sa-001 | Test demonstrates an Element Type Declaration with Mixed Content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/001.xml) |
| 3.3 | valid-sa-043 | An element's attributes may be declared before its content model; and attribute values may contain newlines. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/043.xml) |
| 3.3 | valid-sa-097 | Basically an output test, this tests whether an externally defined attribute declaration (with a default) takes proper precedence over a subsequent internal declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/097.xml) |
| 3.3 3.3.1 [52] [54] | valid-sa-040 | Test demonstrates an Attribute List declaration that uses a StringType as the AttType. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/040.xml) |
| 3.3 3.3.1 [52] [54] | valid-sa-077 | Test demonstrates that an AttlistDecl can use an EnumeratedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/077.xml) |
| 3.3 3.3.1 [52] [54] | valid-sa-078 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/078.xml) |
| 3.3 3.3.1 [52] [56] | valid-sa-071 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/071.xml) |
| 3.3 3.3.1 [52] [56] | valid-sa-072 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/072.xml) |
| 3.3 3.3.1 [52] [56] | valid-sa-073 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/073.xml) |
| 3.3 3.3.1 [52] [56] | valid-sa-074 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/074.xml) |
| 3.3 3.3.1 [52] [56] | valid-sa-075 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/075.xml) |
| 3.3 3.3.2 [52] [60] | valid-sa-079 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/079.xml) |
| 3.3 3.3.2 [52] [60] | valid-sa-080 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/080.xml) |
| 3.3 [52] | o-p52pass1 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p52pass1.xml) |
| 3.3 [52] | valid-not-sa-006 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/006.xml) |
| 3.3 [52] | valid-not-sa-007 | Test demonstrates the use of an Attribute list declaration within an external entity. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/007.xml) |
| 3.3 [52] | valid-not-sa-010 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/010.xml) |
| 3.3 [52] | valid-not-sa-026 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/026.xml) |
| 3.3 [52] | valid-sa-045 | Tests whether more than one definition can be provided for the same attribute of a given element type with the first declaration being binding. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/045.xml) |
| 3.3 [52] | valid-sa-046 | Test demonstrates that when more than one AttlistDecl is provided for a given element type, the contents of all those provided are merged. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/046.xml) |
| 3.3 [52][53] | valid-sa-113 | Test demonstrates that it is not an error to have attributes declared for an element not itself declared. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/113.xml) |
| 3.3 [53] | o-p53pass1 | a valid AttDef | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p53pass1.xml) |
| 3.3.1 | valid-sa-076 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/076.xml) |
| 3.3.1 | valid-sa-090 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/090.xml) |
| 3.3.1 | valid-sa-091 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/091.xml) |
| 3.3.1 4.1 [54] [66] | valid-sa-041 | Test demonstrates an Attribute List declaration that uses a StringType as the AttType and also expands the CDATA attribute with a character reference. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/041.xml) |
| 3.3.1 4.1 [54] [66] | valid-sa-042 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/042.xml) |
| 3.3.1 4.1 [54] [66] | valid-sa-056 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/056.xml) |
| 3.3.1 [54] | o-p54pass1 | the three kinds of attribute types | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p54pass1.xml) |
| 3.3.1 [55] | o-p55pass1 | StringType = "CDATA" | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p55pass1.xml) |
| 3.3.1 [56] | o-p56pass1 | the 7 tokenized attribute types | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p56pass1.xml) |
| 3.3.1 [57] | o-p57pass1 | enumerated types are NMTOKEN or NOTATION lists | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p57pass1.xml) |
| 3.3.1 [58] | o-p58pass1 | NOTATION enumeration has on or more items | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p58pass1.xml) |
| 3.3.1 [59] | o-p59pass1 | NMTOKEN enumerations haveon or more items | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p59pass1.xml) |
| 3.3.1 [59] | v-sgml01 | XML permits token reuse, while SGML does not. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/sgml01.xml) |
| 3.3.2 [60] | o-p60pass1 | the four types of default values | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p60pass1.xml) |
| 3.3.2 [60] | required00 | Tests the #REQUIRED attribute declaration syntax, and the associated validity constraint. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/required00.xml) |
| 3.3.3 | valid-ext-sa-013 | Test demonstrates that whitespace is handled by adding a single whitespace to the normalized value in the attribute list. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/013.xml) |
| 3.3.3 | valid-sa-058 | Test demonstrates that extra whitespace be normalized into a single space character in an attribute of type NMTOKENS. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/058.xml) |
| 3.3.3 | valid-sa-095 | Basically an output test, this requires extra whitespace to be normalized into a single space character in an attribute of type NMTOKENS. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/095.xml) |
| 3.3.3 | valid-sa-096 | Test demonstrates that extra whitespace is normalized into a single space character in an attribute of type NMTOKENS. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/096.xml) |
| 3.3.3 | valid-sa-102 | Test demonstrates that a CDATA attribute can pass a double quote as its value. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/102.xml) |
| 3.3.3 | valid-sa-103 | Test demonstrates that an attribute can pass a less than sign as its value. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/103.xml) |
| 3.3.3 | valid-sa-105 | Basically an output test, this requires a CDATA attribute with a tab character to be passed through as one space. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/105.xml) |
| 3.3.3 | valid-sa-106 | Basically an output test, this requires a CDATA attribute with a newline character to be passed through as one space. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/106.xml) |
| 3.3.3 | valid-sa-107 | Basically an output test, this requires a CDATA attribute with a return character to be passed through as one space. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/107.xml) |
| 3.3.3 | valid-sa-110 | Basically an output test, this requires that a CDATA attribute with a CRLF be normalized to one space. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/110.xml) |
| 3.3.3 | valid-sa-111 | Character references expanding to spaces doesn't affect treatment of attributes. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/111.xml) |
| 3.3.3 | valid-sa-115 | Test demonstrates that an entity reference is processed by recursively processing the replacement text of the entity. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/115.xml) |
| 3.4 [61] | o-p61pass1 | valid conditional sections are INCLUDE and IGNORE | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p61pass1.xml) |
| 3.4 [62] | o-p62pass1 | valid INCLUDE sections -- options S before and after keyword, sections can nest | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p62pass1.xml) |
| 3.4 [62] | valid-not-sa-013 | Test demonstrates the use of the conditional section INCLUDE that will include its contents as part of the DTD. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/013.xml) |
| 3.4 [62] | valid-not-sa-014 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/014.xml) |
| 3.4 [62] | valid-not-sa-016 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/016.xml) |
| 3.4 [62] | valid-not-sa-022 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/022.xml) |
| 3.4 [62] | valid-not-sa-028 | Test demonstrates the use of the conditional section INCLUDE that will include its contents. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/028.xml) |
| 3.4 [62] | valid-not-sa-029 | Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being used. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/029.xml) |
| 3.4 [62] | valid-not-sa-030 | Test demonstrates the use of the conditonal section IGNORE the will ignore its content from being used. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/030.xml) |
| 3.4 [63] | o-p63pass1 | valid IGNORE sections | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p63pass1.xml) |
| 3.4 [63] | valid-not-sa-015 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/015.xml) |
| 3.4 [64] | o-p64pass1 | IGNOREd sections ignore everything except section delimiters | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p64pass1.xml) |
| 4 | valid-sa-085 | Parameter and General entities use different namespaces, so there can be an entity of each type with a given name. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/085.xml) |
| 4.1 4.4.3 [68] | valid-ext-sa-014 | Test demonstrates use of characters outside of normal ASCII range. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/014.xml) |
| 4.1 [66] | valid-sa-060 | Test demonstrates the use of decimal Character References within element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/060.xml) |
| 4.1 [66] | valid-sa-061 | Test demonstrates the use of decimal Character References within element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/061.xml) |
| 4.1 [66] | valid-sa-062 | Test demonstrates the use of hexadecimal Character References within element. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/062.xml) |
| 4.1 [66] | valid-sa-064 | Tests in-line handling of two legal character references, which each expand to a Unicode surrogate pair. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/064.xml) |
| 4.1 [66] | valid-sa-066 | Expands a CDATA attribute with a character reference. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/066.xml) |
| 4.1 [66] | valid-sa-067 | Test demonstrates the use of decimal character references within element content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/067.xml) |
| 4.1 [66] | valid-sa-089 | Tests entity expansion of three legal character references, which each expand to a Unicode surrogate pair. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/089.xml) |
| 4.1 [68] | o-p68pass1 | Valid entity references. Also ensures that a charref to '&' isn't interpreted as an entity reference open delimiter | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p68pass1.xml) |
| 4.1 [69] | o-p69pass1 | Valid PEReferences. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p69pass1.xml) |
| 4.1 [69] | valid-not-sa-003 | Test demonstrates the expansion of an external parameter entity that declares an attribute. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/003.xml) |
| 4.1 [69] | valid-not-sa-004 | Expands an external parameter entity in two different ways, with one of them declaring an attribute. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/004.xml) |
| 4.1 [69] | valid-not-sa-005 | Test demonstrates the expansion of an external parameter entity that declares an attribute. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/005.xml) |
| 4.1 [69] | valid-not-sa-027 | Test demonstrates a parameter entity reference whose value is NULL. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/027.xml) |
| 4.2 | valid-not-sa-025 | Test demonstrates that when more that one definition is provided for the same entity only the first declaration is binding. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/025.xml) |
| 4.2 | valid-sa-086 | Tests whether entities may be declared more than once, with the first declaration being the binding one. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/086.xml) |
| 4.2 4.2.1 [72] [75] | valid-not-sa-011 | Test demonstrates a parameter entity declaration whose parameter entity definition is an ExternalID. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/011.xml) |
| 4.2 [70] | o-p70pass1 | An EntityDecl is either a GEDecl or a PEDecl | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p70pass1.xml) |
| 4.2 [71] | o-p71pass1 | Valid GEDecls | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p71pass1.xml) |
| 4.2 [72] | o-p72pass1 | Valid PEDecls | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p72pass1.xml) |
| 4.2 [72] | valid-not-sa-017 | Test demonstrates a parameter entity declaration that contains an attribute list declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/017.xml) |
| 4.2 [72] | valid-not-sa-021 | Test demonstrates a parameter entity declaration that contains a partial attribute list declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/021.xml) |
| 4.2 [72] | valid-sa-082 | Tests that an external PE may be defined (but not referenced). | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/082.xml) |
| 4.2 [72] | valid-sa-083 | Tests that an external PE may be defined (but not referenced). | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/083.xml) |
| 4.2 [73] | o-p73pass1 | EntityDef is either Entity value or an external id, with an optional NDataDecl | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p73pass1.xml) |
| 4.2.1 4.2.2 | valid-ext-sa-012 | Test demonstrates both internal and external entities and that processing of entity references may be required to produce the correct replacement text. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/012.xml) |
| 4.2.2 4.3.3. 4.4.3 [75] [80] | valid-ext-sa-008 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/008.xml) |
| 4.2.2 4.4.3 [75] | valid-ext-sa-007 | Test demonstrates the use of external entity and how replacement text is retrieved and processed. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/ext-sa/007.xml) |
| 4.2.2 [75] | valid-not-sa-001 | Test demonstrates the use of an ExternalID within a document type definition. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/001.xml) |
| 4.2.2 [75] | valid-not-sa-002 | Test demonstrates the use of an ExternalID within a document type definition. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/002.xml) |
| 4.2.2 [75] | valid-not-sa-008 | Test demonstrates that an external identifier may include a public identifier. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/008.xml) |
| 4.2.2 [75] | valid-not-sa-009 | Test demonstrates that an external identifier may include a public identifier. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/009.xml) |
| 4.2.2 [75] | valid-not-sa-018 | Test demonstrates an EnternalID whose contents contain an parameter entity declaration and a attribute list definition. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/018.xml) |
| 4.2.2 [76] | o-p76pass1 | valid NDataDecls | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/oasis/p76pass1.xml) |
| 4.3.1 4.3.2 [77] [78] | ext01 | Tests use of external parsed entities with and without content. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/ext01.xml) |
| 4.3.1 [77] | valid-not-sa-012 | Test demonstrates an enternal parsed entity that begins with a text declaration. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/012.xml) |
| 4.3.2 [78] | ext02 | Tests use of external parsed entities with different encodings than the base document. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/ext02.xml) |
| 4.3.3 [4,84] | pr-xml-little | Test support for little-endian UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.) | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/japanese/pr-xml-little-endian.xml) |
| 4.3.3 [4,84] | pr-xml-utf-16 | Test support UTF-16 text which relies on Japanese characters. (Also requires ability to process a moderately complex DTD.) | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/japanese/pr-xml-utf-16.xml) |
| 4.3.3 [4,84] | weekly-little | Test support for little-endian UTF-16 encoding, and XML names which contain Japanese characters. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/japanese/weekly-little-endian.xml) |
| 4.3.3 [4,84] | weekly-utf-16 | Test support for UTF-16 encoding, and XML names which contain Japanese characters. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/japanese/weekly-utf-16.xml) |
| 4.3.3 [80] | valid-sa-031 | Test demonstrates a valid EncodingDecl within the prolog. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/031.xml) |
| 4.3.3 [81] | valid-sa-099 | Test demonstrates the name of the encoding can be composed of lowercase characters. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/099.xml) |
| 4.4.2 | valid-sa-053 | Tests inclusion of a well-formed internal entity, which holds an element required by the content model. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/053.xml) |
| 4.4.8 | valid-not-sa-019 | Test demonstrates that a parameter entity will be expanded with spaces on either side. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/019.xml) |
| 4.4.8 | valid-not-sa-020 | Parameter entities expand with spaces on either side. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/not-sa/020.xml) |
| 4.4.8 | valid-sa-070 | Verifies that internal parameter entities are correctly expanded within the internal subset. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/070.xml) |
| 4.5 | v-pe00 | Tests construction of internal entity replacement text, using an example in the XML specification. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/pe00.xml) |
| 4.5 | v-pe01 | Tests construction of internal entity replacement text, using an example in the XML specification. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/sun/valid/pe01.xml) |
| 4.5 | v-pe02 | Tests construction of internal entity replacement text, using a complex example in the XML specification. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/sun/valid/pe02.xml) |
| 4.5 | valid-sa-065 | Tests ability to define an internal entity which can't legally be expanded (contains an unquoted <). | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/065.xml) |
| 4.5 | valid-sa-087 | Tests whether character references in internal entities are expanded early enough, by relying on correct handling to make the entity be well formed. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/087.xml) |
| 4.5 | valid-sa-088 | 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.) | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/088.xml) |
| 4.5 | valid-sa-101 | This tests whether entity expansion is (incorrectly) done while processing entity declarations; if it is, the entity value literal will terminate prematurely. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/101.xml) |
| 4.5 | valid-sa-117 | Test demonstrates that entity expansion is done while processing entity declarations. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/117.xml) |
| 4.5 | valid-sa-118 | Test demonstrates that entity expansion is done while processing entity declarations. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/118.xml) |
| 4.7 | valid-sa-069 | Verifies that an XML parser will parse a NOTATION declaration; the output phase of this test ensures that it's reported to the application. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 1, position 4, file:/d:/xml/xmlconf/xmltest/valid/sa/069.xml) |
| 4.7 [82] | notation01 | 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. | FAIL (thrown com.datachannel.xml.tokenizer.TokenizerException) Unrecognized token following a '<!' sequence! (line 2, position 4, file:/d:/xml/xmlconf/sun/valid/notation01.xml) |
The XML specification places requirements on the data which is reported by XML processors to applications. This data flows through the SAX API (with one minor omission: reporting external entities which are not included). These output tests verify conformance with the specification by recording that data and comparing it with what is required for conformance with the XML 1.0 specification.
Note that output tests automatically fail in cases where the processor failed to parse the (valid) input document used to generate the output data.
| Test ID | Diagnostic |
| valid-sa-093 | (Input failed, no output available) |
| valid-ext-sa-001 | (Input failed, no output available) |
| valid-ext-sa-002 | (Input failed, no output available) |
| valid-ext-sa-004 | (Input failed, no output available) |
| valid-ext-sa-009 | (Input failed, no output available) |
| valid-sa-116 | (Input failed, no output available) |
| valid-ext-sa-006 | (Input failed, no output available) |
| valid-ext-sa-011 | (Input failed, no output available) |
| valid-sa-108 | (Input failed, no output available) |
| valid-sa-068 | (Input failed, no output available) |
| v-lang01 | (Input failed, no output available) |
| v-lang02 | (Input failed, no output available) |
| v-lang05 | (Input failed, no output available) |
| v-lang03 | (Input failed, no output available) |
| v-lang04 | (Input failed, no output available) |
| v-lang06 | (Input failed, no output available) |
| o-p01pass2 | (Input failed, no output available) |
| valid-sa-049 | (Input failed, no output available) |
| valid-sa-050 | (Input failed, no output available) |
| valid-sa-051 | (Input failed, no output available) |
| valid-sa-052 | (Input failed, no output available) |
| valid-sa-092 | (Input failed, no output available) |
| valid-sa-109 | (Input failed, no output available) |
| valid-sa-013 | (Input failed, no output available) |
| valid-sa-014 | (Input failed, no output available) |
| valid-sa-015 | (Input failed, no output available) |
| valid-sa-009 | (Input failed, no output available) |
| valid-not-sa-023 | (Input failed, no output available) |
| o-p12pass1 | (Input failed, no output available) |
| valid-sa-100 | (Input failed, no output available) |
| valid-sa-012 | (Input failed, no output available) |
| valid-sa-063 | (Input failed, no output available) |
| o-p06pass1 | (Input failed, no output available) |
| o-p07pass1 | (Input failed, no output available) |
| o-p08pass1 | (Input failed, no output available) |
| o-p09pass1 | (Input failed, no output available) |
| o-p43pass1 | (Input failed, no output available) |
| empty | (Input failed, no output available) |
| valid-sa-048 | (Input failed, no output available) |
| valid-sa-008 | (Input failed, no output available) |
| valid-sa-119 | (Input failed, no output available) |
| valid-sa-021 | (Input failed, no output available) |
| valid-sa-022 | (Input failed, no output available) |
| dtd01 | (Input failed, no output available) |
| valid-sa-055 | (Input failed, no output available) |
| valid-sa-098 | (Input failed, no output available) |
| valid-sa-016 | (Input failed, no output available) |
| valid-sa-017 | (Input failed, no output available) |
| valid-sa-037 | (Input failed, no output available) |
| valid-sa-038 | (Input failed, no output available) |
| valid-sa-036 | (Input failed, no output available) |
| valid-sa-039 | (Input failed, no output available) |
| valid-not-sa-031 | (Input failed, no output available) |
| valid-sa-018 | (Input failed, no output available) |
| valid-sa-019 | (Input failed, no output available) |
| valid-sa-020 | (Input failed, no output available) |
| valid-sa-114 | (Input failed, no output available) |
| o-p31pass2 | (Input failed, no output available) |
| o-p28pass3 | (Input failed, no output available) |
| o-p28pass5 | (Input failed, no output available) |
| o-p30pass2 | (Input failed, no output available) |
| o-p28pass4 | (Input failed, no output available) |
| o-p30pass1 | (Input failed, no output available) |
| o-p22pass4 | (Input failed, no output available) |
| o-p22pass5 | (Input failed, no output available) |
| o-p22pass6 | (Input failed, no output available) |
| valid-sa-033 | (Input failed, no output available) |
| valid-sa-028 | (Input failed, no output available) |
| valid-sa-029 | (Input failed, no output available) |
| valid-sa-030 | (Input failed, no output available) |
| o-p29pass1 | (Input failed, no output available) |
| o-p31pass1 | (Input failed, no output available) |
| valid-not-sa-024 | (Input failed, no output available) |
| not-sa01 | (Input failed, no output available) |
| not-sa02 | (Input failed, no output available) |
| not-sa03 | (Input failed, no output available) |
| not-sa04 | (Input failed, no output available) |
| sa01 | (Input failed, no output available) |
| sa02 | (Input failed, no output available) |
| sa03 | (Input failed, no output available) |
| sa04 | (Input failed, no output available) |
| sa05 | (Input failed, no output available) |
| valid-sa-032 | (Input failed, no output available) |
| element | (Input failed, no output available) |
| optional | (Input failed, no output available) |
| valid-sa-024 | (Input failed, no output available) |
| valid-ext-sa-003 | (Input failed, no output available) |
| valid-sa-007 | (Input failed, no output available) |
| valid-sa-002 | (Input failed, no output available) |
| valid-sa-005 | (Input failed, no output available) |
| valid-sa-010 | (Input failed, no output available) |
| valid-sa-011 | (Input failed, no output available) |
| valid-sa-104 | (Input failed, no output available) |
| valid-sa-054 | (Input failed, no output available) |
| valid-sa-004 | (Input failed, no output available) |
| valid-sa-006 | (Input failed, no output available) |
| valid-sa-003 | (Input failed, no output available) |
| valid-sa-023 | (Input failed, no output available) |
| valid-sa-047 | (Input failed, no output available) |
| o-p28pass1 | (Input failed, no output available) |
| valid-sa-034 | (Input failed, no output available) |
| valid-sa-035 | (Input failed, no output available) |
| valid-sa-044 | (Input failed, no output available) |
| o-p46pass1 | (Input failed, no output available) |
| o-p48pass1 | (Input failed, no output available) |
| o-p49pass1 | (Input failed, no output available) |
| o-p50pass1 | (Input failed, no output available) |
| o-p47pass1 | (Input failed, no output available) |
| valid-sa-059 | (Input failed, no output available) |
| o-p45pass1 | (Input failed, no output available) |
| valid-sa-025 | (Input failed, no output available) |
| valid-sa-026 | (Input failed, no output available) |
| valid-sa-027 | (Input failed, no output available) |
| valid-ext-sa-005 | (Input failed, no output available) |
| valid-sa-057 | (Input failed, no output available) |
| valid-sa-112 | (Input failed, no output available) |
| valid-sa-081 | (Input failed, no output available) |
| dtd00 | (Input failed, no output available) |
| o-p51pass1 | (Input failed, no output available) |
| valid-sa-001 | (Input failed, no output available) |
| valid-sa-043 | (Input failed, no output available) |
| valid-sa-097 | (Input failed, no output available) |
| valid-sa-040 | (Input failed, no output available) |
| valid-sa-077 | (Input failed, no output available) |
| valid-sa-078 | (Input failed, no output available) |
| valid-sa-071 | (Input failed, no output available) |
| valid-sa-072 | (Input failed, no output available) |
| valid-sa-073 | (Input failed, no output available) |
| valid-sa-074 | (Input failed, no output available) |
| valid-sa-075 | (Input failed, no output available) |
| valid-sa-079 | (Input failed, no output available) |
| valid-sa-080 | (Input failed, no output available) |
| o-p52pass1 | (Input failed, no output available) |
| valid-not-sa-006 | (Input failed, no output available) |
| valid-not-sa-007 | (Input failed, no output available) |
| valid-not-sa-010 | (Input failed, no output available) |
| valid-not-sa-026 | (Input failed, no output available) |
| valid-sa-045 | (Input failed, no output available) |
| valid-sa-046 | (Input failed, no output available) |
| valid-sa-113 | (Input failed, no output available) |
| o-p53pass1 | (Input failed, no output available) |
| valid-sa-076 | (Input failed, no output available) |
| valid-sa-090 | (Input failed, no output available) |
| valid-sa-091 | (Input failed, no output available) |
| valid-sa-041 | (Input failed, no output available) |
| valid-sa-042 | (Input failed, no output available) |
| valid-sa-056 | (Input failed, no output available) |
| o-p54pass1 | (Input failed, no output available) |
| o-p55pass1 | (Input failed, no output available) |
| o-p56pass1 | (Input failed, no output available) |
| o-p57pass1 | (Input failed, no output available) |
| o-p58pass1 | (Input failed, no output available) |
| o-p59pass1 | (Input failed, no output available) |
| v-sgml01 | (Input failed, no output available) |
| o-p60pass1 | (Input failed, no output available) |
| required00 | (Input failed, no output available) |
| valid-ext-sa-013 | (Input failed, no output available) |
| valid-sa-058 | (Input failed, no output available) |
| valid-sa-095 | (Input failed, no output available) |
| valid-sa-096 | (Input failed, no output available) |
| valid-sa-102 | (Input failed, no output available) |
| valid-sa-103 | (Input failed, no output available) |
| valid-sa-105 | (Input failed, no output available) |
| valid-sa-106 | (Input failed, no output available) |
| valid-sa-107 | (Input failed, no output available) |
| valid-sa-110 | (Input failed, no output available) |
| valid-sa-111 | (Input failed, no output available) |
| valid-sa-115 | (Input failed, no output available) |
| o-p61pass1 | (Input failed, no output available) |
| o-p62pass1 | (Input failed, no output available) |
| valid-not-sa-013 | (Input failed, no output available) |
| valid-not-sa-014 | (Input failed, no output available) |
| valid-not-sa-016 | (Input failed, no output available) |
| valid-not-sa-022 | (Input failed, no output available) |
| valid-not-sa-028 | (Input failed, no output available) |
| valid-not-sa-029 | (Input failed, no output available) |
| valid-not-sa-030 | (Input failed, no output available) |
| o-p63pass1 | (Input failed, no output available) |
| valid-not-sa-015 | (Input failed, no output available) |
| o-p64pass1 | (Input failed, no output available) |
| valid-sa-085 | (Input failed, no output available) |
| valid-ext-sa-014 | (Input failed, no output available) |
| valid-sa-060 | (Input failed, no output available) |
| valid-sa-061 | (Input failed, no output available) |
| valid-sa-062 | (Input failed, no output available) |
| valid-sa-064 | (Input failed, no output available) |
| valid-sa-066 | (Input failed, no output available) |
| valid-sa-067 | (Input failed, no output available) |
| valid-sa-089 | (Input failed, no output available) |
| o-p68pass1 | (Input failed, no output available) |
| o-p69pass1 | (Input failed, no output available) |
| valid-not-sa-003 | (Input failed, no output available) |
| valid-not-sa-004 | (Input failed, no output available) |
| valid-not-sa-005 | (Input failed, no output available) |
| valid-not-sa-027 | (Input failed, no output available) |
| valid-not-sa-025 | (Input failed, no output available) |
| valid-sa-086 | (Input failed, no output available) |
| valid-not-sa-011 | (Input failed, no output available) |
| o-p70pass1 | (Input failed, no output available) |
| o-p71pass1 | (Input failed, no output available) |
| o-p72pass1 | (Input failed, no output available) |
| valid-not-sa-017 | (Input failed, no output available) |
| valid-not-sa-021 | (Input failed, no output available) |
| valid-sa-082 | (Input failed, no output available) |
| valid-sa-083 | (Input failed, no output available) |
| o-p73pass1 | (Input failed, no output available) |
| valid-ext-sa-012 | (Input failed, no output available) |
| valid-ext-sa-008 | (Input failed, no output available) |
| valid-ext-sa-007 | (Input failed, no output available) |
| valid-not-sa-001 | (Input failed, no output available) |
| valid-not-sa-002 | (Input failed, no output available) |
| valid-not-sa-008 | (Input failed, no output available) |
| valid-not-sa-009 | (Input failed, no output available) |
| valid-not-sa-018 | (Input failed, no output available) |
| o-p76pass1 | (Input failed, no output available) |
| ext01 | (Input failed, no output available) |
| valid-not-sa-012 | (Input failed, no output available) |
| ext02 | (Input failed, no output available) |
| pr-xml-little | (Input failed, no output available) |
| pr-xml-utf-16 | (Input failed, no output available) |
| weekly-little |