Re: [xml2rfc] can xref section= reference an anchor?

Julian Reschke <julian.reschke@gmx.de> Mon, 16 December 2019 17:46 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 36B3D120885 for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 09:46:04 -0800 (PST)
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 i-tGGNMHl4D9 for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 09:46:02 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50DD4120033 for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 09:46:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1576518358; bh=s8NXKTWPqptiBmzYAVvpt7bmRt0uiHktKFOLyzR/yRU=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=JrucEFXyEabDW/npNVL93O0cugpyawj7WMMhkyCOLTGmF9UbORUje6CDemRs1J/j+ KhUnatOEH2KxxMDLaqkub8DrK89LMg+Ns31mVXcjCrf1TBE0xtix1t1ko94ijmFd7+ vVjr8FlFKFcqzjARbsYM+xDf/Wlq6qo0vkMUEaO0=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([91.61.56.199]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MRmjq-1iI8W43FkY-00TC9w; Mon, 16 Dec 2019 18:40:46 +0100
To: Robert Moskowitz <rgm@htt-consult.com>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <5d192de5-c6ca-aa1f-b7e0-0500704e491a@htt-consult.com> <13eeba5e-bb17-a0dc-cf21-8380150f480d@gmx.de> <2e3a4d01-34e2-5609-5179-3ddd47493947@htt-consult.com> <9193046f-22f1-e9f2-0a11-86d622ab11fd@gmx.de> <83e5ec0e-4182-5a75-c312-aaa238a98985@htt-consult.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <c37c8180-95f4-cdec-4101-1e0a4f6803ea@gmx.de>
Date: Mon, 16 Dec 2019 18:40:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <83e5ec0e-4182-5a75-c312-aaa238a98985@htt-consult.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:3biZj2mNX6CCPSJPepL6uwBdWWXcOIzrP8vmL+pTp8cuL/fdnly fYeB+Po1bFoQjLSvYEIFLtbT63zfCfGaMxpjRf6NXuRgvYSwZNZfdCl9SsIk3EenIPhKhDV tePxdQGzgC+M1ZVxtfqP0fLAvgSJAo1FSYthlxj97WSFseXOkEnncTYB3eJ4MnKwaQ27o5P deozFAlMrYl8CQNcXV6Kg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:FwAYDu7MvA4=:a34JOSyBcNreEJZW9pL21C reEotDAhN1//6nkf6FqTQlnsU0878co3L5bbdPbkmjJtsBRl9ZwGclJQvwgktni+5nAlVb0XR tqtyWqDz5aVmF5H2flgq8exJMIo5BlduS/P+xh2grDFfrb2FzHmlIXRi/Iatikeg1tHT7vdA8 p5zHZUaJ3/jL3hole5K3RSulQt80miytN3uZNIazqDV61DQfF5b0Yo9fr1945rsaf0371UnSu dHPVdHbLjmOJohCAEU9ZRtrgcuJA1OLsVe3WEeMjH9Y2NrRyk9BdA2bqk+VNGb5PZA0T/uP/u LDr+0rx6pXTFAW6MCAjvBOBUBj1NXTdpA9Pd644nnAO2HVAH/BliC40pYmhuCWQ+HLyM9d268 wzP3kHn6ZrL9jermodHBHfjj9pcanHlPTKm6j1lMYzcar2C1Z7DiMn6jFfEqieINfWcE2uiOp OtvGFPqrldcirYRhd7/kSIRvuVwhhSygA6+ouul7Nn8efyCqmH2qUzC8+kdUImBzUZOWjBixS Xme9FUAzmyU1t9ex+YWYLaY+iroF0y5ad/tnYXDyvqX3vzRDXsa4Fa0gzgRHPG+cNnySTuuey yzDNirgR6t89FL4cu6S/XxloFkjCN1srfJSQgtRylVmCcrmTdfYXaWvSMl8ol1uDj2kufCX/K YXCzSMki9zf3MW6T1+GHs8kcBPrexhi9251PZg0PtUtr9TUuJ7HTvzJtDkripf1PTDz/ZSD6M idajU9KXNslTu5fnjYvEDB7Fy2HqQ+96p6cZR04VoEGQxIhJ9P4nBOBr+4RKFH5ZqCX0GJFX/ 8L3uz9IP+8nxo9KePqDsgAtpJtsYfeILLOXe4kifGgKliSELhvvTjW9TxAJA3azOlm/+cAH6t n9DM9L0X/Nt5P+NRFI6SAj7U9q/KfXz9wuky7zcMoTeqz7vF5BUit06X+eQMcy5/z+AcIiMxo VMOTLow0VzACZc4T0yo7JLXFbe2EIE+6N+U4piBTI9aQzkx47dWq/nU7sDYOQLiYtsiZjDHsJ dmsqVBti+/7vGkBmPZbdzKqEE2cMAy4Iyg8c1n1w80EfeY/c96h2Z1xMWiyeE9c9oA5zqqyZH sMtH43kcEN5aVxuXQkGCc9LhrLv9DCZE7Oar/uLQ3rvPSpFdraVNz42cfaJPRvVRyyrOFKFfe 8tfO26We0E1QLUP2NQ5H3go1sAe9utBUYk+ccvJQp0JYd6/L0gng+1XOmBi7qecs1/d+0eQ63 1OlmRTIN1f/I7hp+O+rvR/T7MalUKI0DT17jA4vez4GXLRuXMPTw8gVJoWko=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/ZbvUsxvo24vtY_-c6jp3jxGRObM>
Subject: Re: [xml2rfc] can xref section= reference an anchor?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Mon, 16 Dec 2019 17:46:04 -0000

On 16.12.2019 18:30, Robert Moskowitz wrote:
> ...
> I kind of thought this would be the case.  You basically have to run
> xml2rfc to get the section # assigned to the section.
>
> I remember times past struggling to kept all the sec # aligned in a set
> of cross-referenced drafts.
>
> So put this into a feature request :)
> ...

Well, my code *does* have that feature (as extension), because we needed
that for the HTTP specs...

We briefly discussed that for v3, but decided it to be out of scope back
then. (But then we also thought v3 would be put into production years
ago...).

Best regards, Julian