From nobody Thu Aug 10 13:49:31 2023 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 BC758C151987; Thu, 10 Aug 2023 13:49:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.104 X-Spam-Level: X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7gw_LS2ZaWUj; Thu, 10 Aug 2023 13:49:24 -0700 (PDT) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCA6DC14CEED; Thu, 10 Aug 2023 13:49:24 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-52340d9187aso1619893a12.3; Thu, 10 Aug 2023 13:49:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691700563; x=1692305363; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QzCaUj9Jp3+eqz3OUlbsC4KvtPT6Py2iWFTPY79gU4I=; b=GRqyv+HcQ8fc3wyhQeRuWkU8BhdTB9cGtVhttW6RMJMRac/MlnswRCWvr3r2H1EuVY 8f6XyuQ+vIhWwJHcevAdH8011PpvMv6vcBMhBMD6xiG6L8Ayzgrd03gp7wfMmQxVyO2q bYBtDemIGR4M1Cf5BHrl7DRmfz3BteXiNHf4YcATLry9KxVYeltaniPvqagwC0HHft0N eAbIHOQuIhcNgTh8bBo7NMNhdWQye0TcFiBhhCeoJQKfwEKqvrSKnMY3yNC3NzLgbLt6 kuUm4IXbGM+HMLrsVh2bHiHoVFwWhVu1y4rgi39Jk+yPFqnNkhm4Yry64dDgvbr0/DUX DTEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691700563; x=1692305363; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QzCaUj9Jp3+eqz3OUlbsC4KvtPT6Py2iWFTPY79gU4I=; b=N+EGKGN0ShI1HjzU+WNVShy0nfN7pnxeFJ6vUnq4ythPxo/XhRLsAWmwHLwAar7HML 9TEhQUTGt8h8mztjkhYB6QX+qo/iE28K3Kwn88RbgmMtVm0EfDEcNPBe5u9AcatSXUMU 2wA+fAvrXV0cD0hGOxu5QxWCBbpomKv5h3DvCR9jk8PShUwMsmmbp7bHSTuUTZxB5TFA DAh3J3ctypkSYwIjxeFr9Qbm80+LZJqCVuFXos/PdHtOfJE5m4JBMEg/9jRsWjUNGQj8 x67y5FI733Mi33Og/z0gdgZuQRN0SGnxWGQPLddnusRZ5XVuDN7C5xMm5NtUxadZ/YiP Vb9g== X-Gm-Message-State: AOJu0YzqZMayESEqWcddZp9h9w2lyUwM4AJ+XjIS5lBoy7PqGpFMP0qm sQDrSNh9yKlQNt6P0a52MmmlOxkKJmc0w8ua+hM= X-Google-Smtp-Source: AGHT+IH+ogUedLO84LGm/LDSxYqksvvmNb4BFA6zLegE3OYTITIDDzU79PAuzFKiT/UZ/jsr0vgO8bmA8k6ff2t4q+A= X-Received: by 2002:a05:6402:14d7:b0:523:4d60:71c0 with SMTP id f23-20020a05640214d700b005234d6071c0mr88774edx.33.1691700563002; Thu, 10 Aug 2023 13:49:23 -0700 (PDT) MIME-Version: 1.0 References: <169169150183.43222.18081751127010886819@ietfa.amsl.com> <2A26E027-BB60-4423-8DFC-6A5200795CFF@gmail.com> In-Reply-To: <2A26E027-BB60-4423-8DFC-6A5200795CFF@gmail.com> From: Rob Sayre Date: Thu, 10 Aug 2023 13:49:11 -0700 Message-ID: To: James Cc: Linda Dunbar , gen-art@ietf.org, draft-ietf-jsonpath-base.all@ietf.org, jsonpath@ietf.org, last-call@ietf.org Content-Type: multipart/alternative; boundary="0000000000001fcedf060297bbd8" Archived-At: Subject: Re: [Jsonpath] [Last-Call] Genart last call review of draft-ietf-jsonpath-base-17 X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.39 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, 10 Aug 2023 20:49:28 -0000 --0000000000001fcedf060297bbd8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I also object. This document is better than most IETF documents. I don't understand the GenArt review here, and I know more about JSON than most humans on earth. thanks, Rob On Thu, Aug 10, 2023 at 1:14=E2=80=AFPM James wrote: > (speaking only for myself here as a JSON Path enthusiast) > > Thank you for your review, but I strongly disagree and I'm concerned > you've misunderstood the purpose of the document and its aims for > extensibility and interoperability. To reply to the three points you have > raised: > > 1. The document aims to define a way of querying, without modification to > existing JSON specifications and to do so with interop in mind. Could you > please elaborate why Standards Track is not appropriate for a document wi= th > those goals, and what requisites have not been met? > > 2. The document includes extensibility to reduce any need for changes to > syntax and thus help with ongoing interoperability of queries between > implementations. Should someone propose new syntax to represent the > traversal of JSON structures in the future that would not fit within the > proposed extensions model, then a new version of the specification could = be > written. > > 3. The IANA registry is intended to avoid collisions in extension names > that may result in two different implementations having impactful > differences in behaviour. > > I hope this provides further clarity. > > - J > > > On 10 Aug 2023, at 20:18, Linda Dunbar via Datatracker > wrote: > > > > Reviewer: Linda Dunbar > > Review result: Not Ready > > > > I am the assigned Gen-ART reviewer for this draft. The General Area > > Review Team (Gen-ART) reviews all IETF documents being processed > > by the IESG for the IETF Chair. Please treat these comments just > > like any other last call comments. > > > > For more information, please see the FAQ at > > > > . > > > > Document: draft-ietf-jsonpath-base-17 > > Reviewer: Linda Dunbar > > Review Date: 2023-08-10 > > IETF LC End Date: 2023-08-09 > > IESG Telechat date: Not scheduled for a telechat > > > > Summary: > > > > The document specifies a method to parse the JSON objects to get values > and > > specifies the syntax to retrieve a list of values. The document reads > well. > > However, like any software programs, errors can be encountered at run > time even > > after careful review. > > > > Major issues: > > The major issue is that this document should not be =E2=80=9CStandard T= rack=E2=80=9D > because: > > 1. Existing parsers for JSON data don=E2=80=99t need to change to = comply > with the > > syntax specified in this document. 2. Like SQL, this document > specified > > syntax may change as more ways being developed by implementers to parse > the > > JSON objects. 3. It is not clear why IANA registration is needed. > > > > Minor issues: > > > > Nits/editorial comments: > > > > Thanks, Linda Dunbar > > > > > > -- > last-call mailing list > last-call@ietf.org > https://www.ietf.org/mailman/listinfo/last-call > --0000000000001fcedf060297bbd8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I also object.

This document is better = than most IETF documents. I don't understand the GenArt review here, an= d I know more about JSON than most humans on earth.

thanks,
Rob


On Thu, Aug 10, 2023 at 1:14=E2= =80=AFPM James <james.ietf@gmail= .com> wrote:
(speaking only for myself her= e as a JSON Path enthusiast)

Thank you for your review, but I strongly disagree and I'm concerned yo= u've misunderstood the purpose of the document and its aims for extensi= bility and interoperability. To reply to the three points you have raised:<= br>
1. The document aims to define a way of querying, without modification to e= xisting JSON specifications and to do so with interop in mind. Could you pl= ease elaborate why Standards Track is not appropriate for a document with t= hose goals, and what requisites have not been met?

2. The document includes extensibility to reduce any need for changes to sy= ntax and thus help with ongoing interoperability of queries between impleme= ntations. Should someone propose new syntax to represent the traversal of J= SON structures in the future that would not fit within the proposed extensi= ons model, then a new version of the specification could be written.

3. The IANA registry is intended to avoid collisions in extension names tha= t may result in two different implementations having impactful differences = in behaviour.

I hope this provides further clarity.

- J

> On 10 Aug 2023, at 20:18, Linda Dunbar via Datatracker <noreply@ietf.org> wrote:<= br> >
> Reviewer: Linda Dunbar
> Review result: Not Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area > Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.=C2=A0 Please treat these comments just=
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://wiki.ietf.org/en/group/gen/GenArtFAQ>.
>
> Document: draft-ietf-jsonpath-base-17
> Reviewer: Linda Dunbar
> Review Date: 2023-08-10
> IETF LC End Date: 2023-08-09
> IESG Telechat date: Not scheduled for a telechat
>
> Summary:
>
> The document specifies a method to parse the JSON objects to get value= s and
> specifies the syntax to retrieve a list of values. The document reads = well.
> However, like any software programs, errors can be encountered at run = time even
> after careful review.
>
> Major issues:
> The major issue is that this document should not be =E2=80=9CStandard = Track=E2=80=9D because:
> 1.=C2=A0 =C2=A0 =C2=A0 Existing parsers for JSON data don=E2=80=99t ne= ed to change to comply with the
> syntax specified in this document. 2.=C2=A0 =C2=A0 =C2=A0 Like SQL, th= is document specified
> syntax may change as more ways being developed by implementers to pars= e the
> JSON objects. 3.=C2=A0 =C2=A0 =C2=A0 It is not clear why IANA registra= tion is needed.
>
> Minor issues:
>
> Nits/editorial comments:
>
> Thanks, Linda Dunbar
>
>

--
last-call mailing list
last-call@ietf.org<= /a>
https://www.ietf.org/mailman/listinfo/last-call
--0000000000001fcedf060297bbd8--