- From: Jirka Kosek <jirka@kosek.cz>
- Date: Wed, 10 Oct 2012 23:21:09 +0200
- To: Shaun McCance <shaunm@gnome.org>
- CC: public-multilingualweb-lt@w3.org
- Message-ID: <5075E6C5.8010401@kosek.cz>
On 10.10.2012 19:00, Shaun McCance wrote: > I was working with the DOM XPath API and noticed that it doesn't > have a standard way of binding variables to an XPath evaluation > context. That means you really can't support its:param if you're > using that API. Standard DOM is well known as the worst and the most impractical to use tree-based interface for XML. :-) In which language you are using DOM? Many languages extended DOM to support variable bindings. For example Java: http://docs.oracle.com/javase/1.5.0/docs/api/javax/xml/xpath/XPathVariableResolver.html .NET: http://msdn.microsoft.com/en-us/library/system.xml.xsl.xsltcontext.resolvevariable(v=vs.71).aspx > Would it make sense to make its:param an optional feature? We > were careful to specify that no variables should be used unless > specified in an its:param element. So I think we could safely > say something like "an implementation that does not support > its:param must not apply any rules from an its:rules element > that contains any its:param elements". I don't have strong position here. If it's to hard to implement this for implementors we can make it optional. 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 Wednesday, 10 October 2012 21:21:38 UTC