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

Tim Bray <tbray@textuality.com> Tue, 15 September 2020 07:21 UTC

Return-Path: <tbray@textuality.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 C3E543A0D38 for <jsonpath@ietfa.amsl.com>; Tue, 15 Sep 2020 00:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.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 sZqG9Uk4ctUf for <jsonpath@ietfa.amsl.com>; Tue, 15 Sep 2020 00:21:19 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 EA6123A0D22 for <jsonpath@ietf.org>; Tue, 15 Sep 2020 00:21:18 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id y17so1981209lfa.8 for <jsonpath@ietf.org>; Tue, 15 Sep 2020 00:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qChalnVGMgd29MDegvY3LGrZ+f0ZLtUnjrkN3l1l+q8=; b=BsPpW8rsCL+KRzAvp33mYXmMAFTPXEoONxZ/H+FwRLvAmmf2gf1mmAof4cVCVhlizQ Guj8Eh8mTkDuy67orxWVe0yzbfX7QMLBhJAuWhN4zRSdb+KN8C8JyQ55+6ZL9JICDaaK mA6MwctEEHlMwRN38BtBOeAHlnQF3YhTKkJwOZGEzjOsTiXMCrsemoVVxcJxwoO7RJ/f DJ6RBujBVOaPc2cGYmBLJUur0UGKvzg0+eZEo6srZxLVQvYz77jJJmK744GOu5XNMEqN UhCdoVPgOiUD39SMu4sLMGMGd+jx0yX0s8kPq60dndZc60QcKVW3Be3sXOaNYUqL1XBf sYxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qChalnVGMgd29MDegvY3LGrZ+f0ZLtUnjrkN3l1l+q8=; b=gg7dd0EQp9lmfnvCY7BQFvUvxSH8NB2mTrCUEhwAbsFCc4OmxcqBcqRGHcH6HXlbkm cB9zD76NhyFZqttRfUDfbwHg3PgndAbZ3QqsxvqFmEfXqdyni0bYCOGfhfd83J/1K8pg 8Gn1C/QN7/mwkk/Q79VjKdRMokBaydVj8KYhW5C+gBPgKOkASNk482omL/y9aMqBV9PH Nk3sCsTmLz+8W3gbZ0R0KI+WJTGrAWLuAX2F+/RuGw8TuYky4B4IA3fTMf5EEkcmLpi9 JEL63r/I5NGrZYzFNfhMjCMsDx1rxe2X2L6Qo+pKp9ZdD6/GGEqz1+koh8q7NGO0Rbcy zaaw==
X-Gm-Message-State: AOAM532if48+bOi2WRMNaGbzfI0GvaL4q5JrmywG1Tw+EYSNmW8mlg00 xLYPYutKkSr+Z9l35SLIrTgDL8MMpuCjCK0PKbjxyQ==
X-Google-Smtp-Source: ABdhPJzExA5GvLMMBDVbDzirpSIGYzuXhL0cxSqMtkTuSF7TOyigVRXlqdQ9aLnUibPoJH+Zc0lz4aVsXv5wLRYM+cc=
X-Received: by 2002:a19:c07:: with SMTP id 7mr4915208lfm.516.1600154476899; Tue, 15 Sep 2020 00:21:16 -0700 (PDT)
MIME-Version: 1.0
References: <159467093010.19477.7181341398452455173@ietfa.amsl.com> <77B617C1-2148-4AE6-8428-DAD43D01FBC5@tzi.org> <3B8242C5-CACE-4E85-AF0A-A0C6F77A5EDB@tzi.org> <CAL0qLwZx24X_-3_Ty0J_P5_Nf7VOp2AmpTgtfqyKB0JrE8EY4g@mail.gmail.com> <92BFBB4F-54B7-4E14-B322-A8B323631584@mnot.net> <CAL0qLwas16Tb-cUQ8_wtHYmmf7n76yabv6cdntZtwXuVNAWE0Q@mail.gmail.com> <40603C98-BE0D-4D3C-8170-FEA83494065F@mnot.net>
In-Reply-To: <40603C98-BE0D-4D3C-8170-FEA83494065F@mnot.net>
From: Tim Bray <tbray@textuality.com>
Date: Tue, 15 Sep 2020 00:21:04 -0700
Message-ID: <CAHBU6ivRCWC6D=CUHRQCunHCfRuca_FdE5wTZ+g0YaXMzLS96Q@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, jsonpath@ietf.org, DISPATCH list <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002e8fe605af54ffef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/j2jO8OTQlvimXXFznHW2gdlWRZE>
Subject: Re: [Jsonpath] [dispatch] draft-goessner-dispatch-jsonpath-00.txt
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, 15 Sep 2020 07:21:21 -0000

Plan B: Don't mention JSONPointer at all. It's not what we want to work on,
and the charter should be about what we want to work on.

On Mon., Sep. 14, 2020, 11:02 p.m. Mark Nottingham, <mnot@mnot.net> wrote:

>
>
> > On 15 Sep 2020, at 4:07 am, Murray S. Kucherawy <superuser@gmail.com>
> wrote:
> >
> > On Sun, Sep 13, 2020 at 5:20 PM Mark Nottingham <mnot@mnot.net> wrote:
> > Two nits in the charter text:
> >
> > 1) I don't think it's necessary to compare this effort to JSONPointer;
> they do different things (querying a document vs. referring to a particular
> part of a document), just as XPath and XPointer do different things. Each
> has a place, it's not a matter of compatibility or supplanting JSONPath.
> So, 'Other, incompatible approaches exist... but have not succeeded in
> supplanting JSONPath' should be removed.
> >
> > I suggested including something like this to head off questions from
> people who might wonder why we're standardizing another JSON referencing
> method when JSON Pointer wasn't that long ago.  Perhaps:
> >
> > "This work is similar in concept to JSON Pointer (RFC xxxx) but
> documents a mechanism that has broader support yet is in need of formal
> standardization."
> >
> > ?
>
> No - it's not similar in concept, they're separate things. If you really
> wanted to mention JSON Pointer, you could say something like "Note that
> while JSON Pointer (RFC xxxx) is already standardised, it is designed to
> provide a reference to a single, specific part of a JSON document, whereas
> JSONPath provides the ability to query a document and potentially return
> multiple values."
>
>
> > 2) If this charter is predicated on adopting a specific draft, it should
> be listed (e.g., as we did in <
> https://datatracker.ietf.org/doc/charter-ietf-quic/01/>).
> >
> > I don't think there is such a draft yet, just the external source
> material.  We could say that the intent is to generate a draft from the
> text found there.
>
> I see two:
> * https://datatracker.ietf.org/doc/draft-goessner-dispatch-jsonpath/
> * https://jsonpath-standard.github.io/internet-draft/
>
> Cheers,
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> --
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
>