IETF Logo Mail Archive

Re: [xml2rfc] Differentiating prepped from unprepared documents

Julian Reschke <julian.reschke@gmx.de> Thu, 23 June 2022 04:12 UTC

Return-Path: <julian.reschke@gmx.de>
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 98025C157B41; Wed, 22 Jun 2022 21:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.786
X-Spam-Level:
X-Spam-Status: No, score=-3.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-1.876, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 QWqm990IC-n6; Wed, 22 Jun 2022 21:12:02 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3A8DC157B3A; Wed, 22 Jun 2022 21:12:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1655957515; bh=djZaWn4TXIbsn8FVkKN8lf/tn3dXiTtQg9kTdbt7OEI=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=GsvKBnskFjC7P1cawZhyd4RNZpX3EohYW7mpN5wC/N++Ig7xARCUBxfA8cZxFIZ7w SKUTym3dM7kUMLpT3EFZhtdyhwzcaf3BnRcnBvlc+hJkSXwolWvcy+2outqMowF/e8 v1YDBK0kiRd9NdNw3HSBwtW7g/fv0dTrEDxqJWHQ=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([91.61.55.62]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MOzOm-1oKfgd18wu-00PLYT; Thu, 23 Jun 2022 06:11:55 +0200
Message-ID: <ed900d20-c307-a296-b957-40bb0886db49@gmx.de>
Date: Thu, 23 Jun 2022 06:11:48 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
To: "John R. Levine" <johnl@iecc.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Jay Daley <exec-director@ietf.org>, xml2rfc@ietf.org
References: <222A7719-518F-45FB-BE05-A3CA1172DD9B@ietf.org> <d8b7991c-344a-5741-afd8-52f5db1f8f50@gmail.com> <d6bb380d-f000-0388-bbf3-1423846b5ebe@iecc.com>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <d6bb380d-f000-0388-bbf3-1423846b5ebe@iecc.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:STCxVy15Ykn8xAWAH+Fp7aHKWSxilJ53/lDfjHzrSIe3Apy/a0D iAcyISwJTadShradVaguGt97rA+xYc/MhfCGhVBJspVTw2DwuMqz1HIlEgQ4Ne5g7Q2jqjS 3WOrOX9UdD1wtnE73uhTcw3h1CsOp1HLZsqMdwA/P4J7gxan/DvTaKKsuymqp9qA34Eri8G MQ01Ot43Rts0kx5h/KYDQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:uznvvpg7TEA=:fRtvflwnnMImpB9lv6ZJaf 0EYb6XNLJoFqH3wqnn0+cttvVmSpSTOVjrFL1NfhgixhjzYqOXa4hVCzTT6qTFWJOG7Sq88A1 QzelyRttV0co2DzTy3xHNlpd7rGcFCCQLcPw1KfiribtJEOhLu6nQYJ6+MnV2PZMJ/a6ZZzSI b4lWqAJOQY1lg0lhJobaVMmWAHq58rV1CTep5ULgs7NG20hyFAU2VZZg6f40OYAgCvhAfh+Fn sMIhpzgbRrhyDOKarZxNQIQYdh10pysqG6CLQrugYVC+ELRhtMnFirjUagNgFmY/ndS/AGfbK t6ldzVWyU6r3Up1rlZNw9TEo+IYmRYOb80vWufY4NO5gZqzjRxHrHGSLlZ/2fauEXQm+aSJ2x 81Y5Fb656P843SvCjyTXeYsLIuwCnEG2PM5mvw0JH1KmxpHb31pbgpI6ZnPJZfuMCjIdoo96D 9nfuXF/fFRxLxuTMy+b234Zhy6UQPQovbZJwF/+7hofSNfZEAaG9pbDqH/XLNszlq9+HyT0IH dY2Ew6mna49tZL9spgtZCmV3qXzMbjGXxvz3gjmJqyxq7mwCaLuk0fr5ynPc7yymuPCSAI2eW mrttH+KZrNiLKiKeqH3qHmLrLCW0waQhnhaTtecLyyROuj+PcA0eO++xs0+5BLklIwG6olIKt qDwScm5B9Xx4rBV7CgBLgqgodRz56OQ2om0rN/+tdd48Fg+5rcIJWzMUDIde/e0Xil+CNaH/f eUMqqj7121YB/+alEatK1k5m1xD4M7q14jv4UkHDDZIDExkU11j6Ei1MbJ7BX8RHPfwCTJdrq 1bWRuGCpqafwPUlG30PKvlyXLLFdGKAr/CG8QtkSwdFBFjURGgx2afWSw/l7KXKUU++fFrKwa MLTsEuvQtmjfSRhJ+eFAKDB0NhModCzx7B0GsYOQ4Mbvm06FFBNSlLnQIrqBktYyVXqeaFt7D T4LzNqwNhRBmC2OEixla9m8p+T0YS7nBhXscHlkGYxzecS8XynBHrI5nQpdqGs6Z3aOg5DG3p Tw7BPZp5lCh7AlUqCGqY+qQobPVQU4SJrzi05vX7YzEivRHZOfv81yxOWgoP4NQkUX1vDHjNl 1vgt0uZeOeiHO48UKZO0Zt66nr/0zKJjAwoA4X1hrHoI7kmKSlSxNW9TQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/GZ7F2L100V3xyXxXLQerdHfVdh8>
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 04:12:02 -0000

Am 22.06.2022 um 23:47 schrieb John R. Levine:
> ...
>> 2. (substantive) A common need when working on a bis document is to
>> retrieve the *unprepped* XML as opposed to the canonical prepped XML,
>> and ideally it should include exactly what was in an I-D that never
>> existed - all the user's non-default choices, but also the text edits
>> made by the RFC Editor. Can that need be satisfied?
>
> Assuming we make the unprep tool work, that's what you should get if you
> unpprep a published RFC. I suppose there might be a minor tweak or two
> to the header turn it from an RFC back into an I-D.
> ...

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.

(Maybe we'll get there when the RFC Editor moves to edit documents
publicly in Git :-)

Best regards, Julian

v2.23.0 | Report a Bug | By Email