Altova Mailing List Archives

Re: XPath 2.0: Collection-Valued Expressions (Was: Re: [xsl] XQuery 1.0 and XPath 2.0 Functions and Operators Version 1.0)

From: Mark Nahabedian <naha@---------->
Date: 9/9/2001 4:12:00 AM
Jeni Tennison writes:
 > Hi Mike,
 > > As for the division between XPath and XSLT, I think the best way of
 > > rationalising the split is that XPath is for selecting information
 > > from the source document, XSLT is for constructing the result
 > > document. It should never be necessary to use multiple instructions
 > > at the XSLT level in order to extract a single piece of information
 > > from the source document.
 > I'm beginning to understand that part of that separation is also
 > between simple types (strings, decimals, dates etc.) and complex types
 > (XML). For example, even in XPath/XSLT 1.0, you can construct a string
 > from within XPath with the concat() and format-number() functions. So
 > FLWR expressions in XPath 2.0 would be used for generate sequences of
 > simple values whereas xsl:for-each constructs in XSLT 2.0 would be
 > used to generate complex values.
 > ... but then what are the functions like xf:copy() and xf:shallow()
 > doing in XPath? They seem to be about constructing the result
 > document. Aren't they?
 > >> Can you (or someone) reassure me that there will still be automatic
 > >> conversions between value types such that we won't have to be
 > >> casting/constructing specific data types all over the place?
 > >
 > > This is a matter of intense debate. I wish I could give you such an
 > > assurance but you'll have to wait and see what gets published.
 > OK Mike, I'll trust you to fight the good fight.

Is there some way that we should make it clear to the working group
how big Mike's "constituency" is?

 XSL-List info and archive:


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.