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