This will probably end up being called "XSLTemplate".

Chime

should this be rolled in or is the proposal not the place for this?

I don't really agree with the assertion that "DTML and/or DOM manipulations via Python are not suited for this task ..." but who cares. :) I'm certainly in favor of XSLT support.

Well, actually, one should be able to make an argument for a technology/solution that consists of more than a negative assertion about alternate technology or solutions.

I'll not insist that this be changed, but, in the future, please take a tone that is more focussed on the positive contribution of what you are proposing.

Chime

The assertion was part of the problem statement, and so isn't all the proposal is based on. I'm not sure how I could have worded the problem positively, but I'll bear in mind tone from now on. I think the issue here is really the assertion of the problem. Perhaps if I expand on the problem statement it will solve this problem (no pun intended)

The deliverables are really features not deliverables. A deliverable is something like:

• A working implementation,

• User documentation