I think it would be nice if XPath rules for the XML language behaved exactly as regular XPath does. This is related to this bug (#915), where the standard XPath function text() doesn't work, because our wrapper instead creates a node text with an @Image. I think this is completely wrong and XML xpath rules would be more powerful and easier to write if we used Saxon's own xpath engine on the DOM instead of our AST wrapper. I think, to fix this, we need a new rule class XmlXPathRule that invokes Saxon directly (or rather, we should rehabilitate the current one, currently deprecated).
Originally posted by @oowekyala in #3413 (comment)
Also related to #2766
I think it would be nice if XPath rules for the XML language behaved exactly as regular XPath does. This is related to this bug (#915), where the standard XPath function
text()doesn't work, because our wrapper instead creates a nodetextwith an@Image. I think this is completely wrong and XML xpath rules would be more powerful and easier to write if we used Saxon's own xpath engine on the DOM instead of our AST wrapper. I think, to fix this, we need a new rule classXmlXPathRulethat invokes Saxon directly (or rather, we should rehabilitate the current one, currently deprecated).Originally posted by @oowekyala in #3413 (comment)
Also related to #2766