Re: [xml2rfc-dev] [Ext] v3 <seriesInfo> vs IMPNOTES vs canonical XML

"John R Levine" <johnl@taugh.com> Thu, 19 December 2019 18:26 UTC

Return-Path: <johnl@taugh.com>
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 A0F32120A5E for <xml2rfc-dev@ietfa.amsl.com>; Thu, 19 Dec 2019 10:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=hjO/cPbB; dkim=pass (1536-bit key) header.d=taugh.com header.b=mRecqlAZ
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 2eT-2tDLZWOc for <xml2rfc-dev@ietfa.amsl.com>; Thu, 19 Dec 2019 10:26:07 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4527120A38 for <xml2rfc-dev@ietf.org>; Thu, 19 Dec 2019 10:26:06 -0800 (PST)
Received: (qmail 96984 invoked from network); 19 Dec 2019 18:26:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=17ad4.5dfbc0bd.k1912; i=johnl-iecc.com@submit.iecc.com; bh=amcUy95b0Tk+4S9OveTbnx/TwTMhJvRnPzScUKFjhCw=; b=hjO/cPbBdTv3Pxud0QWSIh7C1m9tMMW/JUoY3w+f30F2/SBDxtOAInHhLwgCnREXL9IJHbbEzFdCXWu6UwKLPa8aNboCK2oZ9rjTHhwkBJjjKQlJPUUZ4b+SQPVrtlbtsmoJEpbBJ9u/8qMvPHjifC9zkQgCoLzaRDWF20m/6axBpnV2Bw5I+lJFdh94YcSXTBNSsfdDfoZaDjJl1yaSeC8MCrdbLaGX5MdrIeVRYLfhHrkp8KyFeapkzx2/8YM8
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=17ad4.5dfbc0bd.k1912; olt=johnl-iecc.com@submit.iecc.com; bh=amcUy95b0Tk+4S9OveTbnx/TwTMhJvRnPzScUKFjhCw=; b=mRecqlAZ7VeBW83iftGvceLdckdgNyGrwA/YP4VU7R6jOWoLCvQtC8nGSy+t9IQ2J+9EpGm1Ih+Wz+uXWZhgtBiRVf3aWzZzfBG6zrg9jRLEYOnOVrDiJG6tltdwlJ7URtB4KEjMBOBP1GX8IDh2Ulo5AxiP47PVZCcHGIeAdimXqZmrN6ePbvcYZYBFS/FFKUcGVBnDtqg7kLL6KwdrJfgEteNoPY3uJYiTEabOHtkFsysEbetVhJZbKqmS8PlK
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 19 Dec 2019 18:26:05 -0000
Date: Thu, 19 Dec 2019 13:26:04 -0500
Message-ID: <alpine.OSX.2.21.99999.374.1912191315110.83919@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: Heather Flanagan <rse@rfc-editor.org>, Julian Reschke <julian.reschke@gmx.de>, XML Developer List <xml2rfc-dev@ietf.org>
In-Reply-To: <3C9A92E5-FDE2-402E-BE2B-7DF4063B2562@icann.org>
References: <dd955428-7129-c0e9-4064-ef963ada90c7@gmx.de> <159956F3-1DDA-436E-8565-689F4EA74609@rfc-editor.org> <6b631129-546a-0935-aeca-0ad31db47d62@gmx.de> <E98A6936-406B-4D65-A077-E23989CCA6B2@rfc-editor.org> <b6369b2c-61af-e948-ad87-da41bf581dbf@gmx.de> <e3e50137-0588-92bf-7b00-670588fea8e7@gmx.de> <5B698092-3354-4910-A0D3-BDD7E57F79D4@rfc-editor.org> <3C9A92E5-FDE2-402E-BE2B-7DF4063B2562@icann.org>
User-Agent: Alpine 2.21.99999 (OSX 374 2019-10-27)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/UDr8ArKp5GyJ728Rcqy1JoQjqMU>
Subject: Re: [xml2rfc-dev] [Ext] v3 <seriesInfo> vs IMPNOTES vs canonical XML
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: Thu, 19 Dec 2019 18:26:08 -0000

> The current canonical RFCs in XML don't match any published spec. This 
> leaves us in the situation of having to publish a new spec that might 
> have escape clauses ("the XML might contain X or Y for this element") 
> and then later publish a more definitive spec that says what we really 
> want. Or, we can admit that we made a mistake with the current canonical 
> XML and fix them when the revision to RFC 7991 is finished. This is 
> related to the decision about what the version number for the revision 
> to RFC 7991 will be, given that the current canonical XML is not 
> honestly reporting the version number.

One of the major reasons we moved from free text to XML is that it lets us 
write a well defined specification for what's in the XML.  That makes it 
possible to write translators into display formats, and write future 
translators for display formats that haven't been invented yet.

I would be dismayed if we had the XML equivalent of early Postscript RFCs 
where the Postscript is missing fonts and modern software can only guess 
at what it was supposed to look like.

Ten years from now when our successors have some new haptic accessible 
output devices, they should be able to write a converter and run the old 
XML through it to support the new devices.  If the XML changes from one 
RFC to the next, we'll have made that gratuitously much harder.

At this point I have no strong opinion about the best way to fix it, but 
we do need to fix it.

R's,
John