IETF Logo Mail Archive

Re: [xml2rfc] Differentiating prepped from unprepared documents

Carsten Bormann <cabo@tzi.org> Thu, 23 June 2022 16:25 UTC

Return-Path: <cabo@tzi.org>
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 5FEF3C157B49; Thu, 23 Jun 2022 09:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 A_EAYH0zIZUH; Thu, 23 Jun 2022 09:25:00 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (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 49C52C14F740; Thu, 23 Jun 2022 09:24:57 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (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 4LTQZY46RhzDCcL; Thu, 23 Jun 2022 18:24:53 +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: <905ade12-8975-6cc8-b01e-82b4ca466327@iecc.com>
Date: Thu, 23 Jun 2022 18:24:53 +0200
Cc: Julian Reschke <julian.reschke@gmx.de>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Jay Daley <exec-director@ietf.org>, xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 677694293.157752-ee4dead1b53c92abbee58645946a3d98
Content-Transfer-Encoding: quoted-printable
Message-Id: <506EBF0F-345D-4EEA-8A24-461684924B90@tzi.org>
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> <905ade12-8975-6cc8-b01e-82b4ca466327@iecc.com>
To: "John R. Levine" <johnl@iecc.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/EnEv5nR75g0s-jlP58IevtPp8xI>
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 16:25:02 -0000

On 2022-06-23, at 16:52, John R. Levine <johnl@iecc.com> wrote:
> 
> 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?

The answer is relatively easy to derive from https://github.com/ietf-tools/xml2rfc/blob/main/xml2rfc/writers/unprep.py 

(No, I haven’t done that work.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email