Evan, I avoid the use of "document()" by means of aggregation: one "map:part" for the template, the other "map:part" for data.
The use of meta-stylesheets doesn't excite me... I smell performance problems, though it is rather a sexy thing to do :) I even managed to have "for each" and "if" constructs in my tag library (based, IIRC on an XML.com article)... but maybe this was stretching the concept too far. Anyway, I agree with you that graphic designers shouldn't touch XSL and tag libraries are the way to go. Best regards, Luca Morandini [EMAIL PROTECTED] > -----Messaggio originale----- > Da: Lenz, Evan [mailto:lenze@;seattleu.edu] > Inviato: marted́ 12 novembre 2002 20.37 > A: '[EMAIL PROTECTED]' > Oggetto: RE: Separation of concerns? > > > I've taken this approach in the past. I've found that it involves > heavy (or > at least essential) use of the document() function. This approach has been > documented in a couple articles on XML.com. > > http://www.xml.com/pub/a/2000/07/26/xslt/xsltstyle.html > http://www.xml.com/pub/a/2002/03/27/templatexslt.html > > But I learned there are apparently problems with use of the document() > function in Cocoon, given current limitations with respect to caching. > > http://xml.apache.org/cocoon/faq/faq-xslt.html#faq-6 > > I was pleased to find Leigh Dodds' note on the Cocoon Wiki for > "metastylesheets". > > http://outerthought.net/wiki/Wiki.jsp?page=MetaStylesheets > > I'm now successfully using this approach in my current project to > implement > custom tag libraries in Cocoon without needing to use the document() > function. > > However, I am wondering how much this approach really scales. I > guess I will > find out. > > I believe that putting XSLT into the hands of graphic designers > and average > Web developers does *not* achieve separation of concerns. Custom tag > libraries is the way to go. XSP addresses that. But Cocoon appears yet to > directly address the problem of implementing tag libraries *in XSLT*. > Perhaps "metastylesheets" is the way to go. Or perhaps the document() > function is the way to go, and the caching problems just need to get > addressed. Or perhaps there is another approach that I haven't considered. > In any case, this needs to be addressed, IMHO. It's also quite > possible that > this has been fully addressed and I just haven't seen it. In that case, I > would appreciate a link to that discussion :-) > > Evan > > > -----Original Message----- > > From: Luca Morandini [mailto:spectrum.morandini@;ipzs.it] > > Sent: Tuesday, November 12, 2002 5:35 AM > > To: [EMAIL PROTECTED] > > Subject: R: Separation of concerns? > > > > Lorenzo, > > > > to ease the burden on your graphic designers, you could even > build a sort > > of > > "taglib" with XML elements to be expanded by an appropriate XSL. > > > > I've done a lib which allows me to specify "smart" HTML without the need > > of > > XSL (well, it works behind the scenes)... here's an example: > > > > <img src="{insert-request-parameter:images-home}/blank.gif" border="0" > > width="4"/> > > > > I hope you got the idea :) > > > > Best regards, > > > > Luca Morandini > > [EMAIL PROTECTED] > We are protected from the virus by Norton Antivirus Corporate Edition --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
