IETF Logo Mail Archive

Re: [rfc-i] Updates to RFC XML

Julian Reschke <julian.reschke@gmx.de> Tue, 10 May 2022 05:07 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EBFDC15E6E1 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 9 May 2022 22:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1652159267; bh=5Ffh4Ml45wg/IP+InorS81aa1HZut/P6A4zsXKefz1g=; h=Date:To:References:From:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=TCo26iDabkh0o0z1J9z7GzSy6E+3EB3ldW4G5u82zaNjaVlKO+PRVL+H5nBbg6xtA 9sIQikkXIj3d9PRXxrQOvtVXs9Q8/Ewbc2ybm+GdK58buzkQkZJMCkm07DPi8v5wz9 MhVem47uzFWfDTfJdIm9w41aAT9o/5wKAzQoX8e8=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Mon May 9 22:07:47 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6801CC14F728; Mon, 9 May 2022 22:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1652159267; bh=5Ffh4Ml45wg/IP+InorS81aa1HZut/P6A4zsXKefz1g=; h=Date:To:References:From:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=TCo26iDabkh0o0z1J9z7GzSy6E+3EB3ldW4G5u82zaNjaVlKO+PRVL+H5nBbg6xtA 9sIQikkXIj3d9PRXxrQOvtVXs9Q8/Ewbc2ybm+GdK58buzkQkZJMCkm07DPi8v5wz9 MhVem47uzFWfDTfJdIm9w41aAT9o/5wKAzQoX8e8=
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C881C14F728 for <rfc-interest@ietfa.amsl.com>; Mon, 9 May 2022 22:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.757
X-Spam-Level:
X-Spam-Status: No, score=-3.757 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.857, RCVD_IN_MSPIKE_H2=-0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0uTKQTCcu9lw for <rfc-interest@ietfa.amsl.com>; Mon, 9 May 2022 22:07:42 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 8CECDC14F726 for <rfc-interest@rfc-editor.org>; Mon, 9 May 2022 22:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1652159252; bh=QmrZZezT7Iliy6yiu/GBJY7ouGdKm4WY+g45mlASi2k=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=gNF2kbD8tuvlLz5MQ6GZpmTCcM6Ytha5PgcL4aKvTGZ3NcqIoM5vM84DOz6jHTfa9 wFqT/b0D/vNm3YDKaRvPTlpy/gde1Q371tegFGS6pEMAbriTU4pUq3LGR8rvvYDaBK gjR5r107Pqpybzm4OZ9FXRczbzRkqnDYlD/SoJ78=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([84.171.154.147]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1McpNo-1oNtpO0Cgc-00ZzUE; Tue, 10 May 2022 07:07:32 +0200
Message-ID: <6e4f60d3-012a-41d7-de14-48608a94a5a3@gmx.de>
Date: Tue, 10 May 2022 07:07:25 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
To: John Levine <johnl@taugh.com>, rfc-interest@rfc-editor.org
References: <20220509214746.E11AE3FAEBA7@ary.qy>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <20220509214746.E11AE3FAEBA7@ary.qy>
X-Provags-ID: V03:K1:0wdu7T/qw2MMgGt+D84nAKyWOBh9IEMnn6Jj997ocgWiXxhTmz5 REk6qSri6A4y561FEKjVOzc31zdJsM1O7Ba/lmR/e/6YiK9neN3kgk2NHN3j7ewDxOiEqTt jHK2fFDjPtdYVsURXiOrjHUuTHMKh9HhYM6Doi9CiNpasHNILzvl6+L+f0bZkA8J+LyeKq6 QL7OHucEHVJd0TOGqWZEA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:Sby9mxJN0is=:RqrTYhpWNAeSIMRR+aX1pP FtOixap6GiOVzBI7Uaa8VXjAlJnSzJ4vbSBwJkQZCIzNxHQ0q6Fkz+Ta3tuVMROkAN3s3iymD hOb0SEJT4c5LUFdMwphg+4R2VmrybeimmxcvhPs7bUUiciFveUhJ/yo7ihckL1ImPsDOX8cND WmrYvAyAXlqbzFw3oge4MS3TExzDM/7n/7C6nxYUnHHXtCtX8mgOf9PEcllBkpQz7aktMTTEJ fJ1w8zxEYEtTxbiXn1wyi7QlQD+IVUUnVMaYIlfqPs+BMOLgSgcUCAkLrW825XLVeejE91nN2 kEy+VJBUrsPz7NbbDC06nngBfCCX8UR1SsiEZ4LlOpbwAEJH2daa4VZL3LJnDAsAnkzvtMYCJ j+RoTg+TCR5mtdOsdOvlhebhsAtLR/wqbXa0wfqD4ou+kl7TBIsDP76FubwNgjdmWkw3uyEMp yzikGG7sX/Ir8XsYMnLlJCUdvNBvE2IFTj/eMcBIOPN54rYYORPqnBDLLMMnvbbbK+Mpg5L6q iXEc5/5TFvqJYVtrQtvD3eFexmR61+kcLcX7PWIIc6Ct+IKAjP1tQeqQK6K9UzP5GIwLqt7tc m0NquloMVRf2uIF7nMevPfG3NuZS5EUoacm4q4GCJlbFwGFGh0990B+nhtHoWnE2S/1ehDYE6 C1OkPDP/v6dlesmjf8QLLXjvZFSooU9ZfzvBBnepEFiVJyPSSFxQugrcTbxRs9WlXBuqBBrbK XzU3Flh4LDvXLbj6NjMB5gg3lvLRXvIQumHcfHBvjnwQfAolmP2KD4kxJSY6U7w/vHogxKGM5 zLSZMpmeEWCCyZUoL1p7lsirUqEXEXdE6udwpyG7Sc8THZN20l+F5qq+ygc87CWAdh8mtTeMf ssoBJ4VEA4iQdohD7bJ62dam+pyUZ2+7F5MVwUg+k3LDdpUY3x95wSU8aDp9LM95N6KjqRQmD XuO/n8Odps2/F5Du9agS3ugA9oVi5DLkapbD+gwmHHAyKBs1jrnobOkpYg12Pi33o8sK5Onwk PRCF5yyX8PF8h8eedd1egZQDfwvlhO2NBydXL4tCLe3kuBbpVxZ3m1+ZxFMx92SZpolgvzPdS K3dtvSWv6Xqxpo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/FUBObAKAXwWCIUsmdHSe-FByUKE>
Subject: Re: [rfc-i] Updates to RFC XML
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Am 09.05.2022 um 23:47 schrieb John Levine:
> It appears that Julian Reschke  <julian.reschke@gmx.de> said:
>>> In the <rfc> element, make the docName attribute the name of the RFC,
>>> e.g., "rfc9999" rather than the draft it used to be.  The draft name is
>>> available in a <link> element.
>>
>> I would prefer to restore the number attribute defined in 7749 (and the
>> sibling attributes).
>
> I gather that means you can have docName or number but not both?  I wouldn't
> be opposed to that but I don't know what that would break.  Also, which
> sibling attributes?

What RFC 7749 said.

/rfc/@number just overrides /rfc/@docName. There are also
/rfc/@seriesNumber etc. The introduction of <seriesInfo> as child of
<front> was a mistake.

>>> Remove the generated <toc> element in prepped XML.  It's not used when
>>> rendering the document (xml2rfc scans the section headers), takes up
>>> space, and is confusing.  The TOC in rendered text, HTML, and PDF would
>>> be unaffected.
>>
>> Absolutely. And please remove related atrocities, like <author> as child
>> element of <section>.
>
> Do any published RFCs have <author> in <section>?  I'm trying to limit this
> to changes we can do mechanically so we don't have to hand edit and proofread
> a thousand documents again.  I suppose I could check easily enough but you
> can probably write the xslt faster than I can write the python.

They have an auto-generated back section with those after running the
preptool. Before, no.

Best regards, Julian

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email