Re: [Tools-discuss] Why post text and not XML?

John C Klensin <john-ietf@jck.com> Sun, 17 March 2024 17:18 UTC

Return-Path: <john-ietf@jck.com>
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 10F78C14F5FD; Sun, 17 Mar 2024 10:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jyrPWPkletqg; Sun, 17 Mar 2024 10:18:34 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBC5AC14F5F9; Sun, 17 Mar 2024 10:18:30 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1rlu9T-00058i-ST; Sun, 17 Mar 2024 13:18:27 -0400
Date: Sun, 17 Mar 2024 13:18:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: Julian Reschke <julian.reschke=40gmx.de@dmarc.ietf.org>, tools-discuss@ietf.org
Message-ID: <D14A2F335E585A85D96C7872@PSB>
In-Reply-To: <241262fa-811f-40ef-b24e-5cf7a913fca0@gmx.de>
References: <1952067F-6467-4BEC-9CA5-BB8B16FA662B@tzi.org> <14807.1709682543@obiwan.sandelman.ca> <effb521c-1e20-cff8-acd3-17212a6b3fb9@gmail.com> <447A96F55A3D36851570B3B6@PSB> <60f18950-a2e0-16be-3a05-33f9a637062d@gmail.com> <CABcZeBPzYvscB3yeaRYQg6waR1BvqQMhJ+GpoKAZThoDvREs+w@mail.gmail.com> <241262fa-811f-40ef-b24e-5cf7a913fca0@gmx.de>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/ERdaArXm5GYqDJ3iRqBMivUJas4>
Subject: Re: [Tools-discuss] Why post text and not XML?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
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, 17 Mar 2024 17:18:36 -0000


--On Sunday, March 17, 2024 13:09 +0100 Julian Reschke
<julian.reschke=40gmx.de@dmarc.ietf.org> wrote:

> Am 16.03.2024 um 21:50 schrieb Eric Rescorla:
>> ...
>> I don't much care about the comments, but I would observe
>> that a consequence of having the XML kept private like this
>> is to make it more difficult for others to work on the
>> documents, either by submitting diffs to the text or by
>> forking them and making their own documents.

Again focusing on IETF Stream standards track documents, "fork
and make their own" is an excellent way to create confusion in a
WG (or other discussion) about which document is being discussed
and how it is different from the other(s).
 
> ...or understanding why something changed between revisions.

Something better accomplished, IMO, by an explicit change log
that identifies and, as needed, explains substantive changes.
We've never required those on an IETF-wide basis (although ADs
occasionally have done so with "their" WGs), but it has become
the custom in many WGs.  By contrast, suppose an author makes a
change in the XML, does not provide a change log, and either
does not include a comment about the nature of the change or
suppresses those comments before posting.  In what way would
access to the XML provide more information about changes,
especially why they occurred, than, e.g., a diff on the text
form.

best,
   john