The entire article rests on this: > JSON was not designed to have such features [as XPath, XML Schema, XSL, etc.] But this claim is not justified, just stated

The entire article rests on this: > JSON was not designed to have such features [as XPath, XML Schema, XSL, etc.] But this claim is not justified, just stated. And the supposed inferiority of eg. JSONPath vs XPath is not justified either. I would actually claim that JSONPath is superior to XPath. JSONPath is much simpler, easier to understand, easier to implement, and still fulfills the most common use cases. Also JSONPath can be evaluated on a streaming input, which is not possible for XPath in general (maybe some subset of XPath queries could support streaming).