IETF Logo Mail Archive

Re: [Jsonpath] Hex in jsonpath

Carsten Bormann <cabo@tzi.org> Sat, 05 August 2023 18:17 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: jsonpath@ietfa.amsl.com
Delivered-To: jsonpath@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5BCC14CE4C for <jsonpath@ietfa.amsl.com>; Sat, 5 Aug 2023 11:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aUHRKm1Z7aTS for <jsonpath@ietfa.amsl.com>; Sat, 5 Aug 2023 11:17:36 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA7E4C14F726 for <jsonpath@ietf.org>; Sat, 5 Aug 2023 11:17:34 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:20:12:b819:70cc:6fba:3aad:9396]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RJ9mB2x5dzDCcN; Sat, 5 Aug 2023 20:17:30 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail-52777779-75F2-44DF-971B-B6A4A4953B01"
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Mime-Version: 1.0 (1.0)
Date: Sat, 05 Aug 2023 20:17:19 +0200
Message-Id: <FD89258A-7F9A-46E0-A5A1-A72A8799C7ED@tzi.org>
References: <m2sf8xz9ye.fsf@nwalsh.com>
Cc: Glyn Normington <glyn.normington.work@gmail.com>, jsonpath@ietf.org
In-Reply-To: <m2sf8xz9ye.fsf@nwalsh.com>
To: Norm Tovey-Walsh <ndw@nwalsh.com>
X-Mailer: iPhone Mail (20G75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/l6ADn8Gu1FO-p3spipb8zcmX5_c>
Subject: Re: [Jsonpath] Hex in jsonpath
X-BeenThere: jsonpath@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A summary description of the list to be included in the table on this page <jsonpath.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jsonpath/>
List-Post: <mailto:jsonpath@ietf.org>
List-Help: <mailto:jsonpath-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Aug 2023 18:17:39 -0000


Sent from mobile, sorry for terse

> On 5. Aug 2023, at 19:16, Norm Tovey-Walsh <ndw@nwalsh.com> wrote:
> 
> Constructing the whole grammar in a single file from the various
>   fragments scattered through the spec was a bit tedious.

The repo has a tool for that, under scripts iirc. The tool kramdown-rfc-extract-sourcecode should work even without that. 

I would give examples if I had a keyboard right now…

v2.46.0 | Report a Bug | By Email | System Status