"G. Ken Holman" wrote:
I often have two namespaces for each library: a public one
(declaring global constructs users of the black box are allowed
to override) and a private one (declaring global constructs users
of the black box are not allowed to override).
I also use this technique. I wonder what naming scheme people here
use for the private namespace URI. Personally, over the time I use(d)
three different kinds of naming schemes:
http://company.com/project/some-stylesheet.xsl
some-stylesheet.xsl
impl:some-stylesheet.xsl
where "some-stylesheet.xsl" can have more levels, reflecting the
project structure:
http://company.com/project/some-module/some-style.xsl
Sometimes, I just use the same URI within all the stylesheets in the
project (mostly for small projects.)
Does someone use something else, or have any comments on those above?
Regards,
--
Florent Georges
http://www.fgeorges.org/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--