Class Transformation

java.lang.Object
eu.bandm.tools.xslt.base.MessageSender
eu.bandm.tools.xslt.base.Transformation

public class Transformation extends MessageSender
Represents one complete xslt program, which processes any xml input (for which a tpath interpreter exists), and delivers a bandm tdom result of a given type (or just plain text, in case of non-xml mode). It consists of (1) at least ONE(1) xslt file = Templates, which is top-level, (2) possibly further files, included or imported, (3) a library of tpath functions.
Import precedence is considered for
  • xsl:strip-space [XSLT10:3.4]
  • xsl:apply-templates [XSLT10:5.5 list 1 point 1]
  • xsl:apply-import [XSLT10:5.6] not only precedence, but more restricted
  • xsl:call-template [XSLT10:5.6] (not clear)
  • xsl:namespace-alias [XSLT10:7.1.1]
  • xsl:attribute-set [XSLT10:7.1.4] (attribute-wise merging)
  • xsl:variable and xsl:param [XSLT10:11.4] (not very clear)
  • xsl:key NOT for non-conflicting [XSLT10:12.2] (but else? not clear)
  • xsl:namespace-alias [XSLT10:7.1.1]
  • xsl:decimal-format NOT for conflicts [XSLT10:12.3]
  • xsl:output, attributes except cdata-section-elements [XSLT10:16]

The scope of the following constructs does not extend in a transparaent way, neither to imports nor to includes,
"A subtree rooted at an xsl:stylesheet element does not include any stylesheets imported or included by children of that xsl:stylesheet element."
in CONTRADICTION to [SXLT10:2.6.1]
"The fact that template rules or definitions are included does not affect the way they are processed."
  • xsl:exclude-result-prefices [XSLT10:7.1.1]
  • xsl:extension-element-preficxes [XSLT10:14.1]

FIXME "growing result" nachhalten, um [comment][attrib][/attrib][/comment] etc. schon STATISCH zu erkennen ?