From nobody Mon Nov 1 13:53:07 2021 Return-Path: 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 0A8023A2F78 for ; Mon, 1 Nov 2021 13:53:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Wpc5qRgJLW3t for ; Mon, 1 Nov 2021 13:53:01 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F7503A2F77 for ; Mon, 1 Nov 2021 13:53:01 -0700 (PDT) Received: from [192.168.217.118] (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Hjlbs6fb4z2xN2; Mon, 1 Nov 2021 21:52:57 +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 In-Reply-To: Date: Mon, 1 Nov 2021 21:52:57 +0100 Cc: James , jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 657492777.410148-aa5dd845aaa246ef09e755501d02e8b3 Content-Transfer-Encoding: quoted-printable Message-Id: <33DD7851-B50C-4738-97A0-5621C7577677@tzi.org> References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> To: Tim Bray X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2021 20:53:06 -0000 On 2021-10-28, at 19:45, Tim Bray wrote: >=20 > 1. Introduction >=20 > [ED] - Lose 1st para, polish >=20 > 1.1. Terminology >=20 > [OK] - May need to revisit if we change any of our terms >=20 > 1.2. Inspired by XPath >=20 > [BAD] Just lose it. Put one sentence crediting XPath in the intro >=20 > 1.3. Overview of JSONPath Expressions >=20 > [ED] - lose XPath stuff, not sure about language about conversion to = bracket notation, that's internal to a processor, right? I cleaned up the introduction and moved the XPath material into an = appendix, as had previously been discussed. A short history section in = the introduction points to the appendix. Pull request at: https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/pull/129 Diff: https://u.nu/phrOT Long form of this URL:=20 = https://www.ietf.org/rfcdiff?url1=3Dhttps://ietf-wg-jsonpath.github.io/dra= ft-ietf-jsonpath-base/draft-ietf-jsonpath-base.txt&url2=3Dhttps://ietf-wg-= jsonpath.github.io/draft-ietf-jsonpath-base/xpath-inspired/draft-ietf-json= path-base.txt HTML version of document with PR: = https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/xpath-inspired= /draft-ietf-jsonpath-base.html#name-overview-of-jsonpath-expres These changes are all editorial and should move us forward to having a = document we can publish as soon as the technical issues are done as = well. Sorry for not quite keeping up the Schlagzahl (*) of 1 PR per day... Gr=C3=BC=C3=9Fe, Carsten (*) Sorry, untranslatable. =20 The rate of rowing strokes per unit of time in a boat. Of course, Germans would think about intellectual work this way. Thomas Mann wrote a page a day, even on the day where he fled Nazi = Germany. From nobody Tue Nov 2 01:54:12 2021 Return-Path: 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 4A2DE3A0FC4 for ; Tue, 2 Nov 2021 01:54:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.227 X-Spam-Level: X-Spam-Status: No, score=-5.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-3.33, 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 51sGIrAkwPFQ for ; Tue, 2 Nov 2021 01:54:06 -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 4AFD53A0FBF for ; Tue, 2 Nov 2021 01:54:05 -0700 (PDT) Received: from [192.168.178.20] ([88.130.50.229]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MsYzF-1mT2p602Rv-00txlM; Tue, 02 Nov 2021 09:54:03 +0100 Content-Type: multipart/alternative; boundary="------------rYErKWvGrJOfMzh00rHBDVC8" Message-ID: Date: Tue, 2 Nov 2021 09:54:00 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= To: Tim Bray , James Cc: jsonpath@ietf.org References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> In-Reply-To: <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> X-Provags-ID: V03:K1:t7M2uqbnGVhNOpcYpWHbzuDz0VZg41/ATK9r2EFhxCwtBYrh3Q+ FUsXrCN9hopPxMcYkBAc09bUYkcMziFSOXlLb5KNUvMpFAKklFTo2ZPVNuuv4XWd/Ped//q SuVdcuoT0Yrv+InTbRAdUohVpXsXz+pKlMxeSp3Sfh9FYzT3bjXhqPKbjY+KoaFAc8LPmaF eFRutezWTqFrjvh4nGWXA== X-UI-Out-Filterresults: notjunk:1;V03:K0:H1OqD7U983A=:5PKzEXXCxyBRqluSv4mNZg M3s3ltxTWuC/dQI4/iy2aGyVC3yBkbvGPasufm2tgwBWJLQH5/qZAGAv2qj2+hjTIcWhyxQW1 zIdk4bBqRf38+4XqCphP3sxgT2Dv3aqu4xsqwg7HdyYWAGTE6MuEurTuMkV8rJDK3VOkEWAJI /X8d3duWrtN/XaLJUB9BCUo7nKy/qPygOVOr97QGiHReUpSo+8p73X3quHqQbh7seW8uCsuB6 1PLkVg1dlUGfEaOfRu4hr3aD6rF+wP3hnBEf9D3/nsG7VL3U0Ey44mftJDow0bVR1j9eAKv3x 4TT5Gv2HSgXZLAulr/pbKqHb9GE+UGwCAAI6QFGK06y0ywih6TpEn9U1K/fQL5ok7q81F2bXZ zN3+AgUBpDioxrrdkWXX+s8jDbIa2bSwy8pkaOl6fvE5sOsO+nKryN/B1RFLJqdl2gOKzLaLc Rwx/7EqVO0FRmTeTyMXWyUoznrX1H5FYZIfOCGypBGercrSNs7QcHozs2GgMK+aOKfdN8kaxu AL1tGypos+D40FYNaEfrk8C/BFgqAn+1Eij35pNnoieRNLtNzHmC4jMqqFu81D8LiyrcQs9WH qtqVv1vwCQ+0Cm5u9fyWjY7pk+0TlLK8yzusBLasuCpeNThcDo5Xy7U1uXwxRUeKb/dlhEiyB X+mDZy39gCjMqK8fkbgfS2poRuWek/9J9fjVBD5wJP8cdgUQ2JCLp13cQ4VJDcg+umDc= Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2021 08:54:11 -0000 This is a multi-part message in MIME format. --------------rYErKWvGrJOfMzh00rHBDVC8 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I can see two big construction sites (or merely decisions to add them later or leave them out):     * functions in the expression language, `key(@)`, `length(@.arr)` or additions to `@` as in `@key`.     * equality tests for structured types (deep equals) and one not so big:     * clean up blank space in ABNF `S` (I can do that) (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126) We also need to discuss and aim for agreement regarding: * JsonInclude (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124) -- sg Am 30.10.2021 um 18:31 schrieb Stefan Gössner: > ... just to let you know ... I will be back on the list on Monday ... > -- > Stefan > > > Am 28.10.2021 um 19:45 schrieb Tim Bray: >> You'll note that on the draft agenda, there's an item labeled "Draf >> Status - Tim". >> >> I went and took an end-to-end pass through the current draft, asking >> myself the question "How much work is left to finish this and send it >> off to the IESG?"  There's quite a bit, but less than I thought.  To >> help us talk about this, I offer this annotated table-of-contents, >> outlining what I think the draft status is section-by-section. >> >> Feel free to disagree or amplify, either right here, by raising >> issues over on GitHub, or during our Nov 10 meeting. >> ======================================= >> Options for each section: >> >> OK - Ready, more or less >> ED - Technically OK, needs editorial work >> TECH - Open technical issue(s) >> BAD - Needs rewrite >> >> Contributing >> >> [BAD] - IETF style >> >> 1.  Introduction >> >> [ED] - Lose 1st para, polish >> >> 1.1.  Terminology >> >> [OK] - May need to revisit if we change any of our terms >> >> 1.2.  Inspired by XPath >> >> [BAD] Just lose it.  Put one sentence crediting XPath in the intro >> >> 1.3.  Overview of JSONPath Expressions >> >> [ED] - lose XPath stuff, not sure about language about conversion to >> bracket notation, that's internal to a processor, right? >> >> 2.  JSONPath Examples >> >> [OK] - May need to revisit if we change stuff >> >> 3.  JSONPath Syntax and Semantics >> 3.1.  Overview >> >> [ED] - "no further errors…" language needs a little more expansion >> >> 3.2.  Processing Model >> >> [OK] >> >> 3.3.  Syntax >> >> [OK] >> >> 3.4.  Semantics >> >> [OK] >> >> 3.5.  Selectors >> >> [ED] - why is the ABNF up in 3.3 while the descriptions are here. >> >> 3.5.1.  Root Selector >> >> [ED] the "Semantics" section is confusing, I think we already said >> what it does >> >> 3.5.2.  Dot Selector >> >> [ED] >> >> Should we have an example in each of these 3.5.* >> Maybe a note about the dangers here, e.g. if you have something like >> { "a.b": 23 } you can't use dot notation >> >> 3.5.3.  Dot Wild Card Selector >> >> [OK] >> >> 3.5.4.  Index Selector >> >> [OK] >> >> 3.5.5.  Index Wild Card Selector >> >> [OK] >> >> 3.5.6.  Array Slice Selector >> >> [ED] - Seems unnecessarily long, and the language about its history >> adds no value? >> >> 3.5.7.  Descendant Selector >> >> [ED] XML history adds no value? >> >> 3.5.8.  Union Selector >> 3.5.8.1.  Syntax >> >> [ED] - sloppy informal language >> >> 3.5.8.2.  Semantics >> >> [ED] in this place "Semantics" gets its own Table of Contents entry, >> but not in the other selectors >> >> 3.5.9.  Filter Selector >> >> 3.5.9.1.  Syntax >> >> [TECH] This one seems to have all our open issues in it!! >> >> 3.5.9.2.  Semantics >> >> [OK] - modulo some changes if we revise 3.5.9.1 >> >> 4.  Expression Language >> >> [TECH] more open issues here. >> >> 5.  IANA Considerations >> >> [TECH] I suggest application/jsonpath >> >> 6.  Security Considerations >> >> [TECH] Having nothing here is unacceptable. Work item. >> >> 7.  References >> 7.1.  Normative References >> 7.2.  Informative References >> >> [OK] I guess? >> >> >> On Thu, Oct 28, 2021 at 9:51 AM James wrote: >> >> Folks, >> IETF 112 is a few weeks away with our next meeting being held on >> Wednesday, 10th of November from 12:00 to 14:00 UTC. If you >> haven’t already registered, you can do so here: >> >> https://registration.ietf.org/112/ >> >> We have only a few items on our agenda for this session: >> >> https://datatracker.ietf.org/doc/agenda-112-jsonpath/ >> >> If there’s any other subjects or issues you’d like to be part of >> it please email myself or Tim and we can include it. >> >> - J >> -- >> Jsonpath mailing list >> Jsonpath@ietf.org >> https://www.ietf.org/mailman/listinfo/jsonpath >> >> >> >> Virenfrei. www.avg.com >> >> >> >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> > > --------------rYErKWvGrJOfMzh00rHBDVC8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit I can see two big construction sites (or merely decisions to add them later or leave them out):
    * functions in the expression language, `key(@)`, `length(@.arr)` or additions to `@` as in `@key`.
    * equality tests for structured types (deep equals)

and one not so big:

    * clean up blank space in ABNF `S` (I can do that) (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126)

We also need to discuss and aim for agreement regarding:

* JsonInclude (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124)

--
sg


Am 30.10.2021 um 18:31 schrieb Stefan Gössner:
... just to let you know ... I will be back on the list on Monday ...
--
Stefan


Am 28.10.2021 um 19:45 schrieb Tim Bray:
You'll note that on the draft agenda, there's an item labeled "Draf Status - Tim".  

I went and took an end-to-end pass through the current draft, asking myself the question "How much work is left to finish this and send it off to the IESG?"  There's quite a bit, but less than I thought.  To help us talk about this, I offer this annotated table-of-contents, outlining what I think the draft status is section-by-section.

Feel free to disagree or amplify, either right here, by raising issues over on GitHub, or during our Nov 10 meeting.
=======================================
Options for each section:

OK - Ready, more or less
ED - Technically OK, needs editorial work
TECH - Open technical issue(s)
BAD - Needs rewrite

Contributing

[BAD] - IETF style

1.  Introduction

[ED] - Lose 1st para, polish

1.1.  Terminology

[OK] - May need to revisit if we change any of our terms

1.2.  Inspired by XPath

[BAD] Just lose it.  Put one sentence crediting XPath in the intro

1.3.  Overview of JSONPath Expressions

[ED] - lose XPath stuff, not sure about language about conversion to bracket notation, that's internal to a processor, right?

2.  JSONPath Examples

[OK] - May need to revisit if we change stuff

3.  JSONPath Syntax and Semantics
3.1.  Overview

[ED] - "no further errors…" language needs a little more expansion

3.2.  Processing Model

[OK]

3.3.  Syntax

[OK]

3.4.  Semantics

[OK]

3.5.  Selectors

[ED] - why is the ABNF up in 3.3 while the descriptions are here.

3.5.1.  Root Selector

[ED] the "Semantics" section is confusing, I think we already said what it does

3.5.2.  Dot Selector

[ED]

Should we have an example in each of these 3.5.*
Maybe a note about the dangers here, e.g. if you have something like { "a.b": 23 } you can't use dot notation

3.5.3.  Dot Wild Card Selector

[OK]

3.5.4.  Index Selector

[OK]

3.5.5.  Index Wild Card Selector

[OK]

3.5.6.  Array Slice Selector

[ED] - Seems unnecessarily long, and the language about its history adds no value?

3.5.7.  Descendant Selector

[ED] XML history adds no value?

3.5.8.  Union Selector
3.5.8.1.  Syntax

[ED] - sloppy informal language

3.5.8.2.  Semantics

[ED] in this place "Semantics" gets its own Table of Contents entry, but not in the other selectors

3.5.9.  Filter Selector

3.5.9.1.  Syntax

[TECH] This one seems to have all our open issues in it!!

3.5.9.2.  Semantics

[OK] - modulo some changes if we revise 3.5.9.1

4.  Expression Language

[TECH] more open issues here.

5.  IANA Considerations

[TECH] I suggest application/jsonpath

6.  Security Considerations

[TECH] Having nothing here is unacceptable. Work item.

7.  References
7.1.  Normative References
7.2.  Informative References

[OK] I guess?


On Thu, Oct 28, 2021 at 9:51 AM James <james.ietf@gmail.com> wrote:
Folks,
IETF 112 is a few weeks away with our next meeting being held on Wednesday, 10th of November from 12:00 to 14:00 UTC. If you haven’t already registered, you can do so here:


We have only a few items on our agenda for this session:


If there’s any other subjects or issues you’d like to be part of it please email myself or Tim and we can include it.

- J
--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath

Virenfrei. www.avg.com




--------------rYErKWvGrJOfMzh00rHBDVC8-- From nobody Tue Nov 9 19:15:44 2021 Return-Path: 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 9FE5B3A1073 for ; Tue, 9 Nov 2021 19:15:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com 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 QKZFAAwN8vC2 for ; Tue, 9 Nov 2021 19:15:41 -0800 (PST) Received: from sonic313-15.consmr.mail.bf2.yahoo.com (sonic313-15.consmr.mail.bf2.yahoo.com [74.6.133.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E290B3A106A for ; Tue, 9 Nov 2021 19:15:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1636514139; bh=XE70+5eHNafn/RZgW2uJCLBgbtxdC7ypv451qF0dm/s=; h=Date:From:Reply-To:To:Subject:References:From:Subject:Reply-To; b=AdELfORrmxTmERZZShbv2z+sqUvEneaVyUlJTrn6OP/ZZ+oHV4JJ3NMubRdgQnVQFxdgv353YffoR0fP/h9WbZOWPKB5bNXeU4Amprk6zupIDii55Xjsef3cbobFwX7Cbm5UcgngqohXZBoqTSWrH1ILxYEXcLdVOtO+JX6fvJ3E2jzv9VS1Uv1ihXW7QEo3EP99UIgcgYIZhbUqKVihnTrO1/yupB6YYlEhrVC+CaD5Ch9HlE/JfCJF7c6FnsJCO8SBwe8Xru1DDZ4q31rfszQp6im48FtK/aBqrFxj0bRkr9cBt0bE3bA6Hul+6kOnEGV8g+CINXN5gGfnp9RL+Q== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1636514139; bh=nvEQUATfbbOE5BSQ7VmAhRmok8ASMdkgFJ2IAySk1En=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=LwHehs/x6OezcVhloiKe3DfEWt3rzbobOJ8G8y5W+muvK58fUcSzqklma3hNbRNn7ZSKqybpVgBclnwwb3t7cblHUMyHG2LNJMsSR+a8WjTpYI/H8OFL8J21+3feMT5PL1SYVyTjV510LzQXUOQzwevrSIW5kZHrE+OvNPrEMGrhSnxLBID3i0R6HBmkfeqKiH4iDZw68b8cxutIAZD9PWaZvtaCcgTh+x1QjklNlU1FfEIMtBWMG0aHbq5DdcCOAyEN95qOCCkG4J5KyYGP7k25Ujsmuj9U3GfBBFhfEv0oa0p6nlSpuJ+oaXyopavCVPA0A3Iban+e6CQbgnVeHw== X-YMail-OSG: IvnqeYkVM1mHTfA6KNi_UrjM29KD56saiTW79MmYpHa.UAjTTOrsFuCyv2hBBeM 9zAwkXqaJKTmFdyJQq3ZZ_TznS3uJTUj9nucxwF4EmempmLMSjdfsTPTIjIziCXOGj5x3VtDjUQO 2MDa.oInHCSZH.2ZRyP34RSceMyvWxcR0p9apG3Q3ed5D9Mj_bUo5L9XtbuxkZrxWNFbDrNSJR0. hTfIsTQ.353wBZAgvhsZY9demtlnwQN56S._EAvWg73G0reHEfJa1GAqAT_Sfw0aoIxlfarQZ6Cf KXIxe9x2YBUrZg9f3ErL_2bx2JKlmoXj6hYnvISl3CCWmbYHLaY9ZWy7n5rnqfOpltMZKBb5kzkG 2JI5VJhS1_sZ3z4eqLwRCrC8nZkYtYatdvIaulekWqQpwGsEgT8xnDKHu1OdsqM9nQLM0eGqsme2 7NZy84KPb6kZfSEeXTNmYbXLJxo8kHyBu_FVbTm1LKADSZKhwy9Ga1DpNrNxpV3m7GjCotXcXFe6 9Xkwzh6_dQv6mURgGzuND.41KF78iInnsKoQx3kEGM_ORRb8iinEJTxyaIjODWZ3qf2fq.yMM5z8 2rL2kuOZ3DP68er26NTYA8.McRmR2bU83__GlRTQtDYrgwYkq7YBY0.Q.1gmk.HnZK.v.hqGTX_o KlFijecFCukmY4UO1GMGBot5TxDP7n4SUXX64Uc6LR2ZkCM1ekGtFwB7r800QHzpxM1NWNDK3nGi m7Mdfv0P4RwZaNb5Z6eyyZLqIQcGV2DYe5ITpaVPiIpoU2TSD3yWrXAmuOiG3ri5HLFfLBDQWvb_ 34gzfY.LQgw.tZ1Sa.dhdzXrW5My76ItHlyUrk6rCUmEW13rR8eDaax182hNj2umqHAgfVfTagUL O3G0DkSjCfDP6gGIEMbl6OcUi7JLuL2EV2I7k_0CW0XO.hMBzuKxW8RwZJpa0mkfmO4LhL08xMbX JHL8Mh.cJsw99eW3RcJJ9rN1bzFmgv_9tgepRZ_uYixPd2TqAcSogwQUCaAOWQkmTkXXUsROkME1 XYjwlR_ElO_puPcxSHnFHoLvFfUsllNYfa.OidivQ12tDFosd.TyDfNu8FyPpdWa2HD1zPt._kMC HIT1.qhUMwvhBXFbrRij4xvadBArjVwLf6P45i138BThM1hq6V99xy07Wb5a4NzqUXSLVZ.hLapt v92mZuQn10zb9KfkFAGcxfwUMnbu5MwPf6ct_sHTNckeCG2.vXFliyiYfRsT_qsOCjH9lmhnbaNV NYjmpR5PQPaOOxy24gqetmXRWphFvaIvIhRMFdtqBOnFPi.bfgNSOWbMz6kvstuiWI5fucfggXjF kGmPQvXhMWPdmxEiFIXbhaJrGiJzHqZl2OlZKHyb_8skfpeGofWIsX9ffwXqgu5ZgEocSvGAdbg7 BSPHYT3cZ8Ucu.KmVCUUxATI0E4Q4dLBslA2skuoUotfB.HzRSqMI_9GwI8N7V051SSxJi6o5E1Z NLG2nX0mBHepexqeH0GMGpzhnu6bJDE3mUYGFct5d0bY_pt3NN_tgQaUQmfVwGHewAz4PFl.rxff 4bEy4AtLWkH1g6pC79xqDA8osWbSSbEMsPHpiDg.Cy7ccnoejwHrSVYqcwVacqNxUWK70n8vwAdV FDSK24bU3onOtYK8cZxMOKE6Z0IZI..O1H_WmGV6mL6nWkEhDGb29z.ITA071TNZP8NBgGqp7MYE zB1GKLG57oDA7IqltPM8OICwe4rhhiyQ8oOlTgj2GjLBYHk6WgYqXm1bM0lOrTd19ijSszH0G2Vi yC2R37MpJ3MMVqWpPkdo56qGGj9yIlIRhq.VHWldiCyiK0o7TgPnVl9hNmDlOohn5hMTIdfBBiN2 YA8rJ5y_IzflPYXD0uuxMCfXmRzAAazUOEJeUofEtZDcgbFjP0d7Se1UqTCBDO.XFDSqucpZZrOF j0DLKNBHkjU3rW_1HywBSYkBDvg9yAr0qCOXhmqd_sc7NvxQHiighhUQunkIm4tIJz183gm_HpUY Mjvn4rpLP7mpgS2NnDN8QWdZuFQuui0vxKjHRY4EJ.AVqFqmA9E2bAysRQlTgOVikNtaHlXtwGXM 7d5gUqnleKSwF8yebHL5nucSw8FIT3B2P02O8H0Q9HvuMwE4ovoiuJ3ER1VTSRhaosw7kLpU8hRJ K6ojXAP0d5rc8vTBcvCMjsxdNA8BfN0Su0CJlNL53mJvri3ZI4a14f1fin8vx8y5rJd1Hk544bod Gfb1Cs2UUp1PAvkFg9dgBuo6S_L4wFn2ob0pSObUIrIgplrPVgD6uFalA6Uwt85Bf2KMuBt3Q_H1 lNwnC16h0Sj2Ho3nzU9ydTneGXOaGHOIG9d3VqTI.gsJuliB4OFZZ4YI- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.bf2.yahoo.com with HTTP; Wed, 10 Nov 2021 03:15:39 +0000 Date: Wed, 10 Nov 2021 03:15:33 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: Message-ID: <661668953.1426338.1636514133505@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1426337_533099293.1636514133504" References: <661668953.1426338.1636514133505.ref@mail.yahoo.com> X-Mailer: WebService/1.1.19266 YahooMailAndroidMobile Archived-At: Subject: [Jsonpath] Closed GH issues 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 03:15:43 -0000 ------=_Part_1426337_533099293.1636514133504 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Carsten, I see that you've closed a bunch of issues and referenced the asso= ciated PRs.=C2=A0 Thanks for doing this maintenance. However, it's a bit difficult to know what the final resolution was on some= of them.=C2=A0 Would it be possible for you to edit some of those closure = comments to summarize the outcome? ThanksGreg ------=_Part_1426337_533099293.1636514133504 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Carsten, I see that you've closed a bunch of issues and referenced the associated PRs.  Thanks for doing this maintenance.

However, it's a bit difficult to know what the final resolution was on some of them.  Would it be possible for you to edit some of those closure comments to summarize the outcome?

Thanks
Greg
------=_Part_1426337_533099293.1636514133504-- From nobody Tue Nov 9 20:13:00 2021 Return-Path: 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 9BE5F3A1157 for ; Tue, 9 Nov 2021 20:12:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.919 X-Spam-Level: X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 3ArjxPHSDrjA for ; Tue, 9 Nov 2021 20:12:54 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 451193A1153 for ; Tue, 9 Nov 2021 20:12:54 -0800 (PST) Received: from smtpclient.apple (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Hprzl5MgKz2xdM; Wed, 10 Nov 2021 05:12:51 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: Carsten Bormann In-Reply-To: <661668953.1426338.1636514133505@mail.yahoo.com> Date: Wed, 10 Nov 2021 05:12:50 +0100 Cc: jsonpath@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <6C8B938E-3C05-40BD-8B8D-A5D2A8E8C1E9@tzi.org> References: <661668953.1426338.1636514133505.ref@mail.yahoo.com> <661668953.1426338.1636514133505@mail.yahoo.com> To: Greg Dennis X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [Jsonpath] Closed GH issues 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 04:12:59 -0000 On 10. Nov 2021, at 04:15, Greg Dennis = wrote: >=20 > Carsten, I see that you've closed a bunch of issues and referenced the = associated PRs. Thanks for doing this maintenance. >=20 > However, it's a bit difficult to know what the final resolution was on = some of them. =20 Which ones? > Would it be possible for you to edit some of those closure comments to = summarize the outcome? Sure. Which ones need this? (Some of the issues are meandering brain dumps, and it is not clear that = there was an outcome. I=E2=80=99ve marked a few of those with =E2=80=9COBE =E2=80=94 can we = close this=E2=80=9D; we=E2=80=99ll need to find out if any of the = participants see anything open remaining in these issues; I cannot find = that out.) Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Nov 9 20:25:36 2021 Return-Path: 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 2B3ED3A116F for ; Tue, 9 Nov 2021 20:25:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com 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 DWyOkOiJAoNO for ; Tue, 9 Nov 2021 20:25:29 -0800 (PST) Received: from sonic303-1.consmr.mail.bf2.yahoo.com (sonic303-1.consmr.mail.bf2.yahoo.com [74.6.131.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14F383A1167 for ; Tue, 9 Nov 2021 20:25:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1636518322; bh=Ayys9PKenX+ZZfGSdPO3hOk+1WoeDyBDiHfsYMFUG6U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=NO5U8/h5W6lhfZk6c4Negwi7aG95QRw/bd7VOSFuUTfSY6Z/01NK0JY5yjD/hbWS2Mb/gml/Z+6zzq92QTJX7b21RVwYAAxBTlDja5k1geKZsiJXi76MjN7UMDZG31wsHoVP2nABWKu2ATkNLXM3IPW27/SoDrzPDjE90N/gW2hrhT2ivw91EIaVyT857Aa7c12FOhUy/DEIFaoxmk/xxOcfW3L+/lK0ucXzFShhHlyGgQEAT0re3bfYbqIaVziIHw7ppvGun1/FRRUVksFWFq2QazDYD5jO+41yL68+0hnqrpKjXy3qQW4J1p48DsruJRWKwwZYYKKnG8axMjGWbQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1636518322; bh=pC6teX/CvO/skVkMN0o1PCnVJylv16zvtrUQVHPp3GW=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=cew/FjmeEe522mYpG00W6+vbhmi0Gfmu8CXVmb3abHkVTgM3TeCGWOLP7BlvDM5SPFk8pIyJUFKKmgnroTwfDu31mtn1Mm4xpp4xTb1CX39h2eReorBXrvVIv+nPHRvP5oURTAxDMZTEucTqwBN5BJhX5WiCphIEhH50z8ZCBXfgEEYDC1yFusAIgTIg4VaP2XZsRyIN1b8PFKv/wsh1GdClxLs0uvDuzUF1KGtadBH1YGc1TJzCuWn+POhzYVDBfFXjwvjJL/PW4iFLxlop5NMeOCLR5BuZHWp9Ro95/DP69F4+uGJljussGB2T8ytKYpXxeJHKXXnMCuaIb00SRQ== X-YMail-OSG: 48qf.oYVM1lV2OSce3AbEm.49RuA6Zo3tr7EBJT7gjNQGBT8hVN83ihWMBcSotW vMJlhhi_SrO6306tUZtTSIQgmVgZBuXb_n_8uMwvFNrpzxGDrS5sXZbSKB.oEpiUCOgZ1wmc8DU4 Ikd8Vd2F55GKHZGrVgrHGKvg3050usFiT4qlk4foQNGoTjSNVM8geCEXas.NEIF.s0RTWfUKZJhW Iw4S1oefuU_q8vLEzN0ycauZUospBx1L28Bn.jUqP.j7w1U6GWbtp4Nl1COCl_10wYBKQuBUzC_9 jybqOGgbyr775dWCFC1USbxR3CcxUG0_vE0UAaquWfNeQYwStQBtHbZy7ZBujpI6s8Bgh6RuB9Oq B2jcxTQ.fqgX1mp_3XDNitQLmbohn5iWzjzjpv25GCxnSKJZN25Qd2UJ1VAZx8JACQt._NJlpTk_ _GDDK1lPC6XwE6mlZXGM3trSt2Gc5i8X4nx3XjEUMYCHu2cJHovozeBUn5Kp7dagy7cjjqLfEcMQ ZLODNlrAnEEizVJK02F5Ty7UUfFyVLPFYaXFYptMWWUf4v.SK7ztkHEIR4kl4nBea4nF19XDDl2W gov0s6oHgGfjGebQ4EUmetI6NIghcexWXHSP1651v8cCHW7RrQDURuiYLnD1rJZ1Kh8dwoAUB6MZ s4ktQmT_lkF5f18jP9TLYn_slqoutiMrhhlcMjkYtXXvTfSstxRWAqTmHiYzmINaZ9ULowgIK3yc aZaSbPsNDw1p470pQM9dxz8mqf87tkc3Ymtg9HGzi8FSjIrgmjX.jV6BF4v84TJ.1PckvnEwGUY2 hbnnBPu_TNeX1ydTTwrBHljuNuATHStLEw2aVfW2EAfbi9tBlzAtOl8PhCUb5qUqvKO0Qtkw7qt2 xDcAz60hugV1Ms4Hkuf1IaUxRUHT30ZYguLvX2vucplmUQjXoEJ6VuKAYPfYGOm6ExAAqBs.vgMV AAiRguNpMDv4NqlypKVzE7IGQO41C48FTC6f14J5igOjWh4gDwxvkJ741Cu1fRkfIPuzp9xZcLlX cQnmXhGH4oSG82gsf3CVqGIsbcwQzxqKJSmpOut3OPWT0dWXfRxrOSWFj.jxFTTmxmZDzIoWApgb MbEBButc2Qi9iv5ZfK7IaXxKw4TY4GecEFlaDPx4CEsNPc3v8NsY52dRT41srZV87XrgKx2WkBPQ vJmyh5y0gr94NRSmjy2zQ9.ADOpt.MejlxTOrUXhAGsF3zgR_FfaNWTL7_aT.mGK4HzGXeqflwnv eEpugt3V5F9JXrmuOiI9iBnhm5ZMMRyWlRZecpmVnbvVlx5o6kYNU3LTrurZIuPYGB7OFJwkiPsz AH3Sjj.8N4R_PyS6_w5x4WFq.nBBXFC3lS1Vv1a00sD37nDbLS6m6zjeok9mKfocXfEyXfdrLjaH p5BOkmHlgZPkcXRZrTSE4vs6GvGX9C4mZmsrlx8XuIOm4NVJJgDybbjty8QoTkax4p98VZFwrLNz bTQ0DIJMjJiL3f_gO2s8D3U8PkSiktEOsrz2iSUhzIn.7wj7G36eCf0yURvxrh53NWEWDbVBOZ3h .tYqoVPwF4UNEfQNk.WVzMVx2FlXTDh5F6Rf_sX2d3vUBcybXay4Hz5qk3UA44r7gzF3ATXBB1q3 ij_22sizax9Ywl52OBZFrj7ZwfIQcK78TqNZfZfkctI0LDX_3BzvXWBsw3gyW9D7qDgeUYaWzGDQ vYMBwr2Z9nNpj2Vjj7.TRNXTNjO6b39cYCG9pGZ6PmXEGQLAdurQSTFLbl0ZEw4pvjcipY0pdJc9 DMVdiITEg43wCVVmqNFQdVzd2GysCBKHIpyAvWT2yi8eHOOykGGK0LiujqNOPSSuzussZG0fUVLq aqONZ9fIFskCEeyekJMHmipXoevN4XI1chRYrOMY4LZColICofS0aNJ40b5E6lnURcFToKucsEpX rvVqfPSSNzzYj8r97RxMQ_OHj5uGPCFs_OXJk6PdyIz5oc37uPpSHi0S4RJJpu.kWAvDBYTmWwwO NrxTlJcP3rdKxkN6VukzVWmzPakANYcS6nA16zEcSMeeKebHposxL7rYkcgP0w4bVidIVDBhk8XU QG0DYCajV_iUHfOFpKDTKdWdbk0j00U2g6Jw09AGFzT.eF3RXN1nFvGjt9UEB0ax1f0m_xQSWuYe 0zYGJs8CQ8bcarnFUVAWKXbc76YZ5bumPi8Ts95Cl7NLL1CpkQho8Wl78hWm9cHpS97dZpsfQHVX Ojpodgw7.usTE1W_oHsN.xumg3viw5S1ViFCX_A2MrQWhaPJNGJpGo.LAMYMCNEbMi_lu9i.eYgf l_StuT9GTQ2lwasLhaxZScDeAHbi5u6vOGBKfmqR3gI9jR.u.yvvxW5gUxKGeDH1OL4aUabXQNat X29jYfa6L33P7ssAY X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.bf2.yahoo.com with HTTP; Wed, 10 Nov 2021 04:25:22 +0000 Date: Wed, 10 Nov 2021 04:24:18 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: cabo@tzi.org Cc: jsonpath@ietf.org Message-ID: <889202295.1444025.1636518258585@mail.yahoo.com> In-Reply-To: <6C8B938E-3C05-40BD-8B8D-A5D2A8E8C1E9@tzi.org> References: <661668953.1426338.1636514133505.ref@mail.yahoo.com> <661668953.1426338.1636514133505@mail.yahoo.com> <6C8B938E-3C05-40BD-8B8D-A5D2A8E8C1E9@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1444024_1948104721.1636518258584" X-Mailer: WebService/1.1.19266 YahooMailAndroidMobile Archived-At: Subject: Re: [Jsonpath] Closed GH issues 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 04:25:34 -0000 ------=_Part_1444024_1948104721.1636518258584 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'll comment on the ones that aren't clear to me. Thanks. =20 =20 On Wed, 10 Nov 2021 at 5:12 pm, Carsten Bormann wrote: On= 10. Nov 2021, at 04:15, Greg Dennis wrote: >=20 > Carsten, I see that you've closed a bunch of issues and referenced the as= sociated PRs.=C2=A0 Thanks for doing this maintenance. >=20 > However, it's a bit difficult to know what the final resolution was on so= me of them.=C2=A0=20 Which ones? > Would it be possible for you to edit some of those closure comments to su= mmarize the outcome? Sure.=C2=A0 Which ones need this? (Some of the issues are meandering brain dumps, and it is not clear that th= ere was an outcome. I=E2=80=99ve marked a few of those with =E2=80=9COBE =E2=80=94 can we close= this=E2=80=9D; we=E2=80=99ll need to find out if any of the participants s= ee anything open remaining in these issues; I cannot find that out.) Gr=C3=BC=C3=9Fe, Carsten =20 ------=_Part_1444024_1948104721.1636518258584 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'll comment on the ones that aren't clear to me. Thanks.

On Wed, 10 Nov 2021 at 5:12 pm, Carsten Bormann
<cabo@tzi.org= > wrote:
On 10. Nov 2021, at 04:15, Greg D= ennis <gregsdennis=3D40yahoo.com@dmarc.i= etf.org> wrote:
>
> Carst= en, I see that you've closed a bunch of issues and referenced the associate= d PRs.  Thanks for doing this maintenance.
>
> However, it's a bit difficult to know what the final re= solution was on some of them. 

W= hich ones?


> Would it be possible for you to edit some of those= closure comments to summarize the outcome?


Sure.  Which ones need this?
(Some of th= e issues are meandering brain dumps, and it is not clear that there was an = outcome.
I=E2=80=99ve marked a few of those with =E2=80= =9COBE =E2=80=94 can we close this=E2=80=9D; we=E2=80=99ll need to find out= if any of the participants see anything open remaining in these issues; I = cannot find that out.)

Gr=C3=BC=C3=9Fe= , Carsten

=
------=_Part_1444024_1948104721.1636518258584-- From nobody Tue Nov 9 23:15:01 2021 Return-Path: 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 25A0E3A1331 for ; Tue, 9 Nov 2021 23:14:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 HX1Ijbg8nEn5 for ; Tue, 9 Nov 2021 23:14:54 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29EF23A0B58 for ; Tue, 9 Nov 2021 23:14:53 -0800 (PST) Received: from [192.168.217.118] (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Hpx1f1PD7z2xMt; Wed, 10 Nov 2021 08:14:46 +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 In-Reply-To: Date: Wed, 10 Nov 2021 08:14:45 +0100 X-Mao-Original-Outgoing-Id: 658221285.757261-66304a6a3039639965e611a97395ba67 Content-Transfer-Encoding: quoted-printable Message-Id: <2899C5CF-FE41-43AE-8ABF-0B41545D78A5@tzi.org> References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 07:14:59 -0000 I made some slides for today; I think the chairs may be sleeping and = can=E2=80=99t publish them in the meeting materials, so you can peek = here: http://tzi.org/~cabo/2021-11-10-jsonpath-cabo.pdf > On 2021-11-02, at 09:54, Stefan G=C3=B6ssner = wrote: >=20 > I can see two big construction sites (or merely decisions to add them = later or leave them out): > * functions in the expression language, `key(@)`, `length(@.arr)` = or additions to `@` as in `@key`. I missed that part, maybe I can do some additional slides. > * equality tests for structured types (deep equals) This is under #127 in my slides. >=20 > and one not so big: >=20 > * clean up blank space in ABNF `S` (I can do that) = (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126) Which is now done (thank you!). > We also need to discuss and aim for agreement regarding: >=20 > * JsonInclude = (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124) My handling in the slide for #124 is a bit terse: >>> Proposal: Not in base RFC. Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Nov 10 00:20:14 2021 Return-Path: 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 E32B93A005C for ; Wed, 10 Nov 2021 00:20:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.226 X-Spam-Level: X-Spam-Status: No, score=-5.226 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-3.33, 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 ZRKj2M6qDrQF for ; Wed, 10 Nov 2021 00:20:07 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (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 626453A0045 for ; Wed, 10 Nov 2021 00:20:07 -0800 (PST) Received: from [192.168.178.20] ([88.130.50.44]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MysmQ-1mWvJ9167G-00vsy5 for ; Wed, 10 Nov 2021 09:20:05 +0100 Content-Type: multipart/alternative; boundary="------------lFMRu0owLTqwC7e3PUXBCHbU" Message-ID: <8d16e6c3-48ac-ff70-039a-822493eee192@goessner.net> Date: Wed, 10 Nov 2021 09:20:02 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 To: jsonpath@ietf.org References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> <2899C5CF-FE41-43AE-8ABF-0B41545D78A5@tzi.org> From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= In-Reply-To: <2899C5CF-FE41-43AE-8ABF-0B41545D78A5@tzi.org> X-Provags-ID: V03:K1:wcFzR/WWrEHXskZWmW0iXOrRNSMKCxdXalg3DLeFpKGG6nvETwp Rxj0mela3dGcQeXtKTcmOY8rQxGaA4VPw554AKjEUxBWIm8MbkteNXuKj/w1H/YOXfgu17V pQNzHN6As78Ze+/MoNJV60FcDhVa6XSAxkTTrznYwXIG/GjS4pyLt8oqsPCdyRZkvH/9dA/ bzXiNPKPdgiJrJVKPyaEA== X-UI-Out-Filterresults: notjunk:1;V03:K0:1fx0MogyMv4=:wdC8TUoXBZohcs+r2AHGJo dyiGNyiN72qiSLOqGQCZRBRcr8uxpuJTaqm3L4QEHo/IIlTfNsY+RyxShxOKu1vGqO4DYTEbx bCB1wJ/BVXAUeoHkRNTpl/C8BqRQn4lmDljtN9hIEzWcQdjU27V8c+98VnuBu/QVyquwLWk0j nRg4QpHD+CsB3eDnJsW5KKcBlJFkYH973Ws8uZKblDHgEc8F20iMAyWKGtNE4yakhgtrs+tzA aXOE/UVrZOhOlvnHP0s3kbCxG/ePZ503MA7qri/ch07ouoCXFHxeUZun8N9UBVbBjDMDEZCDR 9runbk3+4IYHgHJB+7VoDYLNLCjIvNc2JBt5fBy8UXid7ucptgFPSLhiJNnm7kWk/e80OVY+/ fmFc8QBVRztRaCZZGOhz+1kgbak8pBBP31yLV7YLmtykSYBBpd1O0verUWSfNh0nuN7RgJ42W x6yG+kXr8H16/zEe86yQ7QB7nrCc29EIXD+EZZymz4TXOhG3jcZycXY/6pQZW4bMgh0/c0iAr 2pW0zku5TAtNLcN/UpuyNPjGh75Sh63pBBrVWci50lOQLTyws3EUW4yIQ4XSXIxoHj/zY537o UHMSBDk7PtFtiWAfyEAD6D3XxI+nqyS93bO9Sg/kqgRiO/CVVEkwRuBpq5wUJ+I93WbxR3nCo OAsws7wnnxSWYXkx+NTTLsZFsByfjQC5/aa5/hqtuvqkD/BY6dIuFOIDmgcBnK3+lhR8= Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 08:20:13 -0000 This is a multi-part message in MIME format. --------------lFMRu0owLTqwC7e3PUXBCHbU Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit thanks for making the slides. I will go through them. I also applaud your closing of issues. My lecture will overlap with todays meeting. So I will join you 10 to 15 minutes later. Thanks -- Stefan Am 10.11.2021 um 08:14 schrieb Carsten Bormann: > I made some slides for today; I think the chairs may be sleeping and can’t publish them in the meeting materials, so you can peek here: > > http://tzi.org/~cabo/2021-11-10-jsonpath-cabo.pdf > >> On 2021-11-02, at 09:54, Stefan Gössner wrote: >> >> I can see two big construction sites (or merely decisions to add them later or leave them out): >> * functions in the expression language, `key(@)`, `length(@.arr)` or additions to `@` as in `@key`. > I missed that part, maybe I can do some additional slides. > >> * equality tests for structured types (deep equals) > This is under #127 in my slides. > >> and one not so big: >> >> * clean up blank space in ABNF `S` (I can do that) (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126) > Which is now done (thank you!). > >> We also need to discuss and aim for agreement regarding: >> >> * JsonInclude (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124) > My handling in the slide for #124 is a bit terse: >>>> Proposal: Not in base RFC. > > Grüße, Carsten > --------------lFMRu0owLTqwC7e3PUXBCHbU Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit thanks for making the slides. I will go through them. I also applaud your closing of issues.

My lecture will overlap with todays meeting. So I will join you 10 to 15 minutes later.

Thanks
--
Stefan


Am 10.11.2021 um 08:14 schrieb Carsten Bormann:
I made some slides for today; I think the chairs may be sleeping and can’t publish them in the meeting materials, so you can peek here:

http://tzi.org/~cabo/2021-11-10-jsonpath-cabo.pdf


On 2021-11-02, at 09:54, Stefan Gössner <stefan@goessner.net> wrote:

I can see two big construction sites (or merely decisions to add them later or leave them out):
    * functions in the expression language, `key(@)`, `length(@.arr)` or additions to `@` as in `@key`.

I missed that part, maybe I can do some additional slides.


    * equality tests for structured types (deep equals)

This is under #127 in my slides.


and one not so big:

    * clean up blank space in ABNF `S` (I can do that) (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126)

Which is now done (thank you!).


We also need to discuss and aim for agreement regarding:

* JsonInclude (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124)

My handling in the slide for #124 is a bit terse:

Proposal: Not in base RFC.


Grüße, Carsten

--------------lFMRu0owLTqwC7e3PUXBCHbU-- From nobody Wed Nov 10 01:19:43 2021 Return-Path: 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 431BB3A0AB1 for ; Wed, 10 Nov 2021 01:19:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.217 X-Spam-Level: X-Spam-Status: No, score=-5.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-3.33, 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 CGvXyoa1vNxd for ; Wed, 10 Nov 2021 01:19:37 -0800 (PST) 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 F157C3A0AAD for ; Wed, 10 Nov 2021 01:19:36 -0800 (PST) Received: from [192.168.178.20] ([88.130.50.44]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1M9WqY-1mqFXu1toa-005b12 for ; Wed, 10 Nov 2021 10:19:34 +0100 Content-Type: multipart/alternative; boundary="------------Y7U8I1g8mwiDCMZl27HYlhwJ" Message-ID: Date: Wed, 10 Nov 2021 10:19:32 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= To: jsonpath@ietf.org References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> <2899C5CF-FE41-43AE-8ABF-0B41545D78A5@tzi.org> <8d16e6c3-48ac-ff70-039a-822493eee192@goessner.net> In-Reply-To: <8d16e6c3-48ac-ff70-039a-822493eee192@goessner.net> X-Provags-ID: V03:K1:U/PHkPlOXc6bpfyLEa5KFCpKiZcZN4dkAwc1SwXOo36HJceYluj pINzYY1TC+iVTuD+YbQsN5LpQmjTSTHg5hCjVz/Jye6+g6fYAdnkJNsu/YF6gLKb/KBVl/5 GZmUTUh/dbepxF/PrhFA0uJOw0NLXgJ6+mnN98d+9aU75ZLhZLoNPmKp4DURKYvr2oGX2w/ tbetha0STJByJaMovk8gQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:7ak7qRdcxpc=:QVSOajzs5d4VyiYx0zPqZV ttGqT4ciUCLnR320MpmJb+WDYuCN+mYZiKvmVI1JuvyHlcwtvPnfsMv3+lBvcVUo3VC56NtyW GjQ6neXLujZO34DXMpDL4jNLjZBfQ8CEry7+2mOJRsRZBo8enY62VI4lIZS7h5W3Uy03juVrT E773GTtG37x48/t6KCOHWyOAKOsibFFQbdHo8M8oWPKVmRnyb8t93iomy5zxFTdWdyO384BtQ tSd14GpckVn3iJvGn2I/za+Gh1jO0b+eTHJYBt7hzt3QRowCZZsTtPRuIzsuS9VomB/L7F835 FrE7ABSh4565rT6eOvQVgU64VIaIZO0x6SozkATjO53qZ+puTMr0Nc5/qMsjQAZBJaiZOH/+W njjbFGt3WHletITETCBB8ALCiUUWmUfgjatuFC6JOY4/rkFy8Tqq+KGsx/YmN+yrbILKmdDcb Wss3avZEs0ZmZq7AQAFTux4WzL52/tA3bmdlSkvZCCMx/BCVMvmxHjqbpmlIneVgjRMyrFXdW 49fS1BvXI9rXpmWn90yUgfCwRoWIB32BlXe3D9fbM/OVCZTyXUwAIAygpjMCJPatrAIkH8ePX ZBkGsmAUJXRxkG1ZymSz8/bbbPiadgnOWbZ+vH5OPE5BO5DPSh5eWyaL+F8Phl/YI1azrgnSG mTYt4G7l6zDlRBMZksyfy6yuXT4pmS6SL8wpMmB4aAyRgPMRTlOv39lUib0owHI4RfKk= Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 09:19:42 -0000 This is a multi-part message in MIME format. --------------Y7U8I1g8mwiDCMZl27HYlhwJ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit which session software is used today ? Am 10.11.2021 um 09:20 schrieb Stefan Gössner: > thanks for making the slides. I will go through them. I also applaud > your closing of issues. > > My lecture will overlap with todays meeting. So I will join you 10 to > 15 minutes later. > > Thanks > -- > Stefan > > > Am 10.11.2021 um 08:14 schrieb Carsten Bormann: >> I made some slides for today; I think the chairs may be sleeping and can’t publish them in the meeting materials, so you can peek here: >> >> http://tzi.org/~cabo/2021-11-10-jsonpath-cabo.pdf >> >>> On 2021-11-02, at 09:54, Stefan Gössner wrote: >>> >>> I can see two big construction sites (or merely decisions to add them later or leave them out): >>> * functions in the expression language, `key(@)`, `length(@.arr)` or additions to `@` as in `@key`. >> I missed that part, maybe I can do some additional slides. >> >>> * equality tests for structured types (deep equals) >> This is under #127 in my slides. >> >>> and one not so big: >>> >>> * clean up blank space in ABNF `S` (I can do that) (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126) >> Which is now done (thank you!). >> >>> We also need to discuss and aim for agreement regarding: >>> >>> * JsonInclude (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124) >> My handling in the slide for #124 is a bit terse: >>>>> Proposal: Not in base RFC. >> Grüße, Carsten >> > > > > Virenfrei. www.avg.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > --------------Y7U8I1g8mwiDCMZl27HYlhwJ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit which session software is used today ?


Am 10.11.2021 um 09:20 schrieb Stefan Gössner:
thanks for making the slides. I will go through them. I also applaud your closing of issues.

My lecture will overlap with todays meeting. So I will join you 10 to 15 minutes later.

Thanks
--
Stefan


Am 10.11.2021 um 08:14 schrieb Carsten Bormann:
I made some slides for today; I think the chairs may be sleeping and can’t publish them in the meeting materials, so you can peek here:

http://tzi.org/~cabo/2021-11-10-jsonpath-cabo.pdf


On 2021-11-02, at 09:54, Stefan Gössner <stefan@goessner.net> wrote:

I can see two big construction sites (or merely decisions to add them later or leave them out):
    * functions in the expression language, `key(@)`, `length(@.arr)` or additions to `@` as in `@key`.

I missed that part, maybe I can do some additional slides.


    * equality tests for structured types (deep equals)

This is under #127 in my slides.


and one not so big:

    * clean up blank space in ABNF `S` (I can do that) (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126)

Which is now done (thank you!).


We also need to discuss and aim for agreement regarding:

* JsonInclude (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124)

My handling in the slide for #124 is a bit terse:

Proposal: Not in base RFC.

Grüße, Carsten


Virenfrei. www.avg.com


--------------Y7U8I1g8mwiDCMZl27HYlhwJ-- From nobody Wed Nov 10 01:22:49 2021 Return-Path: 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 39EE13A0AB9 for ; Wed, 10 Nov 2021 01:22:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 mXdWIH2O1EnC for ; Wed, 10 Nov 2021 01:22:43 -0800 (PST) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 192583A0AAD for ; Wed, 10 Nov 2021 01:22:43 -0800 (PST) Received: by mail-ed1-x531.google.com with SMTP id o8so7930342edc.3 for ; Wed, 10 Nov 2021 01:22:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zDlcBv29PnI9okbBY44svk3IhO3BvBNnQzs10hMRRNk=; b=inSvHndrFN4LnZVXN4Rg5eAlqlQ6EFpyT9l2kZsHvo/grEi7MkLkAAEZmkIVcO10KY Ibs1nLYy12rsNpM+YNjXN1wuMMyEssnrKNOWC3unJI7yIZulSuYJS4S/RkH8QWvfzOj4 WrfEG2ta52h98Pue7E6m5GSnVoscQQdLNMFhMBPLPqQzghjyrNpru/T+FiExkeDXFkPW W1ERa0kiFIL/PEeA3589UuZVRlo+zbScFhHyB3Kq8YKTGFRKsiYTnf68obJTIT3AuQ9F ZpZ1RseuJZ4f1nMUaEu9tnvvNFU3Yg6NR6pEQ+N9BbTKHXCeg02azX9ADIp8zSO3QDu7 vJGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zDlcBv29PnI9okbBY44svk3IhO3BvBNnQzs10hMRRNk=; b=UrT6SJ4LszzHKiRSXexMD7GFGq1Tf5E0EGY3+v/78+ByZlfUpl2u/2UFv2BuTlBHeQ i/JeEI++lM+Nb4aypN56dr7bM+TnR7QXPvxOcBusejrgAjinpffd0dU1WM9jZy06cmuT tQAitGhgyfTUqmPoKrspDsixSEJMF7EPok0zLiwRwAzRBcSOhzgpBz6qXwBaIkdXtJMv UP2yYnNzGZ8CYQML8R6vLKz4PPA4xa8mM22rw/RSZLv+3fjx9cgPw9hK5BHEIQTVFZws 11n5oGGJ+QQjyxs4JVcSCpcrpdvgr9+hIWXDHym/TcG38iEMCDgcLrAodnSASBXdXamU uhAA== X-Gm-Message-State: AOAM532rFubcWt1nVTQoOeLSzYxjIR6fgk+kTDbBq8ShYqEsd8Of7vVW 80MBF+HU4L77B7lgdokvnOcTeNaOsLA= X-Google-Smtp-Source: ABdhPJxGEnhX208o/fhPN44lYKbMa0fjsJk/p1PHCa9KErRzrmOdyAtsgP3gqzIaORTFlT8Sy7DG4w== X-Received: by 2002:a17:906:6547:: with SMTP id u7mr18677534ejn.544.1636536159863; Wed, 10 Nov 2021 01:22:39 -0800 (PST) Received: from smtpclient.apple ([145.58.25.246]) by smtp.gmail.com with ESMTPSA id hr17sm2216901ejc.57.2021.11.10.01.22.39 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Nov 2021 01:22:39 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: James In-Reply-To: Date: Wed, 10 Nov 2021 10:22:38 +0100 Cc: jsonpath@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <64ABF79F-1471-47DD-9B99-EA259A25DDB1@gmail.com> References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> <2899C5CF-FE41-43AE-8ABF-0B41545D78A5@tzi.org> <8d16e6c3-48ac-ff70-039a-822493eee192@goessner.net> To: =?utf-8?Q?Stefan_G=C3=B6ssner?= X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 09:22:48 -0000 We don't use external VC software - all will be done in Meetecho, which = should work with any modern browser, and I believe you've used before in = previous interim meetings. The link to the meeting can be found on the = agenda on the icons on the right hand side: https://datatracker.ietf.org/meeting/agenda/ - J > On 10 Nov 2021, at 10:19, Stefan G=C3=B6ssner = wrote: >=20 > which session software is used today ? >=20 >=20 > Am 10.11.2021 um 09:20 schrieb Stefan G=C3=B6ssner: >> thanks for making the slides. I will go through them. I also applaud = your closing of issues. >>=20 >> My lecture will overlap with todays meeting. So I will join you 10 to = 15 minutes later. >>=20 >> Thanks >> -- >> Stefan >>=20 >>=20 >> Am 10.11.2021 um 08:14 schrieb Carsten Bormann: >>> I made some slides for today; I think the chairs may be sleeping and = can=E2=80=99t publish them in the meeting materials, so you can peek = here: >>>=20 >>>=20 >>> http://tzi.org/~cabo/2021-11-10-jsonpath-cabo.pdf >>>=20 >>>=20 >>>=20 >>>> On 2021-11-02, at 09:54, Stefan G=C3=B6ssner >>>> wrote: >>>>=20 >>>> I can see two big construction sites (or merely decisions to add = them later or leave them out): >>>> * functions in the expression language, `key(@)`, = `length(@.arr)` or additions to `@` as in `@key`. >>>>=20 >>> I missed that part, maybe I can do some additional slides. >>>=20 >>>=20 >>>> * equality tests for structured types (deep equals) >>>>=20 >>> This is under #127 in my slides. >>>=20 >>>=20 >>>> and one not so big: >>>>=20 >>>> * clean up blank space in ABNF `S` (I can do that) ( >>>> = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/126 >>>> ) >>>>=20 >>> Which is now done (thank you!). >>>=20 >>>=20 >>>> We also need to discuss and aim for agreement regarding: >>>>=20 >>>> * JsonInclude ( >>>> = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/124 >>>> ) >>>>=20 >>> My handling in the slide for #124 is a bit terse: >>>=20 >>>>>> Proposal: Not in base RFC. >>>>>>=20 >>> Gr=C3=BC=C3=9Fe, Carsten >>>=20 >>>=20 >>=20 >>=20 >> Virenfrei. www.avg.com >>=20 >=20 >=20 > --=20 > JSONpath mailing list > JSONpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath From nobody Wed Nov 10 03:37:17 2021 Return-Path: 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 288BF3A0E51 for ; Wed, 10 Nov 2021 03:37:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.919 X-Spam-Level: X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Fg7mm5w1ldfF for ; Wed, 10 Nov 2021 03:37:11 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8418E3A0E48 for ; Wed, 10 Nov 2021 03:37:09 -0800 (PST) Received: from [192.168.217.118] (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Hq2rL3GNTz2xbf; Wed, 10 Nov 2021 12:37:06 +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 In-Reply-To: <2899C5CF-FE41-43AE-8ABF-0B41545D78A5@tzi.org> Date: Wed, 10 Nov 2021 12:37:06 +0100 X-Mao-Original-Outgoing-Id: 658237026.13609-e618f48cbd69db332fd296ac620c1c59 Content-Transfer-Encoding: quoted-printable Message-Id: <89BA7BCB-7478-47A6-9F0B-41BF83EB5E89@tzi.org> References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> <2899C5CF-FE41-43AE-8ABF-0B41545D78A5@tzi.org> To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 11:37:16 -0000 I made an update, and the chairs uploaded it quickly, so you can look at = https://datatracker.ietf.org/meeting/112/materials/slides-112-jsonpath-iss= ues-01 instead of the below. Gr=C3=BC=C3=9Fe, Carsten > On 2021-11-10, at 08:14, Carsten Bormann wrote: >=20 > I made some slides for today; I think the chairs may be sleeping and = can=E2=80=99t publish them in the meeting materials, so you can peek = here: >=20 > http://tzi.org/~cabo/2021-11-10-jsonpath-cabo.pdf >=20 >=20 From nobody Thu Nov 11 01:38:14 2021 Return-Path: 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 AE8F63A0846 for ; Thu, 11 Nov 2021 01:38:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 ax5v_c2KMfO0 for ; Thu, 11 Nov 2021 01:38:08 -0800 (PST) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1595A3A083F for ; Thu, 11 Nov 2021 01:38:08 -0800 (PST) Received: by mail-ed1-x536.google.com with SMTP id z21so21757609edb.5 for ; Thu, 11 Nov 2021 01:38:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=+eGBrnZWxgEWDJkElijgw34k87FscgQMgs6VlbQu7lI=; b=g44RVibe5Xwyv/VK6hzw8EgqRobsZjC2Ec0pLn7h9f1oOqpmcjfS8MZ2VXuU4DthY6 TpHFh3MMTidADyL33Bs6Pi9+tEzWVwwdjMp+HxUv9oCLMV6vfH04h9CEqYQ5m6Z7jg7q Se1EOZpjcKDdB08QcH1vMickm4MVLdjaPhmdX93ZfALNcnfdqvz+7Kpj3ziA5VwcIG43 TBA59/R9Y+v8e3V0vObQbJmh60MnfpeP8qV+iVe161EBub9KAuiXgywV7qxLUs3lUKzN rNoeix6+sFysLWCDppJaTixBvhNRjt5iG0+UUPT3RIlRibcmFd7b3EtRkRWxD/mTaKHP MqVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=+eGBrnZWxgEWDJkElijgw34k87FscgQMgs6VlbQu7lI=; b=mSzGvth2RjPwO/2/a5qfvXwW6VhgHybbcMhXwgI+h4vjwkhhhmPTOipftGjXPmXxih osjk6knLkPs66Xc7J+24nw9LiAZNsVAskrXPu/3/rC8jWVt7IYOYsyvCVtelhQAwHVBM sIlqi3vrNe7RtTNIQZKvVIZY/U83+cg4PXGUUy1nBUmmyJ/9tl4rtQbDVW0/qjKLvWBs pY6yQ/NGjoGrmJIFRNUPKys3/L21WxgJuhtHhF6Fqs3Z4SARpgIZ+4Q4NbasA3Sz7O+G 0FRMOv4l8y189fVvVcCgS0Rv2XIGsAJF6jt1FM2ME/WKUtRd8Iz0s/NfiqJ33ulGWiOg cLlQ== X-Gm-Message-State: AOAM531d7lzLKihiacReUuEZDLXyzyvyy2maDXhS2r7nh+cQT1OOt7U9 phKUbYryIzg3lpny5mMCIM4d3CL9427umA== X-Google-Smtp-Source: ABdhPJwSlU9H3mboOhPpAqLxCn1XBZnLMb4BgW8yD0YRXnbJf3qr2Po1J/qmInBB0+l9cMu89JoKWQ== X-Received: by 2002:aa7:c693:: with SMTP id n19mr7913859edq.101.1636623484926; Thu, 11 Nov 2021 01:38:04 -0800 (PST) Received: from smtpclient.apple ([2001:984:65b0:2:e5f0:a10d:6a55:59b]) by smtp.gmail.com with ESMTPSA id d18sm427547edj.23.2021.11.11.01.38.04 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Nov 2021 01:38:04 -0800 (PST) From: James Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Message-Id: Date: Thu, 11 Nov 2021 10:38:04 +0100 To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: [Jsonpath] January 2022 interim meeting poll 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2021 09:38:13 -0000 Thank you to everyone who attended our very productive session at IETF = 112. I'll be sending out notes and action items to the list in a few = days once the dust settles. We're now looking to schedule our next interim meeting in January, = starting Monday the 17th. If this isn=E2=80=99t feasible for you, please = let us know and we can discuss or expand the polling. The poll is here https://doodle.com/poll/2yhfunacqxtcyrqa and we'll = close it in a few weeks time based on people's responses. Thanks Tim & James JSONPath Chairs= From nobody Thu Nov 11 10:04:18 2021 Return-Path: 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 C38B93A0E03 for ; Thu, 11 Nov 2021 10:04:16 -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, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 KypSihR2giJC for ; Thu, 11 Nov 2021 10:04:14 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (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 E92E13A0DFB for ; Thu, 11 Nov 2021 10:04:13 -0800 (PST) Received: from [192.168.178.20] ([88.130.50.178]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MWRmF-1nE2ee3L9H-00XxIK for ; Thu, 11 Nov 2021 19:04:11 +0100 Content-Type: multipart/alternative; boundary="------------vvHvL8bwLMWdQ7THSllTW5iQ" Message-ID: <0360996e-5040-3152-251c-d09139595211@goessner.net> Date: Thu, 11 Nov 2021 19:04:10 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 To: jsonpath@ietf.org From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= X-Provags-ID: V03:K1:uYZr65NS6vesGkkdVMCAq1VSzAirxxlGUrUiAu5ls8kU5Ag/04G M3GQZ8Sygw57QiqHlM101xRQFqdTLneL0bXTBjPemTpUDwuZSZgTPoKB2auS4E+VDEgsRj6 8Bnc9IBcGzJeaMEeLbXBaSAPll6hVhqXBxZ/1Fsyb1RBSw6rOj6q2xkKan8W2MzGn5v4L41 bnHTTvo9TSY3Sm2faRNfQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:kiSleobkP/M=:U2ZDBFfMuFS0D2DMWjEkmh G6aW2Yv5oV5A58QlprM+WMpyunHU2E8IFGG4CZCcoG9uD1kfCBQGKVoz8v530VV3p8VU2lTB0 jbKwMNyRlDJfu6so9Aig2MiVRbZLco1Bo5dq0nj+Hoh2rp1qC4WE45xJnvvESZntq9sb2amqD 7OPK3d1vu16FLrozG+FcfWxPXLSqqSMRgAX/rddS6z5I1MHKGgC0uCoXngixiPHvJktIPB2Ek VOyxMFDuHkcE4erEnFaBSYIi+mWh9rrOi5LfDIhO3qIqafpXYdLADnt0K73LSKW9Gf12yLIG+ xy4tbdOp55B3pxGU75pGLOareLkb2R0b9vK0x11BtULx7zlxEOlNc++gO3KnoQn6EbkL0MyXM 8ueOUNhB349X2dYBi2QfW9wxRa04Io+AZA73+V/EKb3eThMEhsIeinLxWhjkb4q9jQHQy7J4Z cdEP0oNnlcftXP0vTSF9h3FV+pyJQyTU90gGCI2Ph4d9fZOf29WHt4An3oqxAve8BIEFCkyoU ubxCiFNDDJYi8tDz+cqUIfptRGgZw3qPKkEZFjHphQpAIKwmj3KtvSPBHVtamM/9nuEDppcZj wBxeL6Nr0DQR2tRVNMztSBoaOcN3oL6h5s0mA8RcWEnfrkTMivH+Bi8YYrshKz+ouzAwKac3Y RgQ809pGuPUFm2NSwPTQMl8NmGszvHaU0FDWsRjQBkF+KfkW+zPgU0/1ZGv8DdA6rkM86BvsV lym3/uUyP6zwkKL9 Archived-At: Subject: [Jsonpath] Object member names in JSONPath queries ... 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2021 18:04:17 -0000 This is a multi-part message in MIME format. --------------vvHvL8bwLMWdQ7THSllTW5iQ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I consider it an important result of our discussion yesterday, that object member names can ... 1. be used explicitly in JSONPath queries only with     - dot-selector     - index-selector     - descendant-selector     - union-selector 2. be used explicitly specifically in filter-selectors with relative pathes only with     - dot-selector     - index-selector 3. not be implicitly accessed as a target in filter-selectors Please can someone enlighten a dump mechanical engineer, what 'projection' means in this context. -- sg --------------vvHvL8bwLMWdQ7THSllTW5iQ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit I consider it an important result of our discussion yesterday, that object member names can ...

1. be used explicitly in JSONPath queries only with
    - dot-selector
    - index-selector
    - descendant-selector
    - union-selector
2. be used explicitly specifically in filter-selectors with relative pathes only with
    - dot-selector
    - index-selector
3. not be implicitly accessed as a target in filter-selectors


Please can someone enlighten a dump mechanical engineer, what 'projection' means in this context.

--
sg
--------------vvHvL8bwLMWdQ7THSllTW5iQ-- From nobody Thu Nov 11 10:12:13 2021 Return-Path: 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 12D553A0062 for ; Thu, 11 Nov 2021 10:12:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 4KseyrXCu1yA for ; Thu, 11 Nov 2021 10:12:07 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C16433A005F for ; Thu, 11 Nov 2021 10:12:07 -0800 (PST) Received: from smtpclient.apple (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HqqYb4NlJz2xKV; Thu, 11 Nov 2021 19:12:03 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: Carsten Bormann In-Reply-To: <0360996e-5040-3152-251c-d09139595211@goessner.net> Date: Thu, 11 Nov 2021 19:12:03 +0100 Cc: jsonpath@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <8EFB9969-AB7C-4624-B293-A2E668022EA2@tzi.org> References: <0360996e-5040-3152-251c-d09139595211@goessner.net> To: =?utf-8?Q?Stefan_G=C3=B6ssner?= X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [Jsonpath] Object member names in JSONPath queries ... 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2021 18:12:12 -0000 On 11. Nov 2021, at 19:04, Stefan G=C3=B6ssner = wrote: >=20 > 1. be used explicitly in JSONPath queries only with > - dot-selector > - index-selector > - descendant-selector > - union-selector > 2. be used explicitly specifically in filter-selectors with relative = pathes only with > - dot-selector > - index-selector Why are these two lists different? Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Nov 12 09:17:16 2021 Return-Path: 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 7B6F03A0EB4 for ; Fri, 12 Nov 2021 09:17:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 BouXdgNJxson for ; Fri, 12 Nov 2021 09:17:09 -0800 (PST) Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EA563A0F44 for ; Fri, 12 Nov 2021 09:17:09 -0800 (PST) Received: by mail-wm1-x32e.google.com with SMTP id y196so8298631wmc.3 for ; Fri, 12 Nov 2021 09:17:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=BzoJU9Gm0SC7o7wacRimnEQkvMs3bFOuZ8JTh4bByIo=; b=d9WbibXJ1lHA8XbP7LnhBXGsNN42UKTO703Y8bJCG1qrB/ne6+laFyO4x3sydvrRgQ szj30qEzyIRuRobkMNOq1W5qsbrDFPlxMUItUMfe5+jeD9ixZ9+Eg4pJ0MSPDJedh/9n lc+SSYznvjKP6LAt5qI7+vtBb3QZTp9IT7HaGdMt5h7OqSUePQUMj69eUUkpEfSDBv/k 1BLZi80toAi+hy2EBl1UPnZke+L3TPld/kgvquS/7kztXz0v40zTY5Q9K4pHKd5kuFo6 YwgUwVeC3xjsbTF0JHJbKyMS0ayAo0ETeOg16BcaIQkXLqddPrAMFYWZMsq1hVrfJFNK 1QHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=BzoJU9Gm0SC7o7wacRimnEQkvMs3bFOuZ8JTh4bByIo=; b=lPc1NV6oye7S1DeElsYHdZlloRnapt6T1PbNSc9BqrbD8heQ33S+vbgW6KHtoIcoNE ANObkp8la8vU0PbFSr/IaBewWwGWEnmh1t2z7xc1wS00UrkdvDu8VT7hXOP/qJvUGHme MIsm6+hd/iusIFSjUnxpPe9Jj2304NSeNQM05+KKavZ3hY8+COKpz+Sny0mJXwmFEVFE ih4llvSNudJG96n+uzLYEpnjMuUAHGY37N6lpwj5URrNfkCzNJOQREenQGvzTexqRTjh tK050RfKY3ckGltXR3zDr5oMyW125rJCSwbiMK4DpDXZzwKFOOJRV+SSqZvKHH+15YRP FRSg== X-Gm-Message-State: AOAM533zYf+7XXBsPFaVUuYG+ZQ29KBVMTW1ga68Hc8mdl2Kg4PvVkRF a6scH1ZNVB87cF+l97/TbD235ns+/7PNObK1E+gppuUWIHE= X-Google-Smtp-Source: ABdhPJzS/FsEHTDbMZDrBd3UJNxiAwd3yXMBkvhSnd3hSFNd5umfgwVQYs7K9h8kN0Z81+SEfNv9Av391wPt9hAoyf4= X-Received: by 2002:a1c:4681:: with SMTP id t123mr35963672wma.83.1636737426686; Fri, 12 Nov 2021 09:17:06 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Fri, 12 Nov 2021 12:16:54 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: [Jsonpath] Object member names in JSONPath queries ... 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2021 17:17:14 -0000 > From: "Stefan G=C3=B6ssner" > To: jsonpath@ietf.org > Please can someone enlighten a dump mechanical engineer, what 'projection= ' means in this context. > Regarding the meaning of projection, consider a selector, e.g. '.*', that returns a list of N nodes, node1, ... nodeN. Any subsequent selector will be evaluated against each individual node in the list. So the evaluation of '.*child-selector' will be child-selector(node1), ... child-selector(nodeN). This is referred to as a projection, the selector child-selector is projected onto each node produced by '.*'. Daniel From nobody Sun Nov 14 03:35:25 2021 Return-Path: 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 553923A0788 for ; Sun, 14 Nov 2021 03:35:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 zhstMfkq3-ws for ; Sun, 14 Nov 2021 03:35:20 -0800 (PST) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6B793A07B1 for ; Sun, 14 Nov 2021 03:35:19 -0800 (PST) Received: by mail-ed1-x52f.google.com with SMTP id e3so21859941edu.4 for ; Sun, 14 Nov 2021 03:35:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=u8KxHtn7dJ9R8zdts5q9+LTaDekouaSF0psYQx19FHk=; b=KMSixHlvin6bwaOF4HWLb/43xQvkhZudQUXiwY27TlES7agI30bdfwOS60Pxqiq2gQ N7IET+BCWK39NkMYMhrHv6iurUDAXtq47ZUh54fdcLd9ByyVVGFO5cZLvJ1p+sBabosf 8J6Jbk7kDNZRM/w44WDYCy3cT5POjJ0V5Qo343tRzG4pvHi2xAQORdHlqjtC4caAT1gL H3n+3zF2OBnPXtzhJJ/y7qHLLiW5Sf1o66pGcfNTh2ZwXZOPC8OxAmFP4KH+0HHKSAH0 iKq2dWwxKQvmZv95KHbmX60Y2Di0wd3NuclTuDEPCHQHwxcV7sFD6iQap9nJmwZouK8M pfQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=u8KxHtn7dJ9R8zdts5q9+LTaDekouaSF0psYQx19FHk=; b=MOSSMsAfXJNlghOOV9ZDcBrlzM+at8RS0KIEA9nJTJ+J7jE0et5MYROqgoG+dJRaJj ISuy4IRH04J/Q32+JCl4khMN2e7G4G6LSNiIN+rz4Am468Pg1GCoaUipgoEm4NWNPRO/ MBWaXXVaWvW7YNX5hJxv+lDczvWpUOULwvLEppipGP3ZPl8I7KDPziIoD2vDOHvy49mL Zk6pv5yri7ipej4mGmMjLZDiMgZeb6JFu+0y+10C1Mu4WhVQmyxToEiW4j2+Hlk8xqs1 mZ2ENijqncKuqwfHBTqgiHqgM9X12f/UeQaNgbGj5HwTvwleyVir9egZLPvlNyTVUG+A YYhA== X-Gm-Message-State: AOAM530X+htLmCaOCtfe7+sgc5yiPWl6S+eAdbhYfiOaeN1hY8SXGMv/ 9vx90BTzg1Y6S++BDtDcBiePUlj5qJ3Jfg== X-Google-Smtp-Source: ABdhPJy+OKoOYR8wQlor6Vm6ruSDWTedrJ1ErctiySB92qHAU92LkW8hnqJaP34nRAIonJ9t1q+6Yg== X-Received: by 2002:a05:6402:4412:: with SMTP id y18mr41749045eda.103.1636889716335; Sun, 14 Nov 2021 03:35:16 -0800 (PST) Received: from smtpclient.apple ([2001:984:65b0:2:8ce8:be2d:12a3:b4d9]) by smtp.gmail.com with ESMTPSA id e12sm4911399ejs.86.2021.11.14.03.35.15 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 14 Nov 2021 03:35:16 -0800 (PST) From: James Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Message-Id: <03E1325D-268F-4380-A5D0-F45E2BE61360@gmail.com> Date: Sun, 14 Nov 2021 12:35:15 +0100 To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: [Jsonpath] Draft minutes, consensus points, and actions from IETF 112 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2021 11:35:24 -0000 All, The minutes for our session at IETF 112 are now uploaded to datatracker = here: https://datatracker.ietf.org/doc/minutes-112-jsonpath/ Consensus: * #124 - Won't be used, but can be added in future if there's real = demand * #127 - Won't be included in the specification, but can be part of = extensions * #119 - In boolean contexts, path converts to false if nodelist is = empty, but does not check value(s) * #117 - Normalization not part of spec, codepoint comparison should be = used * #109 - We acknowledge but won't address this issue * #95 - This won't be part of spec as it's an API problem but could be = included in future Outstanding action items that were captured from the meeting: * Draft Status - Tim to make a PR * #127 - Example queries need to be written * #124 - Carsten to comment that consensus is to leave it for an = extension * #123 - Discuss use cases to get consensus of undefined vs NaN on list * #119 - Carsten to make further edits based on consensus * #109 - Carsten to update the issue * #70 - Have discussion on list with known options Please let me know of any omissions or errata. - J= From nobody Sun Nov 14 12:45:09 2021 Return-Path: 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 F2A413A08EA for ; Sun, 14 Nov 2021 12:45:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 o2Y0L7wly5bh for ; Sun, 14 Nov 2021 12:45:02 -0800 (PST) Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 469763A08EB for ; Sun, 14 Nov 2021 12:45:02 -0800 (PST) Received: by mail-wr1-x429.google.com with SMTP id s13so26554949wrb.3 for ; Sun, 14 Nov 2021 12:45:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=KVaWCaIThpHdnBAuya8Ui3eTTKhU0mp2lv0ZNBPqgF0=; b=CYhCeTeQheKaB9XsH/qP0TvKAwb+y5jSovBru9XUVGrC2Dpsb0CdKmlkxLB4N71REP iLQEW4Lx0dLJicaGSRN2AAATNG6fLTd+5gNv80AOx3Mqg5/wvT4yMQaD7QELgEKgLLcP d1mznMtOD3IcOakS+dS8xC9WX+77YFx4AnzKexfeG9ecSEnf9VaP39op850Pjmfz/7nb JKiHiY8D9nQOI8W5Ocd1H5DWIvlxc7Z1oXsHVcNxttGbLjuHYaO5P9kNYnwwEHBUh9jb PomrDamuJU7mWox5PVn3p3PcLSKNg778ZDovyLIWyXZmWNm1ZPB/bsJnzdjWdOGuYvY1 5MAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=KVaWCaIThpHdnBAuya8Ui3eTTKhU0mp2lv0ZNBPqgF0=; b=47j7gEXCGa+pU1Wb9eTjT3OAxx1fhrcl9GTttvDqJylfGHA/Rb+rLY9kWFDqVv7wYF E7Jdxvi4g3sRGatDxxCAmXLXL97ZDk1qQXBWkdQyz0uhyZF2d0xkHVVxIZrq4iLYzS5t e+1KBGgWpz38fSBXglc2Fm8R0pLYhTCbg4Np2toAL/FtL5b8XNcNgMRpzOp9wtQdrw/X xKnhZIGJsL6Y0GoVsoUuhbE03woulfpSs52m69oYVlHKG1xuT5FnXORLJXIa9yKqelH2 6tAh2ACciIIufLLP1eb3yKc7gaaRbI2feuxkZY2JQX3ObJD+j1yPPWpto6gTwmyPjY7s aJjQ== X-Gm-Message-State: AOAM531wUzlBCoU/L5LbEqXmaaBnUweFIW28vFCEOoJRqdSdnCKv6FN/ NE0MjLrMmw8BTYethPhgmWQrIvewWaaqbGhXYiRFWuLeC1Q= X-Google-Smtp-Source: ABdhPJy3w/ESeDD1IXEHlZBxiS3ROCeM7uzgnLrir2oreXlLG+0WabP8PV5lpA7+u1yOf/+dEirn33A3FrsE3JROP7E= X-Received: by 2002:a5d:4ed1:: with SMTP id s17mr40402966wrv.310.1636922695272; Sun, 14 Nov 2021 12:44:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Sun, 14 Nov 2021 15:44:42 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: [Jsonpath] Object member names in JSONPath queries ... 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2021 20:45:07 -0000 > From: Daniel P > > From: "Stefan G=C3=B6ssner" > > > Please can someone enlighten a dump mechanical engineer, what 'projecti= on' means in this context. > > > Regarding the meaning of projection, consider a selector, e.g. '.*', > that returns a list of N nodes, node1, ... nodeN. Any subsequent > selector will be evaluated against each individual node in the list. > So the evaluation of '.*child-selector' will be child-selector(node1), > ... child-selector(nodeN). This is referred to as a projection, the > selector child-selector is projected onto each node produced by '.*'. > Just a follow up, having read the recently distributed minutes on datatracker, I gather this is the context: "Darrel: JMESPath is focused on projections, and JSONPath should focus on selection" Projections in JMESPath are described here https://jmespath.org/tutorial.html#projections and here https://jmespath.org/specification.html#wildcard-expressions. I think _all_ JSONPath selectors may be regarded as having projection semantics in this sense. JMESPath, on the other hand, supports expressions that do _not_ have projection semantics, such as the Pipe Expression, described here, https://jmespath.org/tutorial.html#pipe-expressions. Daniel From nobody Sun Nov 14 13:15:00 2021 Return-Path: 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 094BC3A0784 for ; Sun, 14 Nov 2021 13:14:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 i7EukZVcK_ES for ; Sun, 14 Nov 2021 13:14:53 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77E243A0776 for ; Sun, 14 Nov 2021 13:14:52 -0800 (PST) Received: from [192.168.217.118] (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HslT46dw3z2xrl; Sun, 14 Nov 2021 22:14:48 +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 In-Reply-To: <03E1325D-268F-4380-A5D0-F45E2BE61360@gmail.com> Date: Sun, 14 Nov 2021 22:14:48 +0100 X-Mao-Original-Outgoing-Id: 658617288.448471-672cc44b772be5c810eed94b4b42204e Content-Transfer-Encoding: quoted-printable Message-Id: References: <03E1325D-268F-4380-A5D0-F45E2BE61360@gmail.com> To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: [Jsonpath] #70 Regexps (was: Re: Draft minutes, consensus points, and actions from IETF 112) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2021 21:14:58 -0000 On 2021-11-14, at 12:35, James wrote: >=20 > * #70 - Have discussion on list with known options As a reminder, my slides had these options (renumbered for easier = reference, and expanded a bit): 1. Select (define) one regular expression flavor 2. Provide a way to plug in regular expressions (of different flavors) 3. No regexps in base RFC (but keep an extension point) 1. further splits into: 1a. Select *a version of* ECMAScript (parsing/searching RE) 1b. Select W3C XSD RE (matching RE) 1c. Build "modest subset" (e.g., iregexp) Since we don=E2=80=99t have a consensus or even a majority among the = implementations, we are free to do the right thing, if we can pull that = off. As you know, I have been exploring 1c. I submitted an updated version -01 of draft-bormann-jsonpath-iregexp. As in -00, I=E2=80=99m using W3C XSD RE as a base, as these are actual = regular expressions, amenable to implementation techniques that are less = susceptible to DoS problems than the Perl/PCRE/ECMAscript dialect. Apart from character class subtraction and the exact semantics of = Multi-Character escapes (\s \d \w etc., outside and inside of character = class expressions), W3C XSD RE are pretty much a consensus subset of the = various regular expression dialects, except that they are in the form of = matching expressions (no anchors needed) instead of parsing expressions. = =20 I believe the spec should have conversion instructions for implementers = that just want to use the regexp engine they happen to have handy. = Because of the consensus subset nature of W3C XSD RE, these instructions = are relatively straightforward (copy, and surround by the anchors the = target flavor happens to use). I tried to add conversion instructions for Multi-Character escapes (\s = \d \w and \S \D \W, leaving out the \c and \i that nobody except W3C = has). As you can see when looking at the diff, the result is not pretty when = it comes to double negation in character classes. Maybe a pathological = case, but a bit of a trap, and maybe not that useful anyway as the W3C = semantics is quite different from the PCRE ones. So I=E2=80=99m leaning towards a -02 that does not have Multi-Character = escapes. (None of the regexps I found in RFCs uses them, and not having them also = happens to be pretty much what the json-schema.org drafts seem to = converge at.) Gr=C3=BC=C3=9Fe, Carsten Status: = https://datatracker.ietf.org/doc/draft-bormann-jsonpath-iregexp/ Html: = https://www.ietf.org/archive/id/draft-bormann-jsonpath-iregexp-01.html Diff: = https://www.ietf.org/rfcdiff?url2=3Ddraft-bormann-jsonpath-iregexp-01 From nobody Sun Nov 14 13:20:38 2021 Return-Path: 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 D77933A0817 for ; Sun, 14 Nov 2021 13:20:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20210112.gappssmtp.com 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 DPhBXD8JLdW8 for ; Sun, 14 Nov 2021 13:20:32 -0800 (PST) Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C970E3A0811 for ; Sun, 14 Nov 2021 13:20:31 -0800 (PST) Received: by mail-lj1-x232.google.com with SMTP id k2so23577482lji.4 for ; Sun, 14 Nov 2021 13:20:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=025sjQjQbw7K6/kbs+9vbO4hYMdR11PJzkJLCHzAJ8A=; b=FYr8LqKtY8vZkUYWXCp6gysEt34m6bLkRgWGZx04teX7dtPipx9NziWoK3OlxJvVHq MLSf70paKp/KHsaVcAl4aXMAW7n/QbxddZh43lXhoYI40QMdVy8Uj4H3imoDnV237hRP 4OL2lAKuwDUJhngsanjQ4QaYcgWFVJ0rH3GHlbEWcTAUwR+8XoQxWJNBKEXLT7zvInXV mInvGmddpZP9dQwJAMRKFijWB22qjox9RnehsuVcOUPpnhUfzx40dMBb84zhqKXFLYnl IZyx4lo+lRScH53ZIzhyJhfcojYB1PZsQbaOxihR8nDuh5GEJtGAvozs8pWsmi1LUJCo vhDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=025sjQjQbw7K6/kbs+9vbO4hYMdR11PJzkJLCHzAJ8A=; b=22y5y/Hl9bFIX4UB+8//XAHFTOb7FCzIFvoA+uJo8ipgS1rkXDtglfdbqT1DJwSXXm DUJUBPdVb3jq1XuqNivUhiT7qxQEAcbfTFcOikTuxlYz9Z6XupMnyAYFJg/Ejbgg6u7w FpgjryLrWfaRmGTDkZKaehLfCYPJb6kamgfLJ77FS0Z1pSe/pW5SNMrJGgbhD7s/zh+i KKHZp22Zxb7WVw4N9FG053VF5q2S7nzr616rUDm30hjIh3KSQrVv2hR9N+Bt1dwAIy7a wO+UeyMKPTa1L3jiMBltdW9l5Biz547qWeK4NvIb7P/+k4MSWf5g7CI177NZgSbgeAsE SiZA== X-Gm-Message-State: AOAM530x9D+zCq6NI3mYwy+uv6JV5uaORjB5WFZM9z5gnwX37d8BpcaR oHrlvBYgvwR94QszoXpkw4f2Fh8Hx967s/8AR4WW/A== X-Google-Smtp-Source: ABdhPJyy7uqXBtTy3imj8WvVC8uG/5JvdfTFrf4cywWGyCL6Brx/FJ8oESy+aJwIkeJfcu57koK1TSeZCMj8kXBvGu4= X-Received: by 2002:a05:651c:1256:: with SMTP id h22mr34359333ljh.269.1636924828143; Sun, 14 Nov 2021 13:20:28 -0800 (PST) MIME-Version: 1.0 References: <03E1325D-268F-4380-A5D0-F45E2BE61360@gmail.com> In-Reply-To: From: Tim Bray Date: Sun, 14 Nov 2021 13:20:16 -0800 Message-ID: To: Carsten Bormann , Francesca Palombini Cc: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000e7e1b305d0c642a6" Archived-At: Subject: Re: [Jsonpath] #70 Regexps (was: Re: Draft minutes, consensus points, and actions from IETF 112) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2021 21:20:37 -0000 --000000000000e7e1b305d0c642a6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I suspect that we are not the only WG, in the present or the future, who need to/will need to address this issue. I suggest that we should take this to ietf@ or ask the IESG if they have an opinion. Francesca, do you have any thoughts? On Sun, Nov 14, 2021 at 1:15 PM Carsten Bormann wrote: > On 2021-11-14, at 12:35, James wrote: > > > > * #70 - Have discussion on list with known options > > As a reminder, my slides had these options (renumbered for easier > reference, and expanded a bit): > > 1. Select (define) one regular expression flavor > 2. Provide a way to plug in regular expressions (of different flavors) > 3. No regexps in base RFC (but keep an extension point) > > 1. further splits into: > > 1a. Select *a version of* ECMAScript (parsing/searching RE) > 1b. Select W3C XSD RE (matching RE) > 1c. Build "modest subset" (e.g., iregexp) > > Since we don=E2=80=99t have a consensus or even a majority among the > implementations, we are free to do the right thing, if we can pull that o= ff. > > As you know, I have been exploring 1c. > > I submitted an updated version -01 of draft-bormann-jsonpath-iregexp. > As in -00, I=E2=80=99m using W3C XSD RE as a base, as these are actual re= gular > expressions, amenable to implementation techniques that are less > susceptible to DoS problems than the Perl/PCRE/ECMAscript dialect. > > Apart from character class subtraction and the exact semantics of > Multi-Character escapes (\s \d \w etc., outside and inside of character > class expressions), W3C XSD RE are pretty much a consensus subset of the > various regular expression dialects, except that they are in the form of > matching expressions (no anchors needed) instead of parsing expressions. > > I believe the spec should have conversion instructions for implementers > that just want to use the regexp engine they happen to have handy. Becau= se > of the consensus subset nature of W3C XSD RE, these instructions are > relatively straightforward (copy, and surround by the anchors the target > flavor happens to use). > > I tried to add conversion instructions for Multi-Character escapes (\s \d > \w and \S \D \W, leaving out the \c and \i that nobody except W3C has). > As you can see when looking at the diff, the result is not pretty when it > comes to double negation in character classes. Maybe a pathological case= , > but a bit of a trap, and maybe not that useful anyway as the W3C semantic= s > is quite different from the PCRE ones. > So I=E2=80=99m leaning towards a -02 that does not have Multi-Character e= scapes. > (None of the regexps I found in RFCs uses them, and not having them also > happens to be pretty much what the json-schema.org drafts seem to > converge at.) > > Gr=C3=BC=C3=9Fe, Carsten > > Status: https://datatracker.ietf.org/doc/draft-bormann-jsonpath-iregexp= / > Html: > https://www.ietf.org/archive/id/draft-bormann-jsonpath-iregexp-01.html > Diff: > https://www.ietf.org/rfcdiff?url2=3Ddraft-bormann-jsonpath-iregexp-01 > > -- > JSONpath mailing list > JSONpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > --000000000000e7e1b305d0c642a6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I s= uspect that we are not the only WG, in the present or the future, who need = to/will need to address this issue.=C2=A0 I suggest that we should take thi= s to ietf@ or ask the IESG if they have an opinion.=C2=A0 Francesca, do you= have any thoughts?

On Sun, Nov 14, 2021 at 1:15 PM Carsten Bormann &l= t;cabo@tzi.org> wr= ote:
On 2021-11-14, at 12:35, James <james.ietf@gmail.com= > wrote:
>
> * #70 - Have discussion on list with known options

As a reminder, my slides had these options (renumbered for easier reference= , and expanded a bit):

1. Select (define) one regular expression flavor
2. Provide a way to plug in regular expressions (of different flavors)
3. No regexps in base RFC (but keep an extension point)

1. further splits into:

1a. Select *a version of* ECMAScript (parsing/searching RE)
1b. Select W3C XSD RE (matching RE)
1c. Build "modest subset" (e.g., iregexp)

Since we don=E2=80=99t have a consensus or even a majority among the implem= entations, we are free to do the right thing, if we can pull that off.

As you know, I have been exploring 1c.

I submitted an updated version -01 of draft-bormann-jsonpath-iregexp.
As in -00, I=E2=80=99m using W3C XSD RE as a base, as these are actual regu= lar expressions, amenable to implementation techniques that are less suscep= tible to DoS problems than the Perl/PCRE/ECMAscript dialect.

Apart from character class subtraction and the exact semantics of Multi-Cha= racter escapes (\s \d \w etc., outside and inside of character class expres= sions), W3C XSD RE are pretty much a consensus subset of the various regula= r expression dialects, except that they are in the form of matching express= ions (no anchors needed) instead of parsing expressions.=C2=A0

I believe the spec should have conversion instructions for implementers tha= t just want to use the regexp engine they happen to have handy.=C2=A0 Becau= se of the consensus subset nature of W3C XSD RE, these instructions are rel= atively straightforward (copy, and surround by the anchors the target flavo= r happens to use).

I tried to add conversion instructions for Multi-Character escapes (\s \d \= w and \S \D \W, leaving out the \c and \i that nobody except W3C has).
As you can see when looking at the diff, the result is not pretty when it c= omes to double negation in character classes.=C2=A0 Maybe a pathological ca= se, but a bit of a trap, and maybe not that useful anyway as the W3C semant= ics is quite different from the PCRE ones.
So I=E2=80=99m leaning towards a -02 that does not have Multi-Character esc= apes.
(None of the regexps I found in RFCs uses them, and not having them also ha= ppens to be pretty much what the json-schema.org drafts seem to converge a= t.)

Gr=C3=BC=C3=9Fe, Carsten

Status:=C2=A0 =C2=A0https://datatrac= ker.ietf.org/doc/draft-bormann-jsonpath-iregexp/
Html:=C2=A0 =C2=A0 =C2=A0https= ://www.ietf.org/archive/id/draft-bormann-jsonpath-iregexp-01.html
Diff:=C2=A0 =C2=A0 =C2=A0https:= //www.ietf.org/rfcdiff?url2=3Ddraft-bormann-jsonpath-iregexp-01

--
JSONpath mailing list
JSONpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath
--000000000000e7e1b305d0c642a6-- From nobody Sun Nov 14 14:11:02 2021 Return-Path: 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 6FBA93A09EA for ; Sun, 14 Nov 2021 14:11:00 -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_H3=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 B-g7mX5oKWyA for ; Sun, 14 Nov 2021 14:10:56 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFDF43A09E9 for ; Sun, 14 Nov 2021 14:10:55 -0800 (PST) Received: from [192.168.217.118] (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Hsmjn0HPRz2xqf; Sun, 14 Nov 2021 23:10:53 +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 In-Reply-To: Date: Sun, 14 Nov 2021 23:10:52 +0100 Cc: Francesca Palombini , jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 658620652.676311-4d2d211f9f7e7f11988375491e431a63 Content-Transfer-Encoding: quoted-printable Message-Id: References: <03E1325D-268F-4380-A5D0-F45E2BE61360@gmail.com> To: Tim Bray X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] #70 Regexps (was: Re: Draft minutes, consensus points, and actions from IETF 112) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2021 22:11:01 -0000 On 2021-11-14, at 22:20, Tim Bray wrote: >=20 > I suspect that we are not the only WG, in the present or the future, = who need to/will need to address this issue. I suggest that we should = take this to ietf@ or ask the IESG if they have an opinion. =20 This is not a new subject to the IETF=E2=80=A6 The two specifications that already use regexps I am most familiar with = are YANG and CDDL (*); both use W3C XSD REs. Defining a useful subset = that is easy to implement (e.g., based on conversion instructions to = popular dialects) would benefit both ecosystems. I=E2=80=99m not sure ietf@ is the right place to bring this up. dispatch@ is closer (we could also start at art@). It is probably best to move the discussion over there when we have a = reasonably solid proposal; I don=E2=80=99t think asking the question in = a vacuum will be productive. So I think we should first try to do what is good for jsonpath, maybe = check next with cbor@ and netmod@ (the people who do YANG) whether we = have missed anything that would allow them to just adopt (in the English = sense) our result, and then maybe ask at dispatch@ whether they see a = problem with completing this spec in the jsonpath WG (which might bring = us a few new faces =E2=80=94 I don=E2=80=99t think that could hurt). > Francesca, do you have any thoughts? Listening attentively... Gr=C3=BC=C3=9Fe, Carsten (*) (Of course, there are NAPTRs, which use POSIX ERE for a transformation = (replacement) operation. OpenPGP uses "the same syntax as the Henry Spencer's "almost public = domain" regular expression [REGEX] package.=E2=80=9D, but then goes on = to define a iregexp-like subset with anchors. Various documents use regular expressions as a specification technique; = these usually point to POSIX but then use an iregexp-like subset; e.g., = RFC 7970. RFC 4730 goes as far as defining a specific regexp dialect for dialing = digit sequences, DRegEx. I don=E2=80=99t think any of these are strongly related to the matching = regexp intention of JSONpath, CDDL, or YANG.) From nobody Tue Nov 16 09:38:41 2021 Return-Path: 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 735B33A00B1 for ; Tue, 16 Nov 2021 09:38:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 Gh1pFSbF9G4z for ; Tue, 16 Nov 2021 09:38:35 -0800 (PST) Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 168D13A0061 for ; Tue, 16 Nov 2021 09:38:35 -0800 (PST) Received: by mail-pf1-x429.google.com with SMTP id z6so43793pfe.7 for ; Tue, 16 Nov 2021 09:38:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to:cc; bh=3sDgZpyDdKY79Pj5riyaYc67028oFXwfHXyl0+7JsbE=; b=dcyG8/19p3RqRmK8G7aSv5xSgJCsdxGXxX3Nw/pF4R/6JvIrYc2eQ3nQriPWB1R8Za MtBJLglgPP2thkquC0uBwhB6Fg6cxD/cHX7hTv5M0bWejruDD28brJbd9U8JgM2m4ai4 qlAYikILVES3Zn223mwaBnIPuBpy6rV/e+/dFKUiuvLhxaiNairdvqELSqQMRdpGigLW YY+QdvM4OEt3zYKPvd+u/sxO88wXMXpr/yVkfRJKIRj9FxPBA+SLiF9n2PAmFRnI+Xq3 GsNsYzhmNOUAFTiM+Wmc7jDCTOxMyLKP95+HVHIvdjtY+YWlgz3RCQgV7ShWKbn/oTsu 2X8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=3sDgZpyDdKY79Pj5riyaYc67028oFXwfHXyl0+7JsbE=; b=GxCRH4pEceUja+m0S/4paMUHVJo2G+ixu8V4tP9Y8EzlYC1xbzqvDlCSuUbPtx3vgw gQWftyAqne6iB4WuUADuSh/p1DpA9jnpSiehLIWwUPI5d5NsXL/RqfYLoAyM81qb7uYR yhM5LqKyImY2GErtSthUhX1lQNxewrgNpBH36F0B0OcHrR/aUgrjwxa/5Ph2hZQII73I ChPX1YRAVNQNRAUv314KWEjiiZSi3v7vaHAZWzgMYx3fvEcvJnr6etfQXWyjmHF8m8r/ KDfFUQeC3AmqI+NE/xSKItnGlfp9Ip79dhw3iSdFoNn8v5XZHnOCpHguSbng8AIelX5H Vgdw== X-Gm-Message-State: AOAM530M1BDBgRy+bzKIj3eYAY5tJ0Ve0aymwNzg95rzht59VEWsi4Tc 7iigKmOB1hj0Hg95qGSoZb61P09QvfDt+LsgFc/56dmX X-Google-Smtp-Source: ABdhPJxZlbFCh6C21ylUFJ/nnx2hXWqA1gFk/J08OC4R4Qn36Aq9lylT4mjxIlhZ/KNHolla/Vjwi6+CHwdFWWBreUs= X-Received: by 2002:a65:5a8d:: with SMTP id c13mr512434pgt.228.1637084313125; Tue, 16 Nov 2021 09:38:33 -0800 (PST) MIME-Version: 1.0 From: Glyn Normington Date: Tue, 16 Nov 2021 17:38:22 +0000 Message-ID: To: Carsten Bormann Cc: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000f3861305d0eb64d4" Archived-At: Subject: [Jsonpath] Templating regexps (was: Re: #70 Regexps (was: Re: Draft minutes, consensus points, and actions from IETF 112)) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2021 17:38:40 -0000 --000000000000f3861305d0eb64d4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > 2. Provide a way to plug in regular expressions (of different flavors) Let's explore the above option a little further in this separate thread. If we defined a general way of using jsonpath with a variety of regexp specs -- basically just ensuring that we can parse a filter's regexps without consuming more of the surrounding jsonpath than we should --, then jsonpath would effectively become a template for concrete specifications such as jsonpath/iregexp, jsonpath/RE2, etc. This would break the dependency between the jsonpath spec and completion of iregexp, allowing jsonpath to complete early. It would also allow the iregexp spec to be revised without having to revise the jsonpath spec. Another advantage is that it would reduce the cost of implementation in some cases and thereby increase the adoption of the jsonpath spec. Our ultimate, interoperable recommendation could still end up being jsonpath/iregexp, once iregexp is finished. We could do this either by recommending (or mandating) jsonpath/iregexp in a second version of the jsonpath spec or we could publish a separate spec tying the two together. The main problem with this template approach is the reduction in interoperability among implementations which choose distinct regexp specs. But an advantage for implementers is that they could simply choose the most convenient regexp implementation, not have to perform any mapping (which would include possibly onerous test writing), and get good interoperation with other jsonpath implementations which make the same choice. I think this would increase the adoption of jsonpath among implementers. Another problem with the template approach is that implementers may be tempted to plug in a convenient regexp implementation without a decent spec. This would make using that combination more difficult (because of the need for guesswork on regexp details) and could further limit interoperation. Admittedly, this option has several disadvantages, but I don't think we should necessarily discount it, especially as a stepping-stone to our final destination. On Sun, 14 Nov 2021 at 21:15, Carsten Bormann wrote: > On 2021-11-14, at 12:35, James wrote: > > > > * #70 - Have discussion on list with known options > > As a reminder, my slides had these options (renumbered for easier > reference, and expanded a bit): > > 1. Select (define) one regular expression flavor > 2. Provide a way to plug in regular expressions (of different flavors) > 3. No regexps in base RFC (but keep an extension point) > > 1. further splits into: > > 1a. Select *a version of* ECMAScript (parsing/searching RE) > 1b. Select W3C XSD RE (matching RE) > 1c. Build "modest subset" (e.g., iregexp) > > Since we don=E2=80=99t have a consensus or even a majority among the > implementations, we are free to do the right thing, if we can pull that o= ff. > > As you know, I have been exploring 1c. > > I submitted an updated version -01 of draft-bormann-jsonpath-iregexp. > As in -00, I=E2=80=99m using W3C XSD RE as a base, as these are actual re= gular > expressions, amenable to implementation techniques that are less > susceptible to DoS problems than the Perl/PCRE/ECMAscript dialect. > > Apart from character class subtraction and the exact semantics of > Multi-Character escapes (\s \d \w etc., outside and inside of character > class expressions), W3C XSD RE are pretty much a consensus subset of the > various regular expression dialects, except that they are in the form of > matching expressions (no anchors needed) instead of parsing expressions. > > I believe the spec should have conversion instructions for implementers > that just want to use the regexp engine they happen to have handy. Becau= se > of the consensus subset nature of W3C XSD RE, these instructions are > relatively straightforward (copy, and surround by the anchors the target > flavor happens to use). > > I tried to add conversion instructions for Multi-Character escapes (\s \d > \w and \S \D \W, leaving out the \c and \i that nobody except W3C has). > As you can see when looking at the diff, the result is not pretty when it > comes to double negation in character classes. Maybe a pathological case= , > but a bit of a trap, and maybe not that useful anyway as the W3C semantic= s > is quite different from the PCRE ones. > So I=E2=80=99m leaning towards a -02 that does not have Multi-Character e= scapes. > (None of the regexps I found in RFCs uses them, and not having them also > happens to be pretty much what the json-schema.org drafts seem to > converge at.) > > Gr=C3=BC=C3=9Fe, Carsten > > Status: https://datatracker.ietf.org/doc/draft-bormann-jsonpath-iregexp= / > Html: > https://www.ietf.org/archive/id/draft-bormann-jsonpath-iregexp-01.html > Diff: > https://www.ietf.org/rfcdiff?url2=3Ddraft-bormann-jsonpath-iregexp-01 > > -- > JSONpath mailing list > JSONpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > --000000000000f3861305d0eb64d4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> 2. Provide a way to plug in reg= ular expressions (of different flavors)

Let's = explore the above option a little further in this separate thread.

If we defined a general way of using jsonpath with a v= ariety of regexp specs -- basically just ensuring that we can parse a filte= r's regexps without consuming more of the surrounding jsonpath than we = should --, then jsonpath would effectively become a template for concrete s= pecifications such as jsonpath/iregexp, jsonpath/RE2, etc.

This would break the dependency between the jsonpath spec and comp= letion of iregexp, allowing jsonpath to complete early. It would also allow= the iregexp spec to be revised without having to revise the jsonpath spec.= Another advantage is that it would reduce the cost of implementation in so= me cases and thereby increase the adoption of the jsonpath spec.
<= div>
Our ultimate, interoperable recommendation could still e= nd up being jsonpath/iregexp, once iregexp is finished. We could do this ei= ther by recommending (or mandating) jsonpath/iregexp in a second version of= the jsonpath spec or we could publish a separate spec tying the two togeth= er.

The main problem with this template approa= ch is the reduction in interoperability among implementations which choose = distinct regexp specs. But an advantage for implementers is that they could= simply choose the most convenient regexp implementation, not have to perfo= rm any mapping (which would include possibly onerous test writing), and get= good interoperation with other jsonpath implementations which make the sam= e choice. I think this would increase the adoption of jsonpath among implem= enters.

Another problem with the template approach= is that implementers may be tempted to plug in a convenient regexp impleme= ntation without a decent spec. This would make using that combination more = difficult (because of the need for guesswork on regexp details) and could f= urther limit interoperation.

Admittedly, this opti= on has several disadvantages, but I don't think we should necessarily d= iscount it, especially as a stepping-stone to our final destination.

On Sun, 14 Nov 2021 at 21:15, Carsten Bormann <cabo@tzi.org> wrote:
<= /div>
On 2021-11-14, at 12= :35, James <ja= mes.ietf@gmail.com> wrote:
>
> * #70 - Have discussion on list with known options

As a reminder, my slides had these options (renumbered for easier reference= , and expanded a bit):

1. Select (define) one regular expression flavor
2. Provide a way to plug in regular expressions (of different flavors)
3. No regexps in base RFC (but keep an extension point)

1. further splits into:

1a. Select *a version of* ECMAScript (parsing/searching RE)
1b. Select W3C XSD RE (matching RE)
1c. Build "modest subset" (e.g., iregexp)

Since we don=E2=80=99t have a consensus or even a majority among the implem= entations, we are free to do the right thing, if we can pull that off.

As you know, I have been exploring 1c.

I submitted an updated version -01 of draft-bormann-jsonpath-iregexp.
As in -00, I=E2=80=99m using W3C XSD RE as a base, as these are actual regu= lar expressions, amenable to implementation techniques that are less suscep= tible to DoS problems than the Perl/PCRE/ECMAscript dialect.

Apart from character class subtraction and the exact semantics of Multi-Cha= racter escapes (\s \d \w etc., outside and inside of character class expres= sions), W3C XSD RE are pretty much a consensus subset of the various regula= r expression dialects, except that they are in the form of matching express= ions (no anchors needed) instead of parsing expressions.=C2=A0

I believe the spec should have conversion instructions for implementers tha= t just want to use the regexp engine they happen to have handy.=C2=A0 Becau= se of the consensus subset nature of W3C XSD RE, these instructions are rel= atively straightforward (copy, and surround by the anchors the target flavo= r happens to use).

I tried to add conversion instructions for Multi-Character escapes (\s \d \= w and \S \D \W, leaving out the \c and \i that nobody except W3C has).
As you can see when looking at the diff, the result is not pretty when it c= omes to double negation in character classes.=C2=A0 Maybe a pathological ca= se, but a bit of a trap, and maybe not that useful anyway as the W3C semant= ics is quite different from the PCRE ones.
So I=E2=80=99m leaning towards a -02 that does not have Multi-Character esc= apes.
(None of the regexps I found in RFCs uses them, and not having them also ha= ppens to be pretty much what the json-schema.org drafts seem to converge a= t.)

Gr=C3=BC=C3=9Fe, Carsten

Status:=C2=A0 =C2=A0https://datatrac= ker.ietf.org/doc/draft-bormann-jsonpath-iregexp/
Html:=C2=A0 =C2=A0 =C2=A0https= ://www.ietf.org/archive/id/draft-bormann-jsonpath-iregexp-01.html
Diff:=C2=A0 =C2=A0 =C2=A0https:= //www.ietf.org/rfcdiff?url2=3Ddraft-bormann-jsonpath-iregexp-01

--
JSONpath mailing list
JSONpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath
--000000000000f3861305d0eb64d4-- From nobody Sun Nov 28 16:08:38 2021 Return-Path: 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 3142A3A09F4 for ; Sun, 28 Nov 2021 16:08:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 p77tx1hV2PbD for ; Sun, 28 Nov 2021 16:08:32 -0800 (PST) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC5C53A09F6 for ; Sun, 28 Nov 2021 16:08:29 -0800 (PST) Received: from [192.168.217.118] (p5089a436.dip0.t-ipconnect.de [80.137.164.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4J2Qft1XqVz2xdr; Mon, 29 Nov 2021 01:08:22 +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 In-Reply-To: <03E1325D-268F-4380-A5D0-F45E2BE61360@gmail.com> Date: Mon, 29 Nov 2021 01:08:21 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 659837301.744054-4f2283993e367fc7172dedf3e5c3b0cd Content-Transfer-Encoding: quoted-printable Message-Id: <6205D3F4-C144-47EC-BEAD-C84B0ABF76AE@tzi.org> References: <03E1325D-268F-4380-A5D0-F45E2BE61360@gmail.com> To: James X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] Draft minutes, consensus points, and actions from IETF 112 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2021 00:08:36 -0000 I have not forgotten these action points, but I actually first created a = pull request based on Michael McCool=E2=80=99s comments: https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/pull/137 I have structured this into multiple commits in case we can=E2=80=99t = merge all of this immediately. New (somewhat) technical content: * The text is now using I-JSON (RFC 7493) to discuss integer number = value ranges. This removes some weasel wording that is likely to cause interop = issues. * Some of the text about false/truthy is gone, some more changes will be = needed. * The text about negative indexes is now less misleading. There is also a little markdown adjustment, and a lot of editorial = fixes. Thanks to Michael for the review! Gr=C3=BC=C3=9Fe, Carsten > On 2021-11-14, at 12:35, James wrote: >=20 > All, >=20 > The minutes for our session at IETF 112 are now uploaded to = datatracker here: >=20 > https://datatracker.ietf.org/doc/minutes-112-jsonpath/ >=20 > Consensus: >=20 > * #124 - Won't be used, but can be added in future if there's real = demand > * #127 - Won't be included in the specification, but can be part of = extensions > * #119 - In boolean contexts, path converts to false if nodelist is = empty, but does not check value(s) > * #117 - Normalization not part of spec, codepoint comparison should = be used > * #109 - We acknowledge but won't address this issue > * #95 - This won't be part of spec as it's an API problem but could be = included in future >=20 > Outstanding action items that were captured from the meeting: >=20 > * Draft Status - Tim to make a PR > * #127 - Example queries need to be written > * #124 - Carsten to comment that consensus is to leave it for an = extension > * #123 - Discuss use cases to get consensus of undefined vs NaN on = list > * #119 - Carsten to make further edits based on consensus > * #109 - Carsten to update the issue > * #70 - Have discussion on list with known options >=20 > Please let me know of any omissions or errata. >=20 > - J From nobody Mon Nov 29 00:01:56 2021 Return-Path: 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 538583A0AD9 for ; Mon, 29 Nov 2021 00:01:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 ywz-qadIUHZJ for ; Mon, 29 Nov 2021 00:01:49 -0800 (PST) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F1D03A0332 for ; Mon, 29 Nov 2021 00:01:49 -0800 (PST) Received: by mail-ed1-x52e.google.com with SMTP id t5so68293706edd.0 for ; Mon, 29 Nov 2021 00:01:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=8lCmrv0Xb9RNd8+aa8xhZbbGTV3rH1xfpvyKS6Hf6No=; b=JcavYl2QHW2JpRXMP2BmGXLNC1aLI4N8Zn5yz0f+TDHikdxYJcjRWf4RIWGelXRzOG aJb7LixQ5dP6E77zsTCpO47G1nHWnWnHAF1S1Kkf3tRjRM3/jPst/WKMSVD5kQPgj8Zb ENeAsomnUY8rKGNKb09OjSCVpS7HYDkb+zVfVrx1OVMYifP0CVdbs7Ixg2ToTi7NnoPS ffLr99WIn4YsLycP2MtqOSfHFYRabMzt9VYxEWFnD1M290S30haJim/BxQfNTDFFpi0p PfDn73il6O7YOEaYvD8ePXLUoqeZd9dAeXsukdSY0sdfTf62xDfmT9peKPDEZPcOrWph u5Nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=8lCmrv0Xb9RNd8+aa8xhZbbGTV3rH1xfpvyKS6Hf6No=; b=2EJ9FrTVkUMFGdhZ8TOyjvDHi08JK+pqDbYskyJZ/EH2uFN3HI+KAaW8vBsr/Er/W2 A+ptoA8e+6bcrQTKOsdO91b0ASJvjk7AN8c4hVzCbZDFRDrBYJBDTUG3p0J0Uth8TmO0 E11jnQSHWhKl6nUlWvci372TVeDcAz6nfWIERyyzzcILVOqTTHdj9Hujirrk1m/SmAcs NhbP0svZrVqpfmZxhDPo6gg2/Ce1z0VgWlrQlh1MEG6jqlQdXQNH18LMNP5R5oOhmC66 s0eFwOTxV4C2uHauQAVyjJAZfCJCQb5ZZ6mlYxrT8UNekY7jgUGDD02j/uJhNj4yd9E1 3Szw== X-Gm-Message-State: AOAM530VqfxX/q9nhV+mQIDTA6n0DHpj4HvQwz/KdZXf/1OQOr48HUHq fIkhx7vJj66HGqs8Q0/F5f/WMbOUFOxC7w== X-Google-Smtp-Source: ABdhPJwPP9DJdYgu1zkphEMNebdd0SVFhfxaBoJSIt5w6zpPWsM8aqqDwnW55wooIZnoShl8FkP/Eg== X-Received: by 2002:a05:6402:26d4:: with SMTP id x20mr72484003edd.119.1638172905908; Mon, 29 Nov 2021 00:01:45 -0800 (PST) Received: from smtpclient.apple ([2001:984:65b0:2:e8f8:4384:d6c7:f17a]) by smtp.gmail.com with ESMTPSA id qf9sm7455512ejc.18.2021.11.29.00.01.45 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Nov 2021 00:01:45 -0800 (PST) From: James G Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.20.0.1.32\)) Date: Mon, 29 Nov 2021 09:01:45 +0100 References: To: jsonpath@ietf.org In-Reply-To: Message-Id: <1FCC9B49-FCB1-44E0-B121-AD222B6C955D@gmail.com> X-Mailer: Apple Mail (2.3693.20.0.1.32) Archived-At: Subject: Re: [Jsonpath] January 2022 interim meeting poll 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2021 08:01:55 -0000 If you haven't already added your availability to the poll for our = January interim, this is a gentle reminder to please do so. I'll close the poll this Friday the 3rd, in the case of a tie the = earliest date will be chosen. Thanks James > On 11 Nov 2021, at 10:38, James wrote: >=20 > Thank you to everyone who attended our very productive session at IETF = 112. I'll be sending out notes and action items to the list in a few = days once the dust settles. >=20 > We're now looking to schedule our next interim meeting in January, = starting Monday the 17th. If this isn=E2=80=99t feasible for you, please = let us know and we can discuss or expand the polling. >=20 > The poll is here https://doodle.com/poll/2yhfunacqxtcyrqa and we'll = close it in a few weeks time based on people's responses. >=20 > Thanks >=20 > Tim & James > JSONPath Chairs