IETF Logo Mail Archive

Re: [Jsonpath] RFC 9535 on JSONPath: Query Expressions for JSON

Carsten Bormann <cabo@tzi.org> Sat, 09 March 2024 21:56 UTC

Return-Path: <cabo@tzi.org>
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 34A83C14F5FE for <jsonpath@ietfa.amsl.com>; Sat, 9 Mar 2024 13:56:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3HE4juwDiIo for <jsonpath@ietfa.amsl.com>; Sat, 9 Mar 2024 13:56:16 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 770D7C14F6EA for <jsonpath@ietf.org>; Sat, 9 Mar 2024 13:56:10 -0800 (PST)
Received: from eduroam-pool10-208.wlan.uni-bremen.de (eduroam-pool10-208.wlan.uni-bremen.de [134.102.90.207]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4TscLG025hzDCbW; Sat, 9 Mar 2024 22:56:05 +0100 (CET)
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: <CAHBU6ivpNV8EmXJcnvQ0NWHDyf_PaZ58HcEDkvkxf+1kQwxp6w@mail.gmail.com>
Date: Sat, 09 Mar 2024 22:56:05 +0100
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, jsonpath@ietf.org
X-Mao-Original-Outgoing-Id: 731714165.483126-1a9a2c420d71f8be1d0a39505ba68867
Content-Transfer-Encoding: quoted-printable
Message-Id: <C32DD370-2F2D-4029-81CD-7CAE323671D0@tzi.org>
References: <20240222050037.7739C1F73698@rfcpa.amsl.com> <CAL0qLwbD1PfUqn6k_=D56KPeC9BAno4NT9U6F_e=_vf699YFEw@mail.gmail.com> <CAHBU6ivpNV8EmXJcnvQ0NWHDyf_PaZ58HcEDkvkxf+1kQwxp6w@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/U5lj7_2I1xMlibgDcPMYTAym7gk>
Subject: Re: [Jsonpath] RFC 9535 on JSONPath: Query Expressions for JSON
X-BeenThere: jsonpath@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of JSONPath syntax <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: Sat, 09 Mar 2024 21:56:20 -0000

On 2024-03-09, at 21:33, Tim Bray <tbray@textuality.com> wrote:
> 
> I’m not against future revisions of JSONPath, but we need experience with the adoption (or not) of this version before anyone does anything further. Let’s close the WG.

+1
But I think that didn’t fully answer Murray's question:

>> This concludes the current charter.  Has the working group discussed rechartering to do other work, or will the working group now close?

I don’t think the WG as such discussed this a lot, but a few main players all seemed to agree on list with closing down the WG in  <https://mailarchive.ietf.org/arch/msg/jsonpath/KoBwV08Js64BVmogHhqMvg55QR0> and thread, in particular the plan laid out in <https://mailarchive.ietf.org/arch/msg/jsonpath/LqpUPVp7Ks-Ksapoz7yFeGd9z74>.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email