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
There's a great deal of data in the JSONPath comparisons, but each query represents an isolated data point, and some cannot be understood except in combination with other queries. For example, understanding the consensus on naming in the dot notation requires looking at both $.<etc> and [?(@.<etc>)], as inconsistencies abound.
@cburgmer, have you thought about starting a document on your site that attempts to analyze the data? One that limits itself to comparing and contrasting the data, but not prescribing? If you do, I would be interested in contributing PR's on specific topics, such as a summary of different approaches to the filter expression applied to a JSON object, or an analysis of differences across implementations in the recursive descent operator.
The text was updated successfully, but these errors were encountered:
I missed that. `OPEN_QUESTIONS.md` would actually be a good start. The one line questions could be expanded into short sections that interpret what the comparison data reveals about them.
On Thursday, July 29, 2021, 04:34:01 a.m. EDT, Christoph Burgmer ***@***.***> wrote:
The best I can offer is the OPEN_QUESTIONS.md document. However nothing structured. Would be interested to see what structure you have in mind!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
There's a great deal of data in the JSONPath comparisons, but each query represents an isolated data point, and some cannot be understood except in combination with other queries. For example, understanding the consensus on naming in the dot notation requires looking at both
$.<etc>
and[?(@.<etc>)]
, as inconsistencies abound.@cburgmer, have you thought about starting a document on your site that attempts to analyze the data? One that limits itself to comparing and contrasting the data, but not prescribing? If you do, I would be interested in contributing PR's on specific topics, such as a summary of different approaches to the filter expression applied to a JSON object, or an analysis of differences across implementations in the recursive descent operator.
The text was updated successfully, but these errors were encountered: