cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <giac...@apache.org>
Subject Re: [RT]: Names for pipeline components section
Date Fri, 10 Jan 2003 16:25:39 GMT
On Fri, 10 Jan 2003, Stefano Mazzocchi wrote:

> Nicola Ken Barozzi wrote:
> >
> >
> > Carsten Ziegeler wrote:
> >
> >> Giacomo Pati wrote:
> >>
> >>> On Fri, 10 Jan 2003, Carsten Ziegeler wrote:
> >>>
> >>>
> >>>> We currently have two sections named map:pipelines and map:pipeline
in
> >>>> the sitemap (2.1). As we all know from experience this is absolutely
> >>>> confusing and wasn't a good naming idea (my fault).
> >>>>
> >>>> I think Sylvain and Michael have already suggested new names, but
> >>>> I can't remember them and I'm too lazy to search the mail archives :)
> >>>>
> >>>> We need a new and simple name for the components section:
> >>>> <map:components>
> >>>>  <map:pipelines default="caching">
> >>>>    <map:pipeline .../>
> >>>>  ...
> >>>
> >>>
> >>> What about simply map:pipe[s]?
> >>>
> >>
> >> Yes, why not - if noone comes up with a better name, we will use that.
> >
> >
> > I'd prefer to keep the current naming instead of that one.
> >
> > For consistency it would be map:pipeline in the components, and map:pipe
> > in the "beefy" part.
> >
> >  pipeline generator transformer ...
> >  pipe     generate  transform   ...
> >
> > Inverting it is not so cool IMHO. I haven't yet seen users complain it's
> > not understandable and I've never had that problem myself.
>
> Careful. "pipe" is not only a verb, but also a noun. A believe that
> Giacomo was using it in that sense.
>
> Also, we made a seriuos effort to never use the same sitemap tag for
> meaning different things depending on its context (say, complete xpath
> compared to simple tag matching). This is a good pattern to follow, and
> might help a lot implementing sitemap editors in the future.
>
> Also, as far as using
>
>   <pipe>
>    <match>
>     <generate>
>
> where "pipe" is a verb, I would be against this because the pipeline are
> *not* piping themselves and are not active. They support the skeleton
> where the events flow.
>
> 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>


This was exactly what I had in mind. Thanks, Stefano, explaining it so
clearly.

Giacomo


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


Mime
View raw message