[xml2rfc-dev] When did v2v3 stop spewing redundant attributes?

Carsten Bormann <cabo@tzi.org> Sun, 27 February 2022 00:07 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E1B3A093B for <xml2rfc-dev@ietfa.amsl.com>; Sat, 26 Feb 2022 16:07:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R91B24rJlNfn for <xml2rfc-dev@ietfa.amsl.com>; Sat, 26 Feb 2022 16:07:15 -0800 (PST)
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 B392B3A0940 for <xml2rfc-dev@ietf.org>; Sat, 26 Feb 2022 16:07:15 -0800 (PST)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (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 4K5kMz0cPZzDCbV; Sun, 27 Feb 2022 01:07:10 +0100 (CET)
From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Sun, 27 Feb 2022 01:07:10 +0100
Message-Id: <681C8835-5154-4261-88CF-BE0AA90905FA@tzi.org>
To: XML2RFC Dev <xml2rfc-dev@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/Y-JlwXr3gTZhiFIJTaMyv2mUQdU>
Subject: [xml2rfc-dev] When did v2v3 stop spewing redundant attributes?
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Feb 2022 00:07:19 -0000

We have a little mystery over in https://github.com/cabo/kramdown-rfc/issues/162

The xml2rfc v2v3 code used to output redundant attributes of the form

<section anchor="sdfevent" numbered="true" toc="default”>

where numbered and toc have their default values (and weren’t set on the input side either).

This seems to have stopped with xml2rfc 3.12.1.

I have a few instances generated from 3.11.1 v2v3 that look like the above, and I have a few from the same version that look like

<section anchor="clarifications" toc="default”>

(i.e., one redundant attribute gone, one still there).

Previous versions (3.10.0 or earlier) consistently output the redundant attributes.

Now the mystery:
When downgrading to, say, 3.9.1, the problem does not recur (!).

Where was this fixed?  In xml2rfc or maybe some of its dependencies?

I’m not asking for the bug to be put back in, but it would help if we could understand what the shape of the set of instances is that have this problem.

(Note that this is a discussion about documents in processable form (“unprepped”, editable); not an attempt to bring up the discussion whether default values are needed in prepped (final published form) XML documents.)

Grüße, Carsten