IETF Logo Mail Archive

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

Michael Kay <mike@saxonica.com> Tue, 18 January 2022 18:31 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 EF6C63A1041 for <jsonpath@ietfa.amsl.com>; Tue, 18 Jan 2022 10:31:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 YIbolTfnkskf for <jsonpath@ietfa.amsl.com>; Tue, 18 Jan 2022 10:30:57 -0800 (PST)
Received: from p3plwbeout05-04.prod.phx3.secureserver.net (p3plsmtp05-04-2.prod.phx3.secureserver.net [97.74.135.49]) (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 61E9D3A1047 for <jsonpath@ietf.org>; Tue, 18 Jan 2022 10:30:56 -0800 (PST)
Received: from mailex.mailcore.me ([94.136.40.143]) by :WBEOUT: with ESMTP id 9tFtnCBIQRkdg9tFunj7DD; Tue, 18 Jan 2022 11:30:54 -0700
X-CMAE-Analysis: v=2.4 cv=C7csdSD+ c=1 sm=1 tr=0 ts=61e7075f a=EhJYbXVJKsomWlz4CTV+qA==:117 a=G++axsv19AQkVQuwCdl4cA==:17 a=0d-FJ89MWBcA:10 a=DghFqjY3_ZEA:10 a=ZEAgVxdcAAAA:8 a=48vgC7mUAAAA:8 a=NEAV23lmAAAA:8 a=5D0ujAclF3ITgqyYMSoA:9 a=CjuIK1q_8ugA:10 a=fa6iYZI0K8gA:10 a=0ccr5IRoRmQA:10 a=LEni5nUE42jjaq2XkyEA:9 a=vRZBt7kUhwx-SR12:21 a=_W_S_7VecoQA:10 a=K4stkocu346RsC3JbKGV:22 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: mike@saxonica.com
X-SID: 9tFtnCBIQRkdg
Received: from [82.152.109.221] (helo=smtpclient.apple) by smtp13.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 1n9tFr-0004pA-PI; Tue, 18 Jan 2022 18:30:53 +0000
From: Michael Kay <mike@saxonica.com>
Message-Id: <B878DADB-23DB-4590-9B62-AAB0F893EE19@saxonica.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FEFF1248-4123-4E6D-AC93-A14CE90C572A"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Tue, 18 Jan 2022 18:30:51 +0000
In-Reply-To: <CAHBU6ivTZC+qn1gDct6JDT3gZFgEZFkZ3HQyR0nGh_1A28K09A@mail.gmail.com>
Cc: jsonpath@ietf.org
To: Tim Bray <tbray@textuality.com>
References: <CAHBU6ivTZC+qn1gDct6JDT3gZFgEZFkZ3HQyR0nGh_1A28K09A@mail.gmail.com>
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: 82.152.109.221
X-CMAE-Envelope: MS4xfGJIb1ut5u2+B5MGKw1ySNjB4oo9PRwM87pzQIDDoV81QYLD3Epd0WwPTsJAVuvRZ/K3R7Qk5i6H/IHglBnaieuFDNX6zGg8UucLuvuNNglEcsbeI03k 2ARx0enMgRKk/3FQLB2bMfhh+1w0fLI71FhVxgjwhHvO78XSWZBl1U6E5xh5ijHQn/riCSA9aFwrzQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/1V0apIurRjqJAhUJYfHPAJvYHzo>
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: Tue, 18 Jan 2022 18:31:01 -0000

I would suggest referencing XSD 1.1 rather than XSD 1.0.

The only difference in the regex capabilities is that XSD 1.1 fixes some bugs in the specification. It would be a shame to have a normative reference to a spec with known bugs.

Michael Kay
Saxonica

> On 18 Jan 2022, at 18:16, Tim Bray <tbray@textuality.com> wrote:
> 
> Co-chair hat on: At our interim meeting earlier today, we got a strong sense that the jsonpath WG has consensus in favor of allowing regular expressions in jsonpath filters, but that for this to be useful, the flavor of regexps needs to be specified precisely, and that flavor should be limited enough in scope to allow interoperation across as many as possible different regex libraries. 
> 
> Carsten Bormann has done the work of proposing such a small-scope regexp specification. The draft may be read at https://www.ietf.org/archive/id/draft-bormann-jsonpath-iregexp-02.html <https://www.ietf.org/archive/id/draft-bormann-jsonpath-iregexp-02.html>
> and is on GitHub at https://github.com/cabo/iregexp <https://github.com/cabo/iregexp>
> 
> If you have any issues to raise or objections to this, please let the WG know.
> -- 
> JSONpath mailing list
> JSONpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath

v2.23.0 | Report a Bug | By Email