Re: [Jsonpath] June interim meeting

Stefan Gössner <stefan@goessner.net> Mon, 14 June 2021 08:38 UTC

Return-Path: <stefan@goessner.net>
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 D43293A1B9D for <jsonpath@ietfa.amsl.com>; Mon, 14 Jun 2021 01:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_REMOTE_IMAGE=0.01, 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 gzYfE6rm_U5h for <jsonpath@ietfa.amsl.com>; Mon, 14 Jun 2021 01:38:08 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) (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 DB8CC3A1B9C for <jsonpath@ietf.org>; Mon, 14 Jun 2021 01:38:07 -0700 (PDT)
Received: from [192.168.178.20] ([87.123.195.221]) by mrelayeu.kundenserver.de (mreue106 [212.227.15.183]) with ESMTPSA (Nemesis) id 1M3DeV-1ltXS214Kj-003hea; Mon, 14 Jun 2021 10:38:03 +0200
To: Tim Bray <tbray@textuality.com>, jsonpath@ietf.org
References: <CAHBU6iuJr5Z-r0ZT_qwj=Si_oOGUuY_4g7qshuoBQwG0zBCshg@mail.gmail.com>
From: Stefan Gössner <stefan@goessner.net>
Message-ID: <5f257963-74a1-26a6-413a-ce9e16292180@goessner.net>
Date: Mon, 14 Jun 2021 10:38:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CAHBU6iuJr5Z-r0ZT_qwj=Si_oOGUuY_4g7qshuoBQwG0zBCshg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------47B6286EEE02E738C8F6A79C"
X-Provags-ID: V03:K1:ksXqZOkOzR4gR/ZW3R/o6lcPNkzcn3uc3aYA+Nz2GNaddKgX1KW WOhUO/Q9Q9FHBerGkQlj7A+kMkgTbLQamSJ09+QfNFkZWU+ME/AILdU22wdDaPVv4OcPLob 7WI5mHQIjXqcBBL2K0KunwBTkuQvxI1jBcK/IMpj2Qncj2NM7DmqULTBmTJEPIKv17BkjAj tu3JGE7HVjOl1+xZ1/hyg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:6ldbkW2QVPI=:t72///YIYc7lcpU666LxP7 I9sPGCbKsMabyUvCxiMjJzySg3mFrG8yg451NC/3Gx+qlqh0JG8mc4I4ZBRn9lIZ3afRwXu77 YVsSzQyifkjGk/fIJiYO+uaAxK3KPFtKZKMEACbErKKvtOuGUuDoAZTujuNk7JvtoyzjM/Rnw PdlufBxj+i1Ur1euFBq4JjgYZMgM9HG3IXGCIxxRj/hND3pV4FYiW8lww0m4JML25guIb2TXr Do2e55GJ8H96/04KS/wvp6ZN6R2HCnvcZ2LUqhEaCNfalmwQv+u/j94+J4S+xdXQoxvN708el WoXnCYkSj5HAMYuEiUMfbn8VHTp5pTAYcC0M6n579E2usRUGLAsNmO/gmnadZEPxp5Ql6ySE5 Jg3Vj/d8x0V9hLKmIDAXJFMD+fvdNGOqQ7y7tz0iUSOqTEoAgAfNYCa6vwKzysvrXcqRX+VaU kWSJG5TF8tTR7MT+ebpH9dNyy+g8wnwPYwJ13AvTybHaRyRwJEHSJs9I4UoPN3iOJ8MeBXGiJ vE5BMAGLCEHohdjV6wR2Ms=
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/NgKhsP-VjBKgmQTMH2Bbro69rUg>
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 08:38:13 -0000

I collected some topics worth discussing from my point of view ...

/* ==========

## Topics - June interims meeting

### Terminology

* *primitive/atomic/simple* value types vs. 
*complex/structured/container* value types. Two common terms seem to be 
needed here.


### Selectors

* Fundamental point is the alternate wording in text ... :
     * ... selects a value.
     * ... selects a node.

Both is possible with Jsonpath, but we should stick with one throughout 
the text.

* Is a dot-member name allowed to start with a DIGIT?
* Are unions allowed to contain wild cards, descendant-selectors and 
filter-selectors ?
* Do we need to specify the order of evaluation of the 
`descendant-selector`?
* Discuss the proposed lean backward compatible syntax `[?<expr>]` in 
contrast to original `[?(<expr>)]`.
* Discuss proposal of `in-op` operator.
* Should comparison with structured values be allowed?
* What's the opinion about supporting functions? Related to this is: How 
to access a specific member in `{...,"key":5,...}` via filter expression 
`[?@...]` ?

==========*/

--
sg





Am 14.06.2021 um 06:07 schrieb Tim Bray:
> 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.
>
> 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.
>
> Should someone want to post a summary/overview note before the meeting 
> that would also be useful.
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virenfrei. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>