There are also implementations in many languages as Java (https://github.com/jayway/JsonPath), Python (http://pypi.python.org/pypi/jsonpath/), Ruby (https://github.com/joshbuddy/jsonpath) and Perl (https://github.com/masukomi/jsonpath-perl).
There are also implementations in other languages as Java (<a href="https://github.com/jayway/JsonPath" rel="nofollow">https://github.com/jayway/JsonPath</a>), Python (<a href="http://pypi.python.org/pypi/jsonpath/" rel="nofollow">http://pypi.python.org/pypi/jsonpath/</a>), Ruby (<a href="https://github.com/joshbuddy/jsonpath" rel="nofollow">https://github.com/joshbuddy/jsonpath</a>) and Perl (<a href="https://github.com/masukomi/jsonpath-perl" rel="nofollow">https://github.com/masukomi/jsonpath-perl</a>).
I wrote a really simple JSON parsing tool using a JavaScript implementation of JSONPath. It's been invaluable as a tool to analyze the JSON returned by my APIs.<p>I guess I should add a nice template (right now it's really crude HTML with just the bare necessities) and release it to the world... maybe next weekend :)
Legitimate question: can someone tell me why something like this would be useful? Don't most libraries that handle json decoding make parsing it extremely easy? I read through the examples on the site, and I'm still not convinced something like JSONPath is necessary for what they're doing.
I made a similiar type of library for Erlang called props[1], which also includes common data manipulation tasks like merging, replacing data at a path, etc.<p>[1] <a href="https://github.com/greyarea/props" rel="nofollow">https://github.com/greyarea/props</a>