IETF Logo Mail Archive

Re: [Jsonpath] JSONPath draft charter

Glyn Normington <normingtong@vmware.com> Wed, 02 September 2020 09:29 UTC

Return-Path: <normingtong@vmware.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 AFBAB3A0F49 for <jsonpath@ietfa.amsl.com>; Wed, 2 Sep 2020 02:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=vmware.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 0tUZaNVeUIjT for <jsonpath@ietfa.amsl.com>; Wed, 2 Sep 2020 02:29:46 -0700 (PDT)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2074.outbound.protection.outlook.com [40.107.92.74]) (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 7DE913A0F48 for <jsonpath@ietf.org>; Wed, 2 Sep 2020 02:29:46 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nztgT2AtujkWNk+tKEbX/yxW7hivysqlVI5MIJh3qn8Usy4AbucjcyxjUYYenLG81fKgYtCIPRnIY7oUZnKOvB3/Wf1NI+ZZu72M9CfvCrwdWtkeBLJ6YTD1Q1jYnNddI7y/4f1mg610TfHteMMB3duU25hfye9dUurYUw8y9sPaTozcK2cuHHTDw0NlaCF8afILZ+Yoyst4qYGrwECsP2BivYDNJCdTpvKy2ZWfiK5D94Skq9YmN4hgf8ajCawr1hoTw55iGYl3zxmzbFYOBlzgus5Zcw0YYIWH8Wm1CqfdCmsJVvHIEKD65P+UlyxXZLGA6wIshccDWAVHAObLCQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=axb7GTyK5ktasX8JHRVX7Svqik9ztPRMW4A02GLoLtQ=; b=fgP6gAXoi8UrJLJ+srpyoglfh5MSqtnBNlm7U0XdMbE4Zb3GCFdT9AUirVmxAvZB6GoHZPNgNGC/yJCQZqQ0wV/wGQU/FH6KEkkXmfuSpR8ZM/uoK6pLCNzbtHOYzv/8r/J/s59iYz6+KJ2HXeQ46LIS982gvaZB7vNjD22wqoXtji9f5sX+VWdtgEYN3ABnjuZNWrmhUNyqtI6QXndyaxuEDjoUMoXvx8vShIowAVq488/JQd2GwMN+6H58gixvo3bk8YbYC+Ab9nRQOSXnSXGR/CO+QsD/eUuT5XekXVfX7r2WV+2niVNAH5vVbcAgn4LuVZ6TzyGBPn0ulk5ywQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=vmware.com; dmarc=pass action=none header.from=vmware.com; dkim=pass header.d=vmware.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vmware.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=axb7GTyK5ktasX8JHRVX7Svqik9ztPRMW4A02GLoLtQ=; b=P373ggZJ+XbYTJqfkeL2TDyg+NNdWN6jnoVP0qy7jNT8VQ8UV2iMeQOGouFKEOQ4PLVVe8+/jmfQQKWUKWUHrVLxhYJ5hSY8AjWJJ7F68x23wnEVCWJ1V5INTCQ243igW7BhKCGDIRJj+eCFRdC8T/T1KqYr9Jz/QTtBEyZbjAU=
Received: from DM5PR0501MB3766.namprd05.prod.outlook.com (2603:10b6:4:7c::29) by DM6PR05MB5948.namprd05.prod.outlook.com (2603:10b6:5:105::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.6; Wed, 2 Sep 2020 09:29:37 +0000
Received: from DM5PR0501MB3766.namprd05.prod.outlook.com ([fe80::1079:7a1f:90f9:2c8f]) by DM5PR0501MB3766.namprd05.prod.outlook.com ([fe80::1079:7a1f:90f9:2c8f%3]) with mapi id 15.20.3348.014; Wed, 2 Sep 2020 09:29:36 +0000
From: Glyn Normington <normingtong@vmware.com>
To: Carsten Bormann <cabo@tzi.org>
CC: "Murray S. Kucherawy" <superuser@gmail.com>, "jsonpath@ietf.org" <jsonpath@ietf.org>, Tim Bray <tbray@textuality.com>
Thread-Topic: [Jsonpath] JSONPath draft charter
Thread-Index: AQHWgD5tC8nvN0wgr0KdsRX+uCeCEqlUFQCAgACyUQCAADCxAIAAHqYA
Date: Wed, 02 Sep 2020 09:29:36 +0000
Message-ID: <F868B402-52BE-4E79-84D8-13C000F0942F@vmware.com>
References: <mailman.38.1597172408.10748.jsonpath@ietf.org> <CA+mwktKSMn0e3Xh5K3z-wxeC_icx3dnepWvxKu74miGqLb_wxA@mail.gmail.com> <AEE0C02D-DF63-4CEF-AC78-08180BC0B0F2@tzi.org> <CAHBU6ivxaeKRm8+5_DiP=qtpiWXEffD374n6dxx4bgJTt1nCbw@mail.gmail.com> <22C87C6B-F7FB-4074-8EEF-118AA28AB61B@tzi.org> <3AC3C075-2CA3-4DDC-BEE8-C3C4B179A61B@vmware.com> <CAHBU6ivA79KFJa4DfO4BEdGJ1K9pWP+cgHC4tegNjW90favxAw@mail.gmail.com> <CAL0qLwb4WtQEKcnPmPYhkXp4_0rYjJKC52SEVtuxiG3MCVtXjQ@mail.gmail.com> <2498CFE1-D301-4238-AD9E-926817C4D7E5@tzi.org>
In-Reply-To: <2498CFE1-D301-4238-AD9E-926817C4D7E5@tzi.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: tzi.org; dkim=none (message not signed) header.d=none;tzi.org; dmarc=none action=none header.from=vmware.com;
x-originating-ip: [195.213.80.251]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3f81880b-cf27-4305-8b15-08d84f22b5b8
x-ms-traffictypediagnostic: DM6PR05MB5948:
x-microsoft-antispam-prvs: <DM6PR05MB5948B4CDF3A6276FF86EE4D7C32F0@DM6PR05MB5948.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: RbcCm4s6pNKfvaQsea+qXgS8MzPvXY8tmuZi3nTc2Wq2fOos7T6nL03/kh+JZzOYG+DuzeA4jLOvpLxjzeR8vs+mPTAcJRKaRT65kxERMykNNg9+RVoBUDoeDu7LdZ6XGquSsvsDERleTrAz9SlAz7xq8mlIUjGl6DAYyp/rQNp9u4I1DRh+Gb1PWm+j6/7zUvrWb1EiUEO+4dhbWkWQFGf8KdKy0zGZRIRtEJ4Xa+lzERljJMmIzcJk6qDjF0tKmU1PWE49xlhBY32QaTWEN4PXCaJ6zICdJw55UHf3KJSoUrYUyqilAI2F1dK/TI8iOxol3EGFY3IY+C+G4tNkXS1i1Ur62R7koAzRjFWKZYoOUtcXDfO7xe0x/YlE+L+xBcg0cyU2XQp48QHNk/8TOA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM5PR0501MB3766.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(396003)(346002)(376002)(136003)(39860400002)(366004)(64756008)(83080400001)(54906003)(478600001)(2616005)(66446008)(66556008)(8936002)(86362001)(26005)(83380400001)(316002)(76116006)(66476007)(66946007)(91956017)(6512007)(2906002)(33656002)(8676002)(45080400002)(186003)(6916009)(71200400001)(53546011)(6506007)(966005)(6486002)(166002)(4326008)(36756003)(5660300002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: ijU+aCnOHtRpS1SyTWhQ7gL3NkQ9IL+THo8a6YLOWYwDWh9B4jXWAfWnFHZv2i3eFIuLeGLvsaVyueuNKLvWLtmC0npB0gRuRciwdWHhO/v+dJUKoLDNwck1dUI6INnOkZ09wEE9PqTbBgWr+rinV1LjkduXiPBJnVHxAf29/cVHZ9oCRNBsoJygoesHz6063HWsFH0pUldpkJTvTWu671As/3ApCJPzhek7S9L2agwdLWhMXh0eFJQ8VCftWq1fIbBrptgsxS8P02onWX87H5yXh3R72Je1X3JfSn07HhH4jxfcB6L4Eycih1zCe1nOKUb6VPdDQDMKf99FA5okirg20Ilx4szcriU2eyPiWFuP6DjPS6XCZ540wSvHjFl56AMarg0l1VE4jO6dM14v0+9a9nZUAnOe1bU8bOrWnKLi8wBU/Qu/RUuusqliojAWLijn3K8VSNN8dltySMP7r0PNW/430M0Vu8GYh2+yClZsE7ZTCL8r9piuYGNvG1A41LjV7mughXtsv3LXqdIGQX5W5xcpP0ZS0RBb2g6E2YwXi6q91loVeAvMh2fIlpuJWF1E75bNJ9LbvmksJk+Lv/bONwv//hHGP7Bff3cRUHZf2ZM7IJISeXPi4a1Keqf7JJYBriVrp7gLQ+QlFlii5Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_F868B40252BE4E7984D813C000F0942Fvmwarecom_"
MIME-Version: 1.0
X-OriginatorOrg: vmware.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM5PR0501MB3766.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3f81880b-cf27-4305-8b15-08d84f22b5b8
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Sep 2020 09:29:36.8448 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b39138ca-3cee-4b4a-a4d6-cd83d9dd62f0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: qjFgWMHucrt+KLQkMrmKD2exJZvokYsguDusL2n8W5tit3vvjX6h7QXeM84+7U/peZxVJshgDLTRdAwITnwsiA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB5948
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/2-bFzViDc-vc1vje4ReVE8yNQ70>
Subject: Re: [Jsonpath] JSONPath draft charter
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 <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: Wed, 02 Sep 2020 09:29:49 -0000

Similarly, we’ve run into questions along the lines of "Why is JMESPath not sufficient?” as JMESPath ([1]), like JSON Pointer, also has a well-defined specification. In that case, the answer is different because JMESPath is functionally richer than JSONPath. The reason it’s not sufficient is that it would incur a significant migration cost for JSONPath users.

On a separate topic, would it be worth pointing out in the charter that there are over 38 distinct implementations of JSONPath. 38 are covered in a comparison project ([2]) and there is one (part of Kubernetes) which isn’t in that list. The comparison project calculates where there is a consensus on certain features and demonstrates that there is a lot of common ground, which makes this post hoc standardisation exercise feasible.

I’m happy to submit a PR for either of the above, but I hesitate because I don’t know how much detail charters typically include.

[1] https://jmespath.org/
[2] https://cburgmer.github.io/json-path-comparison/

On 2 Sep 2020, at 08:39, Carsten Bormann <cabo@tzi.org<mailto:cabo@tzi.org>> wrote:

On 2020-09-02, at 06:45, Murray S. Kucherawy <superuser@gmail.com<mailto:superuser@gmail.com>> wrote:

I anticipate being asked "Why is JSON Pointer not sufficient?"  Indeed its abstract says:

I’m trying to answer this on the slide at

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyoutu.be%2FUjch6Wukjc0%3Ft%3D48&amp;data=02%7C01%7Cnormingtong%40vmware.com%7C53ad9caf177d494c130408d84f1368c5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637346292073043715&amp;sdata=1Acgf4zPMRKfSe33PVi%2FTgH9dwNOANPOMAgoJlVm9fE%3D&amp;reserved=0

The short answer is that JSON pointer is good if you already know the structure of the JSON data item you want to point into, and you want to point to exactly one position in there.  If you need to do something that is closer to a “search” (which might also result in multiple positions), JSONPath gives you more rope.

BTW, for easier editing/PR-ing I have put up Tim’s proposal with Brian’s proposed changes at
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjsonpath-wg%2Fcharter%2Fblob%2Fmaster%2Fcharter.txt&amp;data=02%7C01%7Cnormingtong%40vmware.com%7C53ad9caf177d494c130408d84f1368c5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637346292073043715&amp;sdata=JI7gcMSHRHF3y8%2Bddd38FhpJ8f7pYIg5zouTmuVOALM%3D&amp;reserved=0

Grüße, Carsten

--
Jsonpath mailing list
Jsonpath@ietf.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fjsonpath&amp;data=02%7C01%7Cnormingtong%40vmware.com%7C53ad9caf177d494c130408d84f1368c5%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637346292073043715&amp;sdata=YKIGD8Cra3%2Bj8UH9EYCJ8xqUK8M3DlDEP%2FXDYh%2FB52Y%3D&amp;reserved=0

v2.23.0 | Report a Bug | By Email