- 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: Automatic markup and XML pipelines
Thanks for the suggestions. Given the Microsoft/.NET bias in the organisation that I’m working for, I don’t think Ant would work, but there is NAnt, which I suppose might do the job. Then we’d just (perhaps) have to rewrite the pipeline in XProc syntax when it got finalised.
Similarly, we have an in-house content management system and I don’t think suggesting eXist would go down too well. I suppose we could script up some code to perform the transformations within the CMS, but it sounds like you’d get a lot of dependencies between the repository and the pipeline: adding a step would mean adding a collection, right? I think that’s something we want to avoid.