From nobody Fri Oct 15 15:42:59 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 83C4B3A0DF7; Fri, 15 Oct 2021 15:34:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: francesca.palombini@ericsson.com, jsonpath@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.39.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <163433724451.17026.9272368507707311505@ietfa.amsl.com> Date: Fri, 15 Oct 2021 15:34:04 -0700 Archived-At: Subject: [Jsonpath] jsonpath - Requested session has been scheduled for IETF 112 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: Fri, 15 Oct 2021 22:34:23 -0000 Dear James Gruessing, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. jsonpath Session 1 (2:00 requested) Wednesday, 10 November 2021, Session I 1200-1400 Room Name: Room 2 size: 502 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/112/sessions/jsonpath.ics Request Information: --------------------------------------------------------- Working Group Name: JSON Path Area Name: Applications and Real-Time Area Session Requester: James Gruessing Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 20 Conflicts to Avoid: People who must be present: Francesca Palombini James Gruessing Tim Bray Resources Requested: Special Requests: --------------------------------------------------------- From nobody Mon Oct 25 15:26:48 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 7D4C13A0809; Mon, 25 Oct 2021 15:26:47 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: internet-drafts@ietf.org To: Cc: jsonpath@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.39.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jsonpath@ietf.org Message-ID: <163520080746.6169.15298539957844978835@ietfa.amsl.com> Date: Mon, 25 Oct 2021 15:26:47 -0700 Archived-At: Subject: [Jsonpath] I-D Action: draft-ietf-jsonpath-base-02.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: Mon, 25 Oct 2021 22:26:48 -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 : JSONPath: Query expressions for JSON Authors : Stefan Gössner Glyn Normington Carsten Bormann Filename : draft-ietf-jsonpath-base-02.txt Pages : 30 Date : 2021-10-25 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 is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-02.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jsonpath-base-02 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Oct 25 17:14:38 2021 Return-Path: X-Original-To: jsonpath@ietfa.amsl.com Delivered-To: jsonpath@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8DA3A0C19 for ; Mon, 25 Oct 2021 17:14:36 -0700 (PDT) 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 VrceYKSUM6xt for ; Mon, 25 Oct 2021 17:14:32 -0700 (PDT) Received: from sonic315-14.consmr.mail.bf2.yahoo.com (sonic315-14.consmr.mail.bf2.yahoo.com [74.6.134.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 4BE7E3A0DD9 for ; Mon, 25 Oct 2021 17:14:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635207270; bh=0wfwAS/1tYxzUmvNhqpw98loNol1/+2NR2HCbSlh0qw=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=OX/adekqI5o0TWD/AUcOkOkH1SYOOCJPyeES+LNMBc4M0l2dV5rneA0NNXT30QhoCozos2HLEQWNId77JECmil9JGgLQjrxs7QQPC3NLpqRrJVeYCY47aimCzhkQoC6mVDtF4yGzN+rSJmnK9vR91iJ/jdmyVyS5Cy700OOoSYslwkiF+pPo6P8Efp1UF7JRyZBjV8CsEiAIFBOJlJ5D91cBhutApNSH4U0z068IMYGSZxkplt2Z+Atl5yzaHjgSnhFBoCh+uwJqmcPmYBK8hJ88T338G2cBJTK5/zqMmeUDZxzoHCiIRjfT2ArBOZxBA5YJ2Pxk0L60JhaIZiRe6Q== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635207270; bh=LskClBd1lWcxymudIdoZNWB3g68S8Dm9V2pzio8rRg7=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=eZC1LKzBnqjmWVu5OCtrLow1pufXtKD83yP42rRLvf+Mbz9kBYHxW9LLx8R8mHHof1OifjiaOtbTfSIOp7lzUy0lu4wxi4R7tqA22IkjIA99nxa7RXHGIcVboFbdgK3vgrgTmE5hkCH65cPuW6Sv6vV2FiBx+/4o15Jp25RyfiOSV8aY1n5wAZfO0UcqsKmrBxZGnvn4zmkvHwEpPMxHsf/JUkZCtxgVDc9pDv+90cQr84JlhW8f+zpnzCtspusexoIlZIbjMicrKTA01UIlOooRScAMjcJQifS+759RTY5oGU6s1EYmRlB1VZQnBvykSGdB9H4sYPpY9BRwzJQLog== X-YMail-OSG: td1lcQMVM1me3WBfwz5MC9EXqyWQPi0Sx1MXNgkCxsu7T1UMw5fUhydlKBobfg9 hVJzapy1z422hyLse4GmLBindlFlfZO238_LxcmJ1ebomxIbOAX9aCpBnsvMHgDHP_cvG5Rqo4_c C9cLIly3P6jlHezwJogayYNBN7.dvWTB8OM3qmPowiWfsa8ogpdSvcYsQHzIaLee5A2WOSmfTlzQ Pkp8ths_ZJUTEl3I7UzqaAksMzmGM16vyrd4ibAtESpmyR0914Wcf3IHYks2ipKVvN6aDJfml3OE 2vwX._jO8U2VVFUxHoPWqIAlFCeKCixgvot_IecK7N.lkW7p8XGeeSmYbNtZXDS7ESijG3YN5_5w YPbVj2.cCzyNYc53T26Wo_1fjbZ2k2SAZNCO5DGTfERE5riBaxLSXs0cAh5YP3wFU5eN.7JSpj65 rM2ZXmXLV0oEbeuSfjdLcWjKKJThst36lKRxK_K16g7LwokIdV3z2NsaKc9R_1TM5dK4NffIlmmj wpcIfNba6_X.RiCKt_EpilqvRMJyPYjIRfzd1w6abAKYDk0ygypxVwq7Hut_ijlh1PBXVVpCTX1Y flqV8jBKxPzVPovUycOzn8DlTIT25lvGsNJOiggmfjy.9TtfLQsO5uQfO.BgV2o3mx8rs.MTPnfr As_e05Rt3O90ve_xpelwcvvVBYeCnwyb9AtdHynRNcdfxz74Rl_RjKSwlDUjAIrHv32KoTDtirR2 pFvEm2YzAoSK3phI1M27Hib.WDnuETO730F7SbWZyo.SAbJdE9xu22epmvvf1QcMYy.g6bbJ2x4a fSRan6.eYXgUvsPsz5eRhZ0nbHN8INW6tMFVlbaesmUyEB6NnfayTWpZWixfPf3XqRwHWs3vShjP Bu62F8zhwH36sB.CIBh.Hl7AMIDpjmXBmFWMFnAoS3Er3qscA_ZTgHvahSJ.canZxfD3E9VVLpzb 5cePYHVAOMYkipIPg3xuRL02DfEOOdr4RZ0CuvS1tErEYVSqQMno4Xv9mkyWKXxktx_Dwcznr3f3 5iCv5YbSSfaBFmPjv3JE013OzeJgsaIeUmR_fDZsrHXXc5GojbI7umk.YOAyVQ1Gtz96iUFgRhxi 6zBfoT6YiGEuMEGwACRxcv8MSHb_EWVtUC.fJL4_DGxCNGXV1rafP9XXTzqYo0m3HniRz072Bp7Z L7IoPHNXyGdSx.M9vp_pzNUCgzHgX6333lx0Jelf7arXCGT0AaV8PZq0gCMNnplm.D8jQMPIyWKI Jg1LbHC.Mkfe1tQ.EC874bjJ63xzoRTYcHeTJK3Ti0ciXWVRI9GT9SFAtcGbdLFEpLAS7cxq2lkZ cXOa.tvhZL2gNn1Orq68WVy7sXwG1YtPLeLNO9UmW3qw4MMMSNa6RWeekhS7olu3T8hjy9hZlCZT N8nTRXOAkPmP61rOXhoc0p4wbXEPEpmXcKrLJaWISmALEHNZeKB5b0Zak5L9ywTMvl.ydJ6e9mJw lXLp5nuXYj08W_iHR3iE1hnKlSa7ONQOpoxx6C9cThDJfJEReAy7Uhs7ukti1XvEqSF.YF3.PpyA A2VI6cvqWu2uNmPINU_xKTEwsZ9hTj_V.ndRzme1EzyINuwVFxBNhMauLXOkCLY4UVOQ1gPZSAyY sstNtis3YQ7K3gTxM0sSJGvCa99IHG4Jk15XsU.hMR82nQG0045fPFbat5AAWLFf.Sn5tEtCAEJk T9ryKtADR1fnVe27OOFV5nl3k5HdTKFu3hB9xSawU0jSiOW0Tahz6Nf72P3YJyHDgBzR4lta.5FQ Nx5vlvGFBZDzXyzOFMAf7Y3rEZvfJPj2LmJBa47KJGa.NnIFJsOqge8tLIiui9HniyJPTNFqqoaU xP8OpF2_gxawvCxrrGs9wdQLoMg0XmD.YisLoAvEQgy6pGBwk27lLR2fte1t.1UuzGmFTNbUF.oK L2mBJr67IOqO0JIfyz3tuIJIRA0Q5fWjLqgGIb5RneRm471H_HMagMCovGeuM_D8GHnKxxFsYoL4 OPkd3WiSvg7mZAY4FR9Wn2FoWwk7V82tnLNnFpU0TMco_QGnHAaK1P4wRCveF774Ma33zUE6QSTy t4SzvAnO0B4VAbGy7YLSeb85DFccXD12Ee4yOe7I0dVxQcfuVWYl3BWo3ZHS845myaplnkdH3L9U kzFjw6asayPrQNmm38MZsU2nCjQCOXoUuJsTsSrfmPF85iEr4sZpunjY2_OM3fkCWt.OFfX9dmNS L2PgTCo7PpO0mEVroKFEZQnIFkAg1.4xGrLD4 X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Tue, 26 Oct 2021 00:14:30 +0000 Date: Tue, 26 Oct 2021 00:14:28 +0000 (UTC) From: Greg Dennis To: "jsonpath@ietf.org" Message-ID: <2064952985.557002.1635207268985@mail.yahoo.com> In-Reply-To: <163520080746.6169.15298539957844978835@ietfa.amsl.com> References: <163520080746.6169.15298539957844978835@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_557001_609258280.1635207268983" X-Mailer: WebService/1.1.19198 YMailNorrin Archived-At: Subject: Re: [Jsonpath] I-D Action: draft-ietf-jsonpath-base-02.txt 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, 26 Oct 2021 00:14:37 -0000 ------=_Part_557001_609258280.1635207268983 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable How do we have a new draft when there hasn't been any activity in Github? On Tuesday, October 26, 2021, 11:26:52 AM GMT+13, internet-drafts@ietf.= org wrote: =20 =20 =20 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the JSON Path WG of the IETF. =C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : JSONP= ath: Query expressions for JSON =C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 : Stefan G= =C3=B6ssner =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Glyn Normington =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Carsten Bormann =C2=A0=C2=A0=C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-ietf-jsonpat= h-base-02.txt =C2=A0=C2=A0=C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 30 =C2=A0=C2=A0=C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 2021-10-= 25 Abstract: =C2=A0 JSONPath defines a string syntax for identifying values within a =C2=A0 JavaScript Object Notation (JSON) document. Contributing =C2=A0 This document picks up the popular JSONPath specification dated =C2=A0 2007-02-21 and provides a normative definition for it.=C2=A0 In its =C2=A0 current state, it is a strawman document showing what needs to be =C2=A0 covered. =C2=A0 Comments and issues may be directed to this document's github =C2=A0 repository (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath- =C2=A0 jsonpath). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-02.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-jsonpath-base-02 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_557001_609258280.1635207268983 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
How do we have a new draft w= hen there hasn't been any activity in Github?

=20
=20
On Tuesday, October 26, 2021, 11:26:52 AM GMT+13, inter= net-drafts@ietf.org <internet-drafts@ietf.org> wrote:



A New Inte= rnet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the JSON Path WG of the I= ETF.

    &nb= sp;   Title          : JSONPath: Query expre= ssions for JSON
        Autho= rs        : Stefan G=C3=B6ssner
                    &= nbsp;     Glyn Normington
   =                     &nbs= p; Carsten Bormann
    Filename&nb= sp;       : draft-ietf-jsonpath-base-02.txt
    Pages          : 30<= br>
    Date       = ;     : 2021-10-25

Abstract:
  JSONPath defines a str= ing syntax for identifying values within a
 = JavaScript Object Notation (JSON) document.
Contributing

  This document picks up the popular JSONPath specific= ation dated
  2007-02-21 and provides a nor= mative definition for it.  In its
  cu= rrent state, it is a strawman document showing what needs to be
  covered.

  Comments and issues may be directed to this document's gi= thub
=
  jsonpath).


The IETF datatracker status page f= or this draft is:

There is also an HTML version avai= lable at:
------=_Part_557001_609258280.1635207268983-- From nobody Thu Oct 28 09:51:38 2021 Return-Path: X-Original-To: jsonpath@ietfa.amsl.com Delivered-To: jsonpath@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D98683A0FD2 for ; Thu, 28 Oct 2021 09:51:37 -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 eWgHQq0QxGQf for ; Thu, 28 Oct 2021 09:51:33 -0700 (PDT) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 514053A0FDA for ; Thu, 28 Oct 2021 09:51:33 -0700 (PDT) Received: by mail-ed1-x533.google.com with SMTP id z20so27743877edc.13 for ; Thu, 28 Oct 2021 09:51:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:mime-version:subject:message-id:date:to; bh=ahe76kNH5bc4qscr6PJSsXKTSeva3dsaSarZeesRbLQ=; b=jIEkl+lheMIYAA8L8Yq/Dy5CF/jGWNSjgULzlOMNWjwuGQwVuDB0dcBGsRErG2+c++ TN+E8RNiU1p6niNdMuDriYBH4wjxIRaGuFv5QlqxRvgCt/WWZVjZiu1y2EbQRu/IN/5O gJ3+DcVMPS5mJWriH/ceusmd2FmU9GoAYpFJTv2mAvRXQhkuHDWsNdwHVj3mepqsIp/i 1U0vraP9kAcA7gAiopNDwdwQ9iCVfWPALc8HthRheSozn+4F7tasuPnaChykfv61Kmn4 ok8K7D1SMijDKjVGGISlWo0WJ2DIShmXsy5DqBNZuNYVIntMK8S2iILpliTnPn5RwkmZ 8wbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=ahe76kNH5bc4qscr6PJSsXKTSeva3dsaSarZeesRbLQ=; b=AeEP648dLaQBYruKDXqw/uqKgD8PvirgXaboLznQPlkdPB5ogzD2wjijlEyGj5oD9l HAdp0d1Fuy0Aqve5TefLbiWccBhdLr0GFz3nyoALG/zT0tytHUGquQKJ7zNbMPPHe/tB nKc2lb1irpbf/DvQuBKnRJwT3zJfsU+JgincHMZRzMGc3scFrXEOu4d0pohRgI6FU2MT dNwGKlXCFffZBXer7ifm5P/0Z7GR+uTzPseR8Pfh69wVRdVtyidT0KOY7MpS4Qy13fVv e4l98fSDxVokOSfMlazCQ+eq4bbDId63aW6vOU1yj2Ee2cda4q29V5F8vg6wNPXBDgUH CI6A== X-Gm-Message-State: AOAM5312yo3XOMz1J+Sahe3UckhTvpig+HN+wrAQAzJOK71ZHGjpYLis zzYSZGpLYYfc5OC4CD51xvbYfyEl5rULzw== X-Google-Smtp-Source: ABdhPJxOv+u2RVt0oEEHUTN+zz9cS2xspVxtctnmO3HybszKZRe0Df14/6fg0LspVq8CQDxTk+kFqA== X-Received: by 2002:a05:6402:4406:: with SMTP id y6mr7475811eda.140.1635439890789; Thu, 28 Oct 2021 09:51:30 -0700 (PDT) Received: from smtpclient.apple ([2001:984:65b0:1:a5d0:103e:54fe:53bd]) by smtp.gmail.com with ESMTPSA id i15sm2040933edk.2.2021.10.28.09.51.30 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 Oct 2021 09:51:30 -0700 (PDT) From: James Content-Type: multipart/alternative; boundary="Apple-Mail=_01834E06-3122-48C1-A7C9-80A3F493F394" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Message-Id: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> Date: Thu, 28 Oct 2021 18:51:30 +0200 To: jsonpath@ietf.org X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: [Jsonpath] Next meeting at IETF 112 and agenda X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2021 16:51:38 -0000 --Apple-Mail=_01834E06-3122-48C1-A7C9-80A3F493F394 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Folks, IETF 112 is a few weeks away with our next meeting being held on = Wednesday, 10th of November from 12:00 to 14:00 UTC. If you haven=E2=80=99= t already registered, you can do so here: https://registration.ietf.org/112/ We have only a few items on our agenda for this session: https://datatracker.ietf.org/doc/agenda-112-jsonpath/ = If there=E2=80=99s any other subjects or issues you=E2=80=99d like to be = part of it please email myself or Tim and we can include it. - J= --Apple-Mail=_01834E06-3122-48C1-A7C9-80A3F493F394 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Folks,
IETF 112 is a few weeks away with our = next meeting being held on Wednesday, 10th of November from 12:00 to = 14:00 UTC. If you haven=E2=80=99t already registered, you can do so = here:

https://registration.ietf.org/112/
We have only a few items on our agenda = for this session:

https://datatracker.ietf.org/doc/agenda-112-jsonpath/
=

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

- J
= --Apple-Mail=_01834E06-3122-48C1-A7C9-80A3F493F394-- From nobody Thu Oct 28 10:45:27 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 A34923A097F for ; Thu, 28 Oct 2021 10:45:19 -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.20210112.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVPCqyorz0h3 for ; Thu, 28 Oct 2021 10:45:15 -0700 (PDT) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 E756D3A0965 for ; Thu, 28 Oct 2021 10:45:14 -0700 (PDT) Received: by mail-lf1-x129.google.com with SMTP id x27so15249692lfu.5 for ; Thu, 28 Oct 2021 10:45:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tzVMff2OG1kIg6UaR3iNpF9iikWaqKAebA20uBDwjLw=; b=ibUkiWJOvFN/VhAVifuimilYSxFphRUQirKE+v0pSH7QMwMceS3jdHbHaGamthzkY2 vpE3GmyBEqYlTfIoW0RVAuEqhn2nCuiXBtEECxMndDBi8KcjFJm90Q5qvUEeV3jx9G7v Bco2Lh4mxngOuXBzkpD9oWy16k9m6oRbobb9FNfVBZuHIvXvTq3rkM8ykqw9VtBAD4za /A7J9DFK81y0B30WBnS/trVrC1hcwQ8A4Jm126/L8/gNvzUTboSIv4okaiKFXCU37bea ZWEMkLX4JK0x6erEFcCe92s275KpSN2Ikb8q8oNuki7WDVsrSAxXGEWUVRmaftKGQu3w hCnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tzVMff2OG1kIg6UaR3iNpF9iikWaqKAebA20uBDwjLw=; b=SiwnXmPYW6vhOTi7j456BsDW9huD+Q3r/QSCXKbVkmEX4o4SIYva9mv1ag/B1itdp6 ZTc9kBkJk35Vbxn+lF1kVT9bKYq3nntGH+phyYsQcrdwweIw9rlWz4+9TgOkqlJTj3ht g1/ZeaS8sumY/TXZk1+aPJ7BcyWqNssk5MMdm+ADNT+/fMwkbyBNKYgA7BIgLGUrN903 YZTpFHtfYXNm705pcGvi9Pkmo6ZFLmqRi2hTHhUZTbeqRELC1RvpUGT5uE+boVTp74E3 xXJJLO+OrIzI3pEYym7nioRCBThFSLlPDSza61BmacqJnESOrHAkZs1aZ2esvOXbXTuU WCHA== X-Gm-Message-State: AOAM532SpMlcUQoI2lCd8s5OjlZI/AGR6C023+AVJCVqu/BoVkVJ+j7Z P/AKHq6IK58Rfp+0+iEGWKwNWYXQMFlMePLGKo1oCBxQJimMSQ== X-Google-Smtp-Source: ABdhPJzS0sDzVma+Co42XnzKHJQhLheyyV2yxRV+DYVSDep/6cvhbNW6wMy+d8faTbYilSHzDAMfV/tx+kFeFCWcCks= X-Received: by 2002:a05:6512:22c3:: with SMTP id g3mr86405lfu.646.1635443112113; Thu, 28 Oct 2021 10:45:12 -0700 (PDT) MIME-Version: 1.0 References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> In-Reply-To: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> From: Tim Bray Date: Thu, 28 Oct 2021 10:45:00 -0700 Message-ID: To: James Cc: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000bf8c7a05cf6d451e" Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2021 17:45:26 -0000 --000000000000bf8c7a05cf6d451e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable You'll note that on the draft agenda, there's an item labeled "Draf Status - Tim". I went and took an end-to-end pass through the current draft, asking myself the question "How much work is left to finish this and send it off to the IESG?" There's quite a bit, but less than I thought. To help us talk about this, I offer this annotated table-of-contents, outlining what I think the draft status is section-by-section. Feel free to disagree or amplify, either right here, by raising issues over on GitHub, or during our Nov 10 meeting. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Options for each section: OK - Ready, more or less ED - Technically OK, needs editorial work TECH - Open technical issue(s) BAD - Needs rewrite Contributing [BAD] - IETF style 1. Introduction [ED] - Lose 1st para, polish 1.1. Terminology [OK] - May need to revisit if we change any of our terms 1.2. Inspired by XPath [BAD] Just lose it. Put one sentence crediting XPath in the intro 1.3. Overview of JSONPath Expressions [ED] - lose XPath stuff, not sure about language about conversion to bracket notation, that's internal to a processor, right? 2. JSONPath Examples [OK] - May need to revisit if we change stuff 3. JSONPath Syntax and Semantics 3.1. Overview [ED] - "no further errors=E2=80=A6" language needs a little more expansion 3.2. Processing Model [OK] 3.3. Syntax [OK] 3.4. Semantics [OK] 3.5. Selectors [ED] - why is the ABNF up in 3.3 while the descriptions are here. 3.5.1. Root Selector [ED] the "Semantics" section is confusing, I think we already said what it does 3.5.2. Dot Selector [ED] Should we have an example in each of these 3.5.* Maybe a note about the dangers here, e.g. if you have something like { "a.b": 23 } you can't use dot notation 3.5.3. Dot Wild Card Selector [OK] 3.5.4. Index Selector [OK] 3.5.5. Index Wild Card Selector [OK] 3.5.6. Array Slice Selector [ED] - Seems unnecessarily long, and the language about its history adds no value? 3.5.7. Descendant Selector [ED] XML history adds no value? 3.5.8. Union Selector 3.5.8.1. Syntax [ED] - sloppy informal language 3.5.8.2. Semantics [ED] in this place "Semantics" gets its own Table of Contents entry, but not in the other selectors 3.5.9. Filter Selector 3.5.9.1. Syntax [TECH] This one seems to have all our open issues in it!! 3.5.9.2. Semantics [OK] - modulo some changes if we revise 3.5.9.1 4. Expression Language [TECH] more open issues here. 5. IANA Considerations [TECH] I suggest application/jsonpath 6. Security Considerations [TECH] Having nothing here is unacceptable. Work item. 7. References 7.1. Normative References 7.2. Informative References [OK] I guess? On Thu, Oct 28, 2021 at 9:51 AM James wrote: > Folks, > IETF 112 is a few weeks away with our next meeting being held on > Wednesday, 10th of November from 12:00 to 14:00 UTC. If you haven=E2=80= =99t already > registered, you can do so here: > > https://registration.ietf.org/112/ > > We have only a few items on our agenda for this session: > > https://datatracker.ietf.org/doc/agenda-112-jsonpath/ > > If there=E2=80=99s any other subjects or issues you=E2=80=99d like to be = part of it please > email myself or Tim and we can include it. > > - J > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > --000000000000bf8c7a05cf6d451e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You= 'll note that on the draft agenda, there's an item labeled "Dr= af Status - Tim". =C2=A0

I went and took an end-to-end pass through the current draft, asking m= yself the question "How much work is left to finish this and send it o= ff to the IESG?" =C2=A0There's quite a bit, but less than I though= t.=C2=A0 To help us talk about this, I offer this annotated table-of-conten= ts, outlining what I think the draft status is section-by-section.

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

OK - Ready, mo= re or less
ED - Technically OK, needs editorial work
TECH - Open tech= nical issue(s)
BAD - Needs rewrite

Contributing

[BAD] - IE= TF style

1.=C2=A0 Introduction

[ED] - Lose 1st para, polish
1.1.=C2=A0 Terminology

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

1.2.=C2=A0 Inspired by XPath

[BAD] Just los= e it.=C2=A0 Put one sentence crediting XPath in the intro

1.3.=C2=A0= Overview of JSONPath Expressions

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

2.=C2=A0 JSONPath Examples

[OK] - May ne= ed to revisit if we change stuff

3.=C2=A0 JSONPath Syntax and Semant= ics
3.1.=C2=A0 Overview

[ED] - "no further errors=E2=80=A6&q= uot; language needs a little more expansion

3.2.=C2=A0 Processing Mo= del

[OK]

3.3.=C2=A0 Syntax

[OK]

3.4.=C2=A0 Sema= ntics

[OK]

3.5.=C2=A0 Selectors

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

3.5.1.=C2=A0 Root Select= or

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

3.5.2.=C2=A0 Dot Selector

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

3.5.3.=C2=A0 Dot Wild Card Selector
<= br>[OK]

3.5.4.=C2=A0 Index Selector

[OK]

3.5.5.=C2=A0= Index Wild Card Selector

[OK]

3.5.6.=C2=A0 Array Slice Selec= tor

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

3.5.7.=C2=A0 Descendant Selector

[ED] XML = history adds no value?

3.5.8.=C2=A0 Union Selector
3.5.8.1.=C2=A0= Syntax

[ED] - sloppy informal language

3.5.8.2.=C2=A0 Semant= ics

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

3.5.9.=C2=A0 Filter Se= lector

3.5.9.1.=C2=A0 Syntax

[TECH] This one seems to have al= l our open issues in it!!

3.5.9.2.=C2=A0 Semantics

[OK] - mod= ulo some changes if we revise 3.5.9.1

4.=C2=A0 Expression Language
[TECH] more open issues here.

5.=C2=A0 IANA Considerations
=
[TECH] I suggest application/jsonpath

6.=C2=A0 Security Consider= ations

[TECH] Having nothing here is unacceptable. Work item.
7.=C2=A0 References
7.1.=C2=A0 Normative References
7.2.=C2=A0 Infor= mative References

[OK] I guess?


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


We have only a few items on our agenda for this session:
<= br>

If there=E2=80=99s any other subjects or iss= ues you=E2=80=99d like to be part of it please email myself or Tim and we c= an include it.

- J
--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath
--000000000000bf8c7a05cf6d451e-- From ross.bundy@amobee.com Wed Oct 20 10:52: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 B443A3A10F5 for ; Wed, 20 Oct 2021 10:52:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.089 X-Spam-Level: X-Spam-Status: No, score=-2.089 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=amobee.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 NwAmVYaMNxTo for ; Wed, 20 Oct 2021 10:52:38 -0700 (PDT) Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B2693A0DE6 for ; Wed, 20 Oct 2021 10:52:27 -0700 (PDT) Received: by mail-lj1-x232.google.com with SMTP id w23so164745lje.7 for ; Wed, 20 Oct 2021 10:52:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amobee.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=QW79dm8+AIK1z14rZxoyz1511EhnEYaNLh3dIMmMuFk=; b=Gx02UgRPdM61W0DBzNSnk1mo7ABJ7Stm/Wb1zzE+sf9duyTA87qh3vAK+EwAxIE82j cV6cVeZSi6uy1l179ha6EPEdx2SndKtXRKk4x5gP2zzAiSBd/fkDVpv+2Z8wFauJIGSM Zm+rT0JI+aY67P+ZrogqFMVA2xMqwLnTJhRusRd+KrcNRZhL9YtEFl/ejoVgRKph6dVW vKErRZd/lsRazUBy9O9JTV3etKeT122FMOkfoxFZpCdwy9CE5+AdSyfmioobcWjgaq8J g8VZ3s/VJU+6yVjQYPZUGlabgANPGePmFb11eiQ+0YdBMWbiwBX2CJwCzdpXtMSS0RZI lynw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=QW79dm8+AIK1z14rZxoyz1511EhnEYaNLh3dIMmMuFk=; b=hEDRDlOU34rX9wgvoEA7EKACUU17KxC9r9eDFc7NoW92HAGWy29ObDnmeFATSuwXyB FYBzAQKfJtnM/UNJsSVaEMicP/ylyiYAPMtGbB77wBGtUZVzw5UwvjK0zhcjBDWxdqbl ytRwCSqEW1QXJtTWTw1niAI7wkRHaEuuSz7AvmNxdw0XTWh3LGaOmqYUW37itpL7NXDJ qAFSeJAUR4HT4PLQd0XDYtclDlxW3YnqCzhnKYwXogYs1SrsFdl4wQaxav4EYxZKAbre v6mKsCZltJlblKL6I4j318ztda26rb7lJx0DGMXkiLDsHP98wWrpmW2TXHLbLk5KgpnL EQOQ== X-Gm-Message-State: AOAM5306/bXeTaGi38219QgSbnnrlSZjhJg8Dx8aRvAXEM5WrNoj+BF0 OjmSvt5OEOuV1os0/rn0WRmdO6nxKydfP1AuwLCwjBM6VAFPEw== X-Google-Smtp-Source: ABdhPJwWsjGcgPoDRT1lcBakFDF2XC/VgdJvmFOWmJb2YM9LIKDiqSSGZhqH4kTsoL5s0GibKyeifncZqB5+vP2RaDE= X-Received: by 2002:a2e:750e:: with SMTP id q14mr546665ljc.338.1634752344121; Wed, 20 Oct 2021 10:52:24 -0700 (PDT) MIME-Version: 1.0 From: Ross Bundy Date: Wed, 20 Oct 2021 12:51:48 -0500 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000c47cb805cecc7020" Archived-At: X-Mailman-Approved-At: Fri, 29 Oct 2021 08:26:03 -0700 Subject: [Jsonpath] Regarding the draft of "JSONPath: Query expressions for JSON" 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, 20 Oct 2021 17:56:52 -0000 --000000000000c47cb805cecc7020 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable To Whom It May Concern, Re: https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-01.html I'm glad that this is becoming an RFC! A few comments regarding the draft... In one of the examples, is given the expression: $..book[(@.length-1)] which is intended to mean the last book in the list. The use of ".length" is confusing and perhaps limiting. It seems obvious that ".length" refers to metadata about the current element, @, and not to a child element of @, but in all other contexts, "." refers to a child element. The context about how to interpret the "." as metadata is provided by the surrounding expression engine characters, "(" and ")", which looks very similar to the filter expression characters, "?(" and ")", which allows to references to child elements, as shown in a later example: $..book[?(@.price<10)] The syntax between the expression engine and the filter expression, and the specification of child element references and metadata references, are too similar and, thus, visually confusing. Further, some future expansion of JSONPath might want to use an element name in the expression engine, but this creates a potential conflict if the JSON element is named "length". For example, given the structure: dimensions: { "length": 5, "width": 10, "height": 15 } does "(...@.length...)" refer to the "length" element or to the "length" metadata? Finally, the meaning of "length" as a metadata attribute of an element, and a description of what other metadata attributes which may be available, are not documented in the draft. I hope this helps. I'm excited to see this become and RFC. Regards, --Ross --=20 Ross E. Bundy Sr. Manager, Engineering 1800 South Oak St, Ste 209, Champaign, IL 61820* =C2=AD* ross.bundy@amobee.com* =C2=AD* [image: linkedin] --000000000000c47cb805cecc7020 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
To Whom It May Concern,

= Re: https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-01.html<= /div>

I'm glad that this is becoming an RFC!

A few comments regarding the draft...

In one of the examples, is given the expression:
$..book[(@.length-1)]
which is intended to = mean the last book in the list.

The use of ".= length" is confusing and perhaps limiting.

It= seems obvious that ".length" refers to metadata about the curren= t element, @, and not to a child element of @, but in all other contexts, &= quot;.<name>" refers to a child element. The context about how t= o interpret the ".<name>" as metadata is provided by the su= rrounding expression engine characters, "(" and ")", wh= ich looks very similar to the filter expression characters, "?(" = and ")", which allows to references to child elements, as shown i= n a later example:
=C2=A0$..book[?(@.p= rice<10)]

The syntax between the expression en= gine and the filter expression, and the specification of child element refe= rences and metadata references, are too similar and, thus, visually confusi= ng.

Further, some future expansion of JSONPath mig= ht want to use an element name in the expression engine, but this creates a= potential conflict if the JSON element is named "length". For ex= ample, given the structure:
dimensions= : {
=C2=A0=C2=A0=C2=A0 "length&qu= ot;: 5,
=C2=A0=C2=A0=C2=A0 "width= ": 10,
=C2=A0=C2=A0=C2=A0 "h= eight": 15
}
do= es "(...@.length...)" refer to the "length" element or = to the "length" metadata?

Finally, t= he meaning of "length" as a metadata attribute of an element, and= a description of what other metadata attributes which may be available, ar= e not documented in the draft.

I hope this helps.<= /div>

I'm excited to see this become and RFC.
<= div>
Regards,
--Ross

--
3D""--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.= ietf.org/mailman/listinfo/jsonpath
------=_Part_1524391_2139499739.1635537026223-- From nobody Sat Oct 30 01:07: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 81F943A0743 for ; Sat, 30 Oct 2021 01:07:24 -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 5Q82u1nGgjG4 for ; Sat, 30 Oct 2021 01:07:20 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D86F63A073E for ; Sat, 30 Oct 2021 01:07:19 -0700 (PDT) Received: from smtpclient.apple (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HhBjK2MFlz30bT; Sat, 30 Oct 2021 10:07:17 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: Carsten Bormann In-Reply-To: <886650584.1524392.1635537026226@mail.yahoo.com> Date: Sat, 30 Oct 2021 10:07:16 +0200 Cc: ross.bundy@amobee.com, jsonpath@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <3107B25C-883B-4A26-8893-91E9D5E47506@tzi.org> References: <886650584.1524392.1635537026226@mail.yahoo.com> To: Greg Dennis X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [Jsonpath] Regarding the draft of "JSONPath: Query expressions for JSON" 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, 30 Oct 2021 08:07:25 -0000 On 29. Oct 2021, at 21:50, Greg Dennis = wrote: >=20 > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/64 That=E2=80=99s a scary issue for a newcomer to look at :-) It=E2=80=99s meandering all over the place. This meandering is great for mailing list discussions to make sure that = all issue are uncovered, but our GitHub issues need to get more focused = than that so they stay actionable. Not sure #64 has resolved on anything re .length. BTW, the editors will step quickly through a sequence of PRs so we have = an updated draft by Nov 7 (when the I-D archive opens again). Tim=E2=80=99s list [1] is the most actionable input we have at this = time, but of course other reviews are welcome. You can see generated renderings, as well as various diffs, of the main = branch as well as recent PRs at [2]. Gr=C3=BC=C3=9Fe, Carsten [1]: = https://mailarchive.ietf.org/arch/msg/jsonpath/aaZpGsUIZD5fKZS2KMQjQEizDcA= [2]: https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/ From nobody Sat Oct 30 09:31:36 2021 Return-Path: X-Original-To: jsonpath@ietfa.amsl.com Delivered-To: jsonpath@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1563A1026 for ; Sat, 30 Oct 2021 09:31:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.227 X-Spam-Level: X-Spam-Status: No, score=-5.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-3.33, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xqPz60ij3ZrJ for ; Sat, 30 Oct 2021 09:31:29 -0700 (PDT) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.73]) (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 1F4B53A1025 for ; Sat, 30 Oct 2021 09:31:28 -0700 (PDT) Received: from [192.168.178.20] ([88.130.50.86]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MCsLu-1mY1Zl0uPo-008v3o; Sat, 30 Oct 2021 18:31:25 +0200 Content-Type: multipart/alternative; boundary="------------F6wwyixyQrZLP8c9tG3hDCYr" Message-ID: <49b28746-2e7e-6c7e-95de-30c7093b8956@goessner.net> Date: Sat, 30 Oct 2021 18:31:23 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 To: Tim Bray , James Cc: jsonpath@ietf.org References: <66A23529-8D13-4A03-95A3-7416AC6A747B@gmail.com> From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= In-Reply-To: X-Provags-ID: V03:K1:KXt94/fD3H0oBW71wM+KyT/cv59lQzjgqyJxN4U6dhdYC3XKd2H n2pefNJpnVjqi35MDk0c+B0VlP6HaERbBSiS9S4qpzgKD8/C0icPkz2V8/f5yiW58rpjqW8 TsUP7lNTxlB6kTAYAc0Yo5+jhAkz1nOqTGuwJbWT/pkv8dtxqYiC8v8PEZqTrtn+1T6YM/Z KCjITQheSDIA81exR49Mw== X-UI-Out-Filterresults: notjunk:1;V03:K0:1a01ly7btQs=:zR5++wrlIFw6fDqn5s2IW2 7/6yXzJBemFxJgZQu4oeSQt8JWdP2Ox2IwiHHuKu3Dypf/HDSTYpRhzL6fem/C6c1/XcgF2AQ Lt6XGwcZ4MFn+IwlMZlaE4qSLxKwMSDohSaeWEPV3y5Q4eX195KQjCpU8spmJTZTOvAl2ZE8u kF91M22BuBj7LyFero24Fw+DXFedyPaYoJQ0bs+O5Ilo2qHPTEHRumooWzHI/rEeLilti6RTx Mf8R/DZIhfgkRWoR27sC/VqcSsNcaO0Kk5Ilrb7L5S/Z52NtrvffF96WWbc1FoD23GM9B+3Cp wGiB3oHCid6m2EMB/Ki5NoQXW3R3gohFCxPVxsrIv/hc72cvKVwhDad35dB3mqKFlBgHXuKD8 pEzG1a6UFhMlyqXiVCGeregbhYEoOFFxEiQejcZEG0InE1s/JDXxA5Tku3pkRBnwGBtY55eW1 h/+NxwPWOvTMAeStepNHBJl/5LO462ZzFZAtHgrRr9dOfFMvVzv6d3a7WnsV2mz9nCm+AlCp1 zUlR9zafJy3ybX/Bc+qoQFyVDRgYkFN+wT/6h1c1GDiZpNGHDXnyQQkVKvtQPABNYy8brO+jb OHhc9WFW9f0n98mn7AMaMKfO8HzgUXe/uko+ncaqjAP1hrZXUb5/q4KEOk7p2WK/SbdscWznm o3+BdpafeylJgTZnVm1i2idFotmq/oWry8TZg0FAxdd8A5cN2+nq4HRL2nOLdPpQp8yE= Archived-At: Subject: Re: [Jsonpath] Next meeting at IETF 112 and agenda X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Oct 2021 16:31:35 -0000 This is a multi-part message in MIME format. --------------F6wwyixyQrZLP8c9tG3hDCYr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ... just to let you know ... I will be back on the list on Monday ... -- Stefan Am 28.10.2021 um 19:45 schrieb Tim Bray: > You'll note that on the draft agenda, there's an item labeled "Draf > Status - Tim". > > I went and took an end-to-end pass through the current draft, asking > myself the question "How much work is left to finish this and send it > off to the IESG?"  There's quite a bit, but less than I thought.  To > help us talk about this, I offer this annotated table-of-contents, > outlining what I think the draft status is section-by-section. > > Feel free to disagree or amplify, either right here, by raising issues > over on GitHub, or during our Nov 10 meeting. > ======================================= > Options for each section: > > OK - Ready, more or less > ED - Technically OK, needs editorial work > TECH - Open technical issue(s) > BAD - Needs rewrite > > Contributing > > [BAD] - IETF style > > 1.  Introduction > > [ED] - Lose 1st para, polish > > 1.1.  Terminology > > [OK] - May need to revisit if we change any of our terms > > 1.2.  Inspired by XPath > > [BAD] Just lose it.  Put one sentence crediting XPath in the intro > > 1.3.  Overview of JSONPath Expressions > > [ED] - lose XPath stuff, not sure about language about conversion to > bracket notation, that's internal to a processor, right? > > 2.  JSONPath Examples > > [OK] - May need to revisit if we change stuff > > 3.  JSONPath Syntax and Semantics > 3.1.  Overview > > [ED] - "no further errors…" language needs a little more expansion > > 3.2.  Processing Model > > [OK] > > 3.3.  Syntax > > [OK] > > 3.4.  Semantics > > [OK] > > 3.5.  Selectors > > [ED] - why is the ABNF up in 3.3 while the descriptions are here. > > 3.5.1.  Root Selector > > [ED] the "Semantics" section is confusing, I think we already said > what it does > > 3.5.2.  Dot Selector > > [ED] > > Should we have an example in each of these 3.5.* > Maybe a note about the dangers here, e.g. if you have something like { > "a.b": 23 } you can't use dot notation > > 3.5.3.  Dot Wild Card Selector > > [OK] > > 3.5.4.  Index Selector > > [OK] > > 3.5.5.  Index Wild Card Selector > > [OK] > > 3.5.6.  Array Slice Selector > > [ED] - Seems unnecessarily long, and the language about its history > adds no value? > > 3.5.7.  Descendant Selector > > [ED] XML history adds no value? > > 3.5.8.  Union Selector > 3.5.8.1.  Syntax > > [ED] - sloppy informal language > > 3.5.8.2.  Semantics > > [ED] in this place "Semantics" gets its own Table of Contents entry, > but not in the other selectors > > 3.5.9.  Filter Selector > > 3.5.9.1.  Syntax > > [TECH] This one seems to have all our open issues in it!! > > 3.5.9.2.  Semantics > > [OK] - modulo some changes if we revise 3.5.9.1 > > 4.  Expression Language > > [TECH] more open issues here. > > 5.  IANA Considerations > > [TECH] I suggest application/jsonpath > > 6.  Security Considerations > > [TECH] Having nothing here is unacceptable. Work item. > > 7.  References > 7.1.  Normative References > 7.2.  Informative References > > [OK] I guess? > > > On Thu, Oct 28, 2021 at 9:51 AM James wrote: > > Folks, > IETF 112 is a few weeks away with our next meeting being held on > Wednesday, 10th of November from 12:00 to 14:00 UTC. If you > haven’t already registered, you can do so here: > > https://registration.ietf.org/112/ > > We have only a few items on our agenda for this session: > > https://datatracker.ietf.org/doc/agenda-112-jsonpath/ > > If there’s any other subjects or issues you’d like to be part of > it please email myself or Tim and we can include it. > > - J > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath > > > > Virenfrei. www.avg.com > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > --------------F6wwyixyQrZLP8c9tG3hDCYr Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit ... just to let you know ... I will be back on the list on Monday ...
--
Stefan


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

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

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

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

Contributing

[BAD] - IETF style

1.  Introduction

[ED] - Lose 1st para, polish

1.1.  Terminology

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

1.2.  Inspired by XPath

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

1.3.  Overview of JSONPath Expressions

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

2.  JSONPath Examples

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

3.  JSONPath Syntax and Semantics
3.1.  Overview

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

3.2.  Processing Model

[OK]

3.3.  Syntax

[OK]

3.4.  Semantics

[OK]

3.5.  Selectors

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

3.5.1.  Root Selector

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

3.5.2.  Dot Selector

[ED]

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

3.5.3.  Dot Wild Card Selector

[OK]

3.5.4.  Index Selector

[OK]

3.5.5.  Index Wild Card Selector

[OK]

3.5.6.  Array Slice Selector

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

3.5.7.  Descendant Selector

[ED] XML history adds no value?

3.5.8.  Union Selector
3.5.8.1.  Syntax

[ED] - sloppy informal language

3.5.8.2.  Semantics

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

3.5.9.  Filter Selector

3.5.9.1.  Syntax

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

3.5.9.2.  Semantics

[OK] - modulo some changes if we revise 3.5.9.1

4.  Expression Language

[TECH] more open issues here.

5.  IANA Considerations

[TECH] I suggest application/jsonpath

6.  Security Considerations

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

7.  References
7.1.  Normative References
7.2.  Informative References

[OK] I guess?


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


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


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

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

3D""
Ross E. Bundy
Sr. Manager, Engineering <= /div>
=C2=A0=C2= =A01800 South Oak St, Ste 209, Champaign, IL 61820=E2=80=85=C2=AD
= =C2=A0=C2=A0ross.bundy@amobee.com=E2=80= =85=C2=AD
3D"lin=
--000000000000c47cb805cecc7020-- From nobody Fri Oct 29 12:50:42 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 BAE533A1663 for ; Fri, 29 Oct 2021 12:50:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.088 X-Spam-Level: X-Spam-Status: No, score=-2.088 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, T_REMOTE_IMAGE=0.01, 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 pWdbEUBC0OFO for ; Fri, 29 Oct 2021 12:50:36 -0700 (PDT) Received: from sonic315-14.consmr.mail.bf2.yahoo.com (sonic315-14.consmr.mail.bf2.yahoo.com [74.6.134.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 E291F3A1662 for ; Fri, 29 Oct 2021 12:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635537035; bh=nkOd6bvVhFsIyhvqA1HIOMiUr4yLp3nGh3XCPYJz+FE=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=beI6wZv+GOUADUjzr99swOymkVqaHZQTfZ7u5pijNSgn7NIR1UbUPI66y/cnriSpBMOK0b261kP4uN5ch5RaBIp1QyC6jceEdFEhi/4K5ehlG2kfsjhQKaTd4sDA1RVE/iPotvK53Twfq4TEFkGeL/YpkvgEOS05AbzJEdgvx8VWrVgGzCwTdpIPLrm8MWj1myFbjcmRxyBOfeh9tc5XCmSCzG3kQId0ajpk7f291t1O7cr1bWdohKeOMFYH0ZhrVCFxsmugHb47qIz9jdve28+IGdPkFCHka6tzYgtvcpqotXhrwcxZ0uxIGp9lyAolx/ydbTd4wo4UXqZAMV7ATQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1635537035; bh=1xxxonf5+THbNLxyIHQyojZfMFIJGAbaBz1QUW2DFnc=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=t2Y07ZHNTtmdOjUdyLseHvdO2oxTDhoqNHLT2pm5re9ee1okgH+Bj0sebyWzR2TcbCFK+XKUqiJ2XEmJHMGeyZzp6s+wbj5XNEFDzt5K0/hyphwro3wQK4IXx8x+DrTOK63nMePAhm2hXI8qOHcNeHBH+QiLZunNSNJvkPFevm0GRmHalqs5H9Rn6bEbXLIc55V7rZT1dYRGf+ItmfYpwSxIHC2XsNyY8whJu0QEsCKpLpy+oGzTt9TyF4I1QFkoCW3nTl7q/RmIMYukeS/1XrQbHVTTXcAHOh5kBvZr6K9yZkjIlFFRDdCU2VOTDq2+QU1ty10eraRiw77Fn41PDA== X-YMail-OSG: LZPvI1EVM1lT2Kv7Pzkg4KW2T1bg58h8KoCeX8cfF3pvQEpG2BmDpDdHubIExQq zztChAKsj_eo0LbeV1devEjwJCjy0bwaVMnVjpIl7l84IyfEPY79hWOeO5ymD6MoHtREvFmXErhQ cd4wvC0lb7I5aPe.cRatq8kAUoYZ25XHvzTbOt_DzmJhyZFQYwuFDKxFDsjxd66BsBnmXlWbDIIS .wztU0_wKeWY6Pyqcr0FpbTQ0zM6fcIyQoGGk8OuIDkzbxxHsxf_6bs48L7f5qHc6CI5np55tbnN cgNn_X0Gx3ElJXpwD8.ySevF4Jjq2XirfPh3F5HigZPCWNLNoJy3CFF0on.Z1a_OgunmbXyPjnCc 6Kz4_FkpN1Uap1EsZ7MGYwmiGbCxbbg.TaB.2fIvBF1MLyNek6hnPw_dxKCxkKjO.VcK.LB6cxB. wuEiQ5U78jg0uAldmwkXApqSGCCstHhBMOHE1LjizJ220Z.5q6LBUlMj1sjTOdk4.OVVKZxT1bfh .WgzPQciuLWO8lnkrf2llfafZVVJMlaBAqbV8LmTJ3tT3eTWXKla3Cwxn7DPzO.wuGk_QvQJaBwb DNMOPxAYgnuSt_8na7SU5PQgxgGrYEvHFGwqI78APL59MTZ4rNy9XaFxaANUYqgs0XWCRiVH5x1A wdtzoynUSY5au6_GTxNb09wHwND.TtXs6LvlmA8xm0BT0ZnupxptjJdq2JP327mbIGkxu4O7_GWJ ADIf_plo8dFQO.zOSofHIloaRuJEWy5QyjdTBUEVJC13XC7GPQJRZrFPwj.yTxoTbm6XNJ_Qe6ha Sn4IBALs2YXuCdOypz8eDU.tUJD2Hfeb_uSvOz1pBKHRv_7Hwe8_f4CN_MPHuRi57Os9EWJa3g9k cwwDwoh9cuUYUNWHnlU1bj5RJn6YTTzYAiXyTgYihPXNviG5fOZ1JPiZA2MG0S5oeSM7rbZYNyoK xLLyy_XCvVbE0Evltz94SuP4AdHdPKfJmMyQazC7OyvZJS2OU_nF73Y7tqpkoMzeYTB6HyOZRBxL P.SS0H2wybVRdZLIZrRYBfN7kZe4ry83cld8iV7U3LJ6tHRNkJ5EbyQPfeqfbDle3vcWvbbv1WE2 dOyC2ssI_ljZjcu39lk7pAizCluzI1VsCIhK8A5So3hQPrnx6ndAP7dCcU8xkKLtyZzbq4q_iICc jzaNduuH16m52MghawNke6a04f8yL4.STfYFbK_SxTjfigKgp6.0SWmRBV3B3BB6t7qBgFKQvk3s eR20xL7Gt8fKC3HIFZ.VTvg3fV4rVPMzJs1r.msEDcXOd8gZx0BDz3MdDTkzgGiPjMFzGkoG4d92 bbp_DGpJaX2TtlTJW2M8uByNXZP8DWHt5cOyjxys_rz12l75JomQTrs.IPhhxNRR6AeeAoa6q8Wv QDjBc.zDWyDzSunmpqVBag5njGy3R09niOFchpJqQYiydrG4a2h1wwsBe1un.3ljq1WNOpmo5X5v HsTsqBOKB1OH1BWkN2eFG8GWXVie.rZWKSNuJPgfQYPPePXwaP4EGNcgyRx2xzQZJIsAMH6I3hzW wz8xEaWhSspmL1xmTRlR9149Lw5Zzn8GLVJLVmArzARQI1n.TMc2LIa076WC_xP8b77MZpAiNfdq 11LWY58jZTZNi7u.oEZ2pcTrxVCyLAuPaVe.mqVS6XtPe2v_BHos3b3JA9du65qHQxmAbxNCywRg rDPmCucd1uIDh3t98Th5si1I.08S7nbsOxajEfqXpeVAzjXf3jGzdtLC8Mqskk_5t9rA4J7eh.M6 aqzIcIwkS1xuhXb3hGdCXmaGR2bRZc0fbac.hYw5FyNNeSsTufd3W7L.y_.xlMZoTgX4DqdqMTfL Bv_YbgxPerehEiazBbDjbvtk8vRmx6EgAhRlyOOyvTiSGulSiC_.CeHc0b2h3nHxjrTOhCwaUJxv kChanj2NSP1OmuFgBmvJ91Q9dwACYPrv641usPQoikmw94Dj59dVvksrgh2w71OI7zqNwx4Ea.C6 JVS_cC3AZD9JP7HII1XQ6cueocFO3nf1tNyVbDKiJBST9WAKtEOPrZQno_ElPG.IevddBbq._V4i LkebJXZoz9GC1B5zChppdpQuQMPhqCUlZtauOSwVst85p0tnQYgEtt51s6Pfwr5GRsthXXScwB5Q HhgsXonV2xZB9GP6Pj1GSRF8XiKWvcNokRpc9wUB62Xn66n0yAg_WT22sXHFlL3ZT7WT1Mvu9fIN ootDnERUFQiDpWN3hz8xmMBTGQFCS5LlnEvOrAH54vnFOTBEjCjWlN3EBPZ83Yfxj47JX79l6pNY W00LzMcV9HPygpfF0EeAvwbmkkGRYWrm0h9Fq..tM6fwVpIPNzLBSudm8Mdv14lVPZKtA1KqxFvh sArm6Zf5fsxM- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.bf2.yahoo.com with HTTP; Fri, 29 Oct 2021 19:50:35 +0000 Date: Fri, 29 Oct 2021 19:50:26 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: ross.bundy@amobee.com, jsonpath@ietf.org Message-ID: <886650584.1524392.1635537026226@mail.yahoo.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1524391_2139499739.1635537026223" X-Mailer: WebService/1.1.19198 YahooMailAndroidMobile Archived-At: Subject: Re: [Jsonpath] Regarding the draft of "JSONPath: Query expressions for JSON" 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, 29 Oct 2021 19:50:41 -0000 ------=_Part_1524391_2139499739.1635537026223 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hey there, Ross. Your sentient is certainly shared with those involved with the spec creatio= n. Please feel free to read and comment on this GitHub issue.=C2=A0 It's the m= ost recent place where we're discussing this. https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/64 Thanks for the input! Greg =20 =20 On Sat, 30 Oct 2021 at 4:26 am, Ross Bundy wrote: = To Whom It May Concern, Re: https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-01.html I'm glad that this is becoming an RFC! A few comments regarding the draft... In one of the examples, is given the expression: $..book[(@.length-1)]which is intended to mean the last book in the list. The use of ".length" is confusing and perhaps limiting. It seems obvious that ".length" refers to metadata about the current elemen= t, @, and not to a child element of @, but in all other contexts, "."= refers to a child element. The context about how to interpret the ".= " as metadata is provided by the surrounding expression engine characters, = "(" and ")", which looks very similar to the filter expression characters, = "?(" and ")", which allows to references to child elements, as shown in a l= ater example:=C2=A0$..book[?(@.price<10)]=20 The syntax between the expression engine and the filter expression, and the= specification of child element references and metadata references, are too= similar and, thus, visually confusing. Further, some future expansion of JSONPath might want to use an element nam= e in the expression engine, but this creates a potential conflict if the JS= ON element is named "length". For example, given the structure:dimensions: = {=C2=A0=C2=A0=C2=A0 "length": 5,=C2=A0=C2=A0=C2=A0 "width": 10,=C2=A0=C2=A0= =C2=A0 "height": 15 } does "(...@.length...)" refer to the "length" element or to the "length" me= tadata? Finally, the meaning of "length" as a metadata attribute of an element, and= a description of what other metadata attributes which may be available, ar= e not documented in the draft. I hope this helps. I'm excited to see this become and RFC. Regards,--Ross --=20 | | | | |=20 |=20 | | =20 | =20 | =20 | Ross E. Bundy Sr. Manager, Engineering | | | =20 | | | =C2=A0=C2=A01800 South Oak St, Ste 209, Champaign, IL 61820=E2=80=85=C2= =AD =C2=A0=C2=A0ross.bundy@amobee.com=E2=80=85=C2=AD | |=20 | | | | | | |=20 | | | | | | --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_1524391_2139499739.1635537026223 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hey there, Ross.

Your sentient is c= ertainly shared with those involved with the spec creation.

Please feel free to read and comment on this= GitHub issue.  It's the most recent place where we're discussing this= .


Thanks for the input!

Greg

On Sat, 30 Oct 2021 at 4:26 am, = Ross Bundy
<ross.bundy@amobee.com> wrote:
To Whom It May= Concern,


I'm glad that this is becoming an RFC!

A few comments regarding the draft...
In one of the examples, is given the expression:
$..book[(@.length-1)]
which is intend= ed to mean the last book in the list.

The use of "= .length" is confusing and perhaps limiting.

It see= ms obvious that ".length" refers to metadata about the current element, @, = and not to a child element of @, but in all other contexts, ".<name>"= refers to a child element. The context about how to interpret the ".<na= me>" as metadata is provided by the surrounding expression engine charac= ters, "(" and ")", which looks very similar to the filter expression charac= ters, "?(" and ")", which allows to references to child elements, as shown = in a later example:
 $..book[?(@= .price<10)]

The syntax between the expression = engine and the filter expression, and the specification of child element re= ferences and metadata references, are too similar and, thus, visually confu= sing.

Further, some future expansion of JSONPath m= ight want to use an element name in the expression engine, but this creates= a potential conflict if the JSON element is named "length". For example, g= iven the structure:
dimensions: {
    "length": 5,
    "width": 10,
    "height": 15
}
does "(...@.length...)" refer to th= e "length" element or to the "length" metadata?

Finally, the meaning of "length" as a metadata attribute of an element, a= nd a description of what other metadata attributes which may be available, = are not documented in the draft.

I hope this helps= .

I'm excited to see this become and RFC.

Regards,
--Ross

--
= <= td>
<= td style=3D"padding-top:0px!important;">
Ross E. Bundy
Sr. Manager, Engineering
  1800 South Oak St, Ste 209, Champaign, IL 61820=E2=80=85=C2=AD
  ross.bundy@amobee.com=E2=80=85=C2=AD
3D"linkedin"
Virenfrei. www.avg.com


--------------F6wwyixyQrZLP8c9tG3hDCYr--