Hacker News Reader

Comment by gte910h | Hacker News Reader

http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m1/inde...

To allow you to use XSLT tools apparently.

XSLT and XPath is about the only reason I can see to use this. But, you know, how hard is:

   x.person.addresses[0].city?

I guess XPath is easier when you probably have to do something like this:

   JSONObject json = (JSONObject) JSONSerializer.toJSON( jsonTxt )
   String city = json.getJSONObject("person").getJSONArray("addresses").getJSONObject(0).getJSONObject("city");

Or however you'd do it in Java.

That's not hard, what's hard is

   //person[@alive="true"]/pets//dog[@hair="long"]/*/flea[@name]

still, i think an xpath evaluator for json would have been the way to go here instead

You appear to be confusing Java and Javascript.

JSON stands for Javascript Object Notation.

In Java the equivalent would simply be serialization.

NB: if XSLT and XPath is the solution, you've already lost.

JSON is used for far far more than javascript these days. It's a far better communication protocol than XML for most things.

"Some people, when confronted with a problem, think 'I know, I'll XSLT.' Now they have two problems."

(edited for relevance)

Reply on news.ycombinator.com