IETF Logo Mail Archive

Re: [Jsonpath] WG adoption draft-bormann-jsonpath-iregexp-02

Michael Kay <mike@saxonica.com> Thu, 20 January 2022 00:04 UTC

Return-Path: <mike@saxonica.com>
X-Original-To: jsonpath@ietfa.amsl.com
Delivered-To: jsonpath@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED503A0B3A for <jsonpath@ietfa.amsl.com>; Wed, 19 Jan 2022 16:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYs2UsnzmJZ2 for <jsonpath@ietfa.amsl.com>; Wed, 19 Jan 2022 16:04:35 -0800 (PST)
Received: from p3plwbeout13-04.prod.phx3.secureserver.net (p3plsmtp13-04-2.prod.phx3.secureserver.net [173.201.192.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 569AC3A0B35 for <jsonpath@ietf.org>; Wed, 19 Jan 2022 16:04:34 -0800 (PST)
Received: from mailex.mailcore.me ([94.136.40.141]) by :WBEOUT: with ESMTP id AKwLnlc8jzUe3AKwLnOX7u; Wed, 19 Jan 2022 17:04:34 -0700
X-CMAE-Analysis: v=2.4 cv=E7sIGYRl c=1 sm=1 tr=0 ts=61e8a712 a=bheWAUFm1xGnSTQFbH9Kqg==:117 a=np+Hvx21kC4Q4qxhmORf6Q==:17 a=iO2Z4BJ_FnUA:10 a=kj9zAlcOel0A:10 a=DghFqjY3_ZEA:10 a=SSmOFEACAAAA:8 a=u4N4SSmShvQ547jWAbUA:9 a=CjuIK1q_8ugA:10
X-SECURESERVER-ACCT: mike@saxonica.com
X-SID: AKwLnlc8jzUe3
Received: from cpc160115-rdng30-2-0-cust150.15-3.cable.virginm.net ([86.19.35.151] helo=smtpclient.apple) by smtp06.mailcore.me with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mike@saxonica.com>) id 1nAKwK-00052E-LY; Thu, 20 Jan 2022 00:04:32 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Michael Kay <mike@saxonica.com>
In-Reply-To: <9343D2DD-C707-4E83-8DA1-F485B2F5ABFF@tzi.org>
Date: Thu, 20 Jan 2022 00:04:31 +0000
Cc: Tim Bray <tbray@textuality.com>, jsonpath@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C47123C-4D61-475D-900C-1C2F311D4796@saxonica.com>
References: <CAHBU6ivTZC+qn1gDct6JDT3gZFgEZFkZ3HQyR0nGh_1A28K09A@mail.gmail.com> <B878DADB-23DB-4590-9B62-AAB0F893EE19@saxonica.com> <9343D2DD-C707-4E83-8DA1-F485B2F5ABFF@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Mailcore-Auth: 439400257
X-Mailcore-Domain: 1881035
X-123-reg-Authenticated: mike@saxonica.com
X-Originating-IP: 86.19.35.151
X-CMAE-Envelope: MS4xfCr6dfprHHxzHb8v6x6BCMH3pT/Ade8qf/Lw3uAr9Gu16nwu6I/pdyLKijMu7rsHXNgOK4Lc7LpVKlgLYI/uuxEAxNPfb4L5rYErSfyGFZMPWR3iyf/t A2kvTh/OThFZNwb+Q+qXL7rx19MMotYPRedJyk4faD1pqrtGKwRdfAuwLOYNOJOLLzTDHQ8zT5RA3w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/zurT-P4AKHmWkIpPri9QE5lsYwQ>
Subject: Re: [Jsonpath] WG adoption draft-bormann-jsonpath-iregexp-02
X-BeenThere: jsonpath@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A summary description of the list to be included in the table on this page <jsonpath.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jsonpath/>
List-Post: <mailto:jsonpath@ietf.org>
List-Help: <mailto:jsonpath-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2022 00:04:39 -0000

> 
> This PR recognizes the fact that XSD 1.0 is more widely implemented than XSD 1.1.

If we're talking about implementations, then they will have had to fix the bugs in the XSD 1.0 spec, and hopefully in most cases they will have fixed them in the same way as XSD 1.1 fixed them. (However, some XSD 1.0 implementors, notably Microsoft, largely ignored the XSD-defined regex rules and just used an existing regex library.)

But I thought we were talking about specs, not about implementations.

For some of the discussion of bugs, see

https://www.w3.org/Bugs/Public/show_bug.cgi?id=1889

https://www.w3.org/Bugs/Public/show_bug.cgi?id=2019

https://www.w3.org/Bugs/Public/show_bug.cgi?id=2058

https://www.w3.org/Bugs/Public/show_bug.cgi?id=2123

Unfortunately these reference documents which are not publicly accessible.

To the best of my knowledge there are no changes in regex syntax/semantics between XSD 1.0 and 1.1 other than bug fixes.

Michael Kay

v2.23.0 | Report a Bug | By Email