JSON Path Working Group

Why not standardize JMESPath instead? C.f. https://gatling.io/2019/07/introducing-jmespath-support/

I’m not an expert here, but seems easier to use something well specified rather than attempting to knit multiple specs together.