From nobody Fri Jul 2 15:06:41 2021 Return-Path: X-Original-To: jsonpath@ietf.org Delivered-To: jsonpath@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B35A3A0AF3; Fri, 2 Jul 2021 15:03:00 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: francesca.palombini@ericsson.com, jsonpath@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.34.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <162526338042.26814.3787482907298180320@ietfa.amsl.com> Date: Fri, 02 Jul 2021 15:03:00 -0700 Archived-At: Subject: [Jsonpath] jsonpath - Requested session has been scheduled for IETF 111 X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2021 22:03:12 -0000 Dear James Gruessing, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. jsonpath Session 1 (2:00 requested) Monday, 26 July 2021, Session III 1600-1800 Room Name: Room 2 size: 502 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/111/sessions/jsonpath.ics Request Information: --------------------------------------------------------- Working Group Name: JSON Path Area Name: Applications and Real-Time Area Session Requester: James Gruessing Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 30 Conflicts to Avoid: People who must be present: Francesca Palombini James Gruessing Tim Bray Resources Requested: Special Requests: --------------------------------------------------------- From nobody Fri Jul 2 15:22:24 2021 Return-Path: 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 919763A09DF for ; Fri, 2 Jul 2021 15:22:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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=yahoo.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 Lt9biGUdUKgD for ; Fri, 2 Jul 2021 15:22:11 -0700 (PDT) Received: from sonic317-27.consmr.mail.bf2.yahoo.com (sonic317-27.consmr.mail.bf2.yahoo.com [74.6.129.82]) (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 A42B33A0C6B for ; Fri, 2 Jul 2021 15:21:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1625264498; bh=0woO8+wFDJFpotYOMHDhZcGqKzbmu3kMoFZjhn0+QyA=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=JeCq/T8BOtmh65W4YgLp0mVmCUUImgWk/0ztHDPv5+mtg80CQ3JKVkQaMAy0qhJbDt6Xa4MX5c3GgZZdYqjEfzM4IRKw0tI7ObHAmsVdHBFcISjokp4GWozwo48Qy7M5Cl8UIOK0pc8FXyoJ3fgn6M32xdiw1X6zzTLZOv3DPwuNycuwt3lEbZnFIBEePgqBKtXVqgAW+RZ7VXMPtl5tCOnou8zXZ3FnR71zS+ItHffBKVfe8ZVXdDjFykEnidtvof6gZH0a0VzMyTYbSy/YIFZ+rl0YV+bMJtSvl4Pd3mJ61vhO5MuEqRGNxA9mY0fxHGodqali3D9q7M7UcPYnVQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1625264498; bh=Nx2gQUwpnYw5AViwyN5ooaA02ZvKj2B5lE+epNRLFES=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=r7AsmwKD20Bs3Eogg3848uCpxsu42bS3z3VqgVh9/vRUKssmiIoA0jflXhsc3YKOKovHTIxYXc2PrVNFLFJr7LUkUhz2OG38vbiJagXPaFYuiy/5eGcRxoBLLyzTPhAYcH1Sq932PzQKuse3148hXmFFUt29M0AISPsRcbtgwywEhtgnei5b0mqKwH/MeujQZ36iRvVQ8DQFf6BowZ091F0Nh/cIZ3JLHbFiRcD5J2XBamNN3hXQMjccrTiRgC0uW4e9cQByt3Uz579IvB4ATL4vZmPod9YbnSTxjKQWFWw1nUCGgxUc3fDBfGhSIIqlU+W0Df2YB7FiIjI/5hSrIw== X-YMail-OSG: eaPgiV4VM1mFY3VuF4Kd1CaZ12L49rR0ehgQlGJqkQWS3bLpHDH5fXNbmiJVUu5 2u4LLNtOMsT_ElL8GW2dN5C2nZkvqqpZ8DnhwACKEjqcHj9WmQPv9GtjXm6INFUoy3txhSZt2ax1 jGkurWoM9keW4PefdkZEsZwdby3PpWT446uWoz8HUbNe8hSsKmOTebfFTiYqw.JaOYcp9TNnjA7f IlHXtx1LoZ2Hbxe.BwkXK6D0jV5vWHLqxa9kcnqzz_cZEihAYtVNh8krfUUsfR_ebZZIkiOYdNeP qmqNjbG7pLnZvSXyDXcamGvgfwCdexN8GurH56oVjYz97roIgO4KnH8MrMzrkXbxPLje8u85wxDc jrp8RXkhT0qfkmgPxsZEa.tpp8Qg5Vmg0sDlwkGwo2vzjnrj7WQQcBY4OLdxnQHqN65gitjrgDRa K_X2QaE69yER31T2Gv5C2nPYN_pPDo6DeBVs35BrKeIH7.uSqbT7uCBEpBPS5wSRu9SXDdcpAcCy iGS8jfz8VaSBiuQfZR018taGR.3pUAcS9zjSXmaWc8nBjcocyHOSFygo6kyzq5ny370OAiXV5uNj FUt13S2raej9RZU0GHnQbxaON6IMYLae8MSFzbgliB47yRvxtbO6RyK1Io5uf7kC36nAoB03ehA6 E21gNFJ6IcDXRR18RfEr_P7MfYb5eJ7FFgoQ4b8bGVPCg44RT.i8X54.NrLknOzZDKhBVPCi.nZT qlf3AqYOMHMvYd5crxFWwddGKMNY20Kb4ivgBTthVmpELFgnh0vzQrcd95fLfHBRQnZRdRxHam8L m1Mth2MK_4p.55QHUZuNRZ06bZTCgVnr_DuRDAyfXlRDX_NB771MmYQEk_2huN.0xxYuij1.UyqM UaRRNzgB9fdzaASM1o98Yzjbqr9ihmizGZfDTVgNJ0T3k9LerRBomJiCN27nZOwGHSr_vXvzQwyE 2GaeNwAY6TuwRVPV9NPdpjPVGh1qveg8ldYSXod3MxiWYcJ88yRM85wxC0svimkLd4sk0GTcS_Mc wXlw3Ic6kiFyagmCvWIGwfDmEttoxFMBWiLmqMGj5n340wClioTcrmt2ygarcmzy7ryhk7YrUGt5 AIc4I7uEwzeb8dyz4o1NKA5Atd4K7tKIceTjlq.afFOsirEN3HdLjfAF09v_9oi.5x.pZruaJN28 lT84YV7pg8qzZ6.gORISG_D4cTomZtl4ofoVgBqhJOuwjD5PkVF4isS_Egj2fju5RTyjFmJm_wmm n7a0dtm0XTqabOBkEwkK3swy44IT_M3.FdW1SYqS8EUtxXFTbiAfI8kC4Cq6SYeXxgfLyRTW.gYV ucoibSj74aF1zMrIhXOwW_upQbct9QfZjSUXn.wFfUV5Vh42Rbsz0iQDIzucVviTmQTHmn6Ur3jF ULEQaPKXuwJovtoyzAIT9P.l.ZOPAQyyJsn1a99zn1r3NfnahTZHonQMsYQw1DhySrqkXim.Pqo3 EQYt2uoKe.iSMg9SB68WQtyUafbADDvwTd6Cynitr0UJEcfHM_0CWsy8oDvZUJE6oWcJSTAy_x9W xy10QxKNDQdwNAJdWr20fSfYDmf5V7zhJt5UKUlwAp6ZpylpqICNSNaC5Ab0C9Q_V7Pia6ZScG4w ARKEon6s4K_qdu1HJHnLUIloKhU_W4Ec3I1l61YVBH0WWq4FoILMj61TeBBL.qu_IVfmGUw3XILw aPsNKteBd4a9HgHj6bZpLnbj_IoDk8xEMGxHto7bXBEwN6W8pIPyP1_VfJvHlMAG3xvlfGGWvtoM O0M_5HfGkymjNjrs1SPdkKUx0VZtTAkZg7l1b738.LNIIC260vnzGnllCuq5YFePo..arXtXkz3z m8oHhfkEVoQfwVagKCZU4vJMsiwfG98H8aaUigcjnItfg90Ingo8RlZEOq0saEi.5f0vlvWuXdth 79wpV7FJqLTz2Ds5D6vaXLNVsVyt3CtqWAAH0xFbqy6wb8MYIdcsDBN_tMYIthQ13FsSykaCfyV1 QuNO358UFnuH__Ufm_7C4rrM4Mc7.LX2aAGcFvbAAd30H7CWj5NPSTI81SeWtRmNmOUUznO2iR6n Nu0P3zLj9pS0_B9jHhOngbkxicw4v9JS7bjM0OulDXjkLqfEx4lo5L94eKTsvFsFhDkVj2Hl7KVp NCJFy4V2Iek5mrx4P0eTbeyzZdAw94DpGYvi4budDlwaoT5XRJyC69kdxg2SeDDNaAlUg4rQufEA x0Sxu8pdCbb3nipscrUzhE3Koy6leaJ5CzgwQY60FJ8rRb0TMnmVtkrLas5wVX0eNDseA8gyPCuu bA6MioAwdYYerivEwiecdzZhXPR5JkDqTdv3rD.ba.Yrg3LRWk79BArYuA4ffDd9VPZJr602eqGn gjBKiErQOQD9s1drpDp4sXLsrD_NUvAiRfdJwL8QRDPYHl3tVcd2SMJLczYZMoRR_B70Hz6VyUCP ix_duB.Py.AuSpTswkTZJLFS74XzbWB6oh66tgyv3hbIpog3UU6ALKDeQRwJ0THOcWbbc_1iwJSs VTYD7FBFr6dylEhiDk60olK1Hsh.RVqrkQ_02Z0jc2w6bGVz.XDDWwHhgC57hXZXyDcH2KNjQCxX mIjYQD.cYeQ-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.bf2.yahoo.com with HTTP; Fri, 2 Jul 2021 22:21:38 +0000 Date: Fri, 2 Jul 2021 22:21:28 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: "jsonpath@ietf.org" Message-ID: <1526584247.913967.1625264488747@mail.yahoo.com> In-Reply-To: <162526338042.26814.3787482907298180320@ietfa.amsl.com> References: <162526338042.26814.3787482907298180320@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_913966_2039803049.1625264488746" X-Mailer: WebService/1.1.18469 YahooMailAndroidMobile Archived-At: Subject: Re: [Jsonpath] jsonpath - Requested session has been scheduled for IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2021 22:22:23 -0000 ------=_Part_913966_2039803049.1625264488746 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I probably won't be able to make this one as I'll be in the middle of my wo= rk day. Greg =20 =20 On Sat, 3 Jul 2021 at 10:16 am, IETF Secretariat wrote: = Dear James Gruessing, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request.=20 =C2=A0 =C2=A0 jsonpath Session 1 (2:00 requested) =C2=A0 =C2=A0 Monday, 26 July 2021, Session III 1600-1800 =C2=A0 =C2=A0 Room Name: Room 2 size: 502 =C2=A0 =C2=A0 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/111/sessions/jsonpath.ics Request Information: --------------------------------------------------------- Working Group Name: JSON Path Area Name: Applications and Real-Time Area Session Requester: James Gruessing Number of Sessions: 1 Length of Session(s):=C2=A0 2 Hours Number of Attendees: 30 Conflicts to Avoid:=20 People who must be present: =C2=A0 Francesca Palombini =C2=A0 James Gruessing =C2=A0 Tim Bray Resources Requested: Special Requests: =C2=A0=20 --------------------------------------------------------- --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_913966_2039803049.1625264488746 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I probably won't be able to make this one as I'll be in the middle of my wo= rk day.

Greg

On S= at, 3 Jul 2021 at 10:16 am, IETF Secretariat
<agenda@ietf.org&= gt; wrote:
Dear James Gruess= ing,

The session(s) th= at you have requested have been scheduled.
Below = is the scheduled session information followed by
= the original request.


    jsonpath Session 1 (2:00 requeste= d)
    Monday, 26 July 2021, Session II= I 1600-1800
    Room Name: Room 2 size:= 502
    ------------------------------= ---------------



Request Information:


-----------------------------= ----------------------------
Working Group Name: = JSON Path
Area Name: Applications and Real-Time A= rea
Session Requester: James Gruessing
<= div dir=3D"ltr">

Numbe= r of Sessions: 1
Length of Session(s):  2 Ho= urs
Number of Attendees: 30
Conflicts to Avoid:







<= div dir=3D"ltr">
People who must be present:
<= /div>
  Francesca Palombini
=   James Gruessing
  Tim Bray
<= div dir=3D"ltr">
Resources Requested:

Special Requests:
 
------------------------------= ---------------------------


--
Jsonpath mai= ling list
------=_Part_913966_2039803049.1625264488746-- From nobody Tue Jul 6 02:38:48 2021 Return-Path: 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 0F0853A20C8 for ; Tue, 6 Jul 2021 02:38:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=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=gmail.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 YmTERUVm5SZb for ; Tue, 6 Jul 2021 02:38:41 -0700 (PDT) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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 4F91E3A20C4 for ; Tue, 6 Jul 2021 02:38:41 -0700 (PDT) Received: by mail-pj1-x1034.google.com with SMTP id b14-20020a17090a7aceb029017261c7d206so1131240pjl.5 for ; Tue, 06 Jul 2021 02:38:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Hjoe1pCoRLoR9oZFziXcgaKgfvyVQ7zUUefCBp9rXtY=; b=b/QuLiC1gFmJ8/4afIOK4N6Au6EG3lw6EcNeSqZSWD84tCt+S9VQsNZESfJ77Lw/1b LCMMhRMfkVHJ0//t5X9bssQyjuFEm9hX3QXRj2AG+knSRetvd2i3XmrYs9iWApefyN7X 9YjC485/eAOA39Qmx4p7Md3POqpFIgBHu+neutMQoYLND/1QlkZP9MejuMyJsQnzavLx 6jTAJP+zZ/bJlYxMyJ1tmv+d4oxXfhOmLVUS7OR3XcRslaqibSyoHF0s3eO3sSfGcrrM 0IYQ1gh7VXklDCBnv9JHsD2Wvq0rbK3y4+XynZHpozIfWLwsTp7rSp+1Oj9Ib+tzwM5e h0QQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Hjoe1pCoRLoR9oZFziXcgaKgfvyVQ7zUUefCBp9rXtY=; b=VE7hBJsfpHz59X3WxZUg6ktsogugM+rnAX14SBWSAWYwdHrjSYzf4dEshY7WPtNk5P eEKNTQQSht5JsDqynwA4jJikuowkHzI5klVyhTAFPhkHlWomUpyX10C5NLUSRMU3+SnN 0EJRFOCrwSwdHJsVnEtt24oNi4eGq6+KqA7p41+3/zw9+rKLsEkp77a1+Uk5lEe2fG4W 8ZuRO4z/95jy64nrY6RcWHeT9ZrMDMyY7caHT94LHXTG0lE1Pj8sWtaVLkfdUP8mcGeH 9EnXsTko/BA3XJs4c5NH4z638kGSm/XTJb7dekPrdU6HlgBJAnzdDi68lKRSN/WUEWdI YhEw== X-Gm-Message-State: AOAM531rkgOLGjD773EcJuJ924EXHWOlyaxAuXNAoWW9Vbo2PsFUNtKl QHJFkyCLDlCEwUStH0RJheRm9dz/8Dyqk11JB5K7yhasM0k= X-Google-Smtp-Source: ABdhPJypa3o97WjMVmhsVynZJ4wycv6s6YLgmric4pF7a9zBuQRIIWt9qYFucwF8h7JM47W4PDZOvklSjG7fsCgzS8s= X-Received: by 2002:a17:90a:c002:: with SMTP id p2mr3402885pjt.132.1625564319629; Tue, 06 Jul 2021 02:38:39 -0700 (PDT) MIME-Version: 1.0 From: Glyn Normington Date: Tue, 6 Jul 2021 10:38:28 +0100 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] Broken reference 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2021 09:38:46 -0000 PR 142 produced a broken reference for no apparent reason. I re-ran the github "Update Editor's Copy " job and the error persisted. The referenced datatracker item seems ok. Does anyone know what the problem might be and how to fix it? Here's where the broken reference is visible: https://tools.ietf.org/rfcdiff?url1=https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/draft-ietf-jsonpath-base.txt&url2=https://ietf-wg-jsonpath.github.io/draft-ietf-jsonpath-base/authorship/draft-ietf-jsonpath-base.txt Regards, Glyn From nobody Tue Jul 6 03:26:27 2021 Return-Path: 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 AB05C3A2221 for ; Tue, 6 Jul 2021 03:26:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 oY52vqRJOL6Q for ; Tue, 6 Jul 2021 03:26:21 -0700 (PDT) Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [134.102.50.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBDE63A221F for ; Tue, 6 Jul 2021 03:26:20 -0700 (PDT) Received: from smtpclient.apple (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GJzHG26KGz2xG3; Tue, 6 Jul 2021 12:26:18 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) From: Carsten Bormann In-Reply-To: Date: Tue, 6 Jul 2021 12:26:17 +0200 Cc: jsonpath@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Glyn Normington X-Mailer: Apple Mail (2.3654.100.0.2.22) Archived-At: Subject: Re: [Jsonpath] Broken reference 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2021 10:26:26 -0000 On 6. Jul 2021, at 11:38, Glyn Normington = wrote: >=20 > PR 142 produced a broken reference for no apparent reason. I re-ran > the github "Update Editor's Copy " job and the error persisted. I can=E2=80=99t find the error in = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/runs/29973756= 64?check_suite_focus=3Dtrue But I=E2=80=99m not sure I=E2=80=99m looking at the right place. The previous build was in = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/runs/29973265= 23?check_suite_focus=3Dtrue And that indeed shows one of the temporary failures we have seen for the = DNS server for rfc-editor.org: /root/.cache/xml2rfc/reference.RFC.6901.xml: fetching from = https://www.rfc-editor.org/refs/bibxml/reference.RFC.6901.xml 15 *** Can't get with persistent HTTP: Failed to open TCP connection to = www.rfc-editor.org:443 (getaddrinfo: Try again) 16 *** Failed to open TCP connection to www.rfc-editor.org:443 = (getaddrinfo: Try again) while fetching = https://www.rfc-editor.org/refs/bibxml/reference.RFC.6901.xml 17 *** No such file or directory @ rb_sysopen - = /root/.cache/xml2rfc/reference.RFC.6901.xml for = /root/.cache/xml2rfc/reference.RFC.6901.xml 18 ** Can't manipulate reference XML: undefined method `attributes' for = nil:NilClass 19 *** KRAMDOWN_OFFLINE: Inserting broken reference for = reference.RFC.6901.xml The next build you started got this right, but did not update the GitHub = pages. I don=E2=80=99t know why it didn=E2=80=99t. The artefact = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/suites/316732= 3681/artifacts/72923752 looks right. But the stage =E2=80=9CUpdate Github Pages=E2=80=9D is simply struck out = in = https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/runs/29973756= 64?check_suite_focus=3Dtrue Rerunning=E2=80=A6 Update still crossed out. Interesting. Gr=C3=BC=C3=9Fe, Carsten From nobody Tue Jul 6 08:22:32 2021 Return-Path: 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 990803A2B67 for ; Tue, 6 Jul 2021 08:22:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=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=gmail.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 ZU1vM3CEoczU for ; Tue, 6 Jul 2021 08:22:25 -0700 (PDT) Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (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 B1DB53A2B61 for ; Tue, 6 Jul 2021 08:22:25 -0700 (PDT) Received: by mail-pg1-x536.google.com with SMTP id s18so6624389pgg.8 for ; Tue, 06 Jul 2021 08:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=eITBALlCwvvvP1zK2/dFgzSJuE6qh63ratKcJzf9OFU=; b=JDOGtwrK78rhYVXrMQvxtwIT8N2chXu+QBfMMgReS5kCg0+T0Yg2EQeEfRu1ss9Y1a eip5/4RaALt9QjLzNTXfGBAg5ArkHLNP8OAQzKo/kaSFGTTTOhKAJj4C9KsztaWwNVOJ uIrhxfXFE8G4+LPQiX7qWS6RSQ93XXDQNgoyobKodIN1aKEfdriLvKIm5LPedTjLuTA+ e5SuS2BK0j5zOn2OLxa/jxlEfuOzLm73gCVIfQQWjFLmatYdc3CxltPcR8UELZcBNcq5 FqRR5PIDZeawKXTiP7HuOZMUpoMoX5/9dmDBev8U+2SCdmNwa4o8Szo761EwvIRMs/Dd PseA== 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:content-transfer-encoding; bh=eITBALlCwvvvP1zK2/dFgzSJuE6qh63ratKcJzf9OFU=; b=tzLkkTPMWAPDHSh4DoTDJjZsXH9Eove7G571Uua58WKR7tqQI40PVq8pCnERNGtbn3 /1H0cEMrHHOiAR5lmFl3rpaJwfccv8SpGWkFixIx9aSxLCg4mELgGO9T0lQ6tJ1HPz2W LzkwExWNDxA6X8KCH0MEIPP50NY4ngQvxj5X/6wHykD1G4HwZ6YvfHeUCDNhnCYuBsEu 3neaiqZFG2oTPnXYwJhzi1WUZJ+GTdB34QZ4v78O13OQ4nVgCL12ECoVuPb0DpR6O1xJ BU3QEelaO4s5qCcZWKz/mVI1eUt7fCHYvDHn6nfmG/q9yB/YY9wvc8tyFFGchNhVX+7Y FwaA== X-Gm-Message-State: AOAM5308uUpvYYl4Ne3YOBijRkysajAbYVAtR6smi7gvOyt6wLGQxrFo BShAyiJizheAyPpHzdUEhMK+gCp8WbbBinR2T7k= X-Google-Smtp-Source: ABdhPJx37x+qzjVEmoXzvGa1UvgShl3H7zecPS2q7ZPppMr8zKLb3bK+rDWI0QPSlFjnuMM9H3Z05Uz7tks+C3ofUnk= X-Received: by 2002:a63:5210:: with SMTP id g16mr5057144pgb.217.1625584943914; Tue, 06 Jul 2021 08:22:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Glyn Normington Date: Tue, 6 Jul 2021 16:22:11 +0100 Message-ID: To: Carsten Bormann Cc: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Jsonpath] Broken reference 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2021 15:22:31 -0000 After making a text change, the broken reference has healed itself up. The update step is still crossed out. Oh well... On Tue, 6 Jul 2021 at 11:26, Carsten Bormann wrote: > > On 6. Jul 2021, at 11:38, Glyn Normington wrote: > > > > PR 142 produced a broken reference for no apparent reason. I re-ran > > the github "Update Editor's Copy " job and the error persisted. > > I can=E2=80=99t find the error in > > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/runs/2997375= 664?check_suite_focus=3Dtrue > > But I=E2=80=99m not sure I=E2=80=99m looking at the right place. > > The previous build was in > > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/runs/2997326= 523?check_suite_focus=3Dtrue > > And that indeed shows one of the temporary failures we have seen for the = DNS server for rfc-editor.org: > > > > /root/.cache/xml2rfc/reference.RFC.6901.xml: fetching from https://www.rf= c-editor.org/refs/bibxml/reference.RFC.6901.xml > 15 > *** Can't get with persistent HTTP: Failed to open TCP connection to www.= rfc-editor.org:443 (getaddrinfo: Try again) > > 16 > *** Failed to open TCP connection to www.rfc-editor.org:443 (getaddrinfo:= Try again) while fetching https://www.rfc-editor.org/refs/bibxml/reference= .RFC.6901.xml > 17 > *** No such file or directory @ rb_sysopen - /root/.cache/xml2rfc/referen= ce.RFC.6901.xml for /root/.cache/xml2rfc/reference.RFC.6901.xml > > 18 > ** Can't manipulate reference XML: undefined method `attributes' for nil:= NilClass > > 19 > *** KRAMDOWN_OFFLINE: Inserting broken reference for reference.RFC.6901.x= ml > > > > The next build you started got this right, but did not update the GitHub = pages. I don=E2=80=99t know why it didn=E2=80=99t. > The artefact https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base= /suites/3167323681/artifacts/72923752 looks right. > But the stage =E2=80=9CUpdate Github Pages=E2=80=9D is simply struck out = in https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/runs/299737= 5664?check_suite_focus=3Dtrue > > Rerunning=E2=80=A6 > > Update still crossed out. > Interesting. > > Gr=C3=BC=C3=9Fe, Carsten > From nobody Thu Jul 8 09:03:54 2021 Return-Path: X-Original-To: jsonpath@ietf.org Delivered-To: jsonpath@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B5B13A2675; Thu, 8 Jul 2021 09:03:48 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: internet-drafts@ietf.org To: Cc: jsonpath@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.34.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: jsonpath@ietf.org Message-ID: <162576022799.11454.8794507765217862657@ietfa.amsl.com> Date: Thu, 08 Jul 2021 09:03:48 -0700 Archived-At: Subject: [Jsonpath] I-D Action: draft-ietf-jsonpath-base-01.txt X-BeenThere: jsonpath@ietf.org X-Mailman-Version: 2.1.29 List-Id: A summary description of the list to be included in the table on this page List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2021 16:03:48 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the JSON Path WG of the IETF. Title : JSONPath: Query expressions for JSON Authors : Stefan Gössner Glyn Normington Carsten Bormann Filename : draft-ietf-jsonpath-base-01.txt Pages : 29 Date : 2021-07-08 Abstract: JSONPath defines a string syntax for identifying values within a JavaScript Object Notation (JSON) document. Contributing This document picks up the popular JSONPath specification dated 2007-02-21 and provides a normative definition for it. In its current state, it is a strawman document showing what needs to be covered. Comments and issues may be directed to this document's github repository (https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath- jsonpath). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-01.html A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-jsonpath-base-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Jul 8 09:06:29 2021 Return-Path: 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 662E13A26AA for ; Thu, 8 Jul 2021 09:06:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=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=gmail.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 ejTHOjgZMiTY for ; Thu, 8 Jul 2021 09:06:26 -0700 (PDT) Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 2E0A23A26A9 for ; Thu, 8 Jul 2021 09:06:25 -0700 (PDT) Received: by mail-pg1-x52a.google.com with SMTP id f5so6487978pgv.3 for ; Thu, 08 Jul 2021 09:06:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=oV434H5Du6bGSJMhSrqE1Ieintr5lSgmLspEsTY4jaA=; b=XIG2ktfvbjk/PuXFApcboDqtImHqZQeUPZj8CJgwdpSGb2Q99u2n1ZPLj7g3zl7ocw sUUuxeleGZyKQlsn5QoiuYGV+Rn0aSND/8GF9b+lOwFBV1CQQ27UrpVxORvXYFkXTRyb ifDyP53Ag+X/h0kF/jpKWckQgyvSabyq/HWqObzwepiGv9WuPWjAu2eeofEs54x9RGEx GSBKrkqLqlXvJwyIcgRwtKUmcHvHx3hLHXS+pwLaH4vBkcg8JXUGabqhtqRLFN51QaRH CdHUlBQXUdjxPkktOrHySR9VZQG4snPG8PStnnGuWdHAwaVWc6jXCT2rKVS6t9JLZsVS RibQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oV434H5Du6bGSJMhSrqE1Ieintr5lSgmLspEsTY4jaA=; b=feaHnHemrum5w0k3kbIO5h8wP9SkO7VJNBPjVdXP/TTh7+Vn2SFzLConrh9eHvHU5v SB1ZgWbxcbXT40CFBpItomVIEoHrCorQmggLURVmMTkdey+zHMng6mycWqTcLhsnmJgW 40ZkvbqplZj0ncjS7BG3TcIZXEa8NLaIgrbDQj0jCX1U3h5DYhDHZOoS2oQc7LmkvwLl MrdOReW6yAwX4dyW1GvQ51+YsnMiMnqKU7bs/1VsgWvXaOqYQFnOsUsvrmh4RZqRrJUM RtzBKR14qv8wOS1f291CZagKCd+SiWDts8jP9oAnkrzma9ZstqG/1DpPTsZNFFsrnbkk ib4g== X-Gm-Message-State: AOAM5327qyqDf/a/gyIdkxy7/MD8qKYfp9UpBJtXcbBmHdXR/GFnlMzr QM6AArwBGuW1f7MoLlw2cL7ur/1D4vmFzhRc/S5nl81hWDfgQQ== X-Google-Smtp-Source: ABdhPJwLvCZPPVonWkvijEvfRaK6b/jc42QmuM1E0N6mj+Xagw7QNbFLROJDj1Z3R9qg3SmDSYGJhlbRVVb3uKolcK4= X-Received: by 2002:aa7:86c4:0:b029:316:98ff:30c with SMTP id h4-20020aa786c40000b029031698ff030cmr31984021pfo.66.1625760384696; Thu, 08 Jul 2021 09:06:24 -0700 (PDT) MIME-Version: 1.0 From: Glyn Normington Date: Thu, 8 Jul 2021 17:06:13 +0100 Message-ID: To: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Jsonpath] Draft submitted for IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2021 16:06:27 -0000 I took the liberty of submitting our latest draft before the deadline of 12 July so we have a clear starting point for IETF 111. (This time I submitted an XML version after advice received last time.) See https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base/ for the uploaded document. Regards, Glyn From nobody Thu Jul 8 09:59:08 2021 Return-Path: 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 8390E3A2A09 for ; Thu, 8 Jul 2021 09:59:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 cpJKGgS1EpNW for ; Thu, 8 Jul 2021 09:59:04 -0700 (PDT) Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [IPv6:2001:638:708:32::19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E99703A2A07 for ; Thu, 8 Jul 2021 09:59:03 -0700 (PDT) Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GLMvT0JRnz2xHS; Thu, 8 Jul 2021 18:59:01 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: Date: Thu, 8 Jul 2021 18:59:00 +0200 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 647456340.710593-7d667fc3b8e022e329c688d35afdc7f9 Content-Transfer-Encoding: quoted-printable Message-Id: <48581C60-CC6F-4A82-848D-33DC263B0EEC@tzi.org> References: To: Glyn Normington X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] Draft submitted for IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2021 16:59:07 -0000 On 2021-07-08, at 18:06, Glyn Normington = wrote: >=20 > See https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base/ Which, by the way, points to the more readable https://www.ietf.org/archive/id/draft-ietf-jsonpath-base-01.html that one gets with an XML submission. Thank you! Gr=C3=BC=C3=9Fe, Carsten From nobody Thu Jul 8 12:53:08 2021 Return-Path: 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 895233A182F for ; Thu, 8 Jul 2021 12:53:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=yahoo.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 PjGS7Bip8HQi for ; Thu, 8 Jul 2021 12:53:02 -0700 (PDT) Received: from sonic309-14.consmr.mail.bf2.yahoo.com (sonic309-14.consmr.mail.bf2.yahoo.com [74.6.129.124]) (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 D966B3A187E for ; Thu, 8 Jul 2021 12:53:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1625773979; bh=veEjgojMISPRb7hJZtlrRpvTIfo32cU2InSQ0LYvM5M=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=mQlYuGWWQtlafeEYGUk9lZoVzvIwWx0/6MIJUwoW8spLCjdg6/uZn9zCevEobJyXGBcOqVgGPj4oczxINjKMekZDslb3HOtSFgcIBhtkLzNjVXhq+rFspYkZTF6JrEZf+nnVLJZKbl+WIwkmvyXC2fh0S2hQRQ5MRgDgM1+C6/n4+obAwFJgiPyWWsqyNULxlDuE7rU1fTgl20GVgFujj2gKY5DjZ6eSpx6bu5VFawuWkynvaNRsLvtFmH4bzPXz72YbT+gKb+0Ci0O9hOeaHX8YvKxL0LlJ/61r33Fefd0OzLqwJGojwYVHA2aMbrh7AAkMswsc/Blz6+VrXYQ05w== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1625773979; bh=vqcZSWDcSN9dQpA3o79SS7PjDlR5IU2IdjjTeT3+Qyq=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=j/Br9Tg5WkOY4ehBRjPPiKkS49Yb67Yb3c5LaBeVeGYiixH2MKY9KVnktEDwFwdKLaMBUT0KI/TGAVt0bLFzW+KRtC5bitWaI3YYZaryRmpkWvYez2tMfG7sZ4A7q4ExyUY17+zDPBW+lgGFXJ8VGs/dkNEoKqFz+jxE5y0qdIljTzGVWOY6Ql0ILrumZKhzMbvsfgWFvt4tS61LPz3ywdN+iiwhn/gjugVdA87DOj3LgyQxc20dXwJwlAe041NEVX2756IASrzeLN5B2el24sNnprc73xyQdLS6CRal1luuRB9QMW7P0PoSinc5RXy6piu/Cn8blRUWCvXrXBAWZQ== X-YMail-OSG: dijPXoUVM1lgrs.Jp2C5jJU.Ev6u1jKuBH9PUgZ9u75LFxxK9GofVUoscknwHtO OeKYUtebbruQJ7BdN.9L_l5Hk1M1iVI6OxYx.aA6u.f9E54KgyaC4nuQW1tD8LOB..4e1.XmReOe UlDd.u0igv8p.yonnk3B7vvdpS2LYigqSuAXhj54rhDv.JlN74Oi1feVKVxoVZ_DwCCrqwprPFWs tCkBNhjPT4dndrWjph93mqXgKNP6d45XSRXYa6PtsRfIyMeVfFp7zdPuhbyT7_Ik7U7Z02vAjere VaANXxiLiSq9pkb1LenBmHzXq0idoYK9udVERcBtdqZi1.VxrGx1AVjgsFZF9RiOWh4bNa_6yxU5 TpIeFAdKstesf3kRvBZ7qHGGnd8fOgVVHtccC6eAu3AfxeRKGeUbOtZok5xIbbBaL6CGUJ5mNd2M atcs.a3Cy3TK01U2kBz_6spGSBrv29dJmPt.Dg_nEsxfBgQeosYQCIBqcuuCLG.ggKAMgjW6g33p N2sLCeUw6clyQ_h8XMabN9oaY_8RO2E2dgW2EUvwXJkB0h1IP3mMFtqmgcFzcgkIDD0OvjLJU.QX tB1O.DzntLp1lZa1Av2bpcDwd2UjUm1Sn8EQ4bj99XfOMsmcNscNOOjoCwDooZG1IGxHwN5Iznmd m76eOrXfWjtiMXJaC3SMnZZGWrMS.4qIr.8aN0cHRNMbJppSm7tJtoqBkGXyVWxK_XmzWcor3t1i IZK8j9GuR4Ja.wQQ9_0titS17KYT.dObz5gy3pcAyoAMzaki7o6vXKSRcOMIG3U_ljrcuACjq_81 LQ93pSAhoO1Smz0asTbIRlxTSslc4hHwgre_1Mu5iU08f7OAcTlykbDyXxrCsa0CFcGQUT2aIi_Y piNvU.e.Fvl3fuqh_R7eF.4PPCMXYhJewK53Am3nbLCD93y426csaT_4ZBitV1NOjl8q.1t4EIGe nCxEZJPTrzQs4RMAX4gSZ62ZN5RHdFQYrnif7E3Fk4SRUqrPEbgvOLqSd11osTITaspwGRBJLdmn qYFYKIhzNQG2zyyEX5eYtGYVssZ_xmqOPZxMhGNLAoBedXkY66yj6s3slp8KWQZB0dPLiZSBSdSE vcrfPO2IifgVh9QfwbSSI5pDP1YEc9S5pZA72LgHk26BAgR_IlICfoi4jond.SA7kB8mJs7hhVy3 JSUIwbohaF2.ea3XDb0ZOIAvcBt5kcGpE7PNctIbDxw8UuKUg4iELD_Vhk_jTrJ4Pt22fsb5hWlt nncEwZ9D4TmpuV.ANkJFz7iSw_tpd2dwK47jupC_6Zu4xswKwZqekxONILyI4rFjUa.I6nvzt72B MgBfob_LXavm4LJJYPIKwjgx7lzJB13llK._Fn_GJgQarFEXC3E03s5K0HuakUr0j6wXAdtGiL.2 Z6EMU5fcbXa3rGfLTyLPWwOfpZj2pcly7zQuv.sagN_eIdYhF7hnPmZD6QVfLf33WWbKSG4tzoKq wjRL_x2G41YsJdOetEvDHChCgWUMkeju2HPuFbjd_yulRr8s5z1s9w9wK3VyE4MmHf83iC5OnoMp D6PkyUy_U31digh9HOlboLnndJYXmiSSiXo074pIAixWjKb3XlXW43dpFB4D3oif5GGblGYhfBMs zn2BkMyJnrtGGoIC.YYETY_0PGBtTJ8GfBqxnZ5O3yRYf4_b38F11pBspe.uHEvPAWWsOYk_wTB3 i0oW28ieg6pDQJCoLih.wPQ7tuVQQ1o7NQGBgD8Sbw3qfOTUSjOE.o5udlZIPDYnd2h0KUgzEdhV N_Swey15ZQFKktEQMiFexg_HHTi09EodAbz7PSooc0vvi0jAynv4gFDYeKG78f7crXtNEpHJ0hH9 mn2r6hO4i4i9t3slcmFSqIfud2Av_azrdpouXj45SL3tuToT0Z4jyP4J1VfLYddtHgUS_6IUkUy. ffG_vteEJ9uBLXkieV0xDvCA85dVqumEOuSYhI01s783.qm0LeRub49LhDggiXtmt28SYJpsDAuM mjePpPbHrXBnG6dhrGYfVA5AArKvZ0tgZCI22yFPB7F0qI_SyZlgHqZlGIEaU4wpzdSmr0s5pK.d _BBOUhWyhvA5YkZv0HjLCV4Rt6jlOvjr5NzgkFVuTn4JnOdTb01LZGpCA1jmwY58zD6rMivhG_05 186wpVS1Kyn.MGpeWBZctbtW9qjNpZudV2Myvjw_nKO91DZXXulPy_wcxQ65abI.DE5tjpCqbvUU lk3PZ0Ag9OCdrdoq3brsQzdajvxkJgo1HNnfSosatMmXM.ZIoYjDvGdV6FZS2Y9N.Dsv9RftlCr. XUQYJp3CR4ftS4OZHnVHmafm5cjAvVCWZCvZza7HzjkCF4RzBGOUR1Y37Pka7uuMpKlDH55WqOqW D.CISPD07ZzvBgNBflezHlhpOJsRy1aHt_NxOEl3MoMqcIMFS6YSSBwfnWb6L6qi8u5Yk1SadQ6H d3IRWq7b8L9MPS_tygBksKoVziWhWaVN4qSxinmDJjXK3yvLHhDWxQNclT5W6MsxtEJ_wjdYkCP2 Tot612.wFDp_qPAQh.K6AdeIxxIYflfgtAkkzcA-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Thu, 8 Jul 2021 19:52:59 +0000 Date: Thu, 8 Jul 2021 19:52:50 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: "jsonpath@ietf.org" Message-ID: <1825056111.1340432.1625773970584@mail.yahoo.com> In-Reply-To: <1594462686.2396269.1624755076394@mail.yahoo.com> References: <1594462686.2396269.1624755076394.ref@mail.yahoo.com> <1594462686.2396269.1624755076394@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1340431_959738512.1625773970583" X-Mailer: WebService/1.1.18469 YahooMailAndroidMobile Archived-At: Subject: Re: [Jsonpath] Odd syntaxes in libraries 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2021 19:53:08 -0000 ------=_Part_1340431_959738512.1625773970583 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Another SO question regarding this syntax. In this question, the asker expresses confusion after finding the syntax deep in their systems. https://stackoverflow.com/q/68304125/878701 Greg On Sun, 27 Jun 2021 at 12:51 pm, Greg Dennis wrote: I just came across a StackOverflow question (https://stackoverflow.com/a/68145809/878701) where the answer highlighted a feature of Jayway JsonPath: Filter Predicates (https://github.com/json-path/JsonPath) The syntax is a bracketed selector with a lone question mark: $.user[?]. This is akin to string interpolation or substitution where the question mark is eventually substituted for a filter that's defined in code. (I'm not sure what would happen if the user tried to "stringify" such a path.) My concern is that this kind of feature seems to say that this syntax is supported by JSON Path, when it's not. Just wanted to keep people aware of things found in the wild. Greg-- Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath ------=_Part_1340431_959738512.1625773970583 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Another SO question regarding this syntax. In this question, the asker expr= esses confusion after finding the syntax deep in their systems.


<= /div>
Greg

=
On Sun, 27 Jun 2021 at 12:51 pm, Greg Dennis
<gregsdenni= s=3D40yahoo.com@dmarc.ietf.org> wrote:
I just came across a StackOverflow question (https:/= /stackoverflow.com/a/68145809/878701) where the answer highlighted a featur= e of Jayway JsonPath: Filter Predicates (https://github.com/json-path/JsonP= ath)

<= /div>
The = syntax is a bracketed selector with a lone question mark: $.user[?].
<= div id=3D"yiv5049699227yMail_cursorElementTracker_1624754905479">
=
This is a= kin to string interpolation or substitution where the question mark is even= tually substituted for a filter that's defined in code. (I'm not sure what = would happen if the user tried to "stringify" such a path.)

My concern is th= at this kind of feature seems to say that this syntax is supported by JSON = Path, when it's not.

Just wanted to keep people aware of things found in the w= ild.

Greg
--
Jsonpath mailing list
Jsonpath@ietf.org
<= a href=3D"https://www.ietf.org/mailman/listinfo/jsonpath" target=3D"_blank"= >https://www.ietf.org/mailman/listinfo/jsonpath
------=_Part_1340431_959738512.1625773970583-- From nobody Fri Jul 9 00:39:47 2021 Return-Path: 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 BAAB93A165F for ; Fri, 9 Jul 2021 00:39:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.897 X-Spam-Level: X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no 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 yr3vESJZUxMJ for ; Fri, 9 Jul 2021 00:39:38 -0700 (PDT) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36E543A165D for ; Fri, 9 Jul 2021 00:39:37 -0700 (PDT) Received: from [192.168.178.20] ([87.123.195.40]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MXoQG-1lgj8W0FDQ-00Y7nW for ; Fri, 09 Jul 2021 09:39:36 +0200 To: jsonpath@ietf.org References: From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: <2fb633fd-7d6c-d12a-691d-7841f564a059@goessner.net> Date: Fri, 9 Jul 2021 09:39:35 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------F95A430658B5388FFEFE1899" X-Provags-ID: V03:K1:BX9w7qQVqdg2XhRXjy8yMwHA/Njn853GWNL62Qd9J7zLQTgFFS2 AYk28HnXcCtv4GBrCxq+MzPvmbwtPytpzZ47Plc2yueAURmMxSPEEcxi9LADmdwPFAPZtld LA9l59c08vKP8YWEw4DEfuYFvnQwCLK9gVDX0B7Tim4s1bfJfRqUQk9SoRksUC49BT4QGAr HcGdrtoHKYjjY2tRUwNUQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:WVFB82g1/AY=:YIJLteFufYxe/FNc5/0waH nIpUvYyfKfA1eWTUXxSjUQxzB1dJ7WfLsdYr48xFi/yTY81iFnoMH7s/3U3aW6xtqH3SsiTMd TfMKrwWmzrJUVe8ArZDhM8shUfL2IMnG9fyqtKzz4V7/XzH8fvlEiYTC2eVOiTj5uiX00Mepz x/s+JlPvaT2qF/6Sfu0Gg7rKFsbjNuE9AO45H1TEMsTV0k/FKtoEV5593xyyGunLaNBIlPmFM NBa0tKKH1wkQXM17WAF5XH7s/U6O+ZlSgLz/q3/pBGA+zCRozk1yyqTtfRJvZJV5NXiYcXBMR Sv1aWfxmma2LIW6zeZ6cCzlz+sNbF81ynyFIN3LQRvZw9GQ3ce1s4xgvKRbotXEi00YlNZGHg 5KCeWe31TUetlk6mkqoijaJ6KfzownBANSfadMUBCA99zLLSFqDDW0rv6iw55BWxZloW2iHGz L4KQmX4ktTZ3j6EDyNnBSo7hpghYX1R36Lcyp62b4NuMgog3V3gR1i4titYhbxNAI1AztgZ9Q pVQh1pQpt6alrRRw5NH0wFsCahcvGa1xhd5dQGWl6kVOKw30zPLYe35dnTtG1UG9GYhZHp+OW Rnh8Axxi1KkdO7OKeBetWpqkYaocNE5ceojAto25iVFlpRll9yK3lciyIGXTz+QuIp1WtckyS m/66j/u9HcuB7VncalI1nOS98eF1F0XRcteSmqnWbSuw+u9W0uRIIKNxk8klsZjodN5aTTZdN FS56vctzOPIYaOEcJtW2emJvM00XbpW8zOrhn8433RtzNf3zLacl0QBRzu2homJRfqxhefM2K NEGGdkGs/QGVZUWSS0oC8xwROwbQFz8xmwmpTT79YwoX49mG1yob3BbsJPDS6cbpo9snPZ1y5 mdSecptUWvVKhfSpbsdQ== Archived-At: Subject: [Jsonpath] work travel ... 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2021 07:39:45 -0000 This is a multi-part message in MIME format. --------------F95A430658B5388FFEFE1899 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I would just like to inform you, that my communication will be restricted until July, 22nd. I will be able to read emails via mobile phone. All the best -- Stefan --------------F95A430658B5388FFEFE1899 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit I would just like to inform you, that my communication will be restricted until July, 22nd. I will be able to read emails via mobile phone.

All the best
--
Stefan

--------------F95A430658B5388FFEFE1899-- From nobody Fri Jul 9 00:50:05 2021 Return-Path: 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 9AA343A16C0 for ; Fri, 9 Jul 2021 00:50:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 po-Yf-oF9PVv for ; Fri, 9 Jul 2021 00:50:01 -0700 (PDT) Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (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 47F933A16BC for ; Fri, 9 Jul 2021 00:50:01 -0700 (PDT) Received: by mail-pg1-x529.google.com with SMTP id w15so9120943pgk.13 for ; Fri, 09 Jul 2021 00:50:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=oOhVOEPeEa/Oi65Klty6ghOI1gD7r0ukgKDT1u9dSOY=; b=qPWj+lo2TnVSa8WLC4MO8AuQN4B7bHEwIVub+pBWw1Py9XY8RZop45EDKBB6HdVBDg HBHJYkjfnv5fxU0n2yJLZnepVAwVR2zmhbtFL2E/JO8wCrZNi+vz1wUxZrnGZR9ut4G6 TtL2G7MPLaJ3VJNx1g+5crh4VGrAKkMJqTS67NQTZeqPqJ1sO/nqPLAtJ8qY+FEL7Dh8 8NUDFU77h9p5jhGpO6CQ5KhM/Ox89DNKpIlnfE/b2MdLqTmqHDTbs38/2DX3fOEn3/ps uI0Jb7HGtl5A0kreCPY7VHBhC063xJElLWKhfmZhgcNsTCvyDJu8dv5kqyPyuI/MIH2H XUvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oOhVOEPeEa/Oi65Klty6ghOI1gD7r0ukgKDT1u9dSOY=; b=oPknCDKskLboib/pVgDXFxyFVAUxM8C58nDCx3NZAnEgYr9ZrQ+ExCcX+ZLVh4hGsR s33cdWLk0Vj30I4mA9KNpvwdeHFtKXiwVB+XGCst4O5zUnijSmSN7VQzUNcr1VJ5dZw9 T9S0qRoVvom5OBgicU/AeEmjQ0T1WFFLyYAo82M/vNXZ3o+YeewkQ++SM8FGzdHzUpdE 3zKGY2qhL7qv/X5/yToBZeFDromn9EuGlzvNaMVU6sMUv+fa3HBN5h+NfXbPMh2BX77n KTbabrkVHw4OrqhC0Vb3hu2e67p7w472Gtv2Fb79ywMzudrH0LqNbe3oj5lQEf/ApC6f 8kug== X-Gm-Message-State: AOAM532PZGVheu9LCExnVtHddSnsZNwXXwcDJovO4ztGkBthLkqzKa3f UQWBADjAU0mMpHTnef8AmDdixg9Y7nx4/ev60QLooa8XnYw= X-Google-Smtp-Source: ABdhPJxMWkLG1PJIr5laWYTv9S3jcLZMEXABGQuQxvGrT98SqeRBT3Ko6IQI7HxbTxuIpBlPlyJ5Znbx95W0ZhfFjUM= X-Received: by 2002:a62:30c5:0:b029:31e:fa6d:1738 with SMTP id w188-20020a6230c50000b029031efa6d1738mr26388070pfw.55.1625816999666; Fri, 09 Jul 2021 00:49:59 -0700 (PDT) MIME-Version: 1.0 From: Glyn Normington Date: Fri, 9 Jul 2021 08:49:49 +0100 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000bc261205c6ac0463" Archived-At: Subject: [Jsonpath] Glyn away 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2021 07:50:04 -0000 --000000000000bc261205c6ac0463 Content-Type: text/plain; charset="UTF-8" I'll be away sailing until the 18th July. Who knows whether I'll receive emails, but please assume I won't. Regards, Glyn --000000000000bc261205c6ac0463 Content-Type: text/html; charset="UTF-8"
I'll be away sailing until the 18th July. Who knows whether I'll receive emails, but please assume I won't.

Regards,
Glyn
--000000000000bc261205c6ac0463-- From nobody Tue Jul 20 10:49:02 2021 Return-Path: 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 641643A2C48 for ; Tue, 20 Jul 2021 10:49:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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.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 bPs-6wMD6vpb for ; Tue, 20 Jul 2021 10:48:59 -0700 (PDT) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 B7A2F3A2C4B for ; Tue, 20 Jul 2021 10:48:58 -0700 (PDT) Received: by mail-lf1-x129.google.com with SMTP id m16so5302568lfg.13 for ; Tue, 20 Jul 2021 10:48:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=PRQlqXGgvGD7u4gCtVNWkYQYIrEz6Xqe4d9essSDhVQ=; b=b05mSET3Iv3D50dN85vjUyc+2kQ+I0tQ9Fjka9YHezh63ZmjUu6APn5oob24Kps2JN PVieJW0SHDD1FMuFIZOWu35Md4PYSdHGCd8lY/AWzVqu/tQ27p035AxFirxYd9fdF8aB q7Gwt7O3z0PDlC9+yIdg9HGkdLf00rS/4sgTx34czS+BFqDcjPRyPCGYj6sDQWjDqQBl GvulviQpRBtj4NkKwMLAhg/6q0kolnEBaNNTwWvA6Ahk2akULfiNu3JcD9OIkGcoHhdH eRrIuQimJy5W0S40zN/2YCuG7l0EQ8JlGnuB0KSVMiTZ+oLwd6Cv6lwfdFJnvnJcDNv5 j/MQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PRQlqXGgvGD7u4gCtVNWkYQYIrEz6Xqe4d9essSDhVQ=; b=WJa1v+GKpNbv5ZMP65H3CKsxmhEJJ0RUU2bloUCKcrG51d60//0GQZP5JjTDi8gnfm KSfJ0rxc7WQyAFXoPLb0NIdVxzSS98Nvj+f+AR3Y+RprGHhgX/sc7kj5NW5zeG9ByeQ9 qAg9zEFEDfUnsGTnQfg7cTXlV5s/boYpgpKf+hX8opWOUT++9HPgYlC4R9cVRGAoq6ej fjT6XyC9bJv1sND8nAF+EdUNBpw5ADETTtI3tDkE36OmFb826/Cv9maGR/QC1NXv67Ju PiB7KXZSNZnYANRCIlJmtL6UJRkDPJyxRA1WwQyW5I0xuQkpoR9gOM9hFT4q8BufjdMk gA4Q== X-Gm-Message-State: AOAM531IOiUEfdR44NB8Gks9Fx4tz/3ypp28zdoXQmRmWR+1HnHJ5lAM gVmXj2qk5p73WhZzFcVhNa/pFdWCQKDybQKAXJei3eizd3ihEg== X-Google-Smtp-Source: ABdhPJyXm3PLSR/jMdODUf/upqIYRw9SEq0NwsHHAjt6k+xGx4Gk2WxuSMXqHOcDeDSiygVQTLdNxBBg7GIyyNQzRMQ= X-Received: by 2002:a05:6512:68c:: with SMTP id t12mr6589282lfe.224.1626803334978; Tue, 20 Jul 2021 10:48:54 -0700 (PDT) MIME-Version: 1.0 From: Tim Bray Date: Tue, 20 Jul 2021 10:48:44 -0700 Message-ID: To: jsonpath@ietf.org, Francesca Palombini Content-Type: multipart/alternative; boundary="000000000000e6b35305c791aa81" Archived-At: Subject: [Jsonpath] JSONPath editorship 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2021 17:49:01 -0000 --000000000000e6b35305c791aa81 Content-Type: text/plain; charset="UTF-8" Marko has resigned the JSONPath co-editorship. The selection of editors is obvious because, de facto, all the editing has been done by Carsten, Glyn,and Stefan. So James and I have asked the three of them to serve as co-editors. Having three co-editors is a little unusual in the IETF, but experience so far suggests this will work out just fine. Thanks in advance to our co-editors! --000000000000e6b35305c791aa81 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Mar= ko has resigned the JSONPath co-editorship. The selection of editors=C2=A0i= s obvious because, de facto, all the editing has been done by Carsten, Glyn= ,and Stefan.=C2=A0 So James and I have asked the three of them to serve as = co-editors.=C2=A0 Having three co-editors is a little unusual in the IETF, = but experience so far suggests this will work out just fine.=C2=A0

Thanks in advance to our co-edito= rs!
--000000000000e6b35305c791aa81-- From nobody Tue Jul 20 10:51:16 2021 Return-Path: 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 B64D13A2C61 for ; Tue, 20 Jul 2021 10:51:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 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] 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 E_sKG1ZsSHnk for ; Tue, 20 Jul 2021 10:51:10 -0700 (PDT) Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 2A3A23A2C65 for ; Tue, 20 Jul 2021 10:51:05 -0700 (PDT) Received: by mail-lf1-x12a.google.com with SMTP id m16so5312247lfg.13 for ; Tue, 20 Jul 2021 10:51:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=xsMHNwEK+txJsLAocJNoSsuDNu49HU6y8esKco770ZY=; b=RdS6FW+H51hvrGgBzIqqQdp9FDVkILMiaOq8dUkCpYPC/xAzw5B0Q46HRcaqvNfS0B 3DtvaD3VIXBUR7GrDvA7VlXkcyZ1NPcIO+kgkL43GA4nzeWlBRz+npBuOz7m14uuqCQu Utvu0l+8mYBBgG2C5UafB/huDR+uivbB/qF3sZzJvStv0hIqsNnXARF1vuUpoOng6Ma/ 2jvUgUNgLVRRdwZyv2xx58jxEoWqnL6DVr5iX+hywsb4DmoeqTUsDttVgLzlBxtuFHsw jDFNJodYxms0emIS5c9Xrg1/KComdHnH9FL32awPuK8rfBtn0Fr/AJgkenboycRhTG9h lS/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xsMHNwEK+txJsLAocJNoSsuDNu49HU6y8esKco770ZY=; b=I8NREzpcrbQ+XZBlNKrAk4PErbgnxeX7vFqujiIFxg50IQtXkfAKDmnzgCi/XDdX3W XW6W9PDc7uFF/35J0fwnBmylY8Iw8qCFRG0+nsJb74IDTpOw4SKcU0wQS8xPDfcdlV1Y WKkyN0cRX3jd8EII6DL7QiYi2FD2nUdjgLzzRDbAs8z8B82CMUKDzDu7pWyKX8vih3UD kUWeN88fZsukwgLM2ief+WIeuSb7DgetoF4PJLsrBj9dGJ9txwDXcmcVwqZd66VFeAD4 Y9u4dM3hUd6F+9areMx9nHFy0DFBa+2v5ma0T8PU4crOuArIypB2qAOX3LNp1veWkQ22 H02A== X-Gm-Message-State: AOAM531+Uqezx+ZcJkKdFIYmQASWDJhm+AMuTIDwu2dGNFKLxYvibLHg PvwqIZH3kBiqkmlQFxHKtzR+Hb79NSRkSbnaAVh45ubgTfk/cA== X-Google-Smtp-Source: ABdhPJx9lsSrrP74IUG9wzE/7GtaH+5+jnJl00S8Esn+mtx51zhJgDP7fEQw4KIalN6MOaqmohMbhmLVAIt/UqPmurQ= X-Received: by 2002:ac2:43d4:: with SMTP id u20mr22625068lfl.451.1626803462194; Tue, 20 Jul 2021 10:51:02 -0700 (PDT) MIME-Version: 1.0 From: Tim Bray Date: Tue, 20 Jul 2021 10:50:51 -0700 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="0000000000007bdfdf05c791b29a" Archived-At: Subject: [Jsonpath] JSONPath meeting at IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2021 17:51:16 -0000 --0000000000007bdfdf05c791b29a Content-Type: text/plain; charset="UTF-8" This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that. We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again. This would be a good time for WG participants to suggest issues they think are near the front of the queue. Thanks in advance! --0000000000007bdfdf05c791b29a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thi= s is happening next Monday at 4PM Pacific time, which means in the middle o= f the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settlin= g issues at our meetings and interims so far, so I'm optimistic we can = succeed again.=C2=A0 This would be a good time for WG participants to sugge= st issues they think are near the front of the queue.

Thanks in advance!


--0000000000007bdfdf05c791b29a-- From nobody Fri Jul 23 07:14:02 2021 Return-Path: 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 8E0073A0A10 for ; Fri, 23 Jul 2021 07:14:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=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=gmail.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 Xi_MFcDJRRgu for ; Fri, 23 Jul 2021 07:13:56 -0700 (PDT) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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 84F6D3A0A0C for ; Fri, 23 Jul 2021 07:13:56 -0700 (PDT) Received: by mail-pj1-x1034.google.com with SMTP id q17-20020a17090a2e11b02901757deaf2c8so3995546pjd.0 for ; Fri, 23 Jul 2021 07:13:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hnm4Umh7hvt/3fGAC2T/nBb+ooImvzyuMAFLrivpTI4=; b=fF0yockd37rM7PfGHOlmREbuBUOYe59qu6Gw3/GYJr4YnCEUV96adtqicwVHMQoA8j Z4hVYISqedN8PmI75Q+72VZCp6zUG/QNSv3WQ951b/PQwoOTR/yAt6zwAcdkAjDVdQmk /Kr6UesNzAm1w9kx8WuQIUgQyYIRuC1SJ4zzcQhtMMt2oup1xCkhjrwRTxgxbDavXjMA /EtiF0ISFLr4EhNAI0FzZygBM9LKddBzWxu7PrX2VrjLbn/2k7LzrR/Em8C6FQGIE9jV l4NlbPa0p98iRIWv2LOKcYBh5lcUYOnoA5c5z0iltDojaI7pmcpZvv5ed3WITc8OoDlK 5ORg== 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=hnm4Umh7hvt/3fGAC2T/nBb+ooImvzyuMAFLrivpTI4=; b=f6xzl8pMQ3FPOJytO6jrqkYQXUge6HfunaYlZewp4wn8haJFo9w8xb4eelzixsmEHA S3KEgTVVuYmDRwJlmlMSdfoHHfNmsLaL7CpioHqlE7StIJmSd1zh2IZ5/d7GyGE8zJOg MiDRwfqUYoh6ZrD/tpr5/JePvB8nmHolbnDN7qrQfaT4HfvjdhCwlXxtNuQ6GKwaEGH2 zoopaexZy/dTbfZoq6Uz5w3C8Y1R4g7pSaShdZ3lvpezebfQbi682s0l0fekomTcCG2u 0VALTz6buELnGCBs+PH3o9Dd80bA4h714UqdigikyK8Vd7qqggVRdxz3RfP2MfDhLgDT 70aw== X-Gm-Message-State: AOAM532NfZa1J626YycdO+6eDjTayx7CafhMhnOtpccS4qNH117XkPOm 9TMhEKl3cynCWSu1lYUA2rItRTNHjDJCYc0tp1U= X-Google-Smtp-Source: ABdhPJzpqZpm24w+6POCJ2DsuC4MoFdJs+6uA3sli6uIU2P44srRd8Bckx+AXDv/UkGk6MzYEDRqSnC2K7OblSzxiQk= X-Received: by 2002:a62:30c5:0:b029:31e:fa6d:1738 with SMTP id w188-20020a6230c50000b029031efa6d1738mr4633352pfw.55.1627049635339; Fri, 23 Jul 2021 07:13:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Glyn Normington Date: Fri, 23 Jul 2021 15:13:44 +0100 Message-ID: To: Tim Bray Cc: jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Jsonpath] JSONPath meeting at IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2021 14:14:01 -0000 I'd like the meeting to decide https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103. It would be great if people could express their opinions in the issue beforehand to save time at the meeting and make it easier to gauge the consensus. I'd like to discuss next steps for regexps in filters in case that feature is stalling. Attempting to define a subset of an existing standard is laudable and good for interoperability, but I'm concerned that, compared to being more open-ended and allowing the use of any "reasonable" regexp implementation (with consequent reduction in interoperability for many regexps), this will increase the cost of implementing JSONPath and put implementers off. I'd like to chat round the following new issue too as I'm hopeful there will be a quick consensus: https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/110. On Tue, 20 Jul 2021 at 18:51, Tim Bray wrote: > > This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that. > > We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again. This would be a good time for WG participants to suggest issues they think are near the front of the queue. > > Thanks in advance! > > > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath From nobody Fri Jul 23 07:44:45 2021 Return-Path: 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 727F23A0CBE for ; Fri, 23 Jul 2021 07:44:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 t-rS_jIccGAP for ; Fri, 23 Jul 2021 07:44:42 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1CD53A0CBA for ; Fri, 23 Jul 2021 07:44:41 -0700 (PDT) Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GWXCT1lcsz2xNH; Fri, 23 Jul 2021 16:44:37 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: Date: Fri, 23 Jul 2021 16:44:36 +0200 Cc: Tim Bray , jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 648744276.865338-4027defd267ece368b6fa90b4278ee52 Content-Transfer-Encoding: quoted-printable Message-Id: <73E6D850-E63B-480C-B5C4-BC1F78E2FA16@tzi.org> References: To: Glyn Normington X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: [Jsonpath] Iregexp (Re: JSONPath meeting at IETF 111) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2021 14:44:45 -0000 On 2021-07-23, at 16:13, Glyn Normington = wrote: >=20 > I'd like to discuss next steps for regexps in filters in case that > feature is stalling. Attempting to define a subset of an existing > standard is laudable and good for interoperability, but I'm concerned > that, compared to being more open-ended and allowing the use of any > "reasonable" regexp implementation (with consequent reduction in > interoperability for many regexps), this will increase the cost of > implementing JSONPath and put implementers off. I think the iregexp approach can only work if we have running code for =E2=80=94 checking a supplied regexp against iregexp rules =E2=80=94 translating an iregexp into one of several popular platform = regexps So coming up with that code would be part of the development project for = me. That should help the implementers. Being somewhat (but not too much) different from the standard regexp = soup out there could actually help interoperability. A little pain at = the start, but portable expressions after that. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Jul 23 08:32:23 2021 Return-Path: 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 DBDB23A10B9 for ; Fri, 23 Jul 2021 08:32:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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=gmail.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 krpDuit0rG35 for ; Fri, 23 Jul 2021 08:32:19 -0700 (PDT) Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 453353A10B8 for ; Fri, 23 Jul 2021 08:32:19 -0700 (PDT) Received: by mail-pj1-x1036.google.com with SMTP id gv20-20020a17090b11d4b0290173b9578f1cso6569261pjb.0 for ; Fri, 23 Jul 2021 08:32:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=w3wPZRFYlaLaLmfomFekj+XlaOrWVNkUIMPDZ6AxQ8w=; b=QYA/9gAzmUrQJTu2wUkcOfZiUZWUWh5Txi4WlxQHFp7kOU+yAZDpBNjTTUTNw1dBs8 5EoCjjR5aB2ZCH9yJe8ZDdujiprJWse8lMQTuKw5a3IGFuv3a3v+gHZkPvaPAoZHp8fK 9xTVqcMFVaTX6tRNaK69IJgmMMxZElA/0+mRhiLixtMh27dJB8gLH6bAb/3Ril8YVYg1 1hK68b+WkNZ6J0Y+GKqSc3QWy5FPEqCXiqBYukk0CwG2nO5YbQnBgsBgKK/erGtDwdhE jumR2JIrzcifrjX+IKthmqLLF4dhl6ejS9JtLmwJMGEKXlxB/RvIi3pPL3LRqCbUK6q1 79eQ== 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; bh=w3wPZRFYlaLaLmfomFekj+XlaOrWVNkUIMPDZ6AxQ8w=; b=PZvxwbxFd23De69IbxguUE3r8ixWPPUEoU51l7nZ0WppDfpaOD4pJyW7no+EbM18D1 ++9jBrgTT5yRKnYXV66YTUJZPAeLA8WtaQnW/AF5BZaBuTIbMdnbuqbPp81f62LYLWk+ VoaZ54AVanYLn4dUGdHJb0nPwuMjHJIc+nCnq/Pdb/o6dXszh4pA1R6ysQPEeihaKbuo kzVK/KI877AUVQ2TFlF3FUCkkm3kF7san5uaI/SzNtRFIp6uUwEzbEK4bOpikeWjpiCq 0ZbWx8Rb3QdL+GM9EJPFp7JaqZyiIkW6s+9sThSrxflT6E2rqYXPv7QIUQOk7LXCSSG7 EthA== X-Gm-Message-State: AOAM533Zq3SNrnp5/wbmGJlUge5iDLSpsjlBYvBBDhQeaPPbrrJl6cqX NqDI1GdDpVHscjGRdTK4Zdi8KzTVZQ/zjTnwt2cdBx/Th20= X-Google-Smtp-Source: ABdhPJxc/0PyZg0UCHnNShxyUiZwcMQZ4ChqN01kjerLQzBLnRbRREqIITszEeC85H4HemEZKcXyVfgltP90VxX6QNI= X-Received: by 2002:a17:90a:e513:: with SMTP id t19mr5090870pjy.104.1627054337829; Fri, 23 Jul 2021 08:32:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Glyn Normington Date: Fri, 23 Jul 2021 16:32:06 +0100 Message-ID: To: jsonpath@ietf.org Content-Type: multipart/alternative; boundary="000000000000d62d1705c7cc1bf8" Archived-At: Subject: [Jsonpath] How to apply RFC 2119 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2021 15:32:21 -0000 --000000000000d62d1705c7cc1bf8 Content-Type: text/plain; charset="UTF-8" Carsten wrote (in issue 103, here ): > Except that I don't know what's "SHOULD" about that, I agree with these > partial ordering guidelines. > > If we want to introduce different compliance levels, that is fine, but it > SHOULD :-) not be coupled to using the term SHOULD vs. MUST. > "Full compliance requires..." > vs. "For conditional compliance, at least..." > As I said in the issue, I'm happy to go along with Carsten's language, but I'd like to discuss briefly why my interpretation of a couple of sections of RFC 2119 is wrong, so we can learn from my mistakes. 3. **SHOULD** This word, or the adjective "RECOMMENDED", mean that there > may exist valid reasons in particular circumstances to ignore a > particular item, but the full implications must be understood and > carefully weighed before choosing a different course. > Ignoring the above ordering requirements is valid although interoperability will be reduced. 6. Guidance in the use of these Imperatives > Imperatives of the type defined in this memo must be used with care > and sparingly. In particular, they MUST only be used where it is > actually required for interoperation or to limit behavior which has > potential for causing harm (e.g., limiting retransmisssions) > The above ordering requirements increase interoperation and reduce the harmful combinatorial explosions of certain tests. Regards, Glyn --000000000000d62d1705c7cc1bf8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Carsten wrote (in issue 103, here):

Except that I don'= t know what's "SHOULD" about that, I agree with these partial= ordering guidelines.

If we want to introduce different compliance le= vels, that is fine, but it SHOULD :-) not be coupled to using the term SHOU= LD vs. MUST.
"Full compliance requires..."
vs. "For conditional compliance, at least..."

As = I said in the issue, I'm happy to go along with Carsten's language,= but I'd like to discuss briefly why my interpretation of a couple of s= ections of RFC 2119 is wrong, so we can learn from my mistakes.

3. **SHOULD** =C2=A0 This word, or the= adjective "RECOMMENDED", mean that there
=C2=A0 =C2=A0may exi= st valid reasons in particular circumstances to ignore a
=C2=A0 =C2=A0pa= rticular item, but the full implications must be understood and
=C2=A0 = =C2=A0carefully weighed before choosing a different course.

Ignoring the above ordering requirements is valid although interoperab= ility will be reduced.

6. Guidance in the use of these Imperatives
=C2=A0=C2=A0 Imperative= s of the type defined in this memo must be used with care
=C2=A0 =C2=A0a= nd sparingly.=C2=A0 In particular, they MUST only be used where it is
= =C2=A0 =C2=A0actually required for interoperation or to limit behavior whic= h has
=C2=A0 =C2=A0potential for causing harm (e.g., limiting retransmis= ssions)

The above ordering requirements increase intero= peration and reduce the harmful combinatorial explosions of certain tests.<= /div>

Regard= s,
Glyn
--000000000000d62d1705c7cc1bf8-- From nobody Fri Jul 23 14:51:48 2021 Return-Path: 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 C46143A1C61 for ; Fri, 23 Jul 2021 14:51:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=yahoo.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 LNtrogr3H5Vw for ; Fri, 23 Jul 2021 14:51:42 -0700 (PDT) Received: from sonic305-3.consmr.mail.bf2.yahoo.com (sonic305-3.consmr.mail.bf2.yahoo.com [74.6.133.42]) (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 210933A1C5F for ; Fri, 23 Jul 2021 14:51:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1627077100; bh=4y8JIZt0jdsKpC5kOAOWkTBMH3LhPrTg+oObr6IGVA4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=lUSw1HumBnfwYtjI+0yV74W9wWaDbUCPhgRXdB6Ki+9fvhSLvAkshD11fAzcOOe7IhXCyDfIYfMUPskvoOGMMHetp2s/WmYuwEfvaGRVxPAoo0p4SMapJDwTPWop39pCRKZleeylfjHx43EPQfh3labP7mD3PT/t2cM/OpPl0Cw4gsFGqa3GN6CTQsSAMDFOYYv7h8c5mBBNRDA32nE30O+wgiCUfNx1IEOpzUafkM9xZAyZcJoVTKkOTsyNL7HPvgRawBxZwo4CazzVC9cOzmolBMzbstLWEFYkVO04WEb9cAXnHJYg+1ioxQNxQ6z4HYdkomOojDiSABep7+56aw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1627077100; bh=hYHHEzNEkZwoHmUN81J891Aj1pk/HmoX0gp706XUub8=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=nDsc9l/Jwo6Voq5NRG5uIhYs6Q76eSWIUWah+syy5RcmQAfMZft6vqH4an1IXDH+t0uzSnmrz60uivFiznYG+AXkhNjEddnNSGWgyGQiQR0GC9quOHv0TdhRrtSeHzkglSvxWOM8LSbHn+CmItQS53RYyRO3y72KP8a8gNyvfhsvnGZjDY3nznu5LbZfekFlRYycRYoTIL9OBj/6Dc8XlbdpT3yAhEHIjXiyL/Ob//7VKE+96d7JdKti2G42ssvTONQhhdcorzvWvyowV6+hSFXeAcP9KJw6pnFI2elYm2KrWTqRhmH5TyLLl1UtFjpU9IGK5SLci/ibDAw14g5VeA== X-YMail-OSG: mecwls0VM1npuX6BozwsrL4SqMcBaG2ayDKfynEKzm8OBRsTghLHDKTe0tKe7cz 24CpStTaEP2J6FK4VLGkpIeEMyPSmcReDtY4ZaYOSu3xLg_VTr226tzQ3c86r7LXzc6WrhbCiL6N USypanPuiAtfzTzl93unzMJR8vcVUNF9audkS9W1uRdpyYT7NF65h_PZ0Fm9.c6WDDspKw_sTZmz WZbXgP1vw3dhM8Zw2o1Iw4qOqaYHkJAtRLSIPReL2iZzBDNqUzfF9wojY5qjV9s8H.Y25r4W_cBg GplT4vRHZbO.juXrYJzC9Q3DT9sJjfvy3UJ3snexbclVcwto0Br15fm0dyefiM5NMK73DmKu4fG5 VMaUmujw1hiMaaGTZuPh5lQeD5krZM98DuvkUON.oHWAOIgPVp_BhVYyHppdjdoEOxQirDvpnfWv SOzR_zpzKT5AiIz.ZEbsPN0HEVBtItAd6RSHMdlEpu.j96KYGwwFoPjWwDWFZs7hOZajGptqqq3C __Vel2AqhsazUfnkMR8xFhuip6Lvf6rqfTHAeVB0WouxlPd4SEET.vru6.oXScLxD.3i4YEFcZOl VZ4Fv_D.ZDIKXjbhpO_KGKYe.491BnKkHwytmN_sD7.iBVo6_Qvv7EIZKnnyscHv9us31G9Ts.hf 7IeWbBP4Zq86dIQbTDM_3RyOEGL1TV6JxF1mUM5RhnLg6699rskv6Krk8P2t5cVaoE_._hZVbB8l Z8pOx7IAZE.REhQDipAVTOIEZPSIChh.krtD0YReK5RFG1OEyvZ4xhXEkDYB7b7ioeXnJ5D.Wj1p 9d9rSbZlupuUop4BnVvPnIxedLSWk0uDxC0cV39iBVE7nevObNUYVdNKP.3Ac1D2g.S7f1zMT_wB f_cbk_eotP6gfdxuovkgulJcG9KdpO_sHRQsCniLHm1dlS_1WJIFsjge6t1WXLcaCmB82.MvfNiq G4G6XIisJoleClOMgACQ.IDpo.q2cs979V90qRBUoPGc6OVpCZO.caghkpZiX10DwDbHyS.V_jl7 Z6dHuchXpKDkvh_ArYocB6x0SVJJhtnlUU_puMcUEmSpLyt_AVmSsVGmHX6EAwuqAi8KjtzRYs4L S6rVVU8A7byhaMlrhN5kd..oMcvjgGnAmhW7yl02_DNXoJKnjYwfx7uTzT6ue4pbvfOJaD9m96U8 mLALQvy7pnDf_XFKExkEnxi6bsyYZd3Q1rsLo9khEaEyzw0IaKKTLVyN37n.V08wvejs5.u89qOD 7haF.26Ojdyfjx8E865NoucfBUgQbqJ7aEXH_vykk3DXTu6G5Gg1YTtdKbsSbCd0hLjL6RI1nVrd X5OR7p.uykQ8yEAKHMSUJ3XnQzongcXU4sgDjFB2I0jmmuDpyec7D0cSmvlTTobXTR8P2lEVae2. ivRNn6AJKnoQqmtPoMpzDZw1rdz0.IoO8IJbDZ2UUslTBhHNp.K7.iqTFXthuQByISYkUwzyG0Jb AdCd8xoXNzRLUqwnZiVzWI93HKLXdoOu2A7RQIlahCKiE6T3BMFGAyhWU3YqYil1zKqGpPxolOCq 3BKvTjDSNRgmtppaTNNNXm8YfYxuRzOEJ.LSffxLZnhoe6wcNjc7v8WsXoAxKTkJ0wcBUW_udShn 2wCJ_9C2HcVwvxTXREUaDm2hnIJWy1Cd6buOm0yWRvuoE.OlDa558HgFhN2_ivjLXItbnTjPc.6j tWjjOneqtAgpRAGgbzbxH1AKZeQy1lmy49qwodJsB38fkIYoYrjovBADXkXNTVuuOgHUf.zwD9l9 bTdNmLBuH0hA_GsMQzrXBIfFPnCG8fcJfolmBWC0VicdBBAen1pcwIlkQwfuKb3xboLWkwxBWIJJ xEQJsRvBhXy6xLBEIFgYKqusS6qi7umVI0RxERTGGv_cnNLrjYxjmFiiGMn6aGX5ieVCyuzWYo7T 8E3vgIo6EjemP1MYUZRRInl4ryVGYSWEmZoqKBV6.E1rXsyuIuDLQ7dTmt9YY8hFW53YEDIs_SiT I2e0cH0fmC8gqp1R.HYSEZ1StwTBM.5WifppaJ8ZlYfAULa8ugWTmt6HmmefmjETgJqfSI_LakGw pYcizTzTrOWuobgXJqbqfKVcdxsbyIY_Q9hSVe3ChFWjXKfNZVnzjdIfnDeexAejAk.3MpNG6j4j 6uAlzfS8Jm3xBxTZHX5.sNJigRPNnnNNEzfcPT7fq9tHjlx6g42bCFrBXY38a7GEjAiQ4VRndQwb eMFAiz_AoOo0VeoB0q7hJQIDMD9x75KWGQmMPI6JLAmtFdjeerdt1GBnoobLwi0m1ibaGE0lf0RY .xthNpB29SpW6FwQKf_z4eqZN_K3mqAfxyEsiYrrE_B_nLpceqVnJ.gzUTEOdhWVGl2IxEPWv0x4 - X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.bf2.yahoo.com with HTTP; Fri, 23 Jul 2021 21:51:40 +0000 Date: Fri, 23 Jul 2021 21:51:33 +0000 (UTC) From: Greg Dennis Reply-To: Greg Dennis To: cabo@tzi.org, Glyn Normington Cc: jsonpath@ietf.org, Tim Bray Message-ID: <423087841.455046.1627077093902@mail.yahoo.com> In-Reply-To: <73E6D850-E63B-480C-B5C4-BC1F78E2FA16@tzi.org> References: <73E6D850-E63B-480C-B5C4-BC1F78E2FA16@tzi.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_455045_1076401170.1627077093900" X-Mailer: WebService/1.1.18736 YahooMailAndroidMobile Archived-At: Subject: Re: [Jsonpath] Iregexp (Re: JSONPath meeting at IETF 111) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2021 21:51:47 -0000 ------=_Part_455045_1076401170.1627077093900 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I would expect prescribed RegEx support would be as near to an intersection= of various implementations so as to only prescribe common ground. Greg =20 =20 On Sat, 24 Jul 2021 at 2:44 am, Carsten Bormann wrote: On= 2021-07-23, at 16:13, Glyn Normington wro= te: >=20 > I'd like to discuss next steps for regexps in filters in case that > feature is stalling. Attempting to define a subset of an existing > standard is laudable and good for interoperability, but I'm concerned > that, compared to being more open-ended and allowing the use of any > "reasonable" regexp implementation (with consequent reduction in > interoperability for many regexps), this will increase the cost of > implementing JSONPath and put implementers off. I think the iregexp approach can only work if we have running code for =E2=80=94 checking a supplied regexp against iregexp rules =E2=80=94 translating an iregexp into one of several popular platform regex= ps So coming up with that code would be part of the development project for me= .=C2=A0 That should help the implementers. Being somewhat (but not too much) different from the standard regexp soup o= ut there could actually help interoperability.=C2=A0 A little pain at the s= tart, but portable expressions after that. Gr=C3=BC=C3=9Fe, Carsten --=20 Jsonpath mailing list Jsonpath@ietf.org https://www.ietf.org/mailman/listinfo/jsonpath =20 ------=_Part_455045_1076401170.1627077093900 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I would expect prescribed RegEx support would be as near to an intersection= of various implementations so as to only prescribe common ground.

Greg

On Sat, 24 Jul 20= 21 at 2:44 am, Carsten Bormann
<cabo@tzi.org> wrote:
=
On 2021-07-23, at 16:13, Glyn Normington <glyn.normington.work@gmail.com> wr= ote:
>
> I'd like to discuss nex= t steps for regexps in filters in case that
> feature = is stalling. Attempting to define a subset of an existing
> standard is laudable and good for interoperability, but I'm concerned=
> that, compared to being more open-ended and allowin= g the use of any
> "reasonable" regexp implementation = (with consequent reduction in
> interoperability for m= any regexps), this will increase the cost of
> impleme= nting JSONPath and put implementers off.

I think the iregexp approach can only work if we have running code for
=E2=80=94 checking a supplied regexp ag= ainst iregexp rules
=E2=80=94 translating an iregexp into= one of several popular platform regexps

So coming up with that code would be part of the development project for= me.  That should help the implementers.

Being somewhat (but not too much) different from the standard reg= exp soup out there could actually help interoperability.  A little pai= n at the start, but portable expressions after that.

Gr=C3=BC=C3=9Fe, Carsten
------=_Part_455045_1076401170.1627077093900-- From nobody Fri Jul 23 15:21:34 2021 Return-Path: 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 200043A1F32 for ; Fri, 23 Jul 2021 15:21:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.498 X-Spam-Level: X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no 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 KBTWNW2Sx5xh for ; Fri, 23 Jul 2021 15:21:29 -0700 (PDT) Received: from p3plwbeout03-04.prod.phx3.secureserver.net (p3plsmtp03-04-2.prod.phx3.secureserver.net [72.167.218.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F09973A1F31 for ; Fri, 23 Jul 2021 15:21:28 -0700 (PDT) Received: from mailex.mailcore.me ([94.136.40.145]) by :WBEOUT: with ESMTP id 73Xrm72Z8jzMg73Xrmt8C6; Fri, 23 Jul 2021 15:21:28 -0700 X-CMAE-Analysis: v=2.4 cv=bu2JuGWi c=1 sm=1 tr=0 ts=60fb40e8 a=7e6w4QD8YWtpVJ/7+iiidw==:117 a=np+Hvx21kC4Q4qxhmORf6Q==:17 a=iO2Z4BJ_FnUA:10 a=kj9zAlcOel0A:10 a=e_q4qTt1xDgA:10 a=48vgC7mUAAAA:8 a=2su83EYyPDp1xhCOoMAA:9 a=CjuIK1q_8ugA:10 a=w1C3t2QeGrPiZgrLijVG:22 X-SECURESERVER-ACCT: mike@saxonica.com X-SID: 73Xrm72Z8jzMg Received: from cpc160115-rdng30-2-0-cust150.15-3.cable.virginm.net ([86.19.35.151] helo=[192.168.0.27]) by smtp02.mailcore.me with esmtpa (Exim 4.94.2) (envelope-from ) id 1m73Xq-000B30-6p; Fri, 23 Jul 2021 23:21:26 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) From: Michael Kay In-Reply-To: <423087841.455046.1627077093902@mail.yahoo.com> Date: Fri, 23 Jul 2021 23:21:25 +0100 Cc: Carsten Bormann , Glyn Normington , jsonpath@ietf.org, Tim Bray Content-Transfer-Encoding: quoted-printable Message-Id: <3A622683-467F-4F09-BD04-26B030C6D33B@saxonica.com> References: <73E6D850-E63B-480C-B5C4-BC1F78E2FA16@tzi.org> <423087841.455046.1627077093902@mail.yahoo.com> To: Greg Dennis X-Mailer: Apple Mail (2.3654.60.0.2.21) X-Mailcore-Auth: 439400257 X-Mailcore-Domain: 1881035 X-123-reg-Authenticated: mike@saxonica.com X-Originating-IP: 86.19.35.151 X-CMAE-Envelope: MS4xfCgiOs8ggFNpyep4VSMmV2/anNFHFWH4vnGOxGY6P+qILZGsV1fwmt8NV2WZceEKue04kHm+lzhrJIECV57Qx1Fmrr3iWV5Vm8Iik9qR9JNRvNFsxe6d kT5d9TlG4YSnspiSBg5Y/0j/UgaVZ8mKFbogHBPYFFq0sHmDMiQ/ra+LwJXG3ol1+jEovJvKTSVKpw== Archived-At: Subject: Re: [Jsonpath] Iregexp (Re: JSONPath meeting at IETF 111) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2021 22:21:33 -0000 > On 23 Jul 2021, at 22:51, Greg Dennis = wrote: >=20 > I would expect prescribed RegEx support would be as near to an = intersection of various implementations so as to only prescribe common = ground. >=20 That's roughly what XSD tried to do; XPath 2.0 and then 3.1 followed in = its footsteps, with a modicum of success. (Some vendors, notably = Microsoft, took the easy route and implemented their own regex dialect = ignoring the standard.) So since the design objectives are the same, one = approach would be to use the XPath 3.1 regex dialect and use it = unchanged. It's not perfect but at least it's rather more thoroughly = specified than most (regex specifications on the whole are notorious for = their lack of precision). A big part of the problem here is that most regex dialects predate = Unicode, and include all kinds of stuff that isn't very pretty in a = Unicode world. The XSD/XPath dialect tried to fix that. Implementing this dialect by translation to a different regex engine is = possible but not easy. James Clark wrote and published a translator from = XSD regexes to JDK regexes - that was before Java changed so that a = surrogate pair is one character rather than two. Probably the hardest = thing to get right with that kind of implementation is the XPath rule = for case-independent matching (the "i" flag) which is based on Unicode = character properties. Doing the Unicode blocks and categories is fairly = straightforward to implement but potentially very inefficient. In Saxon = I used a translation approach initially, but eventually decided to = implement my own regex engine (by modifying an open-source one). = Contrariwise, for Saxon-JS we're translating to JavaScript regular = expressions, somewhat imperfectly. Michael Kay Saxonica From nobody Fri Jul 23 15:44:57 2021 Return-Path: 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 65E783A2010 for ; Fri, 23 Jul 2021 15:44:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 I70okYX_p2TT for ; Fri, 23 Jul 2021 15:44:50 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98D643A200F for ; Fri, 23 Jul 2021 15:44:50 -0700 (PDT) Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GWksV128Bz2xMh; Sat, 24 Jul 2021 00:44:46 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: <3A622683-467F-4F09-BD04-26B030C6D33B@saxonica.com> Date: Sat, 24 Jul 2021 00:44:45 +0200 Cc: Greg Dennis , Glyn Normington , jsonpath@ietf.org, Tim Bray X-Mao-Original-Outgoing-Id: 648773085.373924-d5dc31c5b99fa53f3e9efac938493505 Content-Transfer-Encoding: quoted-printable Message-Id: References: <73E6D850-E63B-480C-B5C4-BC1F78E2FA16@tzi.org> <423087841.455046.1627077093902@mail.yahoo.com> <3A622683-467F-4F09-BD04-26B030C6D33B@saxonica.com> To: Michael Kay X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] Iregexp (Re: JSONPath meeting at IETF 111) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jul 2021 22:44:55 -0000 On 2021-07-24, at 00:21, Michael Kay wrote: >=20 > That's roughly what XSD tried to do Yeah, except they have this character class subtraction that nobody else = has, so essentially you have to profile this out. Not sure why we would want to go beyond XSD into XPath land if we want = to keep this simple. (We need matching, not parsing regexps.) Gr=C3=BC=C3=9Fe, Carsten From nobody Sat Jul 24 08:18:54 2021 Return-Path: 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 52CE83A3ECD for ; Sat, 24 Jul 2021 08:18:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 kQlYWSkvIXFB for ; Sat, 24 Jul 2021 08:18:49 -0700 (PDT) Received: from gabriel-smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED2B53A0C9E for ; Sat, 24 Jul 2021 08:18:48 -0700 (PDT) Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GX8wP5qzfz2xKy; Sat, 24 Jul 2021 17:18:45 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) From: Carsten Bormann In-Reply-To: Date: Sat, 24 Jul 2021 17:18:45 +0200 Cc: jsonpath@ietf.org X-Mao-Original-Outgoing-Id: 648832725.421192-3dfec20736acd1012e8bc06afa168d67 Content-Transfer-Encoding: quoted-printable Message-Id: <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> References: To: Tim Bray X-Mailer: Apple Mail (2.3608.120.23.2.7) Archived-At: Subject: Re: [Jsonpath] JSONPath meeting at IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jul 2021 15:18:53 -0000 On 2021-07-20, at 19:50, Tim Bray wrote: >=20 > This is happening next Monday at 4PM Pacific time, which means in the = middle of the night for the bulk of our EuroPeople; sorry about that. Apparently I didn=E2=80=99t pay enough attention, since I only just = noticed that I have a conflict with IOTOPS in that slot. I think we need to have a slightly more frequent interim cadence. Gr=C3=BC=C3=9Fe, Carsten From nobody Mon Jul 26 08:50:26 2021 Return-Path: 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 4BB5C3A1B0B for ; Mon, 26 Jul 2021 08:50:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.895 X-Spam-Level: X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no 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 lkimE6zFzVlC for ; Mon, 26 Jul 2021 08:50:22 -0700 (PDT) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC7CD3A1B7C for ; Mon, 26 Jul 2021 08:49:59 -0700 (PDT) Received: from [192.168.178.20] ([88.130.51.150]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1My6xz-1l92zc2M6Z-00zWUv; Mon, 26 Jul 2021 17:49:55 +0200 To: Tim Bray , jsonpath@ietf.org References: From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net> Date: Mon, 26 Jul 2021 17:49:54 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------9AFA8A7E6DB2F0EC5BD89AC4" X-Provags-ID: V03:K1:m5ajplQNn9v0kyVBUsgVBBVSAdLMqvz4DCMwrmEMW0IgFiy4pJc xwmEfLVHGCugz3giZl2RTIwRNVIU/oeqHVSoUcpogJwVXyBUEnjY1ctbwbO22ZqBaWF8MJC Y3maE0c8IdFVs+gfE1eelXMegi3mWD6iXBvZjqi8SpJpH45h4xfuw9znzuikAw1Vy4/LKrg 82LPjReLFbe6Epw30lOeg== X-UI-Out-Filterresults: notjunk:1;V03:K0:ST/mYakvw3k=:hDzNrYO7VNOjdU89jFMjc/ KhwBwTzy5k1OjmU8XQzxY7O+8N+KDdhApm2QzNSMKiWbOeE5xlVnhO/eczqHhNxFpx9fK1juU GTe0zTt08I3sDKg4zIXnK8w1ubTbZLjM6Vfj3noh8VL+YQgnW54+Vzn221JC3MSinuCchfu3U iKFbP7McrPz+2XwKhcOwhAi1IuHoilzNrQD/RfXb23nlE3jotUEGRaOJPJLuIb3BWcfhl6zy2 U4qJYc+ZlTdyKdpzYiSHX5HZjzRFvk/glCgifL9A2fFzIoGPtJvq/9ACEboE9+ULzT0SL36qS sEVCAX/UzWTVRdEjJWYaMeVIpPEfzc7v7wAfrT0wqG2Ayd5yTGveg+zLVuoMLB0dvHjqO27nP nq34p5N2918cd5/8rVxDxQmfxW3EWaHBJNIcJCit4mS+H+M8BaWEXFpHMdCXnW/iJV2nOdjrg 6AKLvsbULf62jGUqeN9QWg0vHeMFbE5O51uY1uV2NSI9+6sKuXL0ZQL2m/zuGfQOOtS5T+VZT 3A5MkLkWh/CgTobpBipfyS89krB3SwzT3IQQcXWQQH6b79dEEH2/ziUHxc5sDpeSntZvtDHyh BAMyiDIhmwIbKpyo+G1tIpQ9aQkRAYe+jmbcFOk5lUsNT9tBkAXfaMgwuvp1/gJmcVaGZ0tcx LHM0azGNIxpO5vWQ2L2u6tjogU+ISkDUstO5ux6rHNYoWjl6dZKeOPdRwyiKyX8rY0V9LuDLx bmsZNp5aCF7FGnzlYCRt5FrZswskZt1ltdaJYUavbMhhTQyQNLYGL3YYagnorNX/MoI2xIO+u Wp1RqO7gOdih+1CJdoBnUVI9AWv0ASXbb92ET1m+BgMwgUDiHR+yIJc15F7dTk7TWxveTaJ Archived-At: Subject: Re: [Jsonpath] JSONPath meeting at IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2021 15:50:25 -0000 This is a multi-part message in MIME format. --------------9AFA8A7E6DB2F0EC5BD89AC4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ? -- sg Am 20.07.2021 um 19:50 schrieb Tim Bray: > This is happening next Monday at 4PM Pacific time, which means in the > middle of the night for the bulk of our EuroPeople; sorry about that. > > We have a good track record of settling issues at our meetings and > interims so far, so I'm optimistic we can succeed again.  This would > be a good time for WG participants to suggest issues they think are > near the front of the queue. > > Thanks in advance! > > --------------9AFA8A7E6DB2F0EC5BD89AC4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
--
sg


Am 20.07.2021 um 19:50 schrieb Tim Bray:
This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.

Thanks in advance!



--------------9AFA8A7E6DB2F0EC5BD89AC4-- From nobody Mon Jul 26 09:02:10 2021 Return-Path: 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 6F2813A1B8D for ; Mon, 26 Jul 2021 09:02:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=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=gmail.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 jp2vJojd6bUE for ; Mon, 26 Jul 2021 09:02:04 -0700 (PDT) Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 0E6DF3A1B8A for ; Mon, 26 Jul 2021 09:02:03 -0700 (PDT) Received: by mail-pl1-x62a.google.com with SMTP id e21so7667302pla.5 for ; Mon, 26 Jul 2021 09:02:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=n4c5P4LZ9Jzr/Itn/fnbd4iKZ39wByBlmGxDoBW/CY8=; b=TXNBMNQh4hKpNItxDMoDeIHdvJ7Nfrd+Z5tZZU9VSa9ZWizti4UF3rTeArnQwyMVUJ 1UOu2Is9oevFfWwoPzajbuawYRmR9Rv0kAM4p8sHzSK2e9sX3mMVVTn3oddE0+2Ie7So WiBZnpJPwDefS04WHmX/5miHXn8OSvDtRKwBlgnxbjuyz0WVyAnpB/+TDACQPIFFXw46 zT7m/6mMy/9QB4dtvIQyxCUSJ7rXPGMuUjG89/Axh/Iz1714z1f0geaZq/lyJ8331RHr NaCoSjdchzYHDkS6fc18E9Vzo2bFz7sKAFju6HJWONMmzM9KSq7ZL3Q5TgUW/oDBqJVF a9Bw== 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:content-transfer-encoding; bh=n4c5P4LZ9Jzr/Itn/fnbd4iKZ39wByBlmGxDoBW/CY8=; b=CsYa5VD8Z2q3ttq4JXI8emha/6tSPHlDSzPUXsRs85TpdJ/eHzn76aww3MrcEaflN5 kjaeeLoCjxrjXX2xw26YFV0u0MFdiKHyUDL47IVm9tTQsNsUU5k4HkgT8GuCHj5+7W+7 Kmb8zfZ1ojRe+O3Lg0JQCrxVfmuWfqd3ayZJ79dA4yaqGevHC7D50NIZE4wl1tfywm5Y iACtK2ADl+og/hamFfMNqa7x3g3Ye/mv90J4feZ8ibBHhjVpV8Wpw0e43hMGVDAnj0Cz 0i/f30zn6gA+NkbUYFS2mYlqKRtUqKvrND5nO2XQHLIc9p180ZxKU2YxiDJvKGgmnMsj m2Ew== X-Gm-Message-State: AOAM531ZJC9CKapia28nK5HxtB4RrX4ALpo/muSzd/gWLlC7cuCrCCpZ JO5NLiNtl7OnHi+h6DBaIdAVAxyUxD2nW7KVDk4= X-Google-Smtp-Source: ABdhPJyyPagaPQBdjlp/in3W5+9gzgdfqeL/cjo7v52PzWg513Kps840643wPpvMtBnuXSlQ8JTVpSTUaCm/uVm/20A= X-Received: by 2002:a62:30c5:0:b029:31e:fa6d:1738 with SMTP id w188-20020a6230c50000b029031efa6d1738mr18352477pfw.55.1627315323245; Mon, 26 Jul 2021 09:02:03 -0700 (PDT) MIME-Version: 1.0 References: <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net> In-Reply-To: <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net> From: Glyn Normington Date: Mon, 26 Jul 2021 17:01:52 +0100 Message-ID: To: =?UTF-8?Q?Stefan_G=C3=B6ssner?= Cc: Tim Bray , jsonpath@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Jsonpath] JSONPath meeting at IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2021 16:02:09 -0000 Hi Stefan Tonight's meeting is on MeetEcho as part of IETF 111 which requires you to register (see https://www.ietf.org/how/meetings/111/). Once you've registered, click this link to access meetecho: https://meetings.conf.meetecho.com/ietf111/?group=3Djsonpath&short=3D&item= =3D1 Hope you can make it! Regards, Glyn On Mon, 26 Jul 2021 at 16:50, Stefan G=C3=B6ssner wro= te: > > How will it be possible to attend the meeting tonight ... technically ? = WebEx or something ? > -- > sg > > > Am 20.07.2021 um 19:50 schrieb Tim Bray: > > This is happening next Monday at 4PM Pacific time, which means in the mid= dle of the night for the bulk of our EuroPeople; sorry about that. > > We have a good track record of settling issues at our meetings and interi= ms so far, so I'm optimistic we can succeed again. This would be a good ti= me for WG participants to suggest issues they think are near the front of t= he queue. > > Thanks in advance! > > > > -- > Jsonpath mailing list > Jsonpath@ietf.org > https://www.ietf.org/mailman/listinfo/jsonpath From nobody Mon Jul 26 09:04:21 2021 Return-Path: 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 F26833A1B9B for ; Mon, 26 Jul 2021 09:04:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.895 X-Spam-Level: X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 yTOspivAl-ek for ; Mon, 26 Jul 2021 09:04:15 -0700 (PDT) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9AE53A1B98 for ; Mon, 26 Jul 2021 09:04:13 -0700 (PDT) Received: from [192.168.178.20] ([88.130.51.150]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1N5FxN-1l7S4V38ir-0119N2; Mon, 26 Jul 2021 18:04:10 +0200 To: Glyn Normington Cc: Tim Bray , jsonpath@ietf.org References: <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net> From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= Message-ID: Date: Mon, 26 Jul 2021 18:04:10 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------15E0899352537929C9BA0401" X-Provags-ID: V03:K1:ZXdR2qUAjKOI+pgE13E3w/EZ74xRXGgCYzopoOpWYE88ara+woe 9ew4iVSfnxAEqBVajOXR3Z+BlPvX7wUlDTgP6ptDQmBFp0ZcK2MD+0pFZEsxYK8LhK2daOT gdPyXzkBT94sFLTqR8dujt5qYV4+xegou1M982EEvbxAH9tRufDKU/ZWo7pAfHToa/LADa2 LQbSpTyXjKKRukpDznm4A== X-UI-Out-Filterresults: notjunk:1;V03:K0:y5ykPHAL3Lo=:eoJTLkkJQvj+uEQNHYtQ5C Bt6B4T1rJ7o+QRMkCyvb/VHPWcMAKpKUOSbSBpkbLJUCN6GHCitZZAEpuxrwYSOXmRe0gho4E ueqTFZ+GEh3ZnaId7E4RNYhJCS6NUI8GS4QqFrdkisDahLSxvY0mTXkZ2yv+IpNB1GqkFcfYy WPKt2TWWhA3jJyH3UFA2A+WsiN+kxRQS153W6r0FmA5RN53aPTrsgrAqAxMObHF5ZOQKYa9yK WyTNS7eIow2aU1u+SCcQ8ZtlqfUPNeGNrdwBoEFY2Lsjjq2qtDVek7cuvOu/v4paYtyZNGvTs BpaMzS1IpecXYc2CXmA8csoGVrFQhnIH/NOVruhA/kmY0OtwR11g5ke+DQGhtEkWBgJMg0EQ9 P06lIUsOo2DsoiKd/tAI0/wVXjNS4ZVUu9vAFViQ69UAr+/7Rca0iS+CDHb4EPYPtI2SPYGL5 kykbCWhprfa6FDwfbVR+qVfqV7MMbJ0NNnk4Hhx7g01CC4dSwmwCxyBD6oPQX6C8hj20srFxr p5hRVSdRHr1zFlhFdsVfILxsRmFCiV9qcuJJLlUkPP8tSj0q3Zj3G7r6YzB2Kq2/MnKgGNDIV T8Zjpz4O3c6wfyKto27Xnfe3l0HmBU6HtDzfxjoj+dIAtfaZwveCOWtsYC5aX3CjrTNnIXfBf vPe0PG8G4Xrledb68dGoWyOE0U7+ZS5mIMNYLO9IIJ2MtqAK3H1fr6/RlVVE8yE6ILU2NWw3l y0/RQHxFmmJ6xv+tRYqoCj43YTFZaADgOYsdoc9B6VSD9MDvhluBPj0+j/77MTNrq7dQMVCgZ deRtwRDcMCcihKvNOjclR4t8dVkm6jxYFzfcwiDpCVMWny5bdSPQ7s63dvV9qM05o/5TaDF Archived-At: Subject: Re: [Jsonpath] JSONPath meeting at IETF 111 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2021 16:04:20 -0000 This is a multi-part message in MIME format. --------------15E0899352537929C9BA0401 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit thanks ... I'll try ... -- stefan Am 26.07.2021 um 18:01 schrieb Glyn Normington: > Hi Stefan > > Tonight's meeting is on MeetEcho as part of IETF 111 which requires > you to register (see https://www.ietf.org/how/meetings/111/). > > Once you've registered, click this link to access meetecho: > https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1 > > Hope you can make it! > > Regards, > Glyn > > On Mon, 26 Jul 2021 at 16:50, Stefan Gössner wrote: >> How will it be possible to attend the meeting tonight ... technically ? WebEx or something ? >> -- >> sg >> >> >> Am 20.07.2021 um 19:50 schrieb Tim Bray: >> >> This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that. >> >> We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again. This would be a good time for WG participants to suggest issues they think are near the front of the queue. >> >> Thanks in advance! >> >> >> >> -- >> Jsonpath mailing list >> Jsonpath@ietf.org >> https://www.ietf.org/mailman/listinfo/jsonpath --------------15E0899352537929C9BA0401 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit thanks ... I'll try ...
--
stefan


Am 26.07.2021 um 18:01 schrieb Glyn Normington:
Hi Stefan

Tonight's meeting is on MeetEcho as part of IETF 111 which requires
you to register (see https://www.ietf.org/how/meetings/111/).

Once you've registered, click this link to access meetecho:
https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1

Hope you can make it!

Regards,
Glyn

On Mon, 26 Jul 2021 at 16:50, Stefan Gössner <stefan@goessner.net> wrote:

How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
--
sg


Am 20.07.2021 um 19:50 schrieb Tim Bray:

This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.

Thanks in advance!



--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath


    

    

  


--------------15E0899352537929C9BA0401--


From nobody Mon Jul 26 09:10:39 2021
Return-Path: 
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 E1DBD3A1BD2 for ; Mon, 26 Jul 2021 09:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 gcw_-hcHAp-Y for ; Mon, 26 Jul 2021 09:10:33 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (mail.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41F103A1BD1 for ; Mon, 26 Jul 2021 09:10:33 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYPzC1MBMz2xNH; Mon, 26 Jul 2021 18:10:31 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann 
In-Reply-To: <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org>
Date: Mon, 26 Jul 2021 18:10:30 +0200
X-Mao-Original-Outgoing-Id: 649008630.728323-f547a6d811ce9dc720092dc4dc70dba1
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org>
To: jsonpath@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: 
Subject: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 16:10:38 -0000

In the discussion of=20
https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103, =
it became apparent that we weren=E2=80=99t quite sure what levels of =
compliance language we should be using.  Particularly, I would think =
that a SHOULD is not very useful except when discussing corner cases (or =
non-functional requirements like =E2=80=9CSHOULD NOT blow up=E2=80=9D).

So are we ready to have multiple compliance levels?
A core set to which we expect everyone to comply and set of =
modules/features that can be added to the compliance?  No regular =
expressions in the core but an optional compliance module/feature for =
iregexps?

I don=E2=80=99t want to overthink that and propose a complicated set of =
modules where a single monolithic core would be sufficient, but =
stumbling into these modules without having planned for them is probably =
also not a good idea.

Gr=C3=BC=C3=9Fe, Carsten


> On 2021-07-24, at 17:18, Carsten Bormann  wrote:
>=20
> On 2021-07-20, at 19:50, Tim Bray  wrote:
>>=20
>> This is happening next Monday at 4PM Pacific time, which means in the =
middle of the night for the bulk of our EuroPeople; sorry about that.
>=20
> Apparently I didn=E2=80=99t pay enough attention, since I only just =
noticed that I have a conflict with IOTOPS in that slot.
>=20
> I think we need to have a slightly more frequent interim cadence.
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> --=20
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath


From nobody Mon Jul 26 12:24:13 2021
Return-Path: 
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 BA38D3A0905 for ; Mon, 26 Jul 2021 12:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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=yahoo.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 CeIId-5CCKoM for ; Mon, 26 Jul 2021 12:24:07 -0700 (PDT)
Received: from sonic303-3.consmr.mail.bf2.yahoo.com (sonic303-3.consmr.mail.bf2.yahoo.com [74.6.131.42]) (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 EF08A3A0902 for ; Mon, 26 Jul 2021 12:24:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1627327445; bh=vJOt8HjIRQePbOXN4SeHB9L7gWcO9UTd4P7ES5TFrMw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=ccgiuUzv4qvLI1jlGJmN5J5/pDd9nZJthEihLPGhWQnf3o7aSiD9A36scdC+lBd9Ik4YB7PI1nAe1g9z3StB9NoG966VEYRgm2pR7D/TPMJ99z6P5A8B+a8AP8CsghEvgSePM6y6PwQ5QYADH2UTcO66Fafpmyu3K0qj0uU04qrB2cpPaqV/Zay1MzqiuQR3QsdB7K2CZk6TogD2/RrO51jwwdr77LNgFRj+zXMo4bb1mpix9bI5Q32qn1ry3rCSgSpMjJ9X96XamQwsVOQcQAaf3xktLeXTI+ACrd6GJLTPxmQttbmgq960fcAwT59jmmKZEfhlQhUoMWVfJLkwZg==
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;  t=1627327445; bh=fx5xS05UBa7Tm5xap2v26EBhLCHdX4SRIMagUomE0A4=;  h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=WhTIK/+v1neXrV1u0jHU/+F8I+yzXosJOU/zJcvaQAkslCSBf+b3LZjG8QXnQWA7BNJA/UcciE9AE/hnfp6KfOzk/GXX0ulIg8qv+B2NXQ+druUQ3bhYhfABbwyuDwUgfkg47eK/g0h7RVOG6HWSw+9VdgDTmGmTtvTOLTkKxyBcBQfP/cjGKwGVBQLSxigNm43zvLovmmTSAlis0bSRv+hVzwym+SwJxO6+qqur3IKrC3fJLS3IhML80gdODgXajR7NlWBO19GScpzYGp+J7VyrKG9qJbV4GeKOgWmdt+GnHCcbQ5w6eC7qJk7m56M8lVSkXsi/XOV+ZHhfLVXkjA==
X-YMail-OSG: 8a9P8.gVM1kwCw9NXem6YPMJxS.aN_km7CnT3vKongYj6MUy0jxahdZTly.TXyb bz3LdwiMhePk3atRPps.0wHRjW0WEJ88Gx9rKqTQyHAxPRh443WiGfKh9D0Tk2zo_BYQ_mzxRRmc Ks10cQBp8YRl3UP82v5Gwg5NHRz8vFwlcDMiyC7SaCwsCSgDkoJwnrbGEX9P9TkCkIQckh8nI5gn D6woLv41MzfhCOzbJFzbfX7_iy3afUOR5uE.QLhLH3y0pC_ighy1pqcZuChANMlBJBljBZBFdv.d MFEiaHllZKI2h6JlIK_bAovDe5k04WPNpYCDuH4ihog6iRt0mOImg1rtmpcNCeLDEXXxdYv3e5FV pIA4.SMzUsML1L9jX05k29lJII7zYXZ_7XBOfQvIpieZl6bPotL9WmyB.__pUV.T6tsNXqF4uTcB ybSTuHhO9jLaHGyIYSK.VZZgdpvYScHFCdomNuN3sJiys7LOSpMr6JrtPC671Iiem8pg65msXBDI YdnJTAx.70lQ2_mZ4RHXJwdrtwXcPEmdhfHqGLQpVWNPZpItOH_vCltpnFy0VqJ0pW7PbYOiOaS9 lKOnl9SlX.t.4lWnq2imnySpYbcBVIvyPmYieNOMbnUiJQ07SMSBIQNJDlbSiZqDulwaLAp0dL8_ NLwLqnWJn5eqUL1ROjtewPihXPOUICCiiNUsPC6VW5vCTySdVAaR3EcwJS2qLOmk_nzo8.rzXOqf psvsgoCdaucsYBKtRM3sZSGVi9wR9f8h0BrBcuNQWNhuIorq4ng8zGfsJeqiAzsjWm2eY2uoEOhJ 2MWL.O35aNo.WXHo9VwczaaTHbteOQu.gcQ37i1QEAirDvg9e2OReCcmDOX00RMUewP6nn_G_Q9F Dn8WGA7vAEiFzBoZPjrTU1OFhZFU6XKwqKrhns0n6chRb941Aj3QgE2aCkbBbJT.8rkypIjNRmEr WWMzYfqMrdrcHWfuDL.O35t9lyg_kceE7Uhid2E6quI8HLnm82jnb7Crg2lA04NXM8YlMO.L0GL4 NOzr5RDkV9kzYQYBYfxUiFJ8kBipI5SStuQ0Y99ZIcHOKZxa8MEq2f5OjKDTQev6HgrACJDUwRjD U7uoG6FMTeYeriAnWB2fOdAU7jslxMrCKjVcKWlost14_iMVWPa9Llk9Gfk0blD2kHBVNAm4LaZ5 P3DLqYWJV5YWl5bf5PM00he_YfxndCrxK_fJcjr4Ct0fNGU6t2THs1Q.5iZ.aFcyxoOoLkj5FRg_ M4a3XUZqWhoWUNjmb344dbF_.KqNzVsUVSzpmCT_0uypkNQo_yqt19XtN17r4WL_A1SPfh0nBvQ3 35a4jvYPrxkROfDNCqJt8JLAlBk.amnmUzMDolARjGgWtr1jty3euccz6AidoU6gmTtF3KKo9VSx cscrW0.SYU3JNk81w5tAEZM5hzLsfHYsqekxBGkLX2JbU86YUS6OSk9b8b0VK19oTqDbLEnVe4YE rlWLoupE7uq0YtbzGHkNL1vmg8CTzQqdX16mUx1x.R6Od4JC9o08jLWdRURSZLrBoLixW9CquMlI LX5gxIR8QFBeFY_B160lLf0MJlzCqWEsVhx5vwJ3lREkRmJC_jO00vFvlygvEvFYi0quWLMNT7QS hZWgZDwNzS9YPINDfiRejascq3c7aB.mE0n32vje5GYGUzVnnYRJL2HNWKUKZ3q0rAGoE0JPhyn6 JeDegipkI4Z23cooifSCTqKMh4Kk7p1SkiRlOMO9gut.zIvAisKgl0C7nPe6fmsUg5crBBTr4ACv ixrFWzfP6oYvK.YyGW23FvElCnZ7EJYxL0AwD6qskX5Cp7oX9WdxLDkmoF8M0Fw3fyg.dE5BGUsL cFyRCKS9y6Z8G3v_zgEgX5HIq1A_cWNnCnksPUFzI621ukFSivKNddMTYjNG_YT3xdkhKgo0a05u O1X_5pudi3eV3.OcQgxop7YqWU7rjz7.XqOXMru1ZwrmH8k8zd3sG.FnqmnAJS6XkhLHe4sZBEWL ztB4BChbyQnoDpAHVKfdK0zeaYtbkm5cMLG5P3gI9gWtyenLj0crFF5R3EkyCV1FxOXqSkiELl2Y jR08D9MXcPmifNLE6caI2CHZilRebwPpy74Ee4B5mvwPvXQ8Zw_IpAndAso3tYTcW8wAPOBiNrhb 8aZHnBqAgFWre.m7cD3gnDo0n0XzzgGoXeAv6Z.VpbX5PA_n9KcM6xxRXrn8vGJOXcQ4iqlw2ck5 tqqiot6d72gkJL_4_2KGF3KkvEXSIGbYXvU7HWw5weWvu7JBmcAmGeXNbd4cTUnDgQnSd4dEnGFH 96bw6gFbxwdofJtUADHZFW13_RCa.DslivaABSDALof1_VXCgoqVdr4s.ywpA2KtVP22wFGod8UP CfFRHCZzLtKDpppnPlVdv4fXkOR1rzNVESWUr4h4WCAuLcMaz_VdDDtIeATfV1UV43B4LpDIlph4 CehrNX5PG.kVX0gLfPnQg2S4bKEvAYmiv8LI9bQzFTzJ5_ukCkSLHiyj2r9KhSIE8KdnM11cIBYv vpgL7uPofAPh51uA21AjUj2Fxug5_0ITTIRWJXHg2l1IvTkzhG8D8qcOCsam8mBbxBe_9L21_8ee 2SmMI.mhQWxHW88IRQGCFlXsIc2yM6fnrn0hICKpWYichfMU8I95atbwamrEE6ET069E6UY22uvU 9ZVJ8oid6zcAOAr8HCIVJDbg00uX0wbyf
X-Sonic-MF: 
Received: from sonic.gate.mail.ne1.yahoo.com by sonic303.consmr.mail.bf2.yahoo.com with HTTP; Mon, 26 Jul 2021 19:24:05 +0000
Date: Mon, 26 Jul 2021 19:23:58 +0000 (UTC)
From: Greg Dennis 
Reply-To: Greg Dennis 
To: stefan@goessner.net, Glyn Normington 
Cc: jsonpath@ietf.org, Tim Bray 
Message-ID: <336478305.893521.1627327438649@mail.yahoo.com>
In-Reply-To: 
References:  <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net>  
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_893520_263429540.1627327438648"
X-Mailer: WebService/1.1.18736 YahooMailAndroidMobile
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 19:24:12 -0000

------=_Part_893520_263429540.1627327438648
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I will not be able to make it as in heading into work now.
Greg
=20
=20
  On Tue, 27 Jul 2021 at 4:04 am, Stefan G=C3=B6ssner =
wrote:   --=20
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath
 =20

------=_Part_893520_263429540.1627327438648
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I will not be able to make it as in heading into work now.

Greg
 
 
 
 
On Tue, 27 Jul 2021 at 4:04 =
am, Stefan G=C3=B6ssner
<stefan@goessner.net> wrote:
 =

  

------=_Part_893520_263429540.1627327438648--


From nobody Mon Jul 26 12:33:08 2021
Return-Path: 
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 130283A097C for ; Mon, 26 Jul 2021 12:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 n7D4m62Uuc2h for ; Mon, 26 Jul 2021 12:33:02 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 8A5773A097B for ; Mon, 26 Jul 2021 12:33:02 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id e21so8433898pla.5 for ; Mon, 26 Jul 2021 12:33:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zWl6IYiYnkdL7oYpUcPCL0leYioMCZjJJt49LmIyYCc=; b=CUlyK380u8XhMKWIjhXZZYVXXzFSkKcQg9z0KsAi6fYSYu/4wtTAkvV0q8xpwDFfmb Jddd51jiPJSNzMtgekLBlNTs3wqbsrc0l7D5GD6I94rWo9xnnGFOQ89w/VcOCueSelvP KFbZQcYXStm3D+dNA9YhCpvYdCtJFHEWpkxwvvVCic1HoRirQWAIi1+AwH8ivxYqEMx5 3n8g2Ab29rX2/OydV613VQXjksoVvP+4KwD4i8pP11eFRX/o/MeqRYhUiWPWbMZD8KcU uepwKmfm4bBiQcgzj4uCrKOOWfXtXKu8CICzUyngns38ht/lt46vXl69ZFWW2c3rSNGp FIRA==
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=zWl6IYiYnkdL7oYpUcPCL0leYioMCZjJJt49LmIyYCc=; b=uKqQvuTbnp/L2cvmIrzv4nblAFaHjAWtLGqP48ejXwA5FcO16lw5YbdigFIOnapDw+ r/OBo3QR08DLvTWU6vtC8yDemmcty51zZkP1kJPQFtuZjJ+KRfVkNb6tZVtvQgF5tzsz D7um28I+LuQ/GhtAz1ATwPLjefdfy5T5FCj67NbkYiiUqTwyU3kHDcLnBjN3JFmJ9Ni5 1m9KIA99n1g0/ha5qHySutwf8AAqo1lEaUFKbRGqFR75NUXk7YFZQnhVakVX4d51v1NO 7M6gzpsBAcya7msYrcwWnRzbfv8zo4Oki3rsBd0snNOFBsAPelOmA4OKfgNb5ohPEnDU Sz1w==
X-Gm-Message-State: AOAM5332Zz9ILv95z3iR5a06zy0OZbQ4fxeCnYookqgCsALGjlNkm3nd XJr1wGDwwpGaWhyGqVUoFLFvV/1+uK9lV3/TiME=
X-Google-Smtp-Source: ABdhPJwLAd9F13og14S3TJB1d5jc+KOb9LtIcnNjeI72kaFzZWpdfmM4z3Dqia+n8Wp+D4CaQj+KNU4SSaQVY23eUNI=
X-Received: by 2002:a65:6243:: with SMTP id q3mr19733095pgv.297.1627327981051;  Mon, 26 Jul 2021 12:33:01 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org>
In-Reply-To: <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org>
From: Glyn Normington 
Date: Mon, 26 Jul 2021 20:32:47 +0100
Message-ID: 
To: Carsten Bormann 
Cc: Tim Bray , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003e608305c80bd2a1"
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 19:33:07 -0000

--0000000000003e608305c80bd2a1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Carsten: for the avoidance of uncertainty, which meeting will you be
attending, JSONPath or IOTOPS?

Greg can't make it.

Stefan needs to register, which could be a bit tight, e.g. if he needs a
fee waiver.

I am planning to attend, but if the Chairs think we won't be able to make
much progress given the above, shall we reschedule to an interim meeting in
the next week or two?

Regards,
Glyn


On Sat, 24 Jul 2021, 16:18 Carsten Bormann,  wrote:

> On 2021-07-20, at 19:50, Tim Bray  wrote:
> >
> > This is happening next Monday at 4PM Pacific time, which means in the
> middle of the night for the bulk of our EuroPeople; sorry about that.
>
> Apparently I didn=E2=80=99t pay enough attention, since I only just notic=
ed that I
> have a conflict with IOTOPS in that slot.
>
> I think we need to have a slightly more frequent interim cadence.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
> --
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
>
>

--0000000000003e608305c80bd2a1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Carsten: for the avoidance of uncertainty, which meeting =
will you=C2=A0be attending, JSONPath or IOTOPS?

=

Greg can't make it.=C2=A0

=

Stefan needs to register, which could be a bit tigh=
t, e.g. if he needs a fee waiver.

I am planning to attend, but if the Chairs think we won't be =
able to make much progress given the above, shall we reschedule to an inter=
im meeting in the next week or two?

Regards,
Glyn


On Sat, 24=
 Jul 2021, 16:18 Carsten Bormann, <cabo@=
tzi.org> wrote:
On 2021-07-2=
0, at 19:50, Tim Bray <tbray@textuality.com> wrote:

> 

> This is happening next Monday at 4PM Pacific time, which means in the =
middle of the night for the bulk of our EuroPeople; sorry about that.



Apparently I didn=E2=80=99t pay enough attention, since I only just noticed=
 that I have a conflict with IOTOPS in that slot.



I think we need to have a slightly more frequent interim cadence.



Gr=C3=BC=C3=9Fe, Carsten



-- 

Jsonpath mailing list

J=
sonpath@ietf.org

https://www.ietf.org/mailman/listinfo/jsonp=
ath





--0000000000003e608305c80bd2a1--


From nobody Mon Jul 26 12:41:44 2021
Return-Path: 
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 86E773A09DD for ; Mon, 26 Jul 2021 12:41:41 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 4nLCIYEA3e6J for ; Mon, 26 Jul 2021 12:41:36 -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 5E9BE3A09E0 for ; Mon, 26 Jul 2021 12:41:36 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id g13so17467955lfj.12 for ; Mon, 26 Jul 2021 12:41:36 -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=1pKHYL+7bmCW99jCQMwU3/RLhtVi6Cx8rl+wpiksfJk=; b=Up9liN3I2s6hruOHhxRJMBE8ZyPPaEMDf+RJ+p2FcJ0o/bjEZ2Q048ilSCVQJA0lCd 9n/f+OFJiqRU/E5eSFFr2KCUR9F1FSvvk25NGAFgv/IrFE9razP8q4Sufs6jb6UBhLqd i8EIHo1xvJqngTGZMJT0lV/xcGHC0LVmMtsqLoX/UqAHirQ+2SxhHN936laQZAcTIzNB 4TjmBO/1axT74EpEuHUwdthGV7mbGPO4D3UvMpfoAoIpcrLJgTPF2OH/U1+OJI/1SvnG 5R5of3GaZjgZw9E2H4+W2HO+csLt1gRQpI6lR+tQ/6JM6cMrHMcw49zzWhAXQ1u8dJPm s43w==
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=1pKHYL+7bmCW99jCQMwU3/RLhtVi6Cx8rl+wpiksfJk=; b=EpPo1LL7CNxPdGCsSii+qX7Y/cB9OCeJaYkz5UgNqc9DlpgU2NjcZvzUQUK6MecYAH 0q5kyd+tBfkvUm6S/QX3HsHRUAmmlq0kPpRCyiMT3AO6EjcSRmUVxQzCzeVbBaZ1fvvf 8gOHi9cOmTtfa5m2mqRs+rvowKs99INXu9C8pU8IMVfRimv4cQW39j9t8IdGMIwtUsBq dHsOcFI6Izn3qxQjZYlKgON1aWQ5MWb1vdMx34lNBiH8mHRpSaYwuij9PWojHSZb8mAm HPENipGjkgG2910qB0BOCDfTBmEZvbCsENwKzWUU0OzevVcgZ80aRNryqy9uaVngWVKQ OJsw==
X-Gm-Message-State: AOAM533aujmRFscC8O+ZAOtNBysb2A1JMk7SSsF9djsiRjGerhlOF+Pu us2oUl/ncxB/PhNAY7YGab8NQI5YdVli4cQSwzFIew==
X-Google-Smtp-Source: ABdhPJy7tOjqOqSMmSE4ofp3qY4N0uPEtHLKM6uDM6hVHTeM3LSsNcIlbhX/X9RebbriaMDb+1x0h1K+NRZ4PiVt3Cc=
X-Received: by 2002:a19:c504:: with SMTP id w4mr14090903lfe.192.1627328494012;  Mon, 26 Jul 2021 12:41:34 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> 
In-Reply-To: 
From: Tim Bray 
Date: Mon, 26 Jul 2021 12:41:23 -0700
Message-ID: 
To: Glyn Normington 
Cc: Carsten Bormann , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d19d8305c80bf0c8"
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 19:41:42 -0000

--000000000000d19d8305c80bf0c8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

We should also think about other IETFers who haven't been active but have
arranged their schedule to come to our long-scheduled meeting and might be
grumpy if it's suddenly canceled.  My feeling is that we should gather, see
how many people show up in a few minutes, then decide whether to proceed.

On Mon, Jul 26, 2021 at 12:33 PM Glyn Normington <
glyn.normington.work@gmail.com> wrote:

> Carsten: for the avoidance of uncertainty, which meeting will you be
> attending, JSONPath or IOTOPS?
>
> Greg can't make it.
>
> Stefan needs to register, which could be a bit tight, e.g. if he needs a
> fee waiver.
>
> I am planning to attend, but if the Chairs think we won't be able to make
> much progress given the above, shall we reschedule to an interim meeting =
in
> the next week or two?
>
> Regards,
> Glyn
>
>
> On Sat, 24 Jul 2021, 16:18 Carsten Bormann,  wrote:
>
>> On 2021-07-20, at 19:50, Tim Bray  wrote:
>> >
>> > This is happening next Monday at 4PM Pacific time, which means in the
>> middle of the night for the bulk of our EuroPeople; sorry about that.
>>
>> Apparently I didn=E2=80=99t pay enough attention, since I only just noti=
ced that
>> I have a conflict with IOTOPS in that slot.
>>
>> I think we need to have a slightly more frequent interim cadence.
>>
>> Gr=C3=BC=C3=9Fe, Carsten
>>
>> --
>> Jsonpath mailing list
>> Jsonpath@ietf.org
>> https://www.ietf.org/mailman/listinfo/jsonpath
>>
>>

--000000000000d19d8305c80bf0c8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


We =
should also think about other IETFers who haven't been active but have =
arranged their schedule to come to our long-scheduled meeting and might be =
grumpy if it's suddenly canceled.=C2=A0 My feeling is that we should=C2=
=A0gather, see how many people show up in a few minutes, then decide whethe=
r to proceed.

On Mon, Jul 26, 2021 at 12:33 PM Glyn Normington <glyn.normington.work@gmail.c=
om> wrote:
Carsten: for =
the avoidance of uncertainty, which meeting will you=C2=A0be attending, JSO=
NPath or IOTOPS?

Greg can'=
t make it.=C2=A0

Stefan =
needs to register, which could be a bit tight, e.g. if he needs a fee waive=
r.

I am planning to atte=
nd, but if the Chairs think we won't be able to make much progress give=
n the above, shall we reschedule to an interim meeting in the next week or =
two?

Regards,
Glyn


On Sat, 24 Jul 2021, 16:18 Carsten Borman=
n, <cabo@tzi.org&g=
t; wrote:
On 2021-07-20, at 19:50, Tim Bray <<=
a href=3D"mailto:tbray@textuality.com" rel=3D"noreferrer" target=3D"_blank"=
>tbray@textuality.com> wrote:

> 

> This is happening next Monday at 4PM Pacific time, which means in the =
middle of the night for the bulk of our EuroPeople; sorry about that.



Apparently I didn=E2=80=99t pay enough attention, since I only just noticed=
 that I have a conflict with IOTOPS in that slot.



I think we need to have a slightly more frequent interim cadence.



Gr=C3=BC=C3=9Fe, Carsten



-- 

Jsonpath mailing list

J=
sonpath@ietf.org

https://www.ietf.org/mailman/listinfo/jsonp=
ath






--000000000000d19d8305c80bf0c8--


From nobody Mon Jul 26 12:42:49 2021
Return-Path: 
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 D0A063A09D9 for ; Mon, 26 Jul 2021 12:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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=gmail.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 xBFcPrLtsoPW for ; Mon, 26 Jul 2021 12:42:43 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 117823A09EC for ; Mon, 26 Jul 2021 12:42:42 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id e14so13000921plh.8 for ; Mon, 26 Jul 2021 12:42:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EcCAHfDkDAx95RmpE7aqWSGCvFKYg7AM2k1GYNDjJfo=; b=jZA+E4QGRqEdAXShf2ZPoQ3UfdrMKoIV+31rxY5i7NUTofNdZ5RIfwTgN/slObFLZP 3eaDtOBWUvhJZkZkvA/hMbBAbxa5+ucTc+WlgKpEMRDNop0CjbQ6jaXm+Kd4OyIoTwBe NOh2H8HkoyJfpE5YaL7sPC1O/c7Zyp2y7kPyacAwUp+lIRcesmXEzhf1J6Ftzbnwmdga 0fzCTL69pLV9gP9wH4pgpHNi1oDImhsZGyBAXqNqVJoG7bkvpQTGCetWhXVH5MoWsT9n oVVczxcmkm242mF2ZxNexcVcs6H0EF6rwB6wPNTGG85PV2kxSidRRwLhFwHt4BEzj/19 owEg==
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=EcCAHfDkDAx95RmpE7aqWSGCvFKYg7AM2k1GYNDjJfo=; b=AMKXt5vDpWBTcFg7dLcN129VdJvCez/xb+QuHrO1Dka5dFrt/AANsEArabwYGVbfjo qyjmzXifzBX4jlJiSN9+pMx/vAbwYbbSdTGnrIODjOCWwWB/A/AI2iYAZfJW0+igSk/h Syb9Lg6GP29GxPvZvY3JyhAYAVl1NFKNMOKmMOinwygmZTkXlc98Or9tWveUZla38eb0 czsi2fTyHvkcOqbARAu2WRiGD7tEX87aefBn2TQT3qd/rrCCciKBTjSJNH12RmzPw1YF IkXtNSL+3IDCU1vNyLfOdix54T0wxXNtpIpPRTAg+UrAEknozdAHc+quJkdG6YCu+hTr fxfQ==
X-Gm-Message-State: AOAM533637QEKZ5Ac3/okaOedRbXV0eMoWSsK7XK3TvNWgL0Np18JRRG 9zaLwRCMGoJFGN8ZIRV8MSUJaA3dGXbYHknR1rA=
X-Google-Smtp-Source: ABdhPJzVH13albw2esJ5FNYB1Vze2dunE2AOpwdm0Ii4e2be3IFoF4EjKWk5egl0tuzTQ1Gm76KLhaw66fsZh4t8EUc=
X-Received: by 2002:a17:90a:c092:: with SMTP id o18mr562975pjs.3.1627328561988;  Mon, 26 Jul 2021 12:42:41 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org>  
In-Reply-To: 
From: Glyn Normington 
Date: Mon, 26 Jul 2021 20:42:29 +0100
Message-ID: 
To: Tim Bray 
Cc: Carsten Bormann , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="000000000000decb5005c80bf4e6"
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 19:42:48 -0000

--000000000000decb5005c80bf4e6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Ok, thanks Tim!

On Mon, 26 Jul 2021, 20:41 Tim Bray,  wrote:

> We should also think about other IETFers who haven't been active but have
> arranged their schedule to come to our long-scheduled meeting and might b=
e
> grumpy if it's suddenly canceled.  My feeling is that we should gather, s=
ee
> how many people show up in a few minutes, then decide whether to proceed.
>
> On Mon, Jul 26, 2021 at 12:33 PM Glyn Normington <
> glyn.normington.work@gmail.com> wrote:
>
>> Carsten: for the avoidance of uncertainty, which meeting will you be
>> attending, JSONPath or IOTOPS?
>>
>> Greg can't make it.
>>
>> Stefan needs to register, which could be a bit tight, e.g. if he needs a
>> fee waiver.
>>
>> I am planning to attend, but if the Chairs think we won't be able to mak=
e
>> much progress given the above, shall we reschedule to an interim meeting=
 in
>> the next week or two?
>>
>> Regards,
>> Glyn
>>
>>
>> On Sat, 24 Jul 2021, 16:18 Carsten Bormann,  wrote:
>>
>>> On 2021-07-20, at 19:50, Tim Bray  wrote:
>>> >
>>> > This is happening next Monday at 4PM Pacific time, which means in the
>>> middle of the night for the bulk of our EuroPeople; sorry about that.
>>>
>>> Apparently I didn=E2=80=99t pay enough attention, since I only just not=
iced that
>>> I have a conflict with IOTOPS in that slot.
>>>
>>> I think we need to have a slightly more frequent interim cadence.
>>>
>>> Gr=C3=BC=C3=9Fe, Carsten
>>>
>>> --
>>> Jsonpath mailing list
>>> Jsonpath@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jsonpath
>>>
>>>

--000000000000decb5005c80bf4e6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Ok, thanks Tim!

On Mon, 26 Jul 2021, 20:41 Tim Bray, <<=
a href=3D"mailto:tbray@textuality.com">tbray@textuality.com> wrote:<=
br>
We should also think about other IETFe=
rs who haven't been active but have arranged their schedule to come to =
our long-scheduled meeting and might be grumpy if it's suddenly cancele=
d.=C2=A0 My feeling is that we should=C2=A0gather, see how many people show=
 up in a few minutes, then decide whether to proceed.

On Mon, Jul 26, =
2021 at 12:33 PM Glyn Normington <glyn.normington.work@gmail=
.com> wrote:
Carsten: fo=
r the avoidance of uncertainty, which meeting will you=C2=A0be attending, J=
SONPath or IOTOPS?

Greg can=
9;t make it.=C2=A0

Stefa=
n needs to register, which could be a bit tight, e.g. if he needs a fee wai=
ver.

I am planning to at=
tend, but if the Chairs think we won't be able to make much progress gi=
ven the above, shall we reschedule to an interim meeting in the next week o=
r two?

Regards,
Glyn


On Sat, 24 Jul 2021, 16:18 Carsten Borm=
ann, <cabo@tzi.org> wrote:
On 2021-07-20, at =
19:50, Tim Bray <tbray@textuality.com> wrote:

> 

> This is happening next Monday at 4PM Pacific time, which means in the =
middle of the night for the bulk of our EuroPeople; sorry about that.



Apparently I didn=E2=80=99t pay enough attention, since I only just noticed=
 that I have a conflict with IOTOPS in that slot.



I think we need to have a slightly more frequent interim cadence.



Gr=C3=BC=C3=9Fe, Carsten



-- 

Jsonpath mailing list

Jsonpath@ietf.org

https://www.ietf.org/mailman/lis=
tinfo/jsonpath







--000000000000decb5005c80bf4e6--


From nobody Mon Jul 26 12:44:58 2021
Return-Path: 
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 387B73A0A0D for ; Mon, 26 Jul 2021 12:44:57 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 9sams4SeJ43i for ; Mon, 26 Jul 2021 12:44:52 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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 058563A0A08 for ; Mon, 26 Jul 2021 12:44:51 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id d17so17631948lfv.0 for ; Mon, 26 Jul 2021 12:44:51 -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=ngcETGIlLOmb58+mL5VOZIqUp8dp3WSyILotfm2jSW8=; b=1qCP2auUoJGfIevtO32uBLlF0ASvb/8hAWe09H7swn5b7DnWMW2r7p6j08LDRIAHGA kS/u/T4Ka/RhzGCVzgarUA5Go9d3nOLHhC8zI2hqgILNZ+UDYGZgolLMOpq7ewEXJ+E7 Di4VBqzg647ITNe2S2rvgRwus2VANZal4BHXpbt+KRqlUD4W20ND5vz7R9nEqLQWMqal THVl7Gsl3t+wjChFuBdJ0uGBHKTHfN63vs8w/lqJyVeUsKkrPb6vaPX0RDM4gWwYEk+q rgnUaJWw6kad3mvXMoVWu7cu1A8TOWlJn3BNGCAzSFZtUlL3f42ydRvMpegNiDnhMTvr i4hw==
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=ngcETGIlLOmb58+mL5VOZIqUp8dp3WSyILotfm2jSW8=; b=eTXh29zGkGhJuBEbxVEnMnOm+1FFqv2/QOaL8f1ZzSBICDWFIDW/UM3wUYA6IP10vJ b321tJCe/niCgAMtuRsE1GMVHloICFZx7C/oTFMsTSFRQtk8nFGhOqfVmpuw3BHaq43F Fe7CQluSdejRPTn1N2GpWNT9HxogY5CmZ/nSuyCXd7hZ0xjvPif6tq5Y+GamWVbc9ygF ob7qykYCKg4U30jpV7wUpKZjR6FzKXolySMnf7EM8ZDdRQ3u2xD2Ivgu6TxS2QKiswV1 jT/Hs/7xbN06h3EJ03qizSF/DxTdUh4sk+afZJOvVR4K2pyu5BIAbSV5BPe3NU9Gz0AK LQNg==
X-Gm-Message-State: AOAM532YZaypPEOPA3cOsCMnMeFeZ2M6lULzpYWKBVi7WghBLqz8E7nY 7EfRP3PoKMTPDyXZGodCLumcWps97eDCMLkZDFU03Q==
X-Google-Smtp-Source: ABdhPJxd006VNILpg+QYnz2SZ6IZcbf4IW4jtjR2Di3E/Kx4o8U2q631N4lHCsfvb0xjA8YBS35YSD99HGHg9jpPclk=
X-Received: by 2002:a19:e00a:: with SMTP id x10mr14391225lfg.536.1627328688686;  Mon, 26 Jul 2021 12:44:48 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org>   
In-Reply-To: 
From: Tim Bray 
Date: Mon, 26 Jul 2021 12:44:37 -0700
Message-ID: 
To: Glyn Normington 
Cc: Carsten Bormann , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006c293805c80bfcde"
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 19:44:57 -0000

--0000000000006c293805c80bfcde
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

And BTW, if we don't get to any useful work, agreed on another interim
before too long.

On Mon, Jul 26, 2021 at 12:42 PM Glyn Normington <
glyn.normington.work@gmail.com> wrote:

> Ok, thanks Tim!
>
> On Mon, 26 Jul 2021, 20:41 Tim Bray,  wrote:
>
>> We should also think about other IETFers who haven't been active but hav=
e
>> arranged their schedule to come to our long-scheduled meeting and might =
be
>> grumpy if it's suddenly canceled.  My feeling is that we should gather, =
see
>> how many people show up in a few minutes, then decide whether to proceed=
.
>>
>> On Mon, Jul 26, 2021 at 12:33 PM Glyn Normington <
>> glyn.normington.work@gmail.com> wrote:
>>
>>> Carsten: for the avoidance of uncertainty, which meeting will you be
>>> attending, JSONPath or IOTOPS?
>>>
>>> Greg can't make it.
>>>
>>> Stefan needs to register, which could be a bit tight, e.g. if he needs =
a
>>> fee waiver.
>>>
>>> I am planning to attend, but if the Chairs think we won't be able to
>>> make much progress given the above, shall we reschedule to an interim
>>> meeting in the next week or two?
>>>
>>> Regards,
>>> Glyn
>>>
>>>
>>> On Sat, 24 Jul 2021, 16:18 Carsten Bormann,  wrote:
>>>
>>>> On 2021-07-20, at 19:50, Tim Bray  wrote:
>>>> >
>>>> > This is happening next Monday at 4PM Pacific time, which means in th=
e
>>>> middle of the night for the bulk of our EuroPeople; sorry about that.
>>>>
>>>> Apparently I didn=E2=80=99t pay enough attention, since I only just no=
ticed
>>>> that I have a conflict with IOTOPS in that slot.
>>>>
>>>> I think we need to have a slightly more frequent interim cadence.
>>>>
>>>> Gr=C3=BC=C3=9Fe, Carsten
>>>>
>>>> --
>>>> Jsonpath mailing list
>>>> Jsonpath@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/jsonpath
>>>>
>>>>

--0000000000006c293805c80bfcde
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


And=
 BTW, if we don't get to any useful work, agreed on another interim bef=
ore=C2=A0too long.

On Mon, Jul 26, 2021 at 12:42 PM Glyn Normington &l=
t;glyn.normington.work@gm=
ail.com> wrote:
Ok, than=
ks Tim!

On Mon, 26 Jul 2021, 20:41 Tim Bray, <tbray@textuality.com> wrote:
We should also think about other IETFers who haven't bee=
n active but have arranged their schedule to come to our long-scheduled mee=
ting and might be grumpy if it's suddenly canceled.=C2=A0 My feeling is=
 that we should=C2=A0gather, see how many people show up in a few minutes, =
then decide whether to proceed.

<=
div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 26, 2021 at 12:33 PM Glyn =
Normington <glyn.normington.work@gmail.com> wrote:
Carsten: for the avoidance of unc=
ertainty, which meeting will you=C2=A0be attending, JSONPath or IOTOPS?
Greg can't make it.=C2=A0

Stefan needs to register, w=
hich could be a bit tight, e.g. if he needs a fee waiver.

I am planning to attend, but if the Chair=
s think we won't be able to make much progress given the above, shall w=
e reschedule to an interim meeting in the next week or two?

Regards,
Glyn<=
/div>

On Sat, 24 Jul 2021, 16:18 Carsten Bormann, <cabo@tzi.org&=
gt; wrote:
On 2021-07-20, at 19:50, Tim Bray <=
tbray@textuality.com> wrote:

> 

> This is happening next Monday at 4PM Pacific time, which means in the =
middle of the night for the bulk of our EuroPeople; sorry about that.



Apparently I didn=E2=80=99t pay enough attention, since I only just noticed=
 that I have a conflict with IOTOPS in that slot.



I think we need to have a slightly more frequent interim cadence.



Gr=C3=BC=C3=9Fe, Carsten



-- 

Jsonpath mailing list

Jsonpath@ietf.org

https://www.ietf.org/mailman/lis=
tinfo/jsonpath










--0000000000006c293805c80bfcde--


From nobody Mon Jul 26 12:50:27 2021
Return-Path: 
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 370E03A0A64 for ; Mon, 26 Jul 2021 12:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 DD8Wb8mxIHWD for ; Mon, 26 Jul 2021 12:50:21 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E55E53A0A63 for ; Mon, 26 Jul 2021 12:50:20 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYVrn0kKYz31LD; Mon, 26 Jul 2021 21:50:17 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann 
In-Reply-To: 
Date: Mon, 26 Jul 2021 21:50:16 +0200
Cc: Tim Bray , jsonpath@ietf.org
X-Mao-Original-Outgoing-Id: 649021816.59386-1ae149d1a442d9cda91c110f23dae0cf
Content-Transfer-Encoding: quoted-printable
Message-Id: <9305DD00-F602-4EC5-B3C6-D9917F8D8A14@tzi.org>
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> 
To: Glyn Normington 
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 19:50:25 -0000

On 2021-07-26, at 21:32, Glyn Normington =
 wrote:
>=20
> Carsten: for the avoidance of uncertainty, which meeting will you be =
attending, JSONPath or IOTOPS?

IOTOPS.  I think I have just cleared my SECDISPATCH engagement.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Jul 26 12:55:37 2021
Return-Path: 
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 704463A0AB3 for ; Mon, 26 Jul 2021 12:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 iJFEYJ_n03Kj for ; Mon, 26 Jul 2021 12:55:31 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC69D3A0AB2 for ; Mon, 26 Jul 2021 12:55:30 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYVyl3wH3z2xLM; Mon, 26 Jul 2021 21:55:27 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann 
In-Reply-To: <9305DD00-F602-4EC5-B3C6-D9917F8D8A14@tzi.org>
Date: Mon, 26 Jul 2021 21:55:27 +0200
Cc: Tim Bray , jsonpath@ietf.org
X-Mao-Original-Outgoing-Id: 649022126.937701-2161ede9ddc970792debf22ee00c56b9
Content-Transfer-Encoding: quoted-printable
Message-Id: 
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org>  <9305DD00-F602-4EC5-B3C6-D9917F8D8A14@tzi.org>
To: Glyn Normington 
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 19:55:36 -0000

On 2021-07-26, at 21:50, Carsten Bormann  wrote:
>=20
> IOTOPS.  I think I have just cleared my SECDISPATCH engagement.

=E2=80=A6 and, if you summon me (e.g., on Jabber), I=E2=80=99ll jump =
over briefly.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Mon Jul 26 15:52:07 2021
Return-Path: 
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 B55363A0873 for ; Mon, 26 Jul 2021 15:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level: 
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 P8SbWja6lW33 for ; Mon, 26 Jul 2021 15:51:52 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 560313A08B0 for ; Mon, 26 Jul 2021 15:51:49 -0700 (PDT)
Received: from [192.168.178.20] ([88.130.51.150]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MIMKq-1ltnSI3aeC-00EQ3L; Tue, 27 Jul 2021 00:51:46 +0200
To: Glyn Normington 
Cc: Tim Bray , jsonpath@ietf.org
References:  <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net> 
From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= 
Message-ID: <2087b888-d908-ef8f-cd94-6c2b04d69bd2@goessner.net>
Date: Tue, 27 Jul 2021 00:51:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: 
Content-Type: multipart/alternative; boundary="------------D93F19BE1AFE2F535AD93E65"
X-Provags-ID: V03:K1:UawOxzWHnl8eIwp9dJQXcJghcsg4+U2yoQ0B6sraV4w3E5mGmxa QWENr13lSOJZ8x/ba97sOLsACF1XUg86D9XKhfmjSK7gOIPKkFFkkJo0rGu/07Vh38GcByQ W5e/b2HwGCx8aBnsAPPs3HWPrCMiZttkvUm0sg4Iuao7YPBTHIHtg4ZL2L17D3cwv7JvoI2 MfDw+xSEbacWu8rVCQwiA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:e7cd8Va5EoA=:yPXVX9lH/kfQ5MH49q+NHm kuwq7PGe2BtFGawrkG/DaNozx04jd//wFjdTuI7DN98sWVcKCnMxJza0UGj4WfQDMwbbx5YZE DXEHraFntWHu+ytPnAbeZyTvDxVwRuhqKUlqBwntpax/WDsEi+TvTIQZCNJNiV9zSnd9Yd5IU QvZOiinjMb8S5vvG2tPI+LmsR2LFyN5XNsZz6a41XMyKFlBt/ACeUAuihrjzF09yF5rkaUtEj hChcRNdRGbMt+n0MSuWBzJyOXsgNbI+JN9b+gNFSUaz/Kby8c/Ji8LABb0DQqElGOEUfTNVk4 IPB7qTEq29EbhbF074Nko7l9sweLlOmQ3rHR0dLAcqiLzJQVEnqjw9+KeO767VT8TEu9WDrek yuGAoe/9iQcd0kqViRelP9h+duLkFe97GQJtu4DasuPTpSgya6moVdqeuZu/ZdkWWk0FSBT09 +SeI58l+l/LI71AAeffzV5I+fZ1SVmPKlHcXWaK8px+axIOoeXnHLtIvvcwlBWHffp1NQRPrk 0nWYAuR9HMR1GI9GhV8KKiDzy/0nOhQJ5JHTURbOOj1P0TyYMsUIiowSgEJvMxEcV5gIsdObC 3xNGtFbdevL4YveP/dWr31NTNvVZxanVoOaxEKNHcV6G/S7l5gvhCOoNV5HfXdVadSeGhAp8O 8bU5RxPPQ+l/k7ghtoLWjfWq1iKhAOwSRcLyEOIitfTmUsHJjTWsnbP+FDOIvrZKgg6GaR+1f VC7A+VVKI/Ul8eFpEJdRKw0VTElb+Cnw8iRaqyYyeoUpYYMRM/jQo/yXQiR3yEbz8vq727CG+ cj3SiybEBbOYLHJmytDZsPmGWt/uZf0jxJaRB5AF3O+KZYSt/XMGQCCYqYrnjzhQavdkANj
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 22:52:06 -0000

This is a multi-part message in MIME format.
--------------D93F19BE1AFE2F535AD93E65
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

hmm ... do I need to pay a fee to register ?


Am 26.07.2021 um 18:01 schrieb Glyn Normington:
> Hi Stefan
>
> Tonight's meeting is on MeetEcho as part of IETF 111 which requires
> you to register (see https://www.ietf.org/how/meetings/111/).
>
> Once you've registered, click this link to access meetecho:
> https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1
>
> Hope you can make it!
>
> Regards,
> Glyn
>
> On Mon, 26 Jul 2021 at 16:50, Stefan Gössner  wrote:
>> How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
>> --
>> sg
>>
>>
>> Am 20.07.2021 um 19:50 schrieb Tim Bray:
>>
>> This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.
>>
>> We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.
>>
>> Thanks in advance!
>>
>>
>>
>> --
>> Jsonpath mailing list
>> Jsonpath@ietf.org
>> https://www.ietf.org/mailman/listinfo/jsonpath


--------------D93F19BE1AFE2F535AD93E65
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    hmm ... do I need to pay a
        fee to register ?

        

      

    
Am 26.07.2021 um 18:01 schrieb Glyn
      Normington:

    

    

      
Hi Stefan

Tonight's meeting is on MeetEcho as part of IETF 111 which requires
you to register (see https://www.ietf.org/how/meetings/111/).

Once you've registered, click this link to access meetecho:
https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1

Hope you can make it!

Regards,
Glyn

On Mon, 26 Jul 2021 at 16:50, Stefan Gössner <stefan@goessner.net> wrote:


      

        
How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
--
sg


Am 20.07.2021 um 19:50 schrieb Tim Bray:

This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.

Thanks in advance!



--
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath


      

      

    

    

  


--------------D93F19BE1AFE2F535AD93E65--


From nobody Mon Jul 26 15:54:21 2021
Return-Path: 
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 71D973A085D for ; Mon, 26 Jul 2021 15:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 nXVNKnTDFRsf for ; Mon, 26 Jul 2021 15:54:14 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC50B3A0856 for ; Mon, 26 Jul 2021 15:54:14 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYZwy6lxPz2xKB; Tue, 27 Jul 2021 00:54:10 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann 
In-Reply-To: <2087b888-d908-ef8f-cd94-6c2b04d69bd2@goessner.net>
Date: Tue, 27 Jul 2021 00:54:10 +0200
Cc: Glyn Normington , jsonpath@ietf.org, Tim Bray 
X-Mao-Original-Outgoing-Id: 649032850.465139-9df4f1e0d920b354ff85a12acebbf0de
Content-Transfer-Encoding: quoted-printable
Message-Id: <7EA7418C-E0C9-4406-B6F3-85DA8A3A2779@tzi.org>
References:  <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net>  <2087b888-d908-ef8f-cd94-6c2b04d69bd2@goessner.net>
To: =?utf-8?Q?Stefan_G=C3=B6ssner?= 
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 22:54:20 -0000

You can use the fee waiver program

> On 2021-07-27, at 00:51, Stefan G=C3=B6ssner  =
wrote:
>=20
> hmm ... do I need to pay a fee to register ?
>=20
>=20
> Am 26.07.2021 um 18:01 schrieb Glyn Normington:
>> Hi Stefan
>>=20
>> Tonight's meeting is on MeetEcho as part of IETF 111 which requires
>> you to register (see=20
>> https://www.ietf.org/how/meetings/111/
>> ).
>>=20
>> Once you've registered, click this link to access meetecho:
>>=20
>> =
https://meetings.conf.meetecho.com/ietf111/?group=3Djsonpath&short=3D&item=
=3D1
>>=20
>>=20
>> Hope you can make it!
>>=20
>> Regards,
>> Glyn
>>=20
>> On Mon, 26 Jul 2021 at 16:50, Stefan G=C3=B6ssner=20
>> 
>>  wrote:
>>=20
>>> How will it be possible to attend the meeting tonight ... =
technically ?  WebEx or something ?
>>> --
>>> sg
>>>=20
>>>=20
>>> Am 20.07.2021 um 19:50 schrieb Tim Bray:
>>>=20
>>> This is happening next Monday at 4PM Pacific time, which means in =
the middle of the night for the bulk of our EuroPeople; sorry about =
that.
>>>=20
>>> We have a good track record of settling issues at our meetings and =
interims so far, so I'm optimistic we can succeed again.  This would be =
a good time for WG participants to suggest issues they think are near =
the front of the queue.
>>>=20
>>> Thanks in advance!
>>>=20
>>>=20
>>>=20
>>> --
>>> Jsonpath mailing list
>>>=20
>>> Jsonpath@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jsonpath
>=20
> --=20
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath


From nobody Mon Jul 26 15:59:26 2021
Return-Path: 
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 A77803A08CF for ; Mon, 26 Jul 2021 15:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 D5MrxmlzoqjY for ; Mon, 26 Jul 2021 15:59:11 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F8D63A08B8 for ; Mon, 26 Jul 2021 15:59:03 -0700 (PDT)
Received: from [192.168.178.20] ([88.130.51.150]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MgeXk-1lRMcj0syy-00h8C3; Tue, 27 Jul 2021 00:58:53 +0200
To: Carsten Bormann 
Cc: Glyn Normington , jsonpath@ietf.org, Tim Bray 
References:  <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net>  <2087b888-d908-ef8f-cd94-6c2b04d69bd2@goessner.net> <7EA7418C-E0C9-4406-B6F3-85DA8A3A2779@tzi.org>
From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= 
Message-ID: <09331691-f236-6ee2-2596-02e404305a23@goessner.net>
Date: Tue, 27 Jul 2021 00:58:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <7EA7418C-E0C9-4406-B6F3-85DA8A3A2779@tzi.org>
Content-Type: multipart/alternative; boundary="------------A43734BABF57ABD853B8CB63"
X-Provags-ID: V03:K1:GLkglYXrk5BaBXS9RNG/h0Kk3xvyLOXBebAn+V9FFGstSE86igj HZzBmLdzEUDThXe5xRDVwY23BFQSGuTfRdNZhWHXgNv+1hQGj+OAU3VmQSSNFk68ky9VEml GvRMoX0nBFn+VRVOZAdWl03B0+6uxR/NRyJM2Yp50wZAXIaaVLAz2cEOgu5rk2Z/RpoIhZz bp0bvH0+LOIVjpSPSD9WQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:TzckVT8X55k=:ne3gWjCwbKkJv1Nwau5zKC 7ZujEldLboM+FoLvve3e39Mn5pokZH8P+lBcGLtGuBi4ThWq0xrc/CPuOwdVTUvItQRiFCa6r ToAGpASSyLgkjE6O6bnOga2eSlfSPsVcwaXtWLxC7erB/810Mm+NszemNKFWmzcYUphb8/2+N UQ/3r1X1jrRvXIFrbZOkI7Gl8/IpKGtCb62Js5WZqz1vagcdaujxIZsj36tTkVPbTMcYoHSOy /84sq+d9SWa1ZKCbd9m3UWvKYPhuFnpVXIl4PuYaXzlycAcc9VUXPi3VoEDQQVwPlMwkXPv3D DxhW4LQEn7xIAzh2TjjZPKv1kUMHOBY6WQRhntDiKPP+/YBsBWarlYtPYOOSqhokd/8alGuW+ XvmAyz2j+1XhwBU6MRKrbOjnBHgnIq02x2t6riObUqKqmh0yUU9bLF3fJPtslbBADRCk7HfOq rvu+bfyeT/f7nxKmobXHIr1f8L1C0MEPPQqrx/NkfQXHrPfScRL0EozvPUM1De3NJPQKdsamd ivC7xKJoKoDPKQAjSNrEtgyHUtZ4KO26PWzTDZniUcPejz09F8dbwstTMpGLHuEusN+okQFXS 8xKHlU3u/38uaqHQJfCgsVQMXhx0u/R+lo5+mrxPzFsrsvCt2DJ5uGbaYAYKmLVI+cldBt4J2 FTEreZQnamCvgYLQikBxRn3qV00fjUD0JGo73Lm22iTX0KY0f1rZpz9uB3rZ3zF5SgkYn9ZBF E6bpPBZ8xseAfaosXXsCMf7hmXrzuvoApGcRkJgoQGFSizZ1izaho+pd81Xg/i8zI1qSADzXT qrq/lLli4aYr1EfqcZIWwMMAIMj+4P1hSqlEZefYHazhQkZENKJ/BQ2cw7SkiIu/h3D/WOX
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 22:59:25 -0000

This is a multi-part message in MIME format.
--------------A43734BABF57ABD853B8CB63
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

ok .. I did use it.

Now it tells me, that my option is being processed and can take up two 
business days to issue a fee waiver.

blöd ...



Am 27.07.2021 um 00:54 schrieb Carsten Bormann:
> You can use the fee waiver program
>
>> On 2021-07-27, at 00:51, Stefan Gössner  wrote:
>>
>> hmm ... do I need to pay a fee to register ?
>>
>>
>> Am 26.07.2021 um 18:01 schrieb Glyn Normington:
>>> Hi Stefan
>>>
>>> Tonight's meeting is on MeetEcho as part of IETF 111 which requires
>>> you to register (see
>>> https://www.ietf.org/how/meetings/111/
>>> ).
>>>
>>> Once you've registered, click this link to access meetecho:
>>>
>>> https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1
>>>
>>>
>>> Hope you can make it!
>>>
>>> Regards,
>>> Glyn
>>>
>>> On Mon, 26 Jul 2021 at 16:50, Stefan Gössner
>>> 
>>>   wrote:
>>>
>>>> How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
>>>> --
>>>> sg
>>>>
>>>>
>>>> Am 20.07.2021 um 19:50 schrieb Tim Bray:
>>>>
>>>> This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.
>>>>
>>>> We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.
>>>>
>>>> Thanks in advance!
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>


--------------A43734BABF57ABD853B8CB63
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    ok .. I did use it.

        

        Now it tells me, that my option is being processed and can take
        up two business days to issue a fee waiver.

        

        blöd ...

        

        

      

    
Am 27.07.2021 um 00:54 schrieb Carsten
      Bormann:

    

    

      
You can use the fee waiver program



      

        
On 2021-07-27, at 00:51, Stefan Gössner <stefan@goessner.net> wrote:

hmm ... do I need to pay a fee to register ?


Am 26.07.2021 um 18:01 schrieb Glyn Normington:


        

          
Hi Stefan

Tonight's meeting is on MeetEcho as part of IETF 111 which requires
you to register (see 
https://www.ietf.org/how/meetings/111/
).

Once you've registered, click this link to access meetecho:

https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1


Hope you can make it!

Regards,
Glyn

On Mon, 26 Jul 2021 at 16:50, Stefan Gössner 
<stefan@goessner.net>
 wrote:



          

            
How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
--
sg


Am 20.07.2021 um 19:50 schrieb Tim Bray:

This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.

Thanks in advance!



--
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


      

      



    

    

  


--------------A43734BABF57ABD853B8CB63--


From nobody Mon Jul 26 16:02:23 2021
Return-Path: 
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 9C9F43A08D3 for ; Mon, 26 Jul 2021 16:02:21 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 a99L1oYgP0Ut for ; Mon, 26 Jul 2021 16:02:16 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 890B63A08CE for ; Mon, 26 Jul 2021 16:02:16 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id h11so13286765ljo.12 for ; Mon, 26 Jul 2021 16:02:16 -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=HlDs5Nqo/2SnxRwIyAL4bjcXisfogzdIFsXLPTZ5u18=; b=mKaWtj2Ee27Read77vgU8B44Yl604LPEw6qq33anw7iVY41QLTzl1XIAZDY0QXQV5D fRhIRjKc5MTOfZ4S0DYX0lVXAzibkkmaM/gOfK5yAJ+1pW8CB2stj0mvHmACcXGYQOXR 7eczJrKBIsoT0FkXqUysGHjKqWbKJ96YPpwWpFrtHLf6iLwQFEgH9mXiH9DjBTrs2rj9 +CazNgvff/JXUJut2sbr8z2nuWthfuA2C6VmTcFysgbMXaGa/IfZLx8O3bcccaixA5Fc rZELhYwBWabV2fRwnQJXpvhZ7g9U1NpdaQy942XU8WcnijZ8ThQYsroX0MkXSG9CWUeE J3QQ==
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=HlDs5Nqo/2SnxRwIyAL4bjcXisfogzdIFsXLPTZ5u18=; b=USmVOOzAPfSkb+J4mieF8xhw+cYOgjQuTC0oGxPlOMC4yTkiq+K1uPZKq7n1plblON 60ylKKP0h12s1lk15I5VdBnVYcPqbkM7nLbWko2i9gI+IKHl/Uhpu5ALGBM2kdzXEAq6 9txyhk1IRhI158b9XOCJv2yhp9Eqa1iiOH7RvtJRS6A8iegO9XOa0jY+V70WVlvvsGMx 8r0JdIf/Te2B8SMQH3670IRb1InnJOszgfhXbWB/SG3VckJ+DGUohmhULkm7w/XfYCsc RZbYFzgqJYFST5Ps1bW42JqPFIjZ/x8hotIGed3XdRh4sBQKUB3w2iFPnQgwYUc5gd9P FjUA==
X-Gm-Message-State: AOAM530r4y9QUBgUD13aHCwYrCmdmMBQsLhVh4eqr+t5O62jdW6WTMEp tvridOgYvqMIswnlCa1op+b327HqswJWmPlMw0QlUaWU5cCVAQ==
X-Google-Smtp-Source: ABdhPJy1iLvfIgTRg4otRug1EYSyBxePqm0o2OB74zjce5mHECAZuNwAaUScoKZe68RRvf4Kj6kdJ1csffmaUkLvnWg=
X-Received: by 2002:a2e:88d2:: with SMTP id a18mr10307826ljk.143.1627340533419;  Mon, 26 Jul 2021 16:02:13 -0700 (PDT)
MIME-Version: 1.0
References:  <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net>  <2087b888-d908-ef8f-cd94-6c2b04d69bd2@goessner.net> <7EA7418C-E0C9-4406-B6F3-85DA8A3A2779@tzi.org> <09331691-f236-6ee2-2596-02e404305a23@goessner.net>
In-Reply-To: <09331691-f236-6ee2-2596-02e404305a23@goessner.net>
From: Tim Bray 
Date: Mon, 26 Jul 2021 16:02:02 -0700
Message-ID: 
To: =?UTF-8?Q?Stefan_G=C3=B6ssner?= 
Cc: Carsten Bormann , Glyn Normington , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006c654505c80ebec5"
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 23:02:22 -0000

--0000000000006c654505c80ebec5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Alternately, you could pay, and deduct it as a business expense. IETF is a
good cause.

On Mon, Jul 26, 2021 at 3:58 PM Stefan G=C3=B6ssner  w=
rote:

> ok .. I did use it.
>
> Now it tells me, that my option is being processed and can take up two
> business days to issue a fee waiver.
>
> bl=C3=B6d ...
>
>
>
> Am 27.07.2021 um 00:54 schrieb Carsten Bormann:
>
> You can use the fee waiver program
>
>
> On 2021-07-27, at 00:51, Stefan G=C3=B6ssner   wrote:
>
> hmm ... do I need to pay a fee to register ?
>
>
> Am 26.07.2021 um 18:01 schrieb Glyn Normington:
>
> Hi Stefan
>
> Tonight's meeting is on MeetEcho as part of IETF 111 which requires
> you to register (see https://www.ietf.org/how/meetings/111/
> ).
>
> Once you've registered, click this link to access meetecho:
> https://meetings.conf.meetecho.com/ietf111/?group=3Djsonpath&short=3D&ite=
m=3D1
>
>
> Hope you can make it!
>
> Regards,
> Glyn
>
> On Mon, 26 Jul 2021 at 16:50, Stefan G=C3=B6ssner  <=
stefan@goessner.net>
>  wrote:
>
>
> How will it be possible to attend the meeting tonight ... technically ?  =
WebEx or something ?
> --
> sg
>
>
> Am 20.07.2021 um 19:50 schrieb Tim Bray:
>
> This is happening next Monday at 4PM Pacific time, which means in the mid=
dle of the night for the bulk of our EuroPeople; sorry about that.
>
> We have a good track record of settling issues at our meetings and interi=
ms so far, so I'm optimistic we can succeed again.  This would be a good ti=
me for WG participants to suggest issues they think are near the front of t=
he queue.
>
> Thanks in advance!
>
>
>
> --
> Jsonpath mailing list
> Jsonpath@ietf.orghttps://www.ietf.org/mailman/listinfo/jsonpath
>
> --
> Jsonpath mailing listJsonpath@ietf.orghttps://www.ietf.org/mailman/listin=
fo/jsonpath
>
>
>

--0000000000006c654505c80ebec5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Alt=
ernately, you could pay, and deduct it as a business expense. IETF is a goo=
d cause.

On Mon, Jul 26, 2021 at 3:58 PM Stefan G=C3=B6ssner <stefan@goessner.net> wrote:
<=
/div>

 =20
   =20
 =20
  

    ok .. I did use it.

        

        Now it tells me, that my option is being processed and can take
        up two business days to issue a fee waiver.

        

        bl=C3=B6d ...

        

        

      

    
Am 27.07.2021 um 00:54 schrieb Carsten
      Bormann:

    

    

      
You can use the fee waiver program



      

        
On 2021-07-27, at 00:51, Stefan G=C3=B6ssner <stefan@goessner.net> wro=
te:

hmm ... do I need to pay a fee to register ?


Am 26.07.2021 um 18:01 schrieb Glyn Normington:


        

          
Hi Stefan

Tonight's meeting is on MeetEcho as part of IETF 111 which requires
you to register (see=20
https:=
//www.ietf.org/how/meetings/111/
).

Once you've registered, click this link to access meetecho:

https://meetings.conf.meetecho.co=
m/ietf111/?group=3Djsonpath&short=3D&item=3D1


Hope you can make it!

Regards,
Glyn

On Mon, 26 Jul 2021 at 16:50, Stefan G=C3=B6ssner=20
<stefan@goessne=
r.net>
 wrote:



          

            
How will it be possible to attend the meeting tonight ... =
technically ?  WebEx or something ?
--
sg


Am 20.07.2021 um 19:50 schrieb Tim Bray:

This is happening next Monday at 4PM Pacific time, which means in the middl=
e of the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settling issues at our meetings and interims=
 so far, so I'm optimistic we can succeed again.  This would be a good =
time for WG participants to suggest issues they think are near the front of=
 the queue.

Thanks in advance!



--
Jsonpath mailing list

Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath


          

        

        
--=20
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath


      

      

    

    

  





--0000000000006c654505c80ebec5--


From nobody Mon Jul 26 16:03:07 2021
Return-Path: 
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 23BA73A08DC for ; Mon, 26 Jul 2021 16:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 GK-lT128TvS5 for ; Mon, 26 Jul 2021 16:02:59 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 6D5F93A08DA for ; Mon, 26 Jul 2021 16:02:59 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id m13so18349957lfg.13 for ; Mon, 26 Jul 2021 16:02:59 -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=HkpGAHWN0YbqY632ipPVY3qyPZUT8yFfErbrPGL5vAQ=; b=t67BBnXnmJ0Xcd+kQpeF8MEaAu44ie4cXHAQDcoymJt5DVr1/e7TsAPlK4/f23bdSb 3UE5GuWd8sxwLRK0fzidFjRu/Zx6xRo0uhJ8Aseb+HRvp/r1RSizc4/Veij0OrabCFDa JEFHOxK+b/RpTIMpT1ZZ+UJRCj1OM0uImqTB1DHZs04D3aRZGRUJ9Tr5FSYoITy3oSar BRdBPHTZCkwXVkzV5s5y0czhzYajN63w+Su1gWqatQOW6qq09yyfjDy0lIb4fideRc0o yrv8tjDf3qBAmuY+9Y3N9YBUdhVH4mgJqWSEcl9C2yzRj8SyYJ3m7qRTr2oT3Eo1wEH6 6ESw==
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=HkpGAHWN0YbqY632ipPVY3qyPZUT8yFfErbrPGL5vAQ=; b=qO8ZbaHy67Iu+Kb07Gw01pI0TPetrHOq1wYU3MhtZr9wMbyB/tLqcStEP6CVvLSF5+ 1fB1+sK04vb53lF4Xfulvu+t0XPe+iYnx6iV8a/RhBXVl3GU2xh3V4dKMvOaGfV/2hGK iok83PxTYQzfaZcnLEK/Oy2okE2mdIE3pIYtYplNDMpz2eBJwoOV2LaGixcC8HU+YTzz 3fSU8/TXjMLz/8CzYm5u+7yGSGnPm0dlO0cciggr3Z+Tw3xO3mwyewNETO+mRy+jiTPE uSgEi5Kr/zq8nVqh5/ofC/buROV8t+g8ocO0lH3M3qJvs9FHYgaHU25EeOkH4V2gkgau ZYAg==
X-Gm-Message-State: AOAM531PX7abZzoTUGhiaJIzjHNWMvGFceLT9KErToER1Xsx1NcXu6/c 4YbqOX42jjoSTR2O53bMDX3dD5pyTVnlqZ5Hvptp5g==
X-Google-Smtp-Source: ABdhPJxypFUrFo9fqon+cwWFX4HEDEhEZlNp2DwVguoDCnDsc3a0EXEFV1EpYUAhueNtZPno8dY7noN49TYdJ5FKAkY=
X-Received: by 2002:ac2:5bcb:: with SMTP id u11mr14808722lfn.136.1627340575610;  Mon, 26 Jul 2021 16:02:55 -0700 (PDT)
MIME-Version: 1.0
References:  <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net>  <2087b888-d908-ef8f-cd94-6c2b04d69bd2@goessner.net> <7EA7418C-E0C9-4406-B6F3-85DA8A3A2779@tzi.org> <09331691-f236-6ee2-2596-02e404305a23@goessner.net> 
In-Reply-To: 
From: Tim Bray 
Date: Mon, 26 Jul 2021 16:02:44 -0700
Message-ID: 
To: =?UTF-8?Q?Stefan_G=C3=B6ssner?= 
Cc: Carsten Bormann , Glyn Normington , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f02f5305c80ec028"
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 23:03:05 -0000

--000000000000f02f5305c80ec028
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

But probably don't, because we have very poor turn-out and may not have a
meeting.

On Mon, Jul 26, 2021 at 4:02 PM Tim Bray  wrote:

> Alternately, you could pay, and deduct it as a business expense. IETF is =
a
> good cause.
>
> On Mon, Jul 26, 2021 at 3:58 PM Stefan G=C3=B6ssner 
> wrote:
>
>> ok .. I did use it.
>>
>> Now it tells me, that my option is being processed and can take up two
>> business days to issue a fee waiver.
>>
>> bl=C3=B6d ...
>>
>>
>>
>> Am 27.07.2021 um 00:54 schrieb Carsten Bormann:
>>
>> You can use the fee waiver program
>>
>>
>> On 2021-07-27, at 00:51, Stefan G=C3=B6ssner   wrote:
>>
>> hmm ... do I need to pay a fee to register ?
>>
>>
>> Am 26.07.2021 um 18:01 schrieb Glyn Normington:
>>
>> Hi Stefan
>>
>> Tonight's meeting is on MeetEcho as part of IETF 111 which requires
>> you to register (see https://www.ietf.org/how/meetings/111/
>> ).
>>
>> Once you've registered, click this link to access meetecho:
>> https://meetings.conf.meetecho.com/ietf111/?group=3Djsonpath&short=3D&it=
em=3D1
>>
>>
>> Hope you can make it!
>>
>> Regards,
>> Glyn
>>
>> On Mon, 26 Jul 2021 at 16:50, Stefan G=C3=B6ssner  =

>>  wrote:
>>
>>
>> How will it be possible to attend the meeting tonight ... technically ? =
 WebEx or something ?
>> --
>> sg
>>
>>
>> Am 20.07.2021 um 19:50 schrieb Tim Bray:
>>
>> This is happening next Monday at 4PM Pacific time, which means in the mi=
ddle of the night for the bulk of our EuroPeople; sorry about that.
>>
>> We have a good track record of settling issues at our meetings and inter=
ims so far, so I'm optimistic we can succeed again.  This would be a good t=
ime for WG participants to suggest issues they think are near the front of =
the queue.
>>
>> Thanks in advance!
>>
>>
>>
>> --
>> Jsonpath mailing list
>> Jsonpath@ietf.orghttps://www.ietf.org/mailman/listinfo/jsonpath
>>
>> --
>> Jsonpath mailing listJsonpath@ietf.orghttps://www.ietf.org/mailman/listi=
nfo/jsonpath
>>
>>
>>

--000000000000f02f5305c80ec028
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


But=
 probably don't, because we have very poor turn-out and may not have a =
meeting.

On Mon, Jul 26, 2021 at 4:02 PM Tim Bray <tbray@textuality.com> wrote:
Alternately, you could pay, and deduct it as a business expense. =
IETF is a good cause.

On Mon, Jul 26, 2021 at 3:58 PM Stefan G=C3=B6ss=
ner <stefan@goe=
ssner.net> wrote:

 =20
   =20
 =20
  

    ok .. I did use it.

        

        Now it tells me, that my option is being processed and can take
        up two business days to issue a fee waiver.

        

        bl=C3=B6d ...

        

        

      

    
Am 27.07.2021 um 00:54 schrieb Carsten
      Bormann:

    

    

      
You can use the fee waiver program



      

        
On 2021-07-27, at 00:51, Stefan G=C3=B6ssner <stefan@goessner.net> wro=
te:

hmm ... do I need to pay a fee to register ?


Am 26.07.2021 um 18:01 schrieb Glyn Normington:


        

          
Hi Stefan

Tonight's meeting is on MeetEcho as part of IETF 111 which requires
you to register (see=20
https:=
//www.ietf.org/how/meetings/111/
).

Once you've registered, click this link to access meetecho:

https://meetings.conf.meetecho.co=
m/ietf111/?group=3Djsonpath&short=3D&item=3D1


Hope you can make it!

Regards,
Glyn

On Mon, 26 Jul 2021 at 16:50, Stefan G=C3=B6ssner=20
<stefan@goessne=
r.net>
 wrote:



          

            
How will it be possible to attend the meeting tonight ... =
technically ?  WebEx or something ?
--
sg


Am 20.07.2021 um 19:50 schrieb Tim Bray:

This is happening next Monday at 4PM Pacific time, which means in the middl=
e of the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settling issues at our meetings and interims=
 so far, so I'm optimistic we can succeed again.  This would be a good =
time for WG participants to suggest issues they think are near the front of=
 the queue.

Thanks in advance!



--
Jsonpath mailing list

Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath


          

        

        
--=20
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath


      

      

    

    

  







--000000000000f02f5305c80ec028--


From nobody Mon Jul 26 16:15:26 2021
Return-Path: 
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 C80093A09AD for ; Mon, 26 Jul 2021 16:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 499Du3mpaYvd for ; Mon, 26 Jul 2021 16:15:19 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2A4A3A09A8 for ; Mon, 26 Jul 2021 16:15:18 -0700 (PDT)
Received: from [192.168.178.20] ([88.130.51.150]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPSA (Nemesis) id 1N8GIa-1l4HTF3xCq-014AHc; Tue, 27 Jul 2021 01:15:06 +0200
To: Tim Bray 
Cc: jsonpath@ietf.org, Glyn Normington , Carsten Bormann 
References:  <5557ca41-312a-dfc4-1eff-ff78604251ae@goessner.net>  <2087b888-d908-ef8f-cd94-6c2b04d69bd2@goessner.net> <7EA7418C-E0C9-4406-B6F3-85DA8A3A2779@tzi.org> <09331691-f236-6ee2-2596-02e404305a23@goessner.net>  
From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= 
Message-ID: 
Date: Tue, 27 Jul 2021 01:15:05 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: 
Content-Type: multipart/alternative; boundary="------------BB84842289465375757723F0"
X-Provags-ID: V03:K1:wI7uMxR4p+V28sRWxKH0+z2Pzpyq9NSI56XnJVcASYBTnJwhrFe NSKQeieEfYsXF2+sQ6vMnkUO61JASIUEzeWxdIU60df4dxI89Wd9XwnrNL6Sc/y6nOQ+usw nfu87FiYEp49cM/O+UPITOUaTBsQy40urjdAV+VAbr0PxmZpa9MKHF5XFCXkk2lXaW0hs/C AkCy9eAu7vV7gzQPeOfkw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:ojjYU0YLZgE=:dqT0aGsWghyEZF7B5y++LJ T/nsD7SkCPHghqji2vEgfxn459mCWhETps32fN1Wj5VHfoMdUQ3cB/aqoIUh3w8J7V10ucn0w juyo7Btwa6NbNzoO9kYYb8Q7ODlVTqW0OwIA2J0VRc9wyLYhRiyuyRwfvBk7Fse55FeC+s+/9 FQW2T7v/6/NC91JCpUzZA+UY6k3fDbyE6wm48VLzEs3ot4uKFoM+itTDKiO9eMRIkuWKE1oTO 2YKserblfOSeew3hsmIiHsdnlVsLRzBtzuSFTWNexpTrMebLFNQflTVKrEL5VpY8D5nx/82X8 kCnpuzw/iig4R07KVo/n5vvfOCYeGDg1zN7BFCWzRC+Va+XqywH2UEY03jDSIIT5styizWkxx qzRxjQ5nAFjF2eWps0eaw38tn+yf9nOqwSNLn59dKs9mWc5tHwU3430NKnAoa6Nds3XvzU9ik VYFyLx9eDgz85FtJhvDv1oNYLGJO9stPBK9aD6AcEj4u1WS/73xrDoh8WFDtffB9nlj2bOD5P k1EYk7MklC6p0OWNIdPlKT/W0XAZbUUw6mjDT4MxpDp7Q8vbv8zGdlNKbdq62OEKXrbDB8yv5 M2f8xjFZ8JCsgwWfrcAGrgTn4nhWFCHuvj3wAgDghcb9AcvzNvVo3dfjLFIiPPK2EdusxgGZv +XUjRhtYzkwY6Y00fPf5QUG/3mlARdvH22zC+G2k+a0OvjUrdg3eRfaf3tN6ADMgV+M0wn6qn YXKh2XiARXggZileY2lyWaqahN0EP5oNrEHaZcCih0YMccLZ6xks+TsE7wIkr5yCECi+PMtUV eOeif1E4vjzWMs7xmOa3jLYzyqvvDR91tok/c4I37NxLtx6PblbTesAut3xyYZG37Up7ssl
Archived-At: 
Subject: Re: [Jsonpath] JSONPath meeting at IETF 111
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Mon, 26 Jul 2021 23:15:25 -0000

This is a multi-part message in MIME format.
--------------BB84842289465375757723F0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Well I got an answer ... see below.

Now I need to pay 2 USD, regardless of the coupon, which I would do 
(need to choose a payment method), if you tell me that we will meet.

--
stefan

Thank you for taking the fee waiver option for IETF 111. Please feel 
free to register for IETF 111 with the following link:
https://registration.ietf.org/ 

After registering, on the final payment page there will be a box under 
the final total where you can apply the following coupon code to cover 
your registration:

w6jsGIgp

If you have any questions, please do not hesitate to contact me.Regards,

Jasmine Magallanes, CMP
Project Manager





Am 27.07.2021 um 01:02 schrieb Tim Bray:
> But probably don't, because we have very poor turn-out and may not 
> have a meeting.
>
> On Mon, Jul 26, 2021 at 4:02 PM Tim Bray  > wrote:
>
>     Alternately, you could pay, and deduct it as a business expense.
>     IETF is a good cause.
>
>     On Mon, Jul 26, 2021 at 3:58 PM Stefan Gössner
>     > wrote:
>
>         ok .. I did use it.
>
>         Now it tells me, that my option is being processed and can
>         take up two business days to issue a fee waiver.
>
>         blöd ...
>
>
>
>         Am 27.07.2021 um 00:54 schrieb Carsten Bormann:
>>         You can use the fee waiver program
>>
>>>         On 2021-07-27, at 00:51, Stefan Gössner    wrote:
>>>
>>>         hmm ... do I need to pay a fee to register ?
>>>
>>>
>>>         Am 26.07.2021 um 18:01 schrieb Glyn Normington:
>>>>         Hi Stefan
>>>>
>>>>         Tonight's meeting is on MeetEcho as part of IETF 111 which requires
>>>>         you to register (see
>>>>         https://www.ietf.org/how/meetings/111/  
>>>>         ).
>>>>
>>>>         Once you've registered, click this link to access meetecho:
>>>>
>>>>         https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1  
>>>>
>>>>
>>>>         Hope you can make it!
>>>>
>>>>         Regards,
>>>>         Glyn
>>>>
>>>>         On Mon, 26 Jul 2021 at 16:50, Stefan Gössner
>>>>           
>>>>           wrote:
>>>>
>>>>>         How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
>>>>>         --
>>>>>         sg
>>>>>
>>>>>
>>>>>         Am 20.07.2021 um 19:50 schrieb Tim Bray:
>>>>>
>>>>>         This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.
>>>>>
>>>>>         We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.
>>>>>
>>>>>         Thanks in advance!
>>>>>
>>>>>
>>>>>
>>>>>         --
>>>>>         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  
>
>
>  
> 	Virenfrei. www.avg.com 
>  
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


--------------BB84842289465375757723F0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    Well I got an answer ...
        see below.

        

        Now I need to pay 2 USD, regardless of the coupon, which I would
        do (need to choose a payment method), if you tell me that we
        will meet. 

        

        --

        stefan

        

      

Thank you for taking the fee waiver option for IETF 111. Please feel free to register for IETF 111 with the following link:
    
    

    
    
After registering, on the final payment page there will be a box under the final total where you can apply the following coupon code to cover your registration:

    
      


      

      

        
w6jsGIgp

        


          

      

    If you have any questions, please do not hesitate to contact me.
Regards,

    

    Jasmine Magallanes, CMP

    Project Manager
    


      

      

      

      

      Am 27.07.2021 um 01:02 schrieb Tim Bray:

    

    

      
      

        
But probably
          don't, because we have very poor turn-out and may not have a
          meeting.

      

      

      

        
On Mon, Jul 26, 2021 at 4:02
          PM Tim Bray <tbray@textuality.com> wrote:

        

        

          

            
Alternately,
              you could pay, and deduct it as a business expense. IETF
              is a good cause.

          

          

          

            
On Mon, Jul 26, 2021 at
              3:58 PM Stefan Gössner <stefan@goessner.net>
              wrote:

            

            

              
 ok .. I
                    did use it.

                    

                    Now it tells me, that my option is being processed
                    and can take up two business days to issue a fee
                    waiver.

                    

                    blöd ...

                    

                    

                  

                
Am 27.07.2021 um 00:54 schrieb Carsten Bormann:

                

                

                  
You can use the fee waiver program



                  

                    
On 2021-07-27, at 00:51, Stefan Gössner <stefan@goessner.net> wrote:

hmm ... do I need to pay a fee to register ?


Am 26.07.2021 um 18:01 schrieb Glyn Normington:


                    

                      
Hi Stefan

Tonight's meeting is on MeetEcho as part of IETF 111 which requires
you to register (see 
https://www.ietf.org/how/meetings/111/
).

Once you've registered, click this link to access meetecho:

https://meetings.conf.meetecho.com/ietf111/?group=jsonpath&short=&item=1


Hope you can make it!

Regards,
Glyn

On Mon, 26 Jul 2021 at 16:50, Stefan Gössner 
<stefan@goessner.net>
 wrote:



                      

                        
How will it be possible to attend the meeting tonight ... technically ?  WebEx or something ?
--
sg


Am 20.07.2021 um 19:50 schrieb Tim Bray:

This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.

We have a good track record of settling issues at our meetings and interims so far, so I'm optimistic we can succeed again.  This would be a good time for WG participants to suggest issues they think are near the front of the queue.

Thanks in advance!



--
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


                  

                

                

              

            

          

        

      

      


        

          
            

              
              Virenfrei. www.avg.com 
            

          
        

         

      

      

    

    

  


--------------BB84842289465375757723F0--


From nobody Tue Jul 27 00:01:20 2021
Return-Path: 
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 0D7723A19BB for ; Tue, 27 Jul 2021 00:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=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=gmail.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 q0kJlDXpxMhd for ; Tue, 27 Jul 2021 00:01:13 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 6656B3A19C1 for ; Tue, 27 Jul 2021 00:01:13 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id c11so14643637plg.11 for ; Tue, 27 Jul 2021 00:01:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=nRoJU44A6IkScT5mB6GREyOxOKZe5LkUoNjQ6gG5TpM=; b=GZHp6rFK3erlIf5SscsKIWUWku/Oi8ZqlW643GbzKrHC0iVD9+mIYMV/9BHHm5DoyA ErqlztB9VM/quGBxkueGdB+QqVagbZfdMqI7gobZnhGVEE64b305YtUO+gDKoTTF2ZNz hCIcwnRjt8uhLmNoYDNs0lZ6/HA/RGTXoZk4qB91C5gEFy/gI/Vmt1gRoNdxW6lEbmNV mLplr5BJkRJIBHbaPyDp8yYHJtOnhBrAEZA34De1MtAtcZqqJUiDHBkcQUq8AQfDFVLH fJWL/EpWe9r8AOj713xq8U9SDLhkkSY0SThcnZAnhZphjZOhgJOLqQtL8vKu9HgnScYB +Y9g==
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:content-transfer-encoding; bh=nRoJU44A6IkScT5mB6GREyOxOKZe5LkUoNjQ6gG5TpM=; b=c63W1WllMoil4/CuoGBmJxWEdbCQLvnD5claQjYE0hW50nyl5jaZXgk7IH8enGkwOi JttypDdR1NHBTcW3+nBk2px8NBPt5cWjD+JyyTKKKJ9SsfGaMOdMtaCqODivdy0xjevp XA+pMxyjb+oEH6iSNuQ6c/0QLICN56KTSWW46jLbEUCh90tB5FAYb/fu7tJtwgm3Mq6p pV/uSN2pgAB+ZM3O5HhymBuOcYbdkBZuKhuUmxv12vPuNUe/Zpvas7YJJki36Kr2Tt8G /HuHsKFxadcOzHEJDDYbKT8OPcX2PQJj7GMDgQaPh41+CkLWs3OJBkhVXEaPwb/IYOWw b78A==
X-Gm-Message-State: AOAM532UkUP6j86Tb5IfjaT/aJ5B1umS+zs7GFYMFzqXnyPWmQzNv71v t/CSg+wyGDVMipcCQBZgC6eFVTA6+g9xTwJVp/o=
X-Google-Smtp-Source: ABdhPJznSQGoh/kQ76s16CudpzwfTM7+8VZQ0ol4KV0+zi/xJ+xkvqjE4TpsaKyPH27kdw/pfZ/Mu5vfmd3waPLyCzo=
X-Received: by 2002:a17:90b:1d0a:: with SMTP id on10mr2782189pjb.132.1627369272115;  Tue, 27 Jul 2021 00:01:12 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>
In-Reply-To: <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>
From: Glyn Normington 
Date: Tue, 27 Jul 2021 08:01:00 +0100
Message-ID: 
To: Carsten Bormann 
Cc: jsonpath@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 07:01:18 -0000

My aim was to require iregexp for interoperability, but allow
alternate regexp implementations with potentially degraded
interoperability.

Could we achieve something similar using compliance
levels/modules/features? For example, could an implementer add (to the
regexp-free subset) an alternative regexp module/feature for their
preferred (non-compliant) regexp implementation?

I guess the semantics would be that JSONPath implementations which use
interoperable regexp implementations will interoperate. So, for
example, JSONPath/iregexp implementations would interoperate with each
other as would JSONPath/RE2 implementations. But, for any regexp
implementations x and y, JSONPath/x would only interoperate with
JSONPath/y to the extent that x and y interoperate.

I quite like that this approach separates regexp interoperation from
the JSONPath spec and makes it a matter for regexp.

On Mon, 26 Jul 2021 at 17:10, Carsten Bormann  wrote:
>
> In the discussion of
> https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103, =
it became apparent that we weren=E2=80=99t quite sure what levels of compli=
ance language we should be using.  Particularly, I would think that a SHOUL=
D is not very useful except when discussing corner cases (or non-functional=
 requirements like =E2=80=9CSHOULD NOT blow up=E2=80=9D).
>
> So are we ready to have multiple compliance levels?
> A core set to which we expect everyone to comply and set of modules/featu=
res that can be added to the compliance?  No regular expressions in the cor=
e but an optional compliance module/feature for iregexps?
>
> I don=E2=80=99t want to overthink that and propose a complicated set of m=
odules where a single monolithic core would be sufficient, but stumbling in=
to these modules without having planned for them is probably also not a goo=
d idea.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>
> > On 2021-07-24, at 17:18, Carsten Bormann  wrote:
> >
> > On 2021-07-20, at 19:50, Tim Bray  wrote:
> >>
> >> This is happening next Monday at 4PM Pacific time, which means in the =
middle of the night for the bulk of our EuroPeople; sorry about that.
> >
> > Apparently I didn=E2=80=99t pay enough attention, since I only just not=
iced that I have a conflict with IOTOPS in that slot.
> >
> > I think we need to have a slightly more frequent interim cadence.
> >
> > Gr=C3=BC=C3=9Fe, Carsten
> >
> > --
> > 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


From nobody Tue Jul 27 00:35:49 2021
Return-Path: 
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 F2ED53A23D2 for ; Tue, 27 Jul 2021 00:35:47 -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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 KuUFqTOuArHm for ; Tue, 27 Jul 2021 00:35:43 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDE8B3A23CA for ; Tue, 27 Jul 2021 00:35:42 -0700 (PDT)
Received: from [192.168.178.20] ([88.130.51.231]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MlsWZ-1lPHpw3BEh-00j29W; Tue, 27 Jul 2021 09:35:31 +0200
To: Glyn Normington , Carsten Bormann 
Cc: jsonpath@ietf.org
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org> 
From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= 
Message-ID: <914510be-1526-8bb4-458d-0ea6790ae57f@goessner.net>
Date: Tue, 27 Jul 2021 09:35:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: 
Content-Type: multipart/alternative; boundary="------------48C9D9C93E304D4A464B81FF"
X-Provags-ID: V03:K1:9bS6oRI3/SgsrPV4FpV36EQIa+NLeV4TS56HQlim3UBclETeYPM RTMu6AJ5k1iastRvCxgzBNDZp7mj8UGahA1c8Z89CcYYZRgSX6KtEzheAhQXZVCTJayPFTc 4bYYNqvuyzGfACHCWqQpVpaOcB3SoJZUR8+07U24yojP5ihOa/VGC3R58+pitsIUckExHuG sq0f5jKCZdDQdrKTEXqLw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:jByA+wbiGlA=:SckZTZ3olnAk21+KiXLZ8Y Q9NM6onkQ09bRKPQmk2QyDXEGncqguCKHu0CFzoqBmmLUJjv2rJFs0cRRaanmQKR3ZxZDEEN3 A0qu4w3ZUN6ShMhtTm37fCPyvuNSGH44nd+5CSWHSwfesxzxqBEJRIFjgmOKRu8pQeFLdChEu Ml9Ox4ju4LrDyK/9Evs0N+dTt8ft5Yvs/6nPM9Hr7uXeCLd2LEGvoKfjA6bO4C0VcDBzN2YBE sq1X4/u0LTo0RRsvVrobcGyT8i9dqQJaE4LOGC02aTI60pvDnRkjt6kx5ET8xusNecWxdrhiA LKXnOv6bJeRabOSB0pZNe33U4zk8sEq0eRbSzuZj/2N1KjEIB16TOAqe/siTtJf0wPDrV39Em d6W6BZ0ipUnRoMw6Q83YkWakKzFObYKvkZRrqTWjRJolpF7rl8MTNy3LZvV/YNWFFIdU81z+h YvOkG0YWg4y5PizMXuIk8issrlpWC00VQTaeeY/AK2Gm6JaomVrRjuV8QKSE0JGw1XkwTOKYB Isw5/z+ZTlrNmLfaT8hMpNQ3+UjEm1ABxclgbOYMSf9TYv72lI8aFPgEKh3yccrgPRhvz+pqt HlIRuQgJntysbLLuTuELC9raU2mACfQY6WdeD+NH2KSvkc1Kx6cm9wGqFZzQzHH/BQB32LAW1 Pd3OVJb3xNBHNvXzpDi0JumZ45zgKRCnPO8L9p0jFFiYwAlHynXCu0Q4vRgJMeYAK7FQAZUw5 WcbkH9IUjf+L4MUonQ3OLUqsgzeFvnl0Rp9lpLDDLb3cdP2cFtb38TZ8SBdaFwVlfRiKBBpgd +SHmG48SJKNHQnCnXG0OnMz2uE2xM161h8NnU0Qw0cbENuxwZjqqJu9YQxneLlW45qXxayrrq cKVZ+L6sLPpoA2NWrLHw==
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 07:35:48 -0000

This is a multi-part message in MIME format.
--------------48C9D9C93E304D4A464B81FF
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

I also like that concept of separation of regexp (features) from JSONPath spec.


Am 27.07.2021 um 09:01 schrieb Glyn Normington:
> My aim was to require iregexp for interoperability, but allow
> alternate regexp implementations with potentially degraded
> interoperability.
>
> Could we achieve something similar using compliance
> levels/modules/features? For example, could an implementer add (to the
> regexp-free subset) an alternative regexp module/feature for their
> preferred (non-compliant) regexp implementation?
>
> I guess the semantics would be that JSONPath implementations which use
> interoperable regexp implementations will interoperate. So, for
> example, JSONPath/iregexp implementations would interoperate with each
> other as would JSONPath/RE2 implementations. But, for any regexp
> implementations x and y, JSONPath/x would only interoperate with
> JSONPath/y to the extent that x and y interoperate.
>
> I quite like that this approach separates regexp interoperation from
> the JSONPath spec and makes it a matter for regexp.
>
> On Mon, 26 Jul 2021 at 17:10, Carsten Bormann  wrote:
>> In the discussion of
>> https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103, it became apparent that we weren’t quite sure what levels of compliance language we should be using.  Particularly, I would think that a SHOULD is not very useful except when discussing corner cases (or non-functional requirements like “SHOULD NOT blow up”).
>>
>> So are we ready to have multiple compliance levels?
>> A core set to which we expect everyone to comply and set of modules/features that can be added to the compliance?  No regular expressions in the core but an optional compliance module/feature for iregexps?
>>
>> I don’t want to overthink that and propose a complicated set of modules where a single monolithic core would be sufficient, but stumbling into these modules without having planned for them is probably also not a good idea.
>>
>> Grüße, Carsten
>>
>>
>>> On 2021-07-24, at 17:18, Carsten Bormann  wrote:
>>>
>>> On 2021-07-20, at 19:50, Tim Bray  wrote:
>>>> This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.
>>> Apparently I didn’t pay enough attention, since I only just noticed that I have a conflict with IOTOPS in that slot.
>>>
>>> I think we need to have a slightly more frequent interim cadence.
>>>
>>> Grüße, Carsten
>>>
>>> --
>>> 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


--------------48C9D9C93E304D4A464B81FF
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    
I also like that concept of separation of regexp (features) from JSONPath spec.


    

    
Am 27.07.2021 um 09:01 schrieb Glyn
      Normington:

    

    

      
My aim was to require iregexp for interoperability, but allow
alternate regexp implementations with potentially degraded
interoperability.

Could we achieve something similar using compliance
levels/modules/features? For example, could an implementer add (to the
regexp-free subset) an alternative regexp module/feature for their
preferred (non-compliant) regexp implementation?

I guess the semantics would be that JSONPath implementations which use
interoperable regexp implementations will interoperate. So, for
example, JSONPath/iregexp implementations would interoperate with each
other as would JSONPath/RE2 implementations. But, for any regexp
implementations x and y, JSONPath/x would only interoperate with
JSONPath/y to the extent that x and y interoperate.

I quite like that this approach separates regexp interoperation from
the JSONPath spec and makes it a matter for regexp.

On Mon, 26 Jul 2021 at 17:10, Carsten Bormann <cabo@tzi.org> wrote:


      

        
In the discussion of
https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103, it became apparent that we weren’t quite sure what levels of compliance language we should be using.  Particularly, I would think that a SHOULD is not very useful except when discussing corner cases (or non-functional requirements like “SHOULD NOT blow up”).

So are we ready to have multiple compliance levels?
A core set to which we expect everyone to comply and set of modules/features that can be added to the compliance?  No regular expressions in the core but an optional compliance module/feature for iregexps?

I don’t want to overthink that and propose a complicated set of modules where a single monolithic core would be sufficient, but stumbling into these modules without having planned for them is probably also not a good idea.

Grüße, Carsten




        

          
On 2021-07-24, at 17:18, Carsten Bormann <cabo@tzi.org> wrote:

On 2021-07-20, at 19:50, Tim Bray <tbray@textuality.com> wrote:


          

            
This is happening next Monday at 4PM Pacific time, which means in the middle of the night for the bulk of our EuroPeople; sorry about that.


          

          
Apparently I didn’t pay enough attention, since I only just noticed that I have a conflict with IOTOPS in that slot.

I think we need to have a slightly more frequent interim cadence.

Grüße, Carsten

--
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


      

      

    

    

  


--------------48C9D9C93E304D4A464B81FF--


From nobody Tue Jul 27 00:43:24 2021
Return-Path: 
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 0A0AF3A0B6C for ; Tue, 27 Jul 2021 00:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=yahoo.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 vfdiIJkuHX9k for ; Tue, 27 Jul 2021 00:43:17 -0700 (PDT)
Received: from sonic312-22.consmr.mail.bf2.yahoo.com (sonic312-22.consmr.mail.bf2.yahoo.com [74.6.128.84]) (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 18A893A0B63 for ; Tue, 27 Jul 2021 00:43:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1627371794; bh=BjVp1lq8FwB/u/o6UuSsvS96Ok0EJ6nNTXEIAwoOdCA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=OozP0C8ubiExUOqKx1qMd32xwe+CKxZd92oHp8FKFJiesUDnRkWeyeanxRSArQrNuwdgSmuGkMJ30MyE22oPYSdElvvtd2TCNWoyiVp/bXQ+/70TpNfLdTeinqX7rqePnxtsrxL+dUQDLRlhyxTRNS53gu1bnlXc4TPmyMaNqfjH2njCbA4QKayrkOC4Uep40hsMkzUQAN67R1NJ46hsZxaLbDidep50IVob+m6eE0QWslpIDJxRcmH1rolZxwULMvqscdnsVEgpD8b3ftj2XV1fl8kYsH9cl/r01r5fWs2QdEW1p6hlcV0HtzCs+p2pdPiumzc0V2HLmRjVVtU7cg==
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;  t=1627371794; bh=cVduoIYomEaPCqZ1jyZnF3SOC6EkrjiRZcUtQBNF/Fi=;  h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=QHPelOgyYiEJ66NJxtAGUnvd1pB6sfZLOa5m1yI/acUhQt6Aj5/TdIs06EOe4U0HWP9Xl6wr6aOTb2W9DMjk2pmMEhVuu3O/R/bORWhrMdRxOhelPKnj/grQ4MDBFgJDxOMZDjOr3RS+wP4xXhHeQucU+vco83QjtEPJFgZCGfmgaoe/qGhR4x1qQfdbFwgyaJ/jEybtLd7p/bxklWTdC3uAlVWqxh4OsI6HXIZoMAS6Dzw61FrnSNn6WDbf9DiezPH7lboVjRROSsx8Fp8Qrkwn7r45mPFr73ZOxdwsQdv9Jo4uagu4pZEZzoeMdgGLQkgyxz1p2vdguvaHwGmKQA==
X-YMail-OSG: b.GogLkVM1mWh2Th94yN6LzDkhSh9w2dBDRYrw4nB6_bA8oAtuqmwGjHGvjBQT8 9GT9VSReRgNAlRU6nwXP39_6364JbrINyNsWXhadw9ZRW1iDEuhIEmyyy8LI3_g9TUFWiJzYo_JI 20mcVyy5fI7daFtVt6K0NQ70AFpQKtoj.alf3sQ4CNvnvd9jYbP0EZbTDT6s1V5qcr76PvzOr7AY X0vFczwEEvuF4qzp.8pvgMcMlVaE9O1Y4.ZVcjn8ZXgH9N0o8nSCIqXrpXTmzTLFSxmSiQap9hbV 7RupTzjayXqIVa3xfCZqS.KnkqPXJGPNsAfGVdc_0WB5ul_a8o6o97kTSEi8fNCGWKPae09vOVYx oQ0C5n5jPHMSafT686ySG3oorpmCxizny4Goh0x1n7AMlw89iZypjKFzpFqt_CO8.iC6jSyjWsH7 dnmW.qq5yO5Lb8C2SrRfmd16iYs_T0xtulb0wJ1WSSvN.jC4xuI__8.cjYcbcCKzqLXPnlmcQL4L ZeAJ0sNEYOgwX2VpXyAMnO7jECRfgwLu5Wzj9I4mfZ4ucKClBdCQ6f16kgpYH7me1yzsCSphJLtT z19i8h5PqPMxyqopxeeLc0Vm1SgvJQ9YHuE0K4ymRP041inJCKH47A_0xfVEOcRXodvcd5oNhq0m QXVPlsXwwTC1UQ9dgnqkwZ67KNmuS9Grubpt2IsyOfnXjwIV2zjjOTsMm..6op6wxA2_JdmeMbpo vDlMpJ.LlY9.y_G4rXYtTXA0KIJ9yO6TofPGoTjl09W5UC756gPCbvVgUA_2cZrBoeAdDoEZdfT4 C.AdtRYu_skHIXnin1x06Vv3i1Mr4hn5z1NGNx1pb.Pf9XSvwKMWnDbN752DfN7z3.1KqBFUxsbc gLAjKXjpVZDMa2tl1fAC0BosfuOmzYxIZqsp5_QbR54j92CJWxi2i61tIaSoKLDtMm83a42lH0zB o5tFqGT5603kGX9VBzR9WyiFJiKXEVRyRpCUN47wMkCk6Ii9QPD7mh8rVHVHtshyasrV2FdxW3Cj cSxiXAMzUSKNGFwcLCk6mmIJwwVM49yPbSmpzRK2GTpnyhVHBPaWEM1w7oYKSlyxQ.FJlcmBX287 W0enX6LRh5Y5GfliTYUyGMT9GVLJW57JaWxIdnupLtW8iWUfjnzfRj8n96H5TwTjeoUidCnYyHZb EdRCtcvb4NFciR53CWxBOnF966G0er0KqQ59zGCdMBxNlup5L2f12h0JYwY2bHYrQ0I9Retr5Uuq QFXnhempGa_LleB1_tgJLuHGddimUAuWO3OX31C6WcnLYyiNUhMuh2KN9H8MdU5EWdQQeZsFRd0g tXTbBhkNXENrWA5yK2ogDEWTN1s.bPeBPf5AXHy1FsDZObZ0ijy8o.rUu6WgOBDpevp_dcTzJur3 Ta0vDLzNBmij64S4rsaTWXR_IDFA3gdBnF7R0hBSUKinpM.vTmcHc6j.MIaRrd6oTLG6adZZgSbz MoDMkiXf8fZ4io_Wp6Eh6gvD14BRqENSi.dmpwWUg_E7I6lV319Q0zQJMFGp5rHgnelq70fmsM2o qYBM1mLuW7Vn91l8zWMA8DZwAMZQdD1vVJDC2nLznfxp9.jLmcLhqZG98UUjQFK71yP.HvZ_I_yW 0FGWzW26AYMC1bkX03jR_yyE4nXndAulkhOAQHorkbtNpM7bUQ8FWQTSbBG1rHQ8rgNXcb1RbgC6 yGgz2Vos4XVNuZ.Br7xoSgXGAJTALKyFJo5aYkLZHZcz0a3nC4YvFP78sA1cydTeHZRU58aPFtQh sUy.K1akxlOEXB2zucXhGeSHrTRt0DEB13kV6.O2s4i3DD2F6z9qi_tv9PleYqAmtZi7.qL.HISx Z6sOxfknonayM24fG.RWqGAORrc8ZsJvmqjQR5uLYpMeFTcLTuQaI17ut8tKsdTsiDs7JI1RJz0p nj9NljpInCrm7TYzqyEsAx5ryT9bqJMLoJ.yBzrZ4gPKpYBXU1uX.Vq4zboWAvBmEvvNnjwcsTqO tfMNjSVOEKhIWYCr8cHstECyeh9QI0GeOf.ykrEdPzk2LC4njosxwqifpOwSCPC6L3wc2Frofe1c JFZluKcy3pZQu3YxQZrmrhomfnGelD4SyLp2pfJ1bPKNx6C3B8iKSNVPwI5EKXMXtM8sJZATWrYH HdFI0symFXnv2pETdxzcMifOK7JiQaKIasb4Ia3vw7HWkP4SbBLrq2ADiQpkawzwTrMoE7FrIqB2 KkV5gw1P02wulLXkdvLiI8LOsIiaNFurRW.nqyRTsEH_BWsr85W8gLYgImRobMM7od._15s10s7p KeeQnYSyzY78GsAcN5ObXdHXBEKYdMq_QV1fTRlcopz0RxuvpofvsiFKTpWBHX7_rseimUow5p3q JmO569VBs_IepnJzGaX3vJLjnG0AgEZGdFQY8Ip76TuXd76aMiCu8VXHp9i.OPUrkgf.SfX8w_JT rhBUf7pN_SUfkTOHNyDJopHpCiPi_CF7E1DUVfV.CxZC47MAZavpXLROM4FcI3yYhsOcOhXBjySu bDt42mC2npKzc0BQkAxVrB2HGVW.qUxjHMxGRxR3NCtilD4e1PmQUa64A3SrQxDUgiJAdHQAZmP6 AiO1lQRXfHkNGQaKjXZlUgrrEcU2TNwpDJg8rva0R.wmSoBumOTDReVmGeLKs.TMkj7_RXkKhFQc CZBAylRA0b2aeAAVgEie0PxEqE5EKj8kAb8k-
X-Sonic-MF: 
Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Tue, 27 Jul 2021 07:43:14 +0000
Date: Tue, 27 Jul 2021 07:43:06 +0000 (UTC)
From: Greg Dennis 
Reply-To: Greg Dennis 
To: glyn.normington.work@gmail.com, Carsten Bormann 
Cc: jsonpath@ietf.org
Message-ID: <1247207623.69360.1627371787010@mail.yahoo.com>
In-Reply-To: 
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org> 
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_69359_480618347.1627371787009"
X-Mailer: WebService/1.1.18749 YahooMailAndroidMobile
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 07:43:22 -0000

------=_Part_69359_480618347.1627371787009
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

That's the approach that JSON Schema uses, citing ECMA-262 as the preferred=
 flavor.
https://json-schema.org/draft/2020-12/json-schema-validation.html#rfc.secti=
on.6.3.3
=20
=20
  On Tue, 27 Jul 2021 at 7:01 pm, Glyn Normington wrote:   My aim was to require iregexp for interoperability, but all=
ow
alternate regexp implementations with potentially degraded
interoperability.

Could we achieve something similar using compliance
levels/modules/features? For example, could an implementer add (to the
regexp-free subset) an alternative regexp module/feature for their
preferred (non-compliant) regexp implementation?

I guess the semantics would be that JSONPath implementations which use
interoperable regexp implementations will interoperate. So, for
example, JSONPath/iregexp implementations would interoperate with each
other as would JSONPath/RE2 implementations. But, for any regexp
implementations x and y, JSONPath/x would only interoperate with
JSONPath/y to the extent that x and y interoperate.

I quite like that this approach separates regexp interoperation from
the JSONPath spec and makes it a matter for regexp.

On Mon, 26 Jul 2021 at 17:10, Carsten Bormann  wrote:
>
> In the discussion of
> https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103, =
it became apparent that we weren=E2=80=99t quite sure what levels of compli=
ance language we should be using.=C2=A0 Particularly, I would think that a =
SHOULD is not very useful except when discussing corner cases (or non-funct=
ional requirements like =E2=80=9CSHOULD NOT blow up=E2=80=9D).
>
> So are we ready to have multiple compliance levels?
> A core set to which we expect everyone to comply and set of modules/featu=
res that can be added to the compliance?=C2=A0 No regular expressions in th=
e core but an optional compliance module/feature for iregexps?
>
> I don=E2=80=99t want to overthink that and propose a complicated set of m=
odules where a single monolithic core would be sufficient, but stumbling in=
to these modules without having planned for them is probably also not a goo=
d idea.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>
> > On 2021-07-24, at 17:18, Carsten Bormann  wrote:
> >
> > On 2021-07-20, at 19:50, Tim Bray  wrote:
> >>
> >> This is happening next Monday at 4PM Pacific time, which means in the =
middle of the night for the bulk of our EuroPeople; sorry about that.
> >
> > Apparently I didn=E2=80=99t pay enough attention, since I only just not=
iced that I have a conflict with IOTOPS in that slot.
> >
> > I think we need to have a slightly more frequent interim cadence.
> >
> > Gr=C3=BC=C3=9Fe, Carsten
> >
> > --
> > 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

--=20
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath
 =20

------=_Part_69359_480618347.1627371787009
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

That's the approach that JSON Schema uses, citing ECMA-262 as the preferred=
 flavor.

https://json-schema.org/dr=
aft/2020-12/json-schema-validation.html#rfc.section.6.3.3
 
 
 
 On Tue, 27 Jul 2021 at 7:01 pm, Glyn Normington
<glyn.norming=
ton.work@gmail.com> wrote:
 
 
 My aim was to r=
equire iregexp for interoperability, but allow
alternate =
regexp implementations with potentially degraded
interope=
rability.

Could we achieve something s=
imilar using compliance
levels/modules/features? For exam=
ple, could an implementer add (to the
regexp-free subset)=
 an alternative regexp module/feature for their
preferred=
 (non-compliant) regexp implementation?

I guess the semantics would be that JSONPath implementations which useinteroperable regexp implementations will interoperate. So,=
 for
example, JSONPath/iregexp implementations would inte=
roperate with each
other as would JSONPath/RE2 implementa=
tions. But, for any regexp
implementations x and y, JSONP=
ath/x would only interoperate with
JSONPath/y to the exte=
nt that x and y interoperate.

I quite =
like that this approach separates regexp interoperation from
the JSONPath spec and makes it a matter for regexp.
<=
br clear=3D"none">On Mon, 26 Jul 2021 at 17:10, Carsten Bormann <cab=
o@tzi.org> wrote:
>
> In t=
he discussion of
> https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issue=
s/103, it became apparent that we weren=E2=80=99t quite sure what level=
s of compliance language we should be using.  Particularly, I would th=
ink that a SHOULD is not very useful except when discussing corner cases (o=
r non-functional requirements like =E2=80=9CSHOULD NOT blow up=E2=80=9D).>
> So are we ready to have multip=
le compliance levels?
> A core set to which we expect =
everyone to comply and set of modules/features that can be added to the com=
pliance?  No regular expressions in the core but an optional complianc=
e module/feature for iregexps?
>
>=
; I don=E2=80=99t want to overthink that and propose a complicated set of m=
odules where a single monolithic core would be sufficient, but stumbling in=
to these modules without having planned for them is probably also not a goo=
d idea.
>
> Gr=C3=BC=C3=9Fe, Cars=
ten
>
>
> &g=
t; On 2021-07-24, at 17:18, Carsten Bormann <cabo@tzi.org> =
wrote:
> >
> > On 2021-07-2=
0, at 19:50, Tim Bray <tbray@textuality.com> =
wrote:
> >>
> >> This=
 is happening next Monday at 4PM Pacific time, which means in the middle of=
 the night for the bulk of our EuroPeople; sorry about that.
> >
> > Apparently I didn=E2=80=99t pay e=
nough attention, since I only just noticed that I have a conflict with IOTO=
PS in that slot.
> >
> > I =
think we need to have a slightly more frequent interim cadence.
> >
> > Gr=C3=BC=C3=9Fe, Carsten
> >
> > --
>=
; > Jsonpath mailing list
> > Json=
path@ietf.org
> > https://www.=
ietf.org/mailman/listinfo/jsonpath 
 
------=_Part_69359_480618347.1627371787009--


From nobody Tue Jul 27 01:38:57 2021
Return-Path: 
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 259183A1B04 for ; Tue, 27 Jul 2021 01:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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=gmail.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 2hlJreT1GNOc for ; Tue, 27 Jul 2021 01:38:50 -0700 (PDT)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 B5B1C3A1B06 for ; Tue, 27 Jul 2021 01:38:49 -0700 (PDT)
Received: by mail-pj1-x1036.google.com with SMTP id b6so16727412pji.4 for ; Tue, 27 Jul 2021 01:38:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fW92xsTmkNP7XaLFc+ElCd1G0GAfbpkFewFqihjtp54=; b=p1OBZrewkG/zz8KZHaCKjvgKiyY9gIC30ycEeZ0UiTHMBKlFLjyORgQEGAILIYl9yx J7yNRzQBWuekQqA10xrbd6YpPofa+Z9MNDHm3//dHPiQttQj+E1BZ7QzgakhG8/bs6xb JEaid9OGiwdaNNPt7wXZVyNTVnID9RKXMVMINo4Amm8Z+InWrPbADm6NMrNdhmS70NRz 6GBBn1oBnX/PYGS5jevYypMXhKFgTo6iPFZpkJhPGF1bsWuDthUuLLMKHl9SP8Wz8cyG soKyLOGu0Hk47t5Adg5HpDb3UWqI3h3PH8SsGo7iOPGdsqNe+xLi7RDvpQ/zkUSVoAFc lZzA==
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=fW92xsTmkNP7XaLFc+ElCd1G0GAfbpkFewFqihjtp54=; b=U0BSqaFBs3Cewz2poGOUdaDcJMkBMrHdIGU1rupugOkNUOe4R7AMoDdPz4cMzhMvFD 69Re8Dm5PjPSjFjomS0B+gSCAahG9YcVn2OGvsNugkq5uAZ29BMySh93ZrCcd1x4gUMg gMWfol91bvXobZ4MwjyMd3EOR2Y3m9p7Xd17yicp7oc6MsV3oxunYpca0zLRdO4p7Suv NOxvTq3zGFxxB6zjDoe0d1qQeWu3B+NwB5f/EJmIHgTWst6dwc9hid8bP1jm48lt1r+k 89OJQ6qddCrGHXSjZfsCHjFA55mw2GmRPy0Gc4WQq+TqysozaXrO+HLlEzft2AmXqLot zL6Q==
X-Gm-Message-State: AOAM531dFT5flPPUhnm/1g43PqF0CNHDbISsZ7A0U854X/jfrD7yphmC bymWFpIgvK76ejXUSRYj8JSVVkn5itWwZzo/ifw=
X-Google-Smtp-Source: ABdhPJxFASpVuw706YGKFIWKoMlriO9Axy+YuJXrCRtgQp3AuCHT3C0F6fVKHIkMoXnrIMxSsBfVuHyjUFzcaJJZf34=
X-Received: by 2002:a62:30c5:0:b029:31e:fa6d:1738 with SMTP id w188-20020a6230c50000b029031efa6d1738mr21765255pfw.55.1627375128025; Tue, 27 Jul 2021 01:38:48 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com>
In-Reply-To: <1247207623.69360.1627371787010@mail.yahoo.com>
From: Glyn Normington 
Date: Tue, 27 Jul 2021 09:38:35 +0100
Message-ID: 
To: Greg Dennis 
Cc: Carsten Bormann , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006c410705c816cc35"
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 08:38:55 -0000

--0000000000006c410705c816cc35
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Greg. The JSON Schema text is straightforward:

"This string SHOULD be a valid regular expression, according to the
ECMA-262 regular expression dialect."

Couldn't we do something similar? What would be the downside of adopting
ECMA-262 regular expressions for this purpose rather than depending on
developing iregexp?

On Tue, 27 Jul 2021, 08:43 Greg Dennis,  wrote:

> That's the approach that JSON Schema uses, citing ECMA-262 as the
> preferred flavor.
>
>
> https://json-schema.org/draft/2020-12/json-schema-validation.html#rfc.sec=
tion.6.3.3
>
> On Tue, 27 Jul 2021 at 7:01 pm, Glyn Normington
>  wrote:
> My aim was to require iregexp for interoperability, but allow
> alternate regexp implementations with potentially degraded
> interoperability.
>
> Could we achieve something similar using compliance
> levels/modules/features? For example, could an implementer add (to the
> regexp-free subset) an alternative regexp module/feature for their
> preferred (non-compliant) regexp implementation?
>
> I guess the semantics would be that JSONPath implementations which use
> interoperable regexp implementations will interoperate. So, for
> example, JSONPath/iregexp implementations would interoperate with each
> other as would JSONPath/RE2 implementations. But, for any regexp
> implementations x and y, JSONPath/x would only interoperate with
> JSONPath/y to the extent that x and y interoperate.
>
> I quite like that this approach separates regexp interoperation from
> the JSONPath spec and makes it a matter for regexp.
>
> On Mon, 26 Jul 2021 at 17:10, Carsten Bormann  wrote:
> >
> > In the discussion of
> > https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103=
,
> it became apparent that we weren=E2=80=99t quite sure what levels of comp=
liance
> language we should be using.  Particularly, I would think that a SHOULD i=
s
> not very useful except when discussing corner cases (or non-functional
> requirements like =E2=80=9CSHOULD NOT blow up=E2=80=9D).
> >
> > So are we ready to have multiple compliance levels?
> > A core set to which we expect everyone to comply and set of
> modules/features that can be added to the compliance?  No regular
> expressions in the core but an optional compliance module/feature for
> iregexps?
> >
> > I don=E2=80=99t want to overthink that and propose a complicated set of=
 modules
> where a single monolithic core would be sufficient, but stumbling into
> these modules without having planned for them is probably also not a good
> idea.
> >
> > Gr=C3=BC=C3=9Fe, Carsten
> >
> >
> > > On 2021-07-24, at 17:18, Carsten Bormann  wrote:
> > >
> > > On 2021-07-20, at 19:50, Tim Bray  wrote:
> > >>
> > >> This is happening next Monday at 4PM Pacific time, which means in th=
e
> middle of the night for the bulk of our EuroPeople; sorry about that.
> > >
> > > Apparently I didn=E2=80=99t pay enough attention, since I only just n=
oticed
> that I have a conflict with IOTOPS in that slot.
> > >
> > > I think we need to have a slightly more frequent interim cadence.
> > >
> > > Gr=C3=BC=C3=9Fe, Carsten
> > >
> > > --
> > > 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
>
> --
> Jsonpath mailing list
> Jsonpath@ietf.org
> https://www.ietf.org/mailman/listinfo/jsonpath
>
>

--0000000000006c410705c816cc35
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Thanks Greg. The JSON Schema text is straightforward:
"This string SHOULD be a val=
id regular expression, according to the ECMA-262 regular expression dialect=
."

Couldn't we =
do something similar? What would be the downside of adopting ECMA-262 regul=
ar expressions for this purpose rather than depending on developing iregexp=
?

On Tue, 27 Jul 2021, 08:43 Greg Dennis, <gregsdenni=
s@yahoo.com> wrote:
That'=
;s the approach that JSON Schema uses, citing ECMA-262 as the preferred fla=
vor.

https://json-schema.org/draft/2020-12/json-schema=
-validation.html#rfc.section.6.3.3
 
 
 
 
On Tue, 27 Jul 2021 at 7:01 pm, Gly=
n Normington
 
 
 My aim was to requi=
re iregexp for interoperability, but allow
alternate rege=
xp implementations with potentially degraded
interoperabi=
lity.

Could we achieve something simil=
ar using compliance
levels/modules/features? For example,=
 could an implementer add (to the
regexp-free subset) an =
alternative regexp module/feature for their
preferred (no=
n-compliant) regexp implementation?

I =
guess the semantics would be that JSONPath implementations which use
interoperable regexp implementations will interoperate. So, for=

example, JSONPath/iregexp implementations would interope=
rate with each
other as would JSONPath/RE2 implementation=
s. But, for any regexp
implementations x and y, JSONPath/=
x would only interoperate with
JSONPath/y to the extent t=
hat x and y interoperate.

I quite like=
 that this approach separates regexp interoperation from
=
the JSONPath spec and makes it a matter for regexp.

On Mon, 26 Jul 2021 at 17:10, Carsten Bormann <cabo@tzi.org> wrote:
>
> In the discussion of
> htt=
ps://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base/issues/103, i=
t became apparent that we weren=E2=80=99t quite sure what levels of complia=
nce language we should be using.=C2=A0 Particularly, I would think that a S=
HOULD is not very useful except when discussing corner cases (or non-functi=
onal requirements like =E2=80=9CSHOULD NOT blow up=E2=80=9D).
>
> So are we ready to have multiple complianc=
e levels?
> A core set to which we expect everyone to =
comply and set of modules/features that can be added to the compliance?=C2=
=A0 No regular expressions in the core but an optional compliance module/fe=
ature for iregexps?
>
> I don=E2=
=80=99t want to overthink that and propose a complicated set of modules whe=
re a single monolithic core would be sufficient, but stumbling into these m=
odules without having planned for them is probably also not a good idea.>
> Gr=C3=BC=C3=9Fe, Carsten
>
>
> > On 2021=
-07-24, at 17:18, Carsten Bormann <cabo@t=
zi.org> wrote:
> >
> &g=
t; On 2021-07-20, at 19:50, Tim Bray <tbray@textuality.com> wrote:
> >>> >> This is happening next Monday at 4PM Pacific =
time, which means in the middle of the night for the bulk of our EuroPeople=
; sorry about that.
> >
> >=
 Apparently I didn=E2=80=99t pay enough attention, since I only just notice=
d that I have a conflict with IOTOPS in that slot.
> &=
gt;
> > I think we need to have a slightly more fre=
quent interim cadence.
> >
> &=
gt; Gr=C3=BC=C3=9Fe, Carsten
> >
=
> > --
> > Jsonpath mailing list
> > Jsonpath@ietf.org> > https://www.ietf.org/mailman/listinfo/jsonpath 
 


--0000000000006c410705c816cc35--


From nobody Tue Jul 27 02:02:09 2021
Return-Path: 
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 040A43A1BD1 for ; Tue, 27 Jul 2021 02:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 xGno6QK0yFM3 for ; Tue, 27 Jul 2021 02:02:03 -0700 (PDT)
Received: from p3plwbeout24-03.prod.phx3.secureserver.net (p3plsmtp24-03-2.prod.phx3.secureserver.net [68.178.252.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6C013A1BD0 for ; Tue, 27 Jul 2021 02:02:03 -0700 (PDT)
Received: from mailex.mailcore.me ([94.136.40.145]) by :WBEOUT: with ESMTP id 8IyPmjGzxymEz8IyQmod3i; Tue, 27 Jul 2021 02:02:02 -0700
X-CMAE-Analysis: v=2.4 cv=S80cfKgP c=1 sm=1 tr=0 ts=60ffcb8b a=7e6w4QD8YWtpVJ/7+iiidw==:117 a=G++axsv19AQkVQuwCdl4cA==:17 a=0d-FJ89MWBcA:10 a=kj9zAlcOel0A:10 a=e_q4qTt1xDgA:10 a=0diO0PVxq2FKMFDvrkAA:9 a=CjuIK1q_8ugA:10
X-SECURESERVER-ACCT: mike@saxonica.com  
X-SID: 8IyPmjGzxymEz
Received: from [82.152.109.221] (helo=[10.0.0.4]) by smtp11.mailcore.me with esmtpa (Exim 4.94.2) (envelope-from ) id 1m8IyP-0006co-Er; Tue, 27 Jul 2021 10:02:01 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Michael Kay 
In-Reply-To: 
Date: Tue, 27 Jul 2021 10:02:00 +0100
Cc: Greg Dennis , jsonpath@ietf.org, Carsten Bormann 
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E23EAD1-AF27-4E7E-9D1B-20FC4E74615F@saxonica.com>
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com> 
To: Glyn Normington 
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Mailcore-Auth: 439400257
X-Mailcore-Domain: 1881035
X-123-reg-Authenticated: mike@saxonica.com  
X-Originating-IP: 82.152.109.221
X-CMAE-Envelope: MS4xfNHLGiGz7fqoaU+kOYtCvUMuHtaieuVKKdOQ8dCnrCCGJkJg1r9lUh+djet4QcV0CCtBn+scvX9EPQTv4k1B0ejKHUl/zVKXfdDb5aapxk7UvZPsrrgA UyT2ajDySBLdYmWxFXZGOKDS/5OCBXRMnyDS2H/8KyXGSdT0iM+RcMSfp/MImwqmgVsbYjPAB2RNIw==
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 09:02:08 -0000

>What would be the downside of adopting ECMA-262 regular expressions for =
this purpose rather than depending on developing iregexp?


The main one is that you'd be perpetuating the default processing mode =
where you're matching 16-bit code units rather than Unicode codepoints, =
which is really only wanted for legacy reasons: similarly other legacy =
behavior like the strange case-folding semantics of the "i" flag.

If you're going to go for ECMA-262, make it ECMA-262 in Unicode ("u") =
mode.

Michael Kay
Saxonica



From nobody Tue Jul 27 02:29:17 2021
Return-Path: 
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 A07E03A1CB1 for ; Tue, 27 Jul 2021 02:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 0chfOo6TtX7z for ; Tue, 27 Jul 2021 02:29:11 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 170ED3A1CB4 for ; Tue, 27 Jul 2021 02:29:11 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYs1c1fpyz31MH; Tue, 27 Jul 2021 11:29:08 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann 
In-Reply-To: 
Date: Tue, 27 Jul 2021 11:29:07 +0200
Cc: jsonpath@ietf.org
X-Mao-Original-Outgoing-Id: 649070947.761052-0eb47a8b868df82385fd556082df409e
Content-Transfer-Encoding: quoted-printable
Message-Id: <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org>
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com> 
To: Glyn Normington 
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 09:29:16 -0000

On 2021-07-27, at 10:38, Glyn Normington =
 wrote:
>=20
> "This string SHOULD be a valid regular expression, according to the =
ECMA-262 regular expression dialect."

ECMA-262 is a moving target, the there is not really a single =
=E2=80=9CECMA-262 regular expression dialect=E2=80=9D; but that is easy =
to solve by referring to an ECMA-262 edition of a specific year.

For a few years, the functionality supported by ECMA-262 regular =
expressions has expanded significantly.  With today=E2=80=99s extent, =
supporting ECMA-262 regular expressions would require months of =
implementation effort.

This is easy to do if your code runs in a recent JavaScript environment. =
 It is mostly impractical (dwarfing any JSONpath effort) if your =
platform does not already have an ECMA-262 regexp implementation around.

So this is one of those SHOULDs that really mean =E2=80=9CSHOULD, but we =
know you won=E2=80=99t=E2=80=9D.  Why write something like this into a =
standard?  This only makes sense if interoperability is not the main =
goal.

Every competent engineer can implement XSD regexps (and more so the =
iregexp subset) in less than a week.  So if we care about =
interoperability, this is more likely to yield it.

By the way, json-schema.org had a more practical approach 8 months ago:

=
https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section=
-6.4

This isn=E2=80=99t really specified very well, but if one sat down and =
did, it would be closer to the iregexp approach at least in aspiration =
(it is still littered with the useless kind of SHOULD I mentioned =
above).

The iregexp approach uses the XSD choice of anchoring both sides of the =
expression, because that is always what you want in matching operation =
(it is easy to add .* if it is not).  ECMA-262 of course has parsing =
regular expressions, so you have to add ^ and $ for essentially all =
expressions.

It may be a useful approach to support different regexp modules by =
explicitly indicating the dialect at hand, with iregexp as the Rosetta =
Stone that can work everywhere.  This works great both for JSONPath =
users that don=E2=80=99t care about interoperability (because they are =
writing their JSONPath for a specific server implementation) and for =
ones that need interoperability.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Jul 27 02:46:20 2021
Return-Path: 
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 BA78C3A1D4D for ; Tue, 27 Jul 2021 02:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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=yahoo.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 OiX0FR9e3TWb for ; Tue, 27 Jul 2021 02:46:13 -0700 (PDT)
Received: from sonic308-1.consmr.mail.bf2.yahoo.com (sonic308-1.consmr.mail.bf2.yahoo.com [74.6.130.40]) (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 5DB9B3A1D49 for ; Tue, 27 Jul 2021 02:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1627379168; bh=3JvNdIzdWrScGRfWH0MJquYNMEUgbuCoNvxwYITwv1o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject:Reply-To; b=JiEl88+7o79DFhIOpWJyy9mHF/X2hpMrmcQXL7HdL8THZmq8RkZknTGAHERocGotrztTW3DQGfMx1+B/uqgeJr9cw09EsC3lCO39a9nD++uIfGCNKAXGPw1L7DqNmCaXs4EuLrlcXPHEGWZsCTmoPKa1byiP2Dgt5mY4JlobcFtzf6PkV4Y6PbN9OwSVHLRmdw0cFY8i2F/KpCnS8Xzb7GU/8mBBZYu1iaHph8lgmOFagz0BtM32Ga1Y/h0lTe53+qMK85sh0RRbSut+b87MolcxrJSkOAWSPtqXaZTM8P7fQUOuDcY7wGwdt6B5uy24RLhxQfVeVfxNvcKq31Bm4Q==
X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048;  t=1627379168; bh=KIq/f99ZSljmStIkcLtOxyHjvXK2KDiI4TH4xCwlp8v=;  h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=T6cwuXPnA9ZU5XdawQtv2LnKxB/4T1UYBGYKUEXP0xCYOpUmkpGG3sHy0JE35XEwjmsRa3e1FR49xgqCjWcYPKWBNEt54yv7ZTHvYeBlO6NLY8NKf7lvm7AhakAgt6e38if8lR+khxsPMLp3oJQKdvfPiUCg/IBCTWkgoj0dkR6EThUX2uUFSp/VALxpY7fdZU8ap33ShviQvUK57acgbDiBNQkgT5G6iWwmQJXqV86yCfGdhS3lCnQmZ0wSIudFDh5F5G0Z8XOzgVYHdySApVn/9xXRyJ8I4OxdyhihxJLwpF+vLnzYcsRdVNogmjCz3odFeiqWpmF0dQ5f2vzpVA==
X-YMail-OSG: M.ALWFUVM1kzKuhJ2vX7hiuQTRXMe46GSihODsvEkcK4IswSM.VgiKo5J6jCpbc p9LUNhpqqCYk6wGCtVXtfpgIXAufghCsosF2u5Sr3Vs8cEaizOVkSRhibScTCKzziIhlgidAoXDg sseFcB0fJEsFsGU9IkG.QvxQ.IllQ0Yb7JMyat5rxkK.4tqNeVvCFk3McEUvpUrF1T1Yf92dCXLV D_b_u9asDMjVDU7OPl1A1a7DrrWCObfIYQWpwhCqvLccGLY8RKL8Ri9B9iDatViQoh35q3uZ9mFD fcrSS_HQoFu3ttSbXCGQ5qoaUU1VYUMatKFi0sXLhoicWFL7NxuM.hBzjyA5w87xP5pxflV35aSk 14B.nC0caY2jeB3HdhJ_CAQsEpd6VdtorXk1oGLl4BKhSj0SdZ2ZluXi2Gbe0p7pWpjX9.A2QuMa yaApfweIlnJffdOHMRknGfSVRG09RTw1Hfwmwoh1fxZNSlVvK9FHYombM0JkdWWosl.GeGa9v5RE RSjQ84edmgzUuTqy9mesqZqj6e5iydP82VzMEB4_woquk7qYwm42FtwEe9EssV29KHnM_34riQsT fLcNHNwwa5SOkFcZd_2b0m9lIVGrfK.rE1icGHeSBWtVETgtnDvX7PkgUuaZAj2bDoJ_ssX.iQVt 20d_wjnze4PO3cfB9Id2CC7MvmCSJmkC4ztLK_RFTO0w1ie6Lj4dsQZ0y1r1F4GA_ogxEKu_yUjQ ivbyIdmZjtxHCtViCSlT9NBCtrQ0TzECUbxnBw1Pepd0sVEipj3RCjYtr68xE9S7rJOW0jE64bEK m1UNqjC1UE4S1K3bg19Yq090FkmXQzT6FCNUSI150dMW.z5lPZFpFiRaQKp_pPONYGhXxunhKwBW dHTfrkLvsmArX.qbOKez_fztWX.lbpTEr.iqn6Rb6YnfeJ9Dzo_9Omfm5Owb3Krn8TL.ijXyvA0E 70nJ1w.bY2uqhOBLst8RxRTZyruTDVsP6NiykZdmDcdBaJcberHSIjd5nKb_dRym9k.K3oDpkUbN xjWyDb0tKE6dWEz0EjKo6UMCk00q6Kv3DVIlXADOuz7fDJgoYNkatNLjGbh1SrDfjDfujj5i4S5. 9R9RyFg9O0Kg8Ss3PBat3EhcNA0YPR5r4p9iF9p_ZBHQ3BC7yfR9ozFnEjlAvh27cyj8O1olint2 MU1RImyjqDLJ8Uvp_D2vLkduUJoiXNiWPFbp611XVrTvP5PFf4PmTmtEZNBm7Bv1e9bmuZaHI.S. yv5xy146APLtyrB3s1S6qh3tZ9vp9VuVTNxHJjhQ7tC5wtaKgs6h6AIzocWcyjai7xGOGN57_Mlj AdbFYF4gMiOrFFeQ6Fyf9tt0TBbGUR0nxlBNYYYFLTk_2tKnqnHx.A3TPMw3vs55SdNKnpY02Tgo _TSRDzt.tSVAls7V7RctZx7fYn55Bv5sg9H1mwOeOXz_PnZEddGKth8wMAbmdUKtQXOW4JtFbijf myV6cIUH2O17ofR9XV35D26uR_jeAGUbYg5QrfIAW4M26oelBKazcD..apDnlbqzi6Gxo_al..Tj 3TFURNzHNoohCw2huRIuC8vfVu7eJ51VE66y2gsZ3SOPZlHiinxiVdOgY1l3cXGVtSmswKDqtexS .PrTEx1nnABjydBAFEDnib1E4l9NFRTiMiBip4OCT8.NHLkF78roBy2uVWIdZ5ZOiIZb_1YnOl_f 7hji4DKVUtXe5ypLznNgsHHPDMBjFAwyZ0Z7Awb4sUdpzJfSeZzpEMymDbLdBf6S07R7iUhvP8IL xiI.1.AzXkvC.IBC6x31HyONx6oCv6R.ssAO9LAko3jZUtyvHHFM_uWrPrbFxPmfpPXZd8Xktpz0 o8bpcq5VINSTRsMlv4s69w3FsLkC5XMwy5t6rPoDSPjctooewKHtdvtRoShl8pDSSiNWzbdThJZ1 P173BBh2E7AdKeHtt55qSLsY6B_pLC8YxI.ipq8AxSvEnqkLN.xBWdyf8v80swtdVbGsyfSfC0zV .Se_qq5V0bYV_HefIsA4r2k8R11PFo7hHMdvZHROaDoBjZKW9k6fQk.U9XRaMnXwEBgzzVB3Zy74 stwve6_iGwOFKWznKRwzPXUXQl4TjuIqcl_ENCREqAntWru1fuJq2cEXQbjiF08W5wXmcsiirgnD 1cC8Dx9ktXMWjxR6GikpYPYd6NPG2fc8VkRyDHQyHITQPJjyifglbu3qWHgYQuqtDILozjiedRyN DD9GjSnWG2FXEDVRPH1_7U0LBJPi97sgI_iFqpnFBGOgTsXFH6vpxOKfpMcvRt6vKa78jxhX_7SN LNXITIcxxtohMn6yuPYNY5i0UXODqdiiXZ229dAOaQwFvxNtO_pqNCRjaYeOYSHS2HL8AiuHC4S0 HUTlWVG_Ib618fNCguO7XWbEJtMSHUd1XeZbTG73rbbVfGn8YMxITJM4GWxsNuEmIfG3nwMIJYDv 0DaqtZWGaC38EbhXS1UZBJbBgS3dVNnHKcABedKk0lfqpKn4.9WRPD9kZ11SHRjN2PX9rNXkt2kn O9eAx7EfpsuTf9gy4GYAN.14lvd42F6g_ESpLhanLIPTzOrSdyAcyy_LFM6SuACkWH9OvQAeZ2ik UK1fRbJ_80bvlejBSP8WchHWFqrw7zA5L0bU7qItp5ILJ_YjWZQBjol_NxsWHwkP2qzpPeNXHFk1 lJEewTxB.z.5dzPP9cZmsGrd3Cx66XD_lmQ--
X-Sonic-MF: 
Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.bf2.yahoo.com with HTTP; Tue, 27 Jul 2021 09:46:08 +0000
Date: Tue, 27 Jul 2021 09:45:58 +0000 (UTC)
From: Greg Dennis 
Reply-To: Greg Dennis 
To: cabo@tzi.org, Glyn Normington 
Cc: jsonpath@ietf.org
Message-ID: <1647831783.76652.1627379158858@mail.yahoo.com>
In-Reply-To: <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org>
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com>  <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_76651_984793248.1627379158856"
X-Mailer: WebService/1.1.18749 YahooMailAndroidMobile
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 09:46:19 -0000

------=_Part_76651_984793248.1627379158856
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

To be clear, I wasn't suggesting ECMA-262 as the implementation. Rather I w=
as suggesting the wording in the spec that included and referenced it as an=
 example of an approach we could use to reference whatever we wanted to use=
.
Greg
=20
=20
  On Tue, 27 Jul 2021 at 9:29 pm, Carsten Bormann wrote:   On=
 2021-07-27, at 10:38, Glyn Normington  wro=
te:
>=20
> "This string SHOULD be a valid regular expression, according to the ECMA-=
262 regular expression dialect."

ECMA-262 is a moving target, the there is not really a single =E2=80=9CECMA=
-262 regular expression dialect=E2=80=9D; but that is easy to solve by refe=
rring to an ECMA-262 edition of a specific year.

For a few years, the functionality supported by ECMA-262 regular expression=
s has expanded significantly.=C2=A0 With today=E2=80=99s extent, supporting=
 ECMA-262 regular expressions would require months of implementation effort=
.

This is easy to do if your code runs in a recent JavaScript environment.=C2=
=A0 It is mostly impractical (dwarfing any JSONpath effort) if your platfor=
m does not already have an ECMA-262 regexp implementation around.

So this is one of those SHOULDs that really mean =E2=80=9CSHOULD, but we kn=
ow you won=E2=80=99t=E2=80=9D.=C2=A0 Why write something like this into a s=
tandard?=C2=A0 This only makes sense if interoperability is not the main go=
al.

Every competent engineer can implement XSD regexps (and more so the iregexp=
 subset) in less than a week.=C2=A0 So if we care about interoperability, t=
his is more likely to yield it.

By the way, json-schema.org had a more practical approach 8 months ago:

https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-=
6.4

This isn=E2=80=99t really specified very well, but if one sat down and did,=
 it would be closer to the iregexp approach at least in aspiration (it is s=
till littered with the useless kind of SHOULD I mentioned above).

The iregexp approach uses the XSD choice of anchoring both sides of the exp=
ression, because that is always what you want in matching operation (it is =
easy to add .* if it is not).=C2=A0 ECMA-262 of course has parsing regular =
expressions, so you have to add ^ and $ for essentially all expressions.

It may be a useful approach to support different regexp modules by explicit=
ly indicating the dialect at hand, with iregexp as the Rosetta Stone that c=
an work everywhere.=C2=A0 This works great both for JSONPath users that don=
=E2=80=99t care about interoperability (because they are writing their JSON=
Path for a specific server implementation) and for ones that need interoper=
ability.

Gr=C3=BC=C3=9Fe, Carsten

--=20
Jsonpath mailing list
Jsonpath@ietf.org
https://www.ietf.org/mailman/listinfo/jsonpath
 =20

------=_Part_76651_984793248.1627379158856
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

To be clear, I wasn't suggesting ECMA-262 as the implementation. Rather I w=
as suggesting the wording in the spec that included and referenced it as an=
 example of an approach we could use to reference whatever we wanted to use=
.

Greg
 
 
  
On Tue, 27=
 Jul 2021 at 9:29 pm, Carsten Bormann
<cabo@tzi.org> wrote:=

 
 
 On 2021-07-27, at 10:38, Glyn Normington <=
;glyn.normington.work@gmail.com> wrote:
> 
> "This string S=
HOULD be a valid regular expression, according to the ECMA-262 regular expr=
ession dialect."

ECMA-262 is a moving =
target, the there is not really a single =E2=80=9CECMA-262 regular expressi=
on dialect=E2=80=9D; but that is easy to solve by referring to an ECMA-262 =
edition of a specific year.

For a few =
years, the functionality supported by ECMA-262 regular expressions has expa=
nded significantly.  With today=E2=80=99s extent, supporting ECMA-262 =
regular expressions would require months of implementation effort.

This is easy to do if your code runs in a rece=
nt JavaScript environment.  It is mostly impractical (dwarfing any JSO=
Npath effort) if your platform does not already have an ECMA-262 regexp imp=
lementation around.

So this is one of =
those SHOULDs that really mean =E2=80=9CSHOULD, but we know you won=E2=80=
=99t=E2=80=9D.  Why write something like this into a standard?  T=
his only makes sense if interoperability is not the main goal.

Every competent engineer can implement XSD regexps=
 (and more so the iregexp subset) in less than a week.  So if we care =
about interoperability, this is more likely to yield it.
=

By the way, json-schema.org had a more practical approac=
h 8 months ago:

https://datatracker.ietf.org/doc/html/draft-bhut=
ton-json-schema-00#section-6.4

Thi=
s isn=E2=80=99t really specified very well, but if one sat down and did, it=
 would be closer to the iregexp approach at least in aspiration (it is stil=
l littered with the useless kind of SHOULD I mentioned above).

The iregexp approach uses the XSD choice of anchor=
ing both sides of the expression, because that is always what you want in m=
atching operation (it is easy to add .* if it is not).  ECMA-262 of co=
urse has parsing regular expressions, so you have to add ^ and $ for essent=
ially all expressions.

It may be a use=
ful approach to support different regexp modules by explicitly indicating t=
he dialect at hand, with iregexp as the Rosetta Stone that can work everywh=
ere.  This works great both for JSONPath users that don=E2=80=99t care=
 about interoperability (because they are writing their JSONPath for a spec=
ific server implementation) and for ones that need interoperability.


Gr=C3=BC=C3=9Fe, Carsten

-- 
Jsonpath mailing list
Jsonpath@=
ietf.org
https://www.ietf.org/mailma=
n/listinfo/jsonpath
 
 
------=_Part_76651_984793248.1627379158856--


From nobody Tue Jul 27 03:06:55 2021
Return-Path: 
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 F31143A1DF0 for ; Tue, 27 Jul 2021 03:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 P7zfQZejxgYW for ; Tue, 27 Jul 2021 03:06:49 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 42F4D3A1DEE for ; Tue, 27 Jul 2021 03:06:49 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id k1so15081656plt.12 for ; Tue, 27 Jul 2021 03:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Dun3EAHFkIwvDgchQH0bk0GiDLXpj7mZpKGfoNUIg5w=; b=O2IuHYqh6//0yMnOggp2+UooMuYl2CrCHlxW8vDDPVn626uEHa7dyGhMGtvUr/4F9j OI/6sJppXy1CL+QPFejh1h2r30plhTWBPQPNbgs99CYnDoCuIoHHkYEGCFlJXyoEB31V 3G84a0wFMyAYnCqzH9n6tujfG6Wgcs52Xmi2h4Y4Qa6wJ6hzhHkttNrvuTlXyfieTBFi gM39V5XBMi5mgIGOMkuWGtTSdXovKLDRizvsE6R65bxhrTw9CgURs1NflUP0p8zw1LFg naZmo5RJjIPebTZRJeXY/ZTWfCLhsX/w8QeHWGKREXfj261Zk6B/20X6yZJtutcYDS5+ AjxQ==
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=Dun3EAHFkIwvDgchQH0bk0GiDLXpj7mZpKGfoNUIg5w=; b=O0JskVWGRPSgXddBll6AI9e/e7xD/DJazpCa1KSjDc/GYaa0PIPzuq1+xYI4OG3H8b xhsaivI4L8Op7drT/VSYchzRUir7dCP8pIfYDuh2ox+OAzD8mcRG18ZrG0kYt2LgmL52 jMP12BPxXt66PmvyRMcIITpgUo42hACE+uUsGsTdBFBxgmwmmBU5iDGrynFdOgPKDyYJ UeGAa3u4eVniDbLf4R9wNCD+nhnluh/H+jJJgvyL4MbqJHIO2w5W66XB5PBXXMvl7zQk FjV6j44+ae6uQ9/cKLhl/UuixhrPnHCAlFVAPv9juxWbHGMbc9+Y/pdIJFMhgBOS2XPt j6aA==
X-Gm-Message-State: AOAM530kidmX131GUSM54JEZ2sfW6rSQLEzDli9PMI+dK62bRx+CEGZ6 04dQPkRk+0AwjtEt9N8dTzFyHVJVpO2xcdHuWhs=
X-Google-Smtp-Source: ABdhPJwrdidbbpxAlal26nas0YjVHn0Vkq2kzowJhmTlr/xxCTXMIGBiz1MwYofa2vpVj0Jv+BYWaGj7TrXJDYy5zuI=
X-Received: by 2002:a17:90b:1d86:: with SMTP id pf6mr11729183pjb.104.1627380408074;  Tue, 27 Jul 2021 03:06:48 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com>  <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org>
In-Reply-To: <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org>
From: Glyn Normington 
Date: Tue, 27 Jul 2021 11:06:35 +0100
Message-ID: 
To: Carsten Bormann 
Cc: jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002348da05c81807a6"
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 10:06:54 -0000

--0000000000002348da05c81807a6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 27 Jul 2021, 10:29 Carsten Bormann,  wrote:

> On 2021-07-27, at 10:38, Glyn Normington 
> wrote:
> >
> > "This string SHOULD be a valid regular expression, according to the
> ECMA-262 regular expression dialect."
>
> ECMA-262 is a moving target, the there is not really a single =E2=80=9CEC=
MA-262
> regular expression dialect=E2=80=9D; but that is easy to solve by referri=
ng to an
> ECMA-262 edition of a specific year.
>
> For a few years, the functionality supported by ECMA-262 regular
> expressions has expanded significantly.  With today=E2=80=99s extent, sup=
porting
> ECMA-262 regular expressions would require months of implementation effor=
t.
>
> This is easy to do if your code runs in a recent JavaScript environment.
> It is mostly impractical (dwarfing any JSONpath effort) if your platform
> does not already have an ECMA-262 regexp implementation around.
>
> So this is one of those SHOULDs that really mean =E2=80=9CSHOULD, but we =
know you
> won=E2=80=99t=E2=80=9D.  Why write something like this into a standard?  =
This only makes
> sense if interoperability is not the main goal.
>
> Every competent engineer can implement XSD regexps (and more so the
> iregexp subset) in less than a week.  So if we care about interoperabilit=
y,
> this is more likely to yield it.
>
> By the way, json-schema.org had a more practical approach 8 months ago:
>
>
> https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#sectio=
n-6.4
>
> This isn=E2=80=99t really specified very well, but if one sat down and di=
d, it
> would be closer to the iregexp approach at least in aspiration (it is sti=
ll
> littered with the useless kind of SHOULD I mentioned above).
>
> The iregexp approach uses the XSD choice of anchoring both sides of the
> expression, because that is always what you want in matching operation (i=
t
> is easy to add .* if it is not).  ECMA-262 of course has parsing regular
> expressions, so you have to add ^ and $ for essentially all expressions.
>
> It may be a useful approach to support different regexp modules by
> explicitly indicating the dialect at hand, with iregexp as the Rosetta
> Stone that can work everywhere.  This works great both for JSONPath users
> that don=E2=80=99t care about interoperability (because they are writing =
their
> JSONPath for a specific server implementation) and for ones that need
> interoperability.
>

Another class of JSONPath users who don't care about regexp
interoperability is those who don't use regexps.

>
> Gr=C3=BC=C3=9Fe, Carsten
>
>

--0000000000002348da05c81807a6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable




On Tue, 27 Jul 2021, 10:29 Carsten Bormann, <cabo@tzi.org=
> wrote:
On 2021-07-27, at 1=
0:38, Glyn Normington <glyn.normington.work@gmail=
.com> wrote:

> 

> "This string SHOULD be a valid regular expression, according to t=
he ECMA-262 regular expression dialect."



ECMA-262 is a moving target, the there is not really a single =E2=80=9CECMA=
-262 regular expression dialect=E2=80=9D; but that is easy to solve by refe=
rring to an ECMA-262 edition of a specific year.



For a few years, the functionality supported by ECMA-262 regular expression=
s has expanded significantly.=C2=A0 With today=E2=80=99s extent, supporting=
 ECMA-262 regular expressions would require months of implementation effort=
.



This is easy to do if your code runs in a recent JavaScript environment.=C2=
=A0 It is mostly impractical (dwarfing any JSONpath effort) if your platfor=
m does not already have an ECMA-262 regexp implementation around.



So this is one of those SHOULDs that really mean =E2=80=9CSHOULD, but we kn=
ow you won=E2=80=99t=E2=80=9D.=C2=A0 Why write something like this into a s=
tandard?=C2=A0 This only makes sense if interoperability is not the main go=
al.



Every competent engineer can implement XSD regexps (and more so the iregexp=
 subset) in less than a week.=C2=A0 So if we care about interoperability, t=
his is more likely to yield it.



By the way, json-schema.org had a more practical app=
roach 8 months ago:



=
https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-=
6.4



This isn=E2=80=99t really specified very well, but if one sat down and did,=
 it would be closer to the iregexp approach at least in aspiration (it is s=
till littered with the useless kind of SHOULD I mentioned above).



The iregexp approach uses the XSD choice of anchoring both sides of the exp=
ression, because that is always what you want in matching operation (it is =
easy to add .* if it is not).=C2=A0 ECMA-262 of course has parsing regular =
expressions, so you have to add ^ and $ for essentially all expressions.


It may be a useful approach to support different regexp modules by explicit=
ly indicating the dialect at hand, with iregexp as the Rosetta Stone that c=
an work everywhere.=C2=A0 This works great both for JSONPath users that don=
=E2=80=99t care about interoperability (because they are writing their JSON=
Path for a specific server implementation) and for ones that need interoper=
ability.

Another class of JSONPath users who don't care about regexp i=
nteroperability is those who don't use regexps.
=




Gr=C3=BC=C3=9Fe, Carsten






--0000000000002348da05c81807a6--


From nobody Tue Jul 27 03:41:16 2021
Return-Path: 
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 4A8D13A1F24 for ; Tue, 27 Jul 2021 03:41:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 bOH5K51qEYM9 for ; Tue, 27 Jul 2021 03:41:09 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D3423A1F23 for ; Tue, 27 Jul 2021 03:41:09 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GYtcf6nBNz31M6; Tue, 27 Jul 2021 12:41:06 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann 
In-Reply-To: <5E23EAD1-AF27-4E7E-9D1B-20FC4E74615F@saxonica.com>
Date: Tue, 27 Jul 2021 12:41:06 +0200
Cc: Glyn Normington , jsonpath@ietf.org, Greg Dennis 
X-Mao-Original-Outgoing-Id: 649075266.7323771-808d99b811987787397ba92c98ae82e6
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E207AA9-AC28-463E-8170-700D58F6581F@tzi.org>
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com>  <5E23EAD1-AF27-4E7E-9D1B-20FC4E74615F@saxonica.com>
To: Michael Kay 
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 10:41:14 -0000

On 2021-07-27, at 11:02, Michael Kay  wrote:
>=20
> If you're going to go for ECMA-262, make it ECMA-262 in Unicode ("u") =
mode.

Of course!
Sorry, I didn=E2=80=99t even think that needed mentioning.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Jul 27 04:29:52 2021
Return-Path: 
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 D112A3A207E for ; Tue, 27 Jul 2021 04:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Q2QhTPjb9qTD for ; Tue, 27 Jul 2021 04:29:47 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C40F13A207D for ; Tue, 27 Jul 2021 04:29:46 -0700 (PDT)
Received: from [192.168.178.20] ([88.130.51.231]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MirSu-1lTWLC2Kou-00evQR; Tue, 27 Jul 2021 13:29:34 +0200
To: Carsten Bormann , Glyn Normington 
Cc: jsonpath@ietf.org
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com>  <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org>
From: =?UTF-8?Q?Stefan_G=c3=b6ssner?= 
Message-ID: <54f5c891-d90f-a39d-6ab7-c9d5531f210e@goessner.net>
Date: Tue, 27 Jul 2021 13:29:34 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org>
Content-Type: multipart/alternative; boundary="------------2975057DC812CD435B070634"
X-Provags-ID: V03:K1:gXrev2lDMJottodmymEVLWYs2PXV8Bru+9YMAD866WM/Ryp2rJk ytKRVLkdDPzuQDjhPnuiRCtW9P4RuzoapuUUZlw+S9K/salCeeeTCVgjc9XUqewFcswGh1E IEr7cBeJPuuC822ZRkGJe7jmieBU6amvRELANNo/y5DEpO5PE3Sm/6KBPDOnaolHOTfFB8F NGw85RlankrXFXISbLxuA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:gYDxuWDU9+Y=:5ZPhCgSLesfo5d9CsFPYxz bKQQ94zyXfzJ0pDpZ8yifOPvxs41hmEeDtVqcsyIWWwGh7AK6TwbXbmElQ/r9gDc/1hdG6gQz MpASe1G0H4oQ3lxJ5dCozYQciRaGClJoxqWIMyUndLD4jEwfvQk7bzfOzG9jFWnK7xs3g3IZN /VxKG+x9bqi6ZKKXxjrEjBBYNbkJWlS8nNwLd9V+NPCxdaL6uIDSiqOF0nyIqrx4xipy8ojz1 9Zo1+KtLGcWrkKFx0nq9wLB2SvCUl3Ep6rBv8Jz0XEVizD6CSGYaIenAGRut66juLgEtWIKlv we1LjX9ulie4otwHfeyMUMvx83DG8TOPvqa8QiRdiGZrtv7TnfBwqoRkP9LcktDm+C8ztwR5M PGvsAyjw1IusvTZzdd1fqOUABQv/hdfsuQ/2mbq5wndEisj9OWkJZBTx3I4SrbClp9V3+ds+7 3vjWXtIqFBJJWRdeTcgaNFZgJStqhEPG+ORRs7mIiA2yFkiv/1o/SMzLT/JrDM0RFtIV/Cqu1 OzWb1rKQOTJpue4iDDDugGUkXyDUDYaWTPpVUSPMYVCxUAWQ05FGDR45Ev2xAoF2pLwWsR/in yE7pujoBoH6v8RXrOCNlKS+4K+sXDtZtTm96bFBSNZbR2+nqDkjps1332g2CivbTjNWAmbIhn oDOurMhEHPeD4E/gve06RaBvy1lujQMumOP+tVH27VnNVzBikbEjfmszekGEPEYeHiIMft3oe AU//lqJuA/qix29LJwUJo7C8qSzkk2oBn+Gecc5ssR3pBcJA7SFMLzcihwxXRpcCL2oJLB0YF ZfPCYKn7we1fFvqkbAGGvutCVShHq4VbLL56Kd0wtEiUIiLwn67ray5cWzljhLt4BQ/CsIAB8 /Coponza2qslEoDy+lLQ==
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 11:29:52 -0000

This is a multi-part message in MIME format.
--------------2975057DC812CD435B070634
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Addressing ...

Users: They only want to know, if the JSONPath implementation used 
conforms to the spec regarding regexp ... if they are interested in 
regexps at all.

Implementors: They need to know, if the regexp library they want to use 
with their JSONPath implementation conforms to the spec.

So I think, having with I-Regexp a reference to an interoperable flavor 
of regexps is a good thing.
--
sg




Am 27.07.2021 um 11:29 schrieb Carsten Bormann:
> On 2021-07-27, at 10:38, Glyn Normington  wrote:
>> "This string SHOULD be a valid regular expression, according to the ECMA-262 regular expression dialect."
> ECMA-262 is a moving target, the there is not really a single “ECMA-262 regular expression dialect”; but that is easy to solve by referring to an ECMA-262 edition of a specific year.
>
> For a few years, the functionality supported by ECMA-262 regular expressions has expanded significantly.  With today’s extent, supporting ECMA-262 regular expressions would require months of implementation effort.
>
> This is easy to do if your code runs in a recent JavaScript environment.  It is mostly impractical (dwarfing any JSONpath effort) if your platform does not already have an ECMA-262 regexp implementation around.
>
> So this is one of those SHOULDs that really mean “SHOULD, but we know you won’t”.  Why write something like this into a standard?  This only makes sense if interoperability is not the main goal.
>
> Every competent engineer can implement XSD regexps (and more so the iregexp subset) in less than a week.  So if we care about interoperability, this is more likely to yield it.
>
> By the way, json-schema.org had a more practical approach 8 months ago:
>
> https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-6.4
>
> This isn’t really specified very well, but if one sat down and did, it would be closer to the iregexp approach at least in aspiration (it is still littered with the useless kind of SHOULD I mentioned above).
>
> The iregexp approach uses the XSD choice of anchoring both sides of the expression, because that is always what you want in matching operation (it is easy to add .* if it is not).  ECMA-262 of course has parsing regular expressions, so you have to add ^ and $ for essentially all expressions.
>
> It may be a useful approach to support different regexp modules by explicitly indicating the dialect at hand, with iregexp as the Rosetta Stone that can work everywhere.  This works great both for JSONPath users that don’t care about interoperability (because they are writing their JSONPath for a specific server implementation) and for ones that need interoperability.
>
> Grüße, Carsten
>


--------------2975057DC812CD435B070634
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit


  
    
  
  
    Addressing ...

        

        Users: They only want to know, if the JSONPath implementation
        used conforms to the spec regarding regexp ... if they are
        interested in regexps at all.

        

        Implementors: They need to know, if the regexp library they want
        to use with their JSONPath
            implementation conforms to the spec.

            

            So I think, having with I-Regexp a reference to an interoperable flavor of regexps is a good
            thing.

            --

            sg

            

            

            

            

          
    
Am 27.07.2021 um 11:29 schrieb Carsten
      Bormann:

    

    

      
On 2021-07-27, at 10:38, Glyn Normington <glyn.normington.work@gmail.com> wrote:


      

        
"This string SHOULD be a valid regular expression, according to the ECMA-262 regular expression dialect."


      

      
ECMA-262 is a moving target, the there is not really a single “ECMA-262 regular expression dialect”; but that is easy to solve by referring to an ECMA-262 edition of a specific year.

For a few years, the functionality supported by ECMA-262 regular expressions has expanded significantly.  With today’s extent, supporting ECMA-262 regular expressions would require months of implementation effort.

This is easy to do if your code runs in a recent JavaScript environment.  It is mostly impractical (dwarfing any JSONpath effort) if your platform does not already have an ECMA-262 regexp implementation around.

So this is one of those SHOULDs that really mean “SHOULD, but we know you won’t”.  Why write something like this into a standard?  This only makes sense if interoperability is not the main goal.

Every competent engineer can implement XSD regexps (and more so the iregexp subset) in less than a week.  So if we care about interoperability, this is more likely to yield it.

By the way, json-schema.org had a more practical approach 8 months ago:

https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-6.4

This isn’t really specified very well, but if one sat down and did, it would be closer to the iregexp approach at least in aspiration (it is still littered with the useless kind of SHOULD I mentioned above).

The iregexp approach uses the XSD choice of anchoring both sides of the expression, because that is always what you want in matching operation (it is easy to add .* if it is not).  ECMA-262 of course has parsing regular expressions, so you have to add ^ and $ for essentially all expressions.

It may be a useful approach to support different regexp modules by explicitly indicating the dialect at hand, with iregexp as the Rosetta Stone that can work everywhere.  This works great both for JSONPath users that don’t care about interoperability (because they are writing their JSONPath for a specific server implementation) and for ones that need interoperability.

Grüße, Carsten



    

    

  


--------------2975057DC812CD435B070634--


From nobody Tue Jul 27 04:40:40 2021
Return-Path: 
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 B91C33A20E0 for ; Tue, 27 Jul 2021 04:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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=gmail.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 qhaZyDApkIo4 for ; Tue, 27 Jul 2021 04:40:34 -0700 (PDT)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (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 0102E3A20DE for ; Tue, 27 Jul 2021 04:40:33 -0700 (PDT)
Received: by mail-pl1-x62c.google.com with SMTP id t21so15313280plr.13 for ; Tue, 27 Jul 2021 04:40:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6zjzmHUTW5J2rem/yCzwGSBkKpquhpWL+jZCGOfYNLk=; b=ftE8imzT0iFEvPES4ClCCDVDUZo5dpK66fJbfSMIZYOQpWJB2XVv1lIB/t0oi5s01E x1sjbz9sv4/GJKekCyIbaZxd4odsCEUg5zHf+mVIFwXmT2aIjcOzfemB7Tdq+Yyq/xqI nE0kikY0XmxZHoew6bW3JaH4xKbZsSl+7x264WmquYTiD89pd+k5dUZ00teSv+lr4lyn swxlp4iyhz5ynikRtKTLFdxBqV5JiT7jWkqG/VWtGyxFf1HJkrAFs+C3Jh2/xVFf0LP3 WhqwGNJNzUzXfV6MPaX69ZRqVTomBPfk3IXZLwKHD5+LN8R0YveRl8/RToDboY1HeF6C HgSg==
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=6zjzmHUTW5J2rem/yCzwGSBkKpquhpWL+jZCGOfYNLk=; b=Fk6bFgys4fcbA5mgFZ8lWjFAICx05hKuvN+bEecbyK5dSD7ycUP1HXSs4uUnqDnOFo L2qJHetXr0ZROpgdFsKf56/1+wr1exbIQDMNFaoRr/PNvuU3l0X2tbWz6KQPuvfJ9APv a1cRpl8WOrFopJOqzDoQYBcxGykdRSLEv5n3H/B33k4lDZ06slk9+ZWPJMrPzJymwm+K yQoK7Ryj3ur5Rbao8H26Zrfns7mf/B67ZuzhbFAacip9Jf8e9ihQLnUwergyQXphXGGC Rtqx9uWQ4OlayQdeRPfTRewTevZnDkEHC0pRGFCnOzkMcdJ4pYWT07HJo2PWysn7VgR2 3vKQ==
X-Gm-Message-State: AOAM532Gcru+GOM01DdHCkJe6eGsdCs7tG+kWjYFsAz2bEQqfN+86dwX Rr3lKgTZdjM7I7429JE6u1UZyb0LkeMp75nH4TY=
X-Google-Smtp-Source: ABdhPJyPlE7SteiTuyrYLnnhx3e/idxOyAXiUIarhzLuFNKt+/6FX/e2a+H1L/E8BSrNJ9tPOQ4I5CrbYNZYUzTRQBQ=
X-Received: by 2002:a17:902:f681:b029:12c:d3a:61a2 with SMTP id l1-20020a170902f681b029012c0d3a61a2mr10851597plg.62.1627386032871; Tue, 27 Jul 2021 04:40:32 -0700 (PDT)
MIME-Version: 1.0
References:  <675E1A53-AB3B-4FAA-A299-1B71B091CE8F@tzi.org> <7DCDCEAE-454D-4380-9608-1A850D4D8B19@tzi.org>  <1247207623.69360.1627371787010@mail.yahoo.com>  <75488139-A9D9-45C4-AE89-ACDE78313854@tzi.org> <54f5c891-d90f-a39d-6ab7-c9d5531f210e@goessner.net>
In-Reply-To: <54f5c891-d90f-a39d-6ab7-c9d5531f210e@goessner.net>
From: Glyn Normington 
Date: Tue, 27 Jul 2021 12:40:20 +0100
Message-ID: 
To: =?UTF-8?Q?Stefan_G=C3=B6ssner?= 
Cc: Carsten Bormann , jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="00000000000066dc4e05c81956f9"
Archived-At: 
Subject: Re: [Jsonpath] Compliance levels/modules/features (Re: JSONPath meeting at IETF 111)
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 
List-Unsubscribe: , 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: , 
X-List-Received-Date: Tue, 27 Jul 2021 11:40:39 -0000

--00000000000066dc4e05c81956f9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I agree the anticipated interoperability of iregexp will be valuable. I was
trying to explore how tightly coupled the JSONPath spec needs to be to a
regexp spec. It seems the conclusion we are coming to is: pretty tightly
coupled.

On Tue, 27 Jul 2021, 12:29 Stefan G=C3=B6ssner,  wrote=
:

> Addressing ...
>
> Users: They only want to know, if the JSONPath implementation used
> conforms to the spec regarding regexp ... if they are interested in regex=
ps
> at all.
>
> Implementors: They need to know, if the regexp library they want to use
> with their JSONPath implementation conforms to the spec.
>
> So I think, having with I-Regexp a reference to an interoperable flavor
> of regexps is a good thing.
> --
> sg
>
>
>
>
> Am 27.07.2021 um 11:29 schrieb Carsten Bormann:
>
> On 2021-07-27, at 10:38, Glyn Normington =
  wrote:
>
>
> "This string SHOULD be a valid regular expression, according to the ECMA-=
262 regular expression dialect."
>
>
> ECMA-262 is a moving target, the there is not really a single =E2=80=9CEC=
MA-262 regular expression dialect=E2=80=9D; but that is easy to solve by re=
ferring to an ECMA-262 edition of a specific year.
>
> For a few years, the functionality supported by ECMA-262 regular expressi=
ons has expanded significantly.  With today=E2=80=99s extent, supporting EC=
MA-262 regular expressions would require months of implementation effort.
>
> This is easy to do if your code runs in a recent JavaScript environment. =
 It is mostly impractical (dwarfing any JSONpath effort) if your platform d=
oes not already have an ECMA-262 regexp implementation around.
>
> So this is one of those SHOULDs that really mean =E2=80=9CSHOULD, but we =
know you won=E2=80=99t=E2=80=9D.  Why write something like this into a stan=
dard?  This only makes sense if interoperability is not the main goal.
>
> Every competent engineer can implement XSD regexps (and more so the irege=
xp subset) in less than a week.  So if we care about interoperability, this=
 is more likely to yield it.
>
> By the way, json-schema.org had a more practical approach 8 months ago:
> https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-00#sectio=
n-6.4
>
> This isn=E2=80=99t really specified very well, but if one sat down and di=
d, it would be closer to the iregexp approach at least in aspiration (it is=
 still littered with the useless kind of SHOULD I mentioned above).
>
> The iregexp approach uses the XSD choice of anchoring both sides of the e=
xpression, because that is always what you want in matching operation (it i=
s easy to add .* if it is not).  ECMA-262 of course has parsing regular exp=
ressions, so you have to add ^ and $ for essentially all expressions.
>
> It may be a useful approach to support different regexp modules by explic=
itly indicating the dialect at hand, with iregexp as the Rosetta Stone that=
 can work everywhere.  This works great both for JSONPath users that don=E2=
=80=99t care about interoperability (because they are writing their JSONPat=
h for a specific server implementation) and for ones that need interoperabi=
lity.
>
> Gr=C3=BC=C3=9Fe, Carsten
>
>
>
>

--00000000000066dc4e05c81956f9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


I agree the anticipated interoperability of iregexp will =
be valuable. I was trying to explore how tightly coupled the JSONPath spec =
needs to be to a regexp spec. It seems the conclusion we are coming to is: =
pretty tightly coupled.

On Tue, 27 Jul 2021, 12:29 Stefan G=C3=B6ssner, <=
stefan@goessner.net> wrote:

 =20
   =20
 =20
  

    Addressing ...

        

        Users: They only want to know, if the JSONPath implementation
        used conforms to the spec regarding regexp ... if they are
        interested in regexps at all.

        

        Implementors: They need to know, if the regexp library they want
        to use with their JSONPath
            implementation conforms to the spec.

            

            So I think, having with I-Regexp a reference to an interoperable flavor of regexps is a good
            thing.

            --

            sg

            

            

            

            

          
    
Am 27.07.2021 um 11:29 schrieb Carsten
      Bormann:

    

    

      
On 2021-07-27, at 10:38, Glyn Normington =
<glyn.normington.work@gmail.com> wrote:


      

        
"This string SHOULD be a valid regular expression, according to the EC=
MA-262 regular expression dialect."


      

      
ECMA-262 is a moving target, the there is not really a single =E2=80=9CECMA=
-262 regular expression dialect=E2=80=9D; but that is easy to solve by refe=
rring to an ECMA-262 edition of a specific year.

For a few years, the functionality supported by ECMA-262 regular expression=
s has expanded significantly.  With today=E2=80=99s extent, supporting ECMA=
-262 regular expressions would require months of implementation effort.

This is easy to do if your code runs in a recent JavaScript environment.  I=
t is mostly impractical (dwarfing any JSONpath effort) if your platform doe=
s not already have an ECMA-262 regexp implementation around.

So this is one of those SHOULDs that really mean =E2=80=9CSHOULD, but we kn=
ow you won=E2=80=99t=E2=80=9D.  Why write something like this into a standa=
rd?  This only makes sense if interoperability is not the main goal.

Every competent engineer can implement XSD regexps (and more so the iregexp=
 subset) in less than a week.  So if we care about interoperability, this i=
s more likely to yield it.

By the way, json-schema.org had a more practical approach 8 mon=
ths ago:

https://dat=
atracker.ietf.org/doc/html/draft-bhutton-json-schema-00#section-6.4

This isn=E2=80=99t really specified very well, but if one sat down and did,=
 it would be closer to the iregexp approach at least in aspiration (it is s=
till littered with the useless kind of SHOULD I mentioned above).

The iregexp approach uses the XSD choice of anchoring both sides of the exp=
ression, because that is always what you want in matching operation (it is =
easy to add .* if it is not).  ECMA-262 of course has parsing regular expre=
ssions, so you have to add ^ and $ for essentially all expressions.

It may be a useful approach to support different regexp modules by explicit=
ly indicating the dialect at hand, with iregexp as the Rosetta Stone that c=
an work everywhere.  This works great both for JSONPath users that don=E2=
=80=99t care about interoperability (because they are writing their JSONPat=
h for a specific server implementation) and for ones that need interoperabi=
lity.

Gr=C3=BC=C3=9Fe, Carsten



    

    

  





--00000000000066dc4e05c81956f9--