- From: Jirka Kosek <jirka@kosek.cz>
- Date: Mon, 18 Jun 2012 23:03:27 +0200
- To: Yves Savourel <ysavourel@enlaso.com>
- CC: 'Felix Sasaki' <fsasaki@w3.org>, public-multilingualweb-lt@w3.org
- Message-ID: <4FDF979F.1010508@kosek.cz>
On 16.6.2012 10:36, Yves Savourel wrote: > <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. Yes, each ITS implementation can provide it's own mechanism for setting ITS parameters. I think that Felix's concern was about possible name clashes with XSLT parameters he uses internally in his XSLT implementation. For XSLT based implementation it would be logical to map ITS parameters directly to XSLT parameters, because otherwise all XPath expression with variable references will have to be parsed and reconstructed later on. Felix, if this is your concern you can put your internal parameters into namespace. It's not very well know feature of XSLT, but you can have: <xsl:param name="my:param1"/> <xsl:value-of select="$my:param"/> This will prevent possible clashes with ITS parameters in your case. Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------
Received on Monday, 18 June 2012 21:03:54 UTC