IETF JSONPath spec is now RFC 9535.

Author: jg-rp

README.md

@@ -2,6 +2,8 @@
 
 <p align="center">
 A flexible JSONPath engine for Python with JSON Pointer and JSON Patch.
+<br>
+We follow <a href="https://datatracker.ietf.org/doc/html/rfc9535">RFC 9535</a> and test against the <a href="https://github.com/jsonpath-standard/jsonpath-compliance-test-suite">JSONPath Compliance Test Suite</a>.
 </p>
 
 <p align="center">

docs/advanced.md

@@ -43,7 +43,7 @@ Add, remove or replace [filter functions](functions.md) by updating the [`functi
 
 ### Type System for Function Expressions
 
-[Section 2.4.1](https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-21#section-2.4.1) of the IETF JSONPath Draft specification defines a type system for function expressions and requires that we check that filter expressions are well-typed. With that in mind, you are encouraged to implement custom filter functions by extending [`jsonpath.function_extensions.FilterFunction`](api.md#jsonpath.function_extensions.FilterFunction), which forces you to be explicit about the [types](api.md#jsonpath.function_extensions.ExpressionType) of arguments the function extension accepts and the type of its return value.
+[Section 2.4.1](https://datatracker.ietf.org/doc/html/rfc9535#name-type-system-for-function-ex) of RFC 9535 defines a type system for function expressions and requires that we check that filter expressions are well-typed. With that in mind, you are encouraged to implement custom filter functions by extending [`jsonpath.function_extensions.FilterFunction`](api.md#jsonpath.function_extensions.FilterFunction), which forces you to be explicit about the [types](api.md#jsonpath.function_extensions.ExpressionType) of arguments the function extension accepts and the type of its return value.
 
 !!! info
 

docs/cli.md

@@ -189,7 +189,7 @@ $ json path -q "$.price_cap" -f /tmp/source.json --output result.json
 
 _New in version 0.10.0_
 
-Disables JSONPath filter expression well-typedness checks. The well-typedness of a filter expression is defined by the IETF JSONPath Draft specification.
+Disables JSONPath filter expression well-typedness checks. The well-typedness of a filter expression is defined by RFC 9535.
 
 ### `pointer`
 

docs/index.md

@@ -2,9 +2,9 @@
 
 JSONPath is a mini language for selecting objects from data formatted in JavaScript Object Notation, or equivalent Python objects, like dictionaries and lists.
 
-Python JSONPath is a non-evaluating, read-only implementation of JSONPath, suitable for situations where JSONPath query authors are untrusted. We follow most of the [IETF JSONPath draft](https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-13). See [Notable differences](syntax.md#notable-differences) for a list of areas where we deviate from the standard.
+Python JSONPath is a non-evaluating, read-only implementation of JSONPath, suitable for situations where JSONPath query authors are untrusted. We follow most of [RFC 9535](https://datatracker.ietf.org/doc/html/rfc9535). See [Notable differences](syntax.md#notable-differences) for a list of areas where we deviate from the standard.
 
-Since version 0.8.0, we also include implementations of [JSON Pointer](pointers.md) ([RFC 6901](https://datatracker.ietf.org/doc/html/rfc6901)) and [JSON Patch](api.md#jsonpath.JSONPatch) ([RFC 6902](https://datatracker.ietf.org/doc/html/rfc6902)), plus methods for converting a [JSONPathMatch](api.md#jsonpath.JSONPathMatch) to a `JSONPointer`.
+We also include implementations of [JSON Pointer](pointers.md) ([RFC 6901](https://datatracker.ietf.org/doc/html/rfc6901)) and [JSON Patch](api.md#jsonpath.JSONPatch) ([RFC 6902](https://datatracker.ietf.org/doc/html/rfc6902)), plus methods for converting a [JSONPathMatch](api.md#jsonpath.JSONPathMatch) to a `JSONPointer`.
 
 ## Install
 

docs/syntax.md

@@ -1,6 +1,6 @@
 # JSONPath Syntax
 
-Python JSONPath's default syntax is an opinionated combination of JSONPath features from existing, popular implementations, and much of the [IETF JSONPath draft](https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-11). If you're already familiar with JSONPath syntax, skip to [notable differences](#notable-differences).
+Python JSONPath's default syntax is an opinionated combination of JSONPath features from existing, popular implementations and [RFC 9535](https://datatracker.ietf.org/doc/html/rfc9535). If you're already familiar with JSONPath syntax, skip to [notable differences](#notable-differences).
 
 Imagine a JSON document as a tree structure, where each object (mapping) and array can contain more objects, arrays and scalar values. Every object, array and scalar value is a node in the tree, and the outermost object or array is the "root" node.
 
@@ -201,10 +201,9 @@ This is a list of things that you might find in other JSONPath implementation th
 - Python JSONPath is strictly read only. There are no update "selectors", but we do provide methods for converting `JSONPathMatch` instances to `JSONPointer`s, and a `JSONPatch` builder API for modifying JSON-like data structures using said pointers.
 - We don't attempt to handle JSON documents without a top-level array or object (or equivalent Python objects).
 
-And this is a list of areas where we deviate from the [IETF JSONPath draft](https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-13).
+And this is a list of areas where we deviate from [RFC 9535](https://datatracker.ietf.org/doc/html/rfc9535).
 
 - The root token (default `$`) is optional and paths starting with a dot (`.`) are OK. `.thing` is the same as `$.thing`, as is `thing`, `$[thing]` and `$["thing"]`.
-- Whitespace is mostly insignificant unless inside quotes.
 - The built-in `match()` and `search()` filter functions use Python's standard library `re` module, which, at least, doesn't support Unicode properties. We might add an implementation of `match()` and `search()` using the third party [regex](https://pypi.org/project/regex/) package in the future.
 - We don't require property names to be quoted inside a bracketed selection, unless the name contains reserved characters.
 - We don't require the recursive descent segment to have a selector. `$..` is equivalent to `$..*`.

jsonpath/env.py

@@ -352,8 +352,8 @@ def validate_function_extension_signature(
     ) -> List[Any]:
         """Compile-time validation of function extension arguments.
 
-        The IETF JSONPath draft requires us to reject paths that use filter
-        functions with too many or too few arguments.
+        RFC 9535 requires us to reject paths that use filter functions with
+        too many or too few arguments.
         """
         try:
             func = self.function_extensions[token.value]
@@ -452,10 +452,10 @@ async def getitem_async(self, obj: Any, key: object) -> Any:
     def is_truthy(self, obj: object) -> bool:
         """Test for truthiness when evaluating JSONPath filter expressions.
 
-        In some cases, the IETF JSONPath draft requires us to test for
-        existence rather than truthiness. So the default implementation returns
-        `True` for empty collections and `None`. The special `UNDEFINED` object
-        means that _obj_ was missing, as opposed to an explicit `None`.
+        In some cases, RFC 9535 requires us to test for existence rather than
+        truthiness. So the default implementation returns `True` for empty
+        collections and `None`. The special `UNDEFINED` object means that
+        _obj_ was missing, as opposed to an explicit `None`.
 
         Arguments:
             obj: Any object.

jsonpath/function_extensions/arguments.py

@@ -20,8 +20,8 @@ def validate(
 ) -> List[Any]:
     """Generic validation of function extension arguments using introspection.
 
-    The IETF JSONPath draft requires us to reject paths that use filter
-    functions with too many or too few arguments.
+    RFC 9535 requires us to reject paths that use filter functions with too
+    many or too few arguments.
     """
     params = list(inspect.signature(func).parameters.values())