Return-Path: 
 <cocoon-dev-return-31915-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 13221 invoked by uid 500); 12 Oct 2002 17:13:03 -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 13205 invoked from network); 12 Oct 2002 17:13:02 -0000
Message-ID: <20021012171306.97403.qmail@web40802.mail.yahoo.com>
Date: Sat, 12 Oct 2002 10:13:06 -0700 (PDT)
From: Geoff Howard <cocoongeoff@yahoo.com>
Subject: Re: [Announcement] sitemap variables
To: cocoon-dev@xml.apache.org
In-Reply-To: <3DA8552E.2040007@anyware-tech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

How would this name overloading work with respect to:
- references from resources back to their calling
pipeline
- from a subsitemap back to the mounting reference

Seems these cases may make overloading desireable.

Geoff Howard

--- Sylvain Wallez <sylvain.wallez@anyware-tech.com>
wrote:
> <snip/>
> 
> >>>know what? I like it. It seems a pretty nice
> solution and the use of
> >>>anchor-like syntax is simple and understandable.
> >>>
> >>>So you get my +1 on this.
> >>>      
> >>>
> >>I don't know if the attribute should be called
> "name"? Isn't "id" the
> >>right one for that? This would also ensure there
> are no duplicates in a
> >>sitemap.
<snip/>
> I also thought of "id", but I'd like to avoid this
> no-duplicate 
> constraint, hence "name" : a sitemap is often
> consituted of similar 
> pipeline patterns, and the same name will IMO often
> be associated with 
> statements having the same role in different
> branches of the sitemap.
> 
> Example :
> 
> <map:pipeline>
>   <map:match pattern="foo-*" name="topmatcher">
>     <deep-nesting...>
>       <map:generate src="foobase-{#topmatcher:1}"/>
>     </deep-nesting...>
>   </map:match>
> 
>   <map:match pattern="bar-*" name="topmatcher">
>     <deep-nesting...>
>       <map:generate type="bar"
> src="{#topmatcher:1}"/>
>     </deep-nesting...>
>   </map:match>
> </map:pipeline>
> 
> An important difference between a sitemap and an Ant
> file is that 
> pipeline construction follows a path in the sitemap
> hierarchy, and thus 
> a statement cannot use variables defined by a
> statement that isn't one 
> of its ancestors. This isn't true in Ant files where
> targets can be 
> referenced from anywhere in the file.
> 
> I also discussed about name overloading on a single
> path at 
>
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103432718409833&w=2
> 
> I guess you may not like this overloading. In that
> case, what about 
> requiring uniqueness of names _on a path_, meaning
> the same name can be 
> used in different branches of the sitemap tree ?
> 
> Sylvain
> 
> -- 
> Sylvain Wallez
>  Anyware Technologies                  Apache Cocoon
>  http://www.anyware-tech.com          
> mailto:sylvain@apache.org
> 
> 
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email:
> cocoon-dev-help@xml.apache.org
> 


__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com

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