Use: ExpressionSelectingTable/tr[td//text()[contains(., ‘targetString’)]] This means: Select every tr that is a child of any table selected by the expression ExpressionSelectingTable and that (the tr) has at least one td child that has at least one text-node descendent that contains the string ‘targetString’
As other answers have noted, XPath 1.0 does not support regular expressions. Nonetheless, you have the following options: Use an XPath 1.0 expression (note the starts-with() and translate() functions) like this: .//div [starts-with(@id, ‘foo’) and ‘foo’ = translate(@id, ‘0123456789’, ”) and string-length(@id) > 3 ] Use EXSLT.NET — there is a way to use its … Read more
This is FAQ (but I’m lazy to search duplicates today) In XPath 1.0 //*[local-name()=’name’] Selects any element with “name” as local-name. In XPath 2.0 you can use: //*:name
I don’t use xmllint, but I think the reason your XPath isn’t working is because your doc.xml file is using a default namespace (http://purl.org/net/ulf/ns/0.4-02). From what I can see, you have 2 options. A. Use xmllint in shell mode and declare the namespace with a prefix. You can then use that prefix in your XPath. … Read more
Have you tried this? //myparent/mychild[text() = ‘foo’] Alternatively, you can use the shortcut for the self axis: //myparent/mychild[. = ‘foo’]
/a/*[not(self::b)]
The correct answer (note the brackets): (//span[@class=”Big”])[1] The following expression is wrong in the general case: //span[@class=”Big”][1] because it selects every span element in the document, that satisfies the condition in the first predicate, and that is the first such child of its parent — there can be many such elements in an XML document … Read more
First – you don’t need a navigator; SelectNodes / SelectSingleNode should suffice. You may, however, need a namespace-manager – for example: XmlElement el = …; //TODO XmlNamespaceManager nsmgr = new XmlNamespaceManager( el.OwnerDocument.NameTable); nsmgr.AddNamespace(“x”, el.OwnerDocument.DocumentElement.NamespaceURI); var nodes = el.SelectNodes(@”/x:outerelement/x:innerelement”, nsmgr);
The current node is whatever the template is currently operating on. Normally this happens to also be the context node, but the context node has special meaning within a nested XPath expression (the part in square brackets). There, it refers to whatever node is currently being tested for a match. Hence, the context node changes … Read more
In the second example XML file the elements are bound to a namespace. Your XPath is attempting to address elements that are bound to the default “no namespace” namespace, so they don’t match. The preferred method is to register the namespace with a namespace-prefix. It makes your XPath much easier to develop, read, and maintain. … Read more