IETF Logo Mail Archive

Re: [xml2rfc-dev] xml2rfc: use of <boilerplate> in preptool step

Julian Reschke <julian.reschke@gmx.de> Wed, 09 October 2019 16:55 UTC

Return-Path: <julian.reschke@gmx.de>
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 E353B120862 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 9 Oct 2019 09:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1aMTgs4GXwD for <xml2rfc-dev@ietfa.amsl.com>; Wed, 9 Oct 2019 09:55:57 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A311120026 for <xml2rfc-dev@ietf.org>; Wed, 9 Oct 2019 09:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1570640152; bh=IoKR8DDl2c3Wdp+KjhxXBe4FHHPmF+eqAAjbTp7VDH8=; h=X-UI-Sender-Class:Subject:From:To:Cc:References:Date:In-Reply-To; b=kX03Cc82xdgdsV4sJl9KIZ9L7/ziauABWtLl7Ut15qa6Gfs1w3SQ55LEbSjorE4WN 6L8plpPwkC4RkE4i71S+JlNNKWbuyZjkEcV22j7p9bOj+y4w8DO1g1eKi1Hu+9NuSa Sp305b7APFx8YpcIGJbNNK8jdEw4MlzOzZBwP5dU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.145.63]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MAONX-1iOc7I3uI7-00BxQ9; Wed, 09 Oct 2019 18:55:51 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: Heather Flanagan <rse@rfc-editor.org>
Cc: XML Developer List <xml2rfc-dev@ietf.org>
References: <6e36282d-c6d2-6031-2002-e4bbc85b3fc0@gmx.de> <6D64EA29-B4A3-4DF7-A5F0-1B6D4B83886D@rfc-editor.org> <410e71dc-72e3-93b7-09aa-240fccf537e6@gmx.de>
Message-ID: <09c0e5fa-1853-a89e-816e-6579ad9999f4@gmx.de>
Date: Wed, 09 Oct 2019 18:55:50 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <410e71dc-72e3-93b7-09aa-240fccf537e6@gmx.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:Mfy0Hkvl+SaddqjKhTPRbf9sWh5it5yrcZSa4JtrBU8YFlPNEHZ JGVJ7Pq40ugEHgw3TpmfSTokcUZgpyxQpytMyufNWz4R3NCf2SFjKcyc6IvijxORMADs8TD 39XGmftBEOlB1ZbSCiwQb7Wv59ERA3Xdmiit9KtNy3OlO+m+k5c/WKUUgHJQGsm3CoPLXED I2v4Ys6wEIGy+NDIR3vQg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:bfgYTcFBZA8=:LoZqy4ygltSGv+IWbTfxVO jCpdzQYIrn+CZ+GKbv/TVx6TRupKi3NB9K4q61OSpCbEMcQrwHPxlcMn+kprhhF4R/01joIdY xLYvlm9FqZKgfln+25zH3Dfx22KsQ7ILC1KZ6XOK+6T0t5J/rNGt2G+bozpqhTOBHQvhgwTOP IrwOfvlZ/yCbENuPLaVm3mCkFEJkOpU9GjBBG3Uouu35Rd/VZcILOQFgZaBsiEibJO1k1F9Gk tC2VYsXprcZUi9ErXXfzPUPaoxOuiKOhaSc27wR+YhYWEeiOGyccZyc8XGzRPkVaSeZejTvxn nKQfxtDuhyh6C1gqHwdlcXdIw1Cy2v3oorUksTizVXIv9KG0IEAFWu26jf64KXO74BlNwQRyC CkjIUvt8pSVlQoFTGBnEqhiC1+ICfnPVGBBph/Tj1nQlhd4r3wG21RIH/L/QFB25jsdxkqO70 uOOMsmG4tRtNeupz8NFDOxGZcsgIl4MoTBNbL+qnHGbA9SvJo5rMbI2Vd4QuKs175G3HijsIB 6iP2QRq4qmRPoQ1l8pT1EdBYajFMrs9XHlKMbF0PSBCiCZ8mzR/HkCBXwKv25NxehAngM449p F3O6UKcozGtkMuRt9AqDEednA2/IZ+c0JAcOM+qlCTRE8e/1LkWd4RUaQhiSz6A8pUDG9fga9 1vGInRDH35LniJsWjE6iYX8J4w63QWo21R8gSh1DXrDslT597VDn50LfcZ4E6VdlDw8dYdAFq ciJz4zrww0n4At7OlhuNofWJzmyt+WvestCnGp06KudTAnjuC06sdf2cDsKZbyN3sLSFG18TT FFxpNaf98eVT6AJPMmA4bHHTX4y9f/CbE8NG68HUhUOJ9qyP7ufz9nkeiSIw3q1AMXlI1fkfQ lbex3nVdkiBrBgsOuEEWqkYnkDua9Ulyw4eTQ6fFyHlU0kzm+Wb8yVgC0Nuj3QHrNVSUjDwo5 +mrZ6LjWynTXilgbyHtfkIg570UmFQ7L02o/Qvp34OyCLngaWqia76+IiB5uKYCepNlVuMXBU inb0UUTi9BOUJbj6dundH3CHNQ/l9wlVvExm1ldCbKMpx2wAKI2IIgqj/RZg1Rkw0bvtM0HHL eaBj6w69qAWOqUmBMOGKuRYU4FcAv7KqKgj60dT+D1dtvla1EMbSnyoYZEzwaQYr2fc1D8rLz vXMTNrqKD+yHYbFctpo+nkiB7ZE1Wh/v6SappWGZrJXnDuThNoadnziPRAobLxYYLSsO9yrO2 wbIinRdSQQ8vHXdE2HvS+j6CF2t5+mihUnmfN0ktLuP7pb/pNJMTj55VEgf4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/029qSe7plyPcuoafsVh-dgsQkvI>
Subject: Re: [xml2rfc-dev] xml2rfc: use of <boilerplate> in preptool step
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: Wed, 09 Oct 2019 16:56:00 -0000

On 09.10.2019 18:50, Julian Reschke wrote:
> On 09.10.2019 18:44, Heather Flanagan wrote:
>> ...
>>> That said, I still don't get why the Table of Contents needs to be part
>>> of the canonical XML. I understand why it's desirable to be present in
>>> an intermediate representation before rendering, but that doesn't mean
>>> it needs to leak out into the canonical format.
>>
>> I feel fairly strongly that the final XML must be self-contained.
>> While someone can derive the TOC based in section headers, deriving
>> details is not as good as just have the thing available in one place.
>>
>> You don’t agree. I get that. But I am insisting on this one.
>> ...
>
> I don't see the point (and it contradicts the specs). But well, it won't
> hurt either, except that it causes potential confusion. Just make sure
> it's fully specified (for instance, what to do when it's present in the
> input source and does not match the to-be-generated ToC).
> ...

...or under which circumstances an <xref> can reference an element
identified by @pn instead of @anchor...

Best regards, Julian

v2.23.0 | Report a Bug | By Email