RE: XSLT and Text Processing Languages

>I've been using XSLT in place of Omnimark scripting, and in some places in
>conjunction with Omnimark scripting.
>Things which make XSLT better than Omnimark:
>* No need to validate against a DTD
>* Simpler language and syntax
>* Easier to debug, largely due to lack of data structures
>* ... its just plain neater.

Another advantage:
in xslt there are (generally) no problems with conflicting rules, as xslt
has it's own specification for evaluating the most relevant "match" at any
point.
In omnimark you have to be careful to avoid conflicting rules, and when you
get into
large conversion scripts, this makes code incredibly cumbersome 
(E.g element trench when (parent is hope and ancestor isnt para and ancestor
isnt intro etc etc))
******************************************************************
Warning: This email, including any attachments, 
is for the use of the intended recipient(s) only.
Republication and redissemination, 
including posting to news groups or web pages, 
is strictly prohibited without the express prior consent of Brooker's Limited.
******************************************************************


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