IETF Logo Mail Archive

Re: [xml2rfc] Differentiating prepped from unprepared documents

"John R. Levine" <johnl@iecc.com> Thu, 23 June 2022 14:53 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2874C131808 for <xml2rfc@ietfa.amsl.com>; Thu, 23 Jun 2022 07:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com
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 VbtBFbA9ljZN for <xml2rfc@ietfa.amsl.com>; Thu, 23 Jun 2022 07:53:20 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BC6DC1858E7 for <xml2rfc@ietf.org>; Thu, 23 Jun 2022 07:52:43 -0700 (PDT)
Received: (qmail 50203 invoked from network); 23 Jun 2022 14:52:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=c410.62b47e38.k2206; bh=vIkHA7gs94pKkqnAlUCdzIuQNVyD65/2Eiqkavs7B9M=; b=FaEItmSpcSvX/iOgD0pdXUNwswonlyUWlN3tDJQOuxfUg+yE0z8qDBkqOOkYia6GqxWOSCjQfBtmDfwHecthohooTaKCieaqywfmPOLh4p8cfA5k1OrhmI+KC0KoB3dAEhOyAuu0vQiRH76hdRCp4+dkUj0eLXLuxpZwl2ukBprNY/p4nvtCecdPEGwrxOYUWKLThcnSOplcvcIASU0xr7vLw8qJsBa/XktJCHmRbP8VlXHyeNjJaKjLCfYxkFlv25fYgP5bJyLPMPP9dDxTMd+H3Lpo/Kp8pzfAuJv9VsDrbWrDhwpGRsUY241cj7xlta+MNkxlCyOFbXXDAUwdxA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 23 Jun 2022 14:52:39 -0000
Received: by ary.qy (Postfix, from userid 501) id 31C014425756; Thu, 23 Jun 2022 10:52:38 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id D5CED4425738; Thu, 23 Jun 2022 10:52:38 -0400 (EDT)
Date: Thu, 23 Jun 2022 10:52:38 -0400
Message-ID: <905ade12-8975-6cc8-b01e-82b4ca466327@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Julian Reschke <julian.reschke@gmx.de>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Jay Daley <exec-director@ietf.org>, xml2rfc@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <ed900d20-c307-a296-b957-40bb0886db49@gmx.de>
References: <222A7719-518F-45FB-BE05-A3CA1172DD9B@ietf.org> <d8b7991c-344a-5741-afd8-52f5db1f8f50@gmail.com> <d6bb380d-f000-0388-bbf3-1423846b5ebe@iecc.com> <ed900d20-c307-a296-b957-40bb0886db49@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/H4vQTl_TpqVOrX6n9dbExTjbzk8>
Subject: Re: [xml2rfc] Differentiating prepped from unprepared documents
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2022 14:53:25 -0000

> I think it would be much much better if the authors and/or the RFC
> Editor preserved the XML that existed prior to running the preptool -
> just because it will dramatically reduce the amount of changes.

Me too but I also think it would be a good idea to be prepared to be able 
to re-edit documents for which we don't have the unprepped version.

If we move the prep elements into a separate address space, how hard would 
unprepping be?  Remove those, remove attributes which have default values, 
anything else?

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email