Jeni's Musings

Jeni,

Do you think that it is a good practice to have a stand-alone XSLT module, the compile-time validity of which is dependent on global objects (such as xsl:variable s) in other modules? Could you provide an example when doing this is recommended or when it cannot be avoided?

It seems to be just common sense that the including module should depend on the ones it is including/importing — not the opposite.

Even when we have nice tools such as Oxygen, that help make such practice more bearable, does this make it a good practice?

Dimitre Novatchev