IETF Logo Mail Archive

Re: [Jsonpath] IETF JSONPath Implementation in Rust

Glyn Normington <glyn.normington.work@gmail.com> Sun, 12 November 2023 13:49 UTC

Return-Path: <glyn.normington.work@gmail.com>
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 9BFF9C137368 for <jsonpath@ietfa.amsl.com>; Sun, 12 Nov 2023 05:49:17 -0800 (PST)
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 drZ7RODNNA6F for <jsonpath@ietfa.amsl.com>; Sun, 12 Nov 2023 05:49:14 -0800 (PST)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 08C91C1705FA for <jsonpath@ietf.org>; Sun, 12 Nov 2023 05:49:14 -0800 (PST)
Received: by mail-pg1-x52c.google.com with SMTP id 41be03b00d2f7-5b9a7357553so2792364a12.0 for <jsonpath@ietf.org>; Sun, 12 Nov 2023 05:49:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699796953; x=1700401753; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MrtmKS9PVXtnlN0DwgUjRKNt/KfUTZgANL4atKxyBKA=; b=dEG6ao3+L31/BAWSTt1BbWvYj6HHjRHdmHR0WVDR7UZ/KJYtNqFrcDGW9tSmwAQNCt 78xbl7fjn2plc59JqEmUYYUCGXL8G6mH/hZ95jC1QQMU66O3sYxv3L/Gih+bAOa7dDrI 3lAj9pq9bQS+ku875yKtZ83gPT5Oi/0wakXOGJXY5hclNUzHOvtSol1hR7NqXoF8+uQA FpJGTKzssH2TqxFFHSL3Rw3xqeHOtOtP6VRqN8j2wrFZp/MV9cYRvSqsG8pKNpt8IqNq e47pyb1an9a0JF/Nz5WHpgjo6TUeSXP/w2ZIMHb7YOuW3ReJZaBUS1keZQ6aBhWZ9JWm nxYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699796953; x=1700401753; 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=MrtmKS9PVXtnlN0DwgUjRKNt/KfUTZgANL4atKxyBKA=; b=cV4x39B5UaIKwq0Cs/KuGjoLjyZtY1llPO8zP4aJlhkvXcuyF6yWLRPIcAZMO1Gh26 tMeEdX58WBElb/2oqCY0V641ECSc/9NnCsqujlkDHANizCGetYfTU5iC+BIsuOzl+g7O nqdNZ/TFPkDHQFL3lyCupb0hApvWPYKuIi0LuiQGuoSC3NF2K/SP5HN66j8SCHeAfY5s 6x7y2YpoE/jlYtyz2H0WmIfdcxsZwP6+PGx+ck5HGb7SmTgc61rrh8CLUA8D82IOZA6u QnCWj0ykO7R9Flo8afm+0zPbEp6j4vCofMBrPp9XOBkWWUtx1xCqgsNtAhMSssGgahQf cA9w==
X-Gm-Message-State: AOJu0Yw2k7WK3kJjU2hOFmiCvmzIBlGUye/oVDjM0xNuCOzNs+7VtVLR c+IPrKx3cr6Y5gu0nOwskOoK8G9otSwfjl1KIkdL2t+8
X-Google-Smtp-Source: AGHT+IH8Q2XE/GcKXJq219EpTsJ3Vu9EWQDBtlqq/ov2OCBVBAn1+866I0v6hn2NOU9KoP/V1jxnco2WiiZ9d0v7yOU=
X-Received: by 2002:a17:90b:4f81:b0:280:682d:cb2 with SMTP id qe1-20020a17090b4f8100b00280682d0cb2mr4660680pjb.1.1699796953077; Sun, 12 Nov 2023 05:49:13 -0800 (PST)
MIME-Version: 1.0
References: <CABN7U=q1SB8Pup8s+by_1YnAT65RFGeGfufu_8R-jPLS-TJnHQ@mail.gmail.com> <CANH0GbLAQ_+-kTQyURnFUzmud7BEzvMvCD3OYWfYMg4VU5gqcg@mail.gmail.com> <CABN7U=rJpAdjmSLp=ZBL31J8j6a4dqKuN45cQ51uUKdJ1rtqfg@mail.gmail.com>
In-Reply-To: <CABN7U=rJpAdjmSLp=ZBL31J8j6a4dqKuN45cQ51uUKdJ1rtqfg@mail.gmail.com>
From: Glyn Normington <glyn.normington.work@gmail.com>
Date: Sun, 12 Nov 2023 13:49:01 +0000
Message-ID: <CANH0Gb+sPi7nxkPSft3NWYrWmRGQHgtoZKuLZFLF3NXOR47qzg@mail.gmail.com>
To: Trevor Hilton <trevor.hilton@gmail.com>
Cc: jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="000000000000941f410609f4d1bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/nHxxj1_67Z1T4rILR1RAACYgrfE>
Subject: Re: [Jsonpath] IETF JSONPath Implementation in Rust
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 <jsonpath.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jsonpath/>
List-Post: <mailto:jsonpath@ietf.org>
List-Help: <mailto:jsonpath-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Nov 2023 13:49:17 -0000

Sounds good. Please note the CTS is unofficial and incomplete (e.g. doesn't
test for non-determinism allowed in the spec), but useful nevertheless.

On Sun, 12 Nov 2023, 13:45 Trevor Hilton, <trevor.hilton@gmail.com> wrote:

> Hi Glyn,
>
> That is okay. For now, I will clearly mention the RFC alongside JSONPath
> in the README/documentation.
>
> JSONPath also has the compliance test suite (CTS), which I think is fairly
> robust at this point, but understand is still under active development. I
> may open an issue/discussion on the CTS repository about this. I think it
> is worth acknowledging the CTS and that the implementation is compliant
> with it.
>
> Cheers,
> Trevor.
>
> On Sun, Nov 12, 2023 at 8:34 AM Glyn Normington <
> glyn.normington.work@gmail.com> wrote:
>
>> Hi Trevor
>>
>> Thanks for your post and for your work on implementing the JSONPath spec.
>>
>> You wrote:
>>
>> "One question for the group: is there any guideline on how to include
>> compliance/conformance statements in the implementation documentation?"
>>
>> It appears not.
>>
>> Regards,
>> Glyn
>>
>> On Wed, 8 Nov 2023, 01:26 Trevor Hilton, <trevor.hilton@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> First off, congratulations to the group on getting JSONPath
>>> to standardization, it has been a pleasure following the progress and
>>> working with and implementing the document.
>>>
>>> I wanted to let the group know about the IETF JSONPath implementation
>>> that I built for the Rust Programming Language, called serde_json_path [1].
>>> It has been compliant since the v0.6.0 release in April of this year, and
>>> has been downloaded almost 9,000 times since initial release.
>>>
>>> Several open-source projects have started using it, including one
>>> popular one called Arroyo [2], and some others. So, the standard is getting
>>> out there in the Rust world.
>>>
>>> One question for the group: is there any guideline on how to include
>>> compliance/conformance statements in the implementation documentation?
>>>
>>> I am awaiting the official RFC to update the docs for serde_json_path
>>> with a note on conformance/compliance.
>>>
>>> Regards,
>>> Trevor.
>>>
>>> [1] - https://github.com/hiltontj/serde_json_path
>>> [2] - https://www.arroyo.dev/
>>> --
>>> JSONpath mailing list
>>> JSONpath@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jsonpath
>>>
>>

v2.23.0 | Report a Bug | By Email