CSS isn't bound to the Web browser any more than XSL is bound to the few
implementations that already exist for it. I don't have any trouble
imagining a word processor that editing XML and used CSS to apply
formatting, nor do I have trouble seeing a page layout tool that used CSS
to create pages for many different kinds of documents.
The question remains: why are transformations necessary to styles? The
browser has to do an internal elements->presentation transformation anyway,
so why put in the extra elements->transformation->presentation step? There
are plenty of transformation tools that can already do transformations.
Why is this so important to presentations?
Maybe it's time to subscribe to the xsl list. (I did for a while, and
couldn't figure out why it was supposed to be interesting.) This shouldn't
sound any dumber there than my earliest questions sounded on XML-Dev.
Still, this seems like a fairly significant XML software architecture
issue, so I was hoping to find answers here.
Simon St.Laurent
Dynamic HTML: A Primer / XML: A Primer
Cookies / Sharing Bandwidth (November)
Building XML Applications (December)
http://www.simonstl.com