IETF Logo Mail Archive

Re: [Jsonpath] Publication has been requested for draft-ietf-jsonpath-iregexp-03

Carsten Bormann <cabo@tzi.org> Thu, 04 May 2023 08:38 UTC

Return-Path: <cabo@tzi.org>
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 80D45C159A24; Thu, 4 May 2023 01:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 9GH0Gwq3uC23; Thu, 4 May 2023 01:38:34 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 A2C10C159A1D; Thu, 4 May 2023 01:38:34 -0700 (PDT)
Received: from smtpclient.apple (dmz02.dagstuhl.de [192.76.146.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4QBnK32WFhzDCnh; Thu, 4 May 2023 10:38:31 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAL0qLwb92heqRP2spG4or3EP9+7uyHAX9sUXzjOcH=sZhOMTHg@mail.gmail.com>
Date: Thu, 04 May 2023 10:38:20 +0200
Cc: jsonpath@ietf.org, Francesca Palombini <francesca.palombini@ericsson.com>, James <james.ietf@gmail.com>, jsonpath-chairs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <76D33AA1-B1E6-4757-8C60-A98178FF5903@tzi.org>
References: <167579039728.52004.3115613128496850079@ietfa.amsl.com> <CAL0qLwb92heqRP2spG4or3EP9+7uyHAX9sUXzjOcH=sZhOMTHg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/uDve3SSUpYo9T3MlYtAUUs4U0pE>
Subject: Re: [Jsonpath] Publication has been requested for draft-ietf-jsonpath-iregexp-03
X-BeenThere: jsonpath@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 04 May 2023 08:38:38 -0000

On 4. May 2023, at 07:26, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> Hi all, quick AD review here, standing in for Francesca.  Thanks for putting this together.  Just a couple of suggestions.
> 
> * The term "regexp" suddenly begins appearing even though it's never defined.  I realize this is likely obvious to the target audience, but in the interests of being thorough, I suggest you do this in Section 1:
> 
> OLD: 
> 
> This specification describes an interoperable regular expression flavor, I-Regexp.
> 
> NEW:
> 
> This specification describes an interoperable regular expression ("regexp") flavor, I-Regexp.

Makes sense (ignoring the regexp vs. regex vs. RE thing, and the fact that few regexps are actual regular expressions — I-Regexps are, though).  Do you want a new revision with that change?  I can do that tomorrow.

> * The SHOULD in Section 3.1 is curious.  I've never seen interoperability language applied to documentation. 

I’ve seen a lot of those… Mostly people are trying to discuss them away, but here this is an actual interoperability requirement.
(Mostly repeating draft-iab-protocol-maintenance in simpler words.)
We will get much worse interoperability if we don’t make this a (soft) requirement on implementations.

Grüße, Carsten


> It's fine to leave it, just thought I'd mention it.
> 
> Let me know what you think.  Happy to send it on its way once there's been a response.
> 
> -MSK
> 
> On Tue, Feb 7, 2023 at 9:20 AM James Gruessing via Datatracker <noreply@ietf.org> wrote:
> James Gruessing has requested publication of draft-ietf-jsonpath-iregexp-03 as Proposed Standard on behalf of the JSONPATH working group.
> 
> Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-jsonpath-iregexp/
> 
> 
> -- 
> JSONpath mailing list
> JSONpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
> -- 
> JSONpath mailing list
> JSONpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath

v2.23.0 | Report a Bug | By Email