You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that we seem to be considering JSON "parity" in the v4 spec I'm adding this as a placeholder issue with a link to the JSONpath spec as a place to kick off a conversation on what that might entail.
As mentioned in #5, JSONPath reached the status of Internet standard (RFC 9535) in February, here is the link to the up-to-date spec: https://datatracker.ietf.org/doc/rfc9535/
Now that we seem to be considering JSON "parity" in the v4 spec I'm adding this as a placeholder issue with a link to the JSONpath spec as a place to kick off a conversation on what that might entail.
https://datatracker.ietf.org/doc/id/draft-goessner-dispatch-jsonpath-00.html
The text was updated successfully, but these errors were encountered: