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

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 16 December 2019 20:26 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 14F99120918 for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 12:26:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 TZJM60AULpOv for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 12:26:31 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680046.outbound.protection.outlook.com [40.107.68.46]) (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 06A1D120916 for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 12:26:30 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Zp9pJuam/ETEdPDaU20sKf73jWsHmSdTjeKzcHR9WBVxpsD2aPeinGAgRf8yABZXvVFnESD/yujgyqmo44GUSmYzqtN1mZPWSRrzNR9tS+tZdrvt/MSdULJm7qaigYDsX5Fgb5rpuUxurLmH8OPzp8O9PpiPd49gfMUmqH12/KrRrWQfNTk52puo8T27hUimpDsZ/P9ziQVHnsd4SUqacBaeJOBAjZf72jxSim7vObhhQbscMZNXAYVlVDGKx/wgsuLB3q3s9e0Acl7z/hbJEnpYPCTlhVu9sW/V/eSFKts+YYKwrdl0u6xxACXU2MU8lFT6kRbB0ZaP+XaLFTblsQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZvnX7Zy9Jkni1NWs2E5AjTWrERXvm0dhm5YjkUSgLxE=; b=UmkdXfRN4hEdnqStISnt1cjopWzO8sX0dPDqbmHMxc2e37bdNjl96dmUWjs1SDxUngugcFZJYBifqicAGLFJqaWY7FebD4ZaLHbdOKxExUm3cD0GBAcDuBf2QZzH/DVYjuIwYbpWcGUYrKyyrVZfLckZCsI+0NT32Ey6+l9d01BlEBgno/JwfpBdYcScNKTS+N5GIgYXK8BAmaydYvNvLpXifCB9CM7lBYjgRH/o0jAIzYPq2oDEdUSIsa+yM6Bo8fuxPAcsTxppVvCl3Fl0OZTwNhTuHS2azo6Hbp6o57rDGXELNITQfr+J4Gxh1izfKvjrcnWDxqKezf6CdI1uUQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=gmx.de smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZvnX7Zy9Jkni1NWs2E5AjTWrERXvm0dhm5YjkUSgLxE=; b=G9KwsXH5QlAFKLFQZwuE0mWI/QmEaqIz0G14vdBzgHZvKGGBJBtYWmwPZNPnX0I/FrstH02PzpiOH+XOVqrqAqgjiNa7j4o13SHslaegfxaMedJbv079DMWWBzUJ68pzT4lDhwVcMaKcq80Ke6zZpMZuFdIFf8rSqAfr41muXyk=
Received: from CY4PR13CA0015.namprd13.prod.outlook.com (2603:10b6:903:32::25) by BN6PR1201MB0099.namprd12.prod.outlook.com (2603:10b6:405:5a::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.16; Mon, 16 Dec 2019 20:26:28 +0000
Received: from CY1NAM02FT064.eop-nam02.prod.protection.outlook.com (2603:10b6:903:32:cafe::84) by CY4PR13CA0015.outlook.office365.com (2603:10b6:903:32::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.10 via Frontend Transport; Mon, 16 Dec 2019 20:26:28 +0000
Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; gmx.de; dkim=none (message not signed) header.d=none;gmx.de; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by CY1NAM02FT064.mail.protection.outlook.com (10.152.74.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.14 via Frontend Transport; Mon, 16 Dec 2019 20:26:27 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id xBGKQOkl022951 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 16 Dec 2019 15:26:25 -0500
To: Julian Reschke <julian.reschke@gmx.de>, xml2rfc@ietf.org
References: <5d192de5-c6ca-aa1f-b7e0-0500704e491a@htt-consult.com> <C8AF4E96-E5BB-4232-B58C-A617E404DFF4@tzi.org> <78372dfd-39ff-183f-4f51-0b2c7e8d73d0@gmx.de> <f0253702-7b84-9dc1-08c8-87c8d97f3086@alum.mit.edu> <ffb41a52-f9d6-3776-cae7-58b123878ab6@gmx.de>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <380c21e0-ab94-2b28-b944-3bf5e63f0feb@alum.mit.edu>
Date: Mon, 16 Dec 2019 15:26:24 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <ffb41a52-f9d6-3776-cae7-58b123878ab6@gmx.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(199004)(189003)(5660300002)(956004)(26826003)(356004)(31696002)(186003)(70586007)(66574012)(70206006)(498600001)(31686004)(2906002)(2616005)(8676002)(7596002)(8936002)(246002)(86362001)(53546011)(336012)(36906005)(75432002)(76130400001)(26005); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR1201MB0099; H:outgoing-alum.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-alum.mit.edu; A:1; MX:1;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 21f79386-68de-4734-9fd2-08d782663aad
X-MS-TrafficTypeDiagnostic: BN6PR1201MB0099:
X-Microsoft-Antispam-PRVS: <BN6PR1201MB00990302C4E9F33BFC5AFE1FF9510@BN6PR1201MB0099.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-Forefront-PRVS: 02530BD3AA
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: YJ7OkS6NzOMoygl61OVIbnqgDerWbDIS1cwDuXGjZDU2Cs0ZcJWxBv12Nv8F6JWiyID+G9yZ5NmJfelx5lni1KW4/OcHUvKlm1nz52a5Dh5PPNyUnq0bKqlLr1ry33JLk3GxOaAaNE1R9nmqzedo0jBhP45XR6JGFD1UcH560dAeJvN30b9R3Q8t3Okmj0xfBIRAnLtcfpcvUTDSqx8aCQT5ubs0DzLfos6jLSeTghwPlcK034jvy3X+mUoMQLT6Cp4G73QxI0fMJE6qgYtmdkQE349HFVqKJAHObfuZfvppyLlgMiH86g9I4FMvWJmg9REKO7NNhBZcL/RCmroHUsdhQ5OVNz69/+TY6yP5ZpWjy7JDk9mdVM9M7Z0wSefCaOKrKaTFCASRgZ16A1GEtQmFfiHtmrONU+j0GcKui+jNN89S5LNSxyhgVOOVdfgF
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Dec 2019 20:26:27.6875 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 21f79386-68de-4734-9fd2-08d782663aad
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1201MB0099
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/SOfxYkcRrRgfpMMrSmi0bCtGoNQ>
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 20:26:33 -0000

On 12/16/19 2:02 PM, Julian Reschke wrote:
> On 16.12.2019 19:26, Paul Kyzivat wrote:
>> On 12/16/19 1:04 PM, Julian Reschke wrote:
>>
>>> The simplest possible approach for *that* use case is an extension of
>>> <reference> that provides the location of the XML source; the formatter
>>> can then read the source and derive the section number.
>>
>> This will only work when the reference is bound to a single immutable
>> version of the document. It won't work for a wildcard reference to the
>> "latest" version.
> 
> Well, it *does* work for the "latest" version, if you have the URI of
> the "latest" XML.
> 
> Believe me, we (the HTTPBIS WG) have been doing this for a decade.

I don't see how you are going to make that work.

Suppose we have draft-foo that contains a reference to section-xyz of 
draft-bar. Now at the time draft-foo-00.xml is submitted the most recent 
version of draft-bar is -00 and in that section-xyz is Section 6. When 
it is posted, draft-foo-00.txt and draft-foo-00.html are generated.

Later, draft-bar-01 is posted in which section-xyz is Section 8. 
Subsequently, what will the reference look like when I view 
draft-foo-00.txt and draft-foo-00.html in a browser? Note that these 
have not been regenerated from the xml since the original submission.

	Thanks,
	Paul