From nobody Tue Mar 2 02:01:33 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 593E73A14C8 for ; Tue, 2 Mar 2021 02:01:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.92 X-Spam-Level: X-Spam-Status: No, score=-1.92 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] 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 aXZLPsUYAIVh for ; Tue, 2 Mar 2021 02:01:30 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2658F3A16D2 for ; Tue, 2 Mar 2021 02:00:51 -0800 (PST) Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DqXh04ZmmzyXT; Tue, 2 Mar 2021 11:00:48 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: <473018687.319278.1614458246139@mail.yahoo.com> Date: Tue, 2 Mar 2021 11:00:48 +0100 Cc: Glyn Normington , jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 636372048.185127-e484bdd98ff641c6e97bc30f5921fc41 Content-Transfer-Encoding: quoted-printable Message-Id: <2E02A243-A104-4502-AB64-4B8228278126@tzi.org> References: <98ed1a4f-82fd-3f94-a707-8569f89a5041@goessner.net> <502566941.150044.1614366732927@mail.yahoo.com> <280EE68C-F1A7-4863-8F5F-7F544F431973@tzi.org> <350059548.134171.1614369123233@mail.yahoo.com> <1576492499.98241.1614369511559@mail.yahoo.com> <1157333423.170620.1614370476963@mail.yahoo.com> <93F527B6-CC03-475D-93E1-AAC9CEB4B5A8@tzi.org> <2126411059.183763.1614375732675@mail.yahoo.com> <83EA4040-0E7D-4DDB-AF2C-DD8DD59B22B3@tzi.org> <380AD158-6728-4289-BEA2-61121E2A5EA2@tzi.org> <473018687.319278.1614458246139@mail.yahoo.com> To: Greg Dennis X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] Some Comments ... 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 Mar 2021 10:01:32 -0000 I must say I like the stream of pointers to stack overflow discussions = that I can see on slack. That is certainly a nice service. Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Mar 2 02:01:57 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 3C05A3A14C9 for ; Tue, 2 Mar 2021 02:01:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.099 X-Spam-Level: X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, 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 TZjceTOm5KZe for ; Tue, 2 Mar 2021 02:01:55 -0800 (PST) Received: from sonic315-15.consmr.mail.bf2.yahoo.com (sonic315-15.consmr.mail.bf2.yahoo.com [74.6.134.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 CA8F23A14C5 for ; Tue, 2 Mar 2021 02:01:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614679313; bh=TRv1Tkmjp+gfm3u8oAeFQgPYNKiDEahuf9feeCUvG44=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=LegZPEwSACXDbXpCvF0MK22eLJteuQr9bGC/0jmz6Knt9OscoruOnCOyHI+8sTbMCEoJkkWqsv7Mz40of3nNhJu7xtD4tIZ1cRSM9evD1m+aNEbDfh33jPPL6xebqDbv1aBfpoX0JQ/SB9/Nm4Zh2swayzvbA/PdwAxeY7h9BFOO5qRDmaso9pbfeHlxYhg/qLzfYDLH8uE8z979Tt0Vc1yXoN7Fv9zh/lUi605O3kbpA+bsP/RfyRXWB6S3yovXSUdfTtqbsroj/A2d1qSykAZYkIgHJzcFZdBOB0BOjbpilcZmzfYoQNaN6Iei14KvnlZkkQ+90yVwDamj0oAPZQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614679313; bh=PltVnNKr6pVKZ46XYyJVTYpMIG9Kt79k+hqyTwzk2+J=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=CfBCIi2ivOlos7kD7HeFa/WQn0b6UIW2dpqreGHGJ0+Sw+YAdqUoCOuJw7wgZuMKoPLG0yOWPKDgHPJDNkqoLXO83KGD04swrzjhPiHjMyEi8pcIDUCfaLlV2SbOlbksQaGCFQInbOAGCk5QmtMOLl73RE+ppAIcXSxTcapLpoMOs1ybA7BJojasN9rHb/iPUgDM2Xpft2GSIq2dbujo2HkGvOPgULSRJaf6mqB7QMc1m59rG1DEQoIK3kglvUevSHh8b3L0FrCEOYvdzVMrNDuokTx+MpW+Gvoxii4rrm+3dtkxJ5hzHmmLIzk6p1QMqiX+rBVLzdDvhJ1nGPiTxQ== X-YMail-OSG: HaoBf8YVM1nUWBSmSPgSUPgmFywkw5NbaB2FitHymCPid86wbixd2uiGqRp3LHN my_DOaxMTZRotF8g32DkESi378G_hV8pg02ygoVj.sEWskjCWzeZ7jjz006oAtTzHad4KB7FYMAf Klglxy86buqwu9zddxs7UQtFJ_cMCVg34xEI4tBYbqOfLThSrxQymWk1tIXPCa7QwIC5R7jwFYSk MzEkEgj6yqb30Rky5N592mCVgqmkNbsh.O.6wBcYqukb5WGBngon2BdfDcs1Gh.YdsfZWobS2R4I jNPTKgsyizqPzW.TiJtL6w1BegGHqr5.7bpvB8ZcSAPeOGXrYzoApE_806jxq5iIjG7_FIpNNpSd kicMczXr0KPH_NhmEvCh5kcyKoAvcSRTH.r.sf2xXpFM_30S2ZjCnbCckqMTY0BhEn2ez2D0bqHe oJSZzHPmF5lWFfucPlZ4I6m3oR4DMp206oN77YmIwRKd1_cgKSv47bSe0odCs1VDz6PYWCyfWdjZ O4qJ55YD9plLDLsUI3xcP_UTAQJlHvq1NyPTmmQcN_8cUbG5sWPlUgkuH3.Q_83XCRxyAiZY6Gaj Tbv2AOqwmlBwTf9iafZ1H26r52hr3iUMHmOxrWKIR54PWCwUF5upV87I8bhC5aOV7glAJPS7avEd meNUWjx_WTBLYbB7wZX8bG1gd1ksVq71uhEZGDz8ftxPrLJLxURE_F9.hHFlM1dZ_6IPO1kuiuZo M2k87THpd2ZBFjb9WWyfGkxmbD1ZJtUwSdCONTV2EL4kAJcGePcBr4CNQK5wfqYJt2preFze1jui 8XK_3oKBo7U6sRGqjc86EBwW2PuvRBQbMWQy8sB71eG7M013PheftB3MDCecgs6b74cvkgtGSLyQ to5VTKXnl2J2WeSYzAdBVIHJ.NTY4IKPpacAGunSyRAwPFClnDsUo2bMO8expWmHO6f6h8Rp36w_ bxw6AbW.vPK49O7ep2P7cID0bjsDoKQdg9Q3Y.AFTQu9LRzE4qA1S18.B15JzJkC9MLszeXFPZ1k az9W96ri5pHkR82vi_OVFUCR.xvA7ixNJg09RBVCpMTVJpzhqRl_P3yZ1rzl.2fERotxmJXlc6c8 fk.8eKhfwMa0YVH.onBJmrzxFiHnCEHl9XuJPu9z09iOwqaoiM8Rr6qVnrV80YZbXLKG5OTBuGYt 1OelY6xzmpdLKh1GrsftWLCMVLYAOe8svSOqg0fVYkoGEkfCcF7lf5CSl_K1nZG3pfGm5nwod1lj Un1kPycPGAfQlW0d0WXgGqXxj.c5vD.Fr.tGoGHN2Eb4XnVPesI_z9.t.9gGXUIT9W867rDkKHOf WmYO4hHhYDmnXLtV.ANQIuNaGOMAXxWDBHd6eQhjGhGVpuPccfTgiN8DdnYTEJ.WkrIysLkoZK0q E0lvkNg9CmuUM9B3jrhWJmUa6EDykVPW_k3fvdHwWuqKl1CD1Rv2ucwsBIhXfhYZxfFcGmNgsh1Q BQP24HkqcGstpjcaUAEOdb2dqz3q3yy8rjCoh5qjZ1_n9k3GIQ68PpvPzEN.LT6Tyso0nJwYwz72 s_JARrLOgx4E6Bx0WLXtjG9wlS9EyGkQYfzoRqkod6xUC3Mf5lJk8fezxkbtiYXqcwgoDnixjfWL jb_ITY5XJFgy2YsfBw3nfbN_1PfJsFB0VE.5VysyIbZbXFoED5d0Np0xx7hThU4X7BvI.EMjpC0i _nsNyA6wpuY90tw_YAPAdqr6R4g8TokAjGxFf9EiX10CPnNdx.gEVJ.OoCWrEFSVHPBd4JKmpGqN lJQJyDT.mFeXGQ8wZJcgFU1VkoLW.uvixUJwvDRYG7fckO8zpBkb_KTxV4PMLw.eMLSHbszpyoKb iU5XNj8ZXytRpeO8wUrBWI3KWZp6KffkJptmMrS6iowlvxKChPCXZoW.bQbNOICPUabnp6yjKduN mG51Imd7.BvYNBUK7X5KO8ZH7GNnvJVpcIi8gQjBq9qbO989SZxuB2AJLiOKmc8_wlnpBTNFKX3R yGeKJKu2UFj3sMovcxHk6CFMm4nPXDguv_pOY4gsCksd_RuWQvorFl4tBTJKd225ffB1s.KuHIeR 1_iduccn8vntt2wmEn1DhRoJaiavyyJyJTUl8PY3yJVQvb2dI7GwkyrtnF2PQS2Imp8SY3ftQ4Ft MwJzn9o6fWrA77bcNkRG83hG4vYiJl_Ri96aNFX6mw22afhqFc8cYf00w9BG3CPeCZUAbCaN7BzH 8jzFI.Va4s5XgHRKHgTA8bvBvR6jbBKATzf8DlJzStHYVctKJFlJWAzudkJpRZ_i8QhkZjxERegg O39cQ_TUHAOFtNEgGrv3QVQPeZ3LL_9hCVX21TFooOyCIU4G4C0ParXzzvhG2A_IU8QV4RaBTs6N 2KcpD_jJTbB4f5r7f4GfN1T9lZi55Dq_6dVs75KY6tx8v4QkopPqTxDF46r2qWK2FU9JvjkS_bwX E10Dtm4ueQM_5cykqPAx9ORX6WwlabII98YHHsNe0zWA7aj4LWH5bJnxw_S808aS40zbVfPwIGd7 m8B5bXwBciON7MmlYK3qkvXXugvWQJTt1hqt710hhdNLtj2EizLMMpU7jmAq_wnvl6Qwh1GuLAfR gcMVlhyXWEv1skyTv0S2EmjAhGjeeWnwJnfk85WsrudL6OdRZqS2FmMesqRDK2gZT8AdXSD8v3Uu 9 X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Tue, 2 Mar 2021 10:01:53 +0000 Date: Tue, 2 Mar 2021 10:01:47 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: cabo@tzi.org, Carsten Bormann Cc: Glyn Normington , jsonpath@ietf.org Message-ID: <2020167618.824656.1614679307790@mail.yahoo.com> In-Reply-To: <2E02A243-A104-4502-AB64-4B8228278126@tzi.org> References: <98ed1a4f-82fd-3f94-a707-8569f89a5041@goessner.net> <502566941.150044.1614366732927@mail.yahoo.com> <280EE68C-F1A7-4863-8F5F-7F544F431973@tzi.org> <350059548.134171.1614369123233@mail.yahoo.com> <1576492499.98241.1614369511559@mail.yahoo.com> <1157333423.170620.1614370476963@mail.yahoo.com> <93F527B6-CC03-475D-93E1-AAC9CEB4B5A8@tzi.org> <2126411059.183763.1614375732675@mail.yahoo.com> <83EA4040-0E7D-4DDB-AF2C-DD8DD59B22B3@tzi.org> <380AD158-6728-4289-BEA2-61121E2A5EA2@tzi.org> <473018687.319278.1614458246139@mail.yahoo.com> <2E02A243-A104-4502-AB64-4B8228278126@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_824655_1131273142.1614679307789" X-Mailer: WebService/1.1.17828 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.19.4; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Some Comments ... 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 Mar 2021 10:01:56 -0000 ------=_Part_824655_1131273142.1614679307789 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've set up one for GitHub, too. =20 =20 On Tue, 2 Mar 2021 at 11:00 pm, Carsten Bormann wrote: I = must say I like the stream of pointers to stack overflow discussions that I= can see on slack.=C2=A0 That is certainly a nice service. Gr=C3=BC=C3=9Fe, Carsten =20 ------=_Part_824655_1131273142.1614679307789 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've set up one for GitHub, too.

On Tue, 2 Mar 2021 at 11= :00 pm, Carsten Bormann
<cabo@tzi.org> wrote:
=
I must say I like the stream of pointers to stack overflow= discussions that I can see on slack.  That is certainly a nice servic= e.


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

<= /div>
------=_Part_824655_1131273142.1614679307789-- From nobody Tue Mar 2 21:14:58 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 532C93A1926 for ; Tue, 2 Mar 2021 21:14:57 -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, 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=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 mu211qxVUd4X for ; Tue, 2 Mar 2021 21:14:56 -0800 (PST) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 12D443A1925 for ; Tue, 2 Mar 2021 21:14:56 -0800 (PST) Received: by mail-ed1-x52c.google.com with SMTP id h10so28171138edl.6 for ; Tue, 02 Mar 2021 21:14:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=3XpcE2hsSo+R6TO3A8T859e9JkxJnlc5q/Ijq+CQNbU=; b=rlltZ9fuWN1csHf4LIFR1S3DDO0N7upsdsVo+tAY5AEWGo3kjDQsMIgB3Akd2+7Tx4 nzSo/XJBamXEU8QYbclXqY71kH4vae2VCNUpXG2/cs9vgEGgtyy/7QfxR2UDJjjK/TaV GmRDhQ0rG5B8VrrUNq7jgXhJoLWhlSA+DqqumMaEZ2EO7lwTOPy6arROytuVPhiAEo4s HpTVWIKyZwUwFEDyxIhiGh46+7bG/VQMQDLGStNnOErphJrjqkn8iP7jE4EApunNb9K7 cJuPYwlcLcA0mY0TuckIpI+FryeDwsglbwvFUbiVYPCXibYuYyK0ZLLEhz5bTyLm2+Ah zccg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=3XpcE2hsSo+R6TO3A8T859e9JkxJnlc5q/Ijq+CQNbU=; b=cMcmYmfCE4vf12C4ziHROi9VdEpR26Jk5jvQaGwAIAUqdimxBZw8BEh7jBr9GQcWV+ 2sUzO7z+7FOEMkKRw2D4MFYybj/S4V4+t5Wmk24LVtCbB0U6Gnikx5Q4Md7LffgwrnOK oPzUYrbETBmIZfaV2kOXyHtih4tLMokLQ1lS0KQufCLK5qQGpco2t+oVkSLB3yGkGyA0 ibFcyEazPhb6AIHdNak9oXUX5zF4Q68lEHk8JXzLaFYZxzsrGrgXdSwzAzze6pSOro+U 0gmPEYOCUnsAkXx3bH11VA5P/EXvy5TeDdCnjmbnq9aX9cCghmifprs76r6ZgTOrD9i0 vHiQ== X-Gm-Message-State: AOAM531Xaugq7uo0YYyJAYCa2g5sxOtYW60MoMNHBUi7VwrFv84tdOLX n/ZQ2VWzvjRhuDg5Bl3K3KdfYAEr+q8= X-Google-Smtp-Source: ABdhPJzM+VElzdTr34m5ePQyd+HMWL9lXoRudGgsARRCzOKfIGbrQMA0Sfu2s2NYLR1awKLbpvITCA== X-Received: by 2002:a50:e183:: with SMTP id k3mr23946006edl.45.1614748493202; Tue, 02 Mar 2021 21:14:53 -0800 (PST) Received: from [192.168.1.95] (71.224.125.91.dyn.plus.net. [91.125.224.71]) by smtp.gmail.com with ESMTPSA id a22sm11165029ejr.89.2021.03.02.21.14.52 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Mar 2021 21:14:52 -0800 (PST) To: jsonpath@ietf.org From: Glyn Normington Message-ID: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> Date: Wed, 3 Mar 2021 05:14:52 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [Jsonpath] PR 46 merged and plans for IETF 110 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, 03 Mar 2021 05:14:57 -0000 Apologies, but I had forgotten my blocking review of https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, but have now merged it. What's the plan for IETF 110? Will there be a PR to discuss, will we be discussing Stefan's excellent analysis, or what? Thanks, Glyn From nobody Tue Mar 2 22:37:31 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 1FD443A1AFE for ; Tue, 2 Mar 2021 22:37:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.908 X-Spam-Level: X-Spam-Status: No, score=-1.908 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, T_SPF_TEMPERROR=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 8EGVNj3mgbRd for ; Tue, 2 Mar 2021 22:37:24 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCE143A1AFD for ; Tue, 2 Mar 2021 22:37:24 -0800 (PST) Received: from [192.168.217.152] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Dr46p1lwRzyV6; Wed, 3 Mar 2021 07:37:22 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) From: Carsten Bormann In-Reply-To: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> Date: Wed, 3 Mar 2021 07:37:21 +0100 Cc: jsonpath@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> References: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> To: Glyn Normington X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: Re: [Jsonpath] PR 46 merged and plans for IETF 110 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, 03 Mar 2021 06:37:30 -0000 The next step should be to split Stefan=E2=80=99s issue into topics, and = see where we are on each topic. I would expect some are mostly done by #46 already, some need more = tweaks, and some need real work. I=E2=80=99d prefer to discuss actual (if embryonic) PRs on the latter = ones as well. Gr=C3=BC=C3=9Fe, Carsten > On 3. Mar 2021, at 06:14, Glyn Normington = wrote: >=20 > Apologies, but I had forgotten my blocking review of = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, = but have now merged it. >=20 > What's the plan for IETF 110? Will there be a PR to discuss, will we = be discussing Stefan's excellent analysis, or what? >=20 > Thanks, >=20 > Glyn >=20 > --=20 > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath From nobody Wed Mar 3 00:00:52 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 2274C3A1C80 for ; Wed, 3 Mar 2021 00:00:50 -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, NICE_REPLY_A=-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 POumZ9DypwzU for ; Wed, 3 Mar 2021 00:00:48 -0800 (PST) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 A4F663A0744 for ; Wed, 3 Mar 2021 00:00:48 -0800 (PST) Received: by mail-ej1-x636.google.com with SMTP id r17so40287857ejy.13 for ; Wed, 03 Mar 2021 00:00:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=4KcLKABtIFxFssby80d9yeo3TrE0LtPC7z3rnHgUaks=; b=aCXkysjej73ThKneBYzP+KbH7BVaRT9NVsnmYV99W490BpXkE/O/HuVJVkTT6H/+VK btF53GdzH+uOf+yFprlSqzXD0ciNNnX1TYnkZ60DaL+TVDc4R9P+AcgrBMo5SzsSVXbI Z62E3MTjNVMgMhaH1GSf30Kyha9jfgm0pTPLx/G5vnQALoJlacOnxgddPJu+uKeUr4+L b3nGR0QPY1eX5lvMecdDJNkuO8x/LwlIzDCdbyB5/j+hByIpo05Fch6ynG62c58Y1zky WvqCHufgW5zUoNzb83j2lOix7TjmWf+OXkHnqVRfWvXFHQrnC0q6U3aCYX+CGZgx9Oe2 0rbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=4KcLKABtIFxFssby80d9yeo3TrE0LtPC7z3rnHgUaks=; b=YmJ/I23g2t0pjvRkOa3VUErjvqQhkhlE405nqXRPHf/0Bn0mWBS7+0OOj2AoQZRAWd Tm4ldG/1uB2lm0+IC/LqjGWvFN69rzzUnlQumvMV+fF2Yktp3OfzHuorUHvzVZxza+Vw OWPmDaw1cpjj6w13B5oJ/DkpCI03t7wbbfqug0Gv4Cs2Enf5AiDD6Z+Wnidi/tX1sTho GWEPyV4S0eZG5EL47yCr+rBNoJuxRa44gl9X17tHb12KoPa9Rknrzk8mtzjNnXfMKfab HM5NwhAABzJLpYzA6TFy9sY/XCA/PeeTZQRf2KEM4NYFI0hYrbbkVkwa++uHmfBn+OHy 48QA== X-Gm-Message-State: AOAM53313QayeWV7ay74hLYFHWN2CMSXuLOKLkjYSyszfnT6O6zip38K /VtvNovEOxXsw0ML8PLsOdNtOCGpgkM= X-Google-Smtp-Source: ABdhPJyvi1n2vP6ws8oBttn+fbKxgUWYhd2BegDkHhkf9m5wagmo7UwwAwmEb7gTMIb7ievJV2921g== X-Received: by 2002:a17:906:271b:: with SMTP id z27mr24170000ejc.313.1614758445776; Wed, 03 Mar 2021 00:00:45 -0800 (PST) Received: from [192.168.1.95] (71.224.125.91.dyn.plus.net. [91.125.224.71]) by smtp.gmail.com with ESMTPSA id a12sm5517128ejj.121.2021.03.03.00.00.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Mar 2021 00:00:45 -0800 (PST) To: Carsten Bormann Cc: jsonpath@ietf.org References: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> From: Glyn Normington Message-ID: Date: Wed, 3 Mar 2021 08:00:44 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [Jsonpath] PR 46 merged and plans for IETF 110 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, 03 Mar 2021 08:00:50 -0000 +1 to (embrionic) PRs. On 03/03/2021 06:37, Carsten Bormann wrote: > The next step should be to split Stefan’s issue into topics, and see where we are on each topic. > I would expect some are mostly done by #46 already, some need more tweaks, and some need real work. > I’d prefer to discuss actual (if embryonic) PRs on the latter ones as well. > > Grüße, Carsten > > >> On 3. Mar 2021, at 06:14, Glyn Normington wrote: >> >> Apologies, but I had forgotten my blocking review of https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, but have now merged it. >> >> What's the plan for IETF 110? Will there be a PR to discuss, will we be discussing Stefan's excellent analysis, or what? >> >> Thanks, >> >> Glyn >> >> -- >> Jsonpath mailing list >> Jsonpath@ietf.org >> https://www.ietf.org/mailman/listinfo/jsonpath From nobody Wed Mar 3 00:01:46 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 6D9933A1C80 for ; Wed, 3 Mar 2021 00:01:45 -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 gdKvcQZeq3ps for ; Wed, 3 Mar 2021 00:01:44 -0800 (PST) Received: from sonic303-20.consmr.mail.ne1.yahoo.com (sonic303-20.consmr.mail.ne1.yahoo.com [66.163.188.146]) (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 124073A0744 for ; Wed, 3 Mar 2021 00:01:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614758503; bh=OpzmVnbqjOl1udnFr3y1f7xyFGF9chKuDsedH2aC1zo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=Ef6nRmc49fHMyjkIPdhPqoc2xSQBnca5tx6LjLTADYNt3Ht48iMRR2WQUiYEC8FdOyNR01FupTg95QXaeMtJBopuBEoDa/z1Nd6aTFEL4a+hu0vOX1+7xjdnbdI6bNHZHO4Ym5Zu+KWstk6vCeChtOnZkNn1kDqXEx9CjmmOR0dorySYivFXuuOXvXyvFvbX0oh/f/xVq4cNQdLvhAZKcvRZB1O7Bkm8aAVhgNwPI0roI146iY7RHmPYRg/B7tT8WgVGpKU+eB0mpADIiMx9qbDMKujtH2vb36PC1HcbISqyxRzGO60rq29KyO9K4QNjzvmG1jo2bIIxvmnUVz3o9A== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614758503; bh=HSGdl/MEdScPS3qWttLcZgdJqsVxMG+LpwlW8GsHn7c=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=ZntLNLlIZlZnlZNC/K/DzWiXjF7xyhPEJSZAp27fTpfQjc3Sf5c6hFrCMcT6d87WOUUaCryxfxfsfbpQ5FIQ8UZX6dhzaeH/uV2YVFlSqcMR6hIHvSahWumYhklF4M6ifm4hx92lRjeol2zPPnfUmfiVgOFK3A5+79UYadyvTa5kG+aaPumr/vvgDdp2BlITqcbzCo+1gUa1xjpT9YgBvN8kob2cdr4GAaDFGtHJKInKYO00qURpVdPfqfL1c/OncaKDeNorx9aQaryv1lRyffG1bkE4jhEf3wULqnbzx2ivWZuZ7/HJfLuw3+WgtjnD/RYXzQJ3/Q9poQvnHmXsoA== X-YMail-OSG: hmzf9pQVM1n__8liGaB13KepeYGLt0uxGyFjJSiW_DxIkLePzc6i9OfbdLPNUwI YnzPP48cWWUewnrWxfqYz7siibPTb4ex_BX71igUQwxapczQG0e7rgMQ.9hhEgGvgZ3FOAOoZdtz 3MIAvSNirwyKfqYgU0Y_pImGx6lyywHi9ESNw0hnLTdbxr8raAEkusEEVZXlKivZGaLIedV5Kxv3 xjFksjP1WRAVU6iRS2EB3lTl7WyzICKv354PGVSi9r5xcIVQYfuwnpHbEVz5beLJOGII9FLcukCA ZcBGV3LWE3.SJG1b0dnvCXVBc5KvKroEjItW1qoa8o99P46iNl2TAp7gGCGdDcBE5UyHajLZTwTX 5ySt38dx9x1eEEHPXQgVu0fVesW1ESD5DKmn7Ekvo8i2.3YaXdBWdMbaiWWUC75kkgVywRMzxz9l 57ospznsVcCJYVwOcZ50tObwjEqKeK9EO2Nu4ceWiCJBNCItk95Rkep.hc26DGhYitDZlx8ovRhe IjfXRSudqmp33NmZyvc_3Zt8NK1Vxp9OhV9CwkQWUBQKbd7VtttIgiTS1evtMHJHOUzg_tVf10yk f0hQYqMkCBxi5aOsjawAoy_2QFT93kqOSzW02P0MMWWQ4sIbJwHsbj8F2WtbEYMI9qt5SyBx8uDY eKnnG.iB6TPrWZiKeJltYFstkX1aTBoKhtYqtQ64SwaSCI3Whzrlbg2lD5LSGcH_pwhOxc2eZUEn 7TC6gqniSFp3nCGmiQRvne.c2wUrHBI3lkTf7agbTDgLeEdV.fIvXbVX_H6dKEVdCJgK6JNc65YH ziDvJbYvuFY9e7E3X8.Fvm2jy47YxVa4FROM7Pb3UWQ.5Udweeu2WsypMgp7xaMaSHM1hRdN6VPy he3E.ShpnTGTmR6NcMhVbURCcVhJh5IZGD0Xl8i7xjoZfoZGDQ_XTuj8VfZNXVZhpIjNATP62b.q gmJsCf.aSdizlsd0kekmEaatMkdTAMp7ZQTDkybi4lfgGlv4nsa.WdbqrD7ba9DjBwvv1D4ON_mv 7ZXuIjB4Y4i56GepwkO.MYeqOWXFkBdjmJBQmjI9EbEmOfz9nysSj96LUczin5CAwDAwZHjmuKTh iNma8L6yscbpquU3u7wIh8TuHQ69EorBii.y9gfA58NsF0p4_jr5MBbEQcEVzSDkJ8UKH.Jsf8RI FqrRgqLIag1x4c9qjNvEtmpW0NbNCXkp5nv76E3bZIw1931MwQUKh8r20iwenHLjYy7c7CeL3Gqt qy88SJuoJBlWer2005vzXt_2e4q8LsPl0CC2dM5hIyZslICC4ZqMlKZZ9nNNePId5hXN6TXxQ9sO t7NetR0uMVCfHmBoC.6pl1YcrR_nCH90pPuVEjhoWeQp5E0OY0HfUP2leAzPerFLcKC0yZ2uwoY7 LK5_L6XRvWue4.XsRYlYQQvsAUnsC11s6u7HUii0Tx1BIKh295sjpTV6K7I9cijNRq.SY7R7.5a1 weewv5zoYLBqwtLHVSFevGWdAqofPYb02mwcFFLeGPKKlZdgieiyf8qcs7cCRNFoiJ0xMvLlt3An Ars7OYK4PjVhaXlzzp3sKAxEnq4NaxyRS7tmjOxOUHtHav5yi2PeE5CqH81z3pML_Res7.ZJSuNE MLrHVn3RB0R8Zha8l9Hvqnlo0SGcRh2YqCk2Tr3AB2z3hKJkebrM6VWezw5Wwe3X.pMo41aMinPX V8GUB3sa_cfvPJJEEw5.5s.ZndwYoFUM7d3DjQd8BAuiLdjxpWQQ4hRos0I7XVEkYFzQR3.NG2r6 9.zn0xiq86Cpgiyoo8kG7XoaeyOndOUZx8KdZ1iA4M5ZEL2AdtMZ8xhme0hyfi5Xt0l0QD64cw99 XcASMmqUrPRN7lnee9cyvgwiJgmy65jId2MhK4PoBcTBbGLXjwYJ3Z.o2jfTS0GipbEn.1rT5k_i Tl.OwN6P3igvmMc4AR.wIUwsy1IhPGGtlz.kDeGfYlSh6r3ZCQP63fOD4VDu_LcFognuipLjVvcS QiX1KZRAIq_qOwjtsAgtfW2xsNudXkOzH9NWBAAS.B4F.dR_Ax9izOJ8caHKLgkSPulPk5YoTIjh X8E_TTVOqwB16.N1N9PDOB28ni09TnjZFCwjCyfYxfEKPxJU4A4zY_VUFwXFHSbRlMyPV1AVTZj9 bcX_cWL7JWbyjMpRqtDNVLG8U8GJ7T8HIpAgQemWMsHsd2wbL14ez_lMKlaBKMtTF5KX3qLWR4Yc ZJ3.ICYq5UCfGkiQafssKk1tOT9n4Jj2Z1f2bO9tvgQn51BoIzwadh.Gmqdfrfd3cRXnb9nf7Eor bdfIXX1Rvk4HRojcaAGHYkufDZS8F6KuEiqTxhjycimvAsIkrjIbZg3u0rvP6hSyPsLtnQ_bYyKI rmI7yrXsd7BH.rumt9ZjpPE_I4NLKmXq.djPwMiZUnP7Bhl6KexpocSyWDBKpWiGRrKh2GbzoyYX lCCyKzwKeCsc_pL1Mh75eAl0IX6wtryFEJHC5MS3i45FKIKaSAkR4PaPFMEtr2hZfM22ZsldkwgG .W.tyUVBGgBtxR4ZRSafYy9c8pQYF7ZTLgL520Bl9aXdIvDKB0ZI574BdCwLFltWNPN5gs2NdqOD iD3MxRk4dZiSOrU6a_GtH3bSBUApoaYQq11PTXw1CYqX_PAvex.0NnULbD16ui7.1bH3._Gl2Lrk pIIWsGrD5R6JXnWFa7QbhDSc._Q-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.ne1.yahoo.com with HTTP; Wed, 3 Mar 2021 08:01:43 +0000 Date: Wed, 3 Mar 2021 08:01:33 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: cabo@tzi.org, Carsten Bormann , Glyn Normington Cc: jsonpath@ietf.org Message-ID: <919759480.18719.1614758493098@mail.yahoo.com> In-Reply-To: <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> References: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_18718_981383787.1614758493097" X-Mailer: WebService/1.1.17712 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.19.4; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] PR 46 merged and plans for IETF 110 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, 03 Mar 2021 08:01:45 -0000 ------=_Part_18718_981383787.1614758493097 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I would request that if some fit into the issues I've already made (there a= re a few), those issues be continued. Greg =20 On Wed, 3 Mar 2021 at 7:37 pm, Carsten Bormann wrote: The= next step should be to split Stefan=E2=80=99s issue into topics, and see w= here we are on each topic. I would expect some are mostly done by #46 already, some need more tweaks, = and some need real work. I=E2=80=99d prefer to discuss actual (if embryonic) PRs on the latter ones = as well. Gr=C3=BC=C3=9Fe, Carsten > On 3. Mar 2021, at 06:14, Glyn Normington wrote: >=20 > Apologies, but I had forgotten my blocking review of https://github.com/i= etf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, but have now merged i= t. >=20 > What's the plan for IETF 110? Will there be a PR to discuss, will we be d= iscussing Stefan's excellent analysis, or what? >=20 > Thanks, >=20 > Glyn >=20 > --=20 > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_18718_981383787.1614758493097 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I would request that if some fit into the issues I've already made (there a= re a few), those issues be continued.

Greg

On Wed, 3 Mar 2021 at 7:37 pm, Carsten Borm= ann
<cabo@tzi.org> wrote:
The= next step should be to split Stefan=E2=80=99s issue into topics, and see w= here we are on each topic.
I would expect some are mostly= done by #46 already, some need more tweaks, and some need real work.
I=E2=80=99d prefer to discuss actual (if embryonic) PRs on the= latter ones as well.

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


> On 3.= Mar 2021, at 06:14, Glyn Normington <glyn.normington.work@gmail.com> wrote:
> =
> Apologies, but I had forgotten my blocking review o= f https://github.com/ietf-wg-j= sonpath/draft-ietf-jsonpath-jsonpath/pull/46, but have now merged it.>
> What's the plan for IETF 110?= Will there be a PR to discuss, will we be discussing Stefan's excellent an= alysis, or what?
>
> Thanks,
>
> Glyn
> > --
> Jsonpath mailing list
> Jsonpath@ietf.org
>= ; https://www.ietf.org/mailman/listinfo/jsonpath
------=_Part_18718_981383787.1614758493097-- From nobody Wed Mar 3 05:20:57 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 4D9F23A1110 for ; Wed, 3 Mar 2021 05:20:56 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 iDEI9SG73k72 for ; Wed, 3 Mar 2021 05:20:54 -0800 (PST) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 7DEE33A110A for ; Wed, 3 Mar 2021 05:20:54 -0800 (PST) Received: by mail-wm1-x32a.google.com with SMTP id e23so5154048wmh.3 for ; Wed, 03 Mar 2021 05:20:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=x64Ba6WQdE67hHGecalpBNFHo7PuNN9nbVpjIKZ7yF0=; b=NCwbV7xLvH1Kcple31RSzBoiOf5o2EzCZtz9xiXJlnFybq3+L3ss12X2iQKl8G/tME VEU11cYaRl1NMdLd1e1zTpUX0AfaY50TPTcmRhr/swRZBqeSbW6gmT3zxCpjor3UNMyE a5fX0j4FuWZFxzqT8H+if7oVi9DzfDu/2RhzYxE5kRGe7BNO9u2RTbzHO87xSia+yhjg u8lNvo1R4axsQBiNzcDzrQHRHwcy1LpBpQfWL06dwWHOZNfyNckcS5S/1uZTbLzAQrPa fdrntlWACqX6JxfBXmJlc6nfELKgWO3XDnJAi5SaR94e5tdQ0RNLqym7LByYLkZk+tGS AcEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=x64Ba6WQdE67hHGecalpBNFHo7PuNN9nbVpjIKZ7yF0=; b=Yt3nfmlbH4gV1ILQJvjfjRJTm1yA6vk3SITliRUAkIwYr5JYpOE3cb7SdQu4lNRWCf wEZx4ynqAHQmp1AfizPbFZkBuon9wYvfj76fhgX2WJa/q7VzAH+RIQDLEl0Gx4g4F9JI dzIx2mKMWrEb3e0o7Z2euILuBmAlm1OLb7C6SKj+GeQfqkNxqrxx/rONA8fcmENxqqCr qYj7ukSWafs2mg90fYYRVe4TEh+ngbCArDNkpJqP8RGIj+GeX10SG/Rg2htIqyp7k+Nw FPA2nJlRvdA2uPXsdmZnZliy9pO6BdRyLQoWfXoajclXcJWyipcv6jbDVf284PCwMa4j fAUQ== X-Gm-Message-State: AOAM530nRIdS9Dbxzxb04Y0B3km78J4bY3xzlbTttNfwmIVvasXuHiXo DrN7KMS4V9P/zBbqUQ4HpLxnHvbXM5E= X-Google-Smtp-Source: ABdhPJyEZzeStlFAFVSqpU9GiF+iwuneb7jJK7M8Eo12Te9h9MhwcghTf1xedvxXHaGFyWQI4Ff6Vg== X-Received: by 2002:a7b:cb5a:: with SMTP id v26mr9247017wmj.162.1614777648568; Wed, 03 Mar 2021 05:20:48 -0800 (PST) Received: from [192.168.1.95] (71.224.125.91.dyn.plus.net. [91.125.224.71]) by smtp.gmail.com with ESMTPSA id n6sm8011505wmd.27.2021.03.03.05.20.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Mar 2021 05:20:48 -0800 (PST) To: Greg Dennis , cabo@tzi.org Cc: jsonpath@ietf.org References: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> <919759480.18719.1614758493098@mail.yahoo.com> From: Glyn Normington Message-ID: Date: Wed, 3 Mar 2021 13:20:47 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <919759480.18719.1614758493098@mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------C8716602E6E72F15B90FE8B5" Content-Language: en-US Archived-At: Subject: Re: [Jsonpath] PR 46 merged and plans for IETF 110 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, 03 Mar 2021 13:20:56 -0000 This is a multi-part message in MIME format. --------------C8716602E6E72F15B90FE8B5 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit After discussion with Carsten, I aim to submit the current state of our draft on Sunday 7 March so we have an updated draft to reference in our meeting. If anyone would like to update it before then, please get your skates on. :-) On 03/03/2021 08:01, Greg Dennis wrote: > I would request that if some fit into the issues I've already made > (there are a few), those issues be continued. > > Greg > > On Wed, 3 Mar 2021 at 7:37 pm, Carsten Bormann > wrote: > The next step should be to split Stefan’s issue into topics, and > see where we are on each topic. > I would expect some are mostly done by #46 already, some need more > tweaks, and some need real work. > I’d prefer to discuss actual (if embryonic) PRs on the latter ones > as well. > > Grüße, Carsten > > > > On 3. Mar 2021, at 06:14, Glyn Normington > > wrote: > > > > Apologies, but I had forgotten my blocking review of > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, > >but have now merged it. > > > > What's the plan for IETF 110? Will there be a PR to discuss, > will we be discussing Stefan's excellent analysis, or what? > > > > Thanks, > > > > Glyn > > > > -- > > Jsonpath mailing list > > Jsonpath@ietf.org > > https://www.ietf.org/mailman/listinfo/jsonpath > > > > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > > --------------C8716602E6E72F15B90FE8B5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

After discussion with Carsten, I aim to submit the current state of our draft on Sunday 7 March so we have an updated draft to reference in our meeting.

If anyone would like to update it before then, please get your skates on. :-)

On 03/03/2021 08:01, Greg Dennis wrote:
I would request that if some fit into the issues I've already made (there are a few), those issues be continued.

Greg

On Wed, 3 Mar 2021 at 7:37 pm, Carsten Bormann
The next step should be to split Stefan’s issue into topics, and see where we are on each topic.
I would expect some are mostly done by #46 already, some need more tweaks, and some need real work.
I’d prefer to discuss actual (if embryonic) PRs on the latter ones as well.

Grüße, Carsten


> On 3. Mar 2021, at 06:14, Glyn Normington <glyn.normington.work@gmail.com> wrote:
>
> Apologies, but I had forgotten my blocking review of https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, but have now merged it.
>
> What's the plan for IETF 110? Will there be a PR to discuss, will we be discussing Stefan's excellent analysis, or what?
>
> Thanks,
>
> Glyn
>
> --
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
--------------C8716602E6E72F15B90FE8B5-- From nobody Wed Mar 3 09:59:22 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 7A1633A1798 for ; Wed, 3 Mar 2021 09:59:19 -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 extzSHP1taAG for ; Wed, 3 Mar 2021 09:59:16 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EBAE3A1799 for ; Wed, 3 Mar 2021 09:59:16 -0800 (PST) Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DrMFY62VyzyTb; Wed, 3 Mar 2021 18:59:13 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: <919759480.18719.1614758493098@mail.yahoo.com> Date: Wed, 3 Mar 2021 18:59:13 +0100 Cc: Glyn Normington , jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 636487153.179261-cd54ce9fa3b9c0229b1d6ed577219256 Content-Transfer-Encoding: quoted-printable Message-Id: <708775D6-6A2D-44EF-91B4-D1C9DD70C6AD@tzi.org> References: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> <919759480.18719.1614758493098@mail.yahoo.com> To: Greg Dennis X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] PR 46 merged and plans for IETF 110 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, 03 Mar 2021 17:59:19 -0000 On 2021-03-03, at 09:01, Greg Dennis wrote: >=20 > I would request that if some fit into the issues I've already made = (there are a few), those issues be continued. Good idea, but we really have to clean up those issues. We have a few labels, but not enough. I created a new label, =E2=80=9Ccontroversial=E2=80=9D (I know, that = will be controversial :-), and have started putting labels on things, = according to the https://en.wikipedia.org/wiki/Wikipedia:Be_bold = principle. =20 Please go ahead and completely revise this (I just applied "the best way = on the internet to get a question answered still is to put out a wrong = answer" :-). Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Mar 3 10:49: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 A8F2D3A1842 for ; Wed, 3 Mar 2021 10:49:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e5iIkoxuKc0m for ; Wed, 3 Mar 2021 10:49:45 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (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 6DFBB3A1840 for ; Wed, 3 Mar 2021 10:49:45 -0800 (PST) Received: from [192.168.178.20] ([88.130.51.189]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MKbTo-1lVkZ12nls-00KxQr for ; Wed, 03 Mar 2021 19:49:43 +0100 To: jsonpath@ietf.org References: <5f2b9a47-289b-da39-9631-b3b120085806@gmail.com> <12094D1E-16EC-4BF3-B9E8-9B4686364CF8@tzi.org> <919759480.18719.1614758493098@mail.yahoo.com> From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: <2124b780-2d56-a9ac-f7fc-3f6d8833854e@goessner.net> Date: Wed, 3 Mar 2021 19:49:43 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------3E1DBA514D4665DCB73CB3DA" X-Provags-ID: V03:K1:WJRIHaUtXX1Gk5mOt7ZsUosr7fbw6QPa2Wb/Bk2jEmdneI4UJ2q TfmeiQyHGMfZVkKvMOFvHi+gL6DMEH0g1jpcCqcsBxAffmgyO627kaQ9R6buai2US4H6RZf QtIaLhOha2DUzOoKJljMkJ78NGnQ0NQDWFC3g0EvLLISBm7dlpdBK343h96o3CfyEXNa/Bo cj25+cPYqBfXmlpVGCOqg== X-UI-Out-Filterresults: notjunk:1;V03:K0:JnmD0QKVRpk=:H9VFvSbiH+Qie/f0rTdT+z yzNENRcWHiVFm3ZFY3K072c8jSB+H8espUrVggfEP/U146CEyGhVEEgMIJZfHxUT6610bxzWm RSjbw77BOKV1gLyuop3MGDSqJnR7aQneoNAxj4GtukJyCKOf/JRSJSDnAEKJDby4XfAb3t9eN F5H6G1VJ9YZ+82lIiNs0uOp1P80k3ejNM7TRZky0VTT9Cqjmu4oa1ZxQFSkBiPHGgvjlLFsx2 x++RgHuKCXLm3b5wWAMP3XjntkC8ijHgn040QkGvZcum46GQ+XPHuWDpXkbD/wMerKyiwXY79 buAd+Nu/ZacnlOWYGm50aoprNSoA9dm8MBO5ja8iXhskKC0epyhsHoOu/JP9gB7okfKQV2tWZ xPVylF7jUvZVpxeAl/+gzqyPTIee2kIs29uFYBZfMOdMEwPLxWPdk9VGV+wLGFkdDWqTR8nkV h7r8EIwYnA== Archived-At: Subject: Re: [Jsonpath] PR 46 merged and plans for IETF 110 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, 03 Mar 2021 18:49:48 -0000 This is a multi-part message in MIME format. --------------3E1DBA514D4665DCB73CB3DA Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit A lot has been achieved in the last days ... great. The set of terms in the current draft seems to be more consistent and less redundant now, thanks to Carsten. I second Greg's proposal to continue already existing issues. In indirect response to Daniel's posts "@ and the current element" with interesting aspects and links,  I would like to start a first issue. This probably needs more time to reach a solution based on a common consensus. -- sg Am 03.03.2021 um 14:20 schrieb Glyn Normington: > > After discussion with Carsten, I aim to submit the current state of > our draft on Sunday 7 March so we have an updated draft to reference > in our meeting. > > If anyone would like to update it before then, please get your skates > on. :-) > > On 03/03/2021 08:01, Greg Dennis wrote: >> I would request that if some fit into the issues I've already made >> (there are a few), those issues be continued. >> >> Greg >> >> On Wed, 3 Mar 2021 at 7:37 pm, Carsten Bormann >> wrote: >> The next step should be to split Stefan’s issue into topics, and >> see where we are on each topic. >> I would expect some are mostly done by #46 already, some need >> more tweaks, and some need real work. >> I’d prefer to discuss actual (if embryonic) PRs on the latter >> ones as well. >> >> Grüße, Carsten >> >> >> > On 3. Mar 2021, at 06:14, Glyn Normington >> > > wrote: >> > >> > Apologies, but I had forgotten my blocking review of >> https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, >> > >but have now merged it. >> > >> > What's the plan for IETF 110? Will there be a PR to discuss, >> will we be discussing Stefan's excellent analysis, or what? >> > >> > Thanks, >> > >> > Glyn >> > >> > -- >> > Jsonpath mailing list >> > Jsonpath@ietf.org >> > https://www.ietf.org/mailman/listinfo/jsonpath >> >> >> >> -- >> Jsonpath mailing list >> Jsonpath@ietf.org >> https://www.ietf.org/mailman/listinfo/jsonpath >> >> > > > Virenfrei. www.avg.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > --------------3E1DBA514D4665DCB73CB3DA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit A lot has been achieved in the last days ... great. The set of terms in the current draft seems to be more consistent and less redundant now, thanks to Carsten.

I second Greg's proposal to continue already existing issues.

In indirect response to Daniel's posts "@ and the current element" with interesting aspects and links,  I would like to start a first issue. This probably needs more time to reach a solution based on a common consensus.
--
sg



Am 03.03.2021 um 14:20 schrieb Glyn Normington:

After discussion with Carsten, I aim to submit the current state of our draft on Sunday 7 March so we have an updated draft to reference in our meeting.

If anyone would like to update it before then, please get your skates on. :-)

On 03/03/2021 08:01, Greg Dennis wrote:
I would request that if some fit into the issues I've already made (there are a few), those issues be continued.

Greg

On Wed, 3 Mar 2021 at 7:37 pm, Carsten Bormann
The next step should be to split Stefan’s issue into topics, and see where we are on each topic.
I would expect some are mostly done by #46 already, some need more tweaks, and some need real work.
I’d prefer to discuss actual (if embryonic) PRs on the latter ones as well.

Grüße, Carsten


> On 3. Mar 2021, at 06:14, Glyn Normington <glyn.normington.work@gmail.com> wrote:
>
> Apologies, but I had forgotten my blocking review of https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/46, but have now merged it.
>
> What's the plan for IETF 110? Will there be a PR to discuss, will we be discussing Stefan's excellent analysis, or what?
>
> Thanks,
>
> Glyn
>
> --
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath

Virenfrei. www.avg.com


--------------3E1DBA514D4665DCB73CB3DA-- From nobody Wed Mar 3 18:41:28 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 E17333A0BDB for ; Wed, 3 Mar 2021 18:41:25 -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 uMyCa5VUw433 for ; Wed, 3 Mar 2021 18:41:24 -0800 (PST) Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 6522A3A0BDA for ; Wed, 3 Mar 2021 18:41:24 -0800 (PST) Received: by mail-wm1-x329.google.com with SMTP id o16so8114115wmh.0 for ; Wed, 03 Mar 2021 18:41:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=/vTp+1/jWK8GSZROLpbdRs2fgIlcT4SbEe9pNkuF5h4=; b=P3zCrAt6RFILPcBDgCZcaP8TX8lJSMltd9L/V/Ki6fTLKSw00OTn2pzeRWAbrjNNXq HwVZGaGPkQV6QTvKidJWPfSbYoGtfdFqiE0rXPsKLU663yXCXKzHG4fgS3Lqed1RjJl/ tmKUoJNnHUiVDhWRqsb9wzYPoldhOkclK0ivl+6zuzfA9JAmW4oiJpQ/mtLpHK850xcp B19tcrzHuCZIIixUOqn6mMEGEwEZ/HJxqmWpF6fBEfDFttj95efC3f5IFDc30wXPINPL d0y+X4l5jrof+IAocy2toYjGZNGlHBmfESFT6MZgWYOm4N8FTCBbaZH2DewfaWt7tAZF 9fDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=/vTp+1/jWK8GSZROLpbdRs2fgIlcT4SbEe9pNkuF5h4=; b=eyH/nfyX4lkjfRkiT4wyY1vn+Dx2pSNxdxgHmXQIsCD18MTa+fLbwJIm72bpjXRp/p cjOwvIgYXVeaJn60+VO1ODmj/HztjrlO5S/VoggD0WHI+r2da/h+8d1IbTHAEhTwLkaG lbDwFzLSZI2ScBEuhgCToP/FT8EYMd/Skfa4r5hfR3J6pQy9uUD/jQa/X8KHQ4XyoxSw 8dtQSyVTeg2uD4rEuX4xEtMQzIzcLkvsVDSj8Q+bN8q2f71CxdCnvuGWz9K2uUKOJ7DW KwwCQLaBOYCvXSBtC8MriLItS0KrkU5F/96CYY5lUtNJn80cvjerdHWxfiltCxjNyCwV x1PQ== X-Gm-Message-State: AOAM532AbgUcOn1Rcy0iqsbwFTTSKdAhtLpwKorXYIe9/tYW38KjpOB8 R6HPj3TG9DNyJ2lOxMl6ZUC1q17bhbwFifYJqTKnxluPWJX+HA== X-Google-Smtp-Source: ABdhPJwM4IAjkfYXKi+YSbCdVuMHPgRE0hQvWGrvIu6OzYmqStVGWTqxXCVtq/SuALv3EB5TB5FbsYLXAoZPbpcsQuQ= X-Received: by 2002:a1c:3c02:: with SMTP id j2mr1569510wma.92.1614825677320; Wed, 03 Mar 2021 18:41:17 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Wed, 3 Mar 2021 21:41:05 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] Comment on current draft: wildcard with bracket notation 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, 04 Mar 2021 02:41:26 -0000 The draft gives examples of using a wildcard with the bracket notation, e.g. $.store.book[*].author, but unless I've missed it, I don't see it covered in the grammar. The simplest solution would be to treat it symmetrically as a union element, i.e. union-element =/ "[" "*" "]" Not that a query like $.store.book[*,*] makes much sense, but some implementations support that, e.g. Goessner. Is the plan to also support filters and expressions as union elements? Referring to https://cburgmer.github.io/json-path-comparison/results/union_with_filter.html, six out of 41 implementations support union with filter elements. My current view is that it makes sense to treat everything symmetrically. Daniel From nobody Wed Mar 3 19:35:46 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 D76893A0E18 for ; Wed, 3 Mar 2021 19:35:43 -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, 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=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 Lgg8u4bwFNYy for ; Wed, 3 Mar 2021 19:35:40 -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 68D343A0E17 for ; Wed, 3 Mar 2021 19:35:40 -0800 (PST) Received: by mail-wr1-x429.google.com with SMTP id b18so19534136wrn.6 for ; Wed, 03 Mar 2021 19:35:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=IkPzy6vqILedLmDGXQENNvIaK4AV8Y/OHhobahPaQ6k=; b=YqTfaEeOgq0virrYScgEZDRQNxrJe9gpvIacaOL7Dxz3jnQdQAyF9g+6t2RgQljKVk WeCk5Yq6msoqBGRifW/QWYcU+pqLi3vdOC3F9c7Al1zcOXHsFxs2Adwy28XUek2knh2A 0wnx725BWLhgBsQ9V+julmvoTHRZVp9Zqh4UFHOR38H5NUublEKd4KkSz3U5kF5zV4ur Kwsu+OuGwnARQQxKioPQ/yJJfm6+/h8bAkRt7SN6pzL+2DD+D+WEIQB5wBPEWoznEpGo Az/6xiYV3m+/lMZ8vtbaFvzl7ezoei5Yp7//sCpQi8zx7ByH9YLwGPJ8+/Lbz1ju3TpX Eqhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IkPzy6vqILedLmDGXQENNvIaK4AV8Y/OHhobahPaQ6k=; b=oMyjJRoj9/bs5GrkJlSJ0JfZ1iQARElVrzwouZwYka9H0vq83gbBlydEK2+7Fs8s3h pAQMvGCTlCfWxOr0KM61bcJWgE9gou0GLt2PdEpwsh9Ex7zOrHSIIEa4+tsEC2J6ar5S 5PWrbViG12jiD/iIM86ubb2/0hMvo0X1eRcXmR2f54yQJoCEJCF5YNJwdR2NkudZqbOw OXmSOXI4VkHRmTxz9lDG8641mkB86g/m418lqs1K2I9eVhUm2gqI4ScpeLiO5zVW/Ixj EUmtZ7rG3b9/4x8FADH57+eHmCq4rNYECWO7Jaaa+AGaSOzVeMVU9jbRx4wV63QQMO9e 310Q== X-Gm-Message-State: AOAM530X1clRUQVgdA6xacZdgAd4ZNnSA1wHgjwHOwqFmspF3fFPDX+3 qmzNOwNES2p1HIFL6+d3lWw8+ZiKEfLZIREXQHa+GvJj8haEdQ== X-Google-Smtp-Source: ABdhPJxLLh4SXoAlHMfd6ckIrTOap1abeEfS5C2VpUVzaW8JgRM2E1Om5I/37eSeGf4KNG84EKOVK5dVt8sr9JmzFXw= X-Received: by 2002:adf:f0cb:: with SMTP id x11mr1696101wro.206.1614828936263; Wed, 03 Mar 2021 19:35:36 -0800 (PST) MIME-Version: 1.0 From: Daniel P Date: Wed, 3 Mar 2021 22:35:24 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] [jsonpath] Comment on current draft: normalized path 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, 04 Mar 2021 03:35:44 -0000 The draft says, in section 1.3, "Where a JSONPath processor uses JSONPath expressions as output paths, these will always be converted to normalized JSONPath expressions which employ the more general bracket-notation. [2] Bracket notation is more general than dot notation and can serve as a canonical form when a JSONPath processor uses JSONPath expressions as output paths." The definition of normalized path expression should be in terms of symbols defined in the grammar. Intuitively what we want is a path in the bracket notation with only non-negative indices and single quoted names allowed. But the grammar doesn't define bracket notation, it defines union and union-element. It seems to me it would be awkward to define normalized JSONPath expressions in terms of degenerate unions. Would it make sense to introduce a separate non-union bracket expression into the grammar to make it easier to express things like normalized path expressions precisely? Daniel From nobody Wed Mar 3 19:52:40 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 4281E3A0E7B for ; Wed, 3 Mar 2021 19:52:39 -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, 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=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 dWxuJSlMuopx for ; Wed, 3 Mar 2021 19:52:36 -0800 (PST) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 69C113A0E7A for ; Wed, 3 Mar 2021 19:52:36 -0800 (PST) Received: by mail-wr1-x432.google.com with SMTP id v15so26058821wrx.4 for ; Wed, 03 Mar 2021 19:52:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=CbUu70mMg+Dqa9xhvRCRulElYJ7Sj91OBvUoVSTKIQE=; b=sQjIsyAeyD7gUF7fvDXap6hNa2jMpfRkytfZSZpLbya9yL0vVGrT4G7Enc7J0zd7ei F938uGVyF2rfbXzNaUOCXz4pBgCmi5ixkV/kqKFDBdERkmzvNFoQyz9gOwVfDx4yh0CE 4DT8jTBJ9BW22PpG1lXpLlfiWg0cNyCC9N0lK/xhC6HFT59RsVkhATbKKk3+SsyYeLmW BwvmuDA7Q40LIAx64piZzQ6x+mSA/g+K2mHbEG70SyAIId5ap34B9zTJ92yhDEG1VRoi JR2Ruf0yF7YFgc8/Q9k2jQ6nigeulrN3A1uzEIh/yjaEAVAc4iUXJOrgP1PBl11hwSvD vujA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CbUu70mMg+Dqa9xhvRCRulElYJ7Sj91OBvUoVSTKIQE=; b=tXsd7cFx5HMB5k4rkCS6iuatDf36qt/g5kQSqKHKbOBite/mfk98HXdxLxPXPb5QwO 2j+r2ZDRnI/sh90X8yPbTMmEaoM1oiPU8qr1Uy8C2oPgjQ1NA92tXiw0k1kbyJtCiOWQ DwRQgkOkcmViX13T8rdG6B7tOm7BWNbB6axso5OYqlk7lazwLRhQ7FwmsgmzJBrfv8+a Kf+ZdVJHcLL6RJ8Kuwgap8lSGQI7PXqwiqOlNXCYmmNeVN1Y2ixe3nsv01xs46MyKPc4 VlGxW6zx/kqSQ9NW8d3GdnU8fblEMMyclat7kkLdUHjnITemvOVGMYOzxMFLEGuWiepR uw8A== X-Gm-Message-State: AOAM530sz7XoIh9hIhDRWJ8VMccRrMR2UcqdSTeS0t75A4vcliM+P4wv oJyC6E7Le+xF/j/iqIJIud66DTg7/pphEeXd7Y/iN6JndwGHeg== X-Google-Smtp-Source: ABdhPJwBFFWPQ1puNlFSR8OFEWh9jmlj7/vH+sEzmsrnwiVagMTZf+J/10RaI9sBg5Y8p/KNyVin+YR9UQsxsxRl44k= X-Received: by 2002:a05:6000:118c:: with SMTP id g12mr1667996wrx.353.1614829953576; Wed, 03 Mar 2021 19:52:33 -0800 (PST) MIME-Version: 1.0 From: Daniel P Date: Wed, 3 Mar 2021 22:52:21 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] Comment on current draft: position 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, 04 Mar 2021 03:52:39 -0000 The draft defines position as follows: "A JSON data item identical to or nested within the JSON data item to which the query is applied to, expressed either by the value of that data item or by providing a Normalized Path Expression as a JSONPath Output Path." I'm struggling to understand this sentence, especially the part "A JSON data item identical to or nested within the JSON data item to which the query is applied to". Position would be the location of the item and not the item itself, wouldn't it? How could position be expressed as the "value of the data item"? Wouldn't it always be given as a Normalized Path Expression? Incidentally, in section 1.3, the term "normalized JSONPath expressions" is used, I think for consistency the draft should stick to "Normalized Path Expression". Daniel From nobody Thu Mar 4 08:21:04 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 985BB3A0F0A for ; Thu, 4 Mar 2021 08:21:02 -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, RCVD_IN_DNSWL_BLOCKED=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=ispirata.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 WfvMbZL4mIBf for ; Thu, 4 Mar 2021 08:21:01 -0800 (PST) Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 2819C3A0F01 for ; Thu, 4 Mar 2021 08:21:01 -0800 (PST) Received: by mail-wm1-x329.google.com with SMTP id o2so9757531wme.5 for ; Thu, 04 Mar 2021 08:21:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ispirata.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=vrmhWs3W6hP/LWm7FrZrsZrbyWO3aqXESiN4GJYynr4=; b=QWD1XeRLDWyDeem2HhbFgWiwAFjPxahL9AQ+7+AApPI4+dReIaIn7qkgU4BkK7y57h pVVQifdBCm2C0hJ9OUbmri9heO1iSWyEaYN5gGUmVgbTAmmax3qNEWQIYIMi8CSoOLGe 2rUCaBGMkcnMRLvJhMA6Cvv9HXO931tIl6tc5C7756SixaFw1ep1n9KIHLRxjInFeK3W BTWOOLuhB5qOYF2O9l3t8lAGZpPYSmmxiAJcVdEvhDiBHfezrcN4rTdjDI0GRfTCSyO0 w9W2NsNpVrhV5vmeu174HpvKJzdGORlHFBSK+9zBT7mfxEWMEUJ6+gwHD4NUxw51iQVS KLsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=vrmhWs3W6hP/LWm7FrZrsZrbyWO3aqXESiN4GJYynr4=; b=H6YJauBSQszfXX9DzuG9Vh6ScFb+DmKpoJV6Ht6gxuyH79YdjuzG5w5BMmUxvKvxX1 PvkoM6DTRlxPVgQdzBMkByV6G4uoUYX9cn4quW4k7PhyVHXjNX22ZneSwmKkzlaMT8rZ sxqhw5ucGfJEQLan3oZZJY7vDfdmk3DkPZjDTUzt45LgO+cqFusMD2Vyd0TJl0wHhQps g201jiG53EM5VTSXlm1qlSwBb373D6vge5MiUKTqK9n83IohywFXrPVIVyhD5EXNWR5K i049JYOVd1jh5Sehg77A20JEkBQPU9zclho8V2aY7L/mqHetffl/7NvSX3rP2Npuxd23 XGdw== X-Gm-Message-State: AOAM533kTXuM35MrGOjMyXtzGzgYLppWqe6qH947oAcHEJHkM2eE3OIJ OKfBgbtOnLuKnDGoOjIU5fhck7VtwC8Ddyvqpwbr7DvrDwSZFg== X-Google-Smtp-Source: ABdhPJxR3iIb4dSEOYvW7bEz4khu7upRoPiaUHxGIK0X9B9bWo0GNFoY4gOKzhArFmjySNoiaVcZOx90ROEHbpst26s= X-Received: by 2002:a1c:2c05:: with SMTP id s5mr4703680wms.70.1614874859212; Thu, 04 Mar 2021 08:20:59 -0800 (PST) MIME-Version: 1.0 From: Davide Bettio Date: Thu, 4 Mar 2021 17:20:23 +0100 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 04 Mar 2021 16:21:03 -0000 Hello, I've been away from this mailing list for a while, therefore I apologize if a similar topic has been already discussed. I have the following use case and I'd like to understand how it can be addressed from the future JSONPath specification. I also apologize if this sounds a bit OT here, but I hope that the purpose of my point will be clearer at the end of this mail. I'm implementing a logic-less JSON templating system which makes use of JSONPath, so let's start with an example: Let's suppose I need to produce an array of objects such as ``` [ { "a": 1, "b": "test" }, { "a": 2, "b": "test" } ] ``` by using somekind of for-each construct on an input object such as: ``` { "b_value": "test", "a_values": [{"foo": 1}, {"foo": 2}] } ` therefore the template needs to access both the current item and the root item by using JSONPath expressions. At the moment I think there is a grey area about expressions which don't start with `$`, so I wonder if the following pseudo-template makes any sense: ``` [...] { "a": "{{ foo }}", "b": "{{ $.b_value }}" } [...] ``` Here above I made the assumption that when `$` (the root item) is not used the JSONPath is relative to some kind of current context. Another possibility is using "@" for this kind of purposes, e.g.: { "a": "{{ @.foo }}", "b": "{{ $.b_value }}" } So I think that the following 2 points need to be addressed: 1. Do we want to allow any kind of reference to any current context/current item with a standard (or prefered) approach (such as the mentioned relative JSONPath)? 2. Do we want to use paths without starting '$' or the '@' for this kind of purpose? My opinion here is that introducing a semantic difference between `$.something` and `something` makes sense, and it wouldn't break any existing semantic since in most of the cases current context == root context. Moreover that would justify accepting paths as `foo.bar` (without `$`) for a deeper reason than the mere compatibility with existing implementations. I'm looking forward to your opinions. Regards, Davide Bettio. From nobody Thu Mar 4 09:57:23 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 F065D3A134B for ; Thu, 4 Mar 2021 09:57:21 -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 2HTxsFZepFQR for ; Thu, 4 Mar 2021 09:57:18 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D7603A134A for ; Thu, 4 Mar 2021 09:57:18 -0800 (PST) Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Drz8r1fF9zyVy; Thu, 4 Mar 2021 18:57:16 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Thu, 4 Mar 2021 18:57:15 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 636573434.325142-9b7a9e7d3d42e3bd0c39fe02f13e0a4e Content-Transfer-Encoding: quoted-printable Message-Id: <75DBBA4A-42F9-47E9-B0E6-ED84F09D434F@tzi.org> References: To: Davide Bettio X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 04 Mar 2021 17:57:22 -0000 On 2021-03-04, at 17:20, Davide Bettio = wrote: >=20 > produce an array of objects such as Well, JSONpath is a bit like XPath, and a lot less like XSLT. (Although the latter certainly would be nice to have.) Gr=C3=BC=C3=9Fe, Carsten From nobody Thu Mar 4 12:03:05 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 7B1E93A156C for ; Thu, 4 Mar 2021 12:03:04 -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_FONT_LOW_CONTRAST=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 DJE8ZeJisw2P for ; Thu, 4 Mar 2021 12:03:02 -0800 (PST) Received: from sonic302-3.consmr.mail.bf2.yahoo.com (sonic302-3.consmr.mail.bf2.yahoo.com [74.6.135.42]) (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 5F3223A1579 for ; Thu, 4 Mar 2021 12:03:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614888180; bh=//GOjMJdVtsuzP+KW7sYHbNLpC3qY0CzSwI6MlTwuE4=; h=Date:From:To:Subject:References:From:Subject:Reply-To; b=nJp3amdwWnNN8gKC/8VaNWlv0QG9Ydla6JE5lEeWK6B4cg0OYTf8Pzg0QQYZjCsa87FBb0urW94n7JJen2D5gcm7IU9UB74FU8HAI5BnrWY+MqKrkU/5h792NQLUXOPldVpEDBzHSV539K4ShasaneXDF8gnE2HhB01A7VVXzCSS684xHbJINVbpc7dSOofWoqTGg8/d7x+GsGXwmSbf/QOGRaq7oyC6Kn1eluTiN9XdPnNTnQaHA+Qoy8lDUAs43iSZBkmN6EOLjpK0lUKEuHE5OZIyJA4D5UIaMeeMMgpbzOwCfOqsl1r20LMfAGPBBZm100Gc3TsL5/4pqSfRlA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614888180; bh=CScbP1LuOZVHrjW+ORb6344KzACQiJGHn/ARbnOSymP=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=sCzvnb8bbwYKNF7Sq3ixTcNcLZWyhGN+1AB7M/Kkm9RTpzyU0PxV7KnG1bspHd+FFhU5ofvTT1SBrKv5D4frYnOlkQUf8g4ZAyb27wnhxfjemptJiENY1GpBcbpGVIA0moBo8kzhT+2NADWdvtgQbX2dw7YHEjZudmMqIknnMZpRz9LQ2bzz/WWH3/1AjUBYlBxqHPXYQiphL0/eMjiR5HMfUXhI7RkAhubkwnIs+cwylZ8ixrwDBkhQ1u/dHIlvLP0pDYvzEKyZ669OYnoWDBJbG+6J0z71oj+7zP4OJoO1ZmZ4QNT/qNQRjaOowgAh5sUIGVLi5cR9y8YzFvU+ig== X-YMail-OSG: D6xu5c8VM1kxUygqDQn2D0ZAlAqWxxsOZl257PcKu6rRKNmjXMUoom5nZc5gqAh qjwX43NBYpxe9FD29iaBZsJXtZyOr2zSVoabdncSbkQBbIJN.i44KKlVVm2p7HJsFgSDD0nVEAp6 lXu1npPZuRXM8uxqkv2yU8I9OLv1e5ScFhmCtic9t.SfBm5LkqrVpm9bzeKEWixp5YVQ.xD773y8 nRIdBND3rKoOa7xKrtP497TTpniQwO3EsAs08xoqR3k.owLHwBFTIADA62YjFWe2xIc8Bvdvej4e mFrRk8nIGu7kshMy4LFwrFKxbu9PclciOqwjey.tQESeVoTrGUH1v9.rx07.FcRxZSC6aWa1qqIV QH.R0q9BK4YmEkb0cPwqWPR1oyblhcKHPlhIS1dxN4.iTAZq.LLAxLv37LRkecJ.tFumm3zS68aR UuGS.MNZVAzPVuzc6sHiSpdKESat.hAOXDH3XnvISZkRoaoJh.Bx9t43PBZwVrGEUDfdSZDKU_kB AMB9Zqb.GyxIYZk2jv5MSWB2fJf6Dve7aBImKfa.ZWryvKHrkYT.Lg6usFAZLdk22ImN_OdptIIq i2WY2p0ADvXpD9.4kUZHchHx2DisVOgBW4QK7arMf6IlEjhUbhzWZje7ClLIwz8P2YJEvArOSWeE 0ljuEmSlQstzQO6UIteg.SPOnKnvsRgBpdC5OO5NRsY6SyKe8mmgTmSN3v4Ct3AiGv0VXK3JHWa8 VLCiN.mD2invRWbMUUuqSOPQ6OeyFueTewdX83R_KkFNLVL8IGwv5Jx5u5T9w9HSAdg57MSHdwGT 3nYQIVlfuxSvhaSUdXVQwf6eaZEZXBV.mWq91dKRtT5bJg0qTk79tW7VAYruyG7rLQ8hcR0CF43D HtGhAA2JsWZrVJtNKhLZ481gtKmKgKQsZJgdNvhrZujfgT6KOzJgD7.QKKWJNUqcKxohrkwZwWSu hL0FpXaVjDa5FgyCNXTNh6UVt3dZyCXxUSjkKl7VKHb5Qv3aOCZg77DP8kVMkjSV4HjEkZMcXC_7 gloR9fKWeUunAFQy.ZHGyu4j_w8ziCW7Q8fco5_dc_8aTXc94p_D4ajl6bXUH.bRWNG3Hwg6Cf0J 2hbhFLED9R._mt__gvaziIbXSFRDMNlmhFlfJrmbRBujs6qpx5zyKi6pKk_KWDWgpNWwFgycUTG2 9hCzeGxstf0FrfO1B70j5_PyvykCBAfY8xE5uY8Rw1tTOqVlq5NE78DN4J2z4YO6VucwBKGdNQIz chJT2Uc4fy1rkJBpm0cGFkdJGdMQW1lWrMKcD7HZStZdQNivKNjruVX1qrIcNoBGedVh9I5FxtB5 i8W_xW_pbl0mkzqeO6kpkwNdfNijsROfpGOIhTjguOKzOmnWfOuTyo56a2AJxHCCZOl6acTu1AW1 peYjMWUBQLYuAVtXgLmsQx6W0T96OQK_hifmfpJO5yobTkwcBJBM.axHSa9H45ueWDVc_QBNPFY8 GU3Dwcwuz_gJRmTPRTORctjX5kLCKOOVVI7Qzh1PDoOalmoCb6A8hTO5QPC_pvxW2UGR.T2tJ07U SojQtseIBiLw6IZCMNOaCMgtdAIUotlSIFMeanMS4o1X009JehdReadl3uQw7fvo7tz4ya52ILb9 1S3ME2EKmESD0mxfz91FcyC55xlqifGdPlB1RClWOzN1EwQXFjeqaYSipWwKGPgd..hA.VswhsNZ zQjsv3wMA9r5gK6MkKJzK6IkhVIIjlI2_.5X5Va5XNj3DkHGa.w0gGXnrV5O4_yhAbb2kPU3RRkP hAUbhB6RQWIHz5Im7cS6wSqC5f_lwCMAo6dsYWDFwSRASfbwWeNwZXqNSD3SLpjJ1BieCtCoZAXG BbObeLglEkwAOgYWaqXG3Q08NSKAH15W4ZyRrQ8KB8NZuyx3OVdtNVeLrgxupr.eTNsVjadODQi9 vtBIa5HbxlQmH1jEMqwYrG1EgSK.vaRJ8N_3Yvuglt4vKVQYz8HuuP7Jj2tvY5kMEDmxklXRZs9z uM2Udjydi6fk7iY9gC2XqXbqs0Z5vr4a.1a13h7fsdpmblG7f8LSLsYQroD2eBw.j3R4d8dcn.Jp cWFkOLF8Zm8hw3jovn9CFVfmGWk5iHpQO2mvuX.yPeAPj41FgjWOYbZaroogo3dGxroEo31CZ_xK 7k.8626Hlu1g4VcC1G59kCsUlBiK.nBO8lsO7RKqeHRfe9ShEGkvl4vGWkMZbrNM618BgcJPmPn1 pL5w9fhXeqlDDezvUM3qT4KIOhHwk9FWk3j4za2hXlz4lasWGNJFnfMRe9FnGVH2rp.BH5ZFciUn FQYzs8XH8El0xlOAgJYA7FJN_sP_RMRYiH9ezM0kUySwLSFLkYSzH4ArrRzl9S5VqcYAWEr.PHzI xLZWrK0K31BjBYNLrAYWBv.0wa1FRlJzFh.Y- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.bf2.yahoo.com with HTTP; Thu, 4 Mar 2021 20:03:00 +0000 Date: Thu, 4 Mar 2021 20:02:58 +0000 (UTC) From: Greg Dennis To: "jsonpath@ietf.org" Message-ID: <8566793.463782.1614888178366@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_463781_1635611021.1614888178364" References: <8566793.463782.1614888178366.ref@mail.yahoo.com> X-Mailer: WebService/1.1.17712 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.192 Safari/537.36 Archived-At: Subject: [Jsonpath] I have an idea 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, 04 Mar 2021 20:03:05 -0000 ------=_Part_463781_1635611021.1614888178364 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'm still not sure why we're so stuck on using the email list for discussin= g specific changes to the specification, the source for which is stored on = GitHub.=C2=A0 Carsten has said that GitHub is archival, so it's an "approve= d" medium to have discussions.=C2=A0 Moreover, GitHub issues have been spec= ifically designed for the purpose of discussing the content of the reposito= ry, in our case, the specification document. Emails lose context.=C2=A0 The only thing linking one email to another is t= he subject line, and then the sent date.=C2=A0 Multiple threads can spin of= f, and one quickly loses context. But GitHub issues maintain that context in an easy-to-navigate interface.= =C2=A0 Moreover, they support Markdown formatting which allows more express= ion than plain-text emails.=C2=A0 (Yes, we can have HTML emails, but no one= 's using them.) So... to my idea. I propose that we use GitHub to orchestrate email discussion.=C2=A0 It's ac= tually quite simple: 1. Create a GitHub account for jsonpath@ietf.org.2. Subscribe that account = to the=C2=A0ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repository and co= nfigure the account to receive email updates on everything. Now have email archives on literally everything that you could want: issues= , PRs, build statuses, etc.=C2=A0 Additionally, people replying to those em= ails (assuming they use "reply all" to include the GitHub sender) would end= up on the source issue. For example, I create an issue.=C2=A0 GitHub sends an email to jsonpath@iet= f.org, which we all get.=C2=A0 Carsten wants to make a comment, so he repli= es to the email (just like he's always done), keeping the GitHub sender in = the recipients list.=C2=A0 Carsten's response is recorded on the GitHub iss= ue for people who want to track it there.=C2=A0 GitHub further sends and up= date to jsonpath@ietf.org, which we all get. Additionally, the Slack integration that I've set up posts to the workspace= 's #github channel.=C2=A0 I've been notified (as if the emails weren't enou= gh) that there's been activity in GitHub, so I can go check it out.=C2=A0 (= It actually has links and a preview of the content as well.)=C2=A0 I respon= d directly on GitHub, and it sends an update to jsonpath@ietf.org... which = we all get. I know that you're all probably tired of hearing me expound the benefits of= working in not-email.=C2=A0 I understand the need to have this discourse a= rchived in case it needs to be referenced later. There are tools that have been explicitly designed for maintaining threads = of specific topics for the purpose of enacting change to a specific domain.= =C2=A0 GitHub is one of those, and I suggest we use it to its full capacity= . Emails were not designed for this.=C2=A0 GitHub was.=C2=A0 Let's use it. Greg P.S. If you have an idea that is a bit rough around the edges, and you want= to knock the corners off before proposing your well-rounded proposal in an= issue, email is good for that. ------=_Part_463781_1635611021.1614888178364 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm still not sure why we're so s= tuck on using the email list for discussing specific changes to the specifi= cation, the source for which is stored on GitHub.  Carsten has said th= at GitHub is archival, so it's an "approved" medium to have discussions.&nb= sp; Moreover, GitHub issues have been specifically designed for the purpose= of discussing the content of the repository, in our case, the specificatio= n document.

Emails lose context.  The only thing li= nking one email to another is the subject line, and then the sent date.&nbs= p; Multiple threads can spin off, and one quickly loses context.

But GitHub issues maintain that context in an easy-to-navigate inte= rface.  Moreover, they support Markdown formatting which allows more e= xpression than plain-text emails.  (Yes, we can have HTML emails, but = no one's using them.)

So... to= my idea.

<idea>

I = propose that we use GitHub to orchestrate email discussion.  It's actu= ally quite simple:

1. Create a GitHub account for jsonpat= h@ietf.org.
2. Subscribe that a= ccount to the ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repository= and configure the account to receive email updates on everything.

Now have email archives on literally everything that you could w= ant: issues, PRs, build statuses, etc.  Additionally, people replying = to those emails (assuming they use "reply all" to include the GitHub sender= ) would end up on the source issue.

For example, I create= an issue.  GitHub sends an email to jsonpath@ietf.org, which we all g= et.  Carsten wants to make a comment, so he replies to the email (just= like he's always done), keeping the GitHub sender in the recipients list.&= nbsp; Carsten's response is recorded on the GitHub issue for people who wan= t to track it there.  GitHub further sends and update to jsonpath@ietf= .org, which we all get.

Additionally, the Slack integrati= on that I've set up posts to the workspace's #github channel.  I've be= en notified (as if the emails weren't enough) that there's been activity in= GitHub, so I can go check it out.  (It actually has links and a previ= ew of the content as well.)  I respond directly on GitHub, and it send= s an update to jsonpath@ietf.org... which we all get.

<= ;/idea>

I know that you're all probably tired of hea= ring me expound the benefits of working in not-email.  I understand th= e need to have this discourse archived in case it needs to be referenced la= ter.

There are tools that have been explicitly designed f= or maintaining threads of specific topics for the purpose of enacting chang= e to a specific domain.  GitHub is one of those, and I suggest we use = it to its full capacity.

Emails were not designed for thi= s.  GitHub was.  Let's use it.

Greg

P.S. If you have an idea that is a bit rough around the edges, and = you want to knock the corners off before proposing your well-rounded propos= al in an issue, email is good for that.

------=_Part_463781_1635611021.1614888178364-- From nobody Thu Mar 4 13:08:04 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 7BF313A16AB for ; Thu, 4 Mar 2021 13:08:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 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_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 tlZoynF7JLH0 for ; Thu, 4 Mar 2021 13:08:00 -0800 (PST) Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0: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 806033A16AA for ; Thu, 4 Mar 2021 13:08:00 -0800 (PST) Received: by mail-pg1-x536.google.com with SMTP id x29so11477115pgk.6 for ; Thu, 04 Mar 2021 13:08:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k8ONMzACVM2FN9IKk5CEMoMlDo7a0SgvRmjZWT+Lz1I=; b=iRv3do78dYMnFyfcRQ75DWKmo54B9oZP+Of3LP2RJj7BwBtTJNwW+4TO5zpbE+Pslr qnGxMa+rU198a+VR6fRgDgoWBYDMMSegnswT7cpbcDDyr4E6AlJFgLySMQUD6UNQOJ36 7//0zBk3v4iMioaR7GghQDn8miltChHXKdbt7g1GmvWZ+5w35loGVhJhj+TALGhrlE/e WvNxhXGO17WrFzuGwwYdzhgSinzAW0Pj4OSucOCsaLoQQRRd6d44AiRB7sU9WmYhC6zc KYUKmT7vnSag+AWQcMPwomrZ7CmOtyFtBdRfNDZnPTnRx+1Mgsoq0eIUNTXcaVDvQLLY l48A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k8ONMzACVM2FN9IKk5CEMoMlDo7a0SgvRmjZWT+Lz1I=; b=UOn9hQQrIVmK/5fpaQ5f+eZRC6edzRK2uC4Q3VdCTZDy8jt1+V8nAIksLPcmlZqoSi ZHRZBLYYKI72jt1ZJEMc8J8HpJeJ9V18WvOkurQSTD9zQM7nWGEXGcssME73ozBledpS D3lhZxNvJr9lQOrJ1V7Eyp4xDe/v9bJC1stEsYNaHBcSyTito9l2royme8w8k8t/YwpH 82ClpsBe/xARUiUwh4Ozm1UdW+eO9JbuTmuXuBv0Q/o8+Rs8r1VAcbJw0VYMlmJQljUd UaUzZ7Cc0Z+6Nx8LD79uqdYCUvGVZbbFf6i3ZSpNplrd3CQ3IytP+SJkiFQ8lbMDFSvc uB7A== X-Gm-Message-State: AOAM531zC0RyQQa4n89SQq78SiyNJ3sijOIWlAp27v9B1B2VROEZX0li gf2WfAVWGRTornQ12Sc2XNCTtvXiKuPvURuHSq+isebf X-Google-Smtp-Source: ABdhPJydp4mJUdKtmDsFx42e3It7a0+knbA8PVQj1z1LHswoEmgekJ2aCk2R5BRYvNtjFBJ/qSX1sauLfGQJtfsJQGU= X-Received: by 2002:aa7:9341:0:b029:1ee:ee87:643a with SMTP id 1-20020aa793410000b02901eeee87643amr5512036pfn.55.1614892078598; Thu, 04 Mar 2021 13:07:58 -0800 (PST) MIME-Version: 1.0 References: <8566793.463782.1614888178366.ref@mail.yahoo.com> <8566793.463782.1614888178366@mail.yahoo.com> In-Reply-To: <8566793.463782.1614888178366@mail.yahoo.com> From: Glyn Normington Date: Thu, 4 Mar 2021 21:07:47 +0000 Message-ID: To: Greg Dennis Cc: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000b20d4e05bcbc5c35" Archived-At: Subject: Re: [Jsonpath] I have an idea 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, 04 Mar 2021 21:08:03 -0000 --000000000000b20d4e05bcbc5c35 Content-Type: text/plain; charset="UTF-8" While I endorse using GitHub issues for particular, focussed discussions, I wonder whether subscribing this mailing list to all GitHub activity would be counterproductive, particularly for those of us who prefer to subscribe to GitHub activity directly. Another option would be to create a separate jsonpath-github@ietf.org mailing list which could be used to subscribe to GitHub. This would give us archival and would not force participation onto subscribers to this list. Just a thought... On Thu, 4 Mar 2021, 20:03 Greg Dennis, wrote: > I'm still not sure why we're so stuck on using the email list for > discussing specific changes to the specification, the source for which is > stored on GitHub. Carsten has said that GitHub is archival, so it's an > "approved" medium to have discussions. Moreover, GitHub issues have been > specifically designed for the purpose of discussing the content of the > repository, in our case, the specification document. > > Emails lose context. The only thing linking one email to another is the > subject line, and then the sent date. Multiple threads can spin off, and > one quickly loses context. > > But GitHub issues maintain that context in an easy-to-navigate interface. > Moreover, they support Markdown formatting which allows more expression > than plain-text emails. (Yes, we can have HTML emails, but no one's using > them.) > > So... to my idea. > > > > I propose that we use GitHub to orchestrate email discussion. It's > actually quite simple: > > 1. Create a GitHub account for jsonpath@ietf.org. > 2. Subscribe that account to > the ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repository and configure > the account to receive email updates on everything. > > Now have email archives on literally everything that you could want: > issues, PRs, build statuses, etc. Additionally, people replying to those > emails (assuming they use "reply all" to include the GitHub sender) would > end up on the source issue. > > For example, I create an issue. GitHub sends an email to > jsonpath@ietf.org, which we all get. Carsten wants to make a comment, so > he replies to the email (just like he's always done), keeping the GitHub > sender in the recipients list. Carsten's response is recorded on the > GitHub issue for people who want to track it there. GitHub further sends > and update to jsonpath@ietf.org, which we all get. > > Additionally, the Slack integration that I've set up posts to the > workspace's #github channel. I've been notified (as if the emails weren't > enough) that there's been activity in GitHub, so I can go check it out. > (It actually has links and a preview of the content as well.) I respond > directly on GitHub, and it sends an update to jsonpath@ietf.org... which > we all get. > > > > I know that you're all probably tired of hearing me expound the benefits > of working in not-email. I understand the need to have this discourse > archived in case it needs to be referenced later. > > There are tools that have been explicitly designed for maintaining threads > of specific topics for the purpose of enacting change to a specific > domain. GitHub is one of those, and I suggest we use it to its full > capacity. > > Emails were not designed for this. GitHub was. Let's use it. > > Greg > > P.S. If you have an idea that is a bit rough around the edges, and you > want to knock the corners off before proposing your well-rounded proposal > in an issue, email is good for that. > > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > --000000000000b20d4e05bcbc5c35 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
While I endorse using GitHub issues for particular, focus= sed discussions, I wonder whether subscribing this mailing list to all GitH= ub activity would be counterproductive, particularly for those of us who pr= efer to subscribe to GitHub activity directly.

<= div dir=3D"auto">Another option would be to create a separate jsonpath-github@ietf.org mailing list wh= ich could be used to subscribe to GitHub. This would give us archival and w= ould not force participation onto subscribers to this list. Just a thought.= ..

On Thu, 4 Mar 2021, 20:03 Greg Dennis, <gregsdennis=3D40yahoo.com@dmarc.ietf.org> wrot= e:
I= 'm still not sure why we're so stuck on using the email list for di= scussing specific changes to the specification, the source for which is sto= red on GitHub.=C2=A0 Carsten has said that GitHub is archival, so it's = an "approved" medium to have discussions.=C2=A0 Moreover, GitHub = issues have been specifically designed for the purpose of discussing the co= ntent of the repository, in our case, the specification document.

Emails lose context.=C2=A0 The only= thing linking one email to another is the subject line, and then the sent = date.=C2=A0 Multiple threads can spin off, and one quickly loses context.

But GitHub issues maintain = that context in an easy-to-navigate interface.=C2=A0 Moreover, they support= Markdown formatting which allows more expression than plain-text emails.= =C2=A0 (Yes, we can have HTML emails, but no one's using them.)

So... to my idea= .

<idea&g= t;

I propose that we use G= itHub to orchestrate email discussion.=C2=A0 It's actually quite simple= :

1. Create a GitHub accou= nt for jsonpath@ietf.org.
2. Subscribe that accoun= t to the=C2=A0ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repository and = configure the account to receive email updates on everything.

Now have email archives on literally ev= erything that you could want: issues, PRs, build statuses, etc.=C2=A0 Addit= ionally, people replying to those emails (assuming they use "reply all= " to include the GitHub sender) would end up on the source issue.

For example, I create an issue= .=C2=A0 GitHub sends an email to jsonpath@ietf.org, which we all get.=C2= =A0 Carsten wants to make a comment, so he replies to the email (just like = he's always done), keeping the GitHub sender in the recipients list.=C2= =A0 Carsten's response is recorded on the GitHub issue for people who w= ant to track it there.=C2=A0 GitHub further sends and update to jsonpath@iet= f.org, which we all get.

Additionally, the Slack integration that I've set up posts to the wo= rkspace's #github channel.=C2=A0 I've been notified (as if the emai= ls weren't enough) that there's been activity in GitHub, so I can g= o check it out.=C2=A0 (It actually has links and a preview of the content a= s well.)=C2=A0 I respond directly on GitHub, and it sends an update to json= path@ietf.org... which we all get.

</idea>

I k= now that you're all probably tired of hearing me expound the benefits o= f working in not-email.=C2=A0 I understand the need to have this discourse = archived in case it needs to be referenced later.
There are tools that have been explicitly designed = for maintaining threads of specific topics for the purpose of enacting chan= ge to a specific domain.=C2=A0 GitHub is one of those, and I suggest we use= it to its full capacity.

= Emails were not designed for this.=C2=A0 GitHub was.=C2=A0 Let's use it= .

Greg

P.S. If you have an idea that is a bit rough = around the edges, and you want to knock the corners off before proposing yo= ur well-rounded proposal in an issue, email is good for that.

--
Jsonpath mailing list
J= sonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonp= ath
--000000000000b20d4e05bcbc5c35-- From nobody Thu Mar 4 13:14: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 DB3BE3A16B7 for ; Thu, 4 Mar 2021 13:14:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 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_FONT_LOW_CONTRAST=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 9dZWDUTYCywV for ; Thu, 4 Mar 2021 13:14:22 -0800 (PST) Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 EFDF13A16B8 for ; Thu, 4 Mar 2021 13:14:21 -0800 (PST) Received: by mail-pf1-x42e.google.com with SMTP id r5so19853105pfh.13 for ; Thu, 04 Mar 2021 13:14:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2xn2k08yBefz8cjKyin7d3UowO1WG4zLQjHHmNK6kt0=; b=Dk4FTtzdhfWgdmZg8mZY//oVHRx/23c3gVrdgEl14lTnc0bKqWtcz5H0hxTPNUjoZg HFjSbZkiSuiAxqd17j1ARnCxW863CB9Qka5Ja6/EyzHwL4ugiuRNKgtklvFKaywMaRBQ Ou1wfTm6HBI4wU1npLkdxNtprea4A3dygdIegiXU5w9+StF4FL4Ut5M7Rp7HGEUgSo7M 4InivRiMgXkfrw4Sr4DfFN4JMQK9ohWrDzcUg2SAXuMnXeqgi1PrUk30kjKnZF+9iHbX 3lTPl2ZwrPzKgv6x/CpOnVfmYASWu+n5XXQNQdaAry2A6ggeHt8MT9vyucKK++0c3nki u3gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2xn2k08yBefz8cjKyin7d3UowO1WG4zLQjHHmNK6kt0=; b=JgpGaN17v+wt4joFEgYJy9Xq3pqeeeVFPycClcKYIyoiQq2cY3GnxW9yqikwAXFaoQ o/yp3XvjtMPz/CJ3w95C9Wq9VtqFZG7x9Y6d/YaCDeoNhHTF1QrWsXAQLHXD7/IM0/um dkqq747lWjwzTNhAhbuRvSeaosDyWMMFEFiXE3wYGGjaCW+S5YTtIEnRFhjfEFj3T30i IOWIVSaKXLQkdSwf6IvnZuONtEZnGTGH3WBWuCqlluzOuJjdyV9OIm5oMz8naferLdy9 EO2FLGNKG/yMY6OIlxZwg3QnWhPdlG1LaFrv4DKCzGgG342MRizOM9cwlnGITNc88L/f /wMA== X-Gm-Message-State: AOAM530toQpDgY+d2kCbR1e1XFRUJFfZ651DWJ4qGLIu5IPA66kQEjQB d7l/YVHvVd6pNOh9up9BkS8nSZ+WPD8gZaYRKuMPri8Z X-Google-Smtp-Source: ABdhPJyAiBOoy30Hlf94K0XgLjObgUZC/gXgzra52Gve2dy+ZjZJCjDGO/KJocPHti23feLMcKSbuyZ+pZLYeMtV528= X-Received: by 2002:a65:6a43:: with SMTP id o3mr3982654pgu.297.1614892460688; Thu, 04 Mar 2021 13:14:20 -0800 (PST) MIME-Version: 1.0 References: <8566793.463782.1614888178366.ref@mail.yahoo.com> <8566793.463782.1614888178366@mail.yahoo.com> In-Reply-To: From: Glyn Normington Date: Thu, 4 Mar 2021 21:14:09 +0000 Message-ID: To: Greg Dennis Cc: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="0000000000007849a805bcbc7395" Archived-At: Subject: Re: [Jsonpath] I have an idea 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, 04 Mar 2021 21:14:24 -0000 --0000000000007849a805bcbc7395 Content-Type: text/plain; charset="UTF-8" I should add that one of the advantages of GitHub issues is the ability to *unsubscribe* from issues which are (no longer) of interest. This would be trickier in a mailing list subscribed to all GitHub issues - another reason for a separate list. On Thu, 4 Mar 2021, 21:07 Glyn Normington, wrote: > While I endorse using GitHub issues for particular, focussed discussions, > I wonder whether subscribing this mailing list to all GitHub activity would > be counterproductive, particularly for those of us who prefer to subscribe > to GitHub activity directly. > > Another option would be to create a separate jsonpath-github@ietf.org > mailing list which could be used to subscribe to GitHub. This would give us > archival and would not force participation onto subscribers to this list. > Just a thought... > > On Thu, 4 Mar 2021, 20:03 Greg Dennis, 40yahoo.com@dmarc.ietf.org> wrote: > >> I'm still not sure why we're so stuck on using the email list for >> discussing specific changes to the specification, the source for which is >> stored on GitHub. Carsten has said that GitHub is archival, so it's an >> "approved" medium to have discussions. Moreover, GitHub issues have been >> specifically designed for the purpose of discussing the content of the >> repository, in our case, the specification document. >> >> Emails lose context. The only thing linking one email to another is the >> subject line, and then the sent date. Multiple threads can spin off, and >> one quickly loses context. >> >> But GitHub issues maintain that context in an easy-to-navigate >> interface. Moreover, they support Markdown formatting which allows more >> expression than plain-text emails. (Yes, we can have HTML emails, but no >> one's using them.) >> >> So... to my idea. >> >> >> >> I propose that we use GitHub to orchestrate email discussion. It's >> actually quite simple: >> >> 1. Create a GitHub account for jsonpath@ietf.org. >> 2. Subscribe that account to >> the ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repository and configure >> the account to receive email updates on everything. >> >> Now have email archives on literally everything that you could want: >> issues, PRs, build statuses, etc. Additionally, people replying to those >> emails (assuming they use "reply all" to include the GitHub sender) would >> end up on the source issue. >> >> For example, I create an issue. GitHub sends an email to >> jsonpath@ietf.org, which we all get. Carsten wants to make a comment, >> so he replies to the email (just like he's always done), keeping the GitHub >> sender in the recipients list. Carsten's response is recorded on the >> GitHub issue for people who want to track it there. GitHub further sends >> and update to jsonpath@ietf.org, which we all get. >> >> Additionally, the Slack integration that I've set up posts to the >> workspace's #github channel. I've been notified (as if the emails weren't >> enough) that there's been activity in GitHub, so I can go check it out. >> (It actually has links and a preview of the content as well.) I respond >> directly on GitHub, and it sends an update to jsonpath@ietf.org... which >> we all get. >> >> >> >> I know that you're all probably tired of hearing me expound the benefits >> of working in not-email. I understand the need to have this discourse >> archived in case it needs to be referenced later. >> >> There are tools that have been explicitly designed for maintaining >> threads of specific topics for the purpose of enacting change to a specific >> domain. GitHub is one of those, and I suggest we use it to its full >> capacity. >> >> Emails were not designed for this. GitHub was. Let's use it. >> >> Greg >> >> P.S. If you have an idea that is a bit rough around the edges, and you >> want to knock the corners off before proposing your well-rounded proposal >> in an issue, email is good for that. >> >> -- >> Jsonpath mailing list >> Jsonpath@ietf.org >> https://www.ietf.org/mailman/listinfo/jsonpath >> > --0000000000007849a805bcbc7395 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I should add that one of the advantages of GitHub issues = is the ability to *unsubscribe* from issues which are (no longer) of intere= st. This would be trickier in a mailing list subscribed to all GitHub issue= s - another reason for a separate list.

On Thu, 4 Mar 2021, 21:07 Glyn Normi= ngton, <glyn.normingto= n.work@gmail.com> wrote:
While I endorse using GitHub issues for particular, focussed= discussions, I wonder whether subscribing this mailing list to all GitHub = activity would be counterproductive, particularly for those of us who prefe= r to subscribe to GitHub activity directly.

Another option would be to create a separate jsonpath-g= ithub@ietf.org mailing list which could be used to subscribe to GitHub.= This would give us archival and would not force participation onto subscri= bers to this list. Just a thought...

On Thu, 4 Mar 2021, 20:03 Greg De= nnis, <gregsdennis=3D40yahoo.com@dmarc.ietf.org> wrote:
I'= ;m still not sure why we're so stuck on using the email list for discus= sing specific changes to the specification, the source for which is stored = on GitHub.=C2=A0 Carsten has said that GitHub is archival, so it's an &= quot;approved" medium to have discussions.=C2=A0 Moreover, GitHub issu= es have been specifically designed for the purpose of discussing the conten= t of the repository, in our case, the specification document.

Emails lose context.=C2=A0 The only thi= ng linking one email to another is the subject line, and then the sent date= .=C2=A0 Multiple threads can spin off, and one quickly loses context.
=

But GitHub issues maintain that= context in an easy-to-navigate interface.=C2=A0 Moreover, they support Mar= kdown formatting which allows more expression than plain-text emails.=C2=A0= (Yes, we can have HTML emails, but no one's using them.)

So... to my idea.

<idea>

I propose that we use GitHub = to orchestrate email discussion.=C2=A0 It's actually quite simple:

1. Create a GitHub account for= jsonpath@ietf.org.
2. Subscribe that = account to the=C2=A0ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repositor= y and configure the account to receive email updates on everything.

Now have email archives on litera= lly everything that you could want: issues, PRs, build statuses, etc.=C2=A0= Additionally, people replying to those emails (assuming they use "rep= ly all" to include the GitHub sender) would end up on the source issue= .

For example, I create an= issue.=C2=A0 GitHub sends an email to jsonpath@ietf.org, whi= ch we all get.=C2=A0 Carsten wants to make a comment, so he replies to the = email (just like he's always done), keeping the GitHub sender in the re= cipients list.=C2=A0 Carsten's response is recorded on the GitHub issue= for people who want to track it there.=C2=A0 GitHub further sends and upda= te to jsonpath@ietf.org, which we all get.

Additionally, the Slack integration that I&#= 39;ve set up posts to the workspace's #github channel.=C2=A0 I've b= een notified (as if the emails weren't enough) that there's been ac= tivity in GitHub, so I can go check it out.=C2=A0 (It actually has links an= d a preview of the content as well.)=C2=A0 I respond directly on GitHub, an= d it sends an update to jsonpath@ietf.org... which we all get.

</idea>
I know that you're all probably tired of heari= ng me expound the benefits of working in not-email.=C2=A0 I understand the = need to have this discourse archived in case it needs to be referenced late= r.

There are tools that ha= ve been explicitly designed for maintaining threads of specific topics for = the purpose of enacting change to a specific domain.=C2=A0 GitHub is one of= those, and I suggest we use it to its full capacity.

Emails were not designed for this.=C2=A0 GitHub= was.=C2=A0 Let's use it.

Greg

P.S. If you have = an idea that is a bit rough around the edges, and you want to knock the cor= ners off before proposing your well-rounded proposal in an issue, email is = good for that.

--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/lis= tinfo/jsonpath
--0000000000007849a805bcbc7395-- From nobody Thu Mar 4 13:16:04 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 2087E3A16C2 for ; Thu, 4 Mar 2021 13:16:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 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_FONT_LOW_CONTRAST=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 H6OihXsXztr0 for ; Thu, 4 Mar 2021 13:16:01 -0800 (PST) Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 27AAB3A16BC for ; Thu, 4 Mar 2021 13:16:01 -0800 (PST) Received: by mail-pl1-x631.google.com with SMTP id z7so16885515plk.7 for ; Thu, 04 Mar 2021 13:16:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O7a9m5t1azmDFQTBWksZdIKLmoLNd+sxSKCLGX5OWl0=; b=JojQKjb4C0vgsykxaljmIP/A1tbmXfHMaezkoLqP0xpD2mNRNdF/DFaic3mo6JS+1i jPeMKDanaS2ioeBQ/yrdyRvkvVQ5wGWoncdk1Wkv/TCw/S42Y/ydM9MqkqR2s6a4P/8V 2RhPs0slrRHCnvOxYcqSPetxsu9mi0pF3mgf31gYZ/mn3oAUnfukFBbI4XmSXd9gk5mK xrbL7YNcokSpxeY1HMZH1vy8hvq91nHvxUCJH922dgiCviENTp+J41kHa3uZc2UROWSe 9cBsbmGv55rCG+rzO0YP+RIrSZguTsyjRmyMD7I3nd/mU5YWH+reKsD9g6TecOXafe4i 8YiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O7a9m5t1azmDFQTBWksZdIKLmoLNd+sxSKCLGX5OWl0=; b=IDSPF48VTvbY+0XlHS3AGtwwR8gsfG1sXXNHEX6VzjQ/1nBZpbolZDY156S7KROYh7 JK9uF4CTOpizzvGm61QanXXu3EXUKmig6SlrlfWISDm4EvICTmmy5DJOcf0M5LvX8tll lplZJaXKDk5rKMAvDXs4eFu24Gi1/NCs70l8LhU3xT/ooBuBR+6W9QHgBZEN5fBFDZF9 k8G0sYUZUiPs0KY0Ob0jtZXseH6AU9UWZmxZj9xRp4tgKMYv2CO9z28yu4c8xRq7ASa2 ASEenExN3dj3On/jV5l3dioh1Y/pYhEpgtpfYKAhovj+So69rG5fApQdo/RRMZlWQ1py uJhw== X-Gm-Message-State: AOAM530pysjCYeekQlqGdmPODompq8sLSSun8Z7pQMHOLwQVeNH6VoyK BMaDvvXujIIhn4pl6SkzjeK4QSRTU7Ls2KkKmICtvuBl X-Google-Smtp-Source: ABdhPJxA/ufBaHQTzEvVSMxAyqOkveeBqC78puUxI3c8cZqJd1LQgFGO/HrH5w0BX215fh8pwHE6hDpHrhQv6hZuj2U= X-Received: by 2002:a17:90a:7d0a:: with SMTP id g10mr6584047pjl.3.1614892560109; Thu, 04 Mar 2021 13:16:00 -0800 (PST) MIME-Version: 1.0 References: <8566793.463782.1614888178366.ref@mail.yahoo.com> <8566793.463782.1614888178366@mail.yahoo.com> In-Reply-To: From: Glyn Normington Date: Thu, 4 Mar 2021 21:15:49 +0000 Message-ID: To: Greg Dennis Cc: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="00000000000065547205bcbc799f" Archived-At: Subject: Re: [Jsonpath] I have an idea 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, 04 Mar 2021 21:16:03 -0000 --00000000000065547205bcbc799f Content-Type: text/plain; charset="UTF-8" Whoops: I meant "... *unsubscribe* from issues which are not (any longer) of interest". On Thu, 4 Mar 2021, 21:14 Glyn Normington, wrote: > I should add that one of the advantages of GitHub issues is the ability to > *unsubscribe* from issues which are (no longer) of interest. This would be > trickier in a mailing list subscribed to all GitHub issues - another reason > for a separate list. > > On Thu, 4 Mar 2021, 21:07 Glyn Normington, > wrote: > >> While I endorse using GitHub issues for particular, focussed discussions, >> I wonder whether subscribing this mailing list to all GitHub activity would >> be counterproductive, particularly for those of us who prefer to subscribe >> to GitHub activity directly. >> >> Another option would be to create a separate jsonpath-github@ietf.org >> mailing list which could be used to subscribe to GitHub. This would give us >> archival and would not force participation onto subscribers to this list. >> Just a thought... >> >> On Thu, 4 Mar 2021, 20:03 Greg Dennis, > 40yahoo.com@dmarc.ietf.org> wrote: >> >>> I'm still not sure why we're so stuck on using the email list for >>> discussing specific changes to the specification, the source for which is >>> stored on GitHub. Carsten has said that GitHub is archival, so it's an >>> "approved" medium to have discussions. Moreover, GitHub issues have been >>> specifically designed for the purpose of discussing the content of the >>> repository, in our case, the specification document. >>> >>> Emails lose context. The only thing linking one email to another is the >>> subject line, and then the sent date. Multiple threads can spin off, and >>> one quickly loses context. >>> >>> But GitHub issues maintain that context in an easy-to-navigate >>> interface. Moreover, they support Markdown formatting which allows more >>> expression than plain-text emails. (Yes, we can have HTML emails, but no >>> one's using them.) >>> >>> So... to my idea. >>> >>> >>> >>> I propose that we use GitHub to orchestrate email discussion. It's >>> actually quite simple: >>> >>> 1. Create a GitHub account for jsonpath@ietf.org. >>> 2. Subscribe that account to >>> the ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repository and configure >>> the account to receive email updates on everything. >>> >>> Now have email archives on literally everything that you could want: >>> issues, PRs, build statuses, etc. Additionally, people replying to those >>> emails (assuming they use "reply all" to include the GitHub sender) would >>> end up on the source issue. >>> >>> For example, I create an issue. GitHub sends an email to >>> jsonpath@ietf.org, which we all get. Carsten wants to make a comment, >>> so he replies to the email (just like he's always done), keeping the GitHub >>> sender in the recipients list. Carsten's response is recorded on the >>> GitHub issue for people who want to track it there. GitHub further sends >>> and update to jsonpath@ietf.org, which we all get. >>> >>> Additionally, the Slack integration that I've set up posts to the >>> workspace's #github channel. I've been notified (as if the emails weren't >>> enough) that there's been activity in GitHub, so I can go check it out. >>> (It actually has links and a preview of the content as well.) I respond >>> directly on GitHub, and it sends an update to jsonpath@ietf.org... >>> which we all get. >>> >>> >>> >>> I know that you're all probably tired of hearing me expound the benefits >>> of working in not-email. I understand the need to have this discourse >>> archived in case it needs to be referenced later. >>> >>> There are tools that have been explicitly designed for maintaining >>> threads of specific topics for the purpose of enacting change to a specific >>> domain. GitHub is one of those, and I suggest we use it to its full >>> capacity. >>> >>> Emails were not designed for this. GitHub was. Let's use it. >>> >>> Greg >>> >>> P.S. If you have an idea that is a bit rough around the edges, and you >>> want to knock the corners off before proposing your well-rounded proposal >>> in an issue, email is good for that. >>> >>> -- >>> Jsonpath mailing list >>> Jsonpath@ietf.org >>> https://www.ietf.org/mailman/listinfo/jsonpath >>> >> --00000000000065547205bcbc799f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Whoops: I meant "...=C2=A0*unsubscribe* from issues which are not (any longer) of i= nterest".

On Thu, 4 Mar 2021, 21:= 14 Glyn Normington, <g= lyn.normington.work@gmail.com> wrote:
I should add that one of the advantages of GitH= ub issues is the ability to *unsubscribe* from issues which are (no longer)= of interest. This would be trickier in a mailing list subscribed to all Gi= tHub issues - another reason for a separate list.

On Thu, 4 Mar 2021, 21:07 = Glyn Normington, <glyn.normington.work@gmail.com> wro= te:
While I endor= se using GitHub issues for particular, focussed discussions, I wonder wheth= er subscribing this mailing list to all GitHub activity would be counterpro= ductive, particularly for those of us who prefer to subscribe to GitHub act= ivity directly.


On Thu, 4 Mar 2021, 20:03 Greg Dennis, <gregsde= nnis=3D40yahoo.com@dmarc.ietf.org> wrote:
I'm sti= ll not sure why we're so stuck on using the email list for discussing s= pecific changes to the specification, the source for which is stored on Git= Hub.=C2=A0 Carsten has said that GitHub is archival, so it's an "a= pproved" medium to have discussions.=C2=A0 Moreover, GitHub issues hav= e been specifically designed for the purpose of discussing the content of t= he repository, in our case, the specification document.

Emails lose context.=C2=A0 The only thing lin= king one email to another is the subject line, and then the sent date.=C2= =A0 Multiple threads can spin off, and one quickly loses context.

But GitHub issues maintain that con= text in an easy-to-navigate interface.=C2=A0 Moreover, they support Markdow= n formatting which allows more expression than plain-text emails.=C2=A0 (Ye= s, we can have HTML emails, but no one's using them.)

So... to my idea.

<idea>

I propose that we use GitHub to o= rchestrate email discussion.=C2=A0 It's actually quite simple:

1. Create a GitHub account for jsonpath@ietf.org.
2. Subscribe= that account to the=C2=A0ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath rep= ository and configure the account to receive email updates on everything.

Now have email archives on = literally everything that you could want: issues, PRs, build statuses, etc.= =C2=A0 Additionally, people replying to those emails (assuming they use &qu= ot;reply all" to include the GitHub sender) would end up on the source= issue.

For example, I cre= ate an issue.=C2=A0 GitHub sends an email to jsonpath@= ietf.org, which we all get.=C2=A0 Carsten wants to make a comment, so h= e replies to the email (just like he's always done), keeping the GitHub= sender in the recipients list.=C2=A0 Carsten's response is recorded on= the GitHub issue for people who want to track it there.=C2=A0 GitHub furth= er sends and update to jsonpath@ietf.org, which we= all get.

Additionally, th= e Slack integration that I've set up posts to the workspace's #gith= ub channel.=C2=A0 I've been notified (as if the emails weren't enou= gh) that there's been activity in GitHub, so I can go check it out.=C2= =A0 (It actually has links and a preview of the content as well.)=C2=A0 I r= espond directly on GitHub, and it sends an update to jsonpath@ietf.org... w= hich we all get.

</idea= >

I know that you'r= e all probably tired of hearing me expound the benefits of working in not-e= mail.=C2=A0 I understand the need to have this discourse archived in case i= t needs to be referenced later.

There are tools that have been explicitly designed for maintaining th= reads of specific topics for the purpose of enacting change to a specific d= omain.=C2=A0 GitHub is one of those, and I suggest we use it to its full ca= pacity.

Emails were not de= signed for this.=C2=A0 GitHub was.=C2=A0 Let's use it.

Greg

P.S. If you have an idea that is a bit rough around the edges, = and you want to knock the corners off before proposing your well-rounded pr= oposal in an issue, email is good for that.

--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/= mailman/listinfo/jsonpath
--00000000000065547205bcbc799f-- From nobody Thu Mar 4 13:32: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 259F83A1708 for ; Thu, 4 Mar 2021 13:32:00 -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 I8Pan2PPCd21 for ; Thu, 4 Mar 2021 13:31:56 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8E0D3A1706 for ; Thu, 4 Mar 2021 13:31:55 -0800 (PST) Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Ds3wS4cCrzyVN; Thu, 4 Mar 2021 22:31:52 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Thu, 4 Mar 2021 22:31:52 +0100 Cc: Greg Dennis , jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 636586311.2707731-f6c43ae7fc8cfa8edc7b7cc44af67f22 Content-Transfer-Encoding: quoted-printable Message-Id: <8704D5E1-17D3-4DE4-8985-E063DFB9E67D@tzi.org> References: <8566793.463782.1614888178366.ref@mail.yahoo.com> <8566793.463782.1614888178366@mail.yahoo.com> To: Glyn Normington X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] I have an idea 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, 04 Mar 2021 21:32:00 -0000 Please check RFC8874, specifically https://www.rfc-editor.org/rfc/rfc8874.html#name-monitoring-activity I=E2=80=99m neutral to a jsonpath-issues list =E2=80=94 I=E2=80=99m = already watching the repo. Getting the automatic summary in place is a no-brainer, though. (The repo should be converted to Martin Thomson=E2=80=99s template so we = get among others the benefit of some archiving of issues as well.) Gr=C3=BC=C3=9Fe, Carsten > On 2021-03-04, at 22:07, Glyn Normington = wrote: >=20 > While I endorse using GitHub issues for particular, focussed = discussions, I wonder whether subscribing this mailing list to all = GitHub activity would be counterproductive, particularly for those of us = who prefer to subscribe to GitHub activity directly. >=20 > Another option would be to create a separate jsonpath-github@ietf.org = mailing list which could be used to subscribe to GitHub. This would give = us archival and would not force participation onto subscribers to this = list. Just a thought... >=20 > On Thu, 4 Mar 2021, 20:03 Greg Dennis, = wrote: > I'm still not sure why we're so stuck on using the email list for = discussing specific changes to the specification, the source for which = is stored on GitHub. Carsten has said that GitHub is archival, so it's = an "approved" medium to have discussions. Moreover, GitHub issues have = been specifically designed for the purpose of discussing the content of = the repository, in our case, the specification document. >=20 > Emails lose context. The only thing linking one email to another is = the subject line, and then the sent date. Multiple threads can spin = off, and one quickly loses context. >=20 > But GitHub issues maintain that context in an easy-to-navigate = interface. Moreover, they support Markdown formatting which allows more = expression than plain-text emails. (Yes, we can have HTML emails, but = no one's using them.) >=20 > So... to my idea. >=20 > >=20 > I propose that we use GitHub to orchestrate email discussion. It's = actually quite simple: >=20 > 1. Create a GitHub account for jsonpath@ietf.org. > 2. Subscribe that account to the = ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath repository and configure = the account to receive email updates on everything. >=20 > Now have email archives on literally everything that you could want: = issues, PRs, build statuses, etc. Additionally, people replying to = those emails (assuming they use "reply all" to include the GitHub = sender) would end up on the source issue. >=20 > For example, I create an issue. GitHub sends an email to = jsonpath@ietf.org, which we all get. Carsten wants to make a comment, = so he replies to the email (just like he's always done), keeping the = GitHub sender in the recipients list. Carsten's response is recorded on = the GitHub issue for people who want to track it there. GitHub further = sends and update to jsonpath@ietf.org, which we all get. >=20 > Additionally, the Slack integration that I've set up posts to the = workspace's #github channel. I've been notified (as if the emails = weren't enough) that there's been activity in GitHub, so I can go check = it out. (It actually has links and a preview of the content as well.) = I respond directly on GitHub, and it sends an update to = jsonpath@ietf.org... which we all get. >=20 > >=20 > I know that you're all probably tired of hearing me expound the = benefits of working in not-email. I understand the need to have this = discourse archived in case it needs to be referenced later. >=20 > There are tools that have been explicitly designed for maintaining = threads of specific topics for the purpose of enacting change to a = specific domain. GitHub is one of those, and I suggest we use it to its = full capacity. >=20 > Emails were not designed for this. GitHub was. Let's use it. >=20 > Greg >=20 > P.S. If you have an idea that is a bit rough around the edges, and you = want to knock the corners off before proposing your well-rounded = proposal in an issue, email is good for that. >=20 > --=20 > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > --=20 > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath From nobody Fri Mar 5 01:59:39 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 46D713A22AF for ; Fri, 5 Mar 2021 01:59:37 -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, RCVD_IN_DNSWL_BLOCKED=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=ispirata.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 3iA-wT7ut_Pu for ; Fri, 5 Mar 2021 01:59:35 -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 B61723A22AE for ; Fri, 5 Mar 2021 01:59:35 -0800 (PST) Received: by mail-wr1-x429.google.com with SMTP id e10so1363022wro.12 for ; Fri, 05 Mar 2021 01:59:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ispirata.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VpzeRUSuyzs5NYAjpVTcpsWOciel445cNU8+xdRj+t0=; b=eVx2BUVjv4q+DcVdSnDaG5YUFxquw7BP9PpKJPMn/mTlSOj5Jr7NuUM+ORJHorsjYl 6rY4cKw/xv5eNxT47e5y2gmG7Wa9lhyrVhnighmQBlPs7+ssJzNhQ0fEtqY0uwYfqQx3 8KrDBS8UtcLfcmxGiwV2f8jLH0RL9e2QuDq6jlbSPQDfbl8CFF676ziE3cQ8A4fSruxb fSmPU0EnIw2wViVPwGFvAkKKBBpMEf4arhMuZcVAhvXmBeS6T2ECHR8CIg+y351sxlEM pHu6YRWU95amHgpmPNCOM+8H367+SwbB6ncQHmckJJ8nZQvKEqRCPrTmoa7+GbJ72MhU 74PQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VpzeRUSuyzs5NYAjpVTcpsWOciel445cNU8+xdRj+t0=; b=e81EY5PKqLN8rejBgw8NABoytIyaIxq26ew2EeuNwA+tSngrDs1aOD40jFSZ0ZWYII s1o59B+k7vePzYLb8W0iT/gNpP68gZLrMLp85+vvt9PCiQKtH6pF8knxwb4m8KulGKz9 Jqq/V3QcfqViRLsRrDeApzytwEmpgZ/qOVLaZenYr2LTRFrzuy9xuHSraSeKwGaxV0Dy gdTZkI6YSjFG2q+sfk2hBsERllu5FmBRIH2+MT5kg8vDFmEV5VBhfmslVMJOEt4XiTzD 8gZzAnWc9+hJzVrjCyQK6VxhJSLDYH30GWaMdSc9y1NUzr3uw/nxk/FamwvR7BQoQxG6 PeVQ== X-Gm-Message-State: AOAM530VdCYloIgzIPXrBRd5HLJkhF6d0G9DumkNsu34Y4aFBHNNZYzH 1ZjSkvifCbnf9pEsgMti9/bkfs3Ta9hX0sM98kk3LQ== X-Google-Smtp-Source: ABdhPJxzQpND0MWQsx9aCVIG8hrdhkn5HRPrAJg9t2Sko9VAquHEZSSm7TyfmhhhjMztKOz4i29T/yyM3MKF1n7cm+I= X-Received: by 2002:adf:c186:: with SMTP id x6mr8604253wre.253.1614938373501; Fri, 05 Mar 2021 01:59:33 -0800 (PST) MIME-Version: 1.0 References: <75DBBA4A-42F9-47E9-B0E6-ED84F09D434F@tzi.org> In-Reply-To: <75DBBA4A-42F9-47E9-B0E6-ED84F09D434F@tzi.org> From: Davide Bettio Date: Fri, 5 Mar 2021 10:58:57 +0100 Message-ID: To: Carsten Bormann Cc: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 05 Mar 2021 09:59:37 -0000 Hello, > Well, JSONpath is a bit like XPath, and a lot less like XSLT. I'm aware of this and I also agree, however I still need to understand if we may support any kind of semantic for accessing any current item/current context rather than the root item (which is identified by $), which are the points 1 and 2 of my previous mail. On 2021-03-04, at 17:20, Davide Bettio wrote: > So I think that the following 2 points need to be addressed: > 1. Do we want to allow any kind of reference to any current > context/current item with a standard (or prefered) approach (such as > the mentioned relative JSONPath)? > 2. Do we want to use paths without starting '$' or the '@' for this > kind of purpose? Clearly I don't need to discuss any templating language at the moment here, but I brought it as a practical example which is useful to explain why I need to understand if we are going to support relative JSON Paths. Furthermore I'd like to understand what kind of opinion people have on paths that are not starting with $. Regards, Davide Bettio. From nobody Fri Mar 5 05:03:03 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 914743A2507 for ; Fri, 5 Mar 2021 05:03:01 -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 xPBzmWqbrZom for ; Fri, 5 Mar 2021 05:02:59 -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 A7AD43A2504 for ; Fri, 5 Mar 2021 05:02:59 -0800 (PST) Received: by mail-wr1-x429.google.com with SMTP id b18so2002240wrn.6 for ; Fri, 05 Mar 2021 05:02:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=YA66dgm4cTIAJjCPbc2WFZA2Kw6+CzbbEWir87aHNUM=; b=Y7DPxZ1wX2pdYpsU+wZEDE+e41kZ/UOW+l/X8Yl0RGvgct4JH5ROOdXzB21IPwk2Ve HvROT9mQXBkSVoatOBPhfuA8izO2UI2MWQDVu9vec2nizAuL/os0TUqCsn0jNcYG311z UinbiO7zALIQvGQdnUXFZoGf9DGCvWhb16fd3WcoCHL4aDLIdWrwH+/gC3FvV45xLeOG NPLHcrtd2O5T/cVD+gZCh7Air7QdMEh/vQZeYwQzCoMWWbwkKAltTcqtufRd8Fe793QO 6xpGj9zzHpUYSLY2rIm6liK7CojGedDql/ri24gYYd9vTZS5r3dvJ9Bfq/4pdevxIS9b caRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=YA66dgm4cTIAJjCPbc2WFZA2Kw6+CzbbEWir87aHNUM=; b=UBltzwD/llaP5cLYpSHmm6NNB93YByAAvHsh0t2CWFEu4G1FdQV0DCDI197Q/QZEMU +Tqip4SZU1PL56PajVODARm9mwRGpDpcMgQMBlZSM15YOxi4aLrdRGe8NaHs6utOByBB bk9uY4x73N/VZNcFYy8t5ajCz4t+Az1ApIFHm4fY6oSWUlaD5rBMs3SN+qcjH3DEP3J7 Ra8VC4XZ5krfDTgq0ZdAci0G7jZKbAqqcbcg5u6sfw1KGf6sff9CIKt+8/8SiMJJGOvR 7P8vWrKaPqU2sIauhEbjN13kceOTUMd8EpGTMGWRX1XXKf/RToAxSfjtcxlESAxKfpnU nFKg== X-Gm-Message-State: AOAM532U60k8StdCxENc+RsKOW1TI04BOswpcNuKlR1wPN0wJCXwyAro GBSdSuCOoybj6SFfT+/A5qhJZt7OrRkbZWsHF8v12tVjbHA= X-Google-Smtp-Source: ABdhPJyZl63XN3cvBRoLQM6f95cD5bzZrCnFEtGchW8bNvT33lmITmYWqVQSKtqCJiPnw9qh7ocv664ZLXFSrYxw/FI= X-Received: by 2002:a5d:4ac4:: with SMTP id y4mr9159451wrs.86.1614949372438; Fri, 05 Mar 2021 05:02:52 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Fri, 5 Mar 2021 08:02:41 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 05 Mar 2021 13:03:02 -0000 > From: Davide Bettio > > Here above I made the assumption that when `$` (the root item) is not > used the JSONPath is relative to some kind of current context. > > Another possibility is using "@" for this kind of purposes, > If I understand this post correctly, the only use you would make of a "$", "@" or "" at the front of a JSONPath expression is as a flag to determine what JSON instance to pass to a JSONPath select function. As far as the JSONPath select function is concerned, "$.foo" and "@.foo" and "foo" would mean exactly the same thing, the JSONPath select function doesn't know anything about your "current context", it knows about its current instance, which is the instance that you've passed as an argument. That being the case, why wouldn't you simply keep a flag as a separate item in your template for that purpose? Daniel From nobody Fri Mar 5 07:14: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 A207C3A2687 for ; Fri, 5 Mar 2021 07:14:47 -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 hrwHSff9zwrZ for ; Fri, 5 Mar 2021 07:14:46 -0800 (PST) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 B86213A2686 for ; Fri, 5 Mar 2021 07:14:45 -0800 (PST) Received: by mail-wm1-x332.google.com with SMTP id u187so1750394wmg.4 for ; Fri, 05 Mar 2021 07:14:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=gAd3KAziTZsgWq1l/JweEFkUl8nmOdEbBTRsKpqp+jc=; b=kmXX4No+zJdhnPtzYltdqSige+8B+YLk48VUmHmqNt5UaRJ54yK5pJ+N12SuIzl8kG eyszXZEUCWJuV1jrWTFExQubJf1cuGa8ZIdGaxsoCcYMfIzhmcQts7CFvdGYnLL3ynXa tjlKb6ANBWJdGY2QipMCQaU22wU7J5cYC3E0hUNldXUO9qonmee3ESaf+UnqqIphMWb+ aSPK3IIGxkB2wQUn3ScqFNeKDxWW4VeYzgxqlALtu3dSGeJIHO8Hi6nsG/e7/Fk52I27 u5F6clTeyAVqlPIJzJG2o5EAv9XODS9ENqtS6mS0dayuP1jDumBHMyC2UmVdcmAi9uid yQ7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=gAd3KAziTZsgWq1l/JweEFkUl8nmOdEbBTRsKpqp+jc=; b=p8koz9KtOEI3xpRTm+IuHKhSb4pZaGngSG/AlFL1dMEfsuHNQhJPBqCC0Bo89nLtQS pbgcCIFefqifTbpL1F1gcY2sjEIFd5Qg5M8d41n0YGiNLDjViuReOnUP/ccTIEsSjXJW llMJhKcpL+Fm7rq8VEON9RXlcxawomh1ZBCKachrceoLpKkqKZstWrozuWEChkc2x3hG aV61kfCNo0XTvxMwtVnXIgVWTx+sWDNa/tS6p6aCrNfTarBVjall7VSegkuD3NmdwPxG uGaRhrlmwj7wXvY2Q+4MthCEjJeH5mmW6Y17YC9aiaezs5YOujLNUbP2q5ZqSRFON13p yv9A== X-Gm-Message-State: AOAM531mvBDs7PZi+U7CXORNj+qJ46fLfmdB6c9RoIWIbIIvpg4Ldz1z guWjLyrjVF14QvUTcjp/lJ5wQwbCr88RgFd7KpLm1Grq1DQgTQ== X-Google-Smtp-Source: ABdhPJzKDrCu2GzCSkSm76Z3G5UZFB58vYbm86r7L4L8M7nkP29Q9hxuK4o/03wD74mNKo1BpSz5PaSeJUmNnzYgK1Y= X-Received: by 2002:a1c:f30a:: with SMTP id q10mr9718301wmq.159.1614957278933; Fri, 05 Mar 2021 07:14:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Fri, 5 Mar 2021 10:14:27 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 05 Mar 2021 15:14:48 -0000 From: Davide Bettio > > Furthermore I'd like to understand what kind of opinion people have on > paths that are not starting with $. > Should the WG see it that way, I don't think there would be any difficulty, conceptual or technical, to support paths starting with @, understood as the current node. At the start of an expression, the value of the current node _is_ the JSON instance being evaluated by the JSONPath expression. In the course of the evaluation, the value the current node represents will change to reflect the node being evaluated. But I don't think allowing the root or current node symbol to be omitted is a good idea. Consider [{"true" : true}, {"false" : false}] The expression, $[?(@.true == true)], which has a filter that evaluates a JSONPath expression relative to the current node @, and compares it to the JSON literal value true, gives [{"true" : true}}] If we allowed the current node symbol @ to be omitted, the expression would be ambiguous. For comparison, JMESPath also uses the @ symbol to denote the current node, but requires that it be omitted except as a bare expression, being understood.The comparable expression in JMESPath would be [?(true == `true`)] but JMESPath delimits JSON literals with "`", so the ambiguity does not arise. There are some implementations that allow the dot notation without root (".foo"), see https://cburgmer.github.io/json-path-comparison/results/dot_notation_without_root.html) , and more that allow the dot notation without root and dot ("foo"), see https://cburgmer.github.io/json-path-comparison/results/dot_notation_without_root_and_dot.html. Personally, I'm not enthusiastic about that. My own view is that path syntax should follow common conventions, and should not vary depending on whether they appear in the main path or in expressions. Daniel Parker From nobody Fri Mar 5 11:15:23 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 77E153A0867 for ; Fri, 5 Mar 2021 11:15:21 -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 iEtj3H-VQ9Za for ; Fri, 5 Mar 2021 11:15:19 -0800 (PST) Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 DAD253A085E for ; Fri, 5 Mar 2021 11:15:19 -0800 (PST) Received: by mail-pf1-x42c.google.com with SMTP id 18so2811887pfo.6 for ; Fri, 05 Mar 2021 11:15:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v2BrncGUf5VO/oChliaAJs5I+UMlqNlfs0PYLgPkLOw=; b=av4BVvVdtGWN6NWGh8fehGF7MIJ8dr0i/hYM+NqD+l0XLeKBAZX8L5TsCCS289QSfp NeVHfb09fqA0LFa4df3SEljqpdUJesC5V0LaN/6IM1uw1lOl0ZFuxaAAM/jhwjfPvY34 KXOc20CyPNcddaToMVBi8kD9y5y28yca5Wud2jfWMElpxdTKOmip89rEoYrb7T++jM16 hTyGhhoIEVP2Ng8H28O2OBD4oVc8T45ls0grnSrIOwyO9hVl9YneaJno1tyx837wOblT HRg+jmjTxlE02mDsw+YoPa1GJTmRJSMEjeT+EdVWYDqgj8Bln6Q62axFxyHSwttPJm3y oySA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v2BrncGUf5VO/oChliaAJs5I+UMlqNlfs0PYLgPkLOw=; b=NxMP3IayDeSyUHEIcPBZPHQUkc9rGZ6qdVv/W+XnEjzsLOL7h2Dps3BnfWPJdJjl5X XYQIYRD1oLA4iqSqy7lWXDXWJBjJ+4ROOtfNMRExjyo9toQZqLExyA7FYdWFGC+mLOvt mE6Q9ySwGeM33Ej4kGONVfIm/jm39hduhonvnQwRKx7X32/RtLe3B8rRgtT9VhaGmJJd Li4NMG6Z4o38pLmCyKcfFTaZ4vTi4dnfwuDrfdsiyPHmRLe7guyZPNyPUubbUQzQBAko MYZeBhVgMLWdfwiHhqoDmWSAA5eBDC81/BGAm8lvPBZLWRRytkSV4THtMOrvW28RFlgv HZ4Q== X-Gm-Message-State: AOAM5304q3naKRwBQykbUmyJNcODMQJMwJWK5kYI0zxexk4KwQ5O4KfB t+0F438en3UaJOOz9TxIEt7MxSj9alisWz/yzjHQQhTR X-Google-Smtp-Source: ABdhPJxFVcI8+DUioWn+V3kpyqUHJ/KWTxJ3GcF/gBITj7YGP3RNMg6K9rJJr0BmftG125kHE4gIWyrd0MorJ0QQi8U= X-Received: by 2002:a63:43c6:: with SMTP id q189mr9991972pga.217.1614971717682; Fri, 05 Mar 2021 11:15:17 -0800 (PST) MIME-Version: 1.0 References: <75DBBA4A-42F9-47E9-B0E6-ED84F09D434F@tzi.org> In-Reply-To: From: Glyn Normington Date: Fri, 5 Mar 2021 19:15:07 +0000 Message-ID: To: Davide Bettio Cc: Carsten Bormann , jsonpath@ietf.org Content-Type: multipart/alternative; boundary="0000000000008e0d2005bccee7b2" Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 05 Mar 2021 19:15:22 -0000 --0000000000008e0d2005bccee7b2 Content-Type: text/plain; charset="UTF-8" In filter expressions, I think paths should start with @ or $. If we allow one of these to be elided, then the user has to remember which one can be elided. I'm sympathetic to optionally omitting the initial $ of a JSONPath expression because this is unambiguous, but I would be happy with $ being mandatory since this is consistent with the above rule for filter expressions. On Fri, 5 Mar 2021, 09:59 Davide Bettio, wrote: > Hello, > > > Well, JSONpath is a bit like XPath, and a lot less like XSLT. > > I'm aware of this and I also agree, however I still need to understand > if we may support any kind of semantic for accessing any current > item/current context rather than the root item (which is identified by > $), which are the points 1 and 2 of my previous mail. > > On 2021-03-04, at 17:20, Davide Bettio wrote: > > So I think that the following 2 points need to be addressed: > > 1. Do we want to allow any kind of reference to any current > > context/current item with a standard (or prefered) approach (such as > > the mentioned relative JSONPath)? > > 2. Do we want to use paths without starting '$' or the '@' for this > > kind of purpose? > > Clearly I don't need to discuss any templating language at the moment > here, but I brought it as a practical example which is useful to > explain why I need to understand if we are going to support relative > JSON Paths. > > Furthermore I'd like to understand what kind of opinion people have on > paths that are not starting with $. > > Regards, > Davide Bettio. > > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > --0000000000008e0d2005bccee7b2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
In filter expressions, I think paths should start with @ = or $. If we allow one of these to be elided, then the user has to remember = which one can be elided.

I'= ;m sympathetic to optionally omitting the initial $ of a JSONPath expressio= n because this is unambiguous, but I would be happy with $ being mandatory = since this is consistent with the above rule for filter expressions.
<= /div>
O= n Fri, 5 Mar 2021, 09:59 Davide Bettio, <davide.bettio@ispirata.com> wrote:
Hello,

> Well, JSONpath is a bit like XPath, and a lot less like XSLT.

I'm aware of this and I also agree, however I still need to understand<= br> if we may support any kind of semantic for accessing any current
item/current context rather than the root item (which is identified by
$), which are the points 1 and 2 of my previous mail.

On 2021-03-04, at 17:20, Davide Bettio <davide.bettio@ispirata.c= om> wrote:
> So I think that the following 2 points need to be addressed:
> 1. Do we want to allow any kind of reference to any current
> context/current item with a standard (or prefered) approach (such as > the mentioned relative JSONPath)?
> 2. Do we want to use paths without starting '$' or the '@&= #39; for this
> kind of purpose?

Clearly I don't need to discuss any templating language at the moment here, but I brought it as a practical example which is useful to
explain why I need to understand if we are going to support relative
JSON Paths.

Furthermore I'd like to understand what kind of opinion people have on<= br> paths that are not starting with $.

Regards,
Davide Bettio.

--
Jsonpath mailing list
J= sonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonp= ath
--0000000000008e0d2005bccee7b2-- From nobody Fri Mar 5 13:41:40 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 DF9B73A0EA7 for ; Fri, 5 Mar 2021 13:41:38 -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 eJS8icEfbPvG for ; Fri, 5 Mar 2021 13:41:37 -0800 (PST) Received: from sonic304-10.consmr.mail.bf2.yahoo.com (sonic304-10.consmr.mail.bf2.yahoo.com [74.6.128.33]) (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 7486F3A0D87 for ; Fri, 5 Mar 2021 13:41:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614980496; bh=cwnbK/h1Z/Mlxrjdui/TpalyYDReRqe+lbWovQ2eakM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=RiApWvCyP4rKE+sv7viX7/UW69SqdHAqDVLsKN30ye4PwQQG9LlcU88v8uBxHHISqsWuWZbYbqvIM+eahItxjclwFjTigwRlUyxMFxqeRYbWqiKlxAeEE4jH9mCxLLLCJf0zzlRqCQLHhKKCP0AN4FbTzNBpQbyh2mutme74olYuTQnKygNm0sOHE4+R0x7BknVm3oGYKE4PGAFq2HdQ7dGCYZwtopC1EjhBYU5ApOSksNbd4YA4kOg58STqSwy8UuqCYFvV1SXSrNcfsGTLyPrZpQvx8h4/bgIaSYUJHGNkA0WphJLY0YJNpVcqQYCEeMSCgpTtPco1msFjmrw7Og== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1614980496; bh=2zruqoxqjHC4ocVvBVvYigBUFvqpWqsEWklQ38a7m68=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=D0ONKBK/PRofcMLZlQwQZP/tomkBQfj4VdAh9xlhmrgVQZACo03T69Ynp40oDtmCVeJ9fK1MV8jEsLt3J8lez0oj3M/YTPvqevaS25TfrnhlyvRH5IPQ7OWv5WN1rlTKvtxqUsTNM7TUJJpiM5v5poYKkxykuq227wKM2xtUpl+DhIojDNBDFNyfoTUQ7qgOqTlhio7PWvuhBV9YPlrEk6KDnn4kHj6JX2ue9eV5jbd6CFrkObjdbrJzFk3EAYZQ87BOL0Vey0tDjRMz2+CqCAlUGfDF/O7RG87HNGhVAn33HSiDGWkZGDLNSPS9j77KX/ICwoudCnQ6iGmZkyJp2w== X-YMail-OSG: 4Tcv.4IVM1mWpzWp.Ysc4xxRA4dJm72VD9pGOwnVykfye71cdxCmRm_kT5OoHVO zzgSRRRTz5RxqV.krXtSgaf10QS21Hbovzz5LZYhrIdb6XZmpZYUP9ZwZ5IFGSLT7.5Wy7iwZo3. WBrbgq.W9jojSCxgjkeVxvzacuIUenXXf5mO2hqTwZDiOymoKmUkW1MCM6iH3VIrVFA1oCJZDdjb NKvzS5DHMfv9bw_mgaQQ3XvK0Evu6OrIJqYg4jGqGtTzmtRnQlppE9m1LAv9WHY5vu7tjsaxuOXn 5oQA_Hm6B5flvZCuotZpJS7G8Dp9iJatlrjR6R4dAPqcmS1caWQtgpx0CdAzazDhf12MX9__a2a9 cAnNZOinc4gbgiOnBjTTq3NXZw6XFg.4Tih_G6_eLupQx8EFAHU8z_lEN79p0aixY_vRkrcwIsmI pZN_buF7HjEZg9cdPkkvnIb_aX55VYTMnZN84DWIgsknV2Iou6Z1QbOdIutLKkbN7C5gl84fLtft cQydXwmPM3jrgJM6Zpoi_wGgZObOBuM3ltBmP68_Pt9pm10r0X5DQDRN56LzGenqPUMF.ZDPOFJX Nj7MWRAwpOHRNbkP7K_1uD5wFKm_OX2iwAsc4ibHkj3HmERb4jXaEqjcmNidU19iQFEx6S7N_OkQ Q0y.bLquH0qDsrCyawvOWJUB.w52LRun1E0F8PUsi7hKzmUkGA0G3j3npkwZK4lGQYcIfLHT0bCH RGbk87lL2a.SHwI1BvAIrOTjOnjmEheLBArtK6ea9Kc7vQuUM_K5AYCB.Ge5eT9WxKp.LhVDUsFS BQAfVk10xJsfbaSTKi9hre1ihqxKAzpVD5K33Mr2gj7w4TbsCi3Wc4TZwM0ofRJ_DjhXr3rHkI6V VyALPe5uudTubGXLB1HlhsTFRpuyAxVryb2GPbZJBOC.TPpSt1Cz_gu7_HiRSE9wZj59ZQAmIuas 6EgGOxCGZnYBrrf8OcOwm3kxS1_0gsAyC_S885yAkGGbEfPA.qvZXFXZfKMlewhqU4JRnAkW9qCo kIJd9MzLet_pjvaD3aXQbat2h75Ep1AML5C4PmWQzKZint4KKD0S4JoRfBvCTJixo0laJAuHajmS HU306e.BRVQFbhgzc6WiEnmtpEaPTWuVJrx6tMeA0OjdMfz2x0IT36EEH1T_VaeA4ymMY00l25A5 0ACRu2b_84U72hm.MdxCc64.GZixW2IEu.jrRYDaBlWyjbK8mcRi8_z2i5ZTBadlWRj1PYE3fDac o_rOkfzUg4rxBTxQJRcyO_.A4FDuIx.GMzRw2VcnsgdAMzNpCPGyI1tkbEJAitj3.ABKQrPHEDa3 UycpUm5djEaiCzFrauaVU1s5St0b7navelnJNMXvPybxcV0FAYZtAvEkZ7GLzgF0rhu4MSFidYkP xAkxnm8JyRHAsh73QFicUeVYLD3_rn2S1QcAT6QXLZyTxPEQ8Eh4V99..3bxv0Sj0nrLBp91PUnP Dd4t4qlwjLd9TVEM9RyITZtZ0AkufT.GoZBnloJJbM.0tMp1lbd_LEOSXkn__tq9FPGQkaaCre._ 2RzopMA6jU0eKLevjGlKfnxQLjm9PcbVJXMJ5d3upqNwg.jO1rzF2pMeOCeNtd.gB07CxyQ4hpXa M5xyzNxFc2uR4yEEXR3ncWRkO5qr3enn6U9u5.vlj64tfaO9m0w4eQTmJJfdChmA_RFAUDmCCPrc gxnaEJZmQMXlzYuIcS5YF2v0UN940_.ftF0Qzwm3hYpFEJmjSl8dNjXEHRdXsW3ZeQD1KW2_hFyf Ow3HrxPCijSgMN1zPWuumohB30mcV778an31VkdKoXLT.7xw8ITh63KR6FwGkEFseuS4jhxVV5o9 httmurZfDbn5JPEfI_VOQvLZVWruepI.jaR1ebkBAbJwbvinph9NtJcmK3cd50W6UvcEdYlFiCHw Bmt6CXB.6SSsRHQm8xRZewjD1f_29GnN0D4Ub33qhG0ZFpXURZXprLHNR8VzeaKseauKooshHuQP Fv6FgwOKUyqvVm21l6DjhDehvSzfZzuWgoVncWSTWuOlXnSZYBZCAo.bGCVDQYsYfhitPzer_lZ8 qEQ.fYrO7FPFkBccpFJieddyk.96DBUUpQpc6D6TnbhKkRpojDFsv79OFBwoq2fo35YhAj3NqKb8 bEAowHkPNiZoYyVXS1voE6r_wOzEDQE6kU5tSnreJUN2VlwkoL5hW1VlkCqBJqnjaTuLghp1VEQx 8GWjoBl6unegeAM.GWgacV0xSg4hcQzK7OOqDyEPDNcF8996emxnF0rmmq_nRZzLl2pSNe7yeNmv PBv9XlMn_FWryGOu2gxIVFYfjSC8uMYVXNsxyvsswdHhEqLAvC6XSY27Wz8F_2oe.YTjT3cVd_TE iuAD1XB7oel2Mthww8GliXKY6kVWo6NvZpQYbVHxB.ecrjjxX2eiEcRLgOfcIJcAQ5nBKdMw1BcO ePra2E4bRYmKvxLAbG8kyYDTOF_Gm5Fydfsun916jTX31kv.3HR.JFcPG8OGJgasHQFrfi6QCo5G 00u.a9LnxWWOVxc9zvVxkUACAuc8ECGcBNmlI5xeQcifEly38i7LTkVEnOXTjKzd9SOP_G.7.fsU z3vkmw27zUKHLLa8nsias8AtwAKAZIr1sdrNwFKwxAzCvoHmtIj.8WaFSusqFFL1jIAruu6KoAle nJPkim4yRLYNivIvYRI5se2Y_dgo6MEeK4dayTSIKtSfbI7NaNbARG6vXd16ydc6q27ON0sGxWko nsU4k3uXh0kLiplEt6iPDfNEqgff3jBxJn_bl6eCSNxyOuoRW6u7erfJ9jHbEAj9uALdqK8SWI0n QOl9mF.Gp X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Fri, 5 Mar 2021 21:41:36 +0000 Date: Fri, 5 Mar 2021 21:41:27 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: glyn.normington.work@gmail.com, Glyn Normington , Davide Bettio Cc: jsonpath@ietf.org, Carsten Bormann Message-ID: <1631371377.15534.1614980487713@mail.yahoo.com> In-Reply-To: References: <75DBBA4A-42F9-47E9-B0E6-ED84F09D434F@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_15533_464594336.1614980487712" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 05 Mar 2021 21:41:39 -0000 ------=_Part_15533_464594336.1614980487712 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Glyn and I are in agreement in this. (Sound the trumpets) On Sat, 6 Mar 2021 at 8:15 am, Glyn Normington wrote: -- Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath ------=_Part_15533_464594336.1614980487712 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Glyn and I are in agreement in this. (Sound the trumpets)

On Sat, 6 Mar 2021 at 8:15 am, Glyn Normington
<glyn.normington.work@gmail.com> wrote:
------=_Part_15533_464594336.1614980487712-- From nobody Sun Mar 7 09:25:04 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 861763A19A8 for ; Sun, 7 Mar 2021 09:25:01 -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, 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=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 RyEPG1XoeGCP for ; Sun, 7 Mar 2021 09:25:00 -0800 (PST) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 BC94A3A19A6 for ; Sun, 7 Mar 2021 09:24:59 -0800 (PST) Received: by mail-wr1-x42d.google.com with SMTP id h98so8911873wrh.11 for ; Sun, 07 Mar 2021 09:24:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=Tdf0da3ZsRZTq6mpAsiNJrhjf0M6xvaAiZJE+Z2BEvA=; b=djM6DgBMueAwIFlCvJ0b6HVBnDlNczKveoZFGqmMdJeS+/JCaavBmAqOiIwNuVv6Iy 5bEQ002FKWM3VmabIEEendVws2GX/clCl4uDEvRNnKuRtkbS75fwQfMa7qxweqs19zRG ORwotyHlN4+rlgzu7j5gz/WpDBB7cHRNamu590SkeFO0eaO69xoEIpVG20hkjlocwzqt zTAOmOKJPxkrO9LageQdye0eNFLD2+CYXeqvuiyc1mUxn0Wccx4BuY0sHUL3pW3sUo+I VUdT0GQl6YXLN2RPpTBlGgu+za/1NWQ0HGJBtjy77lf+OfPsU0Bex6G+gfSN7IKHQ6Ia B7cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=Tdf0da3ZsRZTq6mpAsiNJrhjf0M6xvaAiZJE+Z2BEvA=; b=FGQrhi0ONbz3FlaJQzTSjOZMeKg/T2ZekXYPWk3Z/+vZrKNBpIlTmrbRzFHe2GEukQ Wra6DKVPkRKtSffItkMcizZN8lMNgfmSihIwnU9uEa0ZgOzDYB7fPb2w2tt0SnKTRKfK o8GW7mDjlFX4qGPjLvHaj0zd3AEMjT5rJHet/f4DzvMabXBsrekbsl59/7Qf4qJm+WWq H9XTSQ+If7eTd7qwRBO90mcS4N2sxk37oQV2pFUT9HY1dQU8chKP0XdweACp6UdnhvSL 3j0ZyqFw5S2JOf9J2BeK9D94WuypCx19EXCW1x6/CSf83wfm1RrZFLjhcmfrVovN2PYz RJng== X-Gm-Message-State: AOAM530i/1thNUEP1wBuuWJZ0644wcuhrMLh/LfoojMhsp9918APliZu 4DY7FgU2n2T4dazczNZJoMhGKt+7ThY= X-Google-Smtp-Source: ABdhPJxDw5OJZR9iwOBZZN8g6VTXupEDybWPu8PbepLVF14teBAXh5z4Lff7YkyvTkpenX8C/QUGjw== X-Received: by 2002:adf:f0cb:: with SMTP id x11mr18626521wro.206.1615137896711; Sun, 07 Mar 2021 09:24:56 -0800 (PST) Received: from [192.168.1.95] (71.224.125.91.dyn.plus.net. [91.125.224.71]) by smtp.gmail.com with ESMTPSA id r10sm14550916wmh.45.2021.03.07.09.24.55 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 07 Mar 2021 09:24:55 -0800 (PST) To: jsonpath@ietf.org From: Glyn Normington Message-ID: <92823e05-b568-fc56-eb05-91c05568644d@gmail.com> Date: Sun, 7 Mar 2021 17:24:54 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [Jsonpath] draft-ietf-jsonpath-base-00 submitted 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, 07 Mar 2021 17:25:02 -0000 Following a conversation with Carsten, I submitted the current draft as draft-ietf-jsonpath-base-00 so that we have a well defined starting point for IETF 110 and for posterity. I created the branch "release-base-00" and the tag "base-00" for that version. Development can continue on the master branch where the document has the version "latest". Regards, Glyn From nobody Sun Mar 7 12:30:29 2021 Return-Path: X-Original-To: jsonpath@ietf.org Delivered-To: jsonpath@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 437CE3A1C4F; Sun, 7 Mar 2021 12:30:25 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: jsonpath@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.27.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jsonpath@ietf.org Message-ID: <161514902524.29123.9110964061100651891@ietfa.amsl.com> Date: Sun, 07 Mar 2021 12:30:25 -0800 Archived-At: Subject: [Jsonpath] I-D Action: draft-ietf-jsonpath-base-00.txt X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 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, 07 Mar 2021 20:30:25 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the JSON Path WG of the IETF. Title : JavaScript Object Notation (JSON) Path Authors : Glyn Normington Edward Surov Marko Mikulicic Fachhochschule Dortmund Filename : draft-ietf-jsonpath-base-00.txt Pages : 22 Date : 2021-03-07 Abstract: JSONPath defines a string syntax for identifying values within a JavaScript Object Notation (JSON) document. Contributing This document picks up the popular JSONPath specification dated 2007-02-21 and provides a normative definition for it. In its current state, it is a strawman document showing what needs to be covered. Comments and issues may be directed to this document's github repository (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath- jsonpath). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-jsonpath-base-00 https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Mar 7 20:46: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 B48CF3A20F0 for ; Sun, 7 Mar 2021 20:45:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.098 X-Spam-Level: X-Spam-Status: No, score=-1.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, XM_RANDOM=1.001] autolearn=no 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 BcU7ZCa2dgaz for ; Sun, 7 Mar 2021 20:45:58 -0800 (PST) Received: from sonic316-13.consmr.mail.bf2.yahoo.com (sonic316-13.consmr.mail.bf2.yahoo.com [74.6.130.123]) (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 A06AF3A2486 for ; Sun, 7 Mar 2021 20:45:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615178756; bh=gNKRf9FQPoK+p96OAE2R5/b1bnGeg7SkgotS5YMGdEY=; h=Date:From:Reply-To:To:Subject:References:From:Subject:Reply-To; b=JH0a7YhZGrxpO3Hqon0EQOlHfg0QpmweEMDIyLhYYOYtAbnzkzkWmzgvo/0yJMvHvZIeJdFQ1obUg0hyr2Wg7ak7JIvVIy43mLmYncZxDuHRPOSdV3G+l4KnDu8Fqe5CyDt0/0vT3jnrLkawAy2jgvaiogMKvOT8/3pmNUtNolwqK2OD/DziIqaulP+cPy0xwLaLX2o27Rr515l42TzvYANUufW1Cm2D6B0CLPO0nscjO4PF2eRdb3QPK7Uki9sfiFhklhpQ3kZygGTL3UV+a4CG9Vs/2+n4bCTm6vxmGVTKA5+absxpD7iPRr3TU1lvzjLlsQTPhpLwWfIwO5WkPw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615178756; bh=szz0IctkpkqjLYHr5pUolasBA9rnTB2YnxUU0g44FMB=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=W4LVJE3IypUZDLP6OkGvDVSTjmlkuJQMuAW67ZSgydB8clXlfPykITZGIhC+9S9Hk2gTFsDrVX5oVj4OFZXQ0SrIsFQ2rpVqz2nHGmnF3ngwWNOJajpMkh0Ww3XEy98gxyAA1I3BX7Fh+gsADpHR/kojWBxcqJ6eoGaaNVvA3SeffJMt27Ouv1bYrcuAK80MlINiFCO7D1RfzJGPx/ARs7QrZaAiViUBAn1Q9EUKg5vZknOAL2399gQ1isB96PeCUgh5h8lH9iPuCBjfsahCcB22i+AF+EZIilkioMakU80nzBDLgpfGr2mhaSzr89bj5JRbsedCPKGWy3e79FDbQw== X-YMail-OSG: qQx1UZ0VM1nf5p_QqodGjdXpO6t2hvZyLmII8dUHiMrIBOIz1wjcdxwO8gBLekQ wzBshAcgiTMszKsJekQH6wfXlHbs3ZwILZ1S6PF6WiC0VS5CFB2dUfGqOgm66NXjGv0rFGaUEFtT hlD.dJazACYOhpShemw1DjJr619c3.6HqXzjMAq2hG4ammhoZuLI1wEsyO4QA.EIKY.gq2VG8yo9 fIBBM7eS9XKPXyeHwVR_.6c1uigvUJkEggxbSkJMuRjsJaEggHOGP.AiVxk8XFnJHXD6duJivwhN TdmQHteNAtZUMDu9kFbiA058LJuBagloHC6orZHPSmA78RxnL.j4is6d.GSV.dEhj932Bz7u2UZN ndjckOtbxAI.h8P2_Hk.CJkP1yiK.YpHMPSm6DK6wZqJJxqa3WizUqL.jB8SgqOD6B6ERQnO64LC YwALeUO0zgrRyrLzDtVwYIfnTVN7UGt83e9tAd1Eh05dKyZ.q9ZsBH4tiYX3MnytnafI5vsxGJ1I u0KbnLTNVAUW5fDbrBOYNnnMkL2tQwjsYnP.hIJ7CoZk_9WXhz0Qil3orpW_ZJ684gEikjcEsJ37 wJe5z.4wgZDocq8XOI3ciBSp.O4bs4GBRcWSYX3kIETRNJZW0xGAi82UAzd7RTxAPzwf5JvFqOFa ZmUzG44tx8SYUZ3fpphDSYi0D6wa0Tk6i3qGpjRBoePoYkLXk6K8J9wgK7Nmar8VwTMEbfXoKVWT YnKDYYzXk3aHYyvt8MbUcvGZk5jBnnpNTHcFNc1R2GnNil.BWgqcqiuYYO1FnpclfL_j2fNjMmI9 ob6CbeZrORyAbmiUNmf9fDiKfHolSiP0IwltoqmTAyWiHaBy4nRRSjeaIejEyHuRnFFKqroBC3hc c_xGzO7Cfkq8NRAdQrxCvt1yTsTWbsJBmlbeytI7.u6Y42YQTPKHtZPJPGdBWMoYs354_AnK5Msv wnCiXqP0Tw5AlwwmVcfMo4ZqDOfKaGHe5Y6mJOOwPR0A_f5aY7MhtD2E.b0TzqURPM5Ebhhpd1WM .zQf4_TDI8hCw_TcG_kyYnQpqdQpIxG8EQQPtcfIisOmABY5qVA8wNwQlMqErlJmAKCi93uzI3mO 3p.0o1_hu2lfr_ohFukSMX7ZoCzckWbn9yIxJlIAn9hpjmzYPPgNGKbIRiy7c4oiW4RfJU696rMg nwkpo8MAz7pW9N6mb6dgmGexWTCtn9AH2qPN_U0gHOy0WptlIvSDpgDQYM_AyBnySWyb9wVVrXIB 4EDCS2JNbFP6i1a037PeJgJVncD8MqzosZCtUnqgc459W2E_2R8OgeTYfKzu.N.Pep2E8ab_hWBe o7nxu3sKLs5ieV5bgVEjBMQ2zmUMAECgbb3sff1H6Ql2bPcqMQm6YpEyXSm4mXwrth.EalIGuuff uHO8v8Du_1t8nIXaywOHpSxxeUWE2zcNaw5yrU.FbfR7oa0TNApNhbVjyoudvjiBvk8mlXwZ51M3 0TM.ffSy_BNPzA0704k83wG68f3LGlSyshTSxccwntbJKmnRXBALCQltGa7KKLN00vuSsDabMOR3 Ihvzw8XCaxDfhR6iiwOiONsm7NJiZDVDAko_qRzdDr7bRJ7dISrNLaNPQKpVfWz2TsgdmpoWvR0z hjr3vCt5kFSSEkN5P4EvYhosIoIhaZV0tRjmrFvr0H0rAzm.gJY8yJk9Qmsrj_PpYB33naYJ12WU b9Iaf94nY2t0wIGIeP5nW3IvQKUrIwkpQ_wcoMncslMtMPxmLRsopQEQlYzVVkoWpGZFejMQ0Zbz iryrxDXwXpWFQH_eZ8WOTjy7EvIhHCeTTVvkgAJf3FtfEJsAWARXJTrL9DUo2sUTD3RlmtX2Ohrn tsQyxPTnze.mgS8bXO0E1eYD0ZWCR1iJPQBaKqiBYqBY.ybL9aRPH8cOnEnPNjXrinslYoT8TEOs QzPwqcgjQqvwzkTwfd4_yomRph6c5ovrX90ffiKbj0kafs_s0HjP04_GEik0qeeDX.JxXDklpnwJ lO0kR06yUnp9FUcASCZ4LkViwXWgRQ1RuGfV3k2Y0PgNwCZYUTocJUJcALa3AZhw5mkwUfK3mfZ6 5lsLBJYlgrU91yR2vjMADfoFhXdbJNeBddsQGU1mt0zOcHHIBsCGVMGDhkZDVpAxKlX.y1uS_Z84 0STYBc9roThvIM5uC62402zVCtsM3_XZEj81PLXvlzGmsQFhx.Lou5HymHXEw1Vhz2Ju7aUduKdp J5Zuj7Y5c1ocCwwqb3Qdllnm9AfUdtkullCAnzoR249zNETFx.BOz5CLpfUq407_TIXhxn8f6xTp X4NOIKqK_52WSpSaFB7VCGsXv0XVbPzUbJgBW.eZ6xfiBUTvseFfRvJagNyTkplAv46H6EXvmEBX tXIGcE5VkhA0vhAL.Vvl9GjuoLtZuW1lqns1FqUR76omSL2DKXooUfPUJbUvhkWObMxobcn033uO uV4R8c6DwStG9BAvr5jFs147.CeMGdu1kybDxILI2V2xSrYoo.N_MhU8v.zvaY00AKrNeV9FPBMr ch3iuSjNlv6RDO7beOnNM5XWphnyGFdodDg-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.bf2.yahoo.com with HTTP; Mon, 8 Mar 2021 04:45:56 +0000 Date: Mon, 8 Mar 2021 04:45:47 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: "jsonpath@ietf.org" Message-ID: <4195121.327382.1615178747366@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_327381_938530171.1615178747365" References: <4195121.327382.1615178747366.ref@mail.yahoo.com> X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: [Jsonpath] The "union" term 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, 08 Mar 2021 04:46:00 -0000 ------=_Part_327381_938530171.1615178747365 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've brought this up before, either on slack before IETF was involved or in= a GitHub issue somewhere, but I'm not sure what the term "union" is intend= ed to represent. Appraising this word either from mathematical and from data structures poin= ts of view doesn't seem to apply here. A math sense would imply a set theory operation, but we're not working with= set unions, which are the distinct combination of all elements within two = or more sets. A data structures sense would mean that were attempting to store two mutual= ly exclusive pieces of data in the same memory space, and interpreting the = bits in that memory as needed when appropriate.=C2=A0 This isn't right eith= er. What is the intent behind the use of this word, e.g. in "union-element"? Greg ------=_Part_327381_938530171.1615178747365 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've brought this up b= efore, either on slack before IETF was involved or in a GitHub issue somewh= ere, but I'm not sure what the term "union" is intended to represent.
=

Appraising this word either from mathematical and from data = structures points of view doesn't seem to apply here.

A math sense would imply a set theory operation, but we'= re not working with set unions, which are the distinct combination of all e= lements within two or more sets.

A data structures sense would mean that were attempting to store two mu= tually exclusive pieces of data in the same memory space, and interpreting = the bits in that memory as needed when appropriate.  This isn't right = either.

What is the intent be= hind the use of this word, e.g. in "union-element"?

Greg
------=_Part_327381_938530171.1615178747365-- From nobody Mon Mar 8 10:44: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 5DD8B3A14BC for ; Mon, 8 Mar 2021 10:44:16 -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 39lki-0n8eBN for ; Mon, 8 Mar 2021 10:44:14 -0800 (PST) Received: from sonic309-14.consmr.mail.bf2.yahoo.com (sonic309-14.consmr.mail.bf2.yahoo.com [74.6.129.124]) (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 034633A15CB for ; Mon, 8 Mar 2021 10:44:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615229038; bh=eFZOOC+h4vL7nqcgBg8gxb9raLsq2Jij78puzmCYjz8=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=nNaaZFOeLXjadEBPcDOAX/2NsxoW0/Rzue9skttL9L8eZQ8w1kdeqVKIHmYW9Y6FKWU/ppLlN2uYkgeSpAesSQiws9JUlHEv0ht4ygmKgD/rT/dT/YiwDElHLeIMSX5Z35MoFV98Cb5rFyaMRcR6AfCOTz7KxjjAV1zu3YmXz1QQOygsg6mtulnKt0VQLGIJF7igvnT1BobgzhtybJc9WIzzH0wMFISv20gZZ8Af4bG79zYrM1SXUx6ocH/L7a1IGB1OmiIHCDTtBVU55e9NJYkbcEJ5hubDoLg2gMSmb72ehWM/oJ/495yI0bPciWtwjQs2gotdeQrQ67o5CajGVg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615229038; bh=Wm7QKQtuSe8oElTpFZsRD+VaJ+AWwPSSE5TFOxVdWRb=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=c107SKv9RnY9bhjVfWJ4bNXkyJPATmPhYu4BNoecZWk8JYyacSgmpBbLNlopilt20mmistM1msABnBl8zpGvO7FCf18aPAc5nC/N0NX/sVozh551jB9TevBtKb2qoPLTWO/hvX7K6d/VE6puYa8trOlRgqfLABoP/rly153tp81vxev8q19rzcXZr9TgNML1w2xGZY9ACeinlYbvYWf64EIWO8wKGDmfiHHvxhpgtI3Up1Nx6nrY/DisT36tBxiDudlz7U6bDkTu4W06EHBjDTxLWRdA4GwSobMuucZUsWnQNEQ8q1mLH4/F8Yk6Gfh4Gjprn1WnuzgIVzh6OE6M0w== X-YMail-OSG: xjrfOZsVM1kzBtFLAbtjTLm27Kl_ib6Fxe0zpZzXUXNMu646qOFMyK.TLGsg.J3 r7mBj_DOuntGOYXx7Rc7Zo9MpsaY_BrMHv41huwF47pl3NJPbAYnBijvG.z7oIKX86W0Dlo9H6sb X7OH9f9ibmQUiYFJZvts7cDlt1Knh28vCKyWMG6fOM70aCJp4j5ANqJCZ64wxvJt6OthNY66pEQs jwmCwnTAkaFRg5FWwCPJigxCQV1Tf6xWwIOYy9rRrdeuswSbHQxGqUzAaj6K8PZNjN4YdpzxhX0_ 5_9RbbCeIjwESHv6Fjbkh9Fdz3imC87uxJo98KxG0ABkLn7fh_vjYh6vZPjHpAMqgtSr.Lwjoxdp 9.4DRUlB_qCa5E7_0TebpmkzxipGFTVABD2UF9m0yver7Kv2m_mvqBa__nJdlbu14gZbayz3aEW. RKCp8U.08icsGYYD2QixkKJaoa4pvzuo.4.WShXfYDF_TL4IPuB5Oik9zR_eiNN9.EeZoMr7sUyG 9FVByhKwCIR5eWQMnVGLC50dMEvl7Ha695qydyhs8xXNFPpYeQqGA054csArk1kct.z03fEpKBLy BX9ASSkGrpbWaVkLTFiG.JlUgcoDRpJ2QfD3cVlqxDR9rmWrQ54Cnr140o1HhnrwthfEvSLUGVc9 ED.St0qubqiFcvTXzOF84uUyW5AHf1xH2MvkV0QI.g6IJ66PZUNomw22GyMppnN9MTY1uPVv.FTk UeuwW7Z6Zeu3lRaJp.1axC0hSHy.4Ckndw8hhhV9sUP3MDB.mpF6TEW5QhTND1SAI2UICt7pzBj7 kkPu8Hucv_5USNvvkPKOmoEQoLNLr4A1CCU_fBzc7Ar9BbPQiqhN8WTaP_sXROm8MD7xvswy132v gSu8CU..6WsrsnHrKnKF47KGkgaDNWJ5c.2db_olndgqtP3X6.fGfly3lCcQ1aQ5CvcG1jWycjDo OslYcKWlEqZN8sNeSQP3i2fsyRwmdjrJjle9zKykCR7KRDumXfvpJvYyMSN173MqNYycqWuQggVy iu.iytnGWK6dCcG9AWwwpgfzLgV33wWlFr5bCMtcmXRQPuvv7jlJXD3qUPYZ5E7J9SJ4PEA.kBqW elC3C47dnkJy7mhlZn4fRvDv_YNjRKBqrOAq6kZS.x9ChqR5_.ETkcuSAXgMJnFmchlYYGrrbQiY Y26eYrYJdlCTTfUway1E2Kx54xjLkB5qjlhXz4_nRgBtnmnvE_tp.OounMUxdiTBSjGUOpV0fWZX .EFrLG6rK1vVqtXDLjnGKgrEyQAn6N4tKJTxbiCn.0ZATgx1SL06p0hBfZYnHhweicQA5E5tfFiU xAxVh2sz5DLHAyj_Y2TH8V.xTo9JinPm40.Md4Gw2qIRNXY3ZJDFeBfsVqGDvqZSaXnTEzkNiMGV F4kgDiC1x3iUtGNqKvlbh8aRfGOjfQJuSNO8o_W3vu8yM9sViKeu2uN9TRWaJqNv8Sn.srR64eDx 2efz0MZqNO_uED15sjx0GPXKrf8BV0T9CNGSztCqNhtt.dpFh9luggQ.QI1zkVT7Yc_uqiwgnS_7 zMg2ZPkXpPjSs3OBq0FdtQDTXznpetHj.uP5O4tuHTaNsSah0NmoqsuDp8_8QmoB1poiWAt9X2ur YXbsWWDyZyAAFFhItLPxYDFjmeCQF3SnRYG3G9.aOcoNCMwUokxkXHs3qyWF5BZIBq81wLUiJnB5 kf4ssD5T_j1V3w0MYsrHB4e_YI8G1t0iRFWtj4YwuI.wwWyRJtqI1UQ2NXhJFNTs8PT8qbt9qJly zbwa9Hrkgaj58PT4TQNQYEvO_yOCWOKbj1oCo88Wx3FB0ONlTfLkLowTJbc2UPD.O0ym6SRGXu8A 18XC3XdpSHfrpkHaHIOA6b.uBWKksvIalxswS2xUTs2Sg1ASdDw.AcaI5sf.QF1CKooE.eDgUsaJ JryXgI0g5B9VTOEeTlrBMSTC_1elAjSQEsVrJwMddyHKXMD8AZ1DS.C4XtYt_L00FbXALRYdRXlw p7w0lEfmnnbhh293Z6_IupGh3pvMx9KVrqAN.v.yFc2CjeIVM_JPwaAMxTTk4IzYUMc2VG_whOTU QFtzH.W7pC8.jGWFfEOMMz3wu_tPOzHqk4ZLq0efQ.uqVqLgb3YaJojcnbNssLLyiR1i2..2UoS1 Llb1kAfTY39wCX1KR6kVtleaw8nCDirLve7X_lN4iDKbePeMajlQxL228wvWwdmeVzK82M7sWFvS 9.ZDn9e1g2P2D.SG.8rUMqHDF1AfnnNPYVDxQAyqUHD6Ug5OWEQub2lLnOwNoxejgo_7CvUNns9j iL2DlR_eNZrIPJ_whCHfJ85_oQdeSAU.msXZ6dS6kvbxXO42dgCCZds_4VdinY4Gg07kMiH0ZNCN .XXGec2Oqd6iThuEFvEqlCXLPVSdJx_ZAQboA3oucizJFWP9A3LmWK04TOE23zN3WJqhMO1x4igM 6nFxPHnEyChDgoaXlxAukuLbwg9NTxBo0e0e42GjcHFYxGLqhiY10BwzT2iRjTdMRIPOiw8qLMB3 ZVivTvwsfC_pPv9kUDPzZHzuFH_p1JpApaSpi60YgfJy.QTZkOOK0fjMcHWrn1PVxqg1KdWiGhTI HkCDdpJhx8P0e.L9fppJyW3deQU.K5LzVdHoumZN6yH11.XxznU3jJZBWObe_Uv.2TP1UBHNtgsT Zuki.OBHXq8MJ1shpptLtK5Q187XBHc.VkkGHBky4ezuM X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Mon, 8 Mar 2021 18:43:58 +0000 Date: Mon, 8 Mar 2021 18:43:49 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: Greg Dennis , Greg Dennis , "jsonpath@ietf.org" Message-ID: <805817754.474655.1615229029430@mail.yahoo.com> In-Reply-To: <4195121.327382.1615178747366@mail.yahoo.com> References: <4195121.327382.1615178747366.ref@mail.yahoo.com> <4195121.327382.1615178747366@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_474654_1757952263.1615229029428" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] The "union" term 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, 08 Mar 2021 18:44:16 -0000 ------=_Part_474654_1757952263.1615229029428 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I really hate my autocorrect. =E2=80=9DAppraising this word either from mathematical and from data struct= ures points of view doesn't seem to apply here.=E2=80=9D should be Applying this word either from mathematical or data structures points of vi= ew doesn't seem to apply here. =20 =20 On Mon, 8 Mar 2021 at 5:46 pm, Greg Dennis wrote: I've brought this up before, either on slack before IE= TF was involved or in a GitHub issue somewhere, but I'm not sure what the t= erm "union" is intended to represent. Appraising this word either from mathematical and from data structures poin= ts of view doesn't seem to apply here. A math sense would imply a set theory operation, but we're not working with= set unions, which are the distinct combination of all elements within two = or more sets. A data structures sense would mean that were attempting to store two mutual= ly exclusive pieces of data in the same memory space, and interpreting the = bits in that memory as needed when appropriate.=C2=A0 This isn't right eith= er. What is the intent behind the use of this word, e.g. in "union-element"? Greg--=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_474654_1757952263.1615229029428 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I really hate my autocorrect.

=E2=80=9DAppraising this w= ord either from mathematical and from data structures points of view doesn'= t seem to apply here.=E2=80=9D

should be

Applying this word either from mathematical or data structu= res points of view doesn't seem to apply here.


On Mon, 8 Mar 2021 at 5:46= pm, Greg Dennis
<gregsdennis=3D40yahoo.com@dmarc.ietf.org>= wrote:
I've brought this up= before, either on slack before IETF was involved or in a GitHub issue some= where, but I'm not sure what the term "union" is intended to represent.

Appraising this word either from mathematical and from dat= a structures points of view doesn't seem to apply here.

A math sense would imply a s= et theory operation, but we're not working with set unions, which are the d= istinct combination of all elements within two or more sets.

A data structur= es sense would mean that were attempting to store two mutually exclusive pi= eces of data in the same memory space, and interpreting the bits in that me= mory as needed when appropriate.  This isn't right either.

What is the in= tent behind the use of this word, e.g. in "union-element"?

Greg
-- =
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.o= rg/mailman/listinfo/jsonpath
------=_Part_474654_1757952263.1615229029428-- From nobody Mon Mar 8 12:58:39 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 A3F933A174A for ; Mon, 8 Mar 2021 12:58:37 -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, 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=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 BeFhCJa2SwfS for ; Mon, 8 Mar 2021 12:58:36 -0800 (PST) Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 5B3F33A1749 for ; Mon, 8 Mar 2021 12:58:36 -0800 (PST) Received: by mail-wr1-x42a.google.com with SMTP id f12so12908665wrx.8 for ; Mon, 08 Mar 2021 12:58:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=XHfQlrfQyYSF97AdjyQWEwlBn+ENA/J6ukrh/o2URNo=; b=GV+ffN77HudqjkFa4Phirsu6WXTHTGtwQUeJQ5KUHpP3MlZeHyCLbVrUcgXXFS8PYt /zwH18RmkyC7YdfS541XhO1XQ+JFPavk6FrFh8gwDAOAAhn/QH2srn1ntMmL1YH7ZrBk wjInHIA5T9AykoWthtJCE5sEfrIcgm007I8v1NjV+puS7lx3AtRD2dyv3GYGVONJ/KuU osWmB6b7p+ghUuCCabYOcborhGJU0kKap391d6OzpOeT/3TCKRatop25FlkUw5VelQ7p 9apNytBpG46dbkiQdYRogdbFd8qxhY6G52WZMIwRz6dlOO13GZK7h+csa1wTGlbYUDrT qd9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=XHfQlrfQyYSF97AdjyQWEwlBn+ENA/J6ukrh/o2URNo=; b=cFzJQOKCzEQXzM2HDfAehr+4TOQ9ysnLTZZRHiCGXmhTlU9bEZObETxrBNi3J48dD/ vpi+YqhGw+089h9jnrKyn5za8Pvr/o+TFNTDrWyTCAlHpdUkMXC3ksE3b8kwwgnFjqDx AUUC07AhUaKjBL40UuUX9WGAU9toCgvRRKrlbcA5LEshucrxm46fTw7Te28z2SF4V6v+ kLZ86WSKKGA19jpdalAjpd821S6Jnnv9U+NQeD/GVZLH8Uk8ZmC9wJ26poBhqTo/8/nF bUe5waB9646PNircgogASTKfthiI+QcxXCWQLiAK7j/JoY42MN3WaSQG7mSSDd1NdaQu Mgaw== X-Gm-Message-State: AOAM533uGWgSPtzG/MrnCB6OJXF3BeHkrU42u+qVE7AF4tkQFN9qgUqt CgbexkYleEET5bijbB94OlnnRKRzfkPJxOTls12SDwqFHhZtFw== X-Google-Smtp-Source: ABdhPJxD9jhsBDriKYpkKNBDSy17hyg5zomkW6zVBnv+uGkydaarkihtx3qwfugv0NzQ2dU7FB/eFnbxhaPoEJFLPF8= X-Received: by 2002:a05:6000:18a:: with SMTP id p10mr24993099wrx.166.1615237114369; Mon, 08 Mar 2021 12:58:34 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Mon, 8 Mar 2021 15:58:22 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] The "union" term 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, 08 Mar 2021 20:58:38 -0000 > From: Greg Dennis > I'm not sure what the term "union" is intended to represent. > > [Applying] this word either from mathematical [or] from data structures points of view > doesn't seem to apply here. > > A math sense would imply a set theory operation, but we're not working with set unions, > which are the distinct combination of all elements within two or more sets. > > A data structures sense would mean that were attempting to store two mutually > exclusive > pieces of data in the same memory space, and interpreting the bits in that memory as > needed when appropriate. This isn't right either. I think "union" makes sense if the operation produces a list with no path duplicates. I note that JSONPath for Node.js characterizes its unions as "real unions" with "no duplicates rather than concatenated results." But I don't think "union" makes sense if it produces concatenated results. Other than that, "union" has historical significance, being used in the original paper. Personally, I'd prefer the JMESPath term "MultiSelect List", but noting that in JMSEPath that term doesn't describe exactly the same thing. Daniel From nobody Mon Mar 8 13:11:50 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 2669A3A179D for ; Mon, 8 Mar 2021 13:11:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.92 X-Spam-Level: X-Spam-Status: No, score=-1.92 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] 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 uQ9vGV4-IOTC for ; Mon, 8 Mar 2021 13:11:45 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B316B3A179B for ; Mon, 8 Mar 2021 13:11:45 -0800 (PST) Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DvWHM64b9zydV; Mon, 8 Mar 2021 22:11:43 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Mon, 8 Mar 2021 22:11:43 +0100 X-Mao-Original-Outgoing-Id: 636930703.433863-79601aa39a76510f760885d7bf828f3c Content-Transfer-Encoding: quoted-printable Message-Id: <37390EC1-5EF5-4C0D-AD6F-C5914C0CC6A5@tzi.org> References: To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] The "union" term 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, 08 Mar 2021 21:11:49 -0000 >> I'm not sure what the term "union" is intended to represent. The feature we are discussing mirrors the =E2=80=9Cunion=E2=80=9D = feature (=E2=80=9C|=E2=80=9D) of XPath. I think this is the only reason why it is called that way at the moment. The union operator is meaningful in XPath as it creates a set union of = two node sets. I=E2=80=99m still not sure that this is the outcome, but if we are going = away from a =E2=80=9Cnodeset=E2=80=9D approach to discrete collections = of data items (positions in the tree), merging two collections is still = a meaningful operation, but offers many ways of duplicate handling and = ordering the results. I don=E2=80=99t have a strong opinion on these ways, just hoping the end = result won=E2=80=99t be too bizarre. How we call the merge operation should depend on what it actually does; = union as a placeholder is fine at the moment as we all know that this is = a placeholder only. Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Mar 8 21:32: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 29A0D3A1179 for ; Mon, 8 Mar 2021 21:32: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 b8ZEPrIPg-Jz for ; Mon, 8 Mar 2021 21:32:13 -0800 (PST) Received: from sonic315-15.consmr.mail.bf2.yahoo.com (sonic315-15.consmr.mail.bf2.yahoo.com [74.6.134.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 187533A1178 for ; Mon, 8 Mar 2021 21:32:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615267932; bh=apVyCvxbjr/iDPy3j1SAcZxnfS7etmjJqz/FBK+CvPY=; h=Date:From:To:Subject:References:From:Subject:Reply-To; b=Vy2XhnuGbkB5JGKELvVUZHjEAQnw1kL1vGjfkUTjN7W9QqsJBJg8kEnbS6Ym9CI/Npvro65oufGzG2Sx9xyjOCOfwVZDIkUM6aqpk1c2EwNBIVHFv2D5h4HWpq+RjpT3S0sL9fmWttNQXCOFNh3LZi5r5uO2/sPcfGiWsKvfcVpmjzE4aHMqlZsKUlPtXMLW/Pf8kR5CUpG00CgADXWOB4hJA1VQWWtwYYB8b9dGs4t8FKnUA7SRXZsyqZh3nrpJ5i2sBypAYYreyUdtxWTRQpz+JPad4lzIrxxxI1mctrgFhI4hki7NfNmI9YmuZdeWD5lkXPTqUcd9uNxo/RXkCg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615267932; bh=wIDhGrt5L89QEoqGuGjGv6VMfWN7bOgbz4dNtvoj+GR=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=ehSBBlOJ3Y2+FOodJwnxWcl1pvp4DobM+PUkKv0rYfYYp4l7eAlkubfIx1y1l0820pAo+s7JDv7DsFkwzV45DyuvRWKNuvAZcj+i6TPUINhgz/xL3wUpY2kgWjWY8XA9zQhcLqgJNwEc7M7TTl54mHoOFd6aQEmi+VBYJldKfAJcKRoi2wPO8GbErnHYpO9cNXWUbNGK5USk9/ydOIimxdyIlKsuHd6UYxCqbMnkAQRaceWl3oc339ttUZBmdhZLUoMgzroIQv5EV7qM3RTrlN0sNf7FGVxG4r9WDtLp8FYwQbBpuGZYcgUi2vPRUuFH/QU4OvHpWYlm4eXo/WZttg== X-YMail-OSG: BqDVJGIVM1l2wQetm.VD6Jdqqyv4HzZeXulqhDI1o0KqfOnq7isAoHr7dLzmjzr HJkV2Lp4.ypjQRxI.nRywzL.D8kbt82M.0ljxv_EEJ6TgcDgTeg0oj33HWF51FAIwtzPt.IV1dy4 58nh7.zcP02mgjVL2dZX7KKYFPxEraMkM9zyyUdrSqa3iFMwQ89t3yX75JC1kLtl3h4pJ5y22TEU .D_R4547oXiBcqfIkAFua1dxIQa.vVgLT95n5F5nln3ZX.69WOkbZL856oZEvE9fjdkWZwraGTtz 9Jetw958BdNr8BD3QhOzAVJSosmdoYc_y4uKifPA5a7LcBVKF_JfvMmmbR3KgENqxsZ7OqNxOuy0 mSxE9hI6x78eOXb2aWbU9QjIDs7iSd0jpfS6iUQ0Gr7lYJOcwtnEl0CL7iFF9le1Z.7wSCLMvU7H 52gy3RMJ1CzQtL4skEkL3pf4V5csH89l.p8AeRvTuafAdVO7fJz8ej3AVvGrw0n5ZZvJR3.vtZ76 _BYhORYWaYT0Xs5pstwL6KPf.Ntm_pDUxF.dtdikErrciUO2dC0c0r3lWideo.v7WCUqxGWr77qc ocpDInanaacIHkTmrs2x.c5MhaNreEmZQBMwyC8yq8dduoU_FHkTB5IQMhNjEz9Ax8aFh4xVRrO1 tF19XhL1dtHFtZavB5iFsTxVw2VzzdLg7S0UXhTCQ594YkMhHJ6cAz88ZCgRRQduDT3KDHtxesFb GdsAMufMmeHN0QNsvPPjZksvp9b8MJSFye9Od75Xxs0sBwueOPt83DRQ7mBYJswh.Y9uvLvPRAIL HprUu5vt3xgga17VZB6aJovjNVLvmNn.dyRZgQSaMpbPx7eNIFzw9IDsVIKnEyR_Xio1apEfEsiz 4w5X8Nr5rLsWveEdAunGTOt6Jr2UKtL1xi9zJYnZ4wNNnrcgyeVRMPpw4937hVGGRrei507pJRtL N7qCb.yYAw3JCjycyuL7li8mYq4zMmpAaNWVkfUCZKbYp8OeOa.yyrtBHCTYll4bWSksVM0Gi2Eq TR4BM0otUMPUpCNWbL17QdLnwjtrBHthRBF.S_A5kzsEkK.6Qc4XqFbyWYIv_jj5003AwNRx7.1v 1TIFhYx3TTv3DiDg7xZePoNq7U9D_kqkLoNegJK9aBS0BGRXJHooMc0iwnlubHYgBuXuGLq_lTAh gqj2IPEuPy_lLXX_2Zyj1EPMT0.3SJHjMk.iEGOChgq6nS3zrirfwEElmuZNCYoMvUWTjnLcDEsu VqpLGxVHesJ16W1adh4ObicanePHAU1N_ppywnuXVrpm0blmbSjbF1l9uyfdq0TJUjUmZUAFZHIn F05U1AribiZ0womVkNwd.EadmGsHdUrWYexGHvrTtlQsM30WOMoqyR7AfuhswwyCJ1FfQG6Un.z3 KRZlOq9ijqe5JSPZmu2OPiKff9CXZwmOGjlsadRTuqXY0bOz.7LR_KF7xOed5GMz5KDHGLKDKnBs cmJmEdCl0blG25MMYA7h9N1S2mG25r0sDBO9d_zsmKlTC.Jitscf3ihiYyINGqrb49jGf346w1g1 g5_S_B2r2F9O5a8VSpFzTliNdP9R71MCIoEu1OCm8jcDfK0YawsAuGRxrJ3ZdBgHQDBDDmf0T07T heEk5vPIgdjWwk519huXwDj6oTCz.eivaGFqvNIRkmx8ikxOZzYyg_oUcQLpM9qV7O7JDvaGyWv5 Sw1EHaOJ1_KL2Xfi0PQhRqHxkUQZthK6t6w_Fq_H9zUPxD_RE6t_AlCUKQB7UsiVENZinR_K0UMv 4ugX9hoCtmfxbZ3lPXZWzWB_Zdbt.rx784amXhTUjHDFXBnjnCy2rsnej_xY3nKAxU.aS0w840YC nymPusKcy3kM.2Wtm4VgNwCVqzuSFhEB.TUIyrXFcRdubx9LsQooHRkqacdrBkEstaNx2LMgS8BW gMo7weVtcX.8ytsVFRBgL1GtKXaCAUhqlj354MA6ip_w3Cd_c.oVPmnfWeM8.c4R_TRo2QJ6hL2j VFNZSjrpWvsNTMLQCSbbNymAtqawmOBVAZHWbGZcnLE68l.wisCl5ccWxLxeV8bKU_8R29RVv_eV asCZTc3olcUCyQEMchz7P9Fnmiimw5_0gQVA9fHtvDGiF134Yi6j3iUEK5ZPEdtS8veJgTXyTFrf W67ZCPKsV7Wg86ovgx618i3inBu8YzKROlQCk9tmaWZJ0RwSYhcHCpywH5biDwLE4kYoUUEpCOt_ a.4gbzzppwXyGjlA3eLEmuverKSDG5ccKdfN45rNAr31Uf1LIEMY5ffmAjM_buCxvW0kB3kiVBeH hS2SxSv1ZVEiHqIXBlWRe6R2Hkv_M2v18v7LS6GpjFbla.ySf2cOsx.aOkoImDJQ_vaOse9isTup N5_yZmN.yYl6Ug0vgZgLIkXp26m23AYgF7d_4NgCXUAiVThuRU1uafQzEH1w6Stg- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Tue, 9 Mar 2021 05:32:12 +0000 Date: Tue, 9 Mar 2021 05:32:07 +0000 (UTC) From: Greg Dennis To: "jsonpath@ietf.org" Message-ID: <1723110914.604590.1615267927220@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_604589_1320754203.1615267927220" References: <1723110914.604590.1615267927220.ref@mail.yahoo.com> X-Mailer: WebService/1.1.17872 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.190 Safari/537.36 Archived-At: Subject: [Jsonpath] Github 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: Tue, 09 Mar 2021 05:32:14 -0000 ------=_Part_604589_1320754203.1615267927220 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable We've had a few new Github issues lately (and I love that we're using them)= .=C2=A0 However it seems there's a lot of crossover in regard to topics.=C2= =A0 Can we put a bit more effort into searching for existing issues rather = than creating new ones, please?=C2=A0 Otherwise, discussions become fractur= ed. Thank you.Greg ------=_Part_604589_1320754203.1615267927220 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
We've had a few new Github issues lately (and I love that we're using them).  However it seems there's a lot of crossover in regard to topics.  Can we put a bit more effort into searching for existing issues rather than creating new ones, please?  Otherwise, discussions become fractured.

Thank you.
Greg
------=_Part_604589_1320754203.1615267927220-- From nobody Mon Mar 8 23: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 0673A3A159B for ; Mon, 8 Mar 2021 23:20:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.92 X-Spam-Level: X-Spam-Status: No, score=-1.92 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] 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 LzZN1Ml1JFwG for ; Mon, 8 Mar 2021 23:20:09 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49C0B3A159C for ; Mon, 8 Mar 2021 23:20:09 -0800 (PST) Received: from [192.168.217.152] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DvmnM1V2Rzyqk; Tue, 9 Mar 2021 08:20:07 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Date: Tue, 9 Mar 2021 08:20:06 +0100 Message-Id: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 07:20:12 -0000 I think what we have so far is: =E2=80=94 there needs to be an expression language that is independent = from specific implementations and their implementation languages. =E2=80=94 the expression language is used both in index expressions [()] = and filter expressions [?()]. Obviously, in index expressions we need the expression to return an = index value (integer, string), while in filter expressions we need a = Boolean value. Also, in index expressions, the implicit parameter @ is the item to be = indexed (the item to which the [()] is applied), while in filter = expressions, @ is the item to be filtered (one of the items in the = container to which the [?()] is applied). We have a dial we can turn how conversion-happy the expression language = should be. E.g., the conversion from the filter expression result to a Boolean can = use a big set of =E2=80=9Cfalsy=E2=80=9D values (false, 0, =E2=80=9C=E2=80= =9D, [], {}) or be more restrictive in what it accepts. Similarly, the conversion from the index expression result to the array = index or map key (JSON object member name) could be loose (e.g., = converting numbers into strings) or more strict. Generally, both kinds of expressions won=E2=80=99t know statically to = which kind of container (array, JSON object) they are applied. It should be possible to write expressions that can operate with both = kinds. Surprising and error prone conversions should be avoided, though. Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Mar 8 23:34:21 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 EB1CE3A15D8 for ; Mon, 8 Mar 2021 23:34:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-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=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 a3-LpV7oKe-R for ; Mon, 8 Mar 2021 23:34:18 -0800 (PST) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 DD7DA3A15E0 for ; Mon, 8 Mar 2021 23:34:17 -0800 (PST) Received: by mail-ed1-x532.google.com with SMTP id b13so18479559edx.1 for ; Mon, 08 Mar 2021 23:34:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=ZA4ST1LtzqpY7iotIVvl+l+psvhVgQJ+55COfH1vc4o=; b=sMOonDvHICrbxbhd4SW7pmnYBjU9Kz4EKz+Nypam69/sMj+9PfZXhYiBIq1hcXFVQy c8fCamz4X+1svfgnN3E+EuierucLj6D+Ne9C0HmDbNTeJjueDCkE8fFzQUvvdOy2yvXT SY7cF9xFkG72jsfI2hG0NInsqkHGYMsfsDtBPLj73WAccCzllQg4Mps0Q+Ft74QCy3ES 7mk0FtN/dks1QMeaerrM6L8nakbM9O55FDx+8HiAKb0ZVNgsseQEl4RWgb9xBkXa0J5M Srmit4SA04/ZBe2CQ/tJOs3m/63ylNBFhrUt0UY39yqv4HT85W1gKO+XZ3DPuMmaHgcN DKrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ZA4ST1LtzqpY7iotIVvl+l+psvhVgQJ+55COfH1vc4o=; b=UoKr0cqY6A97r7KcZog8azlqZKYqj56rSTFmTMQ3UEZO/yQqCe+hp/P9Uf2OgrOPXt oUX9r1WzAyQ+fdyAz+pG9HL/Cx5gBQURqM7a024mdzBjxTsPR7Ld1gY6NxBoqhTOfZSG Boueiyc75Fog/MhpgZUt3XH0NcAmL+/H0jGGq2hPa5F2T/tmcx+wP9xO1nwNaS5od+Jb dslrkyxsGyhlVct3suMs72sJFdyFNn2d+KvzJFeuFGrOX/X4yyP5XGrBmZrtyIzQY0s+ hOb7VbKfy9uv5sbH6QZMXC17NvLKWFVaQpkqfrq2Y18tT47+MXvobTsxMj6Iah9QtQOa Y28A== X-Gm-Message-State: AOAM5312/JDrfnICfZvG7pcSXMVgr2j9S/K8RLhm74JxZDrDP09vmGI/ tBVntkgJnMyfiKylv5zDirbZMR7h19U= X-Google-Smtp-Source: ABdhPJyir/OhNgcyRQOPGIEIkseqic/CgxfAuW0odVYB+xVYKcKNjpZeAFgFZx89Sk2HIzKhi+Xvyg== X-Received: by 2002:a50:f311:: with SMTP id p17mr2667478edm.188.1615275255268; Mon, 08 Mar 2021 23:34:15 -0800 (PST) Received: from [192.168.1.95] (71.224.125.91.dyn.plus.net. [91.125.224.71]) by smtp.gmail.com with ESMTPSA id r19sm3496120ejr.55.2021.03.08.23.34.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Mar 2021 23:34:14 -0800 (PST) To: jsonpath@ietf.org References: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> From: Glyn Normington Message-ID: Date: Tue, 9 Mar 2021 07:34:13 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 07:34:20 -0000 On 09/03/2021 07:20, Carsten Bormann wrote: > the expression language is used both in index expressions [()] Is there a compelling use case for index expressions which could not be supported by other means? (If not, we could drop them.) From nobody Mon Mar 8 23:40:21 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 F30A73A1666 for ; Mon, 8 Mar 2021 23:40: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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 Xj4--177S6Hp for ; Mon, 8 Mar 2021 23:40:11 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16F843A1602 for ; Mon, 8 Mar 2021 23:40:11 -0800 (PST) Received: from [192.168.217.152] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DvnDT2DFXz10Bm; Tue, 9 Mar 2021 08:40:09 +0100 (CET) From: Carsten Bormann Message-Id: <8A691340-D265-4A50-A003-4E836CB80F92@tzi.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_E0B2CE76-9824-4ABC-B70C-D14F55EC2994" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Date: Tue, 9 Mar 2021 08:40:08 +0100 In-Reply-To: To: jsonpath@ietf.org References: X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: Re: [Jsonpath] [ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath] A "General Considerations" section (#58) 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, 09 Mar 2021 07:40:20 -0000 --Apple-Mail=_E0B2CE76-9824-4ABC-B70C-D14F55EC2994 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Moving this discussion to the list, because it touches a large number of = issues. I=E2=80=99ll try to parse apart this pile of unrelated considerations; = maybe we can dispatch them into the specific issues raised. > 6.1. Range of JSON Values >=20 > An instance may be any valid JSON value as defined by JSON. JSON = Schema imposes no restrictions on type: JSON Schema can describe any = JSON value, including, for example, null. >=20 > JSON Schema uses the word "instance" to describe the JSON data that's = being validated. We seem to have landed on the word "data." Regardless, = I think the gist of this also holds true for JSON Path: input values can = be of any JSON type (although only certain types may return results = depending on the Path) >=20 Yes, JSONpath should be able to be applied to any JSON data item (JSON = value). If we haven=E2=80=99t said so yet, that=E2=80=99s probably because it is = an obvious property of a useful query language=E2=80=A6 (Editorial, if you ask me.) > 6.2. Programming Language Independence >=20 > JSON Schema is programming language agnostic, and supports the full = range of values described in the data model. Be aware, however, that = some languages and JSON parsers may not be able to represent in memory = the full range of values describable by JSON. >=20 > This, I think, is of utmost importance. We definitely should not favor = a specific language. Doing so would inhibit inclusivity and shun people = who work in incompatible frameworks. >=20 There is a wide gamut of meanings to the expression =E2=80=9Cfavor a = specific language=E2=80=9D. Is requiring arbitrary precision integers =E2=80=9Cfavoring a specific = language=E2=80=9D? Specifying a specific regex dialect? We may need to accept the dominance of certain platforms in our = decisions (e.g., the I-JSON limitations caused by JavaScript), so I = don=E2=80=99t know how to act on this. Of course, we shouldn=E2=80=99t wholesale import a language (e.g., as = the expression language), except if we do. > This statement also makes it clear that it's understood that some = frameworks inherently have limitations that may prevent them from being = able to implement the full expression of JSON Schema. Declaring this = outright allows such frameworks to have partial "best effort" = implementations and still be compliant with the specification. >=20 We probably want to avoid compliance levels, profile implementation = conformance statements=E2=80=A6 Just as we need =E2=80=9Cextension points=E2=80=9D (see below), we may = need =E2=80=9Climitation points=E2=80=9D. > 6.3. Mathematical Integers >=20 > Some programming languages and parsers use different internal = representations for floating point numbers than they do for integers. >=20 > For consistency, integer JSON numbers SHOULD NOT be encoded with a = fractional part. >=20 > I'm not sure whether this would apply for us, except maybe for array = indices. >=20 No idea what this does here. We don=E2=80=99t get to decide how our = JSON input is encoded. More importantly, we don=E2=80=99t get to see that (unless we require = JSONpath to be used only with a specialty not-quite-JSON decoder!). (But, indeed, we do get to decide the number system used in our = expression language.) > 6.4. Regular Expressions >=20 > Keywords MAY use regular expressions to express constraints, or = constrain the instance value to be a regular expression. These regular = expressions SHOULD be valid according to the regular expression dialect = described in ECMA-262, section 21.2.1. >=20 > Regular expressions SHOULD be built with the "u" flag (or equivalent) = to provide Unicode support, or processed in such a way which provides = Unicode support as defined by ECMA-262. >=20 > Furthermore, given the high disparity in regular expression constructs = support, schema authors SHOULD limit themselves to the following regular = expression tokens: >=20 > individual Unicode characters, as defined by the JSON specification; > simple character classes ([abc]), range character classes ([a-z]); > complemented character classes ([^abc], [^a-z]); > simple quantifiers: "+" (one or more), "" (zero or more), "?" (zero or = one), and their lazy versions ("+?", "?", "??"); > range quantifiers: "{x}" (exactly x occurrences), "{x,y}" (at least x, = at most y, occurrences), {x,} (x occurrences or more), and their lazy = versions; > the beginning-of-input ("^") and end-of-input ("$") anchors; > simple grouping ("(...)") and alternation ("|"). > Finally, implementations MUST NOT take regular expressions to be = anchored, neither at the beginning nor at the end. This means, for = instance, the pattern "es" matches "expression". > Not sure if we're planning on supporting regular expressions. It = appears that some implementations do have some support, but it's all = extension on the original syntax at this point. Still, this is a good = declaration of support. >=20 As we define our own expression language, we also get to define our own = regular expression dialect (I hope in a less mushy way than above). > It also ties in closely to section 6.2 regarding framework limitations = as not all frameworks support the same flavor of regular expression = syntax. >=20 It may be worthwhile to quell outright the expectation that the JSONpath = regexes can just be dumped into the implementation regex dialect. > 6.5. Extending JSON Schema >=20 > Additional schema keywords and schema vocabularies MAY be defined by = any entity. Save for explicit agreement, schema authors SHALL NOT expect = these additional keywords and vocabularies to be supported by = implementations that do not explicitly document such support. = Implementations SHOULD treat keywords they do not support as = annotations, where the value of the keyword is the value of the = annotation. >=20 > Implementations MAY provide the ability to register or load handlers = for vocabularies that they do not support directly. The exact mechanism = for registering and implementing such handlers is = implementation-dependent. >=20 > This is good to have because invariably, implementations will want to = extend functionality beyond what's in the spec. It basically covers = other implementations from also having to provide the same extensions, = requiring only what is stated in the spec. >=20 > It also mentions "vocabularies," which are a spec-defined mechanism by = which implementation can extend functionality via new keywords in such a = way that they can optionally be supported in other implementations. = Furthermore, this mechanism allows the other implementations to refuse = to process a schema that requires a given vocabulary if the = implementation doesn't understand it. This bit I think is good for later = when we eventually get to spec-defined extension mechanisms, but I don't = expect that'll be in the first draft. >=20 Yes, we need an extensibility (and evolvability) story. This will revolve around extension points, which need to be defined in a = more rigorous way than =E2=80=9Cignore what you don=E2=80=99t = understand=E2=80=9D. We may also decide not to have extension points (like JSON did), but we = need to make this decision in a very conscious way. Gr=C3=BC=C3=9Fe, Carsten --Apple-Mail=_E0B2CE76-9824-4ABC-B70C-D14F55EC2994 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Moving this discussion to the list, because it touches a = large number of issues.

I=E2=80=99= ll try to parse apart this pile of unrelated considerations; maybe we = can dispatch them into the specific issues raised.

6.1. Range of JSON Values

An = instance may be any valid JSON value as defined by JSON. JSON Schema = imposes no restrictions on type: JSON Schema can describe any JSON = value, including, for example, null.

JSON Schema uses the word "instance" to = describe the JSON data that's being validated. We seem to have landed = on the word "data." Regardless, I think the gist of this also holds = true for JSON Path: input values can be of any JSON type (although only = certain types may return results depending on the = Path)

Yes, JSONpath should be able to be applied to any = JSON data item (JSON value).
If we haven=E2=80=99t said so = yet, that=E2=80=99s probably because it is an obvious property of a = useful query language=E2=80=A6
(Editorial, if you ask me.)

6.2. Programming Language Independence

JSON Schema is programming language agnostic, and supports = the full range of values described in the data model. Be aware, however, = that some languages and JSON parsers may not be able to represent in = memory the full range of values describable by JSON.

This, I think, is of utmost importance. We = definitely should not favor a specific = language. Doing so would inhibit inclusivity and shun people who work = in incompatible frameworks.

There is a wide gamut of = meanings to the expression =E2=80=9Cfavor a specific = language=E2=80=9D.
Is requiring arbitrary precision integers = =E2=80=9Cfavoring a specific language=E2=80=9D?  Specifying a = specific regex dialect?
We may need to accept the dominance of = certain platforms in our decisions (e.g., the I-JSON limitations caused = by JavaScript), so I don=E2=80=99t know how to act on = this.

Of course, we shouldn=E2=80=99t = wholesale import a language (e.g., as the expression language), except = if we do.

This statement also makes it clear that it's understood that = some frameworks inherently have limitations that may prevent them from = being able to implement the full expression of JSON Schema. Declaring = this outright allows such frameworks to have partial "best effort" = implementations and still be compliant with the = specification.

We probably want to avoid compliance = levels, profile implementation conformance statements=E2=80=A6
J= ust as we need =E2=80=9Cextension points=E2=80=9D (see below), we may = need =E2=80=9Climitation points=E2=80=9D.

6.3. Mathematical Integers

Some = programming languages and parsers use different internal representations = for floating point numbers than they do for integers.

For= consistency, integer JSON numbers SHOULD NOT be encoded with a = fractional part.

I'm not sure whether this would apply for us, = except maybe for array indices.

No idea what this does = here.  We don=E2=80=99t get to decide how our JSON input is = encoded.
More importantly, we don=E2=80=99t get to see that = (unless we require JSONpath to be used only with a specialty = not-quite-JSON decoder!).

(But, = indeed, we do get to decide the number system used in our expression = language.)

6.4. Regular Expressions

Keywords MAY = use regular expressions to express constraints, or constrain the = instance value to be a regular expression. These regular expressions = SHOULD be valid according to the regular expression dialect described in = ECMA-262, section 21.2.1.

Regular expressions SHOULD be = built with the "u" flag (or equivalent) to provide Unicode support, or = processed in such a way which provides Unicode support as defined by = ECMA-262.

Furthermore, given the high disparity in = regular expression constructs support, schema authors SHOULD limit = themselves to the following regular expression tokens:

  • individual Unicode characters, as defined by the JSON = specification;
  • simple character classes ([abc]), range character classes = ([a-z]);
  • complemented character classes ([^abc], [^a-z]);
  • simple quantifiers: "+" (one or more), "" = (zero or more), "?" (zero or one), and their lazy versions ("+?", = "?", "??");
  • range quantifiers: "{x}" (exactly x occurrences), "{x,y}" = (at least x, at most y, occurrences), {x,} (x occurrences or more), and = their lazy versions;
  • the beginning-of-input ("^") and end-of-input ("$") = anchors;
  • simple grouping ("(...)") and alternation ("|").
  • Finally, implementations MUST NOT take regular = expressions to be anchored, neither at the beginning nor at the end. = This means, for instance, the pattern "es" matches "expression".

Not sure if we're planning on supporting = regular expressions. It appears that some implementations do have some = support, but it's all extension on the original syntax at this point. = Still, this is a good declaration of support.

As we = define our own expression language, we also get to define our own = regular expression dialect (I hope in a less mushy way than above).

It also = ties in closely to section 6.2 regarding framework limitations as not = all frameworks support the same flavor of regular expression = syntax.

It may be worthwhile to quell outright the = expectation that the JSONpath regexes can just be dumped into the = implementation regex dialect.

6.5. Extending JSON Schema

Additional = schema keywords and schema vocabularies MAY be defined by any entity. = Save for explicit agreement, schema authors SHALL NOT expect these = additional keywords and vocabularies to be supported by implementations = that do not explicitly document such support. Implementations SHOULD = treat keywords they do not support as annotations, where the value of = the keyword is the value of the annotation.

Implementations MAY provide the ability to register or load = handlers for vocabularies that they do not support directly. The exact = mechanism for registering and implementing such handlers is = implementation-dependent.

This is good to have because invariably, = implementations will want to extend functionality beyond what's in the = spec. It basically covers other implementations from also having to = provide the same extensions, requiring only what is stated in the = spec.

It also mentions "vocabularies," which are a = spec-defined mechanism by which implementation can = extend functionality via new keywords in such a way that they can = optionally be supported in other implementations. Furthermore, this = mechanism allows the other implementations to refuse to process a schema = that requires a given vocabulary if the = implementation doesn't understand it. This bit I think is good for = later when we eventually get to spec-defined extension mechanisms, but I = don't expect that'll be in the first draft.


Yes, we need an extensibility (and evolvability) = story.
This will revolve around extension points, which need = to be defined in a more rigorous way than =E2=80=9Cignore what you = don=E2=80=99t understand=E2=80=9D.
We may also decide not to = have extension points (like JSON did), but we need to make this decision = in a very conscious way.

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

= --Apple-Mail=_E0B2CE76-9824-4ABC-B70C-D14F55EC2994-- From nobody Mon Mar 8 23:40:50 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 103E93A1603 for ; Mon, 8 Mar 2021 23:40:49 -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, RCVD_IN_DNSWL_BLOCKED=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 8jbX18ZZMjaE for ; Mon, 8 Mar 2021 23:40:47 -0800 (PST) Received: from sonic307-1.consmr.mail.bf2.yahoo.com (sonic307-1.consmr.mail.bf2.yahoo.com [74.6.134.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 7B69A3A15FF for ; Mon, 8 Mar 2021 23:40:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615275646; bh=YBCJDFUuQv1H6b7Eqhzvl6Qb/VKB97p00rL9JyUwVSk=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=JC9pEzjaQtz5ztMRj1/CsvHWJVWkhX0CBCTSCvHM3uBaWukwal9rbPRHj+hpOfRJ2LmorRGHY0pUtIsa5cj6a5rm0jrk9gCb07rHuZK4egy2awDVeGPgNClMSi8t3q9E25n1pJbnQf5cHxXWIpBp5s9LFTrex6Xdv56zOeZHRxGD15RhqXmPkko71YeNP4/aJ3wk3yZ6oPAmdIhQOMvG35yV2/dblVNDRqJYFzYhrqPreDcrMqwStV+YWWEDLeoAlYzSw6GuBKGn1zyW76YDdiuPbgHDROqlQjyjjNob+K8I0CI2fNswFptBha9fcLaknPKbEH3EstNWaDb+IjPgMg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615275646; bh=/H2i1BzUzDKc5+335sjPSCsH4o/PyDdKBDqVRlPEZ4W=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=X+PHg+y48vahtfCng/5ZYlq9SZNL/cRcoN9dFdex29ok+U+LV8g+Z6yMHSvIMTdzLBRArYguVxwHzfAife0jQKmGh1RJY98eUMrJfwgdpf7rClnsw3AnEgI2tMFTFAOMahGZscpxM8VZT1ujX3cGTTCd6LSNyQsXf6oDx/UqM8ASb33ViNWQwPFspq1AGowi3DSHQ5+O8bofF+/EZMH/hTuaO4JUunq4I2Ulo5/sP09cogAMX53MkiMSJiIkSpyYtDAvhBdS4Lz/22VWVGP8O+YAPgWaB7gk/+6p7VKFmxN/j9/X0CdTWAMH/QCkH7lrEC/E1BTBWkZeqpG8lD06yg== X-YMail-OSG: Dyv7pioVM1kdiuAevsNeHfQUKgPLqUH5Fsb5h2IENKrYiiq6c32f32L.A8jWlhQ nhwHPsxEMKhICN0p8gkKD_P7s1IDoEfmR.fUNV3YY0zXp.Eb2reQyGIYZJicjU3oSBX3G.l5Hr1_ elnCCWDcYth4FFShfk8e_7uuADke.5KozuGawPrn4NCIPBDMinlVgQWQrhHxmhhjFZk75cZt.8q8 1oLcxnenxbkSHkGMqMsCzHuLWciJmrfoJje8GFkXTqy_j4EKrGZEMzE0_LJx5uYfLOSaj_MMMXDu GgUWBj5IH6DUkPQJYLth2vNvkqXhC3H2tGSG9Q1b8pawa2WPd_xzx1DDY6aagwM4uvXp4DGCEg6r 2uqAkZrg03EIxiTC4BZzHyeMh5WWSv1K29Idw_smvXgNO6abTkNkqtuWtUnnnuN0O_.OlQgp_3vo ELrcG_dyrx9TE_yR4ZU8lletFGJkf3DZ.DbT7Ue_8IlpOmDG06JK6MPVYXxcPugIJ_jVAXZz7Jet z1ETg209glTESkiH1G2.GHXO1BpDGEDZG67hj1ysABRL__KG5jjc5t6vFKiHNzYIX_oi242Fa1Qa fYlfi0aUdZfuMTtRuha8kJWKRIsf6W2i8EbFEE_8a9lhuJ018enUEryQg0DyRJsuKHcarRh6w9hf pD6DjTOftq727DbQgg8EEmbcT5hsRfuu4aP2MeE.LTZU.rUt5B9X6nwACpNAlSlpUAS6dykjM.RL JsYZxp0kbtDqIAPwV9KjxQiAv2bAEseI0uLFOKl_EEz2u8us4bH2oOS_Z9Qam97pI4bXyQDroIrM HsvC8Yq8Vxu5XfHcznqBnwTpqLKeXKUaUmi8bNwowwPzJgRLgkJlFwHInWnUINCSzHcUf_fhrnO_ sxY57CkOYa5717tRrG4Af6YOuNkkX2GwbkvV23EZdb9EVL42BWlBnhRKGZ4mS5J_VCHia2jZHFOA P.VEvwqWCSxLBc7bXNFvz88k0lMtwill4bDP7TRAQbdPQ2b8rRzVwKB6DXatSw0M3.ffKI6Bf5yy J1g_0U.WNkQmqJOJ7CeoabaWdzAHtetKvYHRkcNQ.p6K_JqgAPBifa3Gf.N1DpBrNIALdgUc35nJ JVKkbTclkV7.zHmQBRYObl2d1O3w_sdZCBxnssYCJxJI7ZpdRvixmAb_Brg.4iVTE8zMAoWzZ861 fdKgF6sRWy9R8zE3xAJM.ba3g_tzM5AUNEuCIZULlYE0zn9YuxegcZCEvzRbDnHf.xL7cutjCnFz lRLpfoGnXJkwBY4AMXvPJBuePMqa7Z82im1SzZNYGMLpaMqh_4WqTxLKkfFNKPOQUmmobbEgP07E himblsIq1M_HOXaDPcXWi9NZsHdM8_RC19g9fGe0tD9JGm7IhuJ1rjVpnVOtuIGTLtxhxr6qDJib eDlG7VpvY54BkJlGovqq.AYmBJE7IyB2Ty8VHzgid1rNZ4HzyM_eQC0q4XfvVn.4zTTqMJSH4Hwt aAz7Nss2sISQ3_6ug5v4iHplpiWdTVNboGcp.wpBarFv9wAwrSstWlRI3KOV3lx2UfC7yGoZKZ6y vLPT7eoMfrwwIAndiBRSqn0fGiKwkV6sRlhtf2qAp44UMjpMh2xkBklvSu.YpvnCnZkfI7r1WGyU u1m1PZXjNfQRCa_LHUH1IPKACyHlWM0deCruLBP9nwK2ZvKKKVU295zsMYUhhWYcQ8Oi8gjer7AF .txg9fSEn05JkE1_n6pDJX6MdOQMb8PcceBKO9YZh9Jeiahx88LBPIXE6rAwwdCHdyuksfVLI4kP Ao0g.U0wfYVwthiIqG.i1R7Id0w_VCdxjH5umOstVC6zN1_2D9iitA91ycKF41mxpK5fG7cJnDgI s3hyMEUKZ2AFnY78A5niJCsd1vPeoFOdtfslMRUTv.I9jIlvlI78G6vlGX8oc34V_0kSi_uqoVzP p5r6h_99YdrFkmvGu2nelEMnzEIaDfBxr6JbMX3gmTx14srjQ0t_l3zEDahB3NIr_sxgSYXo4NIq .HaOgRv0XknN.91sAYUiJPEKwkbkaRIlZjXEXbGcW7DJCEWFGe6ZEyUf3I_wNPOgFxXtG0thAR8V dxl.FyfgaIRkaNBuHevIEr8KkMtveFbKh3B56hxfPJ609evhJGYImXZRr6oOeAUZSHecA9o3qTu_ _SpZtb1GeDhDLu9CbpOlfasz9PMGOjbxeuQ4CXqvJikh3xpQDr3mthCNDHWTIcSalXHvOINZSrLN 1RHyDnrkSKJhBezbFCK.gCcLDqcjtPoPar0vfT9hrkC3mcs5XC52mjGEMgMFE175hNuVhQ8._o2X Zuy00WHDsmv6CIl2uknO0vxn5M4IqIO4qn1b9TrxtjXZnAtrVDigrFrdAb3mpbFhiC4OpTe9gYLv k27ZjBAEDv3cd0lwFw7L91kuDBtjJ0aHJ0LL3jiLNzLFQNPdyBZ3jXzcD9reKUX6_JzVQcwwg8nM teDMX.S0r3W5zalXwISuOCC_tp4iBa7MNyWVPMm.yalx.7oULzvA8uA.ZtHqAQ39LXMWrulTiEEX GdA9y.ESwx34Ofw_krVwoWoce8EH68YoIJc6eZcTCAQtoVUqMQASiZCm9VXfQN3MT0FXRGxCSC11 XVa7SZd.r8EwgwsQZ0uKWvxZmke08DHOiT.faQnW7tS9CWOgqBLeLModdlQFSL411Arzy6p.eile 7DkDlbo5Ce0WR1ELuTSg2t01bIFY6466Ju4Q.84xJT6d5DgeC8I7EaGVxSVX3ggS0ofBx17dJ7WF 9 X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.bf2.yahoo.com with HTTP; Tue, 9 Mar 2021 07:40:46 +0000 Date: Tue, 9 Mar 2021 07:40:38 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: glyn.normington.work@gmail.com, Glyn Normington , jsonpath@ietf.org Message-ID: <1310281760.620946.1615275638486@mail.yahoo.com> In-Reply-To: References: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_620945_288708491.1615275638485" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 07:40:49 -0000 ------=_Part_620945_288708491.1615275638485 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Carsten, I think you've made a good summary of the problem space.=C2=A0 Tha= nk you. Glyn, both Stefan and I have shown examples where the index expression coul= d be valuable.=C2=A0 You've suggested that we drop them in other places, an= d my response is the same as I've described in the GitHub issues: just beca= use their usage may be less frequent doesn't mean that the syntax is useles= s.=C2=A0 I can guarantee that if we drop it, users will complain. Greg =20 =20 On Tue, 9 Mar 2021 at 8:34 pm, Glyn Normington wrote: On 09/03/2021 07:20, Carsten Bormann wrote: > the expression language is used both in index expressions [()] Is there a compelling use case for index expressions which could not be=20 supported by other means? (If not, we could drop them.) --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_620945_288708491.1615275638485 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Carsten, I think you've made a good summary of the problem space.  Tha= nk you.

Glyn, both Stefan and I hav= e shown examples where the index expression could be valuable.  You've= suggested that we drop them in other places, and my response is the same a= s I've described in the GitHub issues: just because their usage may be less= frequent doesn't mean that the syntax is useless.  I can guarantee th= at if we drop it, users will complain.

Greg

On Tue, 9 Mar 2021 at 8:34 pm, Glyn Normin= gton
<glyn.normington.work@gmail.com> wrote:
<= div style=3D"padding: 10px 0 0 20px; margin: 10px 0 0 0; border-left: 1px s= olid #6D00F6;"> On 09/03/2021 07:20, Carsten Bormann wrote:
> the expression language is used both in index expressions [()]

Is there a compelling use case for index e= xpressions which could not be
supported by other means? = (If not, we could drop them.)
------=_Part_620945_288708491.1615275638485-- From nobody Mon Mar 8 23:45:08 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 9522A3A165C for ; Mon, 8 Mar 2021 23:45:02 -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 8rX94WHukRq0 for ; Mon, 8 Mar 2021 23:44:59 -0800 (PST) Received: from sonic307-1.consmr.mail.bf2.yahoo.com (sonic307-1.consmr.mail.bf2.yahoo.com [74.6.134.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 994FC3A1631 for ; Mon, 8 Mar 2021 23:44:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615275897; bh=t+2fUcamYOpmO7xa9XgBOr376Gaday/m/5jQ4GoV5Ig=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=AURjEMEG4+LjfW1D0c/Q/4h0PsK/rhM5TVT7J/6Mo3xx6oqf3GnYn3VGk0a1GPZOtIm8dUrzpssDJ8cp4jIjqbf4jX2NnGP3oXxhqcCavhmj68CfEof9e4uk/LxBjmJM0mplJNbIr7t9Qo6ZFwVL4/kWWsLphEshd2Kfofs5sjWCYUlbzjRHDLfbH6MJb0ZgxAqUwVSKizbE/vrfvjHiUZcNIKMCpUDZpoxUKL5kE6QbYW8Jj38SYpNUlKSlgi8hwSLyNXgFp5mEq0MchH6JVmVMW6ZbygLje3GnLKMJWaGqJGjUTj3fSakINonnBUhX+PbNV2nwpB5ofLnPaahpDw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615275897; bh=UvdsyljfygvaxE/6Z28RTproe0ZUdWdbYk5pXTaDats=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=nh2oP5h25TvvzOws90E8qNmD23lrpDyLSYONOVchfZllonNmIb0o1emOdhpYAas3WEvxczOsD6inMkNFO3g7CZ1zJArLy97QftElvCqIiTo+8Fls355DZ9dXJO0soS/UVPqTdBoKLSb9/CUogHZNi9VpIhw5pV7gQ3kG5ilbPKZM++vNJ0Aa5ZRKeXPBxmPxDiQBcwneiQJgOSiM/zVPJGJoPBxkDpuivdA6iu2MM6TzZ2b57LS9gf8nplZ3vjvnPUGNwZGcBUiGxF/12quaqmLzTryfwCGT2kKEzL2ahIWMhp9561ywnyXKI3sFCa0ytJpXNMwg4kpZfeH+QHLTlQ== X-YMail-OSG: 8kHZIiYVM1mt4e6bdpa7zQ0IVG_AtQM.jA1QtWjuhHLVOif07oFl81VUCpINdU2 N28sjid2c6NlLCdWR2ceVCi9WOp0.eis.gHY8PLS92dVVvHi4lFu1H1tf_yDuzZOvPTSh6HSrr9Z zu6Ehf6Zx_GrKO17ludxcpgGT3tycYBazO6kJr.BGIPjz3As3ZM0qourEuhijBW.ufoAbiaJb4Kz BqLNwToCMRyGhD._OvOs7pGX1gwsG6URV437zT8H9HjeNepjIYjc4HGzdYElwVkQupTltnh5nP2N 3Do0VwZgJEzwOmliR54vcXAaqFejfVRJtc7yh5PJSPmdRsteSA1VCxWMPAlF9UtI0GJmPdFtRgIy GZohuUFbnO_7PrCXGnKT0C0nZbdPxzcDAzAhKf.Wi6E_5Qc7rga2r3.zYbNZWXXBCgZGzn0I85Sj 3GfvgcOTwdXDpLvxRzgi38JGC83z_5DboW_1xGkETo_5dOznf.v8nZIuUzZlqT.xo5tJVb1iXHsv HRdkX_BVhfyxo4GD4ZMNZUTJpRB2HFdf4ytjbH6TEbNKENaOXUU.gkKP1_UOD.g8DLgi4Pe5IvVt 5RP6AMOzCi9Sz68_eYEFN_0eOAzfSwukbhKVqZKbSgnnOdmN4cEqmftnMaYbV7ft5Zgigi0po5IG yH82CsOlpZXrDz7gFMR1HaphkRKEvDIZ1yRslgcn_MUNMAavGPSNi_0pAu8ktVM9HMRw_HXPa3Mn rjJeoIO6lkIJSrbyYyVXaMcBRjNayIetP90jcFg345rBTOHJJl1hwff4m528NreYU_vrb_J5aOia af0sx3hVsqz5ByMuXs8eVlY2ZL_0DDeSMTZatAFRNv3Zco4KhcMjRBiMWtf2AcJ2pH2AMLb4XFKj eAzWJ4buFnpzSk.ydqr.mJXXQm8sYkeMkXctumUFh4RxVEbdOaWv3UpTsfApWKEKme_N.oUNGMy3 bgBZ6pL.kwRmgTCTBPhS9eqeNvAhxQwUyqbSYCon_uG_2gjUrXR3WgIJ3P.M4ZA0c8BPbwI4wGcK r1GSCmuiS_LzainGRhtUpjGRVBZTh6R3sJwSsMJG1vbJoAir_k2_4u8lVu_fNmELHB.SXQegC2er BdWe.s4Iv3nvq1gCqkmZhe6.oenSbNLD0jcOaCBZ8AI1TwRZ6_fsZw9YPC25BB8cXtzJxYC6DZw5 KtlrK.elZ6_kldl268HmdUrI7b3WkVNBAnKDRqcf0wEnKG9K7FAHKgaXzJH5m.1BRQBit8qhofCh ykvVGidY_gRZsfcoj0qHx6Pw9aXThT_rEKbUNIL3Kuuekj0IAUjY0YwPm50XGL2ESCJBsx5ddKop P.W4_8zP6MOc7viuMlI.396Gm16FU2AOCyXXNqbl5f50mPa2M34xlsoCN7SImRzSi3EfyqO_rOtS CY6jT2WEaUCPILybzy2kBN3puTksdsrKIhbm3OdCUw0yCBmzNCJaFrCAWFsGvwFo1Bw9cztR1Ldf z_iIB57F0LznW3OETFgJqN6D_VqD5wbTbYOe4hw5uj_kHVZIPs5ePzuryYSCESBcdWrS7F6FXdYe 4BHWMD489M1ozG98Z0zM17kWLxZ7UjtkBRIeSD8UOzZu1sl7wlB2QznwehHVZIX3w82NiIJkfIR3 S3QnWpXCmLfBCXKMvjpbuAiCuxUZxRxnJzgXkloKZm5g3qgd6W_BGNMRl0Wt9Qao3EEnbMlBsCV1 EPaE4WoFQZb.wzBTS5Nwf4unbEzv7Y3W925be7R0thpsazBMai6HGIp2rd4X_TGM0cPLhIrZ2nVH 3io.i76I9mlYbfpE1DcsNCKT5F8LjA02ymO2n4NHaDnt1ROV.fhTxmWbELW3DCcvDZpZZ6RCR9FR .2KrzHBAiPqo5vZqmYIMlTpzCMEnxuqpNRYqFd10ZoejR2jOCaG97v58o.AB32Q916bRcVp9tLcE vBkPCc.sMJdhZgQfHnMuWP.biJeyZeNcJIkfArR8ILpccp7rdW9BDoF4WU7AXGQVPTcmDuuYedFM nNDzLEg2bgYdSOwImaHY5_IWaNr7Xw75mnt3ryy3MuLYWrZmZl2jdLL4ZomNE2shBge55KwuhguI LVy4fH74KAXGOVTBhEXPpolDTvf6a2Xn1F0ByUPknk..qzoj6p8hGrOJsePakz5XkWiY4XBjP_LW ftp3f3oF3nM0to9z3C9s3HViV0c3ETNKb4HIowl9jyBPR7FSmXkZ.ABQFUAa6NqShzyFCFx0C5yh GdpklcDAofQBXk6suucTDwUjOFXfxH1nxUr1M7xd4aLb4v5pqM2O1XRfZ4neVtf7_oqQn.NTAJB4 UDXP9P2V2Y6qkd5kuxLtGWL67W9CYfNwU7uwL2l0FHSRkOLBpWAqcDaUSBge_U24yfH7UKcNAviO 0ee.7vKauP9Tx1ac9Iyw5ajb40D4zvPpZvwVykyZCECwrMtw_4UBWK8IrPe9L3oPGWJViBv_.PG3 LXnu5PDU4tA_2FzXWNgr.CLHvpzbGIyhlNWwPAECnMXsRFBCcwcNF_DuLeLYs4uf7C4dnM.2diQs ZLiXHmFVAJZM9iXz3.iH11DvPdZuFEi450SU95vs7gwsX.twjpO_eDX5nDSrB1Jq_Q5BEC.z4fHv LAE2xM8ApIJ4_SaExSfuo19wQyDwjFEUFvhYv36jA4a86_KzgH07QsVxZ5GRbumPQvOLRYi.Ohao IT1X3.cq4CfT2r16NZ2xEO5bvMb_yQPCc77mBrfiJWNVcv..mxAopRmNQjJk- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.bf2.yahoo.com with HTTP; Tue, 9 Mar 2021 07:44:57 +0000 Date: Tue, 9 Mar 2021 07:44:47 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: cabo@tzi.org, Carsten Bormann , jsonpath@ietf.org Message-ID: <702108521.533403.1615275887380@mail.yahoo.com> In-Reply-To: <8A691340-D265-4A50-A003-4E836CB80F92@tzi.org> References: <8A691340-D265-4A50-A003-4E836CB80F92@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_533402_2145995876.1615275887378" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] [ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath] A "General Considerations" section (#58) 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, 09 Mar 2021 07:45:07 -0000 ------=_Part_533402_2145995876.1615275887378 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Of course, we shouldn=E2=80=99t wholesale import a language (e.g., as the= expression language), except if we do. This doesn't make sense.=C2=A0 "We shouldn't do a thing, unless we do that = thing." =20 =20 On Tue, 9 Mar 2021 at 8:40 pm, Carsten Bormann wrote: Mov= ing this discussion to the list, because it touches a large number of issue= s. I=E2=80=99ll try to parse apart this pile of unrelated considerations; mayb= e we can dispatch them into the specific issues raised. 6.1. Range of JSON Values An instance may be any valid JSON value as defined by JSON. JSON Schema imp= oses no restrictions on type: JSON Schema can describe any JSON value, incl= uding, for example, null. JSON Schema uses the word "instance" to describe the JSON data that's being= validated. We seem to have landed on the word "data." Regardless, I think = the gist of this also holds true for JSON Path: input values can be of any = JSON type (although only certain types may return results depending on the = Path) Yes, JSONpath should be able to be applied to any JSON data item (JSON valu= e).If we haven=E2=80=99t said so yet, that=E2=80=99s probably because it is= an obvious property of a useful query language=E2=80=A6(Editorial, if you = ask me.) 6.2. Programming Language Independence JSON Schema is programming language agnostic, and supports the full range o= f values described in the data model. Be aware, however, that some language= s and JSON parsers may not be able to represent in memory the full range of= values describable by JSON. This, I think, is of utmost importance. We definitely should not favor a sp= ecific language. Doing so would inhibit inclusivity and shun people who wor= k in incompatible frameworks. There is a wide gamut of meanings to the expression =E2=80=9Cfavor a specif= ic language=E2=80=9D.Is requiring arbitrary precision integers =E2=80=9Cfav= oring a specific language=E2=80=9D? =C2=A0Specifying a specific regex diale= ct?We may need to accept the dominance of certain platforms in our decision= s (e.g., the I-JSON limitations caused by JavaScript), so I don=E2=80=99t k= now how to act on this. Of course, we shouldn=E2=80=99t wholesale import a language (e.g., as the e= xpression language), except if we do. This statement also makes it clear that it's understood that some framework= s inherently have limitations that may prevent them from being able to impl= ement the full expression of JSON Schema. Declaring this outright allows su= ch frameworks to have partial "best effort" implementations and still be co= mpliant with the specification. We probably want to avoid compliance levels, profile implementation conform= ance statements=E2=80=A6Just as we need =E2=80=9Cextension points=E2=80=9D = (see below), we may need =E2=80=9Climitation points=E2=80=9D. 6.3. Mathematical Integers Some programming languages and parsers use different internal representatio= ns for floating point numbers than they do for integers. For consistency, integer JSON numbers SHOULD NOT be encoded with a fraction= al part. I'm not sure whether this would apply for us, except maybe for array indice= s. No idea what this does here. =C2=A0We don=E2=80=99t get to decide how our J= SON input is encoded.More importantly, we don=E2=80=99t get to see that (un= less we require JSONpath to be used only with a specialty not-quite-JSON de= coder!). (But, indeed, we do get to decide the number system used in our expression = language.) 6.4. Regular Expressions Keywords MAY use regular expressions to express constraints, or constrain t= he instance value to be a regular expression. These regular expressions SHO= ULD be valid according to the regular expression dialect described in ECMA-= 262, section 21.2.1. Regular expressions SHOULD be built with the "u" flag (or equivalent) to pr= ovide Unicode support, or processed in such a way which provides Unicode su= pport as defined by ECMA-262. Furthermore, given the high disparity in regular expression constructs supp= ort, schema authors SHOULD limit themselves to the following regular expres= sion tokens: =20 - individual Unicode characters, as defined by the JSON specification; - simple character classes ([abc]), range character classes ([a-z]); - complemented character classes ([^abc], [^a-z]); - simple quantifiers: "+" (one or more), "" (zero or more), "?" (zero or= one), and their lazy versions ("+?", "?", "??"); - range quantifiers: "{x}" (exactly x occurrences), "{x,y}" (at least x,= at most y, occurrences), {x,} (x occurrences or more), and their lazy vers= ions; - the beginning-of-input ("^") and end-of-input ("$") anchors; - simple grouping ("(...)") and alternation ("|"). - Finally, implementations MUST NOT take regular expressions to be ancho= red, neither at the beginning nor at the end. This means, for instance, the= pattern "es" matches "expression". Not sure if we're planning on supporting regular expressions. It appears th= at some implementations do have some support, but it's all extension on the= original syntax at this point. Still, this is a good declaration of suppor= t. As we define our own expression language, we also get to define our own reg= ular expression dialect (I hope in a less mushy way than above). It also ties in closely to section 6.2 regarding framework limitations as n= ot all frameworks support the same flavor of regular expression syntax. It may be worthwhile to quell outright the expectation that the JSONpath re= gexes can just be dumped into the implementation regex dialect. 6.5. Extending JSON Schema Additional schema keywords and schema vocabularies MAY be defined by any en= tity. Save for explicit agreement, schema authors SHALL NOT expect these ad= ditional keywords and vocabularies to be supported by implementations that = do not explicitly document such support. Implementations SHOULD treat keywo= rds they do not support as annotations, where the value of the keyword is t= he value of the annotation. Implementations MAY provide the ability to register or load handlers for vo= cabularies that they do not support directly. The exact mechanism for regis= tering and implementing such handlers is implementation-dependent. This is good to have because invariably, implementations will want to exten= d functionality beyond what's in the spec. It basically covers other implem= entations from also having to provide the same extensions, requiring only w= hat is stated in the spec. It also mentions "vocabularies," which are a spec-defined mechanism by whic= h implementation can extend functionality via new keywords in such a way th= at they can optionally be supported in other implementations. Furthermore, = this mechanism allows the other implementations to refuse to process a sche= ma that requires a given vocabulary if the implementation doesn't understan= d it. This bit I think is good for later when we eventually get to spec-def= ined extension mechanisms, but I don't expect that'll be in the first draft= . Yes, we need an extensibility (and evolvability) story.This will revolve ar= ound extension points, which need to be defined in a more rigorous way than= =E2=80=9Cignore what you don=E2=80=99t understand=E2=80=9D.We may also dec= ide not to have extension points (like JSON did), but we need to make this = decision in a very conscious way. Gr=C3=BC=C3=9Fe, Carsten --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_533402_2145995876.1615275887378 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Of course, we shouldn=E2=80=99t wholesale import a language (e.g., as = the expression language), except if we do.

This doesn't make sense.  "We shouldn't do a thing, unless we = do that thing."

On Tue, 9 Mar 2021 at 8:40 pm, Carsten Bo= rmann
<cabo@tzi.org> wrote:
<= div id=3D"yiv2505156816">
Moving this disc= ussion to the list, because it touches a large number of issues.

I=E2=80=99ll try = to parse apart this pile of unrelated considerations; maybe we can dispatch= them into the specific issues raised.

6.1. Range of JSON Values

An instance may be any valid JSON value as defined by JS= ON. JSON Schema imposes no restrictions on type: JSON Schema can describe a= ny JSON value, including, for example, null.

JSON Schema uses the word "instance= " to describe the JSON data that's being validated. We seem to have landed= on the word "data." Regardless, I think the gist of this also holds true = for JSON Path: input values can be of any JSON type (although only certain = types may return results depending on the Path)

Yes, JSONpa= th should be able to be applied to any JSON data item (JSON value).
If we haven=E2=80=99t said so yet, that=E2=80=99s probably because it is= an obvious property of a useful query language=E2=80=A6
(Editori= al, if you ask me.)

6.2. Programming Language Independence

JSON Schema is programming language agnostic, and su= pports the full range of values described in the data model. Be aware, howe= ver, that some languages and JSON parsers may not be able to represent in m= emory the full range of values describable by JSON.

This, I think, is of utmost importa= nce. We definitely should not fav= or a specific language. Doing so would inhibit inclusivity and shun people= who work in incompatible frameworks.

There is a wide gamut= of meanings to the expression =E2=80=9Cfavor a specific language=E2=80=9D.=
Is requiring arbitrary precision integers =E2=80=9Cfavoring a sp= ecific language=E2=80=9D?  Specifying a specific regex dialect?
<= div>We may need to accept the dominance of certain platforms in our decisio= ns (e.g., the I-JSON limitations caused by JavaScript), so I don=E2=80=99t = know how to act on this.

O= f course, we shouldn=E2=80=99t wholesale import a language (e.g., as the ex= pression language), except if we do.

This stat= ement also makes it clear that it's understood that some frameworks inheren= tly have limitations that may prevent them from being able to implement the= full expression of JSON Schema. Declaring this outright allows such frame= works to have partial "best effort" implementations and still be compliant = with the specification.

We probably want to avoid complianc= e levels, profile implementation conformance statements=E2=80=A6
= Just as we need =E2=80=9Cextension points=E2=80=9D (see below), we may need= =E2=80=9Climitation points=E2=80=9D.

6.3. Mathematical Integers

Some programming languages and parsers use different internal re= presentations for floating point numbers than they do for integers.

For consistency, integer JSON numbers SHOULD NOT be = encoded with a fractional part.

I'm not sure whether this would app= ly for us, except maybe for array indices.

No idea what thi= s does here.  We don=E2=80=99t get to decide how our JSON input is enc= oded.
More importantly, we don=E2=80=99t get to see that (unless = we require JSONpath to be used only with a specialty not-quite-JSON decoder= !).

(But, indeed, we do ge= t to decide the number system used in our expression language.)

6.4. Regular Expressions

Keywords MAY use regular expressions to express constraints, or co= nstrain the instance value to be a regular expression. These regular expres= sions SHOULD be valid according to the regular expression dialect described= in ECMA-262, section 21.2.1.

Regular express= ions SHOULD be built with the "u" flag (or equivalent) to provide Unicode s= upport, or processed in such a way which provides Unicode support as define= d by ECMA-262.

Furthermore, given the high di= sparity in regular expression constructs support, schema authors SHOULD lim= it themselves to the following regular expression tokens:

  • individual Unicode characters, as defined by th= e JSON specification;
  • simple character classes ([abc]), range charact= er classes ([a-z]);
  • complemented character classes ([^abc], [^a-z])= ;
  • simple quantifiers: "+" (one or more), "" (zero or more), "?" (zero or one), and their lazy ve= rsions ("+?", "?", "??");
  • range quantifiers: "{x}" (exactly x occurrences= ), "{x,y}" (at least x, at most y, occurrences), {x,} (x occurrences or mor= e), and their lazy versions;
  • the beginning-of-input ("^") and end-of-input (= "$") anchors;
  • simple grouping ("(...)") and alternation ("|")= .
  • Finally, implementations MUST NOT take regular = expressions to be anchored, neither at the beginning nor at the end. This m= eans, for instance, the pattern "es" matches "expression".

Not sure if we're planning on suppo= rting regular expressions. It appears that some implementations do have so= me support, but it's all extension on the original syntax at this point. S= till, this is a good declaration of support.

As we define o= ur own expression language, we also get to define our own regular expressio= n dialect (I hope in a less mushy way than above).

It also ties in closely to section 6.2 regarding framework limitations= as not all frameworks support the same flavor of regular expression syntax= .

It may be worthwhile to quell outright the expectati= on that the JSONpath regexes can just be dumped into the implementation reg= ex dialect.

6.5. Extending JSON Schema

Additional schema keywords and schema vocabularies MAY be define= d by any entity. Save for explicit agreement, schema authors SHALL NOT expe= ct these additional keywords and vocabularies to be supported by implementa= tions that do not explicitly document such support. Implementations SHOULD = treat keywords they do not support as annotations, where the value of the k= eyword is the value of the annotation.

Implem= entations MAY provide the ability to register or load handlers for vocabula= ries that they do not support directly. The exact mechanism for registering= and implementing such handlers is implementation-dependent.

This is good to have because invari= ably, implementations will want to extend functionality beyond what's in th= e spec. It basically covers other implementations from also having to prov= ide the same extensions, requiring only what is stated in the spec.

It also mentions "vocabularies," which are a spec-de= fined mechanism by which implementation can extend functionality via new keywords in such a way that they can optiona= lly be supported in other implementations. Furthermore, this mechanism all= ows the other implementations to refuse to process a schema that requires a given vocabulary if the implementation d= oesn't understand it. This bit I think is good for later when we eventuall= y get to spec-defined extension mechanisms, but I don't expect that'll be i= n the first draft.


Y= es, we need an extensibility (and evolvability) story.
This will = revolve around extension points, which need to be defined in a more rigorou= s way than =E2=80=9Cignore what you don=E2=80=99t understand=E2=80=9D.
We may also decide not to have extension points (like JSON did), but = we need to make this decision in a very conscious way.

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

--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.iet= f.org/mailman/listinfo/jsonpath
------=_Part_533402_2145995876.1615275887378-- From nobody Mon Mar 8 23:47: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 414953A1628 for ; Mon, 8 Mar 2021 23:47: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 5k77tEaIOq3E for ; Mon, 8 Mar 2021 23:47:22 -0800 (PST) Received: from sonic309-15.consmr.mail.bf2.yahoo.com (sonic309-15.consmr.mail.bf2.yahoo.com [74.6.129.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 DCC223A1626 for ; Mon, 8 Mar 2021 23:47:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615276040; bh=iJT2e6KIO4Na3JQcCBta4X8DPivPceLjxHJLupuySYQ=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=qs1m2ITaEdkpBphvz0BNI8I5vSmHO4PT3kkw9G60BWDJfc5O2hVx5mHVs3Y0Hvi+si5tLJhAuy+f+tJVURM6cbTByoXVV57FbZE9ifx3J4nXVVD686FzlmeC6Ton187jOC38Lm8ZLf805QN0CJ23WwVA/ni6rpw2oDa3qh2deurZe3JKJ6zYWXh/qItKrm7U8Hwx1vKaRtfvh1xk9OTJrmSGU1r2RYDhBGKWnYhUGY7jnluKCe54u6JuElr4rr39mWj3z0bV8cPuBClrdZLgSUeUHZXWlwHmbyLhJBvE3T81/4U9gq1qYOEaBVZVbwHMVMzm1fJaa7pySn7S9aOAIQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615276040; bh=xTrICNOyh04UBvV6BxKzuikf2zQvVBMqGVDWy8ZxM31=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=nlarmEWqkYuOGb9KlFVnedmod6Ww2XE17Yd0QNOYjVra++YFWL9wE0Gp76XUTZtGZ7pv9+6bMaiPrdO6DfxNowSB3R1NfiNTbzWqEh8C7T6qykghjm+Lk/MNN4qSwsbuO7x2IjBO6x08Y/goQ4prR2Y7xYUXOwPOtTBLp7iajI2bcgjYV+Sy+IJfrra5su8myUfMC0z1jTxmBCrpmvHwKqA+4UnXHLOMcQUa+yKsHfLIW/sqRrtoq5xjIYQ3tMBftYhZecBfm15rWjxvYrqjktah6I2DMZFCK9phY2dU5tbZx3/gk608kBhye/XflOIbEnsHOY3qWwbcPR85GFqgXQ== X-YMail-OSG: 6xM8va8VM1kOw0ATjQpQYNC5FgcEWzKiGQlLWk6azACi5Wg2.759FS.UoGagMkc .zWEo_NYyfIxj8Mi2JqsDShPJSKQJnlodh6086x.wu7OHkU5N7ZmI.EiY3MOd.4Mg6AG6Z.tz88S qHEI_0AFKusYQoJIFb8CS8JTpV5uqlb52OeMcdn9MnP1z_YMcy7lvTnqiUE8ENUcDdzCcrEp0VyD KWxPKhEsGuN2qRoW68UXNGJ6Pbij6iVN4GYi7Ag0IV7tTsXu37FYAYb6G9BcuSeuDxAHcgNIKQ9A Zab63fCrhWWLPylchpz.TgF2j0MPG6J53t210Xnrj1NFXWIZM_qXhmT9xZbbsBAlgQdI.bJTIabV qfkpAEo_N57qj_3..MrWAeAtPowqqHNCPuAHt.VhDV.mEzCfLBVvcfhXJQ9vMvJ4FoAc9BGsWap5 sSqC20RcMKZ2zGYWPAWUzDPyZLkF3Mhal6uaiyokp7JjIaFrW.6XdGBn8ciEVkoZruws5FbdNTyb C9CE04I.mdQcckBF9YSID5gYsRUHS7Y26f5TCkR_vuh6pPpgBgLJkrcekYlAZoyl4r3r2PKSgUZ3 bSHlmWF2K00zsxzah32orvJojUXDi7glYH7P3x4rzu.UptHpfGDn9vy.9dDhpDCaOOpeinZoWHBH iz0wJg9BixA7XX4sDT.zTSoUJ2zUdzdD40oKKhDthTagAwG4cGB49QgZ5_N8BADRNM3FV9S9IfaD CtRoFzNSSZt7iA9PeI__m8VbrtouclDwMmOgtbiGrc8Gji5GuSRCy47gT1ooiJ46E9DCUKuDVhfT WJ9GshXgrxusSMf6xUF7DNW6yNPKNLRGV3AqTGVaFTIfaigKTZjd5N6l7Jww_sTARe.WAs60MBIu 7_QMKUp_Qpw8dIjv1We5uTbaBWWwNhby9TRl2bZ9V6q57g4G4znkqIBEICQirfdwq8LHQW60GA_4 Oh0kgwDhYFSh3BAEZrgerXIuKp0GxXBVfCiHWQUvb1zoC1xrG4IP9ZkOcihanfEvc2yHh_u4Nt0t nnvQnjH0zsRcF2xPEYsmyhcxKNGyUWFZ1th58DwxdWKwK9VME_1VqzPdKQP7ky0w8yaXNKfNIV38 PCR.CidO7R5rlqOi4r7VqL6dITsubobKMShdC8ytw6GWueQjbuZwOkv.rlSMIqpbLMCVTi6W9MCn jhgEa5HNyzSBiEnprbjlpT1Lve_xUa.tYZb6iFH.IeoLS_kWbHtiP4a1KZ81hRBCR6VcRZ2h_koT Ojw53HvOhsK3j0_tEIuAlLhNQTIUifvCfXWyawabm4p9FThFMMg6tIY2N0sque1JHF_pfomxlWrC XYcTgbbwpTkPlug.qgQbmYrU_dkgifYCor5JqtAnkkBvjvSKMRnJ0ATMmBT8KSAeFHLW57Vwi7Nu hD8VHqlFc9movZtLv8mQ.TU5yRU8ccyD_gYsxWWZjIJ_ry.HSEmVTweKpTATsiP2DZYQb7F8QM6R 2JfgiVXtSs7_6jmx0I93hSGGTX6aQaoL3a89m5EMelwwYYR648fpmDjAGv9dOmtMZ1w0ZBTa6H06 jxY1sVKRpj_SL3EDr97CZ2XrLXoAmnH1VIRrv3pEU.6IA8NkON02FtcBaimr8c0JNMPJk9knkjFD j_cZHvS4wh0qvmmGgugixMYMu6ta3ufSlNYs3IIRCeGDpd.jEsXfzlVwF6JYcF4kPGh378G3fViu Dht4cdD.fK7H20donQ4B20M_yadd0.3uK3NNvnHrtmCL5zDGHAX05_.q6tC4MY43ldpKBks3GHE1 0UWf8.ii35x3S4AAsYyIqAmkEpPv8FkUVTs4PW8JpRTMnD0T2O65kcDyitF6EssAPnWHsxm1.qUy iTE0e00ipgCCQyaY4ATddg0UoOhdbOc_FjMo_WJnOnpKyxaKolgu8mnVP7uCyHYo3hUYrBWz8mxd t.c8MESwN6vGHTwmE0wvaNF2hKXiBYRfApq7SVaDAoGlp7RfxLR8lgDF3hF7klIt9QGdmzJOUDtQ d85btRuB5y4y_KMJe1h9XLNJ.lIBhC7_CZi78CL8NSgfXGolwDk72jJ.3MKmcYBZMu36UgZ05a0F .KBzZaKf9jkvz1uh2sPYORrwOs.xdIoyNiDWoqHmmXDM97ePm_QWFsdrbzYnxo62L2owHvNBT.3s vGaVaElJbuIDJnnvVlml.uUVzxFhGuTXAXbTdbPg030IiX_5U8z0tyNsJo3WIOjmWxfzrKWnIweu _aMo1710zWbraMbFap__l12Dl1Yg1H0yg0s_wG26fQVgLiWI3E8n1mmACtStAuyfsuQ21yBKLd08 QxS9J9iqNsrtHTmu3yUy49hVsyqAsKIKnWD.knXqEsygLM9lIx5W3FyOtQ09lOojBSJHV9rrazFO Tr85OkKEIMNuIXM.Ml5eAcpzFqzhQaDXUIZeCpdpH9mka.92LooAQp0jjWnTmM_Zaovw2R3j6aiO NloDPTGDT4_EyP4Mp33xtXnjXx3j0BQeS9_9hR9apshmUO7K5itNsktEo5_Pa6Sjta0R9O6nZ2nn K1gjzTBB5iPcoTyMzgvQs8F3rkKkgPmCBQPlSiS9QjtZY.aSZb8Wmqmvw.TWGT1kguG8jik6zl1I tKFqD.M6KIUpoMJ9Hxro.Gr9hzZFOMwdaZVR5D0cbt8x4Z.Ko_WIl23UJuzhkqzuEjpAN5fLYz83 Pd.XIdymcQkF1ip9Scv..v9La4dsGmkHCVfDC9IJTGuDFOCAUT_59kYX.pMw- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Tue, 9 Mar 2021 07:47:20 +0000 Date: Tue, 9 Mar 2021 07:47:14 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: cabo@tzi.org, Carsten Bormann , jsonpath@ietf.org Message-ID: <1723015503.534113.1615276034552@mail.yahoo.com> In-Reply-To: <8A691340-D265-4A50-A003-4E836CB80F92@tzi.org> References: <8A691340-D265-4A50-A003-4E836CB80F92@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_534112_1607705067.1615276034550" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] [ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath] A "General Considerations" section (#58) 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, 09 Mar 2021 07:47:24 -0000 ------=_Part_534112_1607705067.1615276034550 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This formatting (or lack thereof) removes all cues as to what's the Schema = spec text vs my comments vs your comments. Greg =20 =20 On Tue, 9 Mar 2021 at 8:40 pm, Carsten Bormann wrote: Mov= ing this discussion to the list, because it touches a large number of issue= s. I=E2=80=99ll try to parse apart this pile of unrelated considerations; mayb= e we can dispatch them into the specific issues raised. 6.1. Range of JSON Values An instance may be any valid JSON value as defined by JSON. JSON Schema imp= oses no restrictions on type: JSON Schema can describe any JSON value, incl= uding, for example, null. JSON Schema uses the word "instance" to describe the JSON data that's being= validated. We seem to have landed on the word "data." Regardless, I think = the gist of this also holds true for JSON Path: input values can be of any = JSON type (although only certain types may return results depending on the = Path) Yes, JSONpath should be able to be applied to any JSON data item (JSON valu= e).If we haven=E2=80=99t said so yet, that=E2=80=99s probably because it is= an obvious property of a useful query language=E2=80=A6(Editorial, if you = ask me.) 6.2. Programming Language Independence JSON Schema is programming language agnostic, and supports the full range o= f values described in the data model. Be aware, however, that some language= s and JSON parsers may not be able to represent in memory the full range of= values describable by JSON. This, I think, is of utmost importance. We definitely should not favor a sp= ecific language. Doing so would inhibit inclusivity and shun people who wor= k in incompatible frameworks. There is a wide gamut of meanings to the expression =E2=80=9Cfavor a specif= ic language=E2=80=9D.Is requiring arbitrary precision integers =E2=80=9Cfav= oring a specific language=E2=80=9D? =C2=A0Specifying a specific regex diale= ct?We may need to accept the dominance of certain platforms in our decision= s (e.g., the I-JSON limitations caused by JavaScript), so I don=E2=80=99t k= now how to act on this. Of course, we shouldn=E2=80=99t wholesale import a language (e.g., as the e= xpression language), except if we do. This statement also makes it clear that it's understood that some framework= s inherently have limitations that may prevent them from being able to impl= ement the full expression of JSON Schema. Declaring this outright allows su= ch frameworks to have partial "best effort" implementations and still be co= mpliant with the specification. We probably want to avoid compliance levels, profile implementation conform= ance statements=E2=80=A6Just as we need =E2=80=9Cextension points=E2=80=9D = (see below), we may need =E2=80=9Climitation points=E2=80=9D. 6.3. Mathematical Integers Some programming languages and parsers use different internal representatio= ns for floating point numbers than they do for integers. For consistency, integer JSON numbers SHOULD NOT be encoded with a fraction= al part. I'm not sure whether this would apply for us, except maybe for array indice= s. No idea what this does here. =C2=A0We don=E2=80=99t get to decide how our J= SON input is encoded.More importantly, we don=E2=80=99t get to see that (un= less we require JSONpath to be used only with a specialty not-quite-JSON de= coder!). (But, indeed, we do get to decide the number system used in our expression = language.) 6.4. Regular Expressions Keywords MAY use regular expressions to express constraints, or constrain t= he instance value to be a regular expression. These regular expressions SHO= ULD be valid according to the regular expression dialect described in ECMA-= 262, section 21.2.1. Regular expressions SHOULD be built with the "u" flag (or equivalent) to pr= ovide Unicode support, or processed in such a way which provides Unicode su= pport as defined by ECMA-262. Furthermore, given the high disparity in regular expression constructs supp= ort, schema authors SHOULD limit themselves to the following regular expres= sion tokens: =20 - individual Unicode characters, as defined by the JSON specification; - simple character classes ([abc]), range character classes ([a-z]); - complemented character classes ([^abc], [^a-z]); - simple quantifiers: "+" (one or more), "" (zero or more), "?" (zero or= one), and their lazy versions ("+?", "?", "??"); - range quantifiers: "{x}" (exactly x occurrences), "{x,y}" (at least x,= at most y, occurrences), {x,} (x occurrences or more), and their lazy vers= ions; - the beginning-of-input ("^") and end-of-input ("$") anchors; - simple grouping ("(...)") and alternation ("|"). - Finally, implementations MUST NOT take regular expressions to be ancho= red, neither at the beginning nor at the end. This means, for instance, the= pattern "es" matches "expression". Not sure if we're planning on supporting regular expressions. It appears th= at some implementations do have some support, but it's all extension on the= original syntax at this point. Still, this is a good declaration of suppor= t. As we define our own expression language, we also get to define our own reg= ular expression dialect (I hope in a less mushy way than above). It also ties in closely to section 6.2 regarding framework limitations as n= ot all frameworks support the same flavor of regular expression syntax. It may be worthwhile to quell outright the expectation that the JSONpath re= gexes can just be dumped into the implementation regex dialect. 6.5. Extending JSON Schema Additional schema keywords and schema vocabularies MAY be defined by any en= tity. Save for explicit agreement, schema authors SHALL NOT expect these ad= ditional keywords and vocabularies to be supported by implementations that = do not explicitly document such support. Implementations SHOULD treat keywo= rds they do not support as annotations, where the value of the keyword is t= he value of the annotation. Implementations MAY provide the ability to register or load handlers for vo= cabularies that they do not support directly. The exact mechanism for regis= tering and implementing such handlers is implementation-dependent. This is good to have because invariably, implementations will want to exten= d functionality beyond what's in the spec. It basically covers other implem= entations from also having to provide the same extensions, requiring only w= hat is stated in the spec. It also mentions "vocabularies," which are a spec-defined mechanism by whic= h implementation can extend functionality via new keywords in such a way th= at they can optionally be supported in other implementations. Furthermore, = this mechanism allows the other implementations to refuse to process a sche= ma that requires a given vocabulary if the implementation doesn't understan= d it. This bit I think is good for later when we eventually get to spec-def= ined extension mechanisms, but I don't expect that'll be in the first draft= . Yes, we need an extensibility (and evolvability) story.This will revolve ar= ound extension points, which need to be defined in a more rigorous way than= =E2=80=9Cignore what you don=E2=80=99t understand=E2=80=9D.We may also dec= ide not to have extension points (like JSON did), but we need to make this = decision in a very conscious way. Gr=C3=BC=C3=9Fe, Carsten --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_534112_1607705067.1615276034550 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This formatting (or lack thereof) removes all cues as to what's the Schema = spec text vs my comments vs your comments.

Greg

On Tue, 9 Mar 2021 at 8:40 pm, Carsten Borma= nn
<cabo@tzi.org> wrote:
Moving this discuss= ion to the list, because it touches a large number of issues.

I=E2=80=99ll try to = parse apart this pile of unrelated considerations; maybe we can dispatch th= em into the specific issues raised.

6.1. Range of JSON Values

An instance may be any valid JSON value as defined by JSON. = JSON Schema imposes no restrictions on type: JSON Schema can describe any J= SON value, including, for example, null.

JSON Schema uses the word "instance= " to describe the JSON data that's being validated. We seem to have landed= on the word "data." Regardless, I think the gist of this also holds true = for JSON Path: input values can be of any JSON type (although only certain = types may return results depending on the Path)

Yes, JSONpa= th should be able to be applied to any JSON data item (JSON value).
If we haven=E2=80=99t said so yet, that=E2=80=99s probably because it is= an obvious property of a useful query language=E2=80=A6
(Editori= al, if you ask me.)

6.2. Programming Language Independence

JSON Schema is programming language agnostic, and su= pports the full range of values described in the data model. Be aware, howe= ver, that some languages and JSON parsers may not be able to represent in m= emory the full range of values describable by JSON.

This, I think, is of utmost importa= nce. We definitely should not fav= or a specific language. Doing so would inhibit inclusivity and shun people= who work in incompatible frameworks.

There is a wide gamut= of meanings to the expression =E2=80=9Cfavor a specific language=E2=80=9D.=
Is requiring arbitrary precision integers =E2=80=9Cfavoring a sp= ecific language=E2=80=9D?  Specifying a specific regex dialect?
<= div>We may need to accept the dominance of certain platforms in our decisio= ns (e.g., the I-JSON limitations caused by JavaScript), so I don=E2=80=99t = know how to act on this.

O= f course, we shouldn=E2=80=99t wholesale import a language (e.g., as the ex= pression language), except if we do.

This stat= ement also makes it clear that it's understood that some frameworks inheren= tly have limitations that may prevent them from being able to implement the= full expression of JSON Schema. Declaring this outright allows such frame= works to have partial "best effort" implementations and still be compliant = with the specification.

We probably want to avoid complianc= e levels, profile implementation conformance statements=E2=80=A6
= Just as we need =E2=80=9Cextension points=E2=80=9D (see below), we may need= =E2=80=9Climitation points=E2=80=9D.

6.3. Mathematical Integers

Some programming languages and parsers use different internal re= presentations for floating point numbers than they do for integers.

For consistency, integer JSON numbers SHOULD NOT be = encoded with a fractional part.

I'm not sure whether this would app= ly for us, except maybe for array indices.

No idea what thi= s does here.  We don=E2=80=99t get to decide how our JSON input is enc= oded.
More importantly, we don=E2=80=99t get to see that (unless = we require JSONpath to be used only with a specialty not-quite-JSON decoder= !).

(But, indeed, we do ge= t to decide the number system used in our expression language.)

6.4. Regular Expressions

Keywords MAY use regular expressions to express constraints, or co= nstrain the instance value to be a regular expression. These regular expres= sions SHOULD be valid according to the regular expression dialect described= in ECMA-262, section 21.2.1.

Regular express= ions SHOULD be built with the "u" flag (or equivalent) to provide Unicode s= upport, or processed in such a way which provides Unicode support as define= d by ECMA-262.

Furthermore, given the high di= sparity in regular expression constructs support, schema authors SHOULD lim= it themselves to the following regular expression tokens:

  • individual Unicode characters, as defined by th= e JSON specification;
  • simple character classes ([abc]), range charact= er classes ([a-z]);
  • complemented character classes ([^abc], [^a-z])= ;
  • simple quantifiers: "+" (one or more), "" (zero or more), "?" (zero or one), and their lazy ve= rsions ("+?", "?", "??");
  • range quantifiers: "{x}" (exactly x occurrences= ), "{x,y}" (at least x, at most y, occurrences), {x,} (x occurrences or mor= e), and their lazy versions;
  • the beginning-of-input ("^") and end-of-input (= "$") anchors;
  • simple grouping ("(...)") and alternation ("|")= .
  • Finally, implementations MUST NOT take regular = expressions to be anchored, neither at the beginning nor at the end. This m= eans, for instance, the pattern "es" matches "expression".

Not sure if we're planning on suppo= rting regular expressions. It appears that some implementations do have so= me support, but it's all extension on the original syntax at this point. S= till, this is a good declaration of support.

As we define o= ur own expression language, we also get to define our own regular expressio= n dialect (I hope in a less mushy way than above).

It also ties in closely to section 6.2 regarding framework limitations= as not all frameworks support the same flavor of regular expression syntax= .

It may be worthwhile to quell outright the expectati= on that the JSONpath regexes can just be dumped into the implementation reg= ex dialect.

6.5. Extending JSON Schema

Additional schema keywords and schema vocabularies MAY be define= d by any entity. Save for explicit agreement, schema authors SHALL NOT expe= ct these additional keywords and vocabularies to be supported by implementa= tions that do not explicitly document such support. Implementations SHOULD = treat keywords they do not support as annotations, where the value of the k= eyword is the value of the annotation.

Implem= entations MAY provide the ability to register or load handlers for vocabula= ries that they do not support directly. The exact mechanism for registering= and implementing such handlers is implementation-dependent.

This is good to have because invari= ably, implementations will want to extend functionality beyond what's in th= e spec. It basically covers other implementations from also having to prov= ide the same extensions, requiring only what is stated in the spec.

It also mentions "vocabularies," which are a spec-de= fined mechanism by which implementation can extend functionality via new keywords in such a way that they can optiona= lly be supported in other implementations. Furthermore, this mechanism all= ows the other implementations to refuse to process a schema that requires a given vocabulary if the implementation d= oesn't understand it. This bit I think is good for later when we eventuall= y get to spec-defined extension mechanisms, but I don't expect that'll be i= n the first draft.


Y= es, we need an extensibility (and evolvability) story.
This will = revolve around extension points, which need to be defined in a more rigorou= s way than =E2=80=9Cignore what you don=E2=80=99t understand=E2=80=9D.
We may also decide not to have extension points (like JSON did), but = we need to make this decision in a very conscious way.

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

--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.iet= f.org/mailman/listinfo/jsonpath
------=_Part_534112_1607705067.1615276034550-- From nobody Mon Mar 8 23:59: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 4AB453A1676 for ; Mon, 8 Mar 2021 23:58:59 -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 qXk6i8PI1w79 for ; Mon, 8 Mar 2021 23:58:57 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27CC33A1675 for ; Mon, 8 Mar 2021 23:58:57 -0800 (PST) Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Dvnf73bCmzyST; Tue, 9 Mar 2021 08:58:55 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: <702108521.533403.1615275887380@mail.yahoo.com> Date: Tue, 9 Mar 2021 08:58:55 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 636969534.994846-b466382efad8abbf1c671d8d3ed6a577 Content-Transfer-Encoding: quoted-printable Message-Id: <98DD8D17-18EB-466F-AB96-F07EC57147E0@tzi.org> References: <8A691340-D265-4A50-A003-4E836CB80F92@tzi.org> <702108521.533403.1615275887380@mail.yahoo.com> To: Greg Dennis X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] [ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath] A "General Considerations" section (#58) 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, 09 Mar 2021 07:58:59 -0000 On 2021-03-09, at 08:44, Greg Dennis = wrote: >=20 > > Of course, we shouldn=E2=80=99t wholesale import a language (e.g., = as the expression language), except if we do. >=20 > This doesn't make sense. "We shouldn't do a thing, unless we do that = thing.=E2=80=9D Sorry, too terse. Long form: We should resist the urge to import a language wholesale, unless we make = a very conscious, well-founded decision to do so (probably after having = found one that fits =E2=80=94 I don=E2=80=99t know any, but I can=E2=80=99= t argue from a position of lack of knowledge). Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Mar 9 00:45:29 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 337E73A1799 for ; Tue, 9 Mar 2021 00:45:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.097 X-Spam-Level: X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 1ssk1Ai_fWKh for ; Tue, 9 Mar 2021 00:45:26 -0800 (PST) Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 7715E3A1798 for ; Tue, 9 Mar 2021 00:45:26 -0800 (PST) Received: by mail-ed1-x530.google.com with SMTP id bd6so18644026edb.10 for ; Tue, 09 Mar 2021 00:45:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=GjVR4MPu6lbfs4fycfB8IL67SzAaX8KGMll9Z4I+1Dc=; b=aU+67jaYLosky6CyNbs3iuTJhAAs7OZr6XEACReH33Nj5fHskTub1ikeFgoKdBLbBN OKJaXROt4wMh97dEDroE+te18FE4EeWOU7h2UzjQXdvQP+UskJBYGN0DFMHuKlnh7Xtn WbbTp3+MZyIAkCTM+kz4Hi+jyKe67djCqItbf0qNH0w+WIgHSa+1HIfVZwDC5UJQm7ZR W6RI1oUzJ6wKwyIwcpjLsUSxwYwQHaR/mr4D2qqak5JLwRh97gcKnAc9sToYsgdEQX5J MVFHr16uxWCwpP1DXzk0FNnYbWLfhoV8l0zMbGIPFrbEIDHOpJ/5OqzpKbUeMTXXw9Cm 30RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GjVR4MPu6lbfs4fycfB8IL67SzAaX8KGMll9Z4I+1Dc=; b=t4O4VNZb8gTQkg4C4lg8KUJVCVOE8GQzRpWqGyuWUVKbvdOEnTY/NTSx+stNZtjZVQ us/8/96X7M26b/L7/KBwZwdS6fx3G9KkbsLxMqAwnkTDtXkgc4etf2eiKdTxhFaZ264A YehDBcSrML42keG6dgVkHII41m7KejIr89rsoIeSzGbiJtG2kzedqDOyfLc9uZ//en3m bwm5ZOAP7atXVllgySCCfifFn4mlzI4kicgIYV90w+L/mGrpiEf1CMcHV5iIwYM8zfPN HwgCZZtSN3wgZwGMWcakAufS0nxPAXDsq1EMfbcpOuD7wzC8mbk418F0iRAH8BIXyfLC aQDQ== X-Gm-Message-State: AOAM531rcIF+Hs7n/YqqNOQ/fM8UHPhZzUVPAlV0zqbiO7ecNSoBv2yB Nz6sEhIiMRJwpy3QqNCQVCOnsSGGuBI= X-Google-Smtp-Source: ABdhPJxSKDliaL1NeNnI25mecRl5RGgRcGH+9fUdvRI5Ltklqv89296ijP1qiHWAfqcc/IYQZnJ8Vg== X-Received: by 2002:a50:da8b:: with SMTP id q11mr2918342edj.352.1615279524770; Tue, 09 Mar 2021 00:45:24 -0800 (PST) Received: from [192.168.1.95] (71.224.125.91.dyn.plus.net. [91.125.224.71]) by smtp.gmail.com with ESMTPSA id cw14sm8880885edb.8.2021.03.09.00.45.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 09 Mar 2021 00:45:24 -0800 (PST) From: Glyn Normington To: Greg Dennis Cc: jsonpath@ietf.org References: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> <1310281760.620946.1615275638486@mail.yahoo.com> Message-ID: <7b9f3d8e-a479-ad0a-848e-065a3959547d@gmail.com> Date: Tue, 9 Mar 2021 08:45:22 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <1310281760.620946.1615275638486@mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------027C89A7A972EC2D287AAF90" Content-Language: en-US Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 08:45:28 -0000 This is a multi-part message in MIME format. --------------027C89A7A972EC2D287AAF90 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I'm afraid I simply don't remember a compelling use case for index expressions which could not be supported by other means. It would also be helpful to include a compelling use case in the spec to motivate the feature. So please could someone oblige me by picking what they think is the most compelling use case? A link to a GitHub issue would be fine too. In https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/57, the consensus appeared to be going against index expressions, but then the discussion veered away apparently without reference to a specific use case. On Tue, 9 Mar 2021, 07:40 Greg Dennis, > wrote: Carsten, I think you've made a good summary of the problem space. Thank you. Glyn, both Stefan and I have shown examples where the index expression could be valuable.  You've suggested that we drop them in other places, and my response is the same as I've described in the GitHub issues: just because their usage may be less frequent doesn't mean that the syntax is useless.  I can guarantee that if we drop it, users will complain. Greg On Tue, 9 Mar 2021 at 8:34 pm, Glyn Normington > wrote: On 09/03/2021 07:20, Carsten Bormann wrote: > the expression language is used both in index expressions [()] Is there a compelling use case for index expressions which could not be supported by other means? (If not, we could drop them.) -- Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath --------------027C89A7A972EC2D287AAF90 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
I'm afraid I simply don't remember a compelling use case for index expressions which could not be supported by other means. It would also be helpful to include a compelling use case in the spec to motivate the feature. 

So please could someone oblige me by picking what they think is the most compelling use case? A link to a GitHub issue would be fine too. In https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/57, the consensus appeared to be going against index expressions, but then the discussion veered away apparently without reference to a specific use case.

On Tue, 9 Mar 2021, 07:40 Greg Dennis, <gregsdennis@yahoo.com> wrote:
Carsten, I think you've made a good summary of the problem space.  Thank you.

Glyn, both Stefan and I have shown examples where the index expression could be valuable.  You've suggested that we drop them in other places, and my response is the same as I've described in the GitHub issues: just because their usage may be less frequent doesn't mean that the syntax is useless.  I can guarantee that if we drop it, users will complain.

Greg

On Tue, 9 Mar 2021 at 8:34 pm, Glyn Normington
On 09/03/2021 07:20, Carsten Bormann wrote:
> the expression language is used both in index expressions [()]

Is there a compelling use case for index expressions which could not be
supported by other means? (If not, we could drop them.)


--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath
--------------027C89A7A972EC2D287AAF90-- From nobody Tue Mar 9 01:03:30 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 E5EC03A17FB for ; Tue, 9 Mar 2021 01:03:28 -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 xrmzPzt6oz3a for ; Tue, 9 Mar 2021 01:03:27 -0800 (PST) Received: from sonic309-13.consmr.mail.bf2.yahoo.com (sonic309-13.consmr.mail.bf2.yahoo.com [74.6.129.123]) (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 3449D3A17FA for ; Tue, 9 Mar 2021 01:03:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615280604; bh=0pj+dLriRwFuvTapsAJd1R/ItL3abiRu95EzyInfYSM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=CLEqI7jJhLIPVYJI8PZIMy28zQRlfJJlptLlMOfcu6Y6Gy3Hs7von1danTzi1VdNpmrE0aF0JlBkuJaUFLNOBd3mFkC4eDhGVekCqgx23AKT7KklawJH9A56HgrSDp+lHNxaytGgmOLcayBlWY1O1mwSU6Nmf+t4U8C3kv1CLbJ3B89jpAaUdLbjMA2guqd65liQb/YxOC1pmdgl1zpRSmJXbGQg+mwj9p8MvxKZPL4hlbHS9t3cfRSpOGAO41pE8Tl7dEGhbpwBUAOoeiiNbmTgmN6dKceg7igWWbhdVtbffNPN2FdTctZvWcyB6TSXbFTbi8EGQxW1MOA4OVVuSQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615280604; bh=NkCr8pSzszRGvLLOQ1b05RgsDEKUynQF1CPaZ+csYYN=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=QrUAKQEqknqGCojGmLt7degXn9W0qOSSLQHbJLfHQl5q5oxurEDCc1rUb+mvzKnNYt9dWYtjDBEdbi9Y5vNsAe5rqv1ecFHHX7Vp9gafb7I6MWJlItTMLVPXz3AWgntcsxwtvwRWxOonqHspnEHg8skD4SkILTSeq2bF3qtv15LQctxgvJzaZiuaXUaI7aNdsq34hr0AOLCyHi+HDyZOXjAXcBgKU2uYe57rk663I6G+WZcRlDewowE/QplCTzdERBsDjDeecBIPLYDxqG+lCF146zeamRkaks792y2/cF2h3qxg2H+fm1BCuKJmaHsSav5FoKY7ytd9msa0xOIQIw== X-YMail-OSG: dEPwkSoVM1kONvvC4H6HLYUE7drvnXk5oQmJXJo6J0q2edw_68gmN10r9N22OhU 67GLNxrBikoSN_AvEzjOMQvojwQlVXloPCmmmqAQA_KGaH.7jPAmisk7C3R8nd6rGzJrkDvcbBbB H0RvFDG6dEGhH8OtN_6DlyPaTDVYGn3ie0rN2PayC2JfN5Bmssta3qgKe_5tuyAx8MPaSsJ2bMTc H_HBBRFimSlHElimndUdmL9aeGyzaNSbjV7MA99UKqcljeRIyhmGsB61AzORB5LCvK5dahcK2dkG Ck6aIRJ.tKOMxiNQ_sxpI0MKW07OgI0mx82FHLB1jvXMeZvSs9n2KJTr6CKA_irGNTandd1Zd2C_ paedVBUkrYmfGc.Dlnj2.RB.9NGP3ZUy.oeSVZDSGJzPqNA9AoAnzJuZ.98sRLILcrspo_WKGgim nFwYxX0SG6mLKFkLTbb5j8Nwgj9A9iubMXKX8zuY_zaZuE7RpWIMd4nJP5GvnJUvW6pR9zPvzPnY 7TBjhbLZ56tb9XRMbyHx.XUH67N3WGd_IVBq_rmbewYc.aewaBMl6mdkUzAsA7zc0zzLqOZjP9JP zg2SVxN.vYp9EE2NaEBivH8bwXhxeO5.skDjLbGu39ZgL6EdXoYJZzqu3QvLyU0IMy9ZEHu08YrC Yz071XI.sPBtSdMZieZ.L._SjGA7NZi75AEoOTfTIrOFCV49xN7050fe1wn2doBQM6jMUGly_l8I vb.ImTY5qGrQ69OlnsZ5r2b_9X1i4SbQx5D703L.GPxN.ABNpq4PP7JJEEs3bGoVuDBu6DkQroWh A7zo1GfkCb3o3W3GONtE3eVX_9tp4Fi.bbvWhx1ub3GSljqplM7Wm7lMjHBPlm97G.Wj9sakRehv 349KSHgAHKz1aL.XkJzxVJ5qu7yDatmN4.fFPQy2EtXdOWmxbes3g2k9wMfqGjST.irdXrInDrz0 6LqxB3NwsEGQ1qVsxTK8D2gwZcto0pmkHGnwU6cleXlscaSqRn0oW7RWzlzYmEAQNR_dLbyJOZbY 9Zi.ZQAcq.qTbWnhl9pekCJAUd642CF1uUgqAVMV6tVaFRjjy1bwrHMSvB5ri9pjWEKwoRWOazLB NsZzjemy1St7QBKUlVcSvkLy_qnAEJlYvQsKG2seTDa1OoEN01jnp38ALGtzCatiJZWY5wNDMKUD eN3EN.Xs181XjfOG2kH.7jRPEwjtCaQ8163x0L4EMOMZyRqhEjfDDxw4Mhoe5Jioe9RBRpguU2zV J150nzInEB1Nrxyg4_yUWq7svp.UsCrTgHEFV_UxMLCXEy0.I1FQAjbXv7mCX_2lbMfu1d2tRbMf m13pCRKYnLZIMIdP6SRXzWyp6_QsErck8aynEcjE3Txv9UNQKLaEpc58oZQYMaIcWS4c5rV.Rcch TXuUdCnxxRYAYBzgKHVDFbK0biOTcIj6PYlYxZSB40J4artV6ZRXGVbXn2KVS4R9.PfFOGK06Jlm XrsvNVOLq6BNdTXSukKncI0.GfhymxY3ZmCNDA.kacvAXxIrH9PLzMRs13U4zeKlOF8AqT9e_lNI GOfTqqkl2EDqFpISSWUWKE.oblvt3uBE4i_wl6sFoKeaZYgftOilTWf_BpUAF4Wr2J8FtpB2VNwg hlZTeME1dkYC02bsiFSHjYyfsjEtDZLFqX9nejNkd_xuOdc7bqSPWbpDIJBPubkIkJ4JBQfF3__C w8tL5.bAx1aCwLte3QGogsRrN8d90JCMgPOUk0lS_R.ZwcqcXaJzXWLumg7clnZd.jcjOY.IsxdA RI2glOHS3PRweAhpn2lfRJEJJaa_7emGsVL8OyaVl69eS3EtyAXodHY0X.OaWh1qiU6YC.Mc.dr0 5LPjxLNodPgdbQFJI6yjh_mlBZRnPEg9wte6MXfn.WgN4cm_Mc_4NO0YlLREXPXAonnea3pDCKkk CvcYzNsd26sOLeYUrJRlphhbgThccT5SgR_d70Mx3BfqIDzU1Abh.EKIoCB64gCZYR3JlxMRXRqx O9U.7Z.rftfu9aWS3Ve4XG0lAmpBKMGQFl9j44g93tM5PqxFnaOHAUhiA.UPNlaUEfE2nTLScOdb eVJkWHRF5FzjP16mosifmu8vCK7ccMkHWpxspBGBJEaRiUbaaIB4LPAB6ynh5A_UBERoGD7Izmcp 8F5LB1dq83vTBtz_nKhkfTzduspjGjrYmAURJ.TeCb5DU3PgwwMThSkbW7LCpVRV7G8xHGQrFj7v 9IkDjSohFHKK6Dpmke0k1RCKb3QayBoI_UJHqPv7Po0gfoL7jVVy.pBoTPzQ.PHZiy9Qbf_6FRrK KTm6hGlsf.o8anVSjC0Y6pa0W_YuaG8I1V4btq07TLjiQb5CctOoRATSNOFpNNPGPog.e5howjKn 3WG_vs3MwFp9.dNBwP2.NFSXGyAGEeoxYSV04baUXaD6oDwvrrKPwrKBsUdFIg7tlTVJWMkAQ5w2 xC_hAPwTg2KRZk6pmftSktZfV72TTBXLicnEHNXGj6NZmEf6sqlsgmMs9xvEvOcbuAGPZ6tC_wkV 4vGrj5vY.E5yR_sMUjSjR1WdCnAAqJI3ccODU7SMIPq786IYiq.2aFoeqeBldMEVoLvs6oIAUxnn 0XwACcOSp2tRJxtg7VEC5ana3GKFPDSLI9G7ttjaHbJ8eYOKwenY3ALYisNhLSGuf_GRHEO0YmNc W69jRlEinmbwtE9QPBT1TXKSf67c9Jq64HWwRQzqB4Tq4ezu7_xMqnITTTW5N2t4gLVkJ610eCnq vXrmyIPE- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Tue, 9 Mar 2021 09:03:24 +0000 Date: Tue, 9 Mar 2021 09:03:19 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: glyn.normington.work@gmail.com, Glyn Normington Cc: jsonpath@ietf.org Message-ID: <164919508.621594.1615280599076@mail.yahoo.com> In-Reply-To: <7b9f3d8e-a479-ad0a-848e-065a3959547d@gmail.com> References: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> <1310281760.620946.1615275638486@mail.yahoo.com> <7b9f3d8e-a479-ad0a-848e-065a3959547d@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_621593_73102292.1615280599075" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 09:03:29 -0000 ------=_Part_621593_73102292.1615280599075 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/= 57, Stefan highlights several use cases where the index to be selected coul= d be contained within the data itself.=C2=A0 I'd be interested in knowing h= ow to achieve this with the filter expression or any other mechanism we've = previously discussed. Further, I've given an explicit example in https://github.com/ietf-wg-jsonp= ath/draft-ietf-jsonpath-jsonpath/issues/17#issuecomment-701892056 =20 =20 On Tue, 9 Mar 2021 at 9:45 pm, Glyn Normington wrote: --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_621593_73102292.1615280599075 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/= 57, Stefan highlights several use cases where the index to be selected coul= d be contained within the data itself.  I'd be interested in knowing h= ow to achieve this with the filter expression or any other mechanism we've = previously discussed.
<= br>
Further, I've= given an explicit example in https://github.com/ietf-wg-jsonpath/draft-iet= f-jsonpath-jsonpath/issues/17#issuecomment-701892056

On T= ue, 9 Mar 2021 at 9:45 pm, Glyn Normington
<glyn.normington.wo= rk@gmail.com> wrote:
------=_Part_621593_73102292.1615280599075-- From nobody Tue Mar 9 01:18:20 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 096E83A1847 for ; Tue, 9 Mar 2021 01:18:13 -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 OHZqBxjPA3xL for ; Tue, 9 Mar 2021 01:18:10 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8788B3A18CA for ; Tue, 9 Mar 2021 01:18:04 -0800 (PST) Received: from [192.168.217.123] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DvqPP4HL4zyX7; Tue, 9 Mar 2021 10:18:01 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: <164919508.621594.1615280599076@mail.yahoo.com> Date: Tue, 9 Mar 2021 10:18:01 +0100 Cc: glyn.normington.work@gmail.com, jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 636974280.666569-d581a9f04889cf9f996428c6abf13451 Content-Transfer-Encoding: quoted-printable Message-Id: <1C6B834C-9523-4500-B547-524EC1B67CD1@tzi.org> References: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> <1310281760.620946.1615275638486@mail.yahoo.com> <7b9f3d8e-a479-ad0a-848e-065a3959547d@gmail.com> <164919508.621594.1615280599076@mail.yahoo.com> To: Greg Dennis X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 09:18:19 -0000 Who provides the cheapest flight from London to Berlin? (Maybe too hard for JSONpath, though.) Gr=C3=BC=C3=9Fe, Carsten > On 2021-03-09, at 10:03, Greg Dennis = wrote: >=20 > In = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/57= , Stefan highlights several use cases where the index to be selected = could be contained within the data itself. I'd be interested in knowing = how to achieve this with the filter expression or any other mechanism = we've previously discussed. >=20 > Further, I've given an explicit example in = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/17= #issuecomment-701892056 >=20 > On Tue, 9 Mar 2021 at 9:45 pm, Glyn Normington > wrote: > --=20 > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > --=20 > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath From nobody Tue Mar 9 01:51:11 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 B3AE13A18C3 for ; Tue, 9 Mar 2021 01:51:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9AYvX6UKQOeM for ; Tue, 9 Mar 2021 01:51:08 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (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 78F793A18BF for ; Tue, 9 Mar 2021 01:51:07 -0800 (PST) Received: from [192.168.178.20] ([87.123.195.255]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MZCSn-1lEs592WSv-00VBbq for ; Tue, 09 Mar 2021 10:51:02 +0100 To: jsonpath@ietf.org References: <516461B7-C586-4392-8F49-B4A6E88C973F@tzi.org> <1310281760.620946.1615275638486@mail.yahoo.com> <7b9f3d8e-a479-ad0a-848e-065a3959547d@gmail.com> <164919508.621594.1615280599076@mail.yahoo.com> From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: Date: Tue, 9 Mar 2021 10:51:03 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <164919508.621594.1615280599076@mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------9AA994C9426ED76B72193079" X-Provags-ID: V03:K1:TwN9p26kBIr47tV/Xxoz1w1Xfjks9Jblo9/SNqNBP3UOZQzFfYg WhQM9RXWr2miPi4Kh4qFn1RW7JZcbYGptE9BGDiY0HC3qzL5AqvKNCnkLzJj7+F7HsrmYqL L/vHUDleGKEGIA00UpqIOoOSJL1h+1jqpNQUl713TwhSIjzQy1lHwagCgZ9PMJfXeE+oFx9 cZdhBFWyttENPNn8le5BQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:9CbeeUeDuEU=:g/bJDQy/0Fd3HjOZQJhVmd lT/azU8sCKxQOQtwbBj2wnqiilzLfiJuTaV3gmiLo+vYR68rMJKs2Mbcrs5vdAROM33aY8pwP wxhpRuKlp/K0BipGrgN1XYWY2qlh6JZERqRWYsu7L+DcTPwUBV8W03ecDVeKiGfLoS3y1JUTP TrzfuxikgMrKIkwPfHBSMniVRvK2fCpSB8lPnJFvhTh3i/utE6ZPsJAHJYhJu978qe07Wgf6l XRN5Yr1/qt+76xBxiIhRqjuocdp700+4LnMvDg4bp1LlFxxR56nKAYe1ziGEdYwNXL84fqnrv WuUOXV2sSV0bgafdDdXWZ9jZMp0JKSSFNC4H3IRNmuv65TZ0v0qnXRR8HdJqWrZZtMKUD31l0 Rfv6QgedaEyL3DH8PUTHPG/TwhA8vmPVRYaHfSCVS3cmZ5FrLnJ2C8tw/UsEvi2O4mimkuA+U d7gpiJNd1gSIdVomvoATDd7cysAVJ1taWmHVZkSp0+1FJPDHwrvLpm2DcnEw2xRy+5XGTIntZ A== Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 09:51:10 -0000 This is a multi-part message in MIME format. --------------9AA994C9426ED76B72193079 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit hmm .. in ... https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/57 I presented a single use case using root selector '$' by referencing data in the same JSON document. I named it 'level of indirection'. Regarding practical use cases of the current element selector '@' there seems to be a general cluelessness (apart from that '@.length' thing). So let's focus on filter expressions first and and possibly include index expressions (good terms here) together with union stuff at a later time or exclude them completely. Am 09.03.2021 um 10:03 schrieb Greg Dennis: > In > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/57, > Stefan highlights several use cases where the index to be selected > could be contained within the data itself.  I'd be interested in > knowing how to achieve this with the filter expression or any other > mechanism we've previously discussed. > > Further, I've given an explicit example in > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/17 > > On Tue, 9 Mar 2021 at 9:45 pm, Glyn Normington > wrote: > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > > > > > Virenfrei. www.avg.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > --------------9AA994C9426ED76B72193079 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit hmm .. in ...

https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/57

I presented a single use case using root selector '$' by referencing data in the same JSON document. I named it 'level of indirection'.

Regarding practical use cases of the current element selector '@' there seems to be a general cluelessness (apart from that '@.length' thing).

So let's focus on filter expressions first and and possibly include index expressions (good terms here) together with union stuff at a later time or exclude them completely.



Am 09.03.2021 um 10:03 schrieb Greg Dennis:
In https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/57, Stefan highlights several use cases where the index to be selected could be contained within the data itself.  I'd be interested in knowing how to achieve this with the filter expression or any other mechanism we've previously discussed.

Further, I've given an explicit example in https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/17

On Tue, 9 Mar 2021 at 9:45 pm, Glyn Normington

Virenfrei. www.avg.com


--------------9AA994C9426ED76B72193079-- From nobody Tue Mar 9 06:20:10 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 804053A0D74 for ; Tue, 9 Mar 2021 06:20:08 -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 4cyLgm7kp1Es for ; Tue, 9 Mar 2021 06:20:05 -0800 (PST) Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 A8C7B3A0D6F for ; Tue, 9 Mar 2021 06:20:05 -0800 (PST) Received: by mail-wr1-x42f.google.com with SMTP id e10so15897277wro.12 for ; Tue, 09 Mar 2021 06:20:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=myMYIP2MulNkRnjL6OXOI+OzXduifm6zrZkmV2/JpqU=; b=pwq112Of4mXhrOHDXT+nomE251lorzggyOzF44XWOt6gbRnTf5fWvQch81QDkTpk5R 5JD3Md+KjDF30UVecKGxvjHP4zyKLcLSK5wPM9+vfFFrghA+JoZrrMulYAUQ4MejXY78 feNvU0GXWLbmQJ50t6Pc24dukt75hpRrvrYCVFx+J0n1tlacfh16FVFTrtfqgh42gO+b pq1bpxeOH0RVme/yN+g4i1rRhc5IH850LDPPoPBCEWmk7a8ZxiI4Bz5pfeKPdLoa3moW UzpIzLR1nUFEW/KukKmGi3Yp1pRCtyOBTFcBFdICHdml52RrFuBE6FmvH6W11mkzC7ev 4l0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=myMYIP2MulNkRnjL6OXOI+OzXduifm6zrZkmV2/JpqU=; b=NOrAT2Tk9eBwgzVlc4rcx/PLaxC8Bznz0dbJlEneyC+YJpZtw9B29ma9r1A0/2Fm13 N9f5+zzgMhqz5uZSjV7ll0XvNRTs/PPb1kn5FV9aXt17ma/k6OV6HpsmQ4rLHhFC3bRN L2ww0JDnVCaDpiPFp7JsZOjCqnLqAhrWs07530krfaZ43MJTkYXcg2Vqle+Su3jquaU/ HSquvRO+nw3T4SId6YvMRmEk7pnKX1tzZrRf19cHPNxXgsHXlQvpqqzZfFICNiBR5nSW 7mYMJXxI0MRn9QWFWJKQM//kpEIgAvcBy5TIr1INDqURUayemJITEczmQVzztdO8QpMu 9FOQ== X-Gm-Message-State: AOAM5300OAs5omwqPkrDAEWd3rJd7jge0x8z8VuSE59JFItPEYxmUuvz 9vd76j/J4KoFvkms3+/9uzm2La4NtgOMO5mTbTqwMGVDJc1yng== X-Google-Smtp-Source: ABdhPJx4ar3U888+A0U5vLeYjrICMs13/pTqMLMbHDf06N1RHLkmU3tTnrL0Pt3l6W2UEhTc76XrzYRZzTkabeaPIbk= X-Received: by 2002:adf:e5c4:: with SMTP id a4mr28375015wrn.174.1615299602329; Tue, 09 Mar 2021 06:20:02 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Tue, 9 Mar 2021 09:19:49 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 14:20:09 -0000 > From: Carsten Bormann > I think what we have so far is: > > =E2=80=94 there needs to be an expression language that is independent fr= om specific > implementations and their implementation languages. > =E2=80=94 the expression language is used both in index expressions [()] = and filter > expressions [?()]. > > Obviously, in index expressions we need the expression to return an index= value > (integer, string), while in filter expressions we need a Boolean value. > Also, in index expressions, the implicit parameter @ is the item to be in= dexed (the > item to which the [()] is applied), while in filter expressions, @ is the= item to be filtered > (one of the items in the container to which the [?()] is applied). > > We have a dial we can turn how conversion-happy the expression language s= hould > be. > E.g., the conversion from the filter expression result to a Boolean can u= se a big set of > =E2=80=9Cfalsy=E2=80=9D values (false, 0, =E2=80=9C=E2=80= =9D, [], {}) or be more restrictive in what it accepts. > Similarly, the conversion from the index expression result to the array i= ndex or map > key (JSON object member name) could be loose (e.g., converting numbers in= to > strings) or more strict. > > Generally, both kinds of expressions won=E2=80=99t know statically to whi= ch kind of container > (array, JSON object) they are applied. > It should be possible to write expressions that can operate with both kin= ds. > Surprising and error prone conversions should be avoided, though. > It seems to me there are a number of distinct issues when talking about expressions. (1) The unary and binary operators to support, and their precedence and associativity. My own suggested list would be https://github.com/danielaparker/jsoncons/blob/master/doc/ref/jsonpath/json= path.md#filter-predicates (2) What kinds of operands to support. My suggestions would be (a) JSONPath expressions, relative to either the root $ or the current node @, (b) single quoted strings, and (c) JSON literals. (3) The meaning of an expression with a binary operator and two operands. In particular, the meaning of an expression when one operand is a JSONPath expression, returning say [0], and the other is a JSON literal, say 0 or [0]. (4) As Carsten mentioned, the rules for determining the effective boolean value of a JSON value. (5) Functions. Functions are unquestionably useful in filter expressions. Implementations that use Javascript or another scripting language for expression evaluation of course have them. There is also prior experience that can be drawn on from implementations with their own expression evaluation that support functions. Another issue is whether expression evaluation should be a separate component, or integrated into the JSONPath grammar proper. My view is the latter. A number of implementations take that approach. Daniel From nobody Tue Mar 9 07:26:34 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 2EFBD3A1001 for ; Tue, 9 Mar 2021 07:26:32 -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, RCVD_IN_DNSWL_BLOCKED=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=ispirata.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 cxZKdhKBZIU0 for ; Tue, 9 Mar 2021 07:26:30 -0800 (PST) Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 5DFC33A0FF2 for ; Tue, 9 Mar 2021 07:26:30 -0800 (PST) Received: by mail-wr1-x431.google.com with SMTP id v15so16427556wrx.4 for ; Tue, 09 Mar 2021 07:26:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ispirata.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qfqX9kFV6RCLdl1D4On7yOTFV9+CdZjTp9mPco2XEQU=; b=aacqIMLWNn6fYdjXYLLxwkwBDOH2l+YoHR51cx4O5d8oymKoyIBztoKTFsH3WGhbyH uAW/C8bZ8H0boSnFUxbcytIzy+8zxmkkpW0AOECARoKy+y+LawUfphCPYBc7Y3IxgmUz WXN2QgvsmZ5PZBp58Q11l3up5lqr9VptPIZESDTigSjboGqQzJcTFG8Eg0C8G/JOuSif 2Nz6RNj3jqLl14cvHKomyc3Vh4QEobR6BJj590Nr/JCy+xU7kWIlGkRrjebumxZNqrY2 EeVae7ezWu5GezgCYBvX6o/PL61jw9+XaHkCXoN0jfgOj1p/AXWM0u/Hdj92eJxG27wW k3pA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qfqX9kFV6RCLdl1D4On7yOTFV9+CdZjTp9mPco2XEQU=; b=ckrouEAppZ2nv5M0qbNMmzRNnLtrbEXtqRdCebC6oytji+ZMGzZW3ochOKuNvgcAwh EJmHNke0bfqpiyZ6sI9GXhL15ViTRp9jAXr6RZyjC0r04RuPQerTjXxMWaoQY5JiBua7 xnbwFFMd45+4Ovc1LKMBwRbkkXouyPUb/Tq1UaMFn9joC24sLZvFNr+3S7Nv96B2PWPm f2UsTcbhRbVc4ZcCpc8gq8jip1NH2VkhVSSbarc1VI6Vp8KtuRcCVESq65CoEGHeMvYg yookujtYknWu/e355Eq51KSLlgR96HCq1fSyztMcEk+zRkxRBIMf7stcPN/thwdDXacv tMDA== X-Gm-Message-State: AOAM5304MqG9hr4tCYcg0BUc4xjfEgwdL30xCEE1WFTCdW7fpkhNsF7U akLIuejYiNMvqhCJE8/b8siEJ8CJaGQFgPPq2/RYRjkP7maPDg== X-Google-Smtp-Source: ABdhPJyumS/wl/h8wN/ZW6IeGKz2nDaLOzjbwjy+PtSQJ+1q+9VHs0oDd0zrbIbibUHkfz3bSZ42yxmmgs7W8Pp7Bio= X-Received: by 2002:adf:a2c2:: with SMTP id t2mr28684698wra.47.1615303586886; Tue, 09 Mar 2021 07:26:26 -0800 (PST) MIME-Version: 1.0 References: <75DBBA4A-42F9-47E9-B0E6-ED84F09D434F@tzi.org> In-Reply-To: From: Davide Bettio Date: Tue, 9 Mar 2021 16:25:51 +0100 Message-ID: To: Glyn Normington Cc: Carsten Bormann , jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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, 09 Mar 2021 15:26:32 -0000 Hello, I opened an issue on this topic: https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/59 To be honest I am still of the opinion that omitting $ is the right approach for relative JSONPaths, which is a similar approach to XPath relative paths (which they don't start with /). Anyway the most important thing for me is to reach a consensus on the idea of supporting relative paths (to the current context) with some kind of syntax. Regards, Davide Bettio. Il giorno ven 5 mar 2021 alle ore 20:15 Glyn Normington ha scritto: > > In filter expressions, I think paths should start with @ or $. If we allow one of these to be elided, then the user has to remember which one can be elided. > > I'm sympathetic to optionally omitting the initial $ of a JSONPath expression because this is unambiguous, but I would be happy with $ being mandatory since this is consistent with the above rule for filter expressions. > > On Fri, 5 Mar 2021, 09:59 Davide Bettio, wrote: >> >> Hello, >> >> > Well, JSONpath is a bit like XPath, and a lot less like XSLT. >> >> I'm aware of this and I also agree, however I still need to understand >> if we may support any kind of semantic for accessing any current >> item/current context rather than the root item (which is identified by >> $), which are the points 1 and 2 of my previous mail. >> >> On 2021-03-04, at 17:20, Davide Bettio wrote: >> > So I think that the following 2 points need to be addressed: >> > 1. Do we want to allow any kind of reference to any current >> > context/current item with a standard (or prefered) approach (such as >> > the mentioned relative JSONPath)? >> > 2. Do we want to use paths without starting '$' or the '@' for this >> > kind of purpose? >> >> Clearly I don't need to discuss any templating language at the moment >> here, but I brought it as a practical example which is useful to >> explain why I need to understand if we are going to support relative >> JSON Paths. >> >> Furthermore I'd like to understand what kind of opinion people have on >> paths that are not starting with $. >> >> Regards, >> Davide Bettio. >> >> -- >> Jsonpath mailing list >> Jsonpath@ietf.org >> https://www.ietf.org/mailman/listinfo/jsonpath From nobody Tue Mar 9 09:51:29 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 5B0D83A14A3 for ; Tue, 9 Mar 2021 09:51:27 -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, 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 FgkypBUGgugL for ; Tue, 9 Mar 2021 09:51:26 -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 9E7223A14A1 for ; Tue, 9 Mar 2021 09:51:25 -0800 (PST) Received: from [192.168.178.20] ([87.123.195.255]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1N1cvQ-1lmBjH3L2m-0121LY for ; Tue, 09 Mar 2021 18:51:23 +0100 References: <15fd7d6a-a262-6df7-2cea-44d8e50dafea@goessner.net> To: jsonpath@ietf.org From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= X-Forwarded-Message-Id: <15fd7d6a-a262-6df7-2cea-44d8e50dafea@goessner.net> Message-ID: <65658184-c32d-33c9-cbfc-fe4342d935d1@goessner.net> Date: Tue, 9 Mar 2021 18:51:22 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <15fd7d6a-a262-6df7-2cea-44d8e50dafea@goessner.net> Content-Type: multipart/alternative; boundary="------------F64930566C549225D232A1EA" X-Provags-ID: V03:K1:0rK6R62SDvGxBEj8YyldWlA9yxzotDoTVTBUczcWZIdY5awDWNH 9vshXDTsiBCKph6t+V87+RHo+btAgkEGXiuFFwAJcjP28hxzYPcBA1RuJdxXXXS7EM+WlUK SUFWjsFFWSVK0S6tBMSbgatvShtcqFgOMhKX0faRobglRStjd+BFjho3pZixqONP6cbH9Kj fvLfdYc31pcmafA5WJAfQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:iBo+buDP9kA=:ekdLb8txHChIfj9THeal83 sJEkPiHrKutTVy3FPGhHNqDWA3aYY6k0nD9WV46x1MOPSrrAnd+MraPLM7uFXXONOMrUL3nIW nLc0lbIjFkiXWrF9SvT4JcScH7iQ2PmmHyptBytt3s/0jm+P+79MO0QygDFsDg7aVhiXuDS7A M39xrLGXC8uRGNQczYrLGEMK/KcjqMybDHbHMOPQbKpzkshDEZUgy+pLVPrFqnLi82thwjaHg zvFa0zRvotFQeQlXl1FChif2tasuLGHeUlZk7dFcpQmEMrg1hIXHyTf+AUZiUQ/mswQ3a6gqr GBKdKtwBqiacvwsUTcyHWNe1E8F0MvlJrObBU2QvZG73uCk4s0fNJw7CS9B4t/cs+0raCQTGO mkvuIgJ47+EL2rY1wXhiouxQR48Tb7A2IPXmpfcQ1KXcDNBknhRYto934zMooHiTdzyQuzVbS Ktunhd/l0XBynPxNDTQ9KLQ9MHekgww= Archived-At: Subject: [Jsonpath] Fwd: Expression language -- index expressions and filter expressions 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, 09 Mar 2021 17:51:27 -0000 This is a multi-part message in MIME format. --------------F64930566C549225D232A1EA Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit ... this is a good summery ... Am 09.03.2021 um 08:20 schrieb Carsten Bormann: > I think what we have so far is: > > — there needs to be an expression language that is independent from specific implementations and their implementation languages. > — the expression language is used both in index expressions [()] and filter expressions [?()]. > > Obviously, in index expressions we need the expression to return an index value (integer, string), while in filter expressions we need a Boolean value. > Also, in index expressions, the implicit parameter @ is the item to be indexed (the item to which the [()] is applied), while in filter expressions, @ is the item to be filtered (one of the items in the container to which the [?()] is applied). > > We have a dial we can turn how conversion-happy the expression language should be. > E.g., the conversion from the filter expression result to a Boolean can use a big set of “falsy” values (false, 0, “”, [], {}) or be more restrictive in what it accepts. > Similarly, the conversion from the index expression result to the array index or map key (JSON object member name) could be loose (e.g., converting numbers into strings) or more strict. > > Generally, both kinds of expressions won’t know statically to which kind of container (array, JSON object) they are applied. > It should be possible to write expressions that can operate with both kinds. ... human JSONPath text writers usually know, what they want to address by '$..[3]' or '$..['name']' ... but during selection process, it will be applied to both types of containers in the loose case. I vote rather for the strict case with not converting to '$..['3']' and '$..[int('name')]'. --------------F64930566C549225D232A1EA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 
... this is a good summery ...

Am 09.03.2021 um 08:20 schrieb Carsten Bormann:
I think what we have so far is:

— there needs to be an expression language that is independent from specific implementations and their implementation languages.
— the expression language is used both in index expressions [()] and filter expressions [?()].

Obviously, in index expressions we need the expression to return an index value (integer, string), while in filter expressions we need a Boolean value.
Also, in index expressions, the implicit parameter @ is the item to be indexed (the item to which the [()] is applied), while in filter expressions, @ is the item to be filtered (one of the items in the container to which the [?()] is applied).

We have a dial we can turn how conversion-happy the expression language should be.
E.g., the conversion from the filter expression result to a Boolean can use a big set of “falsy” values (false, 0, “”, [], {}) or be more restrictive in what it accepts.
Similarly, the conversion from the index expression result to the array index or map key (JSON object member name) could be loose (e.g., converting numbers into strings) or more strict.

Generally, both kinds of expressions won’t know statically to which kind of container (array, JSON object) they are applied.
It should be possible to write expressions that can operate with both kinds.

... human JSONPath text writers usually know, what they want to address by '$..[3]' or '$..['name']' ... 
but during selection process, it will be applied to both types of containers in the loose case. I vote rather 
for the strict case with not converting to '$..['3']' and '$..[int('name')]'.

--------------F64930566C549225D232A1EA-- From nobody Tue Mar 9 10:17:50 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 E31403A1510 for ; Tue, 9 Mar 2021 10:17:48 -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, HTML_MESSAGE=0.001, NICE_REPLY_A=-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 xgghezxGT8N4 for ; Tue, 9 Mar 2021 10:17:47 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (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 0487B3A1539 for ; Tue, 9 Mar 2021 10:17:46 -0800 (PST) Received: from [192.168.178.20] ([87.123.195.255]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MxDgm-1lhnJx12aW-00xbky for ; Tue, 09 Mar 2021 19:17:45 +0100 To: jsonpath@ietf.org References: <15fd7d6a-a262-6df7-2cea-44d8e50dafea@goessner.net> <65658184-c32d-33c9-cbfc-fe4342d935d1@goessner.net> From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: Date: Tue, 9 Mar 2021 19:17:45 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <65658184-c32d-33c9-cbfc-fe4342d935d1@goessner.net> Content-Type: multipart/alternative; boundary="------------DE0C231D5DB9A994D3357821" X-Provags-ID: V03:K1:fmqqbEFeMZ2Rb+HKv7XozceBLDYYLw6l4C+430+S9d7f6SeNyK6 zWx4InFMTkSHFe5fFliJUNWV3s4s1cnAsV+aM4HsLe+NrUicC25KwRHzLdECllZIyzMwv/u G+2s/6FJR7V7ns9c0gk9WcYE7qRsAHvDQIK6h1zccvHOOqx2G64bzKtI1wRadae2ymfIETl HxpYuFqD+cykOVrBhJWww== X-UI-Out-Filterresults: notjunk:1;V03:K0:HHmRvwMuOnI=:RiwL9nUdnDvJfMJxSK9bhP CT4vUA3Dk7GWnyx/D0Db+UbiOo7duTJi3MaNqDCwiXxlHhPJ84I/uGf/a1CRi4t2tiujyxdmv MR1Mn8mG/VpA0cRMuSHWzO8QlwhIHoagA03Zyy+CYG/Vmw/3GbcEtdd/4xC5gWBW3BvYLQcqP RI9+4FCjv+rlW8sDjHMT62wC8s0smpRfJkDEGBlZjPneAI3Oi52d+4Ag4iP3/BmMsZNRB1VXh D+qyGZ2wyexmJS+Vr5my+vts7/YZjoQQvBN2j1KRBMUfbEstsU0DWiWyPDCryo+LTOccKwGyL uv0IGYe+l1aWNe3isToASZlZqSQsu8NRB8/eDQ3wbma3HycsHMjn6XJsoi4xAbLXSaIGxeAoc hWtUxDR+6s3VTQRsRzuyn7piLkiPGZVVlgZZBrKkmY1ooNHfTUTBGo346q8tCkgHvV/GM4D58 vO42o3hpmyVbAoNd34AsBONLn+oeiHU= Archived-At: Subject: Re: [Jsonpath] Fwd: Expression language -- index expressions and filter expressions 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, 09 Mar 2021 18:17:49 -0000 This is a multi-part message in MIME format. --------------DE0C231D5DB9A994D3357821 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit ... strict case should also result in better runtime performance ... > ... human JSONPath text writers usually know, what they want to address by '$..[3]' or '$..['name']' ... > but during selection process, it will be applied to both types of containers in the loose case. I vote rather > for the strict case with not converting to '$..['3']' and '$..[int('name')]'. --------------DE0C231D5DB9A994D3357821 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit 
... strict case should also result in better runtime performance ...

... human JSONPath text writers usually know, what they want to address by '$..[3]' or '$..['name']' ... 
but during selection process, it will be applied to both types of containers in the loose case. I vote rather 
for the strict case with not converting to '$..['3']' and '$..[int('name')]'.

--------------DE0C231D5DB9A994D3357821-- From nobody Tue Mar 9 10:35:23 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 408FD3A1622 for ; Tue, 9 Mar 2021 10:35:22 -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 iTAE0U2dYAFL for ; Tue, 9 Mar 2021 10:35:19 -0800 (PST) Received: from sonic306-2.consmr.mail.bf2.yahoo.com (sonic306-2.consmr.mail.bf2.yahoo.com [74.6.132.41]) (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 41E313A161F for ; Tue, 9 Mar 2021 10:35:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615314917; bh=hHdnC2cxXEfwXO0UHEfwaACoRFh5d2eRnLmpw1VqcHo=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=VC4JRq7WFNeFKNFoPrERznL2b8bhmFNvyvjw5zq3fHfFKoxc8RGHmNaLTC17O6JHw85UrJPvi73Y0PKBO7iUr5KyyiWhpKWuzf8UO2L21bYk91FPydMjuEZh57REcfhRq+68yPw+3k82bfWjoPXGetM0wTaao14KYE3ZLgZxaa3v4hwgmcJXSlqSZ9z3TZL+Z9h33iCPtEKTjd0iiwz6H0MySzmAOvK/eHED3tpvNfb+/GjtPnAEngR0s/qnaptGotPKaOQKK40pmwnSyxbnKdjgIbHxl48mYYkDkxeN1I1jPC5mz4G3F0vjv+a9a60zDzHzNmuLv2GkaPnCu1ixVw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615314917; bh=/TbmmavOeDLVWyfmnDPDpLOIs/Xbz8XQSjwBH5U0CgK=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=iok93Jw7a0fL6qVpNj1LYKAmi9EFqFxg6E3dVqSywuc9Eh2g0CFkj7g3aqdTtOZciEkS9t93iAIe2kdyb17fjpLLD9/7zJyLgIIbmnENIBePaPQAHu0sOmtmJ42EnMhKQZkrY3XJDYklfVjTO4EbWsSDYQJy4AjGzQ2R94TstStNhMFMkgbJxfxDVIQPvNliFJfSmnwFWyoBuNKA70fX5Vozh4SWQoLZIboK9DN8vTCMiwt9DuGnzz6zKMwjzq8Nmk1XnRFtYntXQwbybCZYYqs8R0ciY1uZv/g3s5s2PBc/cdJrQMXve/+0Bi4IwywU9jRoVKTfvqiyCcpx3XPOUw== X-YMail-OSG: 20E2pMQVM1mvjevo87pCfqq_u3Uf0qfQwMTtNC.K0CZcuEBdeuPoVuR8uL5TcUm ng5DfU2CjPDFCZqPBMGs30fWjdqLxYldifAO4RDkolcGG2An2y4aPcCyP62LVl52r3vuHFyiboia CzNWGkruRNYEbKec.AgEs2w88i8f4QeaK6aghu4D8nQghfxc0RqD_xZN7ZTv79ZNZAUx6vB8_QMT HpacLYS68cHP_BBTuKxQZpEYGFQuWYXe7GlvsvLuOh7a8IdempfN5BUlEjaAnGveZVlOrVE1YzDQ w5SwievBRSd_tHmcPjvwLEZG5rRiRJxyYrdwemlzMmsFOhwdjTUlA3P58zCdGuhyJG4.4R.HjfwI asOjBehPjigxrYQUWUIpzgH1HroNuT0HxAJBZ4VNKIDaBX_kTTzKjQyOEYFQ1r7W7sM8ooi35g09 Ud4u6TgOsJgm.WwmWRaxVVrENWzktMlhwDVX.LyZAw0AzHACku_obWDsQbq2g455q8ByzbHthUol hwl65H4y0WqX1rfVoQ9d0pJF5.UA1Ip3qfhesaDy.1K2aCUAqnSemmhU33GnB.DXLZ6Di903C4_m i9CV9q5ZmDm89KWt5O37_bsqBr7dIRWvDYJq5EiOr6d47w0zy4_RCHDLk7mBsuVGA0qWnOqFRkf7 UYbYO25n1LiNASKwCSRDffzA6uqEJHcu29TE.bKJSs3mcDCBhx6YfK_BEwLKSf5Gk1QI3kNucXCi GNAhOmjUagLvPNjrzr7dt3KZIfgaYPeCTlfQld_UIBvJD.hcVNYlOkms7Odlu0QreuRhcj3qaaDG es7tfJ9H_MTQXJLoQVeLrKbMQyVfMa2tALMLjiPksw2G.opJPQlgKwHs3omTOgQD9ZlS15Ixt8qg Rphz8XsuH.hOs3gRX0pEaA_jd8gDEbJ45fcu3sDLPaUe9cL4lSRUx40cfsfvSrVOJPD83mkH04PF QiEjC8pkkS0ktkVMC2Hl67xeZA946GMuurRW7vV1qTAO9vPgXJuKDgnVbwClaStYKvtJonZ46Zmk zU0jwitl_Z2SteicK2Hbu7NKtWrefTUm_Um8QClm9jOKkjCgy_sREYFilc8T6UQJTOR7HSU8pib6 YQ_LTZD_MWEKnrEqMhzppClUTpcV2xB9vKrZRFC2eVRyfPv8DKV7murpvrilfOQlOvsynrDIUF.X uMNoReAkW8RY7qqKk1RLEq0p104AzpvN_zCMbMf8t.A9DqN24LkwFpeIZXeakUiAHfDec4CDZNAV HD2nC07lezWjghx4uKWewMqcwZMUUctfakaBZqz63YLjkFsOGMIzfTuR9WErv93Ga8X09_B3p_cz FHlE2edWwUfFCFF2CWn9hJDeVIPF.zhxLWwQYJOqCNnjFITQtuMKh4t19OY7AVhWESngQcGLAoj8 J3Anl8MYvLW6RNOHByXVaX9cRPGefjW6x3N94_dQS0cJHirBYmj.lgzfTZ.gHQyxhmoYZFUVCWQ. LESUwT7J0wUfIUz2LziarRgC0ukLpAIJRScoGbWfzn9WxQajbL6.bJa8Uz3grXER2PY46N.E28CC ZtALxkEddOZ1mIuEak510_g5FiopUwgxJgSngKAPSqtiPxkTuHJOq07zuHh4SxPr5CNEnaJUsMmt KViPHtlInrmAmlEajcUe0C_QlZCxlUR9mNNff2tMnqPkXjj1VlBVBYM.MgGR12YXostLW5q_DSOX yDeCx0nAh1diJh2Ib7Wus_wJc04xKn_FEDo1LJJf52ZeJruIaessNJLGWRJ6zYVJ7rhaBUOWno0I 3Btc_.sUkLLmQZczru.bMQk6hyaCDgcGZTtncYB0uLsV8_E3.1s0qTCYD_8f4.3.JzfXsosEHi6l rZlGelLvB5ofnzhsc6W9RuHHxY8Y1_TWPHfEqB1i5RxgY5Eilz.ClXtO2nOWxyZEEMQwNP2TDLdg LN3dlo4Z5iArIqwqiC1cLSEiSgBConqhIg89CksyhOvz5bJr9zVpno_CKxMoCwyj294ETuuFuipT pIWb6YzrtaDlMjiK5dqISS6vQB1rgCsy8ffnZl3iVSdHHdYG1RHzkWv12Y.QfO7ZrCCYtqy6VKQ1 mzkPs9r7h0RxwLaWoa12.0ovV_8qL.t18Idp3Pv.XcagXMXMxe4EFsB0eOa1vn0rremwqmYRHBjq XS7Va9LOUSxz.vdk.ScA1MmRWRgTyfR7bx0W4Rku45C2LGbl797BRcvFWxzgiaEZdTAPz_yyDGa4 QNZYpBCAzFQHLiooch.CoyQDW_NoK396groaArXMD3N1Azsqo_SRVjKUbxF9ZMN2k._8rpr2Igla kpsCnDyiRAuNNM.QjFqC6Ss.ZbMXqv6gxpNe9jkx31Bi6i2KvtqaeRmrFIXh347PyZ3zqGpycTJT Jl8DB_6At3lRu99O5x9OoPH9yOQzfyroEwX7jfFeTKJLdNB38_EPEkuQRRpIRaSzu7RulTqZTVaR JaAAxib6AyNQrb0w7m6V_YfDYVT.0jM4iQw1Xgs_hcWxpiIFlTaXHKpnGiAt.9dxyjKpGbjUt51a Ywq7jJ1.NBd.5IsOwjYG6pe5X6GadgGxswhSrbD1T7zB6Fk9pVQ8BZf0oYIxC0SOdcAYsHnsujaE SQohlnQvnWgIQ.PUtcp07p9yi7r6Iam5hCgsMw.vFJmGwg5JsF3HMi_PjpLVgVAVEFyaT5lune.7 aSsv8hqFWRL_6gs1VWwqF77LL38v5tyzsJOoxJv7joLsjq8aE X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.bf2.yahoo.com with HTTP; Tue, 9 Mar 2021 18:35:17 +0000 Date: Tue, 9 Mar 2021 18:35:08 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: danielaparker@gmail.com, Daniel P , jsonpath@ietf.org Message-ID: <1442099741.747532.1615314908361@mail.yahoo.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_747531_631700765.1615314908360" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 18:35:22 -0000 ------=_Part_747531_631700765.1615314908360 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Another issue is whether expression evaluation should be a separate compo= nent, or integrated into the JSONPath grammar proper. - Daniel I'm not sure I understand your meaning being this distinction. Greg=20 =20 On Wed, 10 Mar 2021 at 3:20 am, Daniel P wrote: = > From: Carsten Bormann > I think what we have so far is: > > =E2=80=94 there needs to be an expression language that is independent fr= om specific > implementations and their implementation languages. > =E2=80=94 the expression language is used both in index expressions [()] = and filter > expressions [?()]. > > Obviously, in index expressions we need the expression to return an index= value > (integer, string), while in filter expressions we need a Boolean value. > Also, in index expressions, the implicit parameter @ is the item to be in= dexed (the > item to which the [()] is applied), while in filter expressions, @ is the= item to be filtered > (one of the items in the container to which the [?()] is applied). > > We have a dial we can turn how conversion-happy the expression language s= hould > be. > E.g., the conversion from the filter expression result to a Boolean can u= se a big set of > =E2=80=9Cfalsy=E2=80=9D values (false, 0, =E2=80=9C=E2=80= =9D, [], {}) or be more restrictive in what it accepts. > Similarly, the conversion from the index expression result to the array i= ndex or map > key (JSON object member name) could be loose (e.g., converting numbers in= to > strings) or more strict. > > Generally, both kinds of expressions won=E2=80=99t know statically to whi= ch kind of container > (array, JSON object) they are applied. > It should be possible to write expressions that can operate with both kin= ds. > Surprising and error prone conversions should be avoided, though. > It seems to me there are a number of distinct issues when talking about expressions. (1) The unary and binary operators to support, and their precedence and associativity. My own suggested list would be https://github.com/danielaparker/jsoncons/blob/master/doc/ref/jsonpath/json= path.md#filter-predicates (2) What kinds of operands to support. My suggestions would be (a) JSONPath expressions, relative to either the root $ or the current node @, (b) single quoted strings, and (c) JSON literals. (3) The meaning of an expression with a binary operator and two operands. In particular, the meaning of an expression when one operand is a JSONPath expression, returning say [0], and the other is a JSON literal, say 0 or [0]. (4) As Carsten mentioned, the rules for determining the effective boolean value of a JSON value. (5) Functions. Functions are unquestionably useful in filter expressions. Implementations that use Javascript or another scripting language for expression evaluation of course have them. There is also prior experience that can be drawn on from implementations with their own expression evaluation that support functions. Another issue is whether expression evaluation should be a separate component, or integrated into the JSONPath grammar proper. My view is the latter. A number of implementations take that approach. Daniel --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_747531_631700765.1615314908360 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> Another issue is whether expression evaluation should be a separate= component, or integrated into the JSONPath grammar proper. - Daniel
<= div dir=3D"ltr" style=3D"overflow-wrap: break-word; font-family: sans-serif= ;" id=3D"yMail_cursorElementTracker_1615314854987">
I'm not sure I understand your meanin= g being this distinction.

Greg<= /div>
On Wed, 10 Mar 202= 1 at 3:20 am, Daniel P
<danielaparker@gmail.com> wrote:
> From: Carsten Bormann <cabo@tzi.org><= br clear=3D"none">

> I think what we have so far is:
>
> =E2=80=94 th= ere needs to be an expression language that is independent from specific
> implementations and their imple= mentation languages.
> =E2=80= =94 the expression language is used both in index expressions [()] and filt= er
> expressions [?()].
>
> Obviously, in index expressions we need the expression to return = an index value
> (integer, stri= ng), while in filter expressions we need a Boolean value.
> Also, in index expressions, the implicit param= eter @ is the item to be indexed (the
> item to which the [()] is applied), while in filter expressions, @= is the item to be filtered
> (= one of the items in the container to which the [?()] is applied).
>
> We have a dial we can turn how conversion-happy the expression lan= guage should
> be.
> E.g., the conversion from the filter expr= ession result to a Boolean can use a big set of > =E2=80=9Cfalsy=E2=80= =9D values (false, 0, =E2=80=9C=E2=80=9D, [], {}) or be more restrictive in= what it accepts.
> Similarly, = the conversion from the index expression result to the array index or map
> key (JSON object member name) = could be loose (e.g., converting numbers into
> strings) or more strict.
>
> Generally, both= kinds of expressions won=E2=80=99t know statically to which kind of contai= ner
> (array, JSON object) they= are applied.
> It should be po= ssible to write expressions that can operate with both kinds.
> Surprising and error prone conversions sho= uld be avoided, though.
>
It seems to me there are a number of di= stinct issues when talking
about e= xpressions.

(1) The unary and binary operators to support, and thei= r precedence
and associativity. My= own suggested list would be


(2) What kinds of operands to support. My = suggestions would be (a)
JSONPath = expressions, relative to either the root $ or the current
node @, (b) single quoted strings, and (c) JSON lit= erals.

(3) The meaning of an expression with a binary operator and = two
operands. In particular, the m= eaning of an expression when one operand
is a JSONPath expression,
returning say [0], and the other is a JSON literal, say 0 or [0].

= (4) As Carsten mentioned, the rules for determining the effective
boolean value of a JSON value.

(5)= Functions. Functions are unquestionably useful in filter
expressions. Implementations that use Javascript or= another scripting
language for ex= pression evaluation of course have them. There is also
prior experience that can be
<= div dir=3D"ltr">drawn on from implementations with their own expression eva= luation that
support functions.

Another issue is whether expression evaluation should be a separate
component, or integrated into the J= SONPath grammar proper. My view is
the latter. A number of implementations take that approach.

Daniel=

--
Jsonpath mailing list=
------=_Part_747531_631700765.1615314908360-- From nobody Tue Mar 9 10:46:10 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 26F883A16D5 for ; Tue, 9 Mar 2021 10:46:04 -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 BXOINFVujWJB for ; Tue, 9 Mar 2021 10:46:02 -0800 (PST) Received: from sonic313-14.consmr.mail.bf2.yahoo.com (sonic313-14.consmr.mail.bf2.yahoo.com [74.6.133.124]) (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 BA0283A16E5 for ; Tue, 9 Mar 2021 10:46:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615315561; bh=dV/lfZIC6BHTaROgE6f5tzmfyJ4JnmvvNbpUMAQEzC4=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=qI1oqhDctr29mhvFAq7slHYbN53DwAAJBxcQkjD1We/+2olIcQ6YvVbztPoxszVv94yZWzSY1ZxzRC6BOIOnhhBwCcvcE19N0Vk1T43UWImaCX8CyEm8jAThZTndT4E6wo+Et7aecHasOsxJyyvgA5RHpLjLP3nKCoWO3FptrqWWHJubcTpH5XUBfYH0wwtlm9LuDtGquRbj1/hYTzLOsO6WXU3lrJwKXJjpdMnKS9gDSGVNMF8pxv6k5RfP/IHpn/eHail1WzcY5btez1sjV4byt/YTKFBMpMNqlF6aiBTpEkRsc5XgHHCq/ThBMavrhRYxEscnhkc8M6c6JVxpEw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615315561; bh=YUJkF+EHndOJaV08XEBxSrgegvUSBfxI58gtXSDs5Bu=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=Pefgva0TE8/FVCK27T2L9tkoVUbMV93sHkQyBWVay0cD5YIT8E60Nt4sfA9lSr/cTo/O6EFczfLfZwo5K76XZgYZydyzG6a2898iC6x3G8CnP5JF2IyrKSg46IfxTHlcl8hWhfrh4ipfdPKgkcWSQfUlAoyoj4AS6aScaRsa2OkdgkVjOQAgAHd9wORsrhZuFHmdyIAB5AokJjb7EpPaICOOSkFRkXe9M6jmQYSKrrtagwenQRwHnKq6ZqOXWgHoku3qdffi0P/nBR/aH7viGzItOH1bzl6hO8CvtCdRxrklH9wTmXog9DioVQ23IM9Os01rT1dJodlRubBduaU1Iw== X-YMail-OSG: tGZ2BNsVM1mnCDvp3_GGjGRcQsKJL1HtJSjZogFp1UMVluo9cCbaYxSnwDp5C.R kdOnltFAD6yPENt9w3L0OB7mzr.zsuiRZsj2ceLWjvVoCF5lir4eSKM985Zlcnpa_lBmh.Ebv.70 n5zYs4opgQqqo6paCKdKK2OonscTU77DfBof9VsjI0woGssxSI_qzhyuXixeB4KTAXCg51Nk6Gc5 sZG5HdjKpGPzzNBhoF8QFsCUl5bUXm0zK5G.2Sjbyjf8BwH2iyEOoShy7Yy6K9M8giyvx2Zb1r1v _r9KF1TKf.RwCcEj3VmlrNamVY6JtxeNcZNqAUWPUBKz4VGW0bsGQSm7XOZG16zLDEtAsj.nNvjy BgdJCFVAioaku_aOGZtWdEqznnwT_k8C79eWTsREhDOegFZfFgAgpt_jvQhGvL0rdSsdyOJvMD8H VYawCUVPpavCPkSo2nv_xizlKyqgo2mKAk2xwUzq5LdquB0GbQz5baVd7t94SeWfzLLAVyDhawQV PGR8V7AWEs3FEpa3GT5BvCog6dCe4LiYl6f_XOM8ZXrYbO5qtfhsLZthQaZPTQzM4yo71eE71Y6a YsKK.nPWGX2msww.KRAgnUe2jESAZt_H3RQ9MGgdRA3XYakYVovz31aykaIiHKVA80BEM3pMyC_D OVXE4ctIVrJ0B4fWPtnqUUPJtgj0mlP5ICD.PV63I.mEX4rmAkhCO88IJluOGBVKYB_O_mDhOE6x TogTNS6hBS2g6HlAMpovJKi9bnnT0ogZvkECYlCQglq6PxGPXYCp511Vpf5OcyiCymrQb__fM4G9 whE6IKdlZgQCz15anADCN2Cq9BBEdU2Vu0CiDaWNZ11jVqJKBt6p5l8K19can0KYkx3ZE7rPEGs5 lSqNUIqqAP.r9kVGwQ3vq2pkgMC2YNJyB8wY6QupCUd9GVmvs3_xGYC8HMI6ZjmJFZUo5LXqNSDL fZ2Z71psqS3.DZwbEiEJbxAgcQ4vKXZKKIC0xjs6Ya66lopq6fL9W62ZUQjT4vkhiIpI3WH9OeIw 8K_OC32jOEn9rxgu5djbhf8kqdFQOyJiUnzKNv9gQAgqpq9BVZfhyxKpceyYIw.G4RroACwoFFJM H6dhbgOhPlAJ6NvsI6ySRcXloRwn8ewiGT0E_SDED30nczYQ4mwgZ.TTyPbIZYhRBGadl59E_qPW PSKAuzz2Yd9SkmEUZXv7hs2azcAymHKEWdhJHzDb2EKKtR7NkJE.y.Nr8jSfyulOBqvmDLG3H0RM ng0o8bMLUVuikFvdfj.vBPCBBN0THQ5rPQIBcVJ8XeNaOcm3rMPWL3tFx3GgNk4Tm33CrcESvAY3 uXeS584vbzuro.DycPvvTW.JlHh9dgCpJAbxL8hgqKTDCMMVaCNFLXcMP0soed7xorluwFGN0TUg VXQSUVhbJUP906CUCF6.fZurtfMTGT0t0I.7CuhHM_iHUkO2EePDDlsjGewcPypxfF.AUDnmay6. arExLpHR_5i8cYvKw_dYxdI6mzB1lmU9ZebjwRMpxuWBh_2_cv39arG387C61IUh_q1eyWfFG_P8 fcBcR8PhyMjyeyxgr6Kj1PDvepAS3v565YUCKpChs9qRORX7sxXbp5oXObB1.RojG48f4wMxuhPz WHyQKGdkl5yJxUWAgEsLgeag85XSlmbdbDxP7xMzu4.tVKGc1qPzMXbSkuUXVmdsKoHg7gOv2zbG GvQ2xPbqvifNhdy_WI4FGrt6fK8gwQ5hhq84lQpu2T6wjNJmkrXjOnlFUR22PhhAkBSyDPwczThV 4qz08_1G1wJzz4gI6Pcacnto2awFc91iS48tIcNklYOBAgF8u8iH3NANOkS9pKsQHdzDo3ucWk1j a18a.I1o1bkQW9FBTJ2CoMT3JjIbVwiRWsE3L9A6BMU23DNwzOsQIrlaKG.xvZ4ug6b6a9KNpq2. 4yGoUOJ50Z3TCgJOzmFA7BzFP66jSlMCkmsWVJixZMC4lIRl.yWlhjd7fQ_r3wmrCCM6je2YFVhR qnaWcoxRVBMWBRdhXp4b3kpxImItHC1oiU5YHXv6co5yTLbJDxiupifyCt4TmjWdZUH_Pzd_0vZp 3hMSD0Fl0aCo9_FQIeyUHVO303juGDfJE7ScyeuRAFTgWTHk76hxX.zBs1p6GcHWGKsmM60aSDPN 51HT981jdeSEK6mK5wM.95IhPXgcxA1gfw0pMvCh8GgCov75cJfxpAUW1dbOEXhS0OkdMDjlNdoR _WH1mMkTmAHtktyWP9Yvx0BKD8ZgnI7Nxwop0mz.OeutbRvFVVjiZnKfcydRU1t087t4pdrxRNFg gxrU.7qV7Sfl8TKWqpU0w4_sgOtQTsGRK11yLyZNUZb3RJ1ZG7CP42a9l.H.z2PMDWh7f5CwVUjT fdygEgbVFBXCdU7w3PmvBFMCBPT7wor5drnjf.k9_Icz6osEHUhVZJnTbz93Wm25NkXdZXF__dCB 1DdeRFU2q.eePiAhC_M.cu0hg_IJHONysDB.It5lVXgFdZE.TiqmIsz8newK9kT_Ckfc.YfxOXt9 O3zttmHGpx6JLMFFt1MRQcXrlCPvpxohpnkda3em8naIaOpCvpVSjJZx3lsV2uzILSu.E4e26ZFW QDlQb4O5mC_a_p4N8IKiNL8bs0mu2_wP1HHLavuF0e1asSsRglDnR_wCJ3Q.I7incE4IYftRi1nH uEuQCN9P0ivEcd67is1ETh_C.9ExSLw2VVBhuLh8mvrOECeWG07PSedzKr5cM3EvLRx9GsZAfuZI xK0ht.2iDAbwrSNubOHtAZ_Zs3y3W8eWFIWqBF02oC2NGxQ4HoezRrW5klyty92TZjn9PYp02LMz 3DYAoTW75jJqwItuq4bSqGzSDsw-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.bf2.yahoo.com with HTTP; Tue, 9 Mar 2021 18:46:01 +0000 Date: Tue, 9 Mar 2021 18:45:53 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: Greg Dennis , Greg Dennis , danielaparker@gmail.com, Daniel P , jsonpath@ietf.org Message-ID: <2036310382.743886.1615315553293@mail.yahoo.com> In-Reply-To: <1442099741.747532.1615314908361@mail.yahoo.com> References: <1442099741.747532.1615314908361@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_743885_50256027.1615315553292" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 18:46:09 -0000 ------=_Part_743885_50256027.1615315553292 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Stupid autocorrect.=C2=A0 This wouldn't be an problem on GitHub, where I ca= n edit the comment to fix typos. I'm not sure I understand your meaning behind* this distinction. =20 =20 On Wed, 10 Mar 2021 at 7:35 am, Greg Dennis wrote: --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_743885_50256027.1615315553292 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Stupid autocorrect.  This wouldn't be an problem on GitHub, where I can edit the comment to fix typos.

I'm not sure I understand your meaning behind* this distinction.

On Wed, 10 Mar 2021 at 7:35 am, Greg Dennis
<gregsdennis=40yahoo.com@dmarc.ietf.org> wrote:
------=_Part_743885_50256027.1615315553292-- From nobody Tue Mar 9 11:35: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 54C3A3A1882 for ; Tue, 9 Mar 2021 11:35:43 -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, 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=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 tWoGnEmmmqeH for ; Tue, 9 Mar 2021 11:35:42 -0800 (PST) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 C25673A187E for ; Tue, 9 Mar 2021 11:35:41 -0800 (PST) Received: by mail-wr1-x432.google.com with SMTP id h98so17960455wrh.11 for ; Tue, 09 Mar 2021 11:35:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SZU0mgNsUMHGBAsjmEblAkiwWzYIiMamHL+TR01SDD8=; b=dJmK+N3Qegjvb3d9XAPAeCTLGvuEMu9thoB8udUSqXLy6PRxmUk153VfEnViaSpPJA pDoZtY2PhUoqJF/MikE4Tf29GkfTRqkhxLO4diAVUDop306B7VLgeQgDjLw4Me730QxZ stnRqbrz7TfcEcPsLnGC+/eP2+2/9gsajni8IfwAEVWh5L6VbzvuKjAThHVKLpgsEivS Z6+aErWiD4w1qgXQzBPGYrwdDz2E2CHUypkcnwct+lD1jiwyqSLbCIiO0nuB0ywFpaZF 2CVRWMzqIImq477M5XiitSahdZbRu5vFnGlWr3NZaYYatknkiGl8E94zYkuPmbcC45G+ o/AA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SZU0mgNsUMHGBAsjmEblAkiwWzYIiMamHL+TR01SDD8=; b=InnXGGxkNlV9S4UsQg4Xy1dvxBbtCMHPDRVXhdaDAhJaJbWJn7UeaxaVfGvGpOO4sE bsN2er/RTZTyX4V+tQYvEaXicSNi1Zz6poOE/6zEDOtGjNGC4pXBrmm8ixCBHO0WkTSO ZzcpmLQXppDr1QHI3A513CCiSWuwGvWbGxc4vWwetU3NLQmFHunxc+JHyejdL6YSYIH2 C+fR+EfqaG/tINbj1XmpF+Zv7dpJBARoQbgJbS06OnWdiRQ1sunYSu/N93xLPgF4CyDa UBVcIEDNBEzgGiQninvB24qFGNXa0zecgL1GnEpWZu0WVI88fU/7QoQGvVu6IX1dMS4R v+HQ== X-Gm-Message-State: AOAM530b5NtJDRGCGd0oeNPg3c5IrRkPsbX/nUOmTE8KFZpeJLfmGCsg mvwbTD/lUo3L11s/nI5UJ/HecpX+VwYfiqrUqGM= X-Google-Smtp-Source: ABdhPJzRbyE/GP1EQfEZLR1DbRbZwabZmalkV0DMSVg56EWnjseG2gPdG6A3gaJKDPSVcMazLZWym/UHncZeqTtvuhk= X-Received: by 2002:a05:6000:18a:: with SMTP id p10mr30366181wrx.166.1615318538664; Tue, 09 Mar 2021 11:35:38 -0800 (PST) MIME-Version: 1.0 References: <1442099741.747532.1615314908361@mail.yahoo.com> In-Reply-To: <1442099741.747532.1615314908361@mail.yahoo.com> From: Daniel P Date: Tue, 9 Mar 2021 14:35:27 -0500 Message-ID: To: Greg Dennis Cc: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 19:35:43 -0000 On Tue, Mar 9, 2021 at 1:35 PM Greg Dennis wrote: > > > Another issue is whether expression evaluation should be a separate component, or integrated into the JSONPath grammar proper. - Daniel > > I'm not sure I understand your meaning being this distinction. > > Greg > For an example of filter expression integrated into the JSONPath grammar proper, see https://github.com/kevinbirch/kanabo/blob/master/jsonpath.ebnf I haven't studied the ebnf, it dates to 2013, but it presents a simple JSONPath grammar that integrates path expressions and filter expressions. It's notable because, as far as I can tell, few implementations, including my modest contribution, publish an ebnf (working on that.) The alternative is to have a separately specified ExpressionEvaluator. In this case, the containing parentheses in "[?()]" serve as top level delimiters for the expression, and the root, current node, and expression are handed off to the ExpressionEvaluator for evaluation. Note that if the filter expression is integrated into the JSONPath grammar proper, such that the JSONPath parser understands the expression syntax, then the containing parentheses are no longer necessary, we could have "[?]". Daniel From nobody Tue Mar 9 12:20: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 B57473A0A87 for ; Tue, 9 Mar 2021 12:19:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.92 X-Spam-Level: X-Spam-Status: No, score=-1.92 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] 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 fgMT2rqbMsun for ; Tue, 9 Mar 2021 12:19:58 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB5963A0AD5 for ; Tue, 9 Mar 2021 12:19:57 -0800 (PST) Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Dw6583B1czyQH; Tue, 9 Mar 2021 21:19:56 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Tue, 9 Mar 2021 21:19:56 +0100 Cc: Greg Dennis , jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 637013995.879876-8321d07088842798dc1e5df7385aacd7 Content-Transfer-Encoding: quoted-printable Message-Id: <25377B59-C541-4123-9BC8-3278F931BDFD@tzi.org> References: <1442099741.747532.1615314908361@mail.yahoo.com> To: Daniel P X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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, 09 Mar 2021 20:20:06 -0000 On 2021-03-09, at 20:35, Daniel P wrote: >=20 > The alternative is to have a separately specified ExpressionEvaluator. As Greg pointed out, same difference. (Yes, the *interface* can [and should!] be made well-defined, but = whether there is a section break before the ExpressionEvaluator grammar = rules begin does not make a difference.) Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Mar 9 15:33:04 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 B3FD03A116A for ; Tue, 9 Mar 2021 15:33:03 -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 dIJxIi-o2ovZ for ; Tue, 9 Mar 2021 15:33:02 -0800 (PST) Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 BB4F53A1168 for ; Tue, 9 Mar 2021 15:33:01 -0800 (PST) Received: by mail-wm1-x336.google.com with SMTP id m20-20020a7bcb940000b029010cab7e5a9fso8654493wmi.3 for ; Tue, 09 Mar 2021 15:33:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=+CjriQIqHuqh/tpi1E8GRFJH1t0xZttl2j3/O+62a/8=; b=j3VmZMtmdVUOxbJmVt5Gv+YM174+0QR2pn38JG3wTTqG/W/qlZYru+q8icufGhZK/5 S6kTyZmERbhWrbnR5jWJh3Ib5Y3H8wVhANkaBKBR736y2wdIlYmKhkvgWUNhIxQQlndg YljZzpG297trE6SbTkf1YsMOhsVxiizUG/9mfUskm1dEPBQaxugMsFeWFIpIzB7Nasri Mp/GjxoUgIdN+3eGCQDuMu2+xeke6GbkV89BQD393KBIRVumlw/acP+KY0dVUTGIXOVz Jv891Sl9ZwkEl413KB4A0TaGLPkGnwwVyInMcRoZ9DpI05s09EvLHJ7p8uhqGOkLax55 eK9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+CjriQIqHuqh/tpi1E8GRFJH1t0xZttl2j3/O+62a/8=; b=SjwbsaRwwpP2k6I13hPW+oMqAwxHb1SZyuLwVYSpAbem40zGhQmuuojs5F6QwoXjYl VFlZK7IWN6buSWwOee/dUCl+FER1V1P0PaK+pOLjHn1yHjfc6CApPek4MF4Pn+M5PLpE HhFa9qj+Rrm37VMrZp8Fp3KWL5BIM0Sg1JJvjB3cUEDxHkBOBpik+YL2CDWFMKM4xKIL ZnW4peeqD9KdiyscnBfu8CvxHYuP4U+F/Vir0j/VnvH+/22jqX9h06xrh9ewRvj7u+lw 27sp3JPRePB6bNT+L1kgMmBXtosc3vkZJpABOC08Xu3QwWgJdQ8AJR1wpK7g1i/68Zxk iWkg== X-Gm-Message-State: AOAM531GAlybqtIA+fEIv0ThfQ68mpknfHnrMBCGwtbrsKziZY7ZxWgX tifUMMdRPfrm7/lTAhMbxPtRV9W9FMf6lJAp8UGNSUSwmRU= X-Google-Smtp-Source: ABdhPJzf1JQek3HuMLnvNFjaS1ZyMY/LpWknU0PMfV+VJEF1BIjx5A4RGdAd112iyzHtx+VKCRVSpXmFNMytgucyA/8= X-Received: by 2002:a1c:3c02:: with SMTP id j2mr312159wma.92.1615332775091; Tue, 09 Mar 2021 15:32:55 -0800 (PST) MIME-Version: 1.0 References: <1442099741.747532.1615314908361@mail.yahoo.com> <25377B59-C541-4123-9BC8-3278F931BDFD@tzi.org> In-Reply-To: From: Daniel P Date: Tue, 9 Mar 2021 18:32:44 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] Re Expression language -- index expressions and filter expressions 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, 09 Mar 2021 23:33:04 -0000 On Tue, Mar 9, 2021 at 3:19 PM Carsten Bormann wrote: > > On 2021-03-09, at 20:35, Daniel P wrote: > > > > The alternative is to have a separately specified ExpressionEvaluator. > > As Greg pointed out, same difference. > > (Yes, the *interface* can [and should!] be made well-defined, but whether there is a > section break before the ExpressionEvaluator grammar rules begin does not make a > difference.) > They can be functionally the same, but there are of course differences between a single JSONPathEvaluator, and separate JSONPathEvaluator and ExpressionEvaluator. >From a spec point of view, the ExpressionEvaluator requires some duplication in its grammar, for example, it requires unquoted-string and single-quoted-string. Paths occur in expressions, presumably the ExpressionEvaluator will not fully understand path syntax, but will need to know enough to extract them to be evaluated with the JSONPathEvaluator. >From a non-functional perspective, it is noted that implementers will likely follow the grammar, so if the grammar specifies separate components, implementers will probably implement it that way. This requires a JSONPathEvaluator and ExpressionEvaluator that invoke each other, with more memory requirements, and the likelihood of deeper stack recursion and less performance. Also syntax error checking is more robust if the parser fully understands the tokens it is parsing, instead of simply knowing enough to extract a string to hand off to another component. That's not to say the error wouldn't be detected, it would, but the diagnostic could be less helpful. I don't want to make the case too large, but I do think there is a case to be made for having the filter expression integrated into the JSONPath grammar proper. Daniel From nobody Tue Mar 9 16:02:47 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 2C4793A1365 for ; Tue, 9 Mar 2021 16:02:45 -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 smx2SsNVMzty for ; Tue, 9 Mar 2021 16:02:43 -0800 (PST) Received: from sonic312-22.consmr.mail.bf2.yahoo.com (sonic312-22.consmr.mail.bf2.yahoo.com [74.6.128.84]) (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 7314B3A1366 for ; Tue, 9 Mar 2021 16:02:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615334562; bh=EvPHsM2heNJOfM5dsDYZO+iU2hX134vbNNfegbmQgLQ=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=KhwFnCfyKoxo8Eg8NbH95kR6XdQaXEydpLHKugSG+q9x5x4+oaY8hvH1a/g4Avw2Z3vPpbj9Se7GRFzRkf0ftScnblaKHX8LmCEzx/rxre6jK+3he1/4BwOvKiqeDkqHl+TTNBrHfeuoHd7VhUVLSvkelHAtfT8N+rRRlce99wqMh7F4fMn1DsFX96k1ryx8IbWjja0WhDM25hoQrrxrwvR2b9qSfY9EzC4wnhuKKq8CLnYRDnFFkiYlKxOJ7oG0NBl+S2vwCU8SkIewUq+q/8b16lH+pZNkPKJauN6i6yvfMKg+W2uMD5zNU0ffET3w4ZzUE4X3dEbLex7mHiTCIw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615334562; bh=UN6eQ9fibRNhvnsO6Neq49B6Eww6zdHNre7AgXASHjU=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=TjuhNL53fWQppmelNM58m5KTuamtrk5GH5Uj5ajpupNqF+loTBjuE7yIWQUpqRKPkARreT9F2Nye6kJzoEWzgCoR0Z/yqEEkcvw5ir5jojj3hIQifuZRIzyitmZ5j4+x0bE7yE1swaUvXHeE3SjmlxujiILBBbeDhDncWT5kRforJ+kqPSBIJNE8mltaCvaQgq9zA97kd2LDdCAnOfpKqgqfloJ6YEhQGHsZEfAcesoIx8nf/y0IRNHV5ewXlLJcQEyDRpJSmOldprwrh/MsQ66L3068y9KP+fW2ZcXQo9HMIR5dhVem7tPFvM2S7LcojEUh8aRF0eV5dPdtEZe28w== X-YMail-OSG: UMVl.mgVM1lSBhXZnlrTF7qpxL7rKxUmZ4hp12HQ5if8lMMdNPUt0qGM6bd7TGs 3p50ApmEgHIRz3fLRezIvRr7VabzIgwAsO.cOZUaspc3AnlK9z98XG60YFIFkYPEO6V0WVz89AHj L14hHTaSZacXFlXkh_VBZqVJ63lYLy6Y2xBQ_IJ8MxA_erVlnIP9rqDhmzukSLJ2ve6fApIHJeBc pF8Bp2Z39iHOmLvSCBUZEcxL8x_HppcL15cEQJH1fwyABc4s3cs2bLkglalFMdthrOGpXtqIy1jg yLj9gufE6NgghRszWDBtJADfcTIiWNYefzMw1VmtPdTY3Jszfo8WQjA67j4C6aSDmx8oIVbvRMJ1 M6KUp0WCBhLsUMoKxpZAeuKeT4kkYgz55vECD5ii6Ik4pg.FCpcK_bpOz85dyAPAR4cGSoD_pNs9 0Vj8tp3.icsRIvYHsASHMIp0Bhnulknh5tKzVwG9Qyk1NsaRslfdKzGksN3XYjiAy9ntdI.M6Jk9 WjqVs1eX4.Tij4kuTLQ81LZVnlFyTqk34uvOKKyFt9ACe8LZ8TqeVw.Z2F6Eia4oUnd3ugrDrimg jT38jVz467RLyFPgb_A_CwiU5R1H5T4ergjoN5yt.wBs6_2OVQePdhHB2gVl74JLV90t00EZDhkm 4.phFEWHqygoKMgE7sfxRbROlkk8U1M7IwzdqHBjcqP0KleylP41g2U13enZmt3AjC90JKOOxKVy miQtvo6QsWrlxcaZ.MynVMC_eCD5JQuQhJK1pEN.Hn7UWngRC8GzyaK88EmMsDQIfSUVUFCYYFiH idFwEIQG13YHl0FHUtnmV3Wbn0jIDFRdP2XXQ0FGguD3MZW7TXXoOs7Xmn0d6ld0NddZgiw9UtgM D3nOezAmXT1gbBjPqgb1eJxDsc4mNZN1kJaO4IAtjVCNbjofWTOl67VqKVDWFbA2fpksYLZUgpXi TJjKSAl4Eb3ySwVBXp3XxGhnuBGjhYJLPep8gcd82TzQU_23663mbGjigWw0NWmtj6b_NofBbb4i YcrnEhor5k1KJjOZIq0X_6cA3uSCd3Z9hh9cFYnquDSfF0S1kWnsO8WiidRWnhmrdA6yo9t2lo54 or_gvTPsBIICuu_.8a2itoo8pb85l.bQXG5ueTzTuPeOSpc5LQFmHNH3Ogs1k9cuR8NkqRXl7ZGO RvqIDDg.b9B_i9rYtT6An5SFELjxfstQHanSVpUwkiJX_X9SmKDgmqsuqCaQjTIjiFp5QarbyNdV vEbubPYOA0BCiBSPzFBrxrk1toLC4XuPpI0ZUszP7MYa4ichhSokUpZxAY.wq7Sm7f93q0VqDVI_ CXZOCMAzk.BNwZRYZgNLElq0HSFwH4JDYWrt2Vl_u3JzXZHTd.0YwuX4ks72KMkw8MF0nTgec8vo Gt6.F_RZ4gErKQJmooYR2aEq58EiKv.ZQLj6aO.0pHHrUxKgH.61o1BGGLRvMz1Gi6h5qJfY_Ie2 HiZ5sTAI9UPxq6zIXWPMy4asYoXG1DMmarqBhlCxjqzYbaOi4fAr0urDBofs2ptJLdbzSGJaBKvO G2s7tdsEtgUWkyx5bp8tI6l0GZp6IxxBCcf6BXMV.0a_EES5p2ag4pTNla3YZM3eOEGZLAc13BVF KIHNRzxqijLn2xICNX4AmHxXw9i0naIXfilu_RlsvaY69GGOQRk7Gdf8TOJo0alzN7GD2j4lQ66W ..dV74iq8ot3l7DALzgfrRtgwI4Ncneg3UOXNauHAncGRxKyp5mE0.Km41NwMgr03Us6va9_yvx7 JMUKx9MGTKs4P0Ccyy.pAlQyvIu5dFNkTJNwNAF0uTKzy_nZ.Rf40GIyxvdBcrf5Z7bddwPHLNTr 67Jzjmf95o8OdD0fT6yEChzr5XdIvp8ZNLG35.ESFFQJ4R7LJcf8R7QM.y0NZSoY6XBzcy6jB9dv LfE62xEb9OsCkb5aJkM_KV4WjtqMaWue0nRoD9si0CtHdELqULBoBOTXNlWDoDPzlNVaAyjZpCZ7 gILaykWKduhx7uiG2V4rnstMB.K85HnA3laDq2.pz2rto8WUU3H8.npAYyBiXGSbvA2j7ThQFdPz 7UcxaUSB5j2.HJ.No11ELAFrYNj_VVDlTuqfzqigdklFTs1TWmRAdPyhT6BIedO4xg.RHvhmTzTD eIgdMOe1YW9kqlLHchZlzwb92V_3ujdtdOOxlr4gzMTQwz0f4txeZG_QYdi2u0TApj2fCP_GpkMT K7L5Hu_qEr3h8TI.UCitmIJsziudB.OvXC6m4mL8JcO7XJByJS2TFkVOEoz2iKt8d3H2HqXt5LNq KTX2nQxA7n7sIDiieC6dVTpa9z70AKKNXVWiEqkvIyQih3QGiV5Go7wbzCDMUBvMBO9S6FY9Bfwj xaV0- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Wed, 10 Mar 2021 00:02:42 +0000 Date: Wed, 10 Mar 2021 00:02:36 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: danielaparker@gmail.com, Daniel P , jsonpath@ietf.org Message-ID: <1995936718.840854.1615334556078@mail.yahoo.com> In-Reply-To: References: <1442099741.747532.1615314908361@mail.yahoo.com> <25377B59-C541-4123-9BC8-3278F931BDFD@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_840853_708928001.1615334556075" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Re Expression language -- index expressions and filter expressions 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 Mar 2021 00:02:45 -0000 ------=_Part_840853_708928001.1615334556075 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > They can be functionally the same, but there are of course differences be= tween a single JSONPathEvaluator, and separate JSONPathEvaluator and Expres= sionEvaluator. This is getting into the implementation space, which we shouldn't direct.= =C2=A0 Implementations need to be free to define their own architectures.= =C2=A0 Our role is to define requirements. Greg =20 =20 On Wed, 10 Mar 2021 at 12:33 pm, Daniel P wrote:= On Tue, Mar 9, 2021 at 3:19 PM Carsten Bormann wrote: > > On 2021-03-09, at 20:35, Daniel P wrote: > > > > The alternative is to have a separately specified ExpressionEvaluator. > > As Greg pointed out, same difference. > > (Yes, the *interface* can [and should!] be made well-defined, but whether= there is a > section break before the ExpressionEvaluator grammar rules begin does not= make a > difference.) > They can be functionally the same, but there are of course differences between a single JSONPathEvaluator, and separate JSONPathEvaluator and ExpressionEvaluator. >From a spec point of view, the ExpressionEvaluator requires some duplication in its grammar, for example, it requires unquoted-string and single-quoted-string. Paths occur in expressions, presumably the ExpressionEvaluator will not fully understand path syntax, but will need to know enough to extract them to be evaluated with the JSONPathEvaluator. >From a non-functional perspective, it is noted that implementers will likely follow the grammar, so if the grammar specifies separate components, implementers will probably implement it that way. This requires a JSONPathEvaluator and ExpressionEvaluator that invoke each other, with more memory requirements, and the likelihood of deeper stack recursion and less performance. Also syntax error checking is more robust if the parser fully understands the tokens it is parsing, instead of simply knowing enough to extract a string to hand off to another component. That's not to say the error wouldn't be detected, it would, but the diagnostic could be less helpful. I don't want to make the case too large, but I do think there is a case to be made for having the filter expression integrated into the JSONPath grammar proper. Daniel --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_840853_708928001.1615334556075 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > They can be functionally the same, but there are of course differences= between a single JSONPathEvaluator, and separate JSONPathEvaluator and Exp= ressionEvaluator.

<= /div>
This is getting i= nto the implementation space, which we shouldn't direct.  Implementati= ons need to be free to define their own architectures.  Our role is to= define requirements.

Greg

On Wed, 10 Mar 2021 at 12:33 pm, Daniel P
&l= t;danielaparker@gmail.com> wrote:
On Tue, Mar 9, 2021 at 3:19 PM Carsten Bormann <cabo@tzi.org> wrote= :
>
> On 2021-03-= 09, at 20:35, Daniel P <danielaparker@gmail.com> wrote= :
> >
> > T= he alternative is to have a separately specified ExpressionEvaluator.
>
> As Greg pointed ou= t, same difference.
>
> (Yes, the *interface* can [and should!] be made well-defined, but wh= ether there is a
> section break before the Ex= pressionEvaluator grammar rules begin does not make a
> difference.)
>
They can be functionally the same, but there are of course differences=
between a single JSONPathEvaluator, and separate= JSONPathEvaluator and
ExpressionEvaluator.

>From a spec point of vi= ew, the ExpressionEvaluator requires some
duplica= tion in its grammar, for example, it requires unquoted-string
and single-quoted-string. Paths occur in expressions, presumab= ly the
ExpressionEvaluator will not fully underst= and path syntax, but will
need to know enough to = extract them to be evaluated with the
JSONPathEva= luator.

>From a non= -functional perspective, it is noted that implementers will
likely follow the grammar, so if the grammar specifies separate<= br>
components, implementers will probably implement = it that way. This
requires a JSONPathEvaluator an= d ExpressionEvaluator that invoke each
other, wit= h more memory requirements, and the likelihood of deeper
stack recursion and less performance. Also syntax error checking i= s
more robust if the parser fully understands the= tokens it is parsing,
instead of simply knowing = enough to extract a string to hand off to
another= component. That's not to say the error wouldn't be detected,
it would, but the diagnostic could be less helpful.
<= div dir=3D"ltr">
I don't want to make the case to= o large, but I do think there is a
case to be mad= e for having the filter expression integrated into the
JSONPath grammar proper.

Daniel

--
Jsonpath mailing list
------=_Part_840853_708928001.1615334556075-- From nobody Tue Mar 9 16:42:03 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 5CB293A1440 for ; Tue, 9 Mar 2021 16:42:01 -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, RCVD_IN_DNSWL_BLOCKED=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=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 e1nMeeFUFV1A for ; Tue, 9 Mar 2021 16:42:00 -0800 (PST) Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 3141A3A143E for ; Tue, 9 Mar 2021 16:41:57 -0800 (PST) Received: by mail-wr1-x434.google.com with SMTP id b18so19723803wrn.6 for ; Tue, 09 Mar 2021 16:41:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=0uovwwLQT7KzY1wVJPYlOr7cBUuj6ZCOJDo4/Z8BAeU=; b=bKqHv6ROJ1UI9FSP3oV++IdXYtXAbD9iTZVA62dXO4wzGBlz3PHZsVPMp/QsaxJ1ys 68q6ezMWqRakwl7yBggQjInMyM+l4Ko4/n2Fs7L+U6TgIhkcriAW4DyyT3RP0XbwZu/W H8O2s7tjlRzU1LjRGcUCF4Pb1Oseb9WHgE4xqRBnZ8fj4PwCINqkNjfT7oV/6dz9O+je ghSlYMWpDddroSBPHDMAor0GXf9wpAgDRE4VzwhjUmIqgeRgY6P0gFT84pXlGUxGgHv8 Re0KRqwmCUxhdqdDa8YwNhN0uZQqkgrjBS3cpTITigknSVNeb8zi+35NoDI/8oyu/Lvw G4/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=0uovwwLQT7KzY1wVJPYlOr7cBUuj6ZCOJDo4/Z8BAeU=; b=Fe4c9dXRU15FYUf774uCtvzDMeKtaUyehk3TkgTv9a9oa2++ei8oIGsO17F0fD1XPV GduXll+Qg3e+ezSiV84WQz+9+HNSn+IixOOmHIMVBEfbbyz0IfdgazV9Tj0h5zeHgQ+k mgJokDTyp2nHzCbTGiekMKmWLiiMfuT682viLli/ovPpl/U8JbBwSu+GQG2ACOe64WYw QUGU7UkI1b09VbAi9nMCsSE2OAMCs8eFzXphzwaitbXiOcHSlZfTT9qC8MPnXm+VSe+V OslRGbY6oDAXi/QqSGAvOPDuzGOvKrU3lhJMiZ85AcoA8WNJF6DqFqE6mp2pQcuPSEK1 S8yA== X-Gm-Message-State: AOAM531YLGvQykc3w7GfwTVElhuM0DcjNoathE7s+Qd8INrYPqeaefMa +ocvSK7RjePJ68IOQC+iCYz0oe8lWc1uN1ahOr0= X-Google-Smtp-Source: ABdhPJwq2RpvgXwyZ4lTXWOPEib2EsvNylZx7wxdVMmfQ2rVHYsV1UeVHHpUAPgDkyJ+23qhPRo2+l3JCSoghKRDwOA= X-Received: by 2002:adf:e5c4:: with SMTP id a4mr538078wrn.174.1615336910173; Tue, 09 Mar 2021 16:41:50 -0800 (PST) MIME-Version: 1.0 References: <1442099741.747532.1615314908361@mail.yahoo.com> <25377B59-C541-4123-9BC8-3278F931BDFD@tzi.org> <1995936718.840854.1615334556078@mail.yahoo.com> In-Reply-To: <1995936718.840854.1615334556078@mail.yahoo.com> From: Daniel P Date: Tue, 9 Mar 2021 19:41:38 -0500 Message-ID: To: Greg Dennis , Jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Re Expression language -- index expressions and filter expressions 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 Mar 2021 00:42:01 -0000 On Tue, Mar 9, 2021 at 7:02 PM Greg Dennis wrote: > > > They can be functionally the same, but there are of course differences between a single JSONPathEvaluator, and separate JSONPathEvaluator and ExpressionEvaluator. > > This is getting into the implementation space, which we shouldn't direct. Implementations need to be free to define their own architectures. Our role is to define requirements. > Regardless, the WG still needs to choose whether to integrate the filter expression grammar into the JSONPath grammar proper, or define a separate grammar for the filter expression. That's all. My preference would be for the former. Others may have a different opinion. Daniel From nobody Tue Mar 9 19:44:04 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 D69203A1965 for ; Tue, 9 Mar 2021 19:44:02 -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_DNSWL_NONE=-0.0001, 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 2a5SqxO4GpGZ for ; Tue, 9 Mar 2021 19:44:01 -0800 (PST) Received: from sonic311-15.consmr.mail.bf2.yahoo.com (sonic311-15.consmr.mail.bf2.yahoo.com [74.6.131.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 D8D703A1964 for ; Tue, 9 Mar 2021 19:44:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615347837; bh=5cSXLyWwvk5Ye+2eoybhIDbh73kYVskcAMlNc52e0RM=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=fudE3mTTLeOIy5UG5tpd3+DFAuyx5A3sipTGWJgwsfakx6woIFG+BM7qD9OmfW9oWG/EPwRVRlRp24aL2dwSGFj/IOZGnK18jTKyrS0QTewzHXtMu3slprMasNTzBEvKRJitb6Mk/eDFa8rVwgU+TWzYIDIBJeZp7aUjZ/xt6/XU23nBn3EYcyoLkZWIdEuyAvFm5ikUGaf7SC1IFinoL8v0C0dLyUJE0aNCJFfSupQaL/BdR8EsNF8WAtlMmYJ1yVJcvbUFVBkaFWaVyR2iXcyTpd1z5EMGq8Tt5Gz+hIR18jvpw0Hz5FZX37Czhle+6SjwITzOavYwUe7t//ezRg== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615347837; bh=af3CIGpjrqfOFm7qYkkuWA8Tk1V5nUCYWJ0EWOLwoAH=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=TovDsTDTWdpHD5k7G9eIKJ6YNUfC5c2gRGKyehNbQ9fI1h7WYdH0+JynYZfHIlMDAhGY476QStc3lzJz6fm/9z4o9kK4TG+GlTnHESXO/HWX3fgeZV56kwaCRIXvslNPs9R1GSzOqeHEfn8fydY6lsU5XO686C3jOCCz8yXoX644J4jeMdauhpnQepcwH1h5p7e/JFKNgnpLo5wlv+RDZpzEqEHla910Zn48jo4/xTL9+ypScCrV1EiNsQq4LcYHL+05207Gt9qqkJBuQKBk3cPKP1pj8S4WyNGgE9rS7UNESpBmkTGgOeTpABog+HY9WOc6Z5LbqxE6eIiWL+xj/Q== X-YMail-OSG: DEmQ7_EVM1kU3ev4Ptwx5LSpc2WzZVDxHiFGL805hgsLcxMMloZEqxOSWzUWL3r NBnsQAmPw_hzuE6TYSZW51qmb2Bu1_kxJd.UG3VHkLGpp61tMCy35QNuck1zZngzAF6l6Ul6dW4r sCE5EF1w33FBYmBgerSrDHTpfYTQ_ZZT7S7oMprGdsANo2U1QZwdUcAQYrZHSYgeEYnzvFi2rDHw H7X3iKaoJgJKqkL0w9NvWvthOfOSVIWW_964CPRa..AlZmxzORQHaMQycyJrSs9efS9lASJBqlWU UPxQmzZ4gNegV_RRUM3EmNkvAXMt9ZuFioGnqV60GGBOW2XGH3Qvu5Gi096s8eX7.lhzDixS.SSU LC7cNEL4OUOEDEZEfsDH9fYhOfvO0UvvxKxh3ixi6Dh_vHJN3xh0Nlw2QQILr_VQ6Dv15bb2lJBD Sz0jYFiMMS9YJs0Ii_FLnlXwvV_43oYt2QA6bhTSnhUN3G_kDShC1wCahfcrzgxI4gG0n1uMAIJ8 vmMlfparUCcTZW711kI4RNcflV2eqZDFiyQy2vrr0JnljU1xIEpe3o8rraDYsdgN5rFmOyjSbGUR 5x.h4sEOHoqpNebKSCoNwXeWBrmXGZJpobzwSclnZfn2h18ij83FD8S2eexiLORcuODutyQOVyi5 rzrpzvOBX65RCtktGMZ1PjVOauU73IMZ.7fQ1HplQ3x6ORPKLTil52Rp1t9aQXZSOTohurJ_V.T5 pUrBWfpOcLCM6rHCw.7ut8XETOKG1IOMgQ6SYspoRa84SQ3LtUAbj0gSHKHxR7J0aSutKY0GomT9 TvL.3E3i53NcNhA998mWA5mEann9YXnI4LQE.faBtS0LrXdLIu_GhmsQFykXsiHs8enwp0_aDNpy 71lkaiPgedCv3_4K8QXHSxwTcb6zt8_MH2egRNcbIxGKOn7ItmDoBblRVraKqz7_aosohQOIuItW dzgoFXEuFPj4arUv_lgXJND9L8zrga2T5aUh3xU_uYbfjXPLnB7lU_wi2cr.o48piuDuG6eTUN0R kXNlIK13z9eEVwY7IAnN.kAGI2sxUXeiX7t7znqZ4o1.bAhyPyw5DjhBNEAJSjV63Liz5kG.yEqn 2pDH4o1EBss7.M9W3xaO2lZyeiSOCKVBEV85AOTK0BeYvb6rWSg5ZocWX0vDJHjcpF_deCK8q0wp yxzhR_2URxtRmf1jknBEl8lu89VZPWyj_ZAeoF7AeNma0koCOuEhIrV3YJtmKhuj08T2g03fpCGW s5N3oQxlOosMmtPuMr7_ZudRZu3tfhqzj6.lU.tM8sX6LJQE_axs5q1gdEb26xP1ebLQnnV9qTHY wAPJnGtYiWjkUy4saFKgvMR.j3q2qLCkO9BdHtoC.lge_MlMjamtmmJMuDLIDiohTzcjqnSFqcQv LE47ve7WQZtbB13eMMfSvf0UVpwCVUMCL_tP2BZdOAcedQ_pD87K1PkUkP6obwKGE947stc5XX2j qFOvrnFvGSVOOhYzEXijhudFtJMnk2_1HdTsLJEovZQpl02QvfIluNlTyAGSJRBI2J2zltL8CiFA dcL6xkSKrw12I_ykva5GJK48GQCl9B3WRhziOSVOoiVSk5Z01aZOpbwsfd9WSNK2XeartIbOtlk9 qV.mRLNR4hmtsaVAVavT9jDdA.G0sS.ZNOBcPcLWAudQFBM5sLMv1nG6EtmUsCrfrENyEkID1FGO uyXCP0188cl7YC6QHkYM_P740SscQLE2xYALYnWj7mME9E1bJdgaLq77CqqpHx2D6l_iw9d1eCH8 fH26Ms4OlDnvyxL0IAkqLYgYAQv.2Ul1T7.2CXk16IRzlEz71pdg.XT_OrCztfpiKxO7XSxYzqxw oQ2fd0BdBr7cGehQyCIPIcAcodVyS3v4S3_Kli837KLHJCQWjZmQvdi2ZIz4MZvEyWxgTzRhlEMx Gg3j2nbHtMQbienn1ppdgeMN1JloPhFgiEsz8iblWrECixPiftfRj6f_Fb_QMnsydVrnY9AnXT.7 mZnn72D50ENlDCkqSpLsGh46YGtSSJkhDb7HY6fCokC1.toiaaODaUE6_eAeLZU6yCpletNYXhoZ rSt_thk_NRFeu_vAe9Fv6qcTbwqkdNnpCbjbE.DjHNVzkcszXCmZ8qByOyRz1z7mxd0.FH1p9Brt jMLwFUUCfVV7.IRmPFuW6lA1QFj5z0UhvQEOXYYAkAMFP1FxRF2Fq.BVsEE8DfaRGLBJsRMXTmT1 9froi8qEQJnSqe263.Rf4SenlONMLNlgOEuZo6gDwB8bBBngv5D30yyUvaV2Bx.qxsMBW6zKHqoe .hpeBGcyDHyzoc6vTcZwcA9_sHzn877N._QxXTxATmCvrMX3XwxYrAHEfvvKe28h.jY4qFh_9iQd b4pONnm1wcZGSykV8bjofE5CpMkva851iegBMCYJYFpl6nPs96WvCCYUCvlWxWUJF0dgeqZAvbBe wZPbNwnkpP_.25vjyk2Lpa4JVPnoE4JAWQ1FOkzmaMJhABaLva1nSUgOILQAe9d80evOsmtD3dn2 mixsnO2ktoRSIM9HfDUUPClJS7dF6AFF62CI.QtuXHUQQxXXj0DKhJjvRP.iB87d0.JKFLDGXxY6 aP0GGoiSUYLexi7iinTdflieK8lNcV.F5LeVvnCZOc.zCUOCXv24btq9gzCNtf8Bu8ROyRZtDJ4D 23vxUVRkePA7_83euU0HwYfLuJQaeY5hZ6pD9_1KSIaKxUrnHK.rq X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.bf2.yahoo.com with HTTP; Wed, 10 Mar 2021 03:43:57 +0000 Date: Wed, 10 Mar 2021 03:43:50 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: danielaparker@gmail.com, Daniel P , Jsonpath@ietf.org Message-ID: <1267899746.868305.1615347830722@mail.yahoo.com> In-Reply-To: References: <1442099741.747532.1615314908361@mail.yahoo.com> <25377B59-C541-4123-9BC8-3278F931BDFD@tzi.org> <1995936718.840854.1615334556078@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_868304_425688071.1615347830721" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Re Expression language -- index expressions and filter expressions 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 Mar 2021 03:44:03 -0000 ------=_Part_868304_425688071.1615347830721 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Daniel, could you explain the two grammars, please? I'm not sure I follow w= hat you're suggesting.=C2=A0 I see only a single overall grammar, where exp= ressions are a subset of that grammar and only valid under certain circumst= ances. Surely, the expression grammar will be defined within the same spec (it doe= sn't make sense to write an entirely new spec for an expression grammar tha= t will only be used in JSON Path), but I can't see expression grammar just = being used anywhere within a path.=C2=A0 It only makes sense where an expre= ssion is valid.=C2=A0 Additionally, I would expect that the path grammar sh= ould be valid _within_ an expression, e.g. `@.name`. Separately, there exists a question (which has been mentioned on GitHub) re= garding nested expressions, which also leads to scoping for `@`, but I thin= k that can be left out of this discussion for now.=20 =20 On Wed, 10 Mar 2021 at 1:42 pm, Daniel P wrote: = On Tue, Mar 9, 2021 at 7:02 PM Greg Dennis wrote: > > > They can be functionally the same, but there are of course differences = between a single JSONPathEvaluator, and separate JSONPathEvaluator and Expr= essionEvaluator. > > This is getting into the implementation space, which we shouldn't direct.= =C2=A0 Implementations need to be free to define their own architectures.= =C2=A0 Our role is to define requirements. > Regardless, the WG still needs to choose whether to integrate the filter expression grammar into the JSONPath grammar proper, or define a separate grammar for the filter expression. That's all. My preference would be for the former. Others may have a different opinion. Daniel --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_868304_425688071.1615347830721 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Daniel, could you explain the two grammars, please? I'm not sure I follow w= hat you're suggesting.  I see only a single overall grammar, where exp= ressions are a subset of that grammar and only valid under certain circumst= ances.

Surely, the expression gramm= ar will be defined within the same spec (it doesn't make sense to write an = entirely new spec for an expression grammar that will only be used in JSON = Path), but I can't see expression grammar just being used anywhere within a= path.  It only makes sense where an expression is valid.  Additi= onally, I would expect that the path grammar should be valid _within_ an ex= pression, e.g. `@.name`.

Sepa= rately, there exists a question (which has been mentioned on GitHub) regard= ing nested expressions, which also leads to scoping for `@`, but I think th= at can be left out of this discussion for now.

On = Wed, 10 Mar 2021 at 1:42 pm, Daniel P
<danielaparker@gmail.com= > wrote:
On Tue, Mar 9, 2021 at 7:02 PM Gr= eg Dennis <gregsdennis@yahoo.com> wrote:>
> > They can be functionally t= he same, but there are of course differences between a single JSONPathEvalu= ator, and separate JSONPathEvaluator and ExpressionEvaluator.
>
> This is getting into the implementation sp= ace, which we shouldn't direct.  Implementations need to be free to de= fine their own architectures.  Our role is to define requirements.
>
Regardless, the WG still needs to cho= ose whether to integrate the
filter expression grammar in= to the JSONPath grammar proper, or define
a separate gram= mar for the filter expression. That's all. My
preference = would be for the former. Others may have a different
opin= ion.
------=_Part_868304_425688071.1615347830721-- From nobody Tue Mar 9 23:39:34 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 8B6C33A1CBD for ; Tue, 9 Mar 2021 23:39:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.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 fqvSDQxy8IIH for ; Tue, 9 Mar 2021 23:39:30 -0800 (PST) Received: from JPN01-TY1-obe.outbound.protection.outlook.com (mail-eopbgr1400100.outbound.protection.outlook.com [40.107.140.100]) (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 DFA593A1CBA for ; Tue, 9 Mar 2021 23:39:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Lp8CnIHMhTSSALSTuCXl72hQ3qoArXhPgyfSb9qOgNB9LEk24dy4zsA38lfokMbgEwmKhSxSXeEE1qB4tTDR79LZ1SiEtR2xZSVRvbf4TQxXFckPr2ftY39vG6+lOWtWiLxgdtpFjGrPXHPNoORVJRfIoL9eZT42gZbNfR7XJbQ4xxZr0CVM2eMTbq36Juaht9ZxtUp+Z4SGb3S4RxpxtQs+dWjLbMyaK30ETb60TiEN+RcY/WcpWaucDrkpsaKV8c2BHBNkOhGn3p2/QzAbaFdETLwwDk4J4oLFALo+30lTNzXf7FSWlj99xic0sjgBW6swFGPp4ht01lJprzTpDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QHeWAN2+EWPirhqnEk7FtwB1g6Lf2BlPXjIQgdxrBlA=; b=CM8ozOSFJpwxzid3EMDcqge9qzwkOkAmVN/wKoROtokTTA2bifk9qXeRYnBq8P6umgqSfkAg0pkxK4yvvnQjoHHyQhKXcT8roBPawRt2/LmohlS8f1PZzjltQmXGscA5lDxhOs3iumJrdYIHQTvhNzToSkhjv44qDML/bjZsKTn8PJPyS9YgTHuMxaepM6HAVxSrsUkvcMYr48hzLA+rPncEO08/sm9ZCoCpwXzVvsqt9aEbcuVXzAxumE6xH8PYCcYQFL9Vr6dUx7waMuRcVXl51oq+teDayVY/g/d66k5NCSx2fMCex+8pdwUWeZF9Wlwj8iau4DwmJg0kZI9y4w== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=it.aoyama.ac.jp; dmarc=pass action=none header.from=it.aoyama.ac.jp; dkim=pass header.d=it.aoyama.ac.jp; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector2-itaoyama-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QHeWAN2+EWPirhqnEk7FtwB1g6Lf2BlPXjIQgdxrBlA=; b=IQwyMEN6mtWks4Cf1rKCsSE8jx9lpRBpOwIcWYi4MyehFGrGk9J9usx4idf7KJShc2lMhBLTb51uZdQ6ff7vYaJEq7M11Vbc0kCfnyopiY/YFu/JM0ADfmtbAvUqrHinYvgghEFsHRsdZU0VB2w89iDvlvAimf4bleWnzyg7WOU= Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=it.aoyama.ac.jp; Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7) by TYAPR01MB6251.jpnprd01.prod.outlook.com (2603:1096:402:3d::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.17; Wed, 10 Mar 2021 07:39:24 +0000 Received: from TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::5996:7da1:39fe:eca2]) by TYAPR01MB5689.jpnprd01.prod.outlook.com ([fe80::5996:7da1:39fe:eca2%4]) with mapi id 15.20.3912.029; Wed, 10 Mar 2021 07:39:24 +0000 To: Greg Dennis , cabo@tzi.org, jsonpath@ietf.org References: <8A691340-D265-4A50-A003-4E836CB80F92@tzi.org> <1723015503.534113.1615276034552@mail.yahoo.com> From: =?UTF-8?Q?Martin_J=2e_D=c3=bcrst?= Organization: Aoyama Gakuin University Message-ID: <6bdc5019-726c-f11a-fc24-f7ee58cd17ce@it.aoyama.ac.jp> Date: Wed, 10 Mar 2021 16:39:21 +0900 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 In-Reply-To: <1723015503.534113.1615276034552@mail.yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [223.217.46.174] X-ClientProxiedBy: TY1PR01CA0146.jpnprd01.prod.outlook.com (2603:1096:402:1::22) To TYAPR01MB5689.jpnprd01.prod.outlook.com (2603:1096:404:8053::7) MIME-Version: 1.0 X-MS-Exchange-MessageSentRepresentingType: 1 Received: from [192.168.1.7] (223.217.46.174) by TY1PR01CA0146.jpnprd01.prod.outlook.com (2603:1096:402:1::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.17 via Frontend Transport; Wed, 10 Mar 2021 07:39:23 +0000 X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: f4077d58-4fad-4afc-5ce2-08d8e397a002 X-MS-TrafficTypeDiagnostic: TYAPR01MB6251: X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:10000; X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: QBPL9UaYu7kc3IiFjZz6yBZEaBcM2AO6qjc8Vm9Q8XhBXmhgLPno9DIHq0b4FjOIzLcsju0m6f8c2BYOGtpge4ZKZ90fDGQadDwDJSLiRWmvuHtk4/euigKrvtTST2FjNpUM3GkMg2ipQq1FJPRQC8FGOX4ioT6rFR33TZDwbTxEl+UI1IBN2dFCNnhr6XXHeGUGerFr8/4Xvyj+uBPgONkY2a44clRmE24dAUvUAlFNeE7wc3przzhv2Q7nAaH5Pb20Vk4gVXDIjHJUsapkUs6fbfRcxMYrDsneamCLVmvPiKfha+tlqG4d6+QzszWNXvVVuoiLi/qLq4bloczBLdmnyQRgUWGfnFgGD7aVjkX68+jLCOg1e200uPHIfP9TFkGJ5oMsNhdRzNGZFUUOelNIsahIfuyRw16XSu0KffVhuG7/TEKQJ7V1QEKxR9q9mdCD2zFvg68mZvS7ZCN0SkDHmMZledPuZhGimyuC4LS8QtqIJTasSLVkY0PiFTQq7z5g9tAaScimh4g7z1OBNSYTG9L+7m2+zFgsgnFVBKDtch23uu8cW8UJO7PaIyJcogpr/zfQGRBsjX0vmxZuUCsNE+QEdSODKwAZkZn5fbQ= X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:TYAPR01MB5689.jpnprd01.prod.outlook.com; PTR:; CAT:NONE; SFS:(346002)(136003)(376002)(396003)(39840400004)(366004)(2616005)(956004)(31686004)(83380400001)(5660300002)(52116002)(8936002)(8676002)(66476007)(36916002)(66946007)(66556008)(86362001)(786003)(316002)(478600001)(31696002)(16576012)(6486002)(186003)(16526019)(2906002)(26005)(53546011)(45980500001)(43740500002); DIR:OUT; SFP:1102; X-MS-Exchange-AntiSpam-MessageData: =?utf-8?B?ZUM3YUt2ck1xaHpoek9WYzJrendQK1JWMlp4ZjkzazQyUmRJblNpUDVXM2JW?= =?utf-8?B?eHpMcVJSUE1JUUVvcVJUakswbVZUNDVwdk9HWEtZUUFoaVlJYmhmaWRyVStj?= =?utf-8?B?cURsMXJUVlB5Ykc0aFYwUmZ1M2NrSi9BV0NUQjA2Y2xuR0xIRDFEMmwzTXda?= =?utf-8?B?VVF3UnR5VDJZYitzUXZCcnhFU0tjNkhWRGZiZjlkUWM1Z21RVVZFOTUzdjc4?= =?utf-8?B?TGo5OFA5M2JlVWFqUWZ1NXM2Z084bnRGTFhVYnJtamxTYk9HWmF6S2NhUjI4?= =?utf-8?B?UCtpa1J0aWVLQkgyRVNETXBkR3FLVzY4T1h1ejN6Y1poS0syZHVRRnJaTTgv?= =?utf-8?B?SjhVNGh3Um9Ydy9KQTFUOFQvNmVPemE0SzlpWWlKYXFaT1AyVmc0WjBJVzd1?= =?utf-8?B?QTFzZUxBV05QS2RFV29mSDd0SS9uUG9xWmxSRzV4aUJhZThOQWxYbU4yY2VD?= =?utf-8?B?UU9jZmtBa0JvRktyQmtSNVJrZUJxNTBHK3g1dElMcTVWTlBlaWVWQkM4Qldr?= =?utf-8?B?U1o3cXN2WVQxTTZ2U1FpL0VWMTFmNWpnNGpYU1dCUFFnUzZDMVV4VTBjOFhX?= =?utf-8?B?V0svaHJvSGVjQm4yQVlhcHRzSloyTjRKdGdUVytRY01pMUd0U0hIaXY1MWpQ?= =?utf-8?B?Z3hoanZoU0dOZ0tQdzdISkJiSjMvRm42M3JiN3c1U3EzV3dDRnFWcldIUk1D?= =?utf-8?B?a1RMRkFHR0d2bDg4QTJPWGJQSzlJQmpBZjRRazhuVEFuZmw3M0x6dml1WDZ4?= =?utf-8?B?RkpRSk5ydFNHRGROSVhwdFZqQkVYa0h5ajREeDNGN1lNaTc2SnFTT0FXTVlR?= =?utf-8?B?b2o3NUFEVG5idjV5a3NsY0k4V0ZGSE1KYk1xYzk2TnRvWEhsbnRIOHdhdjd6?= =?utf-8?B?SGh2UDM3UCt3ejdLWjBYcWJ5MzRaam5XNEZNcWkxVzlsNmdGU2s4Wm5JNW9V?= =?utf-8?B?T2t4V3h1VSs2VW9aSEwyN1dLQzV5UUNrQlh3MU12VDhBOGp0SitIT3BDZFdl?= =?utf-8?B?ZklpbHliREtpU0szRE1SM0FJWmxQUHE0WFVnODhuaGR2VzdQNGdNUDNwNDhR?= =?utf-8?B?TDRlOHJWaEpONmtZcFdsK0MvNmcvbDhob1YyejNnK2N0NXFCc29QNjcxdllV?= =?utf-8?B?TnE5NjRBVFdISzZ1Wm5xSjJLK1NSb2NHZkVydndoUmxlbU5FL0pHTzBYM1Mw?= =?utf-8?B?NkxiZjgwN2lxSmNLUXNzT3RwUEJBVHRmOWlheEdZREEzS3RqMVV5NklqRkVJ?= =?utf-8?B?NklHdkxHYzd4NHlBcmdXUnBsN3RXTXgzcDY0cUJ1N1BtK1RXNW00TE5DUFJC?= =?utf-8?B?b0U4ZDc2eWNSRDN4c0dlTzNuS2wremxtKzVnaWlid3B4RTBYa1JMeUNYOXRt?= =?utf-8?B?UVFHVitVL0dCZlVtSFkrNnFmQ3piamxDOU5XNEllMEVoYzdYT2NKdHFNUXRZ?= =?utf-8?B?MnNRcnJnTjJkQlZlMjBYaTNxK3dTSFlTeFBCQjV0K2M4cjBDUktaVVlmTTNZ?= =?utf-8?B?N2c3YVZzWG9HYURPanBrcWFHMVl0cGxSU1hpRlM0dC9kSjJJaUx3d2c0ZjZW?= =?utf-8?B?cW5iN1UyS1JETmU5UzNubkhheUs1K0ZMTFBwNEt2SERaVWtweEczUGplTnFT?= =?utf-8?B?MkU5Rm9zMll4TDJDWThETmxOWXdvWFNuU3dHbE5iemRNVVFjWmFRYnM0UGpB?= =?utf-8?B?b3FDc1QrekY2VXRwVVRhbzNGWXd4YVhoUDc1OTRpUmRWbFluQlQzeUNISFNF?= =?utf-8?Q?ZK+/3JI6HHGXSKU3GO1ZwLC6Dzg1xIj1agovgTW?= X-OriginatorOrg: it.aoyama.ac.jp X-MS-Exchange-CrossTenant-Network-Message-Id: f4077d58-4fad-4afc-5ce2-08d8e397a002 X-MS-Exchange-CrossTenant-AuthSource: TYAPR01MB5689.jpnprd01.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Mar 2021 07:39:23.9590 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: e02030e7-4d45-463e-a968-0290e738c18e X-MS-Exchange-CrossTenant-MailboxType: HOSTED X-MS-Exchange-CrossTenant-UserPrincipalName: 8cKjqF8DHn2xopgBRT4CWGHJYetWTT/Dxk6dYPbOAvKFHutL+7+CLCU4kwrBT+jkROVr5DsbOMF3Pe+EQC659g== X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYAPR01MB6251 Archived-At: Subject: Re: [Jsonpath] [ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath] A "General Considerations" section (#58) 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 Mar 2021 07:39:33 -0000 On 09/03/2021 16:47, Greg Dennis wrote: > This formatting (or lack thereof) removes all cues as to what's the Schema spec text vs my comments vs your comments. > Greg Hello Greg, In the messages from Carsten, I can easily see the distinction. In messages from you, either things are reversed (your new comments look like cited text whereas all the cited text looks like it's newly written text) or there's no distinction at all. You probably have more of a clue as to why that happens than me. I have seen other IETF participants with various similar issues, but not something exactly like you. What Carsten's mailer does is what I see most other mailers in IETF discussions do. I hope you can fix the issues on your side soon. Regards, Martin. P.S.: I'm using Thunderbird. > > On Tue, 9 Mar 2021 at 8:40 pm, Carsten Bormann wrote: Moving this discussion to the list, because it touches a large number of issues. > I’ll try to parse apart this pile of unrelated considerations; maybe we can dispatch them into the specific issues raised. > > > 6.1. Range of JSON Values > > An instance may be any valid JSON value as defined by JSON. JSON Schema imposes no restrictions on type: JSON Schema can describe any JSON value, including, for example, null. > > > JSON Schema uses the word "instance" to describe the JSON data that's being validated. We seem to have landed on the word "data." Regardless, I think the gist of this also holds true for JSON Path: input values can be of any JSON type (although only certain types may return results depending on the Path) > > Yes, JSONpath should be able to be applied to any JSON data item (JSON value).If we haven’t said so yet, that’s probably because it is an obvious property of a useful query language…(Editorial, if you ask me.) > > > > 6.2. Programming Language Independence > > JSON Schema is programming language agnostic, and supports the full range of values described in the data model. Be aware, however, that some languages and JSON parsers may not be able to represent in memory the full range of values describable by JSON. > > > This, I think, is of utmost importance. We definitely should not favor a specific language. Doing so would inhibit inclusivity and shun people who work in incompatible frameworks. > > There is a wide gamut of meanings to the expression “favor a specific language”.Is requiring arbitrary precision integers “favoring a specific language”?  Specifying a specific regex dialect?We may need to accept the dominance of certain platforms in our decisions (e.g., the I-JSON limitations caused by JavaScript), so I don’t know how to act on this. > Of course, we shouldn’t wholesale import a language (e.g., as the expression language), except if we do. > > > This statement also makes it clear that it's understood that some frameworks inherently have limitations that may prevent them from being able to implement the full expression of JSON Schema. Declaring this outright allows such frameworks to have partial "best effort" implementations and still be compliant with the specification. > > We probably want to avoid compliance levels, profile implementation conformance statements…Just as we need “extension points” (see below), we may need “limitation points”. > > > > 6.3. Mathematical Integers > > Some programming languages and parsers use different internal representations for floating point numbers than they do for integers. > > For consistency, integer JSON numbers SHOULD NOT be encoded with a fractional part. > > > I'm not sure whether this would apply for us, except maybe for array indices. > > No idea what this does here.  We don’t get to decide how our JSON input is encoded.More importantly, we don’t get to see that (unless we require JSONpath to be used only with a specialty not-quite-JSON decoder!). > (But, indeed, we do get to decide the number system used in our expression language.) > > > > 6.4. Regular Expressions > > Keywords MAY use regular expressions to express constraints, or constrain the instance value to be a regular expression. These regular expressions SHOULD be valid according to the regular expression dialect described in ECMA-262, section 21.2.1. > > Regular expressions SHOULD be built with the "u" flag (or equivalent) to provide Unicode support, or processed in such a way which provides Unicode support as defined by ECMA-262. > > Furthermore, given the high disparity in regular expression constructs support, schema authors SHOULD limit themselves to the following regular expression tokens: > > - individual Unicode characters, as defined by the JSON specification; > - simple character classes ([abc]), range character classes ([a-z]); > - complemented character classes ([^abc], [^a-z]); > - simple quantifiers: "+" (one or more), "" (zero or more), "?" (zero or one), and their lazy versions ("+?", "?", "??"); > - range quantifiers: "{x}" (exactly x occurrences), "{x,y}" (at least x, at most y, occurrences), {x,} (x occurrences or more), and their lazy versions; > - the beginning-of-input ("^") and end-of-input ("$") anchors; > - simple grouping ("(...)") and alternation ("|"). > - Finally, implementations MUST NOT take regular expressions to be anchored, neither at the beginning nor at the end. This means, for instance, the pattern "es" matches "expression". > > > Not sure if we're planning on supporting regular expressions. It appears that some implementations do have some support, but it's all extension on the original syntax at this point. Still, this is a good declaration of support. > > As we define our own expression language, we also get to define our own regular expression dialect (I hope in a less mushy way than above). > > > It also ties in closely to section 6.2 regarding framework limitations as not all frameworks support the same flavor of regular expression syntax. > > It may be worthwhile to quell outright the expectation that the JSONpath regexes can just be dumped into the implementation regex dialect. > > > > 6.5. Extending JSON Schema > > Additional schema keywords and schema vocabularies MAY be defined by any entity. Save for explicit agreement, schema authors SHALL NOT expect these additional keywords and vocabularies to be supported by implementations that do not explicitly document such support. Implementations SHOULD treat keywords they do not support as annotations, where the value of the keyword is the value of the annotation. > > Implementations MAY provide the ability to register or load handlers for vocabularies that they do not support directly. The exact mechanism for registering and implementing such handlers is implementation-dependent. > > > This is good to have because invariably, implementations will want to extend functionality beyond what's in the spec. It basically covers other implementations from also having to provide the same extensions, requiring only what is stated in the spec. > > It also mentions "vocabularies," which are a spec-defined mechanism by which implementation can extend functionality via new keywords in such a way that they can optionally be supported in other implementations. Furthermore, this mechanism allows the other implementations to refuse to process a schema that requires a given vocabulary if the implementation doesn't understand it. This bit I think is good for later when we eventually get to spec-defined extension mechanisms, but I don't expect that'll be in the first draft. > > > Yes, we need an extensibility (and evolvability) story.This will revolve around extension points, which need to be defined in a more rigorous way than “ignore what you don’t understand”.We may also decide not to have extension points (like JSON did), but we need to make this decision in a very conscious way. > Grüße, Carsten > > From nobody Wed Mar 10 07:24:22 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 639ED3A1009 for ; Wed, 10 Mar 2021 07:24:21 -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 WjAfzmqj1KNs for ; Wed, 10 Mar 2021 07:24:19 -0800 (PST) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 70F8C3A1094 for ; Wed, 10 Mar 2021 07:24:15 -0800 (PST) Received: by mail-wr1-x435.google.com with SMTP id l11so20388986wrp.7 for ; Wed, 10 Mar 2021 07:24:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=dptXhhDWeyuZYPhZ9AcuSFMQsnd+VDh0FUY9c7b1EX8=; b=COsbj6smqCRSSpWLAb09tvihAxhB5PZMQxWR0+iw2lYK04yyQAnK2bxe2pnKr/0ITH eZTRB+h2iHNKYeapvtAGN8/J7U9rcItCVocEVmVpK0RJqXWD5cwMYbQqcancNudlo+X2 lvhMYLnEbrdxp0nLXxQl/jx1NnRpxYbHYMiX7XCZOt92jrFMcpFCRtH0GJmRITn+/YXi TzhSRp44e/BGVtTvBAItug6yJtwHEPeS+w4hi5/urOuK5x8vabJRR6Huh8Cdc/t+oyZ9 e2EcXFUpxo1uqcFAtkfBMd2JOCzjxhpoJgrhC93I3CoW9Wuxmil73oH2Z3mxQnf+sT/l iuDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=dptXhhDWeyuZYPhZ9AcuSFMQsnd+VDh0FUY9c7b1EX8=; b=BFWx6F1MBi5vCkY5sAYxMignaEkVQJVn6JTf9l94iA6ST58Z9JQDoPFhKUgLmyhVap LIkAlWo7BG6aeRUiID9UM8cdE3vaxnoKdi+02Sa9hhG8Ya/NwpROIjPg8ZR7tZuLNb+y WdRI0iqtFhneuzEA5jMIIwJEaD2Hm9P/0FArmc1zhknwK5c56ikmlJyXAZsB55/U48oI i2smsBXTlojKmIxVsMX0qpe0c3HV+FDj91Gl8SpFayfWqzWi4wCgReWEGUiOXNaZ83ZI Q8TCGzO8jLIRztY/TzikSrxd6ilkAiVWH2GS1LbxRQY7xPD16XjiENrUfrzXOZKFFdOv 3/AA== X-Gm-Message-State: AOAM530hKqAAewo6HGKgT/TR+hHgI54673ZDQVSTSm2vtO4hgXOyHaiZ 6rYoMs5ByTepI9AGO3V0xyURJjcMrXxFd6cBY3jMrmk+lmz6cQ== X-Google-Smtp-Source: ABdhPJwtkXik2xq2K/wpaws/06K8Va2CXI8pQIipgpTnx1eiL4XglhAQLTyrWplS1x5QNEW+OQFTa9f9LNXL/kQ3HMg= X-Received: by 2002:adf:f0cb:: with SMTP id x11mr3980810wro.206.1615389852524; Wed, 10 Mar 2021 07:24:12 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Wed, 10 Mar 2021 10:24:00 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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 Mar 2021 15:24:21 -0000 On Tue, Mar 9, 2021 at 10:44 PM wrote: > > From: Greg Dennis > Daniel, could you explain the two grammars, please? I'm not sure I follow what you're > suggesting. I see only a single overall grammar, where expressions are a subset of > that grammar and only valid under certain circumstances. > > Surely, the expression grammar will be defined within the same spec (it doesn't make > sense to write an entirely new spec for an expression grammar that will only be used > in JSON Path), but I can't see expression grammar just being used anywhere within a > path. It only makes sense where an expression is valid. Additionally, I would expect > that the path grammar should be valid _within_ an expression, e.g. `@.name`. > Sure. To make it clear, I'm in favour of a single integrated grammar describing JSONPath selectors and filter expressions, much as other query languages like XPATH and JMESPath have. But historically, many JSONPath "grammars" (implied grammars), defined [?()] and treated within parentheses as a single token, to be extracted and handed off to a separate "script engine" to evaluate. Javascript was a popular script engine. Javascript has its own grammar, it doesn't know anything about JSONPath. The syntax in the Javascript engine would not be exactly the same as in the path grammar, for example, completely general JSONPath expressions would not be supported in Javascript comparator expressions. Unquoted names could have different conventions. It is Javascript, afterall. This works, because while JSONPath depends on Javascript, Javascript has no dependencies on Jsonpath. Of course, not all JSONPath implementations used Javascript, some used different "script engines", and some took the other approach of a single integrated grammar. Let's consider another fully specified language for the moment, JMESPath. In JMESPath, filter expressions are defined in the grammar as list-filter-expr = "[?" expression "]" comparator-expression = expression comparator expression comparator = "<" / "<=" / "==" / ">=" / ">" / "!=" The operands "expression" can be any kind of expression defined in the grammar, whether identifier-expressions, index-expressions, comparator-expressions, JSON literal, and so on. Now let's ask the question, instead of integrating filter expressions into the main grammar, could JMESPath have defined list-filter-expr = "[?" "(" ")" "]" and treated within parentheses as a single token, to be extracted and handed off to a separate "script engine" to evaluate? I don't see how. That script engine wouldn't be like Javascript, which has its own grammar. Rather, it would be intimately dependent on productions in the main grammar, which in turn would be intimately dependent on productions in it. Now, let's come back to JSONPath. Consider [?()] Now, say we want to specify our own script engine for . We could make it very much like Javascript, or different but still independent of the main grammar. That would work. But suppose we want to support things like comparator-expression = expression comparator expression where, analogous to JMESPath, any kind of JSONPath expression is allowed as an operand, including selectors with filters. Now we're back to a situation where productions in the main grammar and productions in the filter expression grammar are intimately dependent on each other. So what could we do? We could do some hand waving and leave it up to implementers to figure it out. We could say "expression can be any JSONPath expression" without further elaboration, effectively treating them as a single token, and let implementers worry about how to extract them. Or, we could place restrictions on "expression". For example, we could restrict "expression" to simple paths like "$.foo.bar", without allowing filters, and have a separate grammar to describe these, that doesn't have a dependency on the filter expression. These are options. Some people may be happy with them. And that's fine. My preferences, though, are (1) for the JSONPath specification to be of the same quality as the JMESPath specification, with an unambiguous grammar, and (2) to allow JSONPath expressions in comparator and arithmetic expressions to be general and not constrained. And for those reasons, I'm in favor of one integrated JSONPath grammar, and not a separately defined "script engine". Daniel From nobody Wed Mar 10 07:29: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 B6FC23A10DF for ; Wed, 10 Mar 2021 07:28: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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 395NPD2IYM7T for ; Wed, 10 Mar 2021 07:28:56 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB9E3A10BA for ; Wed, 10 Mar 2021 07:28:55 -0800 (PST) Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DwbZs5RBfzysx; Wed, 10 Mar 2021 16:28:53 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Wed, 10 Mar 2021 16:28:53 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 637082933.222487-98e52e82ee225a5e2f7a0182391db9cd Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Daniel P X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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 Mar 2021 15:28:59 -0000 On 2021-03-10, at 16:24, Daniel P wrote: >=20 > But historically, many JSONPath "grammars" (implied grammars), defined >=20 > [?()] >=20 > and treated within parentheses as a single token, to be > extracted and handed off to a separate "script engine" to evaluate. Why would we want to do that? Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Mar 10 07:46:31 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 EDF4D3A11ED for ; Wed, 10 Mar 2021 07:46:28 -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 BQXjVfj14hmM for ; Wed, 10 Mar 2021 07:46:26 -0800 (PST) Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 825FF3A11F2 for ; Wed, 10 Mar 2021 07:46:26 -0800 (PST) Received: by mail-wr1-x42b.google.com with SMTP id w11so23857834wrr.10 for ; Wed, 10 Mar 2021 07:46:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xuUb74u60uiAmZ4u4TB5x1D2EU4ItCgiMVtTyUvhrPg=; b=p8/MzVIFEN+jFZ38nJlgr9mUEJVo1xIEsHvTycpyb2RK7Y3qqpqXWadW6cKl4iVJUZ 0aDLDf8m7Ct30WUAcCZVI3PmFBdKIC97PFQzlcYw7RIryzGaKuvO8En0H60ELaTE+kOX Hi/saxObiIOmRSlwuJyFG+CVyxdvC7uIopyxHWFWr0oMWpXUmYHB9fiwl/pp05iXjsOL cbrT3gpzUyJc40spdmozb/2KY3EzQH2+EGuJtPDoOaHYC3btm0t+IN1L9lnLn2tVP02B Ex4T81aFKTpjf0xLTHodoIZQcQJNTPulHUrK6ThfA68lzoI4NPsq8nDOj4nmLe9kSHw6 52lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xuUb74u60uiAmZ4u4TB5x1D2EU4ItCgiMVtTyUvhrPg=; b=lJd5SOM7GTkzNTNNEEM3aLsaFmLwo7YSCWq2RIwbQ4b3wc2JnXDQAuKkSMwq2LX/l9 7ucmrWFaJAbf7X7dB6gZCccbEnYpzpdDhNOQdG2xEP1SAIjl34Y9uqM5Te8eoznmf+N0 R0Gs8Hw31EmR80SI0m1HqkSuSqx2A34jLMqpz5mkz2ICzT/rBKneh3V8cdHULf2zsiOO X9EzFQ+Y8bj3IeVawtRNOaqKm7umc64aOUJTA0dxvGch9kYQEsUm6HrHQ5tiu/rLHJgQ y53pSNFOpqTn47q63UM8aeT25fuC128dau3dgrt90xsZSR7Uhln0dBkR/XFGyv8TNWgi XUuw== X-Gm-Message-State: AOAM533eFCNS1bewiRE6R8JNRe7swQoujneO/2NvNhse0/wQdvJEV8V8 dZfkNzX+Zuqk5/IJG25gxkHXCr0lANxjhz/2Xgk= X-Google-Smtp-Source: ABdhPJzjrgrWpGwF43f17KDQrqfWSrab2n1+aJTH5KVviFhszZyMwfKBoEzuxqtRITFl8wkMXwTx26BSXLE7hwpKQuE= X-Received: by 2002:adf:f0cb:: with SMTP id x11mr4071146wro.206.1615391184451; Wed, 10 Mar 2021 07:46:24 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Daniel P Date: Wed, 10 Mar 2021 10:46:12 -0500 Message-ID: To: Carsten Bormann Cc: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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 Mar 2021 15:46:29 -0000 On Wed, Mar 10, 2021 at 10:28 AM Carsten Bormann wrote: > > On 2021-03-10, at 16:24, Daniel P wrote: > > > > But historically, many JSONPath "grammars" (implied grammars), defined > > > > [?()] > > > > and treated within parentheses as a single token, to be > > extracted and handed off to a separate "script engine" to evaluate. > > Why would we want to do that? > Don't ask me, I don't know. That question should be asked of people that want to do that, if you can find any. One person has written to me privately that they wanted to do that. In my original post, attempting to make a modest contribution to a discussion about filter expressions, I simply "remarked" "Another issue is whether expression evaluation should be a separate component, or integrated into the JSONPath grammar proper. My view is the latter. A number of implementations take that approach." which, as far as I can tell, is a true statement. I didn't expect that to be a controversial statement. Daniel From nobody Wed Mar 10 07:59:37 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 053AD3A1251 for ; Wed, 10 Mar 2021 07:59:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.92 X-Spam-Level: X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 sPxenylukwfw for ; Wed, 10 Mar 2021 07:59:33 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 270073A124F for ; Wed, 10 Mar 2021 07:59:33 -0800 (PST) Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DwcGC3RPYzysh; Wed, 10 Mar 2021 16:59:31 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Wed, 10 Mar 2021 16:59:31 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 637084770.992303-2f7efd43413ec15fe4f655664bab4e77 Content-Transfer-Encoding: quoted-printable Message-Id: <67D7797A-73A8-4F44-8EBD-098C6AC6C976@tzi.org> References: To: Daniel P X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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 Mar 2021 15:59:36 -0000 >> Why would we want to do that? >>=20 >=20 > Don't ask me, I don't know. That question should be asked of people > that want to do that, > if you can find any. One person has written to me privately that they = wanted to > do that. >=20 > In my original post, attempting to make a modest contribution to a > discussion about > filter expressions, I simply "remarked" >=20 > "Another issue is whether expression evaluation should be a separate > component, or integrated into the JSONPath grammar proper. My view is > the latter. A number of implementations take that approach." >=20 > which, as far as I can tell, is a true statement. I didn't expect that = to be > a controversial statement. Finally got it. It seems you just stretched our imagination a bit :-) I think we already have established consensus for not making the = expression sublanguage a pluggable component(*); instead the plan is to = define a single standard one that is part of the standard and build the = grammar around that. Gr=C3=BC=C3=9Fe, Carsten (*) Which to me would mean that you can parse a JSONpath query and hand = over the expressions to an implementation that believes = ++++++++[>++++[>++>+++>+++>+<<<<-]>+>+>->>+[<]<-]>>.>---.+++++++..+++.>>.<= -.<.+++.------.--------.>>+.>++. is a reasonable expression. From nobody Wed Mar 10 08:01:57 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 7BE6B3A122D for ; Wed, 10 Mar 2021 08:01:56 -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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBab2l0Cq5qA for ; Wed, 10 Mar 2021 08:01:54 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (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 723DB3A121E for ; Wed, 10 Mar 2021 08:01:54 -0800 (PST) Received: from [192.168.178.20] ([88.130.51.244]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MyJx6-1leiUk3yfM-00ykjM for ; Wed, 10 Mar 2021 17:01:51 +0100 To: jsonpath@ietf.org References: From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: <106c5cd3-32bc-ffe0-87d2-f8c5ef30c6cc@goessner.net> Date: Wed, 10 Mar 2021 17:01:49 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------97AEBFD56CC85627AD1777B6" X-Provags-ID: V03:K1:z2i5aMyVngL7xMrOibWGXsISmYZ8Z7wYZxxd8dY5n4dH5UTQoCV K1Fq2gni0kK6qNlb1nEP+XO3FQExMxgnycPz4OmosdmFRwR0w1NhH9c42NcCCYsXrhIm81A sVouI97YY4zc5fgq7UpsD55typi/hyj6rg5gyIG2WPBhvOMU4JDHxiaXkGssXRexefY0csG 8x8yQY0EVTPNkzMZBhPVA== X-UI-Out-Filterresults: notjunk:1;V03:K0:EIgjUNdkfv4=:nH2kfQaubsgF6QwqjkoD3F a7Bq4KIErLpOPsq1BX7A//wd98G6iHr+P/izCXYyanpLEQ8fDRGhRaeec02SeG1y32rdTqR8+ 8FfLq2xY/2hpI5N2wJ3LP2498HGUo5dA9oPmsswCF79njlcyoV0BEdeWorfUsi/SZzsHa8S/k K5eYnrdm57GY3DNuKrzN3DeO3+6dyMwb1SuoX8NkxH13lsSmDfvQYWbtTDJHFBJYbOxaS8kfl kYS3Tb3w9SyPedDaNT9ntyWeaiVm+PGZOVIkgw7JhGQcG+c65re7nO3Q4UNTaomWtP4jftMA2 x+fxpnFWhg+H5eQS8rLM+aYKuLnFQWvFHVwxQRc7kq6PRteHzp8Fc4g0izAGuXmK4CqY/574b 0OIQUY7fIxCy64o3Yvj9h40J78MIcMmyiZsmyaipqBDo8qBr80njKQsTQipqXT9nG67ye3g9A uu0O/JAPdg== Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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 Mar 2021 16:01:57 -0000 This is a multi-part message in MIME format. --------------97AEBFD56CC85627AD1777B6 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit .... in #54 I wrote: > The invocation of 'the underlying scripting engine' wasn't meant a serious normative aspect, but rather a quick and dirty solution for JavaScript and PHP implementations at that time. so we should not care about that solution ... Am 10.03.2021 um 16:46 schrieb Daniel P: > On Wed, Mar 10, 2021 at 10:28 AM Carsten Bormann wrote: >> On 2021-03-10, at 16:24, Daniel P wrote: >>> But historically, many JSONPath "grammars" (implied grammars), defined >>> >>> [?()] >>> >>> and treated within parentheses as a single token, to be >>> extracted and handed off to a separate "script engine" to evaluate. >> Why would we want to do that? >> > Don't ask me, I don't know. That question should be asked of people > that want to do that, > if you can find any. One person has written to me privately that they wanted to > do that. > > In my original post, attempting to make a modest contribution to a > discussion about > filter expressions, I simply "remarked" > > "Another issue is whether expression evaluation should be a separate > component, or integrated into the JSONPath grammar proper. My view is > the latter. A number of implementations take that approach." > > which, as far as I can tell, is a true statement. I didn't expect that to be > a controversial statement. > > Daniel > --------------97AEBFD56CC85627AD1777B6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit .... in #54 I wrote:

> The invocation of 'the underlying scripting engine' wasn't meant a serious normative aspect, but rather a quick and dirty solution for JavaScript and PHP implementations at that time.

so we should not care about that solution ...
Am 10.03.2021 um 16:46 schrieb Daniel P:
On Wed, Mar 10, 2021 at 10:28 AM Carsten Bormann <cabo@tzi.org> wrote:

On 2021-03-10, at 16:24, Daniel P <danielaparker@gmail.com> wrote:

But historically, many JSONPath "grammars" (implied grammars), defined

[?(<expr>)]

and treated <expr> within parentheses as a single token, to be
extracted and handed off to a separate "script engine" to evaluate.

Why would we want to do that?


Don't ask me, I don't know. That question should be asked of people
that want to do that,
if you can find any. One person has written to me privately that they wanted to
do that.

In my original post, attempting to make a modest contribution to a
discussion about
filter expressions, I simply "remarked"

"Another issue is whether expression evaluation should be a separate
component, or integrated into the JSONPath grammar proper. My view is
the latter. A number of implementations take that approach."

which, as far as I can tell, is a true statement. I didn't expect that to be
a controversial statement.

Daniel

--------------97AEBFD56CC85627AD1777B6-- From nobody Wed Mar 10 10:30:54 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 952CA3A1542 for ; Wed, 10 Mar 2021 10:30:53 -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 B_5zuVKeL-Pe for ; Wed, 10 Mar 2021 10:30:52 -0800 (PST) Received: from sonic315-13.consmr.mail.bf2.yahoo.com (sonic315-13.consmr.mail.bf2.yahoo.com [74.6.134.123]) (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 0A3C93A1540 for ; Wed, 10 Mar 2021 10:30:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615401051; bh=mlcGrrgVsaljSghUTcZjQfRPH9iFF0HPFrld6kvmmtI=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=d5Wm8vMr6lfQLEVkKYFAHqZz8DJU4ZH6wbrH9ClX+QAjAcWTZW3Y5sU6k7jGrgS6P2xZFHGEqrjQOYUWWTJ0HYnWJGjxLmGmp1aKA6BH9JhsmiL8GeJRnF9cf4nn4eTl44y1VWPBso3QSj6YY3YCo4IEoxxN4RKzCLdSXkujf+vWO7vJq+1kxWvdiXOGe2tSS4AzEYkNX7CxquDYZRo+CJqFTZWGic4djAVysy1y2zEkH3jDvHTGWv+eUwfaj5ME7s3Zm4IhG65gz+lGH+e3aRY2uyO+MvWOFFpP9IdOFDITqyb/APn9Dz99/I7Q7E30yN/mBBSkLcECvYhDOn4tqQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615401051; bh=yy/jhqmSjut0b/7XcLGalDANF2JiiH/O+FEM7r1XfV3=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=CgPYRH8d+aTliFMoR5Y+4aUYzm3D3t+oxQ3ZM2l5PLIiH6biHZM+7Mz7yDCGT2JAUfLy8BFZKVmdMN9VJBpstSNRhEEBHMRya/RSCXO6MBI70on0rlrQaxM0oBhg56drG5wijEYdAhaIP4EoBkhnDiqkOhWcsLRfOD1p4YStxrcmcXsbOVHZUq6uwOmAMmE7HtmT2o4uBmNDIZT9xmRURpjVgxXk1VBv9K27DelrY/ieXKbDnBV7/zF+FERmknOZvQAEI9fzQFG6Ri5geHN4aGPwv4d8OFG+IdmTSdc7V5kjfQrwGFsla1evXzJXnwifTwf37MG0c/N65qRyFGenSQ== X-YMail-OSG: 73.AipkVM1lHheLCosMCYAPSpaytugG.JeblacUf4CJIr8UvJTDSGiRpSsO2A8U bluF_58gMIchij0h9QCGQ46d2.CGhMRhZqjuYWSmId6OsbbTcHp3z_S.U1PismG2q9szUmiEVbR8 EOduc.SrqBKdcZce_tjXEJyvdqmAMa6cwe6fh0JkoGNaNY_2OpQJuEkk28TRdKTy8RjxyuNbWwlR 3wsfncq42vaH0NKZ63wfNgzVd8xUxZUi1BakeZXzVqFKwP3JctRKD7OnAfMzwll3o48k6PPIEel_ EqmAXGfcfCeyaZbvx8wfqEzeYHs5dIFN1g1NgR068kvSMM6JQeRASYwICUNuPxI2BgqnJ7uFwm.s lH6fJBZcChJ2p.I3HNdv7qXl9RhV8ww8F9unxB1JQrbnLW2vCMsEREh8vKUsqdWDSqIKlxWoe7U8 rpUmMBHNsbSBQX7eqUgrWpM6B7alFZDxWmyot1MFEihjXn.4qCq.ZMF_Sbxi3GiWT_EPiBZStNMN 1.gn1YZYnxebMTH4lzeO1dSh.wv3y6IJtMxJlwuYG8FQeywR_D.JE7NDyAQI8swDZqLlPaiwR_9G MEyUbU01tcQdQhFljVcWDl.TnpeunCFb7OA0r4dWUJirKJsz19gO_63byQ30Agm6L_4bQKHQwgLS X7GOJgv32qG5tTj8FjI4esE2kEZyDIcskwxqA4yxE.EeWPktY5ita7BWyat9FgYvQlSe2fvNEEc2 5DXqLtgFEpEds.4VGDwYtZVIjXCaYHT6d4E4g.g8G9QDjvGB.78OFdbWQ058XczxdIPhPpxfbXWF L776fZ7I1JcK6R.wZ86MY8Q_fgBkdwoprsY7ZgoVUu7jnGhhzNkMGZTN9xlLCENgb2zRA392L_o2 FqCG9vVeEJWeXqXYdxqr38BBQ_qGvCXELivzPvWYpLAjvHqIIBmTIX0_L.IGoA7tPRnEeOt8WRXE .54b9ORLdVbxrdeb72lECbRM19Rf.1rda51DZ8qqNJaJRvHcPjRijTAJHiHH1BP2NJtxKeSW4A4w DHLs.4TS_CFFziRmboXZV4RJOmnzINxpgz8PA90CF.o7WH5hO.heUP32b_ZDsIrzzMoVstgGPTWI gR67g0Hh8GGGmzmrqn3gLLsVwKcx9VLXWCSbJtcQkWzKC.c7i7DgAfFeg3oWcDHjQe..3puWN7T6 CGVGqb0MJFsjzza2nEXSk5lJO3iGXvGoIN9vyGDXGnzxbAW4QGGyTVXeGZJfsvafDhCrrbb_GzGQ wqeGHJDedkmmz6ABo.mVl.VKtgrniSati70pzkr6Tbl7gssf6N5cOkxsHlYo3qPTU4U5wi_rgXCc BS2X1ThjfhPMAx5vcJjBMtnoynYbW0fEoXAemaodYj.3iP9TnP5Ta_TKAWeAvXRKWnppO37BvAEz zKmjzk7.bEtjNq1_uKQ1YjDHoeSS9ItYFqeP88mva5_MFZJWgj4hvm45b1fZX8S6soU9Yot1uyIA cE1QAnuv.z_TfZduR5D4pmzSenmSO_ngeoZ7mqsmIWMmyxFUksMDEf0FiARbMtvWHaAg7zBWKxk3 B4oUnFJsx_calXv5nge8wkMU8kPSsz4dGPDYc11TJs92LMNecqFXlkc1jGjcV3RD3YqQa3rGD.eR F5HeSpJnE_1z9X48o4lOy5hx9DlzgZXsIbVI9EamRvh9XyO0faHAJPJC2pdpNvlMrXoLtWuwCaqw u5fXpCT4VXnpSgLSnGU4ypl2eNBLa7ehYzcz389rsTzNkHDH2mcxOty6ptw9Rfr0hF.Q7QUbtQIn m3dqndxdS.RTyJuIYCC7dCMISxZ4brz6nsGbFt2ZyOXIm.dTCLs7I9Ca8XxYBNxvwNr6LHxtkjgC 7cpQZvYxlnuo6fZsSJELk8OzU8YCPCqXkLfhg8qQ_1IxEcZ_LHfZsRLec696Gp3UuI6uw.ixntTg j7jdndMIo1onLiwoE8snxj_g5DM45wK6tY8mytVM95qMGxJNLi9h.vUxk1Zaiz6gtYV8wEi1Nd0k H0STtTFECAK6RgWjt5pxQckIk0.4MvcvH0Gp0H.5h_usEx_H4w99KltBrmniqhXHjJV6sd8W595j bsd2uvt43Y1JApjRI6MhE0JpSO8FVAvhTguIyhgndZGie4WPUePLcvI2_.pmad5Zv.96WeAa1jfW _SlW52CMJtgwdHqA65TsCQd9Q9mFg2EMFV2XNFzePGfTdqlva8m89v_eYhcMUWEVjbfPSTM5ahj9 BF1HmdtDgjANe4Vwr_YmZoxvVa86meGv36COjZ88thCJwi8k9IzYt6e2LuSACtX6pPnCSIf0oVCE hda3CHu0f1tQJOQCq8s9hXlt9IH6FCQp30PBHaA.IMTjjyvlt5wypms31jJT1.C46re0TYnu7.KS Knbpb5VpbkBOGskTPoDvBglsI5LQ_inj_6n6WlrR4IMquFCz.WoElGNiGrRh0L8U.XNtb.h7vbl9 oWApTRh8S001VM5wqvH0mhsS694oh01GVOLRzihddJ.pG3SuNuO0Mp9OTGSUylOQ.xyZKNqY1.FK ZjE_QZqKG7IX8E78tr6negFdNJKH5.M18ecaFarpTEISS8cZ60TLZkABBRIeRbDJPjAkGSQ1i08Z .8kSVYNFZJSs_goHLPVbn725x8wggkaFCHtJ4qoc0m4mI6YxDGSXDzclOjD7LijHEMd1pjClBdO2 o1r1W7M956mTOAAkOR7Fmz5EbOj.9fRCCQ87drixaBmcgxg-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Wed, 10 Mar 2021 18:30:51 +0000 Date: Wed, 10 Mar 2021 18:30:41 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: stefan@goessner.net, =?UTF-8?Q?Stefan_G=C3=B6ssner?= , jsonpath@ietf.org Message-ID: <792165584.902148.1615401041910@mail.yahoo.com> In-Reply-To: <106c5cd3-32bc-ffe0-87d2-f8c5ef30c6cc@goessner.net> References: <106c5cd3-32bc-ffe0-87d2-f8c5ef30c6cc@goessner.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_902147_1669247064.1615401041910" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Expression language -- index expressions and filter expressions 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 Mar 2021 18:30:54 -0000 ------=_Part_902147_1669247064.1615401041910 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I was looking for that... =20 =20 On Thu, 11 Mar 2021 at 5:02 am, Stefan G=C3=B6ssner = wrote: --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_902147_1669247064.1615401041910 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I was looking for that...

On Thu, 11 Mar 2021 at 5:02 am,= Stefan G=C3=B6ssner
<stefan@goessner.net> wrote:
------=_Part_902147_1669247064.1615401041910-- From nobody Wed Mar 10 10:41:51 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 184313A1582 for ; Wed, 10 Mar 2021 10:41:49 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=textuality-com.20150623.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 OCzhWqdgcaMh for ; Wed, 10 Mar 2021 10:41:47 -0800 (PST) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 6608A3A157E for ; Wed, 10 Mar 2021 10:41:47 -0800 (PST) Received: by mail-lf1-x133.google.com with SMTP id d3so35177449lfg.10 for ; Wed, 10 Mar 2021 10:41:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=wknTwqJQJNcWZ4Tk2Ynltn/rS+nvIAM6PB4SXVkmZpo=; b=gUyXd7H4RqlLxo1tBwD4NxYQGWWbYKOG+w6kZq2a0CV/Ho3TvcRQZ2Rq4ddng+qqd1 lWrMR/XKJoQQn2k0tkJsOrWElvaSq1Nm0joA3fwbAU7vqc1fjkl3Z8MC76/DropzaZ59 QPpXRDOtRXYP1pro0Z6L4SBsHS4BThYTsmE6+fE3KB2HDQqeeJVw/V2qUaRLUwackm2g ui1kiVcm4xGcChyMUDhKu5EFeXzmsHdJaiet+2i2xgKpCw08+/coYvfw6pfNMqIVSpqN 6o9GRVqu9yMSFfPg2G3tUahCkA3CYB7qMckViW4fdHiSkS+iSGt179Js1oTvCW4iPy5A HixQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=wknTwqJQJNcWZ4Tk2Ynltn/rS+nvIAM6PB4SXVkmZpo=; b=rs0YU/pSK7dbXxB+q3jFSJ2CutHacY18XoYp1NCgel8HgFYzr6JLn5rfzXHrSq3gZd jcQEeeucrTO4dNQHNyGYx6J4RWPTjUBFhe6rZatyDAnP+6rSCJetzEMglkp2hskjmH3M E0e590UwOD6QCyr1V2dFotmzwnAiEMObT1ofwe9/adi7M7ZQ8fiXPRrI4kJcfy/ca3d3 KQtdU8WJSUfi+Vt/HFKPoMHjfsceq73m5xA+Pz5HpBeH4BB2c99ZznQ/HevuNPNezajm tjjKrEKqEH5FZALYPPPzH8V7wSQsUkVahn+zzd4tP7ilXX6yETT7Ls5Q6Fp5vymp9ZWf 3BFQ== X-Gm-Message-State: AOAM530nEr0ouCUubO/n2KEJcgs/IcPoNl9zgRqacERkFaIeE3vREKP0 Z9QUG3xizmBJ3DOhTjMRWwkZx1XsMPgoVIDcyuh6EbdT6AE= X-Google-Smtp-Source: ABdhPJw4SljQKEe/1G+eHi4HhKBG85Ir+eGuenVyzancGe2cEJQQUf4KMFwMAYijePcxLFK5cBihkUENSBq9jRGxGvw= X-Received: by 2002:a05:6512:2341:: with SMTP id p1mr2851405lfu.192.1615401705639; Wed, 10 Mar 2021 10:41:45 -0800 (PST) MIME-Version: 1.0 From: Tim Bray Date: Wed, 10 Mar 2021 10:41:34 -0800 Message-ID: To: Murray Kucherawy , Francesca Palombini , jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000d5af0605bd3304c6" Archived-At: Subject: [Jsonpath] Apologies, and an interim meeting X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2021 18:41:49 -0000 --000000000000d5af0605bd3304c6 Content-Type: text/plain; charset="UTF-8" My abject apologies for missing our meeting earlier today. My excuse - an off-by-N fat-fingered calendar - is entirely lame. Just to be clear, I remain committed to this WG and do intend to pitch in actively as we move this forward and help us deliver a badly-needed stable spec for JSONPath. Once again, sorry. Thanks to James and Carsten and the others who rallied around and conducted what seems to have been a useful meeting. It seems pretty clear that we should have an interim meeting before the next IETF. James suggested early May and that sounds about right to me. I'll organize a Doodle, but I'll try to harvest a bit of information first to increase the likelihood of success. I suggest something between Wed 5th May and Wed 12th May inclusive. Could people who'd want to come please reply to this with: - (optionally) reasons to look at another date range - their time zone Thanks in advance! That'll help me pull together a useful Doodle that tries to maximize attendance and minimize pain. --000000000000d5af0605bd3304c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My = abject apologies for missing our meeting earlier today.=C2=A0 My excuse - a= n off-by-N fat-fingered calendar - is entirely lame. Just to be clear, I re= main committed to this WG and=C2=A0do intend to pitch in actively as we mov= e this forward and help us deliver a badly-needed stable spec for JSONPath.= =C2=A0 Once again, sorry.

Thanks to James and Carsten and the others who rallied around=C2=A0and con= ducted what seems to have been a useful meeting.

It seems pretty clear that we should have an interi= m meeting before the next IETF. =C2=A0 James suggested early May and that s= ounds about right to me.=C2=A0

I'll organize a Doodle, but I'll try to harvest a bit of info= rmation first to increase the likelihood of success. I suggest something be= tween Wed 5th May and Wed 12th May inclusive.=C2=A0

Could people who'd want to come please reply= to this with:
=
- (optiona= lly) reasons to look at another date range
- their time zone

Thanks in advance! That'll help me pull together a= useful Doodle that tries to maximize attendance and minimize pain.

--000000000000d5af0605bd3304c6-- From nobody Wed Mar 10 10:47:46 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 8B72F3A158F for ; Wed, 10 Mar 2021 10:47:44 -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_DNSWL_NONE=-0.0001, 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 hbUmj_Dd2VyU for ; Wed, 10 Mar 2021 10:47:42 -0800 (PST) Received: from sonic314-14.consmr.mail.bf2.yahoo.com (sonic314-14.consmr.mail.bf2.yahoo.com [74.6.132.124]) (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 3F5DD3A158D for ; Wed, 10 Mar 2021 10:47:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615402061; bh=dNsFzXsP6vWrVST9XgC7dDsFcqsXpUlo+XJt2p9aYnE=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=l4h5z8CSQJKENI3eM16D0qTEcm3IGQnFEZKzmGwKFzx0+lr6dWExBLkL/yJHHvEGj5Y+Zm9nX5yCDn9LW4cv/xHp6IqmPK0S8n3A9iMtIddtxu1bATGkjhY8Edp7ueNjvxvVq1j8SP95KYfrKUZ4g4BllC4A3/duxflvb3/Ilz0bcFZbbwLjajKApA23j0IWSO/1vOeYAdhY0VlOyNXFIyG6/MkPtY8yu9Re621BO4II3Q0GNPtL5U1zNaunQ0SHFntdOc4svrggjDxyVu6B0UPWOUBqITXN1KZn+an9spAsSnepDDivjQeLLuZt76sW16wiCxsP58LUSM2HIcA6TA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1615402061; bh=i0g+XXyd/Vq/CZDoJr1hbQ5X4mfZy7NyA0lGpl/jAi7=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=VfMIsqL8/z0p69XvPrvcxqP+og6+p41Q2NhpX2PTug4JfxbEqW1V3W7SaMq7gpaqFqORdXyGNB6RnswQ0nhl/+I8SSkx39XVcYCBN3+D42/ddqSMcs4RhzYRanmzAVRNhLwaAU/cpUTBr/CQ64OfiP/csie7Mf7OIlv7dH+Qoodb7Aed01wyv3CzpkPD8JoTcUXk4AJomY81Vbdk3pI5d8dQIYliHtngqDGqXcVgF2XMuCMe1sLHzP1PzfWP+NsHOh6QtpklwDLYJXwlapOFTiYw4rGsBFGSNgdwy8zcJy2GoBFxgxpPzCO9yPq+MDBg+bn7KTdJrLMRlYoIJ/O1OA== X-YMail-OSG: EoERiQUVM1msDP991OP_1QETRDFD2sP5CPvkuXDj9cSkAeoP9O4QaaML7jsvO9n q0kVJ9ckggSVK30HfL4dTdqSQgrbjf8_frnEQlrbCK6KdQy.rB4QybTm56iUoVE509dWU.wLe.1o KD6RO9IoB5UEnoTciY_56iFRXd9BWFpfvWmhCV_9IidSLvTudf7p_iwI8YUw7KVnEBzF1pdaftlj s50NSRP2VHswFrJ7RmDlyNQC2tNzcZhr5pQ9UwBMT0A.7nfpdTSGOufM1jebLjNsTqbIBqa72ECJ t9tmAHSfQpJND1XmQtiwJmvQg3HvF2BGLzaxj8lODGRW3BlziP5UI6b8EZRDLUGKaYrABoEzyW.F V0_E3yI6u193EruL5NtqOEw8nJ79MVu46m5zj0Kmxy_9611opVZ46Y1kJaPrXDG_5ocYG4n0PiJf ojWSR7Gumo4i4eiuqHMS8x3jw.VS8gA_H3jOO9k2gy6ZNPPbua_hYOdVZzDtPKm3KoqsfdwBLbHV H1jq_eLJ93KTgRsX.l_9J2mogaQEVltzKcQauQbreYOOgAcmW3H.X1zq5OYAoSOqFaTLYU5Yvylq OxT_NUTO1Fmy_cQwxxgZZqJ2A68JihhZsQngEXntGFkueL5ZLOZBf06MPpk5Xl_rZpGnT1yy07x1 P44JUH7WQIHjG_VS_IIVSZI.C1TldHlJq9I2U_t2RMDovDQ9BWLrDwLrudT94bINHAt_CwJq0ruo GFbrbjEj0f_atvPLSVSJ7jbPxr6JIE7JdiSyonj1qLyut69wc7eQ9RnxMj7kdLb5zSSsbUq3p5EA h6n_NyHjdLFGzGtEWTDC2QjIWZA8pbJpAtLx_QGFWHHfhCDBpOC.KtUWZY1Q4.IO2Uxsd4DLjyMg lKdkpeipkS0APnl0cmFYW1zJ_zkz8cBMFT5Q1wMgh2u101zuZZumwfp6Qz0nleoQMTKJ9332M7ES vBaejVKXb3_sdWWwCqA8Jw3vx1JYKR1mGYSZKahgNQjg_xDCK36scuneLkUT9nhfOyNPOBEjHs65 e4iVFewsewnOy.Lc3r6qn4RYVjw5mNODLZCmAkEx5G40JaRarrsVx8k8FrmIqXJzKhXKnNAApMnn FbNKH.uoFwkzXy2Ib2k4bhb6CpzNM3jLGi9p_J_pxlygpt1fM04dmVxy2PIaKmUZaikmipyZkdKX Qoa8Xe8dTsLdWwOWIvXQAJmpnstsoQqFfasNkBXesDecQZkWpo62h_Jx_EV3U.nv6aSFN1BLmpvl mnmlK.H388MWRNER1o57pNX42GgMBsQsNDN7jQt8cxRQa6Mlrg5KQgdbUTwxXqgfBychHUBK.X0A 9jQXzvWvlAIxEdwqRTDoLOhfH_KIKmZulM6qD0xcR_XMTa7vyRsDRiSXJOskoPUZI5moRuAGMYoo yBMAhU2ScAGGQmVZRZhJiLkqqnGgYBq1v.ggKYef3lXkXkTprkw4cgsUIAerbLI8RGtY.FLA5IAz bxet_MQ.yk8cmqqSVb9fI8VJ7l1v5MVBZ7bqBq1P1OsefAfTJw6YmaZ9AHunb_Zi..Tu0GWLFHvQ sdUj43yKMGgTNmGD.WxLdBqlV4azOaeJtecc91xznvhwsaSyvGqjyAnLH84aZKqojECFb6qB_nJW sxRSP0nDNbtBn77EWdFS7W2GpYt7aSPYUhPPfylI3M7.aHbT6oMnSbADK_cF6prDUjVD5JHsdxzA pHIvHW5ChKSDvB_oF.Tszs2TkgI8ow7AknF1abQ9.ATMJvMTTVcVruD546ZFZRTYgGq1LWJW9wBt yMWZm.PRAT6TbN2_4Ew7YYOKt1OEEHiHmyk8qyImNweIbLolAlUQ95IcEsqkNcVbVHAJaDAIxXs8 m8LShgltn7u1HmeHq2WhJ7c1w6_ui_uIoECMDqj7HP8nXeImm17ZUWogtKeiYZovrmi7Jeyn.yH. 4JtPQgdP2lFjcoUeyQBSGjSE._gI7HB9.wETvKbtlwGz90Dyuip2UMXWqiRZu4X7oneIJkWzHz7x QAUmluRg.OmBDN_II3KaYj6OymMigytoOmdyZQjBra6m0owLjCR2xIjIO55MHtRd4ItONW_YaiZz lYB.b_BS5KSap.WoqBixO10rUMSaJ9I0CB.COYERcXDRlSH5d5WyYKeSF82tDQ1_rX2KepCrvDpn XjP_M1zSrYi4QaJPsvfU2W0B5Ejm9MUpMOrE0yR1qsfGeP687I9XV70x6EYNBVP6zgLY5QLnwYDp pCsP80o1aqoALXf2e6RCcn204.ZIuqBrlOfQVy0S2pC4lTKgpSYI_SrXKWHxyhaYYAMAgmQw1DKk ieFEXJ8f9Doze.bVXET3VeRVOz1V0KFNHNGM.Cn_wmwop0L_UqtJeqJYoCDAv2qJhJl0baa1TyYV HSK_NqmeSYRE3ap9YO1la9ghe2Ab0gYNcsQnqN3z71WHMqJhOo7Z2k3pzJbxcEpC36UvXPbhur7g OfRUauJo3WYvz3luiEmDVWI8SkGyQX7Gz6nd7qiI1_ATeS0aFxtccLcDzrM8aSH3DCyr4AgCviwe 73Quuvwvy2Oqe.bVDoiaXh_sikqBAc66jbmGAyZYWqseRKtFd2WBhgNkx6_IAPUznjewO2nKU_Do 9Cf2Dwlqu3S9Z5LjbcupEHbpE99lxvfzgcEwa8ch_RmT5HK2bB.qZgDBlYCoWPytbg0qURV7MsEz MK9Nmh2QfC3yJCzCWGefnkjw8c91uzFCe0duQvWh.rE_dz8lZ5sf_FBUcCL322O5AxQVGpGx5RXS 2MulgZYTpcnW0Pmnj6kSAO3J0hzMI6nje9WmKFxI- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.bf2.yahoo.com with HTTP; Wed, 10 Mar 2021 18:47:41 +0000 Date: Wed, 10 Mar 2021 18:47:32 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: Tim Bray , Murray Kucherawy , Francesca Palombini , Message-ID: <547949686.1041453.1615402052400@mail.yahoo.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1041452_576351168.1615402052399" X-Mailer: WebService/1.1.17872 YahooMailAndroidMobile YMobile/1.0 (com.yahoo.mobile.client.android.mail/6.20.3; Android/10; QKQ1.190716.003; OnePlus6; OnePlus; ONEPLUS A6003; 5.87; 2087x1080; ) Archived-At: Subject: Re: [Jsonpath] Apologies, and an interim meeting X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2021 18:47:45 -0000 ------=_Part_1041452_576351168.1615402052399 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yeah, I got the reminder from my calendar as I was going to bed... The meet= ing started at 1AM here. I'm in NZ, but I'd at least like to listen in.=C2=A0 Was this meeting recor= ded, and it's it available for viewing/listening? Greg =20 =20 On Thu, 11 Mar 2021 at 7:41 am, Tim Bray wrote: M= y abject apologies for missing our meeting earlier today.=C2=A0 My excuse -= an off-by-N fat-fingered calendar - is entirely lame. Just to be clear, I = remain committed to this WG and=C2=A0do intend to pitch in actively as we m= ove this forward and help us deliver a badly-needed stable spec for JSONPat= h.=C2=A0 Once again, sorry. Thanks to James and Carsten and the others who rallied around=C2=A0and cond= ucted what seems to have been a useful meeting. It seems pretty clear that we should have an interim meeting before the nex= t IETF. =C2=A0 James suggested early May and that sounds about right to me.= =C2=A0 I'll organize a Doodle, but I'll try to harvest a bit of information first = to increase the likelihood of success. I suggest something between Wed 5th = May and Wed 12th May inclusive.=C2=A0 Could people who'd want to come please reply to this with: - (optionally) reasons to look at another date range- their time zone Thanks in advance! That'll help me pull together a useful Doodle that tries= to maximize attendance and minimize pain. --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_1041452_576351168.1615402052399 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yeah, I got the reminder from my calendar as I was going to bed... The meet= ing started at 1AM here.

I'm in NZ,= but I'd at least like to listen in.  Was this meeting recorded, and i= t's it available for viewing/listening?

Greg

On Thu, 11 Mar 2021 at 7:41 am, Tim Bray<= /div>
<tbray@textuality.com> wrote:
=
My abject apologies for missing our m= eeting earlier today.  My excuse - an off-by-N fat-fingered calendar -= is entirely lame. Just to be clear, I remain committed to this WG and = ;do intend to pitch in actively as we move this forward and help us deliver= a badly-needed stable spec for JSONPath.  Once again, sorry.

Thank= s to James and Carsten and the others who rallied around and conducted= what seems to have been a useful meeting.

It seems pretty clear that we= should have an interim meeting before the next IETF.   James suggeste= d early May and that sounds about right to me. 

I'll organize a Doo= dle, but I'll try to harvest a bit of information first to increase the lik= elihood of success. I suggest something between Wed 5th May and Wed 12th Ma= y inclusive. 

Could people who'd want to come please reply to this = with:

- (optionally) reasons to look at another date range
- their time z= one

Thanks in advance! That'll help me pull together a useful Doodle tha= t tries to maximize attendance and minimize pain.

--
Jsonpath mailing list
Jsonpath@ietf.org
https://www= .ietf.org/mailman/listinfo/jsonpath
------=_Part_1041452_576351168.1615402052399-- From nobody Wed Mar 10 10:50:50 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 DDED13A1598 for ; Wed, 10 Mar 2021 10:50:47 -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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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 Ox5a-te7Wlsv for ; Wed, 10 Mar 2021 10:50:46 -0800 (PST) Received: from mail-ej1-x62e.google.com (mail-ej1-x62e.google.com [IPv6:2a00:1450:4864:20::62e]) (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 DAD363A1594 for ; Wed, 10 Mar 2021 10:50:45 -0800 (PST) Received: by mail-ej1-x62e.google.com with SMTP id c10so40743463ejx.9 for ; Wed, 10 Mar 2021 10:50:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=JJwXEv2diD/n1LaAiMqFFIJGrYPmpGqR8ple1o4aQKM=; b=AMCs4XRfIauw23QpPjIHOSNrR1oLT0nHUH3QP9VgLY+cRpdirm6mN6Munku1l3oiSO O7i0V3nhRYq1znldXNLEuaDfGV12YZt6/ydDLTVeuaZgzkawMR1LHfGPhcx0a5tHSPKL B/aoIrRiI3qfDEs3q9H+IY0+Gc1JC2yxa/63QEYdcCU9bR5DEuCNKQgUz/9mGyAVtPFd sIqKlTeLtYx6poJKCGyWeIiFB7nPaHT7zNrWYsn0QaVF58iEXGi/HKcqM9ooqvcOUcRs NLLS16YduDZ8tpRWnwnHz0hdf9lsG8vC+PcKPE46E/xv1/ldrEZPey2Mb0zgb/rsz5yr /izA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=JJwXEv2diD/n1LaAiMqFFIJGrYPmpGqR8ple1o4aQKM=; b=Hx+7f1Z9L2v6FqjJF6NBNFOkcrnrLnvj31PgLvt1HR5QDnr1D+2PmOcLbhQe11I9dQ i95R+GfRHF7+suA4SNMaV9n4tzR5WpBl/DpCNycqgZqCZ/jUV/piNslsv7sEl3NE+nYZ hcnx2pszoOx7tkEADRx6+2RbT/BW4fbOkAaaptXwnA3A8g8NYKGAiJrS5CSZ2nU5aUyN +UqHtFxOrsTL3PA53XCcwAzuxpJOE2wPWUiIsWHQpAx4vwmAkUpqUvkoBISgiEl/RHt3 uJ/u7bSiFWpSa8oWw4tP/uB4GygHiepvVqjfK2BrwIuVXrQNZsj4Z0wNcw6Eqp7TthTy blPg== X-Gm-Message-State: AOAM533Is9KMuIoqOskdmlD8ObxezjpvMBUdcnWFhxmkshUoin7D2BQF G/1iZPWQDefXkRl6A4Tl4+LM1wZNViX/5w== X-Google-Smtp-Source: ABdhPJzixIvNSCld+uRMQLQaB3/IhnNHLepcOW1H1a/NiyhCblP0yUfSZwbydm4VCirUMMQu74X87g== X-Received: by 2002:a17:906:7c43:: with SMTP id g3mr5110379ejp.210.1615402239244; Wed, 10 Mar 2021 10:50:39 -0800 (PST) Received: from ?IPv6:2001:984:65b0:2:40ee:6e:823:c40a? ([2001:984:65b0:2:40ee:6e:823:c40a]) by smtp.gmail.com with ESMTPSA id b4sm74423edh.40.2021.03.10.10.50.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Mar 2021 10:50:38 -0800 (PST) To: Greg Dennis , Tim Bray , jsonpath@ietf.org References: <547949686.1041453.1615402052400@mail.yahoo.com> From: James Message-ID: <29efb1ef-bae5-4240-a184-d2426d399c61@gmail.com> Date: Wed, 10 Mar 2021 19:50:38 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <547949686.1041453.1615402052400@mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------22650029A0C501CC796C34F6" Content-Language: en-AU Archived-At: Subject: Re: [Jsonpath] Apologies, and an interim meeting X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2021 18:50:48 -0000 This is a multi-part message in MIME format. --------------22650029A0C501CC796C34F6 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit The recording is available on Youtube https://www.youtube.com/watch?v=DVhizaHGX_8 here. - J On 10-03-2021 19:47, Greg Dennis wrote: > Yeah, I got the reminder from my calendar as I was going to bed... The > meeting started at 1AM here. > > I'm in NZ, but I'd at least like to listen in.  Was this meeting > recorded, and it's it available for viewing/listening? > > Greg > > On Thu, 11 Mar 2021 at 7:41 am, Tim Bray > wrote: > My abject apologies for missing our meeting earlier today.  My > excuse - an off-by-N fat-fingered calendar - is entirely lame. > Just to be clear, I remain committed to this WG and do intend to > pitch in actively as we move this forward and help us deliver a > badly-needed stable spec for JSONPath.  Once again, sorry. > > Thanks to James and Carsten and the others who rallied around and > conducted what seems to have been a useful meeting. > > It seems pretty clear that we should have an interim meeting > before the next IETF. James suggested early May and that sounds > about right to me. > > I'll organize a Doodle, but I'll try to harvest a bit of > information first to increase the likelihood of success. I suggest > something between Wed 5th May and Wed 12th May inclusive. > > Could people who'd want to come please reply to this with: > > - (optionally) reasons to look at another date range > - their time zone > > Thanks in advance! That'll help me pull together a useful Doodle > that tries to maximize attendance and minimize pain. > > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > > > --------------22650029A0C501CC796C34F6 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

The recording is available on Youtube https://www.youtube.com/watch?v=DVhizaHGX_8 here.

- J

On 10-03-2021 19:47, Greg Dennis wrote:
Yeah, I got the reminder from my calendar as I was going to bed... The meeting started at 1AM here.

I'm in NZ, but I'd at least like to listen in.  Was this meeting recorded, and it's it available for viewing/listening?

Greg

On Thu, 11 Mar 2021 at 7:41 am, Tim Bray
My abject apologies for missing our meeting earlier today.  My excuse - an off-by-N fat-fingered calendar - is entirely lame. Just to be clear, I remain committed to this WG and do intend to pitch in actively as we move this forward and help us deliver a badly-needed stable spec for JSONPath.  Once again, sorry.

Thanks to James and Carsten and the others who rallied around and conducted what seems to have been a useful meeting.

It seems pretty clear that we should have an interim meeting before the next IETF.   James suggested early May and that sounds about right to me. 

I'll organize a Doodle, but I'll try to harvest a bit of information first to increase the likelihood of success. I suggest something between Wed 5th May and Wed 12th May inclusive. 

Could people who'd want to come please reply to this with:

- (optionally) reasons to look at another date range
- their time zone

Thanks in advance! That'll help me pull together a useful Doodle that tries to maximize attendance and minimize pain.

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

--------------22650029A0C501CC796C34F6-- From nobody Thu Mar 11 02:55: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 769B23A18EB for ; Thu, 11 Mar 2021 02:55:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j5RvcNnKH2CJ for ; Thu, 11 Mar 2021 02:55:10 -0800 (PST) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (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 2F2803A18EA for ; Thu, 11 Mar 2021 02:55:09 -0800 (PST) Received: from [192.168.178.20] ([88.130.51.172]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MSLEm-1l9DAx2kum-00ScGR for ; Thu, 11 Mar 2021 11:55:07 +0100 To: jsonpath@ietf.org References: <547949686.1041453.1615402052400@mail.yahoo.com> <29efb1ef-bae5-4240-a184-d2426d399c61@gmail.com> From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: Date: Thu, 11 Mar 2021 11:55:08 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <29efb1ef-bae5-4240-a184-d2426d399c61@gmail.com> Content-Type: multipart/alternative; boundary="------------278331313E141CA42E3C7A2E" X-Provags-ID: V03:K1:MjooQMCpNu15hcKAHEownmAXVKxSC7IoFPQtRhUmvWvCtDD30dc SV+Fb2HeE+EC/H5eax0RMPZY9XS09xgU7TyESvtuQW8yjatKB5Yr1NkuWi5uYf3t1iCXdIF IipyryYN1sOieLPkFE/vnPkWK1LPSdG0BPHXw4+Ltto+AEvUAWCV3NGWUcpVU98/gFFzBqq J6ve2B7UElxypEsJvm+iQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:/MtAXSmmS3g=:yBLJtOAJaRfCW87KUNoYzm EzorhEtXrc32jUIaiVmrUwxSHPJvIaSG0dVFwDaqyHhc5950drt7g5zFhxgHCRqdNaMS1Ay13 MVkP8HbPteXSK99Ai8L1oPwXZBpod7rz8FmTZB6+zYN1YgFekIgH83R8w8XGeWq2PyU5m1uBR C7kv5LzYxjBzJiyx9AOfFWpwjSU0kco2zcHFTrAkJ4OGz3n7LypNAA4m4T5o9406nk81tMpZG MMAG8AopQ7ihcMDIntO7ogBoHMIng2RVymUOZ4/xQq7Ln2lKFKTJGSBr/n82bo7/ScVe8hjRn +7BhewKlP5SzUC0SCNHkR/2R5rEpCZcS46+QLcqLOZsBw2FMYihglKN6x9aBTuT05PQRRLV2B zDWaEcsBdAK1bbypPved6e5pXbZ3h/YrMhktfz50/eq8Bk5be3r0pCeb+J7stSLbRRRWawKqZ LwhYMNDowQ== Archived-At: Subject: Re: [Jsonpath] Apologies, and an interim meeting X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2021 10:55:13 -0000 This is a multi-part message in MIME format. --------------278331313E141CA42E3C7A2E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit ... very interesting recording ... next time I need to attend as a tourist ... Am 10.03.2021 um 19:50 schrieb James: > > The recording is available on Youtube > https://www.youtube.com/watch?v=DVhizaHGX_8 here. > > - J > > On 10-03-2021 19:47, Greg Dennis wrote: >> Yeah, I got the reminder from my calendar as I was going to bed... >> The meeting started at 1AM here. >> >> I'm in NZ, but I'd at least like to listen in.  Was this meeting >> recorded, and it's it available for viewing/listening? >> >> Greg >> >> On Thu, 11 Mar 2021 at 7:41 am, Tim Bray >> wrote: >> My abject apologies for missing our meeting earlier today.  My >> excuse - an off-by-N fat-fingered calendar - is entirely lame. >> Just to be clear, I remain committed to this WG and do intend to >> pitch in actively as we move this forward and help us deliver a >> badly-needed stable spec for JSONPath.  Once again, sorry. >> >> Thanks to James and Carsten and the others who rallied around and >> conducted what seems to have been a useful meeting. >> >> It seems pretty clear that we should have an interim meeting >> before the next IETF.   James suggested early May and that sounds >> about right to me. >> >> I'll organize a Doodle, but I'll try to harvest a bit of >> information first to increase the likelihood of success. I >> suggest something between Wed 5th May and Wed 12th May inclusive. >> >> Could people who'd want to come please reply to this with: >> >> - (optionally) reasons to look at another date range >> - their time zone >> >> Thanks in advance! That'll help me pull together a useful Doodle >> that tries to maximize attendance and minimize pain. >> >> -- >> Jsonpath mailing list >> Jsonpath@ietf.org >> https://www.ietf.org/mailman/listinfo/jsonpath >> >> >> > > > Virenfrei. www.avg.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > --------------278331313E141CA42E3C7A2E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit ... very interesting recording ... next time I need to attend as a tourist ...

Am 10.03.2021 um 19:50 schrieb James:

The recording is available on Youtube https://www.youtube.com/watch?v=DVhizaHGX_8 here.

- J

On 10-03-2021 19:47, Greg Dennis wrote:
Yeah, I got the reminder from my calendar as I was going to bed... The meeting started at 1AM here.

I'm in NZ, but I'd at least like to listen in.  Was this meeting recorded, and it's it available for viewing/listening?

Greg

On Thu, 11 Mar 2021 at 7:41 am, Tim Bray
My abject apologies for missing our meeting earlier today.  My excuse - an off-by-N fat-fingered calendar - is entirely lame. Just to be clear, I remain committed to this WG and do intend to pitch in actively as we move this forward and help us deliver a badly-needed stable spec for JSONPath.  Once again, sorry.

Thanks to James and Carsten and the others who rallied around and conducted what seems to have been a useful meeting.

It seems pretty clear that we should have an interim meeting before the next IETF.   James suggested early May and that sounds about right to me. 

I'll organize a Doodle, but I'll try to harvest a bit of information first to increase the likelihood of success. I suggest something between Wed 5th May and Wed 12th May inclusive. 

Could people who'd want to come please reply to this with:

- (optionally) reasons to look at another date range
- their time zone

Thanks in advance! That'll help me pull together a useful Doodle that tries to maximize attendance and minimize pain.

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


Virenfrei. www.avg.com


--------------278331313E141CA42E3C7A2E-- From nobody Sat Mar 13 03:58:23 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 DB5823A0936 for ; Sat, 13 Mar 2021 03:58:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.099 X-Spam-Level: X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, 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=ispirata.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 FoABG8ZSaTev for ; Sat, 13 Mar 2021 03:58:21 -0800 (PST) Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 1AE533A0934 for ; Sat, 13 Mar 2021 03:58:21 -0800 (PST) Received: by mail-wm1-x332.google.com with SMTP id r15-20020a05600c35cfb029010e639ca09eso17343888wmq.1 for ; Sat, 13 Mar 2021 03:58:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ispirata.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Z35VuAALxJU0Cjnpn/OgyM+w0ehMuZqEJwPTuWP51KA=; b=pi/xhgkGZ76mWa5qacQB4Iek0dHSDqRMxf1gtvUG0jwbF8b4F5UzRchRSLmsomEToU CF0XVFo2AOtJvoSccHpZIkOu0zQ9PqoHgY04eXxBVevMolDGfr5tQaS/q4GDbl8zwq3W gAaJH7M9vYGreDdFggrMKDGiLaqpy9FVOPv+QKO4cSCIj2lbVyuTj3uk0fp/gY7DHeXI 88FCWOXqxD0CnDCYXvIFnZpLSbKIZ9gBkV9X0FXA7wh98nDqgURcM35c8iKilHhDajQQ imETShAaduzBT/f3NolxoBxaFjt3RUlYvPxpj+47B4BDu1lYO8D49a5qo92DEpWgaC+7 6O4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Z35VuAALxJU0Cjnpn/OgyM+w0ehMuZqEJwPTuWP51KA=; b=lWNs6Kt0clkOkCdRXVmr9KULR9T3idxV5nF5FZlLc16XDIjXuP3ZE0IVN5DffJHr64 piQSr+dz+kFm1W0sZLBZK772wYrDWd/iqLjhwz3IFijKsxHMt/L7A9+vKC4RiyMIz6MR mXbE9XjQRblIGKC4mt2rF774nVs3BfIrTKDSHUZ+E/gr0FEkPojg5vrtRkzACksTVXPN Mlt36HCbi7oVUdkVKaNy2kKAums2OBibuyLuqd7+B33pvu9MG6ZpUBBkZpu7a8svazTO 7wZpFFjSLGYhXF6QNf4/7lcEUt0azxGMwQOpoLWbUnU3+E3dnnZzr4cmYUlS52t1bREf y6dA== X-Gm-Message-State: AOAM531uSepCK3OZj76ko6oS+y17lyooRooJ08dv7jJj8bV74rnoPVQB y46cBzd7W+PYlA1hSvdE08HoulXYJ/K0R558npeqfA== X-Google-Smtp-Source: ABdhPJy3/2xdATUw7d5WbBvRzuF7qFfrHBNHAKpeWSuPFhgQnlfdHnzkra08lk3BuHrHT7VH4IAyICbzDkaZPmBr5WI= X-Received: by 2002:a1c:bad6:: with SMTP id k205mr17048477wmf.16.1615636698718; Sat, 13 Mar 2021 03:58:18 -0800 (PST) MIME-Version: 1.0 References: <75DBBA4A-42F9-47E9-B0E6-ED84F09D434F@tzi.org> In-Reply-To: From: Davide Bettio Date: Sat, 13 Mar 2021 12:57:43 +0100 Message-ID: To: Glyn Normington Cc: Carsten Bormann , jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] Absolute ($.foo) and relative JSONPaths semantics 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: Sat, 13 Mar 2021 11:58:23 -0000 Hello, Greg Dennis made a really good synthesis on this topic: https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/59#issuecomment-797212814 Please, take a look at it and let me know what you think. Regards, Davide Bettio. Il giorno mar 9 mar 2021 alle ore 16:25 Davide Bettio ha scritto: > > Hello, > > I opened an issue on this topic: > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/59 > > To be honest I am still of the opinion that omitting $ is the right > approach for relative JSONPaths, which is a similar approach to XPath > relative paths (which they don't start with /). > > Anyway the most important thing for me is to reach a consensus on the > idea of supporting relative paths (to the current context) with some > kind of syntax. > > Regards, > Davide Bettio. > > Il giorno ven 5 mar 2021 alle ore 20:15 Glyn Normington > ha scritto: > > > > In filter expressions, I think paths should start with @ or $. If we allow one of these to be elided, then the user has to remember which one can be elided. > > > > I'm sympathetic to optionally omitting the initial $ of a JSONPath expression because this is unambiguous, but I would be happy with $ being mandatory since this is consistent with the above rule for filter expressions. > > > > On Fri, 5 Mar 2021, 09:59 Davide Bettio, wrote: > >> > >> Hello, > >> > >> > Well, JSONpath is a bit like XPath, and a lot less like XSLT. > >> > >> I'm aware of this and I also agree, however I still need to understand > >> if we may support any kind of semantic for accessing any current > >> item/current context rather than the root item (which is identified by > >> $), which are the points 1 and 2 of my previous mail. > >> > >> On 2021-03-04, at 17:20, Davide Bettio wrote: > >> > So I think that the following 2 points need to be addressed: > >> > 1. Do we want to allow any kind of reference to any current > >> > context/current item with a standard (or prefered) approach (such as > >> > the mentioned relative JSONPath)? > >> > 2. Do we want to use paths without starting '$' or the '@' for this > >> > kind of purpose? > >> > >> Clearly I don't need to discuss any templating language at the moment > >> here, but I brought it as a practical example which is useful to > >> explain why I need to understand if we are going to support relative > >> JSON Paths. > >> > >> Furthermore I'd like to understand what kind of opinion people have on > >> paths that are not starting with $. > >> > >> Regards, > >> Davide Bettio. > >> > >> -- > >> Jsonpath mailing list > >> Jsonpath@ietf.org > >> https://www.ietf.org/mailman/listinfo/jsonpath From nobody Sat Mar 13 05:53: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 C336C3A0E81 for ; Sat, 13 Mar 2021 05:52:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.92 X-Spam-Level: X-Spam-Status: No, score=-1.92 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] 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 Pt5GoBOKINId for ; Sat, 13 Mar 2021 05:52:56 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BA9C3A0E88 for ; Sat, 13 Mar 2021 05:52:56 -0800 (PST) Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DyPJj6NYFzySC; Sat, 13 Mar 2021 14:52:53 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 637336373.493801-4d477c41b6ebbaae2015d2410a0828a3 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Sat, 13 Mar 2021 14:52:53 +0100 Message-Id: <707BC74F-2596-461E-AF9A-D1BB1147B80A@tzi.org> To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Jsonpath] Issue 60: Determinism 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: Sat, 13 Mar 2021 13:53:00 -0000 I think the summary so far is * We recognize that there are operations in JSONPath whose result is = ordered but that order needs to be created based on unordered input. * We are not going to cut off these noses to spite our face. * We have a choice between imposing a language-defined order (e.g., = sorting) or leaving the result non-deterministic. I gather that there is a general direction toward non-determinism, as = imposing an order would be too expensive, but I'm not sure we have a = conclusion here. Gr=C3=BC=C3=9Fe, Carsten From nobody Sat Mar 13 05:59:48 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 A20033A0EBD for ; Sat, 13 Mar 2021 05:59:46 -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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 ZpXBVlGv3NTw for ; Sat, 13 Mar 2021 05:59:44 -0800 (PST) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48DEE3A0EBA for ; Sat, 13 Mar 2021 05:59:44 -0800 (PST) Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DyPSZ5fsZzyTl; Sat, 13 Mar 2021 14:59:42 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 637336782.387697-1f4261b767b950d72b81c316a840c556 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Sat, 13 Mar 2021 14:59:42 +0100 Message-Id: To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Jsonpath] PR #72: Terminology 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: Sat, 13 Mar 2021 13:59:47 -0000 I created a PR from the terminology discussion so we have something = concrete to discuss. https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/72 Comments (there or here) welcome. Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Mar 15 15:41:45 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 177F23A118C for ; Mon, 15 Mar 2021 15:41:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.498 X-Spam-Level: X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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.20150623.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 wrA5nUcNy17f for ; Mon, 15 Mar 2021 15:41:42 -0700 (PDT) Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 6A1D53A1190 for ; Mon, 15 Mar 2021 15:41:42 -0700 (PDT) Received: by mail-lf1-x136.google.com with SMTP id x4so52703240lfu.7 for ; Mon, 15 Mar 2021 15:41:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=Xa7ddbj64WXxTNMkot8LejxmTn4o63GNUdkYUGVujJ0=; b=ZtdK86pP2zKI9vrMur12XubcN7PRMKrfTwa8kUL/Wev0gRtzuQqbJyn64lVawEPRkY bzYpIPaDs1rTPCGntmKmKiSrTAUfuMpzKoE8l4iYE3FxbcK+dun0RVhpECrYywrNQyNm LtOYr14ornOAjHvX/fJgKjdncIGVf5Ku6t2MJEUI70gIXqbTJchwfi1CzacPzGEfqYEO Js9Buv7Nc7LDqodvW/UdLYHufcwlpoM9eUHoxWm3moeTwW0jDOP9+dmTRew94FMEHsEw 6sXgxK/lLRPimsnrcsLF1D28Ty1oP3M4z7unPBRj0Jyn5H6FISLmML4LhJYt+7cuTyU2 UkKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Xa7ddbj64WXxTNMkot8LejxmTn4o63GNUdkYUGVujJ0=; b=DbxZ+IixUg7FS2vhYUTjoeg/JxQFXCE4tMtxKrIieHjzJHqXYtsKkKgZZGo2otML6t 1Z+RKa7SvSxDGYwlWi1i5QbpAHrxX0WKpXa7LKU1uUV95Zse6LkJiCDVbSW1aFjzaewl RAEkX+NKBVpbHrVNTSz7eTj6jh2sIem/x5+KMqfXPdKo1OFVbmTDd9QJGEzwRLcc9r87 GxfDUSX8MNHDyTbnNTrCtRjeXRGOstEf6dqdXnW+d4qxhAduOynSzHN/UfaP42psaRIv Lxg9zIdwrIfuHCdmbEQj47cQHby+0kdwfgqoW5G1I24QfmaoZg4htD8B8Qj6MdPnwpeH 2C6w== X-Gm-Message-State: AOAM531GfGMnpxTvLkytYeukXuhUaSGF3kRZSsMvHjOoSADuxFbr3YTt pdQFkqLOomLjSO5CVFW6huKfpg3Ar46S9tvuHgh4+7ST8lCJMMv6 X-Google-Smtp-Source: ABdhPJyhxIUTNdgKKp1to0VEwWZl7IIcHhxWYGOtz3p1akZ4RkIdbK2k/y7LfjspaoMDXUfzHbL5QKcriKnngJcEO7I= X-Received: by 2002:a05:6512:906:: with SMTP id e6mr9160290lft.224.1615848095439; Mon, 15 Mar 2021 15:41:35 -0700 (PDT) MIME-Version: 1.0 From: Tim Bray Date: Mon, 15 Mar 2021 15:41:24 -0700 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000bd6db005bd9af3b5" Archived-At: Subject: [Jsonpath] Scheduling our interim meeting X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Mar 2021 22:41:44 -0000 --000000000000bd6db005bd9af3b5 Content-Type: text/plain; charset="UTF-8" It turns out the first week of May isn't a great choice so I've focused on the 2nd. Here's a Doodle poll, which covers Mon-Thu that week, offering 10AM Asia, 10AM Euro, and 10AM/2PM Pacific, inline with normal IETF distribution: https://doodle.com/poll/w3xcm4wanbgqwq8h?utm_source=poll&utm_medium=link --000000000000bd6db005bd9af3b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It turns out the first week of May isn't a great choice s= o I've focused on the 2nd.=C2=A0

Here's a Doodle poll, which covers Mon-Thu that week, offer= ing 10AM Asia, 10AM Euro, and 10AM/2PM Pacific, inline with=C2=A0normal IET= F distribution:=C2=A0https://doodle.com/poll/w3xcm4wanbgq= wq8h?utm_source=3Dpoll&utm_medium=3Dlink

--000000000000bd6db005bd9af3b5-- From nobody Wed Mar 17 15:22:34 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 ECE703A1681 for ; Wed, 17 Mar 2021 15:22:32 -0700 (PDT) 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.20150623.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 pn-cD467ox5R for ; Wed, 17 Mar 2021 15:22:31 -0700 (PDT) Received: from mail-ot1-x329.google.com (mail-ot1-x329.google.com [IPv6:2607:f8b0:4864:20::329]) (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 702F23A167B for ; Wed, 17 Mar 2021 15:22:31 -0700 (PDT) Received: by mail-ot1-x329.google.com with SMTP id m21-20020a9d7ad50000b02901b83efc84a0so3324691otn.10 for ; Wed, 17 Mar 2021 15:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=tP4wzGPGof6hRMV7xuVcFRnQMdclGpNgo326i66enB8=; b=OFrthi/MgiFKbWqqJf4y5c19EZ0f7O3GmMnxJws5tmALlPcZ1sHCTONryeGtjbG9CM Z5Rje5TGTsqMflW+s//TQl26MURx/ief21K8eaCFjyLgwvL6kJxX+0rAaH0waEVJEuEe 5+6omXdpCG/gbwErtdBwBCPZirabyfe00tvVl1w1gRGixKWKlIkS8d2TLIwqH4skOSuf Cj18ktGL/OWetcmTe86/ToRKcFR/6dzlddJUw9eX2YkH8szPM0yKNP8BFIuakS6TsUP2 lf+JT5rok7ujSNIsIoiBoBNFtY5NvwqrmEV+HznKhxSdyXo+CwSfYJQZHmOlwuT96vcj d5oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=tP4wzGPGof6hRMV7xuVcFRnQMdclGpNgo326i66enB8=; b=Dy43UhQEwIxr/BZZLHEhek9YiHerBiHWFvEF4NmTg9pXtejM/Mw/iwqRIL9Uj4kDXn oje+GlmE0vNFWamEXrqADKcMiIw+bH2j7trjam9IG20yNFbuEbWw9el86C+6BCdxWXyY jc2thqyRArFUPvqltGlYcalR3rlZWlnws7ZVBgilrlJgL16jt/ns1CXf6prZPAzS2NV8 gqON1bRekDCcEgiav5ZOa4kiezYLRiRtUTzzfqn/OZQwF/mrCzaMB/Rkr8CMrG/KfHyh OeW8xrpS8vukWXtQoR5J7Ag/F6UmW7TU+UqgfzKRIzYuFrk3aoRtl/Woal3s39sNh4wE h6YA== X-Gm-Message-State: AOAM531qOFHtEnuNBJz52KS4/kmkOdABj1wUAGf5vOx+qAwF4/OmYqxA U9x7pGD+/17iBE3WJYcoy+4D9VRuUm9MTmSM6/Gn687w2mRmlA== X-Google-Smtp-Source: ABdhPJzLDOK+QCqRVC/XXY6jEhHfh25kKQZa2AcnRyudEqR6aOzijuvlORqxjMe+PYs651OfobUobCLGVzL0XCdnOIg= X-Received: by 2002:a9d:5a8d:: with SMTP id w13mr5158948oth.145.1616019750172; Wed, 17 Mar 2021 15:22:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tim Bray Date: Wed, 17 Mar 2021 15:22:17 -0700 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="00000000000028cd3f05bdc2eb13" Archived-At: Subject: Re: [Jsonpath] Scheduling our interim meeting X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2021 22:22:33 -0000 --00000000000028cd3f05bdc2eb13 Content-Type: text/plain; charset="UTF-8" Just a reminder; thanks to those of you who've signed up - we have a couple of likely-looking slots - but would like to see a few more names. On Mon, Mar 15, 2021 at 3:41 PM Tim Bray wrote: > It turns out the first week of May isn't a great choice so I've focused on > the 2nd. > > Here's a Doodle poll, which covers Mon-Thu that week, offering 10AM Asia, > 10AM Euro, and 10AM/2PM Pacific, inline with normal IETF distribution: > https://doodle.com/poll/w3xcm4wanbgqwq8h?utm_source=poll&utm_medium=link > > --00000000000028cd3f05bdc2eb13 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Jus= t a reminder; thanks to those of you who've signed up - we have a coupl= e of likely-looking slots - but would like to see a few more names.

On= Mon, Mar 15, 2021 at 3:41 PM Tim Bray <tbray@textuality.com> wrote:
It turns out the first week of May isn't a great choice so I&#= 39;ve focused on the 2nd.=C2=A0

Here's a Doodle poll, which covers Mon-Thu that week, offering 1= 0AM Asia, 10AM Euro, and 10AM/2PM Pacific, inline with=C2=A0normal IETF dis= tribution:=C2=A0https://doodle.com/poll= /w3xcm4wanbgqwq8h?utm_source=3Dpoll&utm_medium=3Dlink

--00000000000028cd3f05bdc2eb13-- From nobody Tue Mar 23 10:04:20 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 E925F3A0BD5 for ; Tue, 23 Mar 2021 10:04:17 -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 owsMrTqXO2Jx for ; Tue, 23 Mar 2021 10:04:13 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 995E43A0BD7 for ; Tue, 23 Mar 2021 10:04:13 -0700 (PDT) Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4F4d4q0918zyVW; Tue, 23 Mar 2021 18:04:10 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 638211850.528476-f06063e73445857ac2c9512696d7c7c6 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Tue, 23 Mar 2021 18:04:10 +0100 Message-Id: <8C75ADA3-D5DB-4DC9-8B3A-1ABD1D401D71@tzi.org> To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Jsonpath] PR #79 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, 23 Mar 2021 17:04:18 -0000 I have created a pull request that starts cleaning up the = syntax/semantics part and creates four specific discussion points on = which we might be able to make actual progress: https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/pull/79 As the repo is not yet set up with Martin Thomson=E2=80=99s I-D = template, I have pushed .html and .txt files so people can see what is = being proposed. These will need to be removed before merging. = https://raw.githack.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/proc= essing-model/draft-ietf-jsonpath-base.html#name-jsonpath-syntax-and-semant= i = https://raw.githubusercontent.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jso= npath/processing-model/draft-ietf-jsonpath-base.txt Obviously, this should only be merged once we have answers for the four = discussion points, marked =E2=80=9CDiscussion:=E2=80=9D and indented. Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Mar 24 03:19:20 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 A42863A2982 for ; Wed, 24 Mar 2021 03:19:17 -0700 (PDT) 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, 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=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 kjHMfzKVglDs for ; Wed, 24 Mar 2021 03:19:16 -0700 (PDT) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 E1B683A2980 for ; Wed, 24 Mar 2021 03:19:14 -0700 (PDT) Received: by mail-ej1-x636.google.com with SMTP id k10so31941002ejg.0 for ; Wed, 24 Mar 2021 03:19:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=TPCtZMxte/5Xzk/sPL8NYNvgchDv5JvdiqJhKjFvrEI=; b=ezOD4xTftbjJD+jyxYBcBZnfHZIoQ+PHPfFLod9AYDMYSh3BgjYmludwLuhGOBlZ3Q +f7WKNQkzugj4yjpk6/g21wRlM+TJyD1tGq8ZuBKv2V/fs8Z2C+OvEkJ7xIBmfAlwKcf FdaQTVhKy9ibl1QesGwGya2Wf29reuLfmC0DlCCyxc1sr/IFMqJZwv5MgrS5gSvPlClG jNH5qfm0jr0Vi35pA+w79dIbtXzTBh4t7m1KOBcgBQMPP02eC27hPjcwmsUjZIZLxjCO kHMy4OWr214oGk4UlBGEV0dutR780Sg+zbSVlq7WuS7cW0BTnAxX5NLSxMOyJ48peNI2 4RVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=TPCtZMxte/5Xzk/sPL8NYNvgchDv5JvdiqJhKjFvrEI=; b=XhhKPMxvcNktt5l5Wle/irRGso2c5dgvZYgD9Rk0lptA1ydnxn2QFVIt6xX3DJie++ WWxvNbg9wJa0NZPjo1BAoFMnXZO6/Ay627DMBJ+tzBbVjaNPhblq8HHv9JpJ+RHdMvlQ eLzHNKtgZqqawCTje944Yy/VQtBIYUV6e7PZWb2LP0+xcQt0VwnihHHdtuRgIfdycxKO apqZcN6CUpXxf2yx+LukdH2kH6uN7gQdKhQkCCxBJlTfYMOwtLvtFs7xJIxKlqijvK/y aFxuLeq0eJa4Y7TOa3bRJq6kqbOHxJuZ+png3xMzp+nv7CTBIaEf+MbZfyNn6BODqDYl pM1Q== X-Gm-Message-State: AOAM5313ux899xDsIcaCNh2luQG9Lseje4wpYRSfK7qwNEsUaOG4emvs drXaJxWQKV6LOcz5cU9WUmVRFMXhgRQ= X-Google-Smtp-Source: ABdhPJyNGDixr4drFe4OfnpHxgCsOye6DXeL0+pk6JBsdgK4+WJS/Vp+Jko/YKcna6cDc7bG+sU/+A== X-Received: by 2002:a17:906:e48:: with SMTP id q8mr2895210eji.84.1616581145885; Wed, 24 Mar 2021 03:19:05 -0700 (PDT) Received: from [192.168.1.95] (71.224.125.91.dyn.plus.net. [91.125.224.71]) by smtp.gmail.com with ESMTPSA id ga28sm684211ejc.82.2021.03.24.03.19.05 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 Mar 2021 03:19:05 -0700 (PDT) To: jsonpath@ietf.org From: Glyn Normington Message-ID: Date: Wed, 24 Mar 2021 10:19:04 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Archived-At: Subject: [Jsonpath] ABNF syntax checks - help wanted 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, 24 Mar 2021 10:19:18 -0000 I raised a couple of issues about ABNF syntax checking the draft. https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/81 points out that the syntax currently appears to be broken. https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/82 is to add a syntax check to CI so we can attempt to keep it clean. If anyone wants to take a crack at either or both of these, that would be helpful. Regards, Glyn From nobody Wed Mar 24 03:21: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 5F8213A29A0 for ; Wed, 24 Mar 2021 03:21:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 hNntgizrjwXv for ; Wed, 24 Mar 2021 03:21:45 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 382123A299B for ; Wed, 24 Mar 2021 03:21:45 -0700 (PDT) Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4F545y4k5mz100y; Wed, 24 Mar 2021 11:21:42 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Wed, 24 Mar 2021 11:21:42 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 638274102.23806-b37c2bdd5ec473e7988af13f7a72e414 Content-Transfer-Encoding: quoted-printable Message-Id: <8AAD912E-220C-4A63-A2F9-0CF37AE0DF16@tzi.org> References: To: Glyn Normington X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] ABNF syntax checks - help wanted 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, 24 Mar 2021 10:21:48 -0000 On 2021-03-24, at 11:19, Glyn Normington = wrote: >=20 >=20 > = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-jsonpath/issues/81= points out that the syntax currently appears to be broken. Well, the script appears to be broken. I get (Shell command failed with code 1 and no output) when running xmlstarlet manually. Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Mar 24 03:25:51 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 C9A313A29B7 for ; Wed, 24 Mar 2021 03:25:49 -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 cMP2UJVvQEvG for ; Wed, 24 Mar 2021 03:25:44 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFFBB3A29B4 for ; Wed, 24 Mar 2021 03:25:44 -0700 (PDT) Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4F54Bb1Xmdz17bt; Wed, 24 Mar 2021 11:25:43 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: <8AAD912E-220C-4A63-A2F9-0CF37AE0DF16@tzi.org> Date: Wed, 24 Mar 2021 11:25:42 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 638274342.78123-4961f5de92b8020d787b44a8b74903f8 Content-Transfer-Encoding: quoted-printable Message-Id: <5DB1EBD1-E200-4C74-85C1-E6C2EA6CE701@tzi.org> References: <8AAD912E-220C-4A63-A2F9-0CF37AE0DF16@tzi.org> To: Glyn Normington X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] ABNF syntax checks - help wanted 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, 24 Mar 2021 10:25:50 -0000 On 2021-03-24, at 11:21, Carsten Bormann wrote: >=20 > Well, the script appears to be broken. Fixed in main. Gr=C3=BC=C3=9Fe, Carsten From nobody Wed Mar 24 10:43:26 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 439E03A31D3 for ; Wed, 24 Mar 2021 10:43:24 -0700 (PDT) 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 OudsUh9wu0Da for ; Wed, 24 Mar 2021 10:43:20 -0700 (PDT) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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 1BBD73A31D1 for ; Wed, 24 Mar 2021 10:43:20 -0700 (PDT) Received: by mail-pj1-x1034.google.com with SMTP id mz6-20020a17090b3786b02900c16cb41d63so1610937pjb.2 for ; Wed, 24 Mar 2021 10:43:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=zTfhx4R6EZRfOxfokF4k0qWGdG1htek9cbqARSMfa+I=; b=jZdnqO5lNmj7wdeSXl/q7YN7eWuiEpc1RENjMFzlq5jAPf0efWlXCk8+nUKC4a1T/i MXT84tya3ab7gqgRRyFE48BXOgWHWSWR6OWJczTt4n9oedUAfEAayrfab6xyoTcysTD7 gahd26fmzixbADD0AmUN05Y+VTvoVTZ+lHj/nCBp3DfD5Q1ByxI7BX5KdecXKZ0jsOB2 HWPiEYgzThWArN5ncLXDv6kaawW+09hA1fyWTs+yLbQekfcGugIj4gKKkxE5YrpKLdTp 7SSk01J53ngjIy1iaNVQYnmFBIDPdsv4WXS1PGnoHjyYVVeT9retFIOkKYuYEzpCmUst UBLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zTfhx4R6EZRfOxfokF4k0qWGdG1htek9cbqARSMfa+I=; b=rAXCOoxEJeq0lMoCUIp+QcDGj8/sstAswhvzhy/mOpvV56MTohTajgD+vaHZHPB+MD oRxIb11Yh1Dqqg+zWwNxMUCOzFQ8XZt51YePatAcbZ7aOgVNmow1yBye/85o7NxXdH62 dDxcJ38m6D3rMS0JLTD+VxyVV0KZ8f6u2m//2F5w8o6LzDMakzt2QGBQGMhpxcXafIQN nX8S2hsmvi4X2I/oOmNOQYVDTtAljv9+t2aD5KT0wTKmZJjhO7l7dct59fGAivyTuI+P s89YxAffrfKEL5y+N0kx8kXObo4WbqBSACgNA7OtZxSoL+KyMUZ2R3Bl1yBo0w+AEI4U RXFA== X-Gm-Message-State: AOAM530jE8ZYXcBWqwnWVtofcWUS3lrlW+feBrY+1kMzZjbMA9ovjeQG 9ALz9SRQwGi72rT6tT/g36OG6DE8M652zQgu0/yr0eYyvIw= X-Google-Smtp-Source: ABdhPJyiqmMHNsAhflX4rQvQCvdoYbuXNZsY4hbREZUiB2BpKFBmWmJpFWpImAeaIN/lYjSoClmCsauMjlW6tfFvgfs= X-Received: by 2002:a17:90a:c249:: with SMTP id d9mr4651797pjx.104.1616607798447; Wed, 24 Mar 2021 10:43:18 -0700 (PDT) MIME-Version: 1.0 From: Glyn Normington Date: Wed, 24 Mar 2021 17:43:06 +0000 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="0000000000009152c105be4bd5c6" Archived-At: Subject: [Jsonpath] nicely formatted PR diffs 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, 24 Mar 2021 17:43:24 -0000 --0000000000009152c105be4bd5c6 Content-Type: text/plain; charset="UTF-8" ICYMI, Carsten upgraded the way our draft is rendered today. See https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/ (this link is in the About column of the repo home page) for links to nicely formatted diffs for PRs as well as the last commit on the main branch (which replaced master today, again ICYMI). Nice work Carsten! Regards, Glyn --0000000000009152c105be4bd5c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
ICYMI, Carsten upgraded the way our draft is rendered= today. See https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/ = (this link is in the About column of the repo home page) for links to nicel= y formatted diffs for PRs as well as the last commit on the main branch (wh= ich replaced master today, again ICYMI).

Nice work= Carsten!

Regards,
Glyn
--0000000000009152c105be4bd5c6-- From nobody Wed Mar 24 11:43:55 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 433093A32F4 for ; Wed, 24 Mar 2021 11:43:55 -0700 (PDT) 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 P8QQ8lMjyLDs for ; Wed, 24 Mar 2021 11:43:50 -0700 (PDT) Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 D550B3A32D5 for ; Wed, 24 Mar 2021 11:43:50 -0700 (PDT) Received: by mail-pf1-x42b.google.com with SMTP id y5so18005613pfn.1 for ; Wed, 24 Mar 2021 11:43:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pbIK59QfYEDtgG/Rv04uCkpeBKnVZvwH+ZkiHfid4IY=; b=syowPb3Hv1pHHJjvM9OzQ8s5yBapk8/0ew5vawukZgZcqLZw+KhQ65Ijqa3p/ORAtR q6/C+FyMtJeLnim0jLVeQFxrLPdC7pFRpVWtCCJ+MaxpTRTVxARF1j++4/IMRbiP2yJc Ey2C8QvIqgFzYgg/VYjFpZ0ZU4RdzT9CO+T/NHH7AbiIfHV/IQQFTNs8Cv6kBEo5BJeJ i2ALlPblGHSplMgkcMEcrJFuPFQxrHNSxCbYRckUFWFfrStfsiCh42wf8Mg6oy/V5JP9 g11CAiM/8D7PF1zsTXCXiOFlq5Ph1Bb7B6cukM2w5BkmlPl6HAOaAxr43OLim36s7bPa OYPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=pbIK59QfYEDtgG/Rv04uCkpeBKnVZvwH+ZkiHfid4IY=; b=oN3bZLoT5Ie5ikleAAeOD1vBY2VQZTpX4rGI6f/qQdUnMz/GINxzh4onJdsZpPSCd8 sijfqN9Uq2+yj/USF7iQs/afa93NLo6ZNdAOteiOHw7kWzOuEKj+A2/pe8d15X/3YDA5 aWpwKD1H7vAUbNQ3h25MTe1mUB5jeD1UttLffIDT0OEPTbxz/qYIEB550Ti8ry2Wcvna QagZGoi5cVTvWjXdXVdeJtAseeqdQmPgS2zTc2Zjy6OKwm7lDZpVpCyRCR7ZdNP5oyFq FYT9tj/VKNj3GNPJ/TZ2JCY3mcG64fGKXjs7jRIIwn3rVbHKoVqhEjJe6yQNZO91VKut KWLw== X-Gm-Message-State: AOAM533H+0sNGQnPEbRnBqARzxnDDmVPgk9vwgk5mrgAOttXm2wDocJW /3AhbfwSQHuN2/iustXN9C4BDC7Lczq5MJ8lcSVb30UtTHY= X-Google-Smtp-Source: ABdhPJznQY3U+pngmPwuZgQFkfHnexkIlCvyhcy8F69ms8G5WXJhd+toWiCb+N6WU5shos4p+1fDJihYdgPI4oR4y5o= X-Received: by 2002:a65:6a43:: with SMTP id o3mr4132901pgu.297.1616611429247; Wed, 24 Mar 2021 11:43:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Glyn Normington Date: Wed, 24 Mar 2021 18:43:36 +0000 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000faf00e05be4cada4" Archived-At: Subject: Re: [Jsonpath] nicely formatted PR diffs 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, 24 Mar 2021 18:43:55 -0000 --000000000000faf00e05be4cada4 Content-Type: text/plain; charset="UTF-8" I wrote: > nicely formatted diffs for PRs as well as the last commit on the main branch Turns out the diff for main is relative to the last submission (presumably to IETF), rather than the last commit. This change just gets better... On Wed, 24 Mar 2021 at 17:43, Glyn Normington < glyn.normington.work@gmail.com> wrote: > ICYMI, Carsten upgraded the way our draft is rendered today. See > https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/ (this link > is in the About column of the repo home page) for links to nicely formatted > diffs for PRs as well as the last commit on the main branch (which replaced > master today, again ICYMI). > > Nice work Carsten! > > Regards, > Glyn > --000000000000faf00e05be4cada4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I wrote:
> nicely formatted diffs fo= r PRs as well as the last commit on the main branch

Turns out the diff for main is relative to the last submission (presumabl= y to IETF), rather than the last commit. This change just gets better...

On Wed, 24 Mar 2021 at 17:43, Glyn Normington <glyn.normington.work@gmail.com> wrot= e:
ICYMI, Carsten upgraded the way our draft is rendered today. See <= a href=3D"https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/" tar= get=3D"_blank">https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/= (this link is in the About column of the repo home page) for links to = nicely formatted diffs for PRs as well as the last commit on the main branc= h (which replaced master today, again ICYMI).

Nice= work Carsten!

Regards,
Glyn
--000000000000faf00e05be4cada4-- From nobody Wed Mar 24 12:07: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 ED8AD3A336E for ; Wed, 24 Mar 2021 12:07:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 vHAzg-MouSXM for ; Wed, 24 Mar 2021 12:07:05 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EEE13A336D for ; Wed, 24 Mar 2021 12:07:05 -0700 (PDT) Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4F5Hm649BGzydF; Wed, 24 Mar 2021 20:07:02 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) From: Carsten Bormann In-Reply-To: Date: Wed, 24 Mar 2021 20:07:02 +0100 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 638305622.1067621-fb068c020f3b26d38a3caa96999024ea Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Glyn Normington X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: Re: [Jsonpath] nicely formatted PR diffs 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, 24 Mar 2021 19:07:08 -0000 On 2021-03-24, at 19:43, Glyn Normington = wrote: >=20 > Turns out the diff for main is relative to the last submission = (presumably to IETF), rather than the last commit. This change just gets = better=E2=80=A6 (And it=E2=80=99s all a feature of Martin Thomson=E2=80=99s excellent = I-D-template for Internet-Draft repositories [1], which we adopted.) Gr=C3=BC=C3=9Fe, Carsten [1]: https://github.com/martinthomson/i-d-template From nobody Wed Mar 24 14:30: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 B45B63A0BF8 for ; Wed, 24 Mar 2021 14:30:40 -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 guZoKVKSbzyx for ; Wed, 24 Mar 2021 14:30:36 -0700 (PDT) Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A19B73A0BF6 for ; Wed, 24 Mar 2021 14:30:36 -0700 (PDT) Received: from [192.168.217.118] (p548dc178.dip0.t-ipconnect.de [84.141.193.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4F5Lxk1KM9zyd6; Wed, 24 Mar 2021 22:30:34 +0100 (CET) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mao-Original-Outgoing-Id: 638314233.706162-2c76ea793a6dc7f554ba3f3495c2580f Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Date: Wed, 24 Mar 2021 22:30:33 +0100 Message-Id: To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: Subject: [Jsonpath] #73 (normalize-fix) -- ready to merge 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, 24 Mar 2021 21:30:41 -0000 I rebased normalize-fix (a side issue that came from one of the long = threads) to current main. When you look at the PR, this looks a bit daunting, as the rebase = process is not handled by github PRs. The actual change is visible in: = https://tools.ietf.org/rfcdiff?url1=3Dhttps://ietf-wg-jsonpath.github.io/d= raft-ietf-jsonpath-base/draft-ietf-jsonpath-base.txt&url2=3Dhttps://ietf-w= g-jsonpath.github.io/draft-ietf-jsonpath-base/normalize-fix/draft-ietf-jso= npath-base.txt This fix should be rather non-controversial, but additional reviews = never hurt. Gr=C3=BC=C3=9Fe, Carsten