second implementation of XSLT 2.0?

Before a W3C Candidate Recommendation advances to Proposed
Recommendation status, "the Working Group should be able to demonstrate
two interoperable implementations of each feature."[1] So far, we've got
Saxon for 2.0, but what else? A week ago I posted a message on the
Xalan-J user list to see if anyone knew anything about schedules or
stages of XSLT 2.0 support in Xalan, and I got no reply. I've recently
learned that XML Spy is advertising XSLT 2.0 support[2]; does anyone
know if they wrote their own engine and how good it is?

thanks,

Bob DuCharme

[1] http://www.w3.org/Consortium/Process-20010719/tr.html#RecsCR
[2] http://www.altova.com/features_xsl.html