Yes, Kerry. I think that propagation would have a great potential. And it would cetainly be very useful for my current needs.
It would leave the input designer full control over it.
I would (by default, unless prevented by an invocation option) exclude from the output the tcases "reserved" value key words (like property, when, whenNot, etc).
Or, alternatively, tcases could by default work as it does now (warning about unexpected keys in the <value>), and, when an invocation option is present, propagating transparently all the included key-value pairs (even the "reserved" ones, that could also be processed by the xslt).
Thanks,
Jose