[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] How Best to Generate Result Documents from Nested Structures?

Subject: Re: [xsl] How Best to Generate Result Documents from Nested Structures?
From: "Dimitre Novatchev dnovatchev@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 26 May 2014 15:57:33 -0000

On Sun, May 25, 2014 at 10:50 AM, Eliot Kimber ekimber@xxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> I should be able to do this:
> <xsl:template match="*">
>   <xsl:result-document href="{name(.)}.xml">
>     <result><xsl:value-of select="name(.)"/></result>
>     <xsl:apply-templates/>
>   </xsl:result-document>
> </xsl:template>
> And get three result documents, a.xml, b.xml, and c.xml.

Yes, this produces three result documents.

However, if in general you want to organize overlapping processing,
and first determine each "processing area", the two-pass approach is a
good one.

In XSLT 3.0 I would put the "area definitions" in a map. The map
data-type can have very efficient implementation, where adding some
new key-value pair to produce a new map is efficient -- that is, this
operation doesn't copy the original map into the new one (that would
be the case if a temporary result tree was used), but internally
*refers* to the old map.

Dimitre Novatchev
Truly great madness cannot be achieved without significant intelligence.
To invent, you need a good imagination and a pile of junk
Never fight an inanimate object
To avoid situations in which you might make mistakes may be the
biggest mistake of all
Quality means doing it right when no one is looking.
You've achieved success in your field when you don't know whether what
you're doing is work or play
To achieve the impossible dream, try going to sleep.
Facts do not cease to exist because they are ignored.
Typing monkeys will write all Shakespeare's works in 200yrs.Will they
write all patents, too? :)
I finally figured out the only reason to be alive is to enjoy it.

Current Thread