Support JSON path spec when it's here!

[gregsdennis]

Chore summary
IETF is building a specification for JSON Path. (Repo / Latest)

Tasks
Support the spec-defined syntax.

Additional context
I'm not sure what library you're using for JSON Path parsing and evaluation (or if it's home-grown), but it might be a good idea to support this when it's released. We're getting pretty close.

[gregsdennis]

Just saw in the docs that you're aware that the spec is coming, but the link is old (https://tools.ietf.org/html/draft-normington-jsonpath-00).

I also saw that you're using a combination of nimma and jsonpath-plus for parsing. It looks like jsonpath-plus is on the comparison site, but nimma isn't, so I've opened an issue to have it added.

[gregsdennis]

I've opened an issue with nimma to support the spec. I think that will trickle down to you.

[gregsdennis]

JSON Path now has an RFC!

https://www.rfc-editor.org/rfc/rfc9535.html

[mikekistler]

It looks to me that the JSON Paths accepted in the "given" field of a ruleset are not compatible with the new JSON Path RFC 9535. In particular, JSONPathPlus filters produce a stream of objects that match the filter whereas RFC 9535 says that a filter produces a stream of object members that match the filter. Sadly, I find the RFC 9535 behavior to be much less useful.