XQuery insists on associating a namespace with the functions and
variables exported by each module. If you want to be disciplined, then I
don't think that's a bad discipline to follow. It's certainly more
sensible to use namespaces than to use naming conventions of your own
invention.
Michael Kay
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
Harold Putman
Sent: 21 November 2003 19:51
To: XSL-List(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] naming conventions for modular XSLT
Hi,
I am starting to break up my large XSLT into separate modules
using xsl:include. It seems like I should have a way to
indicate in my XSLT where the templates and variables come
from if they are not in the same file. Is there a convention
for doing this?
I am trying out using a dot in the names of things that come
from extern modules. That is: main.xsl includes util.xsl.
In util.xsl I name everything that I intend to "export" with
a name beginning with util.
Then in my main.xsl I have
...
Has anyone else done things like this? Is there any downside
to doing it this way?
Thanks,
Harold Putman
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list