My goal in generating these DocBook files is being able to postprocess them, importing them into some other tool, converting to HTML/PDF, etc. However, I can use advice about this choice as well. Why not input HTML, just print HTML -- because I want to enforce structure over the individual documents. Some versions of the resulting documents will keep some sections, others won't. Some material will be piped into other pieces of machinery. Why DocBook -- It already has a structure known to other tools. I am new to XML, XSLT and the gang. I have a feeling that this is the missing piece to organize the document, but I may be wrong. Why not use a wiki -- I tried! Honest! I selected TWiki which is able to provide structure for content... but something went wonky, and it ate an amount of work massive enough to encourage me to take up this hopefully not too big project.

I know of Class::DBI::AsXML which seems fine for the task of getting a direct XML representation from the database contents. I'd hope to postprocess this XML stuff into DocBook. I want to find a good toolchain for this.

So, my questions are, 1) Does the overall approach seem sane to your wisdom? 2) In either case :), which would be the way to perform raw XML to DocBook conversion from inside the said application? Should I (shudder) write down my XSLT sheet from the ground up or does CPAN hide a spell for me?

Respectfully yours