Re: [xsl] Collapsing run-on tag chains not working in saxon or xalan

> Without reading further, this is almost certainly because Microsoft
> (incorrectly, or at least stretching what the spec allows) strips whitespace
> text nodes from the document by default.

Are/will the newest XPath 2.0 and XSLT 2.0 draft specifications be
more strict not to allow such widely different interpretations?

If not, what are the reasons for this and also which are the areas to watch for?

Cheers,

Dimitre.