- 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: Functions or templates? My rules of thumb
I don’t understand what you’re saying. I agree that if you store atomic values in nodes, then you lose the type information about the atomic values. But we’re in agreement that atomic values should be generated by functions. It’s nodes that we’re discussing. And in XSLT 2.0 Basic, nodes can’t have any useful type information associated with them (all elements are
xs:untyped, all attributes arexs:untypedAtomic).