Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20240613185743.E2FD1204E21@rfcpa.rfc-editor.org>
Date: Thu, 13 Jun 2024 22:00:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DBD3FA0-BD5F-4D56-A660-DAB5F5F889CC@tzi.org>
References: <20240613185743.E2FD1204E21@rfcpa.rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Message-ID-Hash: N5TL3DA3UQM5SB5DPLVEXE3QQEWXUUN6
CC: Tim Bray <tbray@textuality.com>,
 "Murray S. Kucherawy" <superuser@gmail.com>, orie@transmute.industries,
 james.ietf@gmail.com, bjoern@dataspace.earth, jsonpath@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BJsonpath=5D_Re=3A_=5BTechnical_Errata_Reported=5D_RFC9485_=2879?=
	=?utf-8?q?90=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/jsonpath/cFbR4G6UK-mfkeeATebDExSlAig>

Hi Bj=C3=B6rn,

thank you for your attention and this report.

However, I need to argue for rejecting this specific report.

On 2024-06-13, at 20:57, RFC Errata System <rfc-editor@rfc-editor.org> =
wrote:
>=20
> `\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.

Mozilla [1] actually claims that, for JavaScript, \S is equivalent to =
[^\f\n\r\t\v\u0020\u00a0\u1680\u2000-\u200a\u2028\u2029\u202f\u205f\u3000\=
ufeff]

The entries in the table are examples, and they clearly need to be =
modulated by the specific type of regex flavor, library version, Unicode =
version, platform specification version etc.
The intent is to demonstrate how these replacements can be built, not to =
supply readymade replacements with the highest fidelity to a specific =
combination of implementation and Unicode versions.

The entries for the first two examples in the table given are based on =
W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes, Appendix =
G.4.2.5 "Multi-character escapes".=20
(The value for the third example is *not* taken from that source, which =
would have suggested \p{Nd}, but mirrors what most regexp writers tend =
to believe \d means.)

Gr=C3=BC=C3=9Fe, Carsten


[1]: =
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expr=
essions/Character_classes