IETF Logo Mail Archive

Re: [Jsonpath] Fwd: I-D Action: draft-bormann-jsonpath-iregexp-04.txt

Tim Bray <tbray@textuality.com> Mon, 25 April 2022 17:26 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 B5048C1D34ED for <jsonpath@ietfa.amsl.com>; Mon, 25 Apr 2022 10:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20210112.gappssmtp.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 JXT9NKj0_EaQ for <jsonpath@ietfa.amsl.com>; Mon, 25 Apr 2022 10:26:43 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (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 083F5C1D34E1 for <jsonpath@ietf.org>; Mon, 25 Apr 2022 10:26:42 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id g20so19302711edw.6 for <jsonpath@ietf.org>; Mon, 25 Apr 2022 10:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5p6NFaMzdwS5pdBdelg2IpIeQqN8TXvWEoDa51mDZCw=; b=kUietdyETAgQj81jXlzoUUgzwPPHwUq5nB3/jxD6mU5z2VlI7A1+J5p4agh5WYoaUC fdQi/gh9COVqm5e2bFmRGJOPCecbGNbLVQKfwZjnjN6u/MPqqzV4zzpP33cHtW1UIvzG EKWpClK1HzDuefT90xO6D0UHdLa2XaMlbxSNQz5WrcDIqZowMRs8DRg8jf8cAw5/9Owq 6UuKLma1d1PzK9snIwwgZTxfcF/c2tVqOVSXrfYSlDuHMp3+EVPIOf6iKirs3VVpQ4HI G182G3XDgmuD9iRPozzzvScM0NBKf5A8F5tqDyDTdM5eWTQYvSowxTG/dpa9Y2KouE3R V/kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5p6NFaMzdwS5pdBdelg2IpIeQqN8TXvWEoDa51mDZCw=; b=Rcv3Z+zNi5df6h+v2GCgnhLu6bysK9+vSMFEomrStmQ74mC9BHYWvfv1dXfnrNdhSz yXIe+4xmdJrW6nXcrKhigOJJlF1zO7hFlK7jXGL9wf0J7RmO5s8ABP4mPbv+AGRn3k4s Qp/z+kSyRx6XivzCLznZljursDF4H0LmuseRUak27iB/KTqms44PRsFto9qCNl9gyV7b 8pmALA5hAxDzAVv7Mk+3zA2Y5luxvdRmvVOwGz2MP0BSKVrzFw3K3i3XEKeMsZGxVI63 3qdXK8yzYQkftClg6FxZPUcSD/ylXlqywI9HmYh7nfnGWXmEpRywceemPqZ5GZO8ujQC 4HWQ==
X-Gm-Message-State: AOAM531mTJcVmjXg6/J56m1e0xYXASwSstvJGYzR/FS8njxxeTGoohUv LbIYGujkTIinu1m7iAfOLWFIaUaV/5X+YpMo858MWg==
X-Google-Smtp-Source: ABdhPJyHjqIU7fhQRvPWYeWg/4J8P03GC+17Fog79ACmh22fibdD7VvRdByEBx1ldV2K1EI/AAeeIffFGwL0z6sDMTE=
X-Received: by 2002:a05:6402:54:b0:419:9b58:e305 with SMTP id f20-20020a056402005400b004199b58e305mr19963956edu.158.1650907601154; Mon, 25 Apr 2022 10:26:41 -0700 (PDT)
MIME-Version: 1.0
References: <165090408999.1001.9669029059632409746@ietfa.amsl.com> <8DF9CF13-3ADA-433A-97DF-6D77A222D607@tzi.org> <CANH0GbJm7CYUDYhvpz+F1e+NhO5pPBOxFr9T3sjEgu6pShS4Yg@mail.gmail.com> <CAHBU6itkyL-Vny_XM3musumN=_CdhoT_tnNDLhtp8RAXqLBdng@mail.gmail.com> <CANH0GbKc_vtT_+vm_S+-EizLX05voCR=mUa3ZksGo_+J821M_g@mail.gmail.com>
In-Reply-To: <CANH0GbKc_vtT_+vm_S+-EizLX05voCR=mUa3ZksGo_+J821M_g@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Mon, 25 Apr 2022 10:26:30 -0700
Message-ID: <CAHBU6iv4Xv=QPmOWrL6O=OxfNNorwwzuYiNCe2MFYvKzRMMMsQ@mail.gmail.com>
To: Glyn Normington <glyn.normington.work@gmail.com>
Cc: Carsten Bormann <cabo@tzi.org>, jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001fc8a305dd7de1fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/_x1frwWdGEpxL6H2_Rji5uxKmk8>
Subject: Re: [Jsonpath] Fwd: I-D Action: draft-bormann-jsonpath-iregexp-04.txt
X-BeenThere: jsonpath@ietf.org
X-Mailman-Version: 2.1.34
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: Mon, 25 Apr 2022 17:26:44 -0000

I can't disagree.  All I can add is that a MUST is a pretty heavy hammer. I
think that for any of the well-known libraries, I could construct and ship
an I-Regexp translator in a very short time, in some cases hours. Building
a syntax checker would be a much more demanding task, and writing the test
suite for such a checker would be very discouraging.

While I at least partially agree with you, here's a counter-proposal: Put
in a MAY (or SHOULD?)  and a paragraph containing basically the text of
your email 5 minutes ago, encouraging implementors to do this.

On Mon, Apr 25, 2022 at 10:07 AM Glyn Normington <
glyn.normington.work@gmail.com> wrote:

> If non-conforming regexps are handled, I think (at least perceived)
> interoperation could suffer. Suppose someone gets used to using a
> particular I-Regexp implementation and fails to notice they have stepped
> outside the official syntax. Then at some point, they try another i-Regexp
> implementation and either (a) their regexp syntax is rejected as invalid or
> (b) the behaviour is different.
>

v2.23.0 | Report a Bug | By Email