- From: Jirka Kosek <jirka@kosek.cz>
- Date: Fri, 06 Jul 2012 14:43:42 +0200
- To: Yves Savourel <ysavourel@enlaso.com>
- CC: public-multilingualweb-lt@w3.org
- Message-ID: <4FF6DD7E.5050309@kosek.cz>
On 6.7.2012 8:52, Yves Savourel wrote: > - We don't have restrictions about not using variables in XPath expressions, but we don't have a way to declare them and provide defaults. So I think it's important to have <its:param> (isn't it like fixing a 1.0 oversight?) Actually declared variables are part of XPath context. As we haven't said anything about XPath context i ITS 1.0 no variables were declared. So I think that ITS 1.0 is in this aspect fine (although it contains another small problems related to XPath integration). > - Should we make a distinction between: > > A) supporting <its:param>, that it: understanding <its:param> and providing the defaults value to the XPath engine, > > and B) (in addition) supporting overriding the ITS parameters, that is: providing a way (tool-specific) to set values other than the defaults? I think that we should say: - implementation MUST support its:param - implementation SHOULD provide means for changing its:param and such means are implementation defined 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 Friday, 6 July 2012 12:44:16 UTC