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

Tim Bray <tbray@textuality.com> Mon, 25 April 2022 17:03 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 E61B4C185156 for <jsonpath@ietfa.amsl.com>; Mon, 25 Apr 2022 10:03:16 -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 gdbAkvbnA5zy for <jsonpath@ietfa.amsl.com>; Mon, 25 Apr 2022 10:03:16 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 75385C1594BB for <jsonpath@ietf.org>; Mon, 25 Apr 2022 10:03:16 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id k27so4032785edk.4 for <jsonpath@ietf.org>; Mon, 25 Apr 2022 10:03:16 -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=EtmhT7byC+PkKrj+M3S+OCVJ9zDm+Msig/tvnaqRfRo=; b=IUxujMdNClv5XWaRL8Df7r1+N4IaUDEuyuX3KewePf2Db5dNDSjFmvvz3xyBWoUaPF JzqqaxALqJ6JSxd8CleEauYC08vQAMj8bf99b2jjh8I4cNl6hpA9f8zo1BRKdmH9lJyp 9PCZ8wQh/0jCQh+BsxFEkk5hiVaBJJpEoa2pzhJ9TPgl4WD1ydmf9p3pT+KVTe+B7gqW shLS4g8z6KDKice3wRWytrWR/q+YCqHujz3qCAOoXqVNB6pIYCD34yPt1FIGWVUq+Njo NIds4A75WBh93/23jBRU/o2LwyXKpj2X8od4a5W77R8lS+NCPALCLR8BJBBvD0VJQk5D BzBg==
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=EtmhT7byC+PkKrj+M3S+OCVJ9zDm+Msig/tvnaqRfRo=; b=3fvJrXMPyLcAiVzvNwEDIdGM8b4ZvKNb1xN54urdYAT61cZUrCuLi40nVIbe+uRGhT JiqAJRSFuraTLGcVhbGvJtLwAI0a7IRn8Sslr72b2/HaZJLR9/nM0Erpw8VbkiMaAu7G Br3UqzU09eflwQLvE7JKahqwU7etHV8ubINXowZmKAGsgdGY14v1O02ZTINqVYZXNTAw Ie8blSHRdlTGWgrDs06RPC6/yM1WI9JvovWIE7bCJbOyR48lwIgG7EIGrlQGIjLXXPgD av7x0MZjHGWztDUPM83JeS5yeJf8JnGP8NUVvEabJepOXC6E1NFmuTldC2KlyjizVBL2 7/cA==
X-Gm-Message-State: AOAM533pKghicHIszMWzOBJfrNVaodGdxAvaQC4Fg1TdAngG0yPZMtqA xgSDXEUdASQJWLpvxnQgw1mfxPAVQDCneW+8DCzJLg==
X-Google-Smtp-Source: ABdhPJwMNwzn1pREt9aNihsNL3RW1o/nsTS7wufGoIeAumVVTZCYa63PcVSjwft8WD+4+QEIzhmzgpWnM4G6gesALo4=
X-Received: by 2002:a05:6402:26c6:b0:425:f86e:77e1 with SMTP id x6-20020a05640226c600b00425f86e77e1mr138637edd.400.1650906194700; Mon, 25 Apr 2022 10:03:14 -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>
In-Reply-To: <CANH0GbJm7CYUDYhvpz+F1e+NhO5pPBOxFr9T3sjEgu6pShS4Yg@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Mon, 25 Apr 2022 10:03:03 -0700
Message-ID: <CAHBU6itkyL-Vny_XM3musumN=_CdhoT_tnNDLhtp8RAXqLBdng@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="0000000000004b01b205dd7d8d6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/7MAN3yG2tyoGDsYzvXz1RRWT-9g>
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:03:17 -0000

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

> I have one question about I-Regexp. Must implementations raise errors for
> regular expressions which do not conform to the I-Regexp syntax? That
> wasn't clear to me from the spec.
>
Hmm, good question.  At the moment, we've got Carsten's specification of
the syntax and then we outsource the semantics to XSD with a MUST.  That's
all we say about implementation behavior. Speaking under my lazy-person
hat, I worry about getting on a slippery slope if we start trying to
specify implementation behavior.

Hmm, I guess we do also at least imply that evaluating an I-Regexp against
a piece of text should produce a boolean result.

I guess the minimal thing we could do would be say "I-Regexp
implementations MUST report violations of the syntax specified in this
document."

But that could be a significant extra effort for developers, so I probably
would be against it, but only by about 51/49 and wouldn't scream too much
if others thought it a good idea.

>
>