Altova Mailing List Archives


Re: Stylesheet vs. Transform

From: Mike Brown <mike@-------->
To:
Date: 6/12/2000 7:47:00 AM
> I think the distinction between transformation and styling is bogus.

I agree. 

I would add that "transformation" is IMHO a misnomer anyway. If the
identity transformation (source=result) were the default, and the
stylesheet were an influence on this process, then yes, the source trees
are being transformed into the result tree. 

But as it stands, the XSLT process is much easier to understand if you
describe it as the creation of a new tree, *possibly* drawing upon
information in source trees during the process. The stylesheet defines a
tree that instructs the XSLT processor in a manner that directs part of
this process.

Also, XSLT is only for abstract tree transformation. Although it is
heavily XML document oriented, it is not necessary for the trees to be
derived from XML documents or for XML documents to be derived from them.

   - Mike
____________________________________________________________________
Mike J. Brown, software engineer at         My XML/XSL resources:
webb.net in Denver, Colorado, USA           http://www.skew.org/xml/


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

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.