CODEWITHSUNDEEP
xslt
iwarv
iwarv

Reputation: 441

XSLT - filter out elements that are not x-referenced

I have developed a (semi-)identity transformation from which I need to filter out elements that are unused.

The source XML contains 2001 "zones". No more, no less.

It also contains any number of devices, which are placed in these zones. One specific example source XML contains 8800 of these devices. More than one device can be placed in the same zone.

Zone 0 is a "null zone", meaning that a device placed in this zone is currently unassigned. This means that the number of real zones is 2000.

Simplified source XML:

<configuration>
  <zones>
    <zone id="0">
    ...
    <zone id="2000"/>
  </zones>
  <devices>
    <device addr="1">
      <zone>1</zone>
    </device>
    ...
    <device addr="8800">
      <zone>1</zone>
    </device>
  </devices>
</configuration>

The problem we have is that out of the 2000 usable zones, most often only roughly 200 of these contain one or more devices. I need to whittle out unused zones. There are reasons for this which serve only to detract from the question at hand, so if you don't mind I will not elaborate here.

I currently have this problem solved, like so:

<xsl:for-each select="zones/zone[@id &gt; 0]">
  <xsl:when test="/configuration/devices/device[zone=current()/@id]">
    <xsl:call-template name="Zone"/>
  </xsl:when>
</xsl:for-each>

And this works. But on some of the larger projects the transformation takes absolute ages. That is because in pseudo code this translates to:

  for each <zone> in <zones>
    find any <device> in <devices> with reference to <zone>
    if found
      apply zone template
    endif
  endfor

With 2000 zones to iterate over - and each iteration triggering up to 8800 searches for a qualifying device - you can imagine this taking a very long time.

And to compound problems, libxslt provides no API for progress reporting. This means that for a long time our application will appear frozen while it imports and converts the customer XML.

I do have the option to write every zone unconditionally, and upon the application bootstrapping from our (output) XML, remove or ignore any zones that have no devices placed in them. And it may turn out that this may be the only option I have.

The downside to this is that my output XML then contains a lot of zones that are not referenced. That makes it a bit difficult to consolidate what we have in our configuration and what parts of it the application is actually using.

My question to you is:

Have I got other options that ensure that the output XML only contains used zones?

I am not averse to performing a follow-up XSLT conversion. I was for instance thinking that it may be possible(?) to write an attribute used="false" to each <Zone> element in my output. Then as I go over the devices, I find the relevant zone in my output XML (providing it is assigned / zone is non-zero) and change this to used="true". Then follow up with a quick second transformation to remove all zones which have used="false".

But, can I reference my own output elements during an XSLT transformation and change its contents?

Upvotes: 0

Views: 44

Answers (1)

Martin Honnen
Martin Honnen

Reputation: 167716

You said you have a kind of identity transformation so I would use that as the starting point, plus a key:

<xsl:key name="zone-ref" match="device" use="zone"/>

and an empty template

<xsl:template match="zones/zone[not(key('zone-ref', @id))]"/>

that prevents unreferences zones from being copied.

Or, if there are other conditions, then e.g.

<xsl:template match="zones/zone[@id > 0 and not(key('zone-ref', @id))]"/>

Upvotes: 1

Related Questions