IETF Logo Mail Archive

Re: [Jsonpath] June interim meeting

Stefan Gössner <stefan@goessner.net> Mon, 14 June 2021 08:54 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 3865E3A1C09 for <jsonpath@ietfa.amsl.com>; Mon, 14 Jun 2021 01:54:16 -0700 (PDT)
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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 TnfzkYNQ3JzP for <jsonpath@ietfa.amsl.com>; Mon, 14 Jun 2021 01:54:11 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (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 339EC3A1C05 for <jsonpath@ietf.org>; Mon, 14 Jun 2021 01:54:10 -0700 (PDT)
Received: from [192.168.178.20] ([87.123.195.221]) by mrelayeu.kundenserver.de (mreue107 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MJEpp-1lcYHa3xQh-00Kdv3; Mon, 14 Jun 2021 10:53:54 +0200
To: Carsten Bormann <cabo@tzi.org>
Cc: Tim Bray <tbray@textuality.com>, jsonpath@ietf.org
References: <CAHBU6iuJr5Z-r0ZT_qwj=Si_oOGUuY_4g7qshuoBQwG0zBCshg@mail.gmail.com> <5f257963-74a1-26a6-413a-ce9e16292180@goessner.net> <970DDA69-9558-4FF6-8E59-F4F4E325B930@tzi.org>
From: Stefan Gössner <stefan@goessner.net>
Message-ID: <fe4c342f-c25f-7226-2c85-49cb45ff6910@goessner.net>
Date: Mon, 14 Jun 2021 10:53:51 +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: <970DDA69-9558-4FF6-8E59-F4F4E325B930@tzi.org>
Content-Type: multipart/alternative; boundary="------------FDEAD54F2E9FB67E93570CB9"
X-Provags-ID: V03:K1:mpUQl0Zyq5SYuKoXGVfIWWpf0O5S8IsrcA+Bxo9O8VoEZe9GZbq fo6sJifBf+SsIp1LzC7JiMWs/bdHs5RCcDaTOVbs0t9VwnLu0n2F05U/cfZZZJysA7r2YAT ilipg42LxSD9IbkEIFKT465MzMGXmubXMf609L6v76TadXb2zFtWVpaax0Kz8kAjQxLcOMZ 7IFPvzM4I79wRLC5XK9Rw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:A5qJMstW/4g=:juWOWsdXZbtBR0Y63o2kk4 IlIMW8o2UhYm83jr/2rOZnqgcSElXLWyPeYxRqoyghkHuGaLC2h2+XQV0KJf2b9GuMvWIDP54 fNyM9sphduXu3i4jIzR2s+mJIa59Eh47qULMOc0ZwaXMrTjwCZZQx3C/DaiquL/yggWqYj9J9 x8uZCz3QDtd6mxwvsWqqK3hk3kNcPVEGBGo0X5tIbWSiobpRM52c0HQUWqWgLI/xJZvTha7+y dSceq1kCdjQakRvR0DZ5YKuCloIsjWBkrO2y2cMHmlB0d14cADIRfwuABrm8/kvpaa+GJPZ5G 6tvFjAkxDSN+FXslW3rDmLS/bzc2IR8UkV9WNuWjrY+fXLeZLCnCXQfwIGnDJs+5GFmtYUral rU/3DDyjvMDfa9u/TbT6GnADs7A1iIvvJ9gE+rLfpsMSSOzfS2Kbm125/FgIbdNP/iCQ0vumi /nzja447H5TVuD2YVWgW7lhsDL3j6zLyfy97YhLjVLEmLv6BsMBk7sxfJUnsalZg7I6DszJYI nZdUWj1nDQ9ndDkraj8Y7s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/WtJ4VMODYBT93gxf9J6Jg0KKMwc>
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:54:16 -0000

I forgot

### Selectors

* What's the opinion about support of arithmetic operators in filter 
expressions?

--
sg


Am 14.06.2021 um 10:39 schrieb Carsten Bormann:
> I’m using these now for making my slides…
>
> Plan to have them ready to look at before 0930Z.
>
> Grüße, Carsten
>
>
>> On 2021-06-14, at 10:38, Stefan Gössner <stefan@goessner.net> wrote:
>>
>> 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.
>>>
>>> 	Virenfrei. www.avg.com
>>>
>>
>> -- 
>> Jsonpath mailing list
>> Jsonpath@ietf.org
>> https://www.ietf.org/mailman/listinfo/jsonpath
>

v2.23.0 | Report a Bug | By Email