- 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 (16)
- modelling (1)
- named graphs (1)
- opendata (1)
- provenance (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (78)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (46)
- 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: Big XSLT applications just got easier to manage
Jeni isn’t talking about standalone modules.
Let me give an example. We want to do l16n of a web form. Generally the structure is going to be all the same, but the labels will be different. So we abstract the shared elements into a separate module that will be imported by the individual localised XSL components. E.g.
layout.xsl:
<dl> <dt><xsl:call-template name='name.label'/></dt> <dd><input type='text' name='name'/></dd> <dt><xsl:call-template name='email.label'/></dt> <dd><input type='text' name='email'/></dd> </dl>form_en.xsl:
form_fr.xsl:
Then you just process using whichever version of form.xsl best fits the locale. layout.xsl isn’t a standalone module, but you still need to edit it.