Closed goessner closed 1 year ago
Perhaps a simple solution would be to avoid the use of the term in 3.3 as this term doesn't appear to be used elsewhere.
Please see the simplification in https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/pull/286.
The term "current node" is traditionally used with iterating over children of structured nodes in filter selectors.
Now it also appears in 3.3 Semantics chapter in a different context:
To avoid confusion of readers, we might use a different term there. A good alternative would be "context node", which is also used by XPath in a similar context.