[Tools-discuss] Let's not be hostile to authors

Carsten Bormann <cabo@tzi.org> Sun, 27 June 2021 06:26 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7F53A1CFA for <tools-discuss@ietfa.amsl.com>; Sat, 26 Jun 2021 23:26: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 UivYZ4bi6XCz for <tools-discuss@ietfa.amsl.com>; Sat, 26 Jun 2021 23:26:06 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de [IPv6:2001:638:708:32::19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AC6E3A1CF9 for <tools-discuss@ietf.org>; Sat, 26 Jun 2021 23:26:06 -0700 (PDT)
Received: from smtpclient.apple (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-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GCLNC0DnVz2xHS; Sun, 27 Jun 2021 08:26:03 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <70fee53d-28b9-874a-6988-6c1234ca149@taugh.com>
Date: Sun, 27 Jun 2021 08:26:02 +0200
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, tools-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <55B80E3D-E22B-439F-9D5B-96185A1CE65B@tzi.org>
References: <20210627013258.1D30F188447C@ary.qy> <691b91b6-86d7-2a3d-b9dc-8c19cc507db4@gmail.com> <584d34d6-5630-bbb7-35cc-9459dabc80f0@taugh.com> <82887902-90d0-3616-656b-fc39e4febd47@gmail.com> <70fee53d-28b9-874a-6988-6c1234ca149@taugh.com>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Tm-q4B0wX87DzaIr9n0bFhb-jzk>
Subject: [Tools-discuss] Let's not be hostile to authors
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jun 2021 06:26:11 -0000

On 27. Jun 2021, at 04:40, John R Levine <johnl@taugh.com> wrote:
> 
>> Excellent. Is there any reason not to run the v2 to v3 converter automatically?
> 
> We really want people to stop using v2.  It's obsolete and missing some semantic features of v3.

John,

let me be blunt here.

The attitude that it is OK to be hostile to document authors in order to further some meaningless abstract goal is completely unacceptable and has to stop.

There are good reasons to continue submitting v2 or v2-with-v3 documents.

For people actually authoring in XML, the version control history of all but the most recently started documents is in v2.  A wholesale v3 conversion loses all that history.

For people using a tool to generate the XML, it is unacceptable to require their tools to generate exactly the v3 of the day, in particular as xml2rfc has a perfect v3 generator inside, which by the nature of the process is more likely to stay in sync with the ongoing fixes to v3.

And, in case I haven't been clear enough, the needs (and even more so the wants!) of the RPC are entirely secondary to those of the authors here, as 98 % of the work on a document happens before the RPC gets it, and the resources feeding that work are non-renewable.

(And yes, the abstract goal of furthering the v3 transition is not entirely meaningless in the long run, but we are *way* off from that goal being a realistic short-term objective.  And the feature of xml2rfc to be more permissive in its converter input than the v3 publishing format must *never* go away, at least as long as we consider the time and quality of work of our authors and tool makers to be a precious resource.)

Grüße, Carsten