OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] XPath 2.0 - how much of XQuery should it include?

[ Lists Home | Date Index | Thread Index ]

Hi Jonathan,

> I think I have a pretty good idea what some of the user communities
> are for XSLT 1.0, and what some of the user communities for XQuery
> will be. I have much less understanding of who the user community
> for XSLT 2.0 will be. Will it be the same community that is now
> using XSLT 1.0?

Yes to the first -- XSLT 2.0 offers several real advantages over XSLT
1.0 (temporary trees, user-defined functions, grouping support,
multiple output documents) that current XSLT users *really want*.
(Which is why the recommendation "Just keep using XSLT/XPath 1.0 if
you don't like 2.0" is so irritating.) As long as there are
implementations, I personally expect most XSLT users to migrate to
XSLT 2.0 fairly rapidly.

> Will people typically use XQuery for their queries and XSLT for
> their reports?

Bear in mind that not everyone processes data-oriented XML -- I
wouldn't call creating HTML from DocBook "report writing". A lot of
transformations aren't carried out on information that originates from
databases at all -- perhaps it's XML that's come in over the wire, or
XML stored on the file system. I imagine that the processing pipeline
would start off with an XQuery query and then go through several
transformations (using XSLT or other transformation tools) before
becoming the destination format, whatever that is.

Out of interest, do you know if there are any plans to add an XQuery
transformer to Cocoon?



Jeni Tennison


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS