Passed 1963 of 2162 tests.
Failed 199 of 2162 tests.
Conformance level: 90.8%.
| Test ID | Type | Input | Compare results | Sections | Test Description | |
|---|---|---|---|---|---|---|
| 1 | not-wf-sa-001 | not-wf | Input | Compare Results | 3.1 [41] | Attribute values must start with attribute names, not "?". |
| 2 | not-wf-sa-002 | not-wf | Input | Compare Results | 2.3 [4] | Names may not start with "."; it's not a Letter. |
| 3 | not-wf-sa-003 | not-wf | Input | Compare Results | 2.6 [16] | Processing Instruction target name is required. |
| 4 | not-wf-sa-004 | not-wf | Input | Compare Results | 2.6 [16] | SGML-ism: processing instructions end in '?>' not '>'. |
| 5 | not-wf-sa-005 | not-wf | Input | Compare Results | 2.6 [16] | Processing instructions end in '?>' not '?'. |
| 6 | not-wf-sa-006 | not-wf | Input | Compare Results | 2.5 [16] | XML comments may not contain "--" |
| 7 | not-wf-sa-007 | not-wf | Input | Compare Results | 4.1 [68] | General entity references have no whitespace after the entity name and before the semicolon. |
| 8 | not-wf-sa-008 | not-wf | Input | Compare Results | 2.3 [5] | Entity references must include names, which don't begin with '.' (it's not a Letter or other name start character). |
| 9 | not-wf-sa-009 | not-wf | Input | Compare Results | 4.1 [66] | Character references may have only decimal or numeric strings. |
| 10 | not-wf-sa-010 | not-wf | Input | Compare Results | 4.1 [68] | Ampersand may only appear as part of a general entity reference. |
| 11 | not-wf-sa-011 | not-wf | Input | Compare Results | 3.1 [41] | SGML-ism: attribute values must be explicitly assigned a value, it can't act as a boolean toggle. |
| 12 | not-wf-sa-012 | not-wf | Input | Compare Results | 2.3 [10] | SGML-ism: attribute values must be quoted in all cases. |
| 13 | not-wf-sa-013 | not-wf | Input | Compare Results | 2.3 [10] | The quotes on both ends of an attribute value must match. |
| 14 | not-wf-sa-014 | not-wf | Input | Compare Results | 2.3 [10] | Attribute values may not contain literal '<' characters. |
| 15 | not-wf-sa-015 | not-wf | Input | Compare Results | 3.1 [41] | Attribute values need a value, not just an equals sign. |
| 16 | not-wf-sa-016 | not-wf | Input | Compare Results | 3.1 [41] | Attribute values need an associated name. |
| 17 | not-wf-sa-017 | not-wf | Input | Compare Results | 2.7 [18] | CDATA sections need a terminating ']]>'. |
| 18 | not-wf-sa-018 | not-wf | Input | Compare Results | 2.7 [19] | CDATA sections begin with a literal '<![CDATA[', no space. |
| 19 | not-wf-sa-019 | not-wf | Input | Compare Results | 3.1 [42] | End tags may not be abbreviated as '</>'. |
| 20 | not-wf-sa-020 | not-wf | Input | Compare Results | 2.3 [10] | Attribute values may not contain literal '&' characters except as part of an entity reference. |
| 21 | not-wf-sa-021 | not-wf | Input | Compare Results | 2.3 [10] | Attribute values may not contain literal '&' characters except as part of an entity reference. |
| 22 | not-wf-sa-022 | not-wf | Input | Compare Results | 4.1 [66] | Character references end with semicolons, always! |
| 23 | not-wf-sa-023 | not-wf | Input | Compare Results | 2.3 [5] | Digits are not valid name start characters. |
| 24 | not-wf-sa-024 | not-wf | Input | Compare Results | 2.3 [5] | Digits are not valid name start characters. |
| 25 | not-wf-sa-025 | not-wf | Input | Compare Results | 2.4 [14] | Text may not contain a literal ']]>' sequence. |
| 26 | not-wf-sa-026 | not-wf | Input | Compare Results | 2.4 [14] | Text may not contain a literal ']]>' sequence. |
| 27 | not-wf-sa-027 | not-wf | Input | Compare Results | 2.5 [15] | Comments must be terminated with "-->". |
| 28 | not-wf-sa-028 | not-wf | Input | Compare Results | 2.6 [16] | Processing instructions must end with '?>'. |
| 29 | not-wf-sa-029 | not-wf | Input | Compare Results | 2.4 [14] | Text may not contain a literal ']]>' sequence. |
| 30 | not-wf-sa-030 | not-wf | Input | Compare Results | 2.2 [2] | A form feed is not a legal XML character. |
| 31 | not-wf-sa-031 | not-wf | Input | Compare Results | 2.2 [2] | A form feed is not a legal XML character. |
| 32 | not-wf-sa-032 | not-wf | Input | Compare Results | 2.2 [2] | A form feed is not a legal XML character. |
| 33 | not-wf-sa-033 | not-wf | Input | Compare Results | 2.2 [2] | An ESC (octal 033) is not a legal XML character. |
| 34 | not-wf-sa-034 | not-wf | Input | Compare Results | 2.2 [2] | A form feed is not a legal XML character. |
| 35 | not-wf-sa-035 | not-wf | Input | Compare Results | 3.1 [43] | The '<' character is a markup delimiter and must start an element, CDATA section, PI, or comment. |
| 36 | not-wf-sa-036 | not-wf | Input | Compare Results | 2.8 [27] | Text may not appear after the root element. |
| 37 | not-wf-sa-037 | not-wf | Input | Compare Results | 2.8 [27] | Character references may not appear after the root element. |
| 38 | not-wf-sa-038 | not-wf | Input | Compare Results | 3.1 | Tests the "Unique Att Spec" WF constraint by providing multiple values for an attribute. |
| 39 | not-wf-sa-039 | not-wf | Input | Compare Results | 3 | Tests the Element Type Match WFC - end tag name must match start tag name. |
| 40 | not-wf-sa-040 | not-wf | Input | Compare Results | 2.8 [27] | Provides two document elements. |
| 41 | not-wf-sa-041 | not-wf | Input | Compare Results | 2.8 [27] | Provides two document elements. |
| 42 | not-wf-sa-042 | not-wf | Input | Compare Results | 3.1 [42] | Invalid End Tag |
| 43 | not-wf-sa-043 | not-wf | Input | Compare Results | 2.8 [27] | Provides #PCDATA text after the document element. |
| 44 | not-wf-sa-044 | not-wf | Input | Compare Results | 2.8 [27] | Provides two document elements. |
| 45 | not-wf-sa-045 | not-wf | Input | Compare Results | 3.1 [44] | Invalid Empty Element Tag |
| 46 | not-wf-sa-046 | not-wf | Input | Compare Results | 3.1 [40] | This start (or empty element) tag was not terminated correctly. |
| 47 | not-wf-sa-047 | not-wf | Input | Compare Results | 3.1 [44] | Invalid empty element tag invalid whitespace |
| 48 | not-wf-sa-048 | not-wf | Input | Compare Results | 2.8 [27] | Provides a CDATA section after the roor element. |
| 49 | not-wf-sa-049 | not-wf | Input | Compare Results | 3.1 [40] | Missing start tag |
| 50 | not-wf-sa-050 | not-wf | Input | Compare Results | 2.1 [1] | Empty document, with no root element. |
| 51 | not-wf-sa-051 | not-wf | Input | Compare Results | 2.7 [18] | CDATA is invalid at top level of document. |
| 52 | not-wf-sa-052 | not-wf | Input | Compare Results | 4.1 [66] | Invalid character reference. |
| 53 | not-wf-sa-053 | not-wf | Input | Compare Results | 3.1 [42] | End tag does not match start tag. |
| 54 | not-wf-sa-054 | not-wf | Input | Compare Results | 4.2.2 [75] | PUBLIC requires two literals. |
| 55 | not-wf-sa-055 | not-wf | Input | Compare Results | 2.8 [28] | Invalid Document Type Definition format. |
| 56 | not-wf-sa-056 | not-wf | Input | Compare Results | 2.8 [28] | Invalid Document Type Definition format - misplaced comment. |
| 57 | not-wf-sa-057 | not-wf | Input | Compare Results | 3.2 [45] | This isn't SGML; comments can't exist in declarations. |
| 58 | not-wf-sa-058 | not-wf | Input | Compare Results | 3.3.1 [54] | Invalid character , in ATTLIST enumeration |
| 59 | not-wf-sa-059 | not-wf | Input | Compare Results | 3.3.1 [59] | String literal must be in quotes. |
| 60 | not-wf-sa-060 | not-wf | Input | Compare Results | 3.3.1 [56] | Invalid type NAME defined in ATTLIST. |
| 61 | not-wf-sa-061 | not-wf | Input | Compare Results | 4.2.2 [75] | External entity declarations require whitespace between public and system IDs. |
| 62 | not-wf-sa-062 | not-wf | Input | Compare Results | 4.2 [71] | Entity declarations need space after the entity name. |
| 63 | not-wf-sa-063 | not-wf | Input | Compare Results | 2.8 [29] | Conditional sections may only appear in the external DTD subset. |
| 64 | not-wf-sa-064 | not-wf | Input | Compare Results | 3.3 [53] | Space is required between attribute type and default values in <!ATTLIST...> declarations. |
| 65 | not-wf-sa-065 | not-wf | Input | Compare Results | 3.3 [53] | Space is required between attribute name and type in <!ATTLIST...> declarations. |
| 66 | not-wf-sa-066 | not-wf | Input | Compare Results | 3.3 [52] | Required whitespace is missing. |
| 67 | not-wf-sa-067 | not-wf | Input | Compare Results | 3.3 [53] | Space is required between attribute type and default values in <!ATTLIST...> declarations. |
| 68 | not-wf-sa-068 | not-wf | Input | Compare Results | 3.3.1 [58] | Space is required between NOTATION keyword and list of enumerated choices in <!ATTLIST...> declarations. |
| 69 | not-wf-sa-069 | not-wf | Input | Compare Results | 4.2.2 [76] | Space is required before an NDATA entity annotation. |
| 70 | not-wf-sa-070 | not-wf | Input | Compare Results | 2.5 [16] | XML comments may not contain "--" |
| 71 | not-wf-sa-071 | not-wf | Input | Compare Results | 4.1 [68] | ENTITY can't reference itself directly or indirectly. |
| 72 | not-wf-sa-072 | not-wf | Input | Compare Results | 4.1 [68] | Undefined ENTITY foo. |
| 73 | not-wf-sa-073 | not-wf | Input | Compare Results | 4.1 [68] | Undefined ENTITY f. |
| 74 | not-wf-sa-074 | not-wf | Input | Compare Results | 4.3.2 | Internal general parsed entities are only well formed if they match the "content" production. |
| 75 | not-wf-sa-075 | not-wf | Input | Compare Results | 4.1 [68] | ENTITY can't reference itself directly or indirectly. |
| 76 | not-wf-sa-076 | not-wf | Input | Compare Results | 4.1 [68] | Undefined ENTITY foo. |
| 77 | not-wf-sa-077 | not-wf | Input | Compare Results | 41. [68] | Undefined ENTITY bar. |
| 78 | not-wf-sa-078 | not-wf | Input | Compare Results | 4.1 [68] | Undefined ENTITY foo. |
| 79 | not-wf-sa-079 | not-wf | Input | Compare Results | 4.1 [68] | ENTITY can't reference itself directly or indirectly. |
| 80 | not-wf-sa-080 | not-wf | Input | Compare Results | 4.1 [68] | ENTITY can't reference itself directly or indirectly. |
| 81 | not-wf-sa-081 | not-wf | Input | Compare Results | 3.1 | This tests the No External Entity References WFC, since the entity is referred to within an attribute. |
| 82 | not-wf-sa-082 | not-wf | Input | Compare Results | 3.1 | This tests the No External Entity References WFC, since the entity is referred to within an attribute. |
| 83 | not-wf-sa-083 | not-wf | Input | Compare Results | 4.2.2 [76] | Undefined NOTATION n. |
| 84 | not-wf-sa-084 | not-wf | Input | Compare Results | 4.1 | 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.) |
| 85 | not-wf-sa-085 | not-wf | Input | Compare Results | 2.3 [13] | Public IDs may not contain "[". |
| 86 | not-wf-sa-086 | not-wf | Input | Compare Results | 2.3 [13] | Public IDs may not contain "[". |
| 87 | not-wf-sa-087 | not-wf | Input | Compare Results | 2.3 [13] | Public IDs may not contain "[". |
| 88 | not-wf-sa-088 | not-wf | Input | Compare Results | 2.3 [10] | Attribute values are terminated by literal quote characters, and any entity expansion is done afterwards. |
| 89 | not-wf-sa-089 | not-wf | Input | Compare Results | 4.2 [74] | Parameter entities "are" always parsed; NDATA annotations are not permitted. |
| 90 | not-wf-sa-090 | not-wf | Input | Compare Results | 2.3 [10] | Attributes may not contain a literal "<" character; this one has one because of reference expansion. |
| 91 | not-wf-sa-091 | not-wf | Input | Compare Results | 4.2 [74] | Parameter entities "are" always parsed; NDATA annotations are not permitted. |
| 92 | not-wf-sa-092 | not-wf | Input | Compare Results | 4.5 | The replacement text of this entity has an illegal reference, because the character reference is expanded immediately. |
| 93 | not-wf-sa-093 | not-wf | Input | Compare Results | 4.1 [66] | Hexadecimal character references may not use the uppercase 'X'. |
| 94 | not-wf-sa-094 | not-wf | Input | Compare Results | 2.8 [24] | Prolog VERSION must be lowercase. |
| 95 | not-wf-sa-095 | not-wf | Input | Compare Results | 2.8 [23] | VersionInfo must come before EncodingDecl. |
| 96 | not-wf-sa-096 | not-wf | Input | Compare Results | 2.9 [32] | Space is required before the standalone declaration. |
| 97 | not-wf-sa-097 | not-wf | Input | Compare Results | 2.8 [24] | Both quotes surrounding VersionNum must be the same. |
| 98 | not-wf-sa-098 | not-wf | Input | Compare Results | 2.8 [23] | Only one "version=..." string may appear in an XML declaration. |
| 99 | not-wf-sa-099 | not-wf | Input | Compare Results | 2.8 [23] | Only three pseudo-attributes are in the XML declaration, and "valid=..." is not one of them. |
| 100 | not-wf-sa-100 | not-wf | Input | Compare Results | 2.9 [32] | Only "yes" and "no" are permitted as values of "standalone". |
| 101 | not-wf-sa-101 | not-wf | Input | Compare Results | 4.3.3 [81] | Space is not permitted in an encoding name. |
| 102 | not-wf-sa-102 | not-wf | Input | Compare Results | 2.8 [26] | Provides an illegal XML version number; spaces are illegal. |
| 103 | not-wf-sa-103 | not-wf | Input | Compare Results | 4.3.2 | End-tag required for element foo. |
| 104 | not-wf-sa-104 | not-wf | Input | Compare Results | 4.3.2 | Internal general parsed entities are only well formed if they match the "content" production. |
| 105 | not-wf-sa-105 | not-wf | Input | Compare Results | 2.7 | Invalid placement of CDATA section. |
| 106 | not-wf-sa-106 | not-wf | Input | Compare Results | 4.2 | Invalid placement of entity declaration. |
| 107 | not-wf-sa-107 | not-wf | Input | Compare Results | 2.8 [28] | Invalid document type declaration. CDATA alone is invalid. |
| 108 | not-wf-sa-108 | not-wf | Input | Compare Results | 2.7 [19] | No space in '<![CDATA['. |
| 109 | not-wf-sa-109 | not-wf | Input | Compare Results | 4.2 [70] | Tags invalid within EntityDecl. |
| 110 | not-wf-sa-110 | not-wf | Input | Compare Results | 4.1 [68] | Entity reference must be in content of element. |
| 111 | not-wf-sa-111 | not-wf | Input | Compare Results | 3.1 [43] | Entiry reference must be in content of element not Start-tag. |
| 112 | not-wf-sa-112 | not-wf | Input | Compare Results | 2.7 [19] | CDATA sections start '<![CDATA[', not '<!cdata['. |
| 113 | not-wf-sa-113 | not-wf | Input | Compare Results | 2.3 [9] | Parameter entity values must use valid reference syntax; this reference is malformed. |
| 114 | not-wf-sa-114 | not-wf | Input | Compare Results | 2.3 [9] | General entity values must use valid reference syntax; this reference is malformed. |
| 115 | not-wf-sa-115 | not-wf | Input | Compare Results | 4.5 | 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. |
| 116 | not-wf-sa-116 | not-wf | Input | Compare Results | 4.3.2 | Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. |
| 117 | not-wf-sa-117 | not-wf | Input | Compare Results | 4.3.2 | Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. |
| 118 | not-wf-sa-118 | not-wf | Input | Compare Results | 4.1 [68] | Entity reference expansion is not recursive. |
| 119 | not-wf-sa-119 | not-wf | Input | Compare Results | 4.3.2 | Internal general parsed entities are only well formed if they match the "content" production. This is a partial character reference, not a full one. |
| 120 | not-wf-sa-120 | not-wf | Input | Compare Results | 4.5 | 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;. |
| 121 | not-wf-sa-121 | not-wf | Input | Compare Results | 4.1 [68] | A name of an ENTITY was started with an invalid character. |
| 122 | not-wf-sa-122 | not-wf | Input | Compare Results | 3.2.1 [47] | Invalid syntax mixed connectors are used. |
| 123 | not-wf-sa-123 | not-wf | Input | Compare Results | 3.2.1 [48] | Invalid syntax mismatched parenthesis. |
| 124 | not-wf-sa-124 | not-wf | Input | Compare Results | 3.2.2 [51] | Invalid format of Mixed-content declaration. |
| 125 | not-wf-sa-125 | not-wf | Input | Compare Results | 3.2.2 [51] | Invalid syntax extra set of parenthesis not necessary. |
| 126 | not-wf-sa-126 | not-wf | Input | Compare Results | 3.2.2 [51] | Invalid syntax Mixed-content must be defined as zero or more. |
| 127 | not-wf-sa-127 | not-wf | Input | Compare Results | 3.2.2 [51] | Invalid syntax Mixed-content must be defined as zero or more. |
| 128 | not-wf-sa-128 | not-wf | Input | Compare Results | 2.7 [18] | Invalid CDATA syntax. |
| 129 | not-wf-sa-129 | not-wf | Input | Compare Results | 3.2 [45] | Invalid syntax for Element Type Declaration. |
| 130 | not-wf-sa-130 | not-wf | Input | Compare Results | 3.2 [45] | Invalid syntax for Element Type Declaration. |
| 131 | not-wf-sa-131 | not-wf | Input | Compare Results | 3.2 [45] | Invalid syntax for Element Type Declaration. |
| 132 | not-wf-sa-132 | not-wf | Input | Compare Results | 3.2.1 [50] | Invalid syntax mixed connectors used. |
| 133 | not-wf-sa-133 | not-wf | Input | Compare Results | 3.2.1 | Illegal whitespace before optional character causes syntax error. |
| 134 | not-wf-sa-134 | not-wf | Input | Compare Results | 3.2.1 | Illegal whitespace before optional character causes syntax error. |
| 135 | not-wf-sa-135 | not-wf | Input | Compare Results | 3.2.1 [47] | Invalid character used as connector. |
| 136 | not-wf-sa-136 | not-wf | Input | Compare Results | 3.2 [45] | Tag omission is invalid in XML. |
| 137 | not-wf-sa-137 | not-wf | Input | Compare Results | 3.2 [45] | Space is required before a content model. |
| 138 | not-wf-sa-138 | not-wf | Input | Compare Results | 3.2.1 [48] | Invalid syntax for content particle. |
| 139 | not-wf-sa-139 | not-wf | Input | Compare Results | 3.2.1 [46] | The element-content model should not be empty. |
| 140 | not-wf-sa-140 | not-wf | Input | Compare Results | 2.3 [4] | Character '゚' is a CombiningChar, not a Letter, and so may not begin a name. |
| 141 | not-wf-sa-141 | not-wf | Input | Compare Results | 2.3 [5] | Character #x0E5C is not legal in XML names. |
| 142 | not-wf-sa-142 | not-wf | Input | Compare Results | 2.2 [2] | Character #x0000 is not legal anywhere in an XML document. |
| 143 | not-wf-sa-143 | not-wf | Input | Compare Results | 2.2 [2] | Character #x001F is not legal anywhere in an XML document. |
| 144 | not-wf-sa-144 | not-wf | Input | Compare Results | 2.2 [2] | Character #xFFFF is not legal anywhere in an XML document. |
| 145 | not-wf-sa-145 | not-wf | Input | Compare Results | 2.2 [2] | 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.) |
| 146 | not-wf-sa-146 | not-wf | Input | Compare Results | 2.2 [2] | Character references must also refer to legal XML characters; #x00110000 is one more than the largest legal character. |
| 147 | not-wf-sa-147 | not-wf | Input | Compare Results | 2.8 [22] | XML Declaration may not be preceded by whitespace. |
| 148 | not-wf-sa-148 | not-wf | Input | Compare Results | 2.8 [22] | XML Declaration may not be preceded by comments or whitespace. |
| 149 | not-wf-sa-149 | not-wf | Input | Compare Results | 2.8 [28] | XML Declaration may not be within a DTD. |
| 150 | not-wf-sa-150 | not-wf | Input | Compare Results | 3.1 [43] | XML declarations may not be within element content. |
| 151 | not-wf-sa-151 | not-wf | Input | Compare Results | 2.8 [27] | XML declarations may not follow document content. |
| 152 | not-wf-sa-152 | not-wf | Input | Compare Results | 2.8 [22] | XML declarations must include the "version=..." string. |
| 153 | not-wf-sa-153 | not-wf | Input | Compare Results | 4.3.2 | Text declarations may not begin internal parsed entities; they may only appear at the beginning of external parsed (parameter or general) entities. |
| 154 | not-wf-sa-154 | not-wf | Input | Compare Results | 2.8 2.6 [23, 17] | '<?XML ...?>' is neither an XML declaration nor a legal processing instruction target name. |
| 155 | not-wf-sa-155 | not-wf | Input | Compare Results | 2.8 2.6 [23, 17] | '<?xmL ...?>' is neither an XML declaration nor a legal processing instruction target name. |
| 156 | not-wf-sa-156 | not-wf | Input | Compare Results | 2.8 2.6 [23, 17] | '<?xMl ...?>' is neither an XML declaration nor a legal processing instruction target name. |
| 157 | not-wf-sa-157 | not-wf | Input | Compare Results | 2.6 [17] | '<?xmL ...?>' is not a legal processing instruction target name. |
| 158 | not-wf-sa-158 | not-wf | Input | Compare Results | 3.3 [52] | SGML-ism: "#NOTATION gif" can't have attributes. |
| 159 | not-wf-sa-159 | not-wf | Input | Compare Results | 2.3 [9] | Uses '&' unquoted in an entity declaration, which is illegal syntax for an entity reference. |
| 160 | not-wf-sa-160 | not-wf | Input | Compare Results | 2.8 | Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. |
| 161 | not-wf-sa-161 | not-wf | Input | Compare Results | 2.8 | Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. |
| 162 | not-wf-sa-162 | not-wf | Input | Compare Results | 2.8 | Violates the PEs in Internal Subset WFC by using a PE reference within a declaration. |
| 163 | not-wf-sa-163 | not-wf | Input | Compare Results | 4.1 [69] | Invalid placement of Parameter entity reference. |
| 164 | not-wf-sa-164 | not-wf | Input | Compare Results | 4.1 [69] | Invalid placement of Parameter entity reference. |
| 165 | not-wf-sa-165 | not-wf | Input | Compare Results | 4.2 [72] | Parameter entity declarations must have a space before the '%'. |
| 166 | not-wf-sa-166 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFF is not legal anywhere in an XML document. |
| 167 | not-wf-sa-167 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFE is not legal anywhere in an XML document. |
| 168 | not-wf-sa-168 | not-wf | Input | Compare Results | 2.2 [2] | An unpaired surrogate (D800) is not legal anywhere in an XML document. |
| 169 | not-wf-sa-169 | not-wf | Input | Compare Results | 2.2 [2] | An unpaired surrogate (DC00) is not legal anywhere in an XML document. |
| 170 | not-wf-sa-170 | not-wf | Input | Compare Results | 2.2 [2] | 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. |
| 171 | not-wf-sa-171 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFF is not legal anywhere in an XML document. |
| 172 | not-wf-sa-172 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFF is not legal anywhere in an XML document. |
| 173 | not-wf-sa-173 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFF is not legal anywhere in an XML document. |
| 174 | not-wf-sa-174 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFF is not legal anywhere in an XML document. |
| 175 | not-wf-sa-175 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFF is not legal anywhere in an XML document. |
| 176 | not-wf-sa-176 | not-wf | Input | Compare Results | 3 [39] | Start tags must have matching end tags. |
| 177 | not-wf-sa-177 | not-wf | Input | Compare Results | 2.2 [2] | Character FFFF is not legal anywhere in an XML document. |
| 178 | not-wf-sa-178 | not-wf | Input | Compare Results | 3.1 [41] | Invalid syntax matching double quote is missing. |
| 179 | not-wf-sa-179 | not-wf | Input | Compare Results | 4.1 [66] | Invalid syntax matching double quote is missing. |
| 180 | not-wf-sa-180 | not-wf | Input | Compare Results | 4.1 | The Entity Declared WFC requires entities to be declared before they are used in an attribute list declaration. |
| 181 | not-wf-sa-181 | not-wf | Input | Compare Results | 4.3.2 | Internal parsed entities must match the content production to be well formed. |
| 182 | not-wf-sa-182 | not-wf | Input | Compare Results | 4.3.2 | Internal parsed entities must match the content production to be well formed. |
| 183 | not-wf-sa-183 | not-wf | Input | Compare Results | 3.2.2 [51] | Mixed content declarations may not include content particles. |
| 184 | not-wf-sa-184 | not-wf | Input | Compare Results | 3.2.2 [51] | In mixed content models, element names must not be parenthesized. |
| 185 | not-wf-sa-185 | not-wf | Input | Compare Results | 4.1 | 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. |
| 186 | not-wf-sa-186 | not-wf | Input | Compare Results | 3.1 [44] | Whitespace is required between attribute/value pairs. |
| 187 | not-wf-not-sa-001 | not-wf | Input | Compare Results | 3.4 [62] | Conditional sections must be properly terminated ("]>" used instead of "]]>"). |
| 188 | not-wf-not-sa-002 | not-wf | Input | Compare Results | 2.6 [17] | Processing instruction target names may not be "XML" in any combination of cases. |
| 189 | not-wf-not-sa-003 | not-wf | Input | Compare Results | 3.4 [62] | Conditional sections must be properly terminated ("]]>" omitted). |
| 190 | not-wf-not-sa-004 | not-wf | Input | Compare Results | 3.4 [62] | Conditional sections must be properly terminated ("]]>" omitted). |
| 191 | not-wf-not-sa-005 | error | Input | Compare Results | 4.1 | Tests the Entity Declared VC by referring to an undefined parameter entity within an external entity. |
| 192 | not-wf-not-sa-006 | not-wf | Input | Compare Results | 3.4 [62] | Conditional sections need a '[' after the INCLUDE or IGNORE. |
| 193 | not-wf-not-sa-007 | not-wf | Input | Compare Results | 4.3.2 [79] | A <!DOCTYPE ...> declaration may not begin any external entity; it's only found once, in the document entity. |
| 194 | not-wf-not-sa-008 | not-wf | Input | Compare Results | 4.1 [69] | In DTDs, the '%' character must be part of a parameter entity reference. |
| 195 | not-wf-not-sa-009 | not-wf | Input | Compare Results | 2.8 | This test violates WFC:PE Between Declarations in Production 28a. The last character of a markup declaration is not contained in the same parameter-entity text replacement. |
| 196 | not-wf-ext-sa-001 | not-wf | Input | Compare Results | 4.1 | Tests the No Recursion WFC by having an external general entity be self-recursive. |
| 197 | not-wf-ext-sa-002 | not-wf | Input | Compare Results | 4.3.1 4.3.2 [77, 78] | External entities have "text declarations", which do not permit the "standalone=..." attribute that's allowed in XML declarations. |
| 198 | not-wf-ext-sa-003 | not-wf | Input | Compare Results | 2.6 [17] | 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). |
| 199 | invalid--002 | invalid | Input | Compare Results | 3.2.1 | Tests the "Proper Group/PE Nesting" validity constraint by fragmenting a content model between two parameter entities. |
| 200 | invalid--005 | invalid | Input | Compare Results | 2.8 | Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between two parameter entities. |
| 201 | invalid--006 | invalid | Input | Compare Results | 2.8 | Tests the "Proper Declaration/PE Nesting" validity constraint by fragmenting an element declaration between two parameter entities. |
| 202 | invalid-not-sa-022 | invalid | Input | Compare Results | 3.4 [62] | Test the "Proper Conditional Section/ PE Nesting" validity constraint. |
| 203 | valid-sa-001 | valid | Input | Compare Results | 3.2.2 [51] | Test demonstrates an Element Type Declaration with Mixed Content. |
| 204 | valid-sa-002 | valid | Input | Compare Results | 3.1 [40] | Test demonstrates that whitespace is permitted after the tag name in a Start-tag. |
| 205 | valid-sa-003 | valid | Input | Compare Results | 3.1 [42] | Test demonstrates that whitespace is permitted after the tag name in an End-tag. |
| 206 | valid-sa-004 | valid | Input | Compare Results | 3.1 [41] | Test demonstrates a valid attribute specification within a Start-tag. |
| 207 | valid-sa-005 | valid | Input | Compare Results | 3.1 [40] | Test demonstrates a valid attribute specification within a Start-tag that contains whitespace on both sides of the equal sign. |
| 208 | valid-sa-006 | valid | Input | Compare Results | 3.1 [41] | Test demonstrates that the AttValue within a Start-tag can use a single quote as a delimter. |
| 209 | valid-sa-007 | valid | Input | Compare Results | 3.1 4.6 [43] | Test demonstrates numeric character references can be used for element content. |
| 210 | valid-sa-008 | valid | Input | Compare Results | 2.4 3.1 [43] | Test demonstrates character references can be used for element content. |
| 211 | valid-sa-009 | valid | Input | Compare Results | 2.3 3.1 [43] | Test demonstrates that PubidChar can be used for element content. |
| 212 | valid-sa-010 | valid | Input | Compare Results | 3.1 [40] | Test demonstrates that whitespace is valid after the Attribute in a Start-tag. |
| 213 | valid-sa-011 | valid | Input | Compare Results | 3.1 [40] | Test demonstrates mutliple Attibutes within the Start-tag. |
| 214 | valid-sa-012 | valid | Input | Compare Results | 2.3 [4] | Uses a legal XML 1.0 name consisting of a single colon character (disallowed by the latest XML Namespaces draft). |
| 215 | valid-sa-013 | valid | Input | Compare Results | 2.3 3.1 [13] [40] | Test demonstrates that the Attribute in a Start-tag can consist of numerals along with special characters. |
| 216 | valid-sa-014 | valid | Input | Compare Results | 2.3 3.1 [13] [40] | Test demonstrates that all lower case letters are valid for the Attribute in a Start-tag. |
| 217 | valid-sa-015 | valid | Input | Compare Results | 2.3 3.1 [13] [40] | Test demonstrates that all upper case letters are valid for the Attribute in a Start-tag. |
| 218 | valid-sa-016 | valid | Input | Compare Results | 2.6 3.1 [16] [43] | Test demonstrates that Processing Instructions are valid element content. |
| 219 | valid-sa-017 | valid | Input | Compare Results | 2.6 3.1 [16] [43] | Test demonstrates that Processing Instructions are valid element content and there can be more than one. |
| 220 | valid-sa-018 | valid | Input | Compare Results | 2.7 3.1 [18] [43] | Test demonstrates that CDATA sections are valid element content. |
| 221 | valid-sa-019 | valid | Input | Compare Results | 2.7 3.1 [18] [43] | Test demonstrates that CDATA sections are valid element content and that ampersands may occur in their literal form. |
| 222 | valid-sa-020 | valid | Input | Compare Results | 2.7 3.1 [18] [43] | Test demonstractes that CDATA sections are valid element content and that everyting between the CDStart and CDEnd is recognized as character data not markup. |
| 223 | valid-sa-021 | valid | Input | Compare Results | 2.5 3.1 [15] [43] | Test demonstrates that comments are valid element content. |
| 224 | valid-sa-022 | valid | Input | Compare Results | 2.5 3.1 [15] [43] | Test demonstrates that comments are valid element content and that all characters before the double-hypen right angle combination are considered part of thecomment. |
| 225 | valid-sa-023 | valid | Input | Compare Results | 3.1 [43] | Test demonstrates that Entity References are valid element content. |
| 226 | valid-sa-024 | valid | Input | Compare Results | 3.1 4.1 [43] [66] | Test demonstrates that Entity References are valid element content and also demonstrates a valid Entity Declaration. |
| 227 | valid-sa-025 | valid | Input | Compare Results | 3.2 [46] | Test demonstrates an Element Type Declaration and that the contentspec can be of mixed content. |
| 228 | valid-sa-026 | valid | Input | Compare Results | 3.2 [46] | Test demonstrates an Element Type Declaration and that EMPTY is a valid contentspec. |
| 229 | valid-sa-027 | valid | Input | Compare Results | 3.2 [46] | Test demonstrates an Element Type Declaration and that ANY is a valid contenspec. |
| 230 | valid-sa-028 | valid | Input | Compare Results | 2.8 [24] | Test demonstrates a valid prolog that uses double quotes as delimeters around the VersionNum. |
| 231 | valid-sa-029 | valid | Input | Compare Results | 2.8 [24] | Test demonstrates a valid prolog that uses single quotes as delimters around the VersionNum. |
| 232 | valid-sa-030 | valid | Input | Compare Results | 2.8 [25] | Test demonstrates a valid prolog that contains whitespace on both sides of the equal sign in the VersionInfo. |
| 233 | valid-sa-031 | valid | Input | Compare Results | 4.3.3 [80] | Test demonstrates a valid EncodingDecl within the prolog. |
| 234 | valid-sa-032 | valid | Input | Compare Results | 2.9 [32] | Test demonstrates a valid SDDecl within the prolog. |
| 235 | valid-sa-033 | valid | Input | Compare Results | 2.8 [23] | Test demonstrates that both a EncodingDecl and SDDecl are valid within the prolog. |
| 236 | valid-sa-034 | valid | Input | Compare Results | 3.1 [44] | Test demonstrates the correct syntax for an Empty element tag. |
| 237 | valid-sa-035 | valid | Input | Compare Results | 3.1 [44] | Test demonstrates that whitespace is permissible after the name in an Empty element tag. |
| 238 | valid-sa-036 | valid | Input | Compare Results | 2.6 [16] | Test demonstrates a valid processing instruction. |
| 239 | valid-sa-037 | valid | Input | Compare Results | 2.6 [15] | Test demonstrates a valid comment and that it may appear anywhere in the document including at the end. |
| 240 | valid-sa-038 | valid | Input | Compare Results | 2.6 [15] | Test demonstrates a valid comment and that it may appear anywhere in the document including the beginning. |
| 241 | valid-sa-039 | valid | Input | Compare Results | 2.6 [16] | Test demonstrates a valid processing instruction and that it may appear at the beginning of the document. |
| 242 | valid-sa-040 | valid | Input | Compare Results | 3.3 3.3.1 [52] [54] | Test demonstrates an Attribute List declaration that uses a StringType as the AttType. |
| 243 | valid-sa-041 | valid | Input | Compare Results | 3.3.1 4.1 [54] [66] | Test demonstrates an Attribute List declaration that uses a StringType as the AttType and also expands the CDATA attribute with a character reference. |
| 244 | valid-sa-042 | valid | Input | Compare Results | 3.3.1 4.1 [54] [66] | 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. |
| 245 | valid-sa-043 | valid | Input | Compare Results | 3.3 | An element's attributes may be declared before its content model; and attribute values may contain newlines. |
| 246 | valid-sa-044 | valid | Input | Compare Results | 3.1 [44] | Test demonstrates that the empty-element tag must be use for an elements that are declared EMPTY. |
| 247 | valid-sa-045 | valid | Input | Compare Results | 3.3 [52] | Tests whether more than one definition can be provided for the same attribute of a given element type with the first declaration being binding. |
| 248 | valid-sa-046 | valid | Input | Compare Results | 3.3 [52] | Test demonstrates that when more than one AttlistDecl is provided for a given element type, the contents of all those provided are merged. |
| 249 | valid-sa-047 | valid | Input | Compare Results | 3.1 [43] | Test demonstrates that extra whitespace is normalized into single space character. |
| 250 | valid-sa-048 | valid | Input | Compare Results | 2.4 3.1 [14] [43] | Test demonstrates that character data is valid element content. |
| 251 | valid-sa-049 | valid | Input | Compare Results | 2.2 [2] | Test demonstrates that characters outside of normal ascii range can be used as element content. |
| 252 | valid-sa-050 | valid | Input | Compare Results | 2.2 [2] | Test demonstrates that characters outside of normal ascii range can be used as element content. |
| 253 | valid-sa-051 | valid | Input | Compare Results | 2.2 [2] | The document is encoded in UTF-16 and uses some name characters well outside of the normal ASCII range. |
| 254 | valid-sa-052 | valid | Input | Compare Results | 2.2 [2] | 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. |
| 255 | valid-sa-053 | valid | Input | Compare Results | 4.4.2 | Tests inclusion of a well-formed internal entity, which holds an element required by the content model. |
| 256 | valid-sa-054 | valid | Input | Compare Results | 3.1 [40] [42] | Test demonstrates that extra whitespace within Start-tags and End-tags are nomalized into single spaces. |
| 257 | valid-sa-055 | valid | Input | Compare Results | 2.6 2.10 [16] | Test demonstrates that extra whitespace within a processing instruction willnormalized into s single space character. |
| 258 | valid-sa-056 | valid | Input | Compare Results | 3.3.1 4.1 [54] [66] | 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. |
| 259 | valid-sa-057 | valid | Input | Compare Results | 3.2.1 [47] | Test demonstrates an element content model whose element can occur zero or more times. |
| 260 | valid-sa-058 | valid | Input | Compare Results | 3.3.3 | Test demonstrates that extra whitespace be normalized into a single space character in an attribute of type NMTOKENS. |
| 261 | valid-sa-059 | valid | Input | Compare Results | 3.2 3.3 [46] [53] | 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. |
| 262 | valid-sa-060 | valid | Input | Compare Results | 4.1 [66] | Test demonstrates the use of decimal Character References within element content. |
| 263 | valid-sa-061 | valid | Input | Compare Results | 4.1 [66] | Test demonstrates the use of decimal Character References within element content. |
| 264 | valid-sa-062 | valid | Input | Compare Results | 4.1 [66] | Test demonstrates the use of hexadecimal Character References within element. |
| 265 | valid-sa-063 | valid | Input | Compare Results | 2.3 [5] | The document is encoded in UTF-8 and the name of the root element type uses non-ASCII characters. |
| 266 | valid-sa-064 | valid | Input | Compare Results | 4.1 [66] | Tests in-line handling of two legal character references, which each expand to a Unicode surrogate pair. |
| 267 | valid-sa-065 | valid | Input | Compare Results | 4.5 | Tests ability to define an internal entity which can't legally be expanded (contains an unquoted <). |
| 268 | valid-sa-066 | valid | Input | Compare Results | 4.1 [66] | Expands a CDATA attribute with a character reference. |
| 269 | valid-sa-067 | valid | Input | Compare Results | 4.1 [66] | Test demonstrates the use of decimal character references within element content. |
| 270 | valid-sa-068 | valid | Input | Compare Results | 2.11, 4.5 | Tests definition of an internal entity holding a carriage return character reference, which must not be normalized before reporting to the application. Line break normalization only occurs when parsing external parsed entities. |
| 271 | valid-sa-069 | valid | Input | Compare Results | 4.7 | Verifies that an XML parser will parse a NOTATION declaration; the output phase of this test ensures that it's reported to the application. |
| 272 | valid-sa-070 | valid | Input | Compare Results | 4.4.8 | Verifies that internal parameter entities are correctly expanded within the internal subset. |
| 273 | valid-sa-071 | valid | Input | Compare Results | 3.3 3.3.1 [52] [56] | 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. |
| 274 | valid-sa-072 | valid | Input | Compare Results | 3.3 3.3.1 [52] [56] | 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. |
| 275 | valid-sa-073 | valid | Input | Compare Results | 3.3 3.3.1 [52] [56] | 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. |
| 276 | valid-sa-074 | valid | Input | Compare Results | 3.3 3.3.1 [52] [56] | 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. |
| 277 | valid-sa-075 | valid | Input | Compare Results | 3.3 3.3.1 [52] [56] | 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. |
| 278 | valid-sa-076 | valid | Input | Compare Results | 3.3.1 | 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. |
| 279 | valid-sa-077 | valid | Input | Compare Results | 3.3 3.3.1 [52] [54] | Test demonstrates that an AttlistDecl can use an EnumeratedType within the Attribute type. The test also shows that IMPLIED is a valid DefaultDecl. |
| 280 | valid-sa-078 | valid | Input | Compare Results | 3.3 3.3.1 [52] [54] | 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. |
| 281 | valid-sa-079 | valid | Input |