W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > June 2012

RE: ISSUE 16: parameters for rules

From: Yves Savourel <ysavourel@enlaso.com>
Date: Sat, 16 Jun 2012 09:36:47 +0100
To: "'Felix Sasaki'" <fsasaki@w3.org>
CC: <public-multilingualweb-lt@w3.org>
Message-ID: <assp.0514515384.assp.051475a450.000501cd4b9b$2bb8fc50$832af4f0$@com>
Hi Felix,

 

<its:param> would be just to define the defaults and declare the variables. I think it’s needed in XPath. The tools can override the defaults any way they want.

 

Jirka, please correct me if needed.

-ys

 

From: Felix Sasaki [mailto:fsasaki@w3.org] 
Sent: Saturday, June 16, 2012 6:04 AM
To: Yves Savourel
Cc: public-multilingualweb-lt@w3.org
Subject: Re: ISSUE 16: parameters for rules

 

Hi Yves,

 

wouldn't that need to conflicts between its:param and implementation specific parameters? E.g. 
http://www.saxonica.com/documentation/using-xsl/commandline.xml

allows to pass parameters to XSLT, and that's just one example. Would that have precedence over its:param?

 

Felix

 

2012/6/15 Yves Savourel <ysavourel@enlaso.com>

Hi Jirka, all,


> Implementation will be very easy for XSLT based toolchains.
> I'm not sure if all pure XPath libraries are able to
> bind parameters before evaluation.

For Java there is a variable resolver the interface for using XPath.

So, should we move forward with a definition for the parameters like this?:

<its:param name="theName">theDefaultValue</its:param>

It seems to be relatively simple to implement. See the attached files.

Cheers,
-ys





 

-- 
Felix Sasaki

DFKI / W3C Fellow

 
Received on Saturday, 16 June 2012 08:37:13 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:24:56 UTC