Re: best practices for managing xsl library

Much better than naming conventions, in 2.0 you can declare the type of the
parameter. This should be a mandatory coding standard: it's really useful
documentation, and it also catches a great number of silly coding mistakes.

btw which version of XSLT > XSLT 1.0 or 2.0 ?

Do you intend the library to be consumed or contributed too by public
users, if so striking the balance between the ease of 'submission'
versus completeness (re doc, tests, etc) can be quite tricky.

Do you intend to auto generate documentation from the library? If so you
may find embedding doc type elements directly inside xslt to be more
useful then have a seperate meta data document.

Also I would first setup various testing harnesses so you are able to
automate test running (be it xslt style unit tests, or simple transforms
with input and expected output); it is important to be able to run tests
against all major processors, I use Ant for this....you may find that
this influences how you design your distro.

Chris Johnson
cs.johnson@xxxxxxx