- 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
you might find some solution using Ant and continuous integration engines like Anthill pro… this is abuse of build systems to achieve ‘work’ … though it has worked for me well in the past when controlling pipelines of XML.
another approach might be using eXist XMLDB and having triggers on collections; each collection could represent a step in your workflow and when a document goes into there(or is updated) you could generate (xslt, xpath, xquery) some output (which could go to another collection and so on) … eXist is not really ready for prime time in its default configuration … I tend to wrap it up in a perl handler and block all access to it (via iptables)…. but very effective.
I have some significant experience with both these approaches and would be willing to answer questions.
cheers, Jim Fuller
Note that I have