[Jsonpath] [Errata Held for Document Update] RFC9535 (8352)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 25 February 2026 19:02 UTC

To: vladimir.gorej@gmail.com, stefan.goessner@fh-dortmund.de, glyn.normington@gmail.com, cabo@tzi.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20260225190240.C67FAC000CC4@rfcpa.rfc-editor.org>
Date: Wed, 25 Feb 2026 11:02:40 -0800
Message-ID-Hash: UTXVSVNGANSNH3SV5O7QTHWD67SILGD7
CC: andy@hxr.us, iesg@ietf.org, jsonpath@ietf.org, rfc-editor@rfc-editor.org
Precedence: list
Subject: [Jsonpath] [Errata Held for Document Update] RFC9535 (8352)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/S-pHE6dp2OdoVeS7Bwxy1pIfFw0>

The following errata report has been held for document update 
for RFC9535, "JSONPath: Query Expressions for JSON". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8352

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Vladimír Gorej <vladimir.gorej@gmail.com>
Date Reported: 2025-03-24
Held by: Andy Newton (IESG)

Section: 2.3.5.1

Original Text
-------------
comparable          = literal /
                      singular-query / ; singular query value
                      function-expr    ; ValueType


Corrected Text
--------------
comparable          = singular-query / ; singular query value
                      function-expr /  ; ValueType
                      literal

Notes
-----
The ABNF grammars in RFC 9535 were designed to be directly usable with PEG (Parsing Expression Grammar) parsers.

However, PEG parsers will fail to parse $[?blt(1==1)] or $[?true(1)==0] with the grammar as given, as they employ prioritized choice, where the order matters.

In the order given, they will try to match the `literal` rule in `function-argument` with the input `1==1`, and find that the `1` indeed matches a `number`, completing the match for `function-argument` and preempting the other choices.  The intended rest of the `function-argument`, `==1` does not match anything, and the rule fails.
By putting the more complex `logical-expr` first, the whole `1==1` matches, and the rule succeeds as intended.

Similary, the function name `true` matches as the literal `true` instead, and preempts parsing `true(1)` as the more complex `function-expr`.  Putting the `literal` choice last prevents the preemptive match.


--------------------------------------
RFC9535 (draft-ietf-jsonpath-base-21)
--------------------------------------
Title               : JSONPath: Query Expressions for JSON
Publication Date    : February 2024
Author(s)           : S. Gössner, Ed., G. Normington, Ed., C. Bormann, Ed.
Category            : PROPOSED STANDARD
Source              : JSON Path
Stream              : IETF

[Jsonpath] [Errata Held for Document Update] RFC9… RFC Errata System