Thanks for the explanation, Jirka. Yes, that was my concern. If we create a dedicated "its:param" element, we probably should add your guidance below. Felix 2012/6/18 Jirka Kosek <jirka@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 > ------------------------------------------------------------------ > > -- Felix Sasaki DFKI / W3C FellowReceived on Tuesday, 19 June 2012 03:59:22 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:45 UTC