- markup (76)
- xml (11)
- xslt (23)
- pipelines (8)
- atom (9)
- overlapping markup (6)
- schema (11)
- creole (5)
- dtll (1)
- xforms (1)
- xpath (1)
- xquery (2)
- coding (2)
- datagovuk (1)
- genealogy (4)
- hardware (1)
- linked data (15)
- named graphs (1)
- opendata (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (77)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (45)
- ontologies (2)
- rdfa (8)
- rdfQuery (5)
- rest (6)
- wikis (1)
- work (3)
- legislation (2)
- xmlsummerschool09 (2)
- life (28)
- children (5)
- equality (6)
- gtd (1)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (11)
- ukgc09 (1)
- xtech (9)
- xtech2008 (3)
- blog (8)
- 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.