IETF Logo Mail Archive

Re: [Rfc-markdown] [xml2rfc] Is the --v3 switch still needed?

Carsten Bormann <cabo@tzi.org> Sun, 24 October 2021 16:33 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D52213A07CC; Sun, 24 Oct 2021 09:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 t2JVh7OGp5TR; Sun, 24 Oct 2021 09:33:29 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.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 B6FE73A079D; Sun, 24 Oct 2021 09:33:29 -0700 (PDT)
Received: from [192.168.217.118] (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (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 4HckD71DNcz30SP; Sun, 24 Oct 2021 18:33:27 +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: <ab61777c-5446-c7c8-1ba1-ec8d8bde2cd4@htt-consult.com>
Date: Sun, 24 Oct 2021 18:33:26 +0200
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 656786006.353845-fbba82cac6cbbea70b7ff0c94f787f1f
Reply-To: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A985F36-1332-497F-8DDC-2531245FA8A3@tzi.org>
References: <ab61777c-5446-c7c8-1ba1-ec8d8bde2cd4@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/6_wevlKD0YZihthjMaL-HXDDKU4>
Subject: Re: [Rfc-markdown] [xml2rfc] Is the --v3 switch still needed?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2021 16:33:34 -0000

On 2021-10-24, at 17:07, Robert Moskowitz <rgm@htt-consult.com> wrote:
> 
> Do we still need to include the --v3 switch on the command line?
> 
> particularly if we have
> 
> <rfc ... version="3">
> 
> getting tired typing it in all the time...

It is generally a big thing to change a command line interface, as the command may be embedded in a lot of scripts (it certainly is for xml2rfc), which then do unexpected things.

I happen to be thinking about a related kind of change for kdrfc, the “driver” command for kramdown-rfc2629.  That change would require some indication of v3ness in the markdown file; but maybe that same indication would be a nice way to get rid of needing to override old defaults (such as setting stand_alone: true, consensus: true if category: std; also the need to declare ipr: trust200902 or pi: [toc, sortrefs, symrefs, comments], etc.).

Feedback about the latter welcome to rfc-markdown@ietf.org.

Grüße, Carsten

v2.8.7 | Report a Bug | By Email