Edward Surov

But what we should check in this case? For example, implementation X returns `$.a.b`, and implementation Y returns `$["a"]["b"]` as a path string. The expressions are different, but they do...

> Also, I't unclear whether most languages even let you distinguish between a key being present or with value `null`. I think that should not be language-dependent. JSON is a...

It would be a nice feature to ignore implementation while calculating consensus, but evaluate it's work later (maybe show results in a different table or mark it's colunn somehow)

I agree.

Here is [k8s dialect of JsonPath](https://kubernetes.io/docs/reference/kubectl/jsonpath/), and it oficially allows to omit root (k8s uses [exponent-io/jsonpath](https://github.com/exponent-io/jsonpath) - seems we don't have it in the table yet).

As for me, root can be easily omitted in outer expressions (`$.foo` -> `.foo`), but that may become confusing in filters (`$.foo[?(@.bar==$.baz)]` -> `.foo[?(@.bar==.baz)]`? Or should we omit most commonly...

> Where is exponent-io/jsonpath used by Kubernetes? I've just looked into [it's `go.mod`](https://github.com/kubernetes/kubernetes/blob/master/go.mod#L242) without further investigations, so I may be wrong, too.

I think that classic octal notation with leading zero is highly confusing for many modern users. I think that there's no reason to forbid leading zeros. My implementation fails to...

> most of the JSONPath implementations lack a formal grammar, so it can be hard to tell whether a "feature" has been intended or merely reflects absent validation I tend...

Dark ages of JsonPath have ruined my beautiful idea, alas. But I still think that we should keep as close to existing JSON spec as possible; something like `STRING_KEY ::=...