> Remember that XSLT isn't intended to be a fully general nonprocedural > programming language -- its focus is query, limited operations upon the > data returned by the query, and recomposition. Using it to glue together > extensions talking to other extensions really wasn't one of the primary > design goals.
Joseph, I think it's interesting you'd state that. As I've mentioned on this list several times, one of our primary uses of XSLT is to use it as "object glue". Although I've always wanted to have the results of each extension be accessible to the XSLT itself, from what I understand there is no reason you have to in fact make the return results conform to XSLT objects if you don't want to access them in the XSLT (even the you should have some success through object coercing)???
