[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Future XSLT expansion.
Jon Smirl wrote: > > Am I experiencing a side effect of this discussion? > > I would like to do this: > > <xsl:variable name="foo"> > <mytag> > data > </mytag> > </xsl:variable> > > <xsl:apply-templates select="$foo"/> Yes, this is a real issue. xsl:variable produces a Result-Set NOT a Node-Set. One could argue that it ought produce a node-set, but that is how the spec reads. I believe that this is why result-set -> node-set 'extension converters' exist, but haven't personally needed to use them. > > This gives me a "cannot convert to node-set error" with XT. > It was my understanding that this was in XSLT to prevent > feedback from the resultset back into the input of the pattern > matches. > > Instead I use: > > <mydata> > <mytag> > data > </mytag> > </mydata> > > <xsl:apply-templates select="document('')/mydata"/> why not: <xsl:apply-templates select="document('data.xml')/mydata" />? I would argue that it is 'cleaner' to factor data out of the transform sheet itself, but regardless it also avoids the double parse issue. > > BTW - the Release 3 of the Microsoft XML dll allows the > first case so it is in disagreement with JClark's XT. > This is a known area of MSXML non-conformance. JClark's XT and Xalan (BTW) are correct. Jonathan Borden XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|