Daniel Koger wrote:
"I fail to see what is inherently complex about XSL.  It basically does one
of two things with an element or object.  It either applies a programmatic
response, or affects a style change.  Complex?"

My point exactly! The best thing about XSL is, that you need only one
language for these two things, instead of a combination of a stylesheet
language (CSS), an interface language (DOM), and a programming/scripting
language (JavaScript, C++, Java, etc.).

Looking at things that way, I can only say that XSL is here to simplify and
compress things. Imagine XQL providing the SQL variant to XML, XLink and
XPointer replacing, enhancing, and extending simple hypertext languages, yet
being far more simple than complicated languages such as HyTime.

The combination of XML, XSL, XQL, XPointer, and XLink harnesses and replaces
the power of a multitude of both simple and complicated languages, yet
maintains an overall structural unity by providing their authors with one
syntactic interface.


Received on Thursday, 27 May 1999 02:53:01 UTC