XSLT and Text Processing Languages

[Brand_Niemann at tax dot org]

I am evaluating XSL based on this mailing list and Michael Kay's book.  I've
used Omnimark for a number of data conversion projects (conversion from xml to
html etc) and have found it to be relatively easy to learn. Other advantages of
Omnimark are conversion of very large files, referent processing, validation of
dtd/xml and more.

 So my question is the following: Does anyone have any feedback of when and
where they would recommend using XSL/T, instead of Omnimark or any other text
processing language?

In addition(as I understand), when used for displaying data to a browser, XSL/T
processing is done either as a conversion process that is completed before the
data is displayed (to HTML) or is raw XML processing that done during run time
when the data is loaded in the browser (as is the case with IE5 MSXML).

My Question is, since other text processing languages like Omnimark are
available, are most of the advantages of XSL/T processing realized when using
XSL/T in connection with the browser at load time.  And if this is the case, is
Microsoft's MSXML the answer?

Brand Niemann



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