- markup (52)
- xml (7)
- xslt (21)
- atom (8)
- overlapping markup (2)
- schema (9)
- creole (4)
- xforms (1)
- pipelines (7)
- coding (2)
- dtll (1)
- genealogy (3)
- gtd (1)
- hardware (1)
- legislation (1)
- ontologies (2)
- unicode (1)
- web (24)
- google (3)
- rdf (6)
- rest (3)
- wikis (1)
- work (1)
- xpath (1)
- xquery (1)
- xtech2008 (3)
- life (26)
- children (5)
- equality (6)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (7)
- xtech (6)
- blog (7)
- drupal (3)
Re: Lessons learnt
Far be it for me to tell you anything about XSLT, but in terms of knowing whether you’ve ignored some content in the input, what I often do with unfamiliar input content is to start my stylesheet with something like
<xsl:template match=”*”> <xsl:message terminate=”yes”> <xsl:text>element not handled: </xsl:text> <xsl:value-of select=”name()”/> </xsl:message> </xsl:template>
That way, if the stylesheet hits some input that I’ve forgotten about, it tells me about it. This assumes that you are using template pattern matching (apply-templates) rather than procedural logic in your stylesheets, but that is what I usually do.
Cheers, Tony.