At 09:13 AM 12/6/2002, Ken wrote:
For netiquette reasons I've been reluctant to post "me too" arguments when
the reasonings and concerns have already been eloquently expressed
Me too. (About the XPath 2.0 thing and all that.)
My feeling is that XSLT will be stronger and more useful if it doesn't try
to do what XML Query tries to do. XSLT should assume that XML Query (with
whatever PSVI-aware processing) will be successful and that both would be
served better by a useful complimentarity of strengths.
One should always be able to pipeline queries and transformations,
shouldn't one? Why does the whole kit need to be in one tool? Even
admitting that their functionalities overlap. One can use a pair of pliers
to turn a nut: but that doesn't make it a good wrench.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list