Re: [dispatch] [Json] draft-goessner-dispatch-jsonpath-00.txt

Brian Rosen <br@brianrosen.net> Tue, 14 July 2020 12:25 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D25D13A0B80 for <dispatch@ietfa.amsl.com>; Tue, 14 Jul 2020 05:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.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 RPxJFhm98kyQ for <dispatch@ietfa.amsl.com>; Tue, 14 Jul 2020 05:25:29 -0700 (PDT)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CFBA3A0B76 for <dispatch@ietf.org>; Tue, 14 Jul 2020 05:25:29 -0700 (PDT)
Received: by mail-il1-x132.google.com with SMTP id t27so13981820ill.9 for <dispatch@ietf.org>; Tue, 14 Jul 2020 05:25:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=WgjgtHl/eLx4zF0CS7LWDxZwlRutT1zcU1sMJ25QQ2U=; b=1o+b3cwsFQPji2bHWdmDtkVToehwhMN7KxyKudWHUh1qswVFzYV8RkEXb3/6hx0wsg CNKfjRON+gFIglR5IaC9JRgfuxzKdPNDK1gPwoBvrW5AS0TynHLyrvdeyN+vBOczEnZp EUb6dy8d74ndBYsEwisVzRFduZ0Vm4dbEQAR2vcuaU/jEMUjjCMATIKwc6y5FIIeYuqX YFc7HKrma4KwQ0nvt+thps2T9sin5hXCOiO/1Onx66f2btmbxK+weInd89HBu7od252N lTufby4sm5P14KBpi9d+HtvSZpmHwi249sJ/WvaSw1Qb+Ezt4izIvz+xWCbyaMxloe7M 6t+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=WgjgtHl/eLx4zF0CS7LWDxZwlRutT1zcU1sMJ25QQ2U=; b=hE0MVV+M20McId0iu9MEqyDO0j0j2k4nC/1QeqnVo5LDhEACcVzH9FThfBMDPtzVzB 2El+cPgyPVEqz8qONx+RxtfF/MC+io2ja8rUS7kLe+Up4R/ZmTvUTPjk/EbpT2x2EMtK 8r0jAgO6JmBq7XV29K6hBr5FVv/fM1H1FPq57H8fKgOzp+DjI39sr0XkeMZ+ZeJ4ddh/ zmvtFByQIuK1leNHPTUibPTILro0aWSHVXXd7/PBWd0nO1gDbHpWADXyI+Xr2qjm8jvw /Z0VtAfblRfRyrG1CicVhjHzolew7COkywHVmh8bxurCgCoVG7GnxSS14hvJH3Ca/zFr AY9w==
X-Gm-Message-State: AOAM530K0+M6CTN4widd3aDC+4/kivvh7ZZ1yJ1zlP6Hswl/ftKovoKA xfIPWhsrPYR3plPXD+FkwRB0XA==
X-Google-Smtp-Source: ABdhPJytzImwYzrtgVlfv2t55uA2xDv/tS68xjbYS5Oi8c7p5Yt5kcu5O0Rx2V2XtBdlnm70kP4wFA==
X-Received: by 2002:a92:aad6:: with SMTP id p83mr4160833ill.65.1594729528286; Tue, 14 Jul 2020 05:25:28 -0700 (PDT)
Received: from brians-mbp-2871.lan (dynamic-acs-24-154-119-158.zoominternet.net. [24.154.119.158]) by smtp.gmail.com with ESMTPSA id f18sm9068754ion.47.2020.07.14.05.25.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jul 2020 05:25:27 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <B5EAC3B0-F593-4D4D-9A9B-A5AB983EED69@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9FCF87D4-63FA-423B-80C1-DF79640D5764"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Tue, 14 Jul 2020 08:25:24 -0400
In-Reply-To: <467d225e-6dcf-4e5f-1101-27e4c074c6af@iit.cnr.it>
Cc: Tim Bray <tbray@textuality.com>, dispatch@ietf.org, cbor@ietf.org, JSON WG <json@ietf.org>
To: Mario Loffredo <mario.loffredo@iit.cnr.it>
References: <159467093010.19477.7181341398452455173@ietfa.amsl.com> <77B617C1-2148-4AE6-8428-DAD43D01FBC5@tzi.org> <CAHBU6iuwknJ3WxPqbtqKLTwKdWV6JKnak8zB-6GohGidGdJVQQ@mail.gmail.com> <467d225e-6dcf-4e5f-1101-27e4c074c6af@iit.cnr.it>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/VwygErSByi1ewWwrA5JOsq5sPv8>
Subject: Re: [dispatch] [Json] draft-goessner-dispatch-jsonpath-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2020 12:25:32 -0000

+1

And I note the discussion of an HTTP API working group, to which this work would fit in.

I’m currently working on a spec for emergency services that uses jsonpath, and the lack of a referenceable spec was a big concern.  

Brian

> On Jul 14, 2020, at 3:33 AM, Mario Loffredo <mario.loffredo@iit.cnr.it> wrote:
> 
> 
> 
> Il 14/07/2020 07:31, Tim Bray ha scritto:
>> During my time at AWS I worked very heavily with JSONPath and lamented a useful referenceable spec. I would be happy to invest cycles into this work. There currently isn't a JSON working group but I suppose it wouldn't be too hard to reconstitute it for this purpose.  
> +1
> 
> Mario
> 
>> 
>> On Mon, Jul 13, 2020 at 10:14 PM Carsten Bormann <cabo@tzi.org <mailto:cabo@tzi.org>> wrote:
>> (Reply-To set to dispatch@ietf.org <mailto:dispatch@ietf.org>)
>> 
>> I would like to initiate discussion for draft-goessner-dispatch-jsonpath:
>> 
>> https://www.ietf.org/id/draft-goessner-dispatch-jsonpath-00.html <https://www.ietf.org/id/draft-goessner-dispatch-jsonpath-00.html>
>> 
>> It says:
>> 
>> > This document picks up the popular JSONPath specification dated
>> > 2007-02-21 and provides a more normative definition for it.
>> > It is intended as a submission to the IETF DISPATCH WG, in order to
>> > find the right way to complete standardization of this specification.
>> > In its current state, it is a strawman document showing what needs to
>> > be covered.
>> 
>> (For some reason the abstract landed in the Contributing note; typical Internet-Draft deadline day botch.)
>> 
>> This is a widely implemented specification that has been around for more than a decade; now may be a good opportunity to finally go ahead and turn it into a proper Internet standards document.  The immediate cause for writing this up now is that some IoT discovery work (some of which happens in W3C) can make good use of JSONPath.  Clearly, we already have JSON Pointer (RFC 6901) for a more limited set of applications; the specification would do good in defining how these two fit together.
>> 
>> There is no active WG that immediately fits this work.
>> 
>> Eventually CDDL may pick JSONPath up in the form of a predicate operator; this might make the CBOR WG the right group (which probably would then go ahead and write up another specification that makes JSONPath useful for querying CBOR instances that go beyond the JSON generic data model).
>> 
>> Reopening the JSON WG may be another approach, as may be creating a short-lived targeted WG.
>> 
>> Please discuss!
>> 
>> Grüße, Carsten
>> 
>> 
>> 
>> > Begin forwarded message:
>> > 
>> > From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>> > Subject: New Version Notification for draft-goessner-dispatch-jsonpath-00.txt
>> > Date: 2020-07-13 at 22:08:50 CEST
>> > To: "Stefan Gössner" <stefan.goessner@fh-dortmund.de <mailto:stefan.goessner@fh-dortmund.de>>, "Stefan Gossner" <stefan.goessner@fh-dortmund.de <mailto:stefan.goessner@fh-dortmund.de>>, "Carsten Bormann" <cabo@tzi.org <mailto:cabo@tzi.org>>
>> > 
>> > 
>> > A new version of I-D, draft-goessner-dispatch-jsonpath-00.txt
>> > has been successfully submitted by Carsten Bormann and posted to the
>> > IETF repository.
>> > 
>> > Name:         draft-goessner-dispatch-jsonpath
>> > Revision:     00
>> > Title:                JSONPath -- XPath for JSON
>> > Document date:        2020-07-12
>> > Group:                Individual Submission
>> > Pages:                14
>> > URL:            https://www.ietf.org/internet-drafts/draft-goessner-dispatch-jsonpath-00.txt <https://www.ietf.org/internet-drafts/draft-goessner-dispatch-jsonpath-00.txt>
>> > Status:         https://datatracker.ietf.org/doc/draft-goessner-dispatch-jsonpath/ <https://datatracker.ietf.org/doc/draft-goessner-dispatch-jsonpath/>
>> > Htmlized:       https://tools.ietf.org/html/draft-goessner-dispatch-jsonpath-00 <https://tools.ietf.org/html/draft-goessner-dispatch-jsonpath-00>
>> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-goessner-dispatch-jsonpath <https://datatracker.ietf.org/doc/html/draft-goessner-dispatch-jsonpath>
>> > 
>> > 
>> > Abstract:
>> >   insert abstract here
>> > 
>> > 
>> > 
>> > 
>> > Please note that it may take a couple of minutes from the time of submission
>> > until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>.
>> > 
>> > The IETF Secretariat
>> > 
>> > 
>> 
>> _______________________________________________
>> json mailing list
>> json@ietf.org <mailto:json@ietf.org>
>> https://www.ietf.org/mailman/listinfo/json <https://www.ietf.org/mailman/listinfo/json>
>> 
>> 
>> _______________________________________________
>> json mailing list
>> json@ietf.org <mailto:json@ietf.org>
>> https://www.ietf.org/mailman/listinfo/json <https://www.ietf.org/mailman/listinfo/json>
> -- 
> Dr. Mario Loffredo
> Systems and Technological Development Unit
> Institute of Informatics and Telematics (IIT)
> National Research Council (CNR)
> via G. Moruzzi 1, I-56124 PISA, Italy
> Phone: +39.0503153497
> Mobile: +39.3462122240
> Web: http://www.iit.cnr.it/mario.loffredo <http://www.iit.cnr.it/mario.loffredo>_______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch