IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 16 December 2019 18: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 704B51208CA for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 10:26:28 -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 vUCpNrM8rP-u for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 10:26:26 -0800 (PST)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2058.outbound.protection.outlook.com [40.107.244.58]) (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 C19081208C9 for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 10:26:26 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nPReTnTAKg/cKvOry3LribibS+v4zMsQ2PfZPSNGoEUbm27cV027ccK+omsJE3m6rWBnPWoFmVi48FkDQDiDHECdLgg03i9cipTM4nWg6qE+uETL6Jh8msqWfCTeWEHPvN7F6NPLONEx2eJO30WlZPiqu9yT4lzY8l0pqw+Hlrij/P4cbAgXqP2OEcfc75vntk7bNC9PUA1kkdwZ+pXsyL6Mw4/H6Z7VL/YlkCL+6aHHnUWU9zhzZGtc1qxuNM0L6eNWeJ5tixfLG16rC7Vs7UVygJCms9PPMOncJ3Qf3xN2a5TfAKgVCS/jC4N0qDwAkz+jlZRNOJW1hwFMT13ewA==
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=1N19K9Py+UqL1xquVbG6UiqyzvC7syA4ZwlTENZG3lQ=; b=YBOYq+FKxVGNY0pWF8FtI1Qknp5fskRkm9dj8WwpVY1xKlor2pC/i2BSs6l/nTESD2yBHgg95fprmEB9dyHrEgAmxIcyQh3grceT3UHzmbiXWkQHoo13Yf8fQPnf2Y/x2SyD1AMuiEze9ShYYxvSVWCHExAFNYGJ0aNXISmBmCop7w5udx6keW/YAZhX2nh0udwV++4YhAamEKpj3rOtij52vVsnRbC23oGcjjRhhkUCTo4cqKWUq8vV306mEdfN8ygBytwuujdUeXmf7rsSgf24wpjXbr3zNp2aavPpjngHwZ8KQrnvFBMUAgYk0ueM6Um2uevBtYIuuIGCMoLeqA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org 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=1N19K9Py+UqL1xquVbG6UiqyzvC7syA4ZwlTENZG3lQ=; b=hj9CmNq66gWCwRrwmZTgHJujS01t+Lv/0pqp1DSrNUl1M0BNlRRqCj+GFHfNyIiywDJashbkRdpuRfBuZfCziO/WnCvJrzeAWBOmwdf9bEGntfrltV8y+0Nc9V43SKyt5m78ATyVAIKeRhgkX0aWRguK0icUNpEVie2ItF7ZAeY=
Received: from CY4PR02CA0043.namprd02.prod.outlook.com (2603:10b6:903:117::29) by DM6PR12MB3451.namprd12.prod.outlook.com (2603:10b6:5:11d::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.18; Mon, 16 Dec 2019 18:26:20 +0000
Received: from CY1NAM02FT056.eop-nam02.prod.protection.outlook.com (2603:10b6:903:117:cafe::ab) by CY4PR02CA0043.outlook.office365.com (2603:10b6:903:117::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.16 via Frontend Transport; Mon, 16 Dec 2019 18:26:20 +0000
Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; 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 CY1NAM02FT056.mail.protection.outlook.com (10.152.74.160) 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 18:26:19 +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 xBGIQCN0015469 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 13:26:13 -0500
To: 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>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <f0253702-7b84-9dc1-08c8-87c8d97f3086@alum.mit.edu>
Date: Mon, 16 Dec 2019 13:26:12 -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: <78372dfd-39ff-183f-4f51-0b2c7e8d73d0@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)(396003)(39860400002)(376002)(346002)(136003)(189003)(199004)(31686004)(53546011)(2906002)(478600001)(26826003)(76130400001)(316002)(75432002)(186003)(5660300002)(786003)(956004)(2616005)(8676002)(356004)(31696002)(246002)(7596002)(8936002)(4744005)(36906005)(86362001)(70206006)(70586007)(336012)(26005)(6916009); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR12MB3451; H:outgoing-alum.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-alum.mit.edu; MX:1; A:1;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 37871af5-26f7-4119-18b1-08d782557248
X-MS-TrafficTypeDiagnostic: DM6PR12MB3451:
X-Microsoft-Antispam-PRVS: <DM6PR12MB3451FE4754B54DC9B3926A35F9510@DM6PR12MB3451.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:7691;
X-Forefront-PRVS: 02530BD3AA
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: dYHwTE8XpPh7OVpXbwqTyDA2sN+UtagxiFVqulwdZXkSJK72y0j//7bYOLw07CZRoNhU6pYZXrK+WDgMY1EUCBXLgPDPFixKkIp67VpVTCVqndj/DWwGkUcd2HgbgeJlGU2LcIqkuE7YzIC3o1kQSgWyenQG6k3gVoozgaDYBnPB5hxlzPOhzNTvPz756z+hIP5mmg0LlKxqR4EwwuikpLpamPBj7L+xrn9xs78vuPss4Qi3lLEQ/DsqOW4Rx0TTHzL/duSZpPmi7WVqMlLueRAhOu1SVXgHaErsR40Aws3ErFMp/y1b+96T3P0nNFWpCh2MZscB/NmamtnYcnKgmA5i8piajUs7CbqvBW1Bb9cEdS6rppkVLSJtRaFwy7A7z2HuOriBjv8d5S8STFJZmcjufSSF/b7k+L56/Dy85zJJ2gARszVx0KBpkO2MvNLd
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Dec 2019 18:26:19.4200 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 37871af5-26f7-4119-18b1-08d782557248
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: DM6PR12MB3451
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/zDYnweSvZxryKcmAs-rxEZbHlA8>
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 18:26:28 -0000

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.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email