Changed the query language from JMESPath to JSONPath #18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Link to the general page of JSONPath so I can remember: https://tools.ietf.org/wg/jsonpath/ |
|
@webron can you approve/merge? |
|
I'm looking at implementing something to do overlays; can I assume this will be merged? I think it should be, if that counts at all! |
|
Uh... current draft is https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base. It's on v20 now, which has some significant changes from v4. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated the proposal to use JSONPath based on the current draft https://www.ietf.org/id/draft-ietf-jsonpath-base-04.html
JMESPath was originally selected because it had a specification and an extensive test suite. However, experimentation has shown that JMESPath is optimized to transforming the input JSON document into an output JSON document. The goal is to select and project. However, for Overlays, the objective is to select a set of elements in the target document. There is no need for the ability to project new JSON objects.
Since the original draft of the Overlay specification was created, there has been an effort in the IETF to standardize the JSONPath specification. The original JSONPath definition relied on scripting support from the underlying implementation. This would not be suitable for the Overlay specification. The new IETF version is taking efforts to make the JSONPath use a fully specified query expression that is not implementation dependent.