chaosophist (kay-os-o-fist)
Chaosophistication – the subtle art of change
-
XML, Violence, Nokogiri and Xpath
I love Xpath.
It makes XML easy to use and easy to query. Gone are the days of parsing things with a SaxParser unless you're really hard up for control of you text.
Also, I love the Ruby Nokogiri Gem.
XML is like violence - if it doesn’t solve your problems, you are not using enough of it.
- Nokogiri docs
But I do have to say that there is a lack of good examples and documentation for anything particularly advanced. I found a working solution to my issue, but thought I'd paste here what I wanted to do versus what I ended up doing.
Given the following XML,
I'd like to grab two elements that include "Cover" in the tag, and then operate on each of them.
Nokogiri's use of Xpath easily allows the first query expression like so:
price_xml = doc_xml.xpath('Container/Set/*[contains(name(), "Cover")]')I've selected all the elements (using *) in Set, and then used an Xpath Expression function:
contains, in order to specify that Adult must be in the name. This returns two Nokogiri XML Nodes in Nodeset.
What I wanted to do was then select one of these elements based on a pattern in the tagname use my favorite tool, Xpath.
But I just couldn't get Nokogiri to give it to me, and several solutions ending up selecting way more than the 1 element I wanted. (Because the nodes in the Nodeset still contain relationships with their parents)
I'm cross posting this on StackOverflow as a question, just in case any Nokogiri Xpath enthusiasts want to recommend a solution that doesn't resort to find()
-
Tweets
Sites I Like
biz-technologist, data lover who dotes on his family, plays with tech. Europhile, travel junkie, startup-addict, CTO @ Flextrip (Tours & Activities Tech); Founding CTO of Everbread (Travel Search Tech).
