Re: [Jsonpath] Milestones changed for jsonpath WG

What a pleasant surprise on my return from a long journey.

Congratulations and thank you for successfully (almost) finalizingthe spec.

Our collaborative work was a fascinating experience for me and I look 
forward to seeing what else may happen on the last mile.
--
Stefan

Am 02.10.2023 um 08:33 schrieb Tim Bray:
> I'm generally pleased with their work. They provide exhaustive diffs 
> and highlight any changes of any import. Their job is to add polish 
> and professionalism. On occasions where I've objected to a change, 
> they've deferred.
>
> On Sun, Oct 1, 2023, 11:19 p.m. Glyn Normington 
> <glyn.normington.work@gmail.com> wrote:
>
>     Hi Carsten
>
>     Thanks for that excellent summary for us uninitiated! It will be
>     fascinating to see what changes the RFC Editor makes (proposes?)
>     with a fresh pair of eyes.
>
>     Regards,
>     Glyn
>
>     On Mon, 2 Oct 2023, 06:48 Carsten Bormann, <cabo@tzi.org> wrote:
>
>         On 2. Oct 2023, at 06:26, Greg Dennis
>         <gregsdennis=40yahoo.com@dmarc.ietf.org> wrote:
>         >
>         > So does that mean we have an official spec?
>
>         Both jsonpath-base and iregexp are approved documents.
>
>         (The milestone updates this is replying to are about events
>         that already have happened earlier: submission of the
>         documents to IESG, i.e., after the Working Group Last Call
>         procedure completed.)
>
>         > I don't see an RFC number or anything.
>
>         You can see the status here:
>
>         https://datatracker.ietf.org/doc/search?name=jsonpath&sort=&rfcs=on&activedrafts=on
>         <https://datatracker.ietf.org/doc/search?name=jsonpath&sort=&rfcs=on&activedrafts=on>
>
>         iregexp is in AUTH48, i.e., the RFC editor has completed their
>         work and has had feedback with the authors with respect to the
>         edits they have applied. (Actually, it should be in
>         AUTH48-DONE now; we are waiting for Murray’s final go ahead
>         only.)  We already know the RFC number, but the RFC is not
>         published yet; I’d expect this to happen approximately this week.
>
>         Jsonpath-base is in EDIT, i.e., the RFC editor is editing it. 
>         This will probably take a couple of months; I’d expect it to
>         reach AUTH48 by December, and it probably will be published
>         this year.
>
>         The RFC editor page for the “cluster” of documents is at:
>
>         https://www.rfc-editor.org/auth48/C490
>         And yes, that cluster includes the first RFC-to-be that is
>         relying on JSONPath, too!
>
>         If you want to see the status of all documents currently being
>         processed by the RFC editor in their various states, please
>         look here:
>         https://www.rfc-editor.org/current_queue.php#draft-ietf-jsonpath-base
>
>         Grüße, Carsten
>
>         -- 
>         JSONpath mailing list
>         JSONpath@ietf.org
>         https://www.ietf.org/mailman/listinfo/jsonpath
>
>