- 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: 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.