Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Thu, 30 May 2002 15:34:05 +0200
From: Christian Haul <haul@dvs1.informatik.tu-darmstadt.de>
To: cocoon-dev@xml.apache.org, Nicola Ken Barozzi <nicolaken@apache.org>
Subject: Re: [VOTE] Syntax for module-based sitemap variables
Message-ID: <20020530153404.N9043@bremen.dvs1.informatik.tu-darmstadt.de>
Reply-To: haul@dvs1.informatik.tu-darmstadt.de
References: <3CF5EBA6.3070405@anyware-tech.com>
 <004e01c207bf$9fdc0620$670004c0@PC103>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004e01c207bf$9fdc0620$670004c0@PC103>
User-Agent: Mutt/1.3.22.1i
Organization: Databases and Distributed Systems Group,
 Darmstadt University of Technology

On 30.May.2002 -- 11:51 AM, Nicola Ken Barozzi wrote:
> From: "Sylvain Wallez" <sylvain.wallez@anyware-tech.com>
> 
> > Hi team,
> > 
> > We all agree to add module-based sitemap variables, but we didn't came 
> > to a consensus about it's syntax. So let's vote to make a choice. To 
> > illustrate each possible syntax, I will consider the substitution of the 
> > "foo" request parameter using the "request" InputModule.
> > 
> > Here are the various syntaxes that people have proposed so far :
> > 
> > 1 : {request:foo}
+1
> > 2 : {/request:foo}
+0.5
> > 3 : {module:request:foo}
+1
> > 4 : {/module:request:foo}
+0.5
> > 5 : {module://request/foo}
+0
> 6 :  (all below apply, similarly to urls; prefer for consistency)
>  
>           {foo}  (default sitemap module )
>           {pathto/foo}  (default sitemap module with path)
>           {module:request://pathto/foo} (complete parameter uri)
+1
> > My +1 goes to (1) : I don't see the need to explicitly specify 
> > "module:", just as we don't prefix URLs with "source:" or "url:" to 
> > specify if they should be handled by a SourceFactory or URLFactory. And 
> > if one day we add another mechanism to InputModules, the choice will be 
> > the job of a variable resolver, just at it is today's job of the 
> > SourceResolver for URLs.
> 
> +1
+1
 
> > In order to have a more formal definition of sitemap variables, I 
> > suggest that we consider unprefixed variables to belong to a builtin 
> > "sitemap" module, which can be named explicitely, for example if the 
> > variable name contains a colon, e.g. "{sitemap:foo:bar}".
> 
> +1
+1
 
> Basically I want them to behave like urls do.

+1

	Chris.

-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

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