IETF Logo Mail Archive

Re: [Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission

Carsten Bormann <cabo@tzi.org> Wed, 28 July 2021 10:01 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 4CC7C3A25D6 for <rfc-markdown@ietfa.amsl.com>; Wed, 28 Jul 2021 03:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 2QegZ6V5MCep for <rfc-markdown@ietfa.amsl.com>; Wed, 28 Jul 2021 03:01:05 -0700 (PDT)
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 A06C53A25D7 for <rfc-markdown@ietf.org>; Wed, 28 Jul 2021 03:01:05 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de [84.141.204.137]) (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 4GZTgs5tD2z2xMm; Wed, 28 Jul 2021 12:00:57 +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: <48cd298c-5ac5-fd6f-19b5-b0117b683c19@gmx.de>
Date: Wed, 28 Jul 2021 12:00:57 +0200
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 649159257.406296-684c4102655766c0c3164ad9b710073a
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D5AECC6-890F-4E89-B4DD-63A8EE6817FA@tzi.org>
References: <20210712034838.B461E209AFFB@ary.qy> <6c781dab-7a40-7031-be1c-d77a182f4cf4@gmail.com> <DE0CD982-D4BE-44A6-9234-B53A756E9717@mnot.net> <bbb8302a-4041-35db-ce61-d2a18b8ebeee@taugh.com> <AB6E5013-C14E-4962-8907-17F241971F9D@tzi.org> <20210719171839.GB24216@faui48e.informatik.uni-erlangen.de> <DBCC4252-8A2D-473C-82CD-B1B2688586D3@tzi.org> <777A0822-6C16-4967-ABD0-BD35359B9FC5@tzi.org> <974739FF-7EB8-475B-A6A9-CB096D567E91@tzi.org> <10368632-F4A3-4876-A4F0-81C3DDBE002F@mnot.net> <F5519EBC-E453-4552-8B7F-F34425DAD2A1@tzi.org> <F15694DF-6ACD-469F-9CA9-E33C5FC03223@mnot.net> <BC5E00A5-2FBF-45E4-985B-5E67935D3192@tzi.org> <078FD4CC-E219-43F5-8DCD-3C55D8ABEF6D@mnot.net> <9F805284-0053-4B5F-8F89-EF6B4BA48D4A@tzi.org> <7B98D0B6-0102-4CE4-B4D6-6FBA04033234@mnot.net> <48cd298c-5ac5-fd6f-19b5-b0117b683c19@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/rfc-markdown/xnWcdYvzetU9deHZJIUBWMq02vI>
Subject: Re: [Rfc-markdown] No longer need to run xml2rfc --v2v3 before I-D submission
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: Wed, 28 Jul 2021 10:01:10 -0000

On 2021-07-27, at 09:40, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> Just stop generating v2 :-)

There was a smiley here, but some people might take this at face value.

As long as

     <?rfc include="reference.RFC.2119”?>

no longer works in v3, I’ll recommend people who can’t (*) convert to markdown to stay with v2 (preferably processed in hybrid mode).

This one specimen is, of course, just an example of how v2 was designed a little bit more for authors, while v3 is prioritizing a form of standards compliance that actually is not giving us anything on the author side.

How is the below better than the above:

    <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>

The v3 version encodes a URI that is brittle (you would probably already tell me that the authority component is wrong now, and the path name also is brittle).  It requires xi:include processing in any additional author-side tools.  And it is impossible to type from memory.

I’m a German, so I do have the genes for excessive bureaucracy.
But this…  No.

Grüße, Carsten

(*) You co-author might retire soon and this is “their last RFC”, so they don’t want to learn something new while they have ingrained RFCXMLv2 skill.  Or some such.

v2.23.0 | Report a Bug | By Email