<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV>
<DIV>Hi, I am in the early stages of working with Saxon-B but was wondering as to the added benefits of Saxon-SA's transformation with schema validation versus Xalan with Xerces. </DIV>
<DIV>My understanding is that Xalan provides support for Xerces to do XML transformation and schema validation. </DIV>
<DIV> </DIV>
<DIV>My understanding also is that Saxon ultimately expands an Xquery string does its conversion and at some stage hold its resultSet as XML nodes. Can these XML nodes prior to output by Saxon-B be transformed and validated via Xalan and Xerces ?</DIV>
<DIV> </DIV>
<DIV>I think I've answered my own question in a way, is the flaw in my logic that validation with Xalan will only happen after a successful / unsuccessful output of XML nodes whereas Saxon does it on the route to generating XML ?</DIV>
<DIV> </DIV>
<DIV>OR is the difference that the Saxon implementation simply offers far better performance to make Xalan a consideration ?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Roger</DIV></DIV></div><br>
</body></html>