[Jsonpath] [Technical Errata Reported] RFC9485 (7990)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 13 June 2024 18:57 UTC

To: cabo@tzi.org, tbray@textuality.com, superuser@gmail.com, orie@transmute.industries, james.ietf@gmail.com, tbray@textuality.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240613185743.E2FD1204E21@rfcpa.rfc-editor.org>
Date: Thu, 13 Jun 2024 11:57:43 -0700
Message-ID-Hash: R3ZL62AWBMSICLALKYYZXTHTA3TCMNMN
CC: bjoern@dataspace.earth, jsonpath@ietf.org, rfc-editor@rfc-editor.org
Precedence: list
Subject: [Jsonpath] [Technical Errata Reported] RFC9485 (7990)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/_HNBVwPU2_TknBdJ_d_i_vIHEYs>

The following errata report has been submitted for RFC9485,
"I-Regexp: An Interoperable Regular Expression Format".

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

--------------------------------------
Type: Technical
Reported by: Bjoern Hoehrmann <bjoern@dataspace.earth>

Section: 5.1

Original Text
-------------
5.1.  Multi-Character Escapes

   I-Regexp does not support common multi-character escapes (MCEs) and
   character classes built around them.  These can usually be replaced
   as shown by the examples in Table 1.

                      +============+===============+
                      | MCE/class: | Replace with: |
                      +============+===============+
                      | \S         | [^ \t\n\r]    |
                      +------------+---------------+
                      | [\S ]      | [^\t\n\r]     |
                      +------------+---------------+
                      | \d         | [0-9]         |
                      +------------+---------------+

Corrected Text
--------------
5.1.  Multi-Character Escapes

   I-Regexp does not support common multi-character escapes (MCEs) and
   character classes built around them.  These can usually be replaced
   as shown by the examples in Table 1.

                      +============+===============+
                      | MCE/class: | Replace with: |
                      +============+===============+
                      | \d         | [0-9]         |
                      +------------+---------------+

Notes
-----
`\S` excludes the form feed and vertical tabulation characters in Perl, ECMAScript, and other implementations, while the suggested replacement includes them. Given the entire document is about interoperable regular expressions, misrepresentation of the common definition of `\S` runs counter to that. Including form feed and vertical tabulation literally in the replacement expression is not likely to be helpful, so removing the misleading rows seems to be the best option.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9485 (draft-ietf-jsonpath-iregexp-08)
--------------------------------------
Title               : I-Regexp: An Interoperable Regular Expression Format
Publication Date    : October 2023
Author(s)           : C. Bormann, T. Bray
Category            : PROPOSED STANDARD
Source              : JSON Path
Stream              : IETF
Verifying Party     : IESG

[Jsonpath] [Technical Errata Reported] RFC9485 (7… RFC Errata System
[Jsonpath] Re: [Technical Errata Reported] RFC948… Carsten Bormann
[Jsonpath] Re: [Technical Errata Reported] RFC948… Bjoern Hoehrmann