| Filename | Collection | Action | Rationale | Status |
|---|---|---|---|---|
| ibm/valid/p02/ibm02v01.xml | IBM | ???? | Bytes are missing from 4-byte UTF-8 sequence in three places- Not fixed there -- what's the intended byte? Character incorrectly encoded in UTF8 - there is a 0xbf byte missing at offset 0x12e | Open |
| ibm-invalid-p29-ibm29i01.xml,ibm-valid-p28-ibm28v02.xml,ibm-valid-p29-ibm29v0[12].xml | IBM | ???? | Output file has PI before the DTD (wrong per SUN canonical form definition)- Not yet updated. The only definition for the Sun canonical form that I have found is the onepackaged with the conformance tests. This is labelled "Draft 1" and does,as you state, indicate that the DTD should appear first. The link to theonline document is broken. I wonder if all current implementationscurrently emit PIs in the order (relative to the DTD) that they appear (asours does). | Open |
| sun/valid/dtdtest.dtd, sun/valid/optional.xml (various files), ibm-valid-p45-ibm45v01.xml, ibm-valid-p47-ibm47v01.xml | IBM | ???? | Contain non-deterministic content models-The "dtdtest.dtd" should just have those content models removed | Open |
| sun/valid/sa02.xml, sun/valid/not-sa02.xml | SUN | ???? | Related to normalization of attribute values. The canonical output of the attribute "nmtokens" is wrong as it is missing a space (#x20) character- > There has been some confusion about the validity of tokens separated> by character references to whitespace (which depends on the> definitions of Names and Nmtokens). They were outlawed by first> edition erratum 62, which was reversed by erratum 108 (apparently> because of a misunderstanding) and have been outlawed again by second> editions erratum 20. The end result is that there examples are not> valid and should therefore not have any canonical output! | Open |
| xmltest/valid/sa/105[106,107].xml | James Clark | ???? | Character reference appear in the output file instead of a space | Open |
| xmltest/not-wf/sa/176.xmlxmltest/valid/sa/093.xml | James Clark | ???? | Input files changed line-ends | Open |
| ibm/not-wf/p13/ibm13n03.xml | IBM | ???? | Input appears to be in ISO-8859-1, not UTF-8 | Open |
| xmltest/valid/not-sa/022.xml | James Clark | Modify | Conditional DTD section must start and end within the same entity | Closed |
| sun/invalid/pe01.xml | SUN | Modify | Test must be labeled as valid in the next version --PE refs are not recognized in attribute values, including default attribute values | Closed |
| ibm-valid-p58-ibm58v01.xml, ibm/valid/p59/ibm59v01.xml | IBM | Modify | Contains duplicate tokens in NOTATION enumeration (needs updating because of erratun E2 to 2nd edition) | Closed |
| ibm-not-wf-p68-ibm68n06.xml | IBM | Modify | Does not test what it is meant to, because the text declaration in the DTD (ibm68n06.dtd) does not contain an encoding declaration | Closed |
| invalid/p51d/ibm51i03.dtd | IBM | Modify | DTD does not contain encoding information, but this file does not seem to be used | Closed |
| not-wf/p75/empty.dtd | IBM | Modify | DTD does not contain encoding information, but all the files that refer to it are not well-formed anyway | Closed |
| xmltest/valid/sa/094.xml | James Clark | Modify | Marked as not-well-formed, but PEs are not expanded in attvalue so is well-formed | Closed |
| ibm-not-wf-p77-ibm77n01.xml | IBM | Modify | Doesn't test what it's meant to because there is a missing semicolon after the entity reference | Closed |
| ibm-not-wf-p77-ibm77n03.xml,ibm-not-wf-p77-ibm77n04 | IBM | Modify | Doesn't test what it's meant to because the encoding is "UTF8" (likely to be unrecognized) instead of "UTF-8" | Closed |
| xmltest/valid/not-sa/003-2.ent, xmltest/not-wf/sa/050.xml, sun/valid/null.ent, oasis/p39fail3.xml, sun/invalid/empty.xml | James Clark,SUN, OASIS | Recover | Missing files- Files were lost during unzipping process | Closed |
| xmltest/valid/sa/out/098.xml,sun/valid/out/{not-sa0[1234].xml,notation01.xml,sa0[2345],xml} | James Clark,SUN | Modify | Canonical output appears to have preserved the input CR-LF combination, which both the test description and the spec appear to indicate that the content of the PI should be subjected to line feed normalization- Should be fixed. This means that the test suite again provides decent coverage for both LF and CRLF style line ends. It's still a bit weak on CR, and should probably include some case using NEL (as not-wf). (actually there are CRs in all the files, probably because the test suite passed through MS Windows; these are the ones where it makes a difference) | Closed |
| ibm/valid/p57/ibm57v01.xml, ibm/valid/p58/ibm58v01.xml | IBM | Modify | These files have the attribute of type NOTATION for the element declared EMPTY - against to "VC:No Notation on Empty Element", but categorized to valid files | Closed |
| xmltest/xmltest.xml | James Clark | Modify | Corrupted files, OUTPUT= attribute says "out069.xml" not "out/069.xml" | Closed |
Please forward all comments/suggestions/bugs to <mbrady@nist.gov>