Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 41353 invoked from network); 2 Oct 2003 12:42:47 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Oct 2003 12:42:47 -0000 Received: (qmail 68432 invoked by uid 500); 2 Oct 2003 12:42:41 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 68083 invoked by uid 500); 2 Oct 2003 12:42:39 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 68069 invoked from network); 2 Oct 2003 12:42:38 -0000 Received: from unknown (HELO linux.local) (80.116.68.72) by daedalus.apache.org with SMTP; 2 Oct 2003 12:42:38 -0000 Received: from apache.org (localhost [127.0.0.1]) by linux.local (Postfix) with ESMTP id D4AC884D36 for ; Thu, 2 Oct 2003 14:42:26 +0200 (CEST) Message-ID: <3F7C1D32.9040904@apache.org> Date: Thu, 02 Oct 2003 14:42:26 +0200 From: Gianugo Rabellino User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: followup (offlist) References: <0E4321AA-F4D5-11D7-9CE7-000393CFE402@apache.org> In-Reply-To: <0E4321AA-F4D5-11D7-9CE7-000393CFE402@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Bertrand Delacretaz wrote: > Le Jeudi, 2 oct 2003, � 14:28 Europe/Zurich, Berin Loritsch a �crit > >> ...For instance, if you changed BLOCK-INF to COCOON-INF, then it is >> very clear >> that the Cocoon solution is proprietary to Cocoon, and noone should >> expect >> a Cocoon block to function the same way in a Merlin/Phoenix environment. > > > Sorry, I overlooked this when saying that I basically agree with Stefano > on going our own way for blocks at this time. > > I'm +1 on changing the BLOCK-INF name to COCOON-INF or whatever makes > sense and does not cause conflicts. +1 here too. Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Now blogging at: http://blogs.cocoondev.org/gianugo/)