[xml2rfc] draft-petithuguenin-computerate-specification-00 [was Re: Fwd: I-D Action: draft-petithuguenin-xml2rfc-asciidoc-00.txt]

Marc Petit-Huguenin <marc@petit-huguenin.org> Tue, 07 February 2023 14:49 UTC

Return-Path: <marc@petit-huguenin.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id DA654C1782BC for <xml2rfc@ietfa.amsl.com>; Tue, 7 Feb 2023 06:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id JgyWd522FMXy for <xml2rfc@ietfa.amsl.com>; Tue, 7 Feb 2023 06:49:46 -0800 (PST)
Received: from implementers.org (implementers.org []) (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 29502C1782BF for <xml2rfc@ietf.org>; Tue, 7 Feb 2023 06:49:45 -0800 (PST)
Received: from [IPV6:2601:204:e37f:a6af:d250:99ff:fedf:93cf] (unknown [IPv6:2601:204:e37f:a6af:d250:99ff:fedf:93cf]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id ACBB2AE230 for <xml2rfc@ietf.org>; Tue, 7 Feb 2023 15:49:42 +0100 (CET)
Message-ID: <15decdb1-5130-8555-f8d5-11277eabb180@petit-huguenin.org>
Date: Tue, 07 Feb 2023 06:49:39 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: xml2rfc list <xml2rfc@ietf.org>
References: <166610588585.1969.13583330647247455526@ietfa.amsl.com> <a839ad82-99c5-8d97-05cc-92ec43df1e08@petit-huguenin.org>
Content-Language: en-US
In-Reply-To: <a839ad82-99c5-8d97-05cc-92ec43df1e08@petit-huguenin.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------4GA2SR3yVBIIqlrxnh1Ey01H"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/XVYdR6Nt9Dl0ewF7cP64zgedZTI>
Subject: [xml2rfc] draft-petithuguenin-computerate-specification-00 [was Re: Fwd: I-D Action: draft-petithuguenin-xml2rfc-asciidoc-00.txt]
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2023 14:49:49 -0000

I just submitted an I-D that explains how to write Internet-Drafts that are partially generated by code that is embedded in the source of the I-Ds:


Just imagine how that would make the Internet work better if the examples in an I-D were generated using verified programming, the ABNF checked for validity each time a version of a draft is submitted, or denominate numbers used to make the conversion between bits, bytes and other units or dimensions.  All of this and more is now possible with the tooling distributed with that I-D.

On 10/18/22 08:28, Marc Petit-Huguenin wrote:
> FYI I just released a new mapping between XML2RFC v3 and AsciiDoc and an implementation of this mapping as a backend for asciidoctor.
> This is still work in progress: The goal is to be able to convert any AsciiDoc document into a valid XML2RFC v3 file, but for that release the goal was to be able to generate any XML2RFC v3 from a subset/superset of AsciiDoc, subset/superset that is fully described in the I-D.
> In itself this work may seem redundant with other markdown languages to XML2RFC v3 efforts, but it will all make sense when I publish the second I-D and tool in the series (hopefully during IETF 115), which will add the ability of mixing code in a document to compute parts of the generated XML2RFC file.

Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug