XSL formatting model

I'm trying to understand what appears to be the WG's current intention
to create a new formatting model, based on flow objects, for web output
that is not equivalent to HTML 4 + CSS 2.

Naively, this seems to be bad idea. Doesn't build off existing practice
and implementations, goes against the market direction, complicates XSL
and possibly reduces its acceptance.

But, the folks on the WG are bright and experienced. I'm sure they're
not heading in this direction w/o thought.

So, explanation please? What's the rationale for abandoning the proven
and deployed formatting model represented by HTML/CSS and attempting to
develop a new model? (The only explanation I've seen offered so far is
that the original XSL note described generating really ugly HTML that
wouldn't behave well in various display environments. The obvious fix
here is to generate better HTML, not to abandon the currently proven web
display model.)

-Lee


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list