Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-jsonpath-base-21> for your review
Carsten Bormann <cabo@tzi.org> Sat, 03 February 2024 00:56 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E96C14F6FA; Fri, 2 Feb 2024 16:56:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01] autolearn=unavailable autolearn_force=no
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 VoCkDZcHTV48; Fri, 2 Feb 2024 16:56:42 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 6FF06C14F68A; Fri, 2 Feb 2024 16:56:38 -0800 (PST)
Received: from smtpclient.apple (unknown [134.102.91.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4TRZ371NDMzDCg4; Sat, 3 Feb 2024 01:56:35 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5AB46EE0-BA9C-4C37-BA1E-FA47FD41EBEF@amsl.com>
Date: Sat, 03 Feb 2024 01:56:24 +0100
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Stefan Gössner <stefan.goessner@fh-dortmund.de>, Glyn Normington <glyn.normington@gmail.com>, jsonpath-ads@ietf.org, jsonpath-chairs@ietf.org, Tim Bray <tbray@textuality.com>, superuser@gmail.com, auth48archive@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DD56C57-47EB-4836-B81C-C1B65A64BC2E@tzi.org>
References: <20240130062410.D02DF1E64A@rfcpa.amsl.com> <8DDA3557-E82D-4A29-9AFA-DDD82BBA13B2@tzi.org> <CCBE94F3-C800-42E0-AB15-4B6C11F46E86@tzi.org> <5AB46EE0-BA9C-4C37-BA1E-FA47FD41EBEF@amsl.com>
To: Alanna Paloma <apaloma@amsl.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/yhwBTDJI7_p5Eeqko8u54B0F8VA>
Subject: Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-jsonpath-base-21> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Feb 2024 00:56:49 -0000
Hi Alanna,
we have now started to check the edits that didn’t have specific questions attached to them.
Our comments on these will come in several installments; below is the first.
Grüße, Carsten
1. (We are still discussing this one.)
2. The change in 2.1.2 starting "In turn, a segment operates" loses the sense of the original text (the sequential processing of the input nodelist, each of the nodes in the input nodelist in turn). Please revert this change.
3. In 2.1.2, the change starting "If a query produces a nodelist with more than one possible ordering" loses the sense of the original text (the possibility of a query producing non-deterministic results). Clearly any nodelist with more than one distinct element can be re-ordered, but the point is about a query that may produce a number of different nodelists with distinct orderings. Please revert this change.
Or possibly use this version:
Original:
If a query may produce a nodelist with more than one possible
ordering, a particular implementation may also produce distinct
orderings in successive runs of the query.
Suggested:
If the semantics of a query gives an implementation a choice of
producing multiple possible orderings, a particular implementation may
produce distinct orderings in successive runs of the query.
4. In 2.1.3, the parenthesis should be deleted as it is irrelevant to the example. A note should instead be added to section 2.3.2.2.
Section 2.1.3
OLD:
Next, [*] selects all its elements (for an object input node, it would select all its member values but not the member names) from any array input node.
NEW:
Next, [*] selects all the elements from the input array node.
Section 2.3.2.2
OLD:
A wildcard selector selects the nodes of all children of an object or array. The order in which the children of an object appear in the resultant nodelist is not stipulated, since JSON objects are unordered. Children of an array appear in array order in the resultant nodelist.
NEW:
A wildcard selector selects the nodes of all children of an object or array. The order in which the children of an object appear in the resultant nodelist is not stipulated, since JSON objects are unordered. Children of an array appear in array order in the resultant nodelist.
Note that the children of an object are its member values, not its member names.
5. It is very unfortunate that Table 5 has been reformatted such that some queries and result paths now include line breaks. This obscures the values of these queries and result paths. Some other solution must be found.
(See also our comment on the NBSP characters lost in the source for the “j j” construction.)
6. Section 2.3.5.2.2 was changed to add "a" to the phrase "normal mathematical equality". We think this is distracting because it raises the possibility that there is more than one mathematical equality (and indeed there is, but here we mean the one with which everyone is familiar). Please revert this change.
7. In section 2.3.5.2.2 an "or" was added to the list (second sub-bullet) following the bullet beginning "A comparison using the operator < yields true". Since all the items in the list are simultaneously true, an "and" should be added instead of an "or”.
OLD:
- the empty string compares less than any non-empty string, or
NEW
- the empty string compares less than any non-empty string, and
8. In section 2.5.1.2 the last two paragraphs were combined. This is misleading as the general observation in the last paragraph (of a child segment drilling down) is not related to the ordering discussion in the last but one paragraph. Please revert this change.
Original (to be reverted to):
Where a selector can produce a nodelist in more than one possible
order, each occurrence of the selector in the child segment may
evaluate to produce a nodelist in a distinct order.
So a child segment drills down one more level into the structure of
the input value.
Current, incorrectly merged paragraph:
Where a selector can produce a nodelist in more than one possible
order, each occurrence of the selector in the child segment may
evaluate to produce a nodelist in a distinct order. Thus, a child
segment drills down one more level into the structure of the input
value.
Potential alternative suggestion:
Where a selector can produce a nodelist in more than one possible
order, each occurrence of the selector in the child segment may
evaluate to produce a nodelist in a distinct order.
In summary, a child segment drills down one more level into the
structure of the input value.
- [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-jsonp… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Stefan Gössner
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Glyn Normington
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Stefan Gössner
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Glyn Normington
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Carsten Bormann
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Glyn Normington
- [auth48] [AD] Re: AUTH48: RFC-to-be 9535 <draft-i… Alanna Paloma
- Re: [auth48] [AD] Re: AUTH48: RFC-to-be 9535 <dra… Glyn Normington
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Carsten Bormann
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Carsten Bormann
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Alanna Paloma
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Glyn Normington
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Stefan Gössner
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Alanna Paloma
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Glyn Normington
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Alanna Paloma
- [auth48] [IANA] AUTH48: RFC-to-be 9535 <draft-iet… Alanna Paloma
- [auth48] [IANA #1359486] [IANA] AUTH48: RFC-to-be… Sabrina Tanamal via RT
- Re: [auth48] [IANA #1359486] [IANA] AUTH48: RFC-t… Alanna Paloma
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Murray S. Kucherawy
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Glyn Normington
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Alanna Paloma
- Re: [auth48] [AD] AUTH48: RFC-to-be 9535 <draft-i… Glyn Normington
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Alanna Paloma
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Glyn Normington
- Re: [auth48] AUTH48: RFC-to-be 9535 <draft-ietf-j… Alanna Paloma
- [auth48] [final question - emoji color] Re: AUTH4… Sandy Ginoza
- Re: [auth48] [final question - emoji color] Re: A… Glyn Normington
- Re: [auth48] [final question - emoji color] AUTH4… Carsten Bormann
- Re: [auth48] [final question - emoji color] AUTH4… Carsten Bormann
- Re: [auth48] [final question - emoji color] AUTH4… Sandy Ginoza
- Re: [auth48] [final question - emoji color] AUTH4… Carsten Bormann
- Re: [auth48] [final question - emoji color] AUTH4… Glyn Normington
- Re: [auth48] [final question - emoji color] AUTH4… Sandy Ginoza
- Re: [auth48] [final question - emoji color] AUTH4… Glyn Normington
- Re: [auth48] [final question - emoji color] AUTH4… Stefan Gössner
- Re: [auth48] [final question - emoji color] AUTH4… Carsten Bormann