IETF Logo Mail Archive

Re: [Jsonpath] IETF JSONPath Implementation in Rust

Trevor Hilton <trevor.hilton@gmail.com> Sun, 12 November 2023 13:45 UTC

Return-Path: <trevor.hilton@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 3243DC1705FA for <jsonpath@ietfa.amsl.com>; Sun, 12 Nov 2023 05:45:14 -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 YGZl0hc8mTLX for <jsonpath@ietfa.amsl.com>; Sun, 12 Nov 2023 05:45:10 -0800 (PST)
Received: from mail-oa1-x36.google.com (mail-oa1-x36.google.com [IPv6:2001:4860:4864:20::36]) (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 1F011C1705EE for <jsonpath@ietf.org>; Sun, 12 Nov 2023 05:45:10 -0800 (PST)
Received: by mail-oa1-x36.google.com with SMTP id 586e51a60fabf-1f04c5ed8d7so2282645fac.1 for <jsonpath@ietf.org>; Sun, 12 Nov 2023 05:45:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699796709; x=1700401509; 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=xk+AqfsyEb0H5ixdp12rnCI3R82LrOALuSEPGSznYz8=; b=XWZblXaP+fF2tpmWsTS2OfnBy7iUfSKXk6HgPGxVEEaRqe1pUwTgf6PzJCV1+GRKOC 6GNjR/mYhJm6qI13pLwhR9nQkBjhSyfTHb12r8nOORQX00QvxKcIP5X4dWGuHn5te/cC ca5/6VcSJBQl719gro8YFwzm3JQswUxZeuyqatdiu0R+skGlJUq3C60XRIuqCqge9SVd m61VbSC+vYKrpD1/GdM3+5jMqpLxgL2huLY41yu61wlu/lUwWi471/5srTbqLz1TKBIM Hfu9ubBrtYjET7JXeZFTSRqAoD+vv24fbo69N1Kr1y9UH7z0FW335wiayhQlPhLI+ms5 dWog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699796709; x=1700401509; 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=xk+AqfsyEb0H5ixdp12rnCI3R82LrOALuSEPGSznYz8=; b=jTJTuIqHqrvDDYsx1bczPx4/tyXCd2DKaOtHI6orJUqfiM5nsIMWkgPEQVQh8uW6Em Agg79G0s5HEgkEZWFtrKotLN8PbifhUfsNIlcW2WNqrQBku2mb0zHIpudYRfL1c+mL5X 8fwTGcf7pbXLBJqwB7rPPGGvVYNIQLHVCD3Sdq89B2znO5z3hCCdwt58WVKf9nW8LsGu Jk9cvlvPatudoa9GoOcIWsMQPJ4S7amjrXc8GuQpeZ80M1wepZCP9NzXt2tsDtwgmytF hyoAZZW7LHL/6seW50YAk4qLMHZ0xSetNssG0A9v0Jyj72L0fU1qi8+ajjJFD36/cM78 6Jiw==
X-Gm-Message-State: AOJu0YwwrnJOOgB6AVVNsGkXZmqu7xfk+XVRZ1Ut4Av7nzLti+HnZfco R8q3oWUnEB9r+T1TlvEgRvMqjXoPpu9QYRFOv7Xq0+j0
X-Google-Smtp-Source: AGHT+IHC6msuzC8HWgFeBkuRuUIiS6x0gv4XGSfexNPauSNLsjWyflt4Kw1q9ARYfq139oKpHB//wghNz17eg8PBHmA=
X-Received: by 2002:a05:6870:5490:b0:1ef:b591:5733 with SMTP id f16-20020a056870549000b001efb5915733mr6191738oan.15.1699796708688; Sun, 12 Nov 2023 05:45:08 -0800 (PST)
MIME-Version: 1.0
References: <CABN7U=q1SB8Pup8s+by_1YnAT65RFGeGfufu_8R-jPLS-TJnHQ@mail.gmail.com> <CANH0GbLAQ_+-kTQyURnFUzmud7BEzvMvCD3OYWfYMg4VU5gqcg@mail.gmail.com>
In-Reply-To: <CANH0GbLAQ_+-kTQyURnFUzmud7BEzvMvCD3OYWfYMg4VU5gqcg@mail.gmail.com>
From: Trevor Hilton <trevor.hilton@gmail.com>
Date: Sun, 12 Nov 2023 08:44:57 -0500
Message-ID: <CABN7U=rJpAdjmSLp=ZBL31J8j6a4dqKuN45cQ51uUKdJ1rtqfg@mail.gmail.com>
To: Glyn Normington <glyn.normington.work@gmail.com>
Cc: jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000307df0609f4c33e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/xIJmYi5IPx8yVbYZqs5UUXEVJyI>
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:45:14 -0000

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