- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Sat, 27 May 2006 12:02:14 +0200
- To: Innovimax SARL <innovimax@gmail.com>, public-xml-processing-model-wg@w3.org
Innovimax SARL wrote:
> Ok, you're right, it is an valid XPath 1.0 expression, but not a
> *usual* XPath 1.0/XSLT 1.0 construction
It is a very usual XPath 1.0 expression, and it is quite typically
used in XSLT 1.0 as well. Example:
<xsl:variable name="document" select="/"/>
and then:
<p:variable name="validity" select="$document/*/@validity" />
You can also write, in pure XSLT 1.0:
<xsl:variable name="document" select="document('other-doc.xml')"/>
No problem at all, and very usual.
> because the variable is a "result tree fragment"
No it isn't. The variable refers to a document node ("root node"
according to XSLT 1.0).
By the way result tree fragments are a (broken) notion from XSLT 1.0,
which has nothing to do with XPath, and this doesn't appear to be
relevant here.
> We should take care to make not to much innovations in the first
> version of XProc, in order to not make the user lost : imagine a
> pure XSLT 1.0/XPath 1.0 fan, he will be allowed to use variable
> bounded in a nodeset in Xproc 1.0 but not in XSLT 1.0 which he uses
> in his pipeline....
See above. The suggested use of XPath is perfectly consistent with
what is done in XSLT 1.0.
-Erik
--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/
Received on Saturday, 27 May 2006 10:03:17 UTC