Return-Path: 
 <cocoon-dev-return-35059-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 44460 invoked by uid 500); 10 Jan 2003 16:26:08 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 44448 invoked from network); 10 Jan 2003 16:26:08 -0000
Date: Fri, 10 Jan 2003 17:26:07 +0100 (CET)
From: Giacomo Pati <giacomo@apache.org>
Sender: giacomo@lapgp
To: cocoon-dev@xml.apache.org,  <nicolaken@apache.org>
Subject: Re: [RT]: Names for pipeline components section
In-Reply-To: <3E1EEE00.3080606@apache.org>
Message-ID: <Pine.LNX.4.44.0301101726000.1964-100000@lapgp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Fri, 10 Jan 2003, Nicola Ken Barozzi wrote:

>
> Stefano Mazzocchi wrote:
> [...]
>
> > The pipelines are statically built and must remain so. Having a verb
> > describing the act of piping might not reflect the concept that
> > pipelines are static assemblations of operational constructs.
> >
> > So, I like
> >
> >  <components>
> >   <pipes>
> >    <pipe>
> >
> > and
> >
> >  <pipelines>
> >   <pipeline>
> >    <match>
> >     <generate>
> >
>
> Too bad this breaks our mapping between java names and sitemap names.

What mappings?

Giacomo


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