[
Lists Home |
Date Index |
Thread Index
]
At 2:04 PM +0000 2/23/04, Michael Kay wrote:
>A shame that someone should go to all the effort of writing a promising
>XML parser and then not finish it. IIRC, it ran most of the other 3000
>or so tests in my test suite quite happily (of course these are XSLT
>tests, they aren't designed to stress the XML parser).
Speaking of writing a promising XML parser and then abandoning it,
what's up with Saxon's AElfred? :-) So far in my tests, it's the only
one to cross the 90% correct threshold, and many of the tests it
fails are bugs in the test framework I need to fix.
The major problems in this fork of Saxon appear to be failure to
detect malformed entities when their resolution is well-formed,
failure to detect some illegal characters (perhaps it's using Java
rules rather than XML rules), and failure to absolutize NOTATION
system IDs. There are also some namespace issues that probably
relate to the legal and illegal character testing. If these problems
were fixed, this branch of AElfred would come very close to 100%
conformance on the XML 1.0 tests.
--
Elliotte Rusty Harold
elharo@metalab.unc.edu
Effective XML (Addison-Wesley, 2003)
http://www.cafeconleche.org/books/effectivexml
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
|
