Re: [Jsonpath] June interim meeting

Carsten Bormann <cabo@tzi.org> Mon, 14 June 2021 05:32 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 45FEE3A1320 for <jsonpath@ietfa.amsl.com>; Sun, 13 Jun 2021 22:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_FAIL=0.001, SPF_HELO_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 tNQmhSPIG-8h for <jsonpath@ietfa.amsl.com>; Sun, 13 Jun 2021 22:32:18 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [IPv6:2001:638:708:32::19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E10943A131F for <jsonpath@ietf.org>; Sun, 13 Jun 2021 22:32:17 -0700 (PDT)
Received: from smtpclient.apple (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4G3Kp76XjHz2xF1; Mon, 14 Jun 2021 07:32:15 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B8F63A94-38CF-420C-BBF8-DE3C721C24DD"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBU6iuJr5Z-r0ZT_qwj=Si_oOGUuY_4g7qshuoBQwG0zBCshg@mail.gmail.com>
Date: Mon, 14 Jun 2021 07:32:15 +0200
Cc: jsonpath@ietf.org
Message-Id: <0CB072D0-915E-48C9-9777-A274EB871F60@tzi.org>
References: <CAHBU6iuJr5Z-r0ZT_qwj=Si_oOGUuY_4g7qshuoBQwG0zBCshg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/jBXgIAvdInOiK20mjuldwTlDqAg>
Subject: Re: [Jsonpath] June interim meeting
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: Mon, 14 Jun 2021 05:32:22 -0000

On 14. Jun 2021, at 06:07, Tim Bray <tbray@textuality.com> wrote:
> 
> I don't know who's coming but I just spent a certain amount of time looking at our PR list and, while I have opinions about the details, I think it's difficult to follow the rapid evolution of these discussions over the last week or so.  

I would prefer if we could merge the ready-to-merge PRs (#94, #101) and get the other ones rebased on those.
With enough time before tomorrow’s meeting that we can still prepare slides.

Can the document authors please get the merging done quickly, so the submitters can rebase their PRs?
This is not the time to be shy — I know there are authors on the document that are invisible, but this will have to be done by the ones who have been doing the work.

(I apologise for forking #99 off #98; I hope I have explained why the tooling made this necessary.
I don’t know how “alive” #75 is; the actual PR would need rebasing after the selector work has progressed.)

So there really only is

— #97, which after rebasing is a single remaining change.  That needs discussion, because it is indicative of a fundamental problem we haven’t addressed yet.
— #99 (with most of the discussion in the thread on #98), which desperately needs to be split up into smaller PRs building on top of each other.

> This is to ask Greg/Glyn/Carsten/Stefan for their help in walking us through which of these selector--definition and terminology issues are considered "open" and worthy of WG time at the meeting.

I can certainly make a slide or two on the remaining significant terminology issue.
(That doesn’t mean terminology is otherwise done, it’s just good enough that work can continue on technical content.)

> Should someone want to post a summary/overview note before the meeting that would also be useful.

Given the short time remaining, I’d prefer to do that in the form of slideware.

Grüße, Carsten