On Sat, May 06, 2006 at 05:16:42AM +0400, Oleg A. Paraschenko wrote: > Hello Kasimier, > > On Fri, 5 May 2006 10:42:26 +0200 > "Buchcik, Kasimier" <[EMAIL PROTECTED]> wrote: > > ... > > <!-- The new meda data element of Libxslt. --> > > <meta xmlns="http://xmlsoft.org/XSLT/"> > > <!-- > > Initialize the module "urn:test:myTest" at compile-time. > > The attribute @scope can be one of: > > 1) "global" - global storage of user-data for this module > > 2) "stylesheet-level" - per stylesheet-level storage of > > user-data for this module > > --> > > <initialize-module namespace="urn:test:myTest" scope="global"/> > > </meta> > ... > > > > Comments and further ideas are appreciated. > > I'd like to resist to this approach. The main problems are: > > * It's an odd thing to see developer-level data (how to initialize a > module) on the user-level (XSLT stylesheet). > > * Stylesheet is polluted by a processor-specific spots. If I have my > extension module for xsltproc, xalan, saxon, I'm not happy to add > meta instructions for each of them.
Yeah, I must admit I'm not fond of adding libxslt specific extension > Probably the best place to inform xsltproc about how to initialize > an module is the module itself. Yup sounds way better from my viewpoint :-) Daniel -- Daniel Veillard | Red Hat http://redhat.com/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ [email protected] http://mail.gnome.org/mailman/listinfo/xslt
