Re: [Jsonpath] Firing up the jsonpath working group

Carsten Bormann <cabo@tzi.org> Mon, 02 November 2020 17:53 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 010EB3A0EF8 for <jsonpath@ietfa.amsl.com>; Mon, 2 Nov 2020 09:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 UBobP04ckj3C for <jsonpath@ietfa.amsl.com>; Mon, 2 Nov 2020 09:53:39 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29AE63A12BB for <jsonpath@ietf.org>; Mon, 2 Nov 2020 09:53:18 -0800 (PST)
Received: from [192.168.217.118] (p548dcc60.dip0.t-ipconnect.de [84.141.204.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CQ0rX5VPkzyTm; Mon, 2 Nov 2020 18:53:16 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <AF9AC4A6-D83D-4861-B3B6-33B1DEE1777F@gmail.com>
Date: Mon, 02 Nov 2020 18:53:16 +0100
Cc: jsonpath@ietf.org
X-Mao-Original-Outgoing-Id: 626032396.303476-c5f7254950f50f844b3f2de0e4d8d38b
Content-Transfer-Encoding: quoted-printable
Message-Id: <2EFFF50D-F630-4E03-B7BE-B7E88B987BD9@tzi.org>
References: <CAHBU6itBgD+B1W15wUoxu=DTA4aKFmCNJWr5KiZ=t5oscXjR+w@mail.gmail.com> <AF9AC4A6-D83D-4861-B3B6-33B1DEE1777F@gmail.com>
To: Glyn Normington <glyn.normington@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/XLuNiEzuwmCfyVBaRWppduQ6h2k>
Subject: Re: [Jsonpath] Firing up the jsonpath working group
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, 02 Nov 2020 17:53:42 -0000

> We *could* talk about the writing/review process.

Yes.  It is probably easier to discuss this in a high-bandwidth meeting than to fire out dozens of emails.

> We *could* talk about how conservative we’ll be with respect to new features, but that discussion will probably need to be repeated on the mailing list anyway.

That (“conservative”) may be just one metric we could use to describe the process.
I think we should do this less from a 30000 foot, nebularly descriptive point of view, but by looking at specific examples.  If you already know examples that could be controversial, please make then available as GitHub issues (e.g., on your draft, or on the other one).

Grüße, Carsten


> 
> Glyn
> 
>> On 30 Oct 2020, at 23:05, Tim Bray <tbray@textuality.com> wrote:
>> 
>> Hello! I'm Tim Bray; your co-chairs are James Gruessing and me. This is from both of us.
>> 
>> We’ll be virtually meeting Nov. 16th at this time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=JSONPath+WG+IETF+109+Session&iso=20201116T16&p1=28&ah=2
>> 
>> This will be inconvenient for quite a lot of us, but just fine for our Asian colleagues who normally are the ones struggling out of bed in the middle of the night.  
>> 
>> Fairly-urgent action item: Agenda.  We need to have our draft agenda submitted next Wednesday and finalized on the ninth.  Please post any items to this mailing list.
>> 
>> Work is proceeding to get us a GitHub repo where draft specs and related material can be posted and diffed and PR'ed. 
>> 
>> I’d like to offer a reading list that I think people should glance over to get themselves equipped to participate in this work.
>> 	• Our charter: https://datatracker.ietf.org/doc/charter-ietf-jsonpath/
>> 	• Stefan Gössner's original "XPath for JSON" write-up that is the only existing spec of any kind: https://goessner.net/articles/JsonPath/
>> 	• An Internet-Draft from Stefan and Carsten Bormann which IETF-izes Stefan's original draft and is designed to launch this discussion: https://www.ietf.org/archive/id/draft-goessner-dispatch-jsonpath-00.html
>> 	• Another Internet-draft style document from Normington, Surov, and Mikulicic, with the goal of specifying JSONPath: https://jsonpath-standard.github.io/internet-draft/
>> 	• "JSONPath Comparison", a comparison by Christoph Burgmer of many different JSONPath implementations and how they handle various JSONPath idioms: https://cburgmer.github.io/json-path-comparison/ - fabulous work!
>> 	• In case that document looks way too big and intimidating, an example of one of its detail pages: Bracket notation with dot: https://cburgmer.github.io/json-path-comparison/results/bracket_notation_with_dot.html
>> 	• For those of you who are new-ish to the IETF, an excellent write-up of how things work: https://www.ietf.org/about/participate/tao
>> 	• Mark Pilgrim's classic "Why specs matter": https://web.archive.org/web/20051016203842/http://diveintomark.org/archives/2004/08/16/specs - it's short, to the point, and explains why good specifications need to be full of illustrative examples.
>> -- 
>> Jsonpath mailing list
>> Jsonpath@ietf.org
>> https://www.ietf.org/mailman/listinfo/jsonpath
> 
> -- 
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath