> From: Ivelin Ivanov [mailto:[EMAIL PROTECTED]] > > Stefano Mazzocchi wrote: > > Mattam wrote: ... > > So, IMO, the best long term solution would be: > > > > 1) deprecate both XIncludeTransformer and CIncludeTransformer > > 2) change CIncludeTransformer to IncludeTransformer > > 3) make IncludeTransformer work just on a cocoon-specific namespace > > > > what do you think? > > > I think that we should leave XInclude transformer in. > Many people think Cocoon is hard to learn. Having as many references as > possible to standards is essential. > > I would suggest that the XInclude transformer takes sitemap parameters > which specify on which namespace to act. So if no parameters are > provided it will act on "http://www.w3.org/xinclude/2000";. > > Just like XSLT is useful on the server, XInclude is too. > Although some browsers support XSLT and more will do so in future, > XSLT on the server is valuable. The decision if transformation should be > applied or not belongs to the sitemap not the transformer. > If XInclude should be left to the client, then the sitemap has to make > sure that the XIclude transformer is either not applied at all, or at > least not with the default namespace.
+1. Namespace should be configurable, and include transformer should have all features of cinclude and xinclude. Then, cinclude could be safely deprecated in favor of new xinclude. Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
