This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: ordering and iteration problem
At 09:07 PM 5/1/01, Mark wrote:
>Dan Diebolt writes:
>
> > If you are low on nodes, why can't you take your random-nodes from
> > both the stylesheet and source XML document?
> >
> > xsl:variable name="random-nodes"
> > select="document('')//node()|//node()" />
>
>I know that the source XML document has enough nodes since the
>elements that I need to use the random nodes iteration hack for is a
>subset of it. I don't know for sure if the XSLT transform document
>will have enough nodes. I was just wondering why this "design
>pattern" was typically described using "document('')//node()" when
>"//node()" seemed to be more correct.
Maybe we use document('')//node() to remind ourselves of how arbitrary it is.
As originally described, the "pattern" (kind of a fancy name for this
idiom/technique/workaround :-) doesn't care what node-set you use as long
as it's big enough (and it's up to you to make sure it is).
But now I'm curious: why can't you just iterate over your subset of
elements, since you apparently know what they are? (I guess I should check
the archives.)
Cheers,
Wendell
======================================================================
Wendell Piez mailto:wapiez@mulberrytech.com
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
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list