cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: [Announcement] sitemap variables
Date Sat, 12 Oct 2002 17:00:30 GMT
Ivelin Ivanov wrote:

>----- Original Message -----
>From: "Giacomo Pati" <giacomo@apache.org>
>To: <cocoon-dev@xml.apache.org>
>Sent: Saturday, October 12, 2002 11:05 AM
>Subject: Re: [Announcement] sitemap variables
>
<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.
>>    
>>
>
>I had exactly the same thought, but didn't want to be the first to muddy the
>waters after such a heavy discussion.
>id will align it with the concept usually used in other XML schemas.
>For example in ANT, each element has an id and can be refered anywhere in
>the script later by a refid attribute.
>  
>

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


Mime
View raw message