Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-Id: <200111211651.fALGp4323356@orion.rgv.hp.com>
From: Ovidiu Predescu <ovidiu@cup.hp.com>
To: Gianugo Rabellino <gianugo@rabellino.it>
Cc: cocoon-dev@xml.apache.org
Subject: Re: [Fwd: freshmeat project listing for Cocoon] 
In-Reply-To: Your message of "Wed, 21 Nov 2001 16:45:56 +0100."
             <3BFBCC34.3090806@rabellino.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Nov 2001 08:51:03 -0800
Sender: ovidiu@orion.rgv.hp.com

On Wed, 21 Nov 2001 16:45:56 +0100, Gianugo Rabellino <gianugo@rabellino.it> wrote:

> Stefano Mazzocchi wrote:
> 
> > Now, I'd be *VERY* happy to pass over the hand to somebody else who is
> > willing to keep the project entry alive and not vegetating as it is
> > right now.
> > 
> > This should be done along with Cocoon 2.0 final to show the renewed
> > development life of this project.
> > 
> > What do you think? any committer volunteering for this?
> 
> I think that Carsten is the right man for the job and that he's right 
> when he says that this task should be in the "release manager" hands.
> 
> As a side note, I must confess that I don't like that much the "About" 
> part, I think that it can and should be rephrased to reflect what Cocoon 
> really is.
> 
> This is the original content:
> 
> About: Cocoon is a pure Java publishing framework servlet that relies on 
> DOM, SAX, XML, and XSL to provide web content. Web content generation is 
> mostly based on HTML. Cocoons changes this view allowing content to be 
> written in XML, style on XSL stylesheets and logic in another XSL 
> stylesheet that converts the whole thing to the XSP namespace. This 
> allows the complete separation of the three layers used to create 
> content. The Cocoon framework creates web content by processing these 
> layers with the ability to create, for example, valid HTML as output.
> 
> I see at least the following issues with it:
> 
> 1. Cocoon is not a servlet, this is severely limiting the power of Cocoon.
> 
> 2. "Web content generation is mostly based on HTML"??? 'nuff said...
> 
> 3. "Cocoons changes this view allowing content to be written in XML, 
> style on XSL stylesheets and logic in another XSL stylesheet that 
> converts the whole thing to the XSP namespace". Ugly, to say the least.
> 
> I think that such description is poor, wrong and troublesome. I think 
> also that it's worth the effort to spend some time investigating juicy 
> alternatives that might be attractive to newcomers and people willing to 
> know what Cocoon is. The same snippet should be placed in the project 
> home page in place of the negative presentation that it's present now.
> 
> Here is a small suggestion for a change:
> 
> "Apache Cocoon is a XML publishing framework leveraging the power of the 
> latest XML technologies. Designed for performance and scalability around 
> the SAX event model, Cocoon offers a flexible and powerful environment 
> based on the separation of concerns between content, logic and style and 
> on a central configuration file which drives the whole processing. 
> Cocoon is able to interact with most data sources (from filesystems to 
> RDBMS, from LDAP to native XML databases) and to serve the content to 
> different devices in different formats (HTML, WML, PDF, SVG, RTF just to 
> name a few). Cocoon can be used both as a servlet or in a standalone 
> fashion."

Very good, +1 from me!

Regards,
-- 
Ovidiu Predescu <ovidiu@cup.hp.com>
http://orion.rgv.hp.com/ (inside HP's firewall only)
http://sourceforge.net/users/ovidiu/ (my SourceForge page)
http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org