Return-Path: 
 <cocoon-dev-return-35054-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 22219 invoked by uid 500); 10 Jan 2003 16:09:57 -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 22183 invoked from network); 10 Jan 2003 16:09:57 -0000
Message-ID: <3E1EF0BD.2090704@apache.org>
Date: Fri, 10 Jan 2003 08:11:42 -0800
From: Stefano Mazzocchi <stefano@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [RT]: Names for pipeline components section
References: <LKENJPKDAIKAPKHEOCMMOEKICEAA.cziegeler@s-und-n.de>
 <3E1EDD2F.8070007@verizon.net>
 <20030110150733.GC322@fztig938.bank.dresdner.net>
 <3E1EE500.8070805@verizon.net>
 <20030110153709.GD322@fztig938.bank.dresdner.net>
In-Reply-To: <20030110153709.GD322@fztig938.bank.dresdner.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Michael Melhem wrote:
> On Fri, Jan 10, 2003 at 10:21:36AM -0500, Vadim Gritsenko wrote:
> 
>>Michael Melhem wrote:
>>
>>
>>>On Fri, Jan 10, 2003 at 09:48:15AM -0500, Vadim Gritsenko wrote:
>>>
>>>
>>>
>>>>Carsten Ziegeler wrote:
>>>>
>>>>  
>>>>
>>>>
>>>>>Michael Melhem wrote:
>>>>>
>>>>>    
>>>>>
>>>>>
>>>>>>I recall suggesting map:pipe in an earlier discussion because it
>>>>>>would confirm to "noun-verb" convention that already exists in 
>>>>>>the sitemap.
>>>>>>
>>>>>>      
>>>>>>
>>>>
>>>>... the only problem being that also pipe is a noun, it does not mean 
>>>>"somebody who makes pipelines". Currently, generator is "somebody who 
>>>>generates", transformer is "somebody who transforms", etc.
>>>>
>>>>But "pipe" noun does not describe an actor, "pipe" is passive... "Piper" 
>>>>could be better but it means "somebody who plays pipe"...
>>>>  
>>>>
>>>
>>>Yes generally "pipe" is a noun...but how about "to pipe something through"
>>>in this context it would be a verb .... 
>>>
>>
>>... this will result in "pipe" (n) - "pipe" (v) pair ... we made a circle :)
>>
>>So, options for the pair are:
>>
>>pipeline - pipeline (existing)
>>pipe - pipeline
>>pipeline - pipe
>>processor - process
>>piper - pipe
>>...
>>
>>Other suggestions?
> 
> 
> I was actually thinking:
> 
>  <components>
>    <map:matchers>
>    </map:matchers>
>  
>    <map:pipelines>
>     <map:pipeline/>
>    </map:pipelines>
>  </components>
>  ..
> 
>  <map:pipes>
>    <map:pipe>
>      <map:act>
>      <map:match>
>      ...
>    </map:pipe>
> 
>    <map:pipe>
>    </map:pipe>
>  </map:pipes>
> 
> thats my suggestion anyway :)

I'm sorry, but I'm -1 on such a severe back incompatible change for a 
simple naming reason. That would be a great way to piss people off (at 
least, I would be)

Besides, I already explained why <pipe> as a component and <pipeline> as 
a sitemap concept make sense and keep back compatibility.

Sitemap 1.1 should be extending Sitemap 1.0, not provide any 
back-incompatible change, otherwise this is really sitemap 2.0 and I 
woundn't like that.

-- 
Stefano Mazzocchi                               <stefano@apache.org>
--------------------------------------------------------------------



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