> > >did this fine: why break a perfectly good piece of software? > > That "perfectly good piece of software" was broken, and was not able = > to > fulfill Cocoon's aim, that is mainly Separation of Concerns.
Hardly "broken" but there was nothing in Cocoon 1 about separation of concerns, only about serving XML with XSL[T]. This phrase seems to have arisen since. > It puts in a page (content) something that tells what to do with the = > page, > which has *nothing* to do with the content of the page itself. You mean the xml-stylesheet PI. Yes, except that it's a convenient place to put it, avoiding the need for a catalog (which it seems is all that sitemap.xml is). Using entityrc and catalog files was always a pain when serving SGML with stylesheets. > But if you think that a page has to have all that is needed to render= > it, > there is no separation, of course ;-) It is poor document engineering to omit that information from the instance, in the same way that it is poor practice to omit the Document Type Declaration, because it means someone coming to the document from the outside requires exogenous information. But you certainly don't have to use it from that location if you prefer a catalog-based approach. In other words, separation of concerns is fine, but not at the expense of usability. > Cocoon1 separated Content and Style, but failed totally in separating > Administration and Flow from the first two. Not the way I implemented it, but that's history. > Cocoon2 separates Administration and programming quite well, and Coco= > on2.1 > will separate Flow as well (there is a schecoon in scratchpad that al= > ready > works). OK. Not needed at present, but nice to know. > If you think that all this is too complicated or theorical, No, it's fine, just the transition seems to be undocumented. > just read= > the > summary: > "Cocoon2 is better than Cocoon1 in every respect". Any clues as to a URL for this? Thanks for your help: this is looking marginally better, but some proper documentation for upgrading would have been useful. If I can get it to work, I'll certainly write it. ///Peter --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
