IETF Logo Mail Archive

Re: [xml2rfc] Error: Did not expect element figure

Carsten Bormann <cabo@tzi.org> Mon, 03 July 2023 07:29 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9D4C14CE2F for <xml2rfc@ietfa.amsl.com>; Mon, 3 Jul 2023 00:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 vluUjwjbBMNf for <xml2rfc@ietfa.amsl.com>; Mon, 3 Jul 2023 00:29:19 -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 C5389C14CF18 for <xml2rfc@ietf.org>; Mon, 3 Jul 2023 00:29:17 -0700 (PDT)
Received: from client-0227.vpn.uni-bremen.de (client-0227.vpn.uni-bremen.de [134.102.107.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4QvcxR07c8zDCdW; Mon, 3 Jul 2023 09:29:14 +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 <cabo@tzi.org>
In-Reply-To: <8b7e1864-d18d-0218-49b2-b6ff80a11653@gmx.de>
Date: Mon, 03 Jul 2023 09:29:14 +0200
Cc: xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 710062154.500553-b8da113ad8525526e56d7e3737d20357
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3B79B43-3370-4489-A06C-1971BAC87DED@tzi.org>
References: <1481bb7d-38fd-4b66-5eb0-be9e06f59bd1@htt-consult.com> <C9A25BBD-7FB1-4007-86F9-4110B2772DD8@staff.ietf.org> <F36D9AB5-F863-40B3-88F6-AF982EEA5673@tzi.org> <8b7e1864-d18d-0218-49b2-b6ff80a11653@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/eCDb8PBWcNNv9ZmfbEoPgap2eoI>
Subject: Re: [xml2rfc] Error: Did not expect element figure
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: Mon, 03 Jul 2023 07:29:23 -0000

On 2023-07-02, at 19:34, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> It's a block level element, and since v3 it can't appear *inside* a
> paragraph anymore.

Right, which of course makes sense for the *publishing* personality of RFCXMLv3.

For the *authoring* side, this just makes life harder for those of us who evolve RFCs over a longer time frame than the short life of the v3 tools.

Interestingly, xml2rfc --v2v3 (tested with 3.17.4) happily spits out XML that is marked as »version=“3”« but does not conform to the new restricted syntax, so even a “why don’t you convert your dusty decks to v3 first” approach doesn’t work.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email