Lists Home |
Date Index |
- From: Paul Prescod <email@example.com>
- To: firstname.lastname@example.org
- Date: Fri, 05 Feb 1999 10:50:59 -0600
Clark Evans wrote:
> I'm not suggesting that the weakend XSL woudn't do any
> transformations, only that the transformations it does
> be based upon a stream rather than upon an object.
I have no problem with a weakened, transformational XSL for certain
stream-based applications. But you seem to think that such a thing could
be a replacement for XSL "as we know it." I don't believe that.
I have the following problems with your two-tier model:
* in general the HTML and PDF versions of a document will order and
organize things differently. Online navigation is quite different from
print navigation. So the part of the language that is "media specific"
must be essentially as powerful as the part that is not.
* if the data has ALREADY been transformed then why isn't CSS "good
enough" for the second step?
* people want the transformation part to take place on the client side in
order to distribute the processing load.
In applications where your model is sufficient, I think we already have
the languages in place to MAKE it work: XSL does the transformation and
CSS does simple style annotation.
Paul Prescod - ISOGEN Consulting Engineer speaking for only himself
"Remember, Ginger Rogers did everything that Fred Astaire did,
but she did it backwards and in high heels."
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)