Re: [Jsonpath] JSONPath draft charter

Brian Rosen <br@brianrosen.net> Tue, 01 September 2020 18:56 UTC

Return-Path: <br@brianrosen.net>
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 A8B1B3A0F31 for <jsonpath@ietfa.amsl.com>; Tue, 1 Sep 2020 11:56:19 -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 zDXHEWQFZfsg for <jsonpath@ietfa.amsl.com>; Tue, 1 Sep 2020 11:56:17 -0700 (PDT)
Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 6397A3A0F30 for <jsonpath@ietf.org>; Tue, 1 Sep 2020 11:56:17 -0700 (PDT)
Received: by mail-il1-x12b.google.com with SMTP id e14so2272799ile.6 for <jsonpath@ietf.org>; Tue, 01 Sep 2020 11:56:17 -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=mPsHSnyVz0On3ejnrPy9DcklCvJfDKGuI7XUV6bO1Ks=; b=mnECFcZOilAHOKUl6FHnRWZYwliXBE3RrOgyK6ESxAKGds9lBXJlsuBq1w6OHBkviW 9kiBwVJdFfuJ4ttTBbfjlblgPCH+I7BLVehhHE57jetUjV/oK+F/eN7PwGB3W+78MHhF 8bBkZMn1+DNiustoXZZRhy7BqNKRpfosHUIa7rYRIuMDbQ1G/e9oJMtvuwXDzCKvt4+w c0a/LvfaUoBA9ZsoYP89Vj16EVdGCH6qzWd5bp4VqvQiym5AVHGvbeP17oMJe6lNPUHT 16oiwfJby2OSt+TvSf2+NJKL3I7C6cMsKpNrSounYnurfG5MdUxIosDPHTcBtMok3WXB z+fQ==
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=mPsHSnyVz0On3ejnrPy9DcklCvJfDKGuI7XUV6bO1Ks=; b=AvU7VJVbd2yy3KR19Ce8YhRFcP3JLtstImsnIWiclsE7IccS6Scu+5RiKN055K9mWq MiiWhk8jCWIJUZQVDuZ29dpGVLo6OgB2h/dU63I+MLiA1QFDq7TR82LlNKqRNupzMdDf kUt9/mbHvpRdVE77vz16aEARABMp4kaPLgp6vsIpz0VBkJzq2mZ/aHsZ2jDxW187nZO5 d2ybfxOO267RSGWBi2Yhx/cBVXgVKdlp7RxAOCnOhpy06QlE/xMOIHManiuJXhpLSz4f De132A9pt2OXbNUTdRrbFYkEVcGXNUP4COghM3GrItJ1R3T3+78lB1p/ku6jUNUbwNE+ lcyQ==
X-Gm-Message-State: AOAM530trjFX9RCs2JnDzOCJCX0JVauvNZ7dgXqI9IeILOP7KhlkhLGT XmhHLnuvGhVp1Bv2GPqrcRaXww==
X-Google-Smtp-Source: ABdhPJzf48004W36b3b3nFbFxC4/xWsqxuoF3ou54ucsyEN4aOF6VwtayLpZ/9EcJ1wA/QETN6KYMQ==
X-Received: by 2002:a92:c9c5:: with SMTP id k5mr412146ilq.231.1598986576651; Tue, 01 Sep 2020 11:56:16 -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 h7sm955855ilo.51.2020.09.01.11.56.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2020 11:56:15 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <3C38DCDC-3F9F-49D8-8208-8366FEA05F2A@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_00FCFE26-F4DA-4501-8BAA-D05218F60F53"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Tue, 01 Sep 2020 14:56:14 -0400
In-Reply-To: <CAHBU6ivA79KFJa4DfO4BEdGJ1K9pWP+cgHC4tegNjW90favxAw@mail.gmail.com>
Cc: Glyn Normington <normingtong@vmware.com>, "jsonpath@ietf.org" <jsonpath@ietf.org>, Carsten Bormann <cabo@tzi.org>, Daniel P <danielaparker@gmail.com>
To: Tim Bray <tbray@textuality.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>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/VxHXHY8XZ27YINvHLt2sLu54w5A>
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: Tue, 01 Sep 2020 18:56:20 -0000

Maybe add “standards-track” after “The WG will work to develop a”, so it’s clear we are doing a PS doc and not an informational.  Also maybe delete “work to” so it’s not “The working group will work to”

Brian

> On Sep 1, 2020, at 2:07 PM, Tim Bray <tbray@textuality.com> wrote:
> 
> Here is a draft charter in space-formatted plain-text. I suppose the IETF has a charter-creation tool but I didn't turn it up in a brief search.  Anyhow, 
> this should be enough to kick off discussion:
> ====================================================================================
> Document          Charter      	   JSONPath WG (jsonpath)
>                   Title        	   JSONpath
>                   Last updated 	   2020-09-01
>                   State        	   draft
> 
> WG                State        	   Nonexistent
> 
> IESG              Responsible AD:  Kucherawy/Leiba
>                   Charter Edit AD:
>                   Send notices to: (None) 
> Charter
> 
> charter-ietf-jsonpath-00
> 
> JSONPath is a syntax, originally based on the XML "XPath" design,
> which selects fields and values from a JSON document.  It is
> used in a variety of applications which rely on JSON message
> formats.
> 
> JSONPath was originally described by Stefan Goessner [1] but has
> never had an official specification of any kind, and
> implementations, while mostly compatible, differ in certain
> behaviors.
> 
> The WG will work to develop a JSONPath specification, with the
> primary goal of capturing the common semantics of existing
> implementations and, where there are differences, choosing
> semantics with the goal of causing the least disruption among
> JSONPath users.
> 
> [1] https://goessner.net/articles/JsonPath/ <https://goessner.net/articles/JsonPath/>
> 
> 
> On Tue, Sep 1, 2020 at 2:01 AM Glyn Normington <normingtong@vmware.com <mailto:normingtong@vmware.com>> wrote:
> What are the next steps on the JSONPath draft charter?
> 
> Tim: are you still up for creating a first draft and, if so, when?. This would be very helpful for those of us unfamiliar with such things.
> 
> Regards,
> Glyn
> 
> > On 11 Aug 2020, at 23:20, Carsten Bormann <cabo@tzi.org <mailto:cabo@tzi.org>> wrote:
> > 
> > On 2020-08-12, at 00:12, Tim Bray <tbray@textuality.com <mailto:tbray@textuality.com>> wrote:
> >> 
> >> Is there a draft charter?  
> > 
> > Not yet.  I thought we might have a little bit of discussion to find out where the different point of views might be lying.
> > 
> >> I don't recall seeing one go by but maybe I missed it.  If not, I can make a first draft.
> > 
> > That would be great!
> > 
> > Since github organizations are cheap, I created one, with a repository that you could use:
> > 
> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjsonpath-wg%2Fcharter&amp;data=02%7C01%7Cnormingtong%40vmware.com%7C69eafdbfeb7a4dec694208d83e44d677%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637327812690554976&amp;sdata=l0CUyDcFpI5fVXkSUQwgoMx8%2FbIyIX60rvPqaW2aUrw%3D&amp;reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjsonpath-wg%2Fcharter&amp;data=02%7C01%7Cnormingtong%40vmware.com%7C69eafdbfeb7a4dec694208d83e44d677%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637327812690554976&amp;sdata=l0CUyDcFpI5fVXkSUQwgoMx8%2FbIyIX60rvPqaW2aUrw%3D&amp;reserved=0>
> > 
> > Grüße, Carsten
> > 
> > -- 
> > Jsonpath mailing list
> > Jsonpath@ietf.org <mailto: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%7C69eafdbfeb7a4dec694208d83e44d677%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637327812690554976&amp;sdata=KDosq4s5Dr58xPwYevCzOoYbe6p8wLCWfDA8Tfx9PIE%3D&amp;reserved=0 <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fjsonpath&amp;data=02%7C01%7Cnormingtong%40vmware.com%7C69eafdbfeb7a4dec694208d83e44d677%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637327812690554976&amp;sdata=KDosq4s5Dr58xPwYevCzOoYbe6p8wLCWfDA8Tfx9PIE%3D&amp;reserved=0>
> 
> -- 
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath