Subject: Re: [xsl] killing xslt From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> Date: Thu, 13 May 2004 13:23:38 -0400 |
By the way, here is more detailed explanation - "Why You Won't See XSLT 2.0 or XPath 2.0 in the Next Version of the .NET Framework" by Dare Obasanjo, http://blogs.msdn.com/dareobasanjo/archive/2004/05/13/131166.aspx
In the decision to go with XQuery over XSLT 2.0, Mark is right that we felt that developers would prefer the familiar procedural model and syntax of XQuery to the template based model and syntax of XSLT 2.0. Most developers working with XSLT try to use it as a procedural language anyway, and don't really harness the power of templates. There's always the steep learning curve until you get to the "Aha" moment and everything clicks. XQuery with its <http://www.w3schools.com/xquery/xquery_flwor.asp>FLWOR construct and user defined functions fits more naturally with how both programmers and database administrators access and manipulate data than does XSLT 2.0. Thus we feel XQuery and not XSLT is the future of XML based query and transformation.
Cheers, Wendell
====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx 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 ======================================================================
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] killing xslt, Oleg Tkachenko | Thread | RE: [xsl] killing xslt, Michael Kay |
RE: [xsl] XSLT Disable-Output-Escap, Shelli D. Orton | Date | RE: [xsl] problems caused by DOCTYP, Passin, Tom |
Month |