IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 16 December 2019 17:02 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 93B6912085E for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 09:02:02 -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 VK4vuB37yknb for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 09:02:00 -0800 (PST)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10on2054.outbound.protection.outlook.com [40.107.93.54]) (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 9C79C12085C for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 09:02:00 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h7w80A3kUeFUl0zvb3nqNtaKgs8tyTy4Kg/2DwBzrtLGFgMZIhOOD6noL1DhwctKYIYYJxR5bBdwTA97WRuCZ+OBvhEfhLxFZAw8spZplWY0QXgzPg/wlMr4QitLSu4W/TC9wzREQ8eID8yMW24TNMwXJjWuw3Z+67r5kieHiwJXJQj/OgSKRIrxrf2YtpEf94PaLbrjXeRNH8bUc0chAMtpNUbTd2Dzlu1apTV92m4UwqEDTGfIpuk2Gm/QLf+Ebm6G51zpmZpqifSZJU4lMhs/WM2x5fNZ3e/cx67awv7Gxlho0SYXBpOGy17u/22d3dsstxNgpVoGT3K18q1TtA==
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=Lj1k1AbY6CISNfGHxFDxD01S4x5931YIHoIbEcUb1ho=; b=E/SsyMhzsgMeXSYIatz2Z70DI2T2kEQ6tSC21lYhtjDd/edHLlg2aACHTCEdIffifp4onMPW/5KCESk8+6yz+hcmWp2wZy4tjob3cDAzlQi1/r9ziuxTBLCu8L/Ei/w3RujpImQTsF3mh83EsXZu3G7rqdwlNK5US/h/te6ot+pu8b4zZnRfbK1lJh2m7VdH182Y4ZhagbfAdabReBU+dCNE/YYwkNVP/2sdsaUtj0GtigOXjHGPr1h0K7e5RV9ZcEKYD5RBqS2UdP9zGFAIDoXhmpHr7YAd8wVHRP3MYc8flHDsJM5sI1Z+HHZC4j9ymXzMHeaZdDvw/IO5VdtJGQ==
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=Lj1k1AbY6CISNfGHxFDxD01S4x5931YIHoIbEcUb1ho=; b=WIaD6BI+nyAiQoSbKKOFV5DGsZ5u51GwylCQSBsGT7k0K7UaR1eYxx91psiyGwi/e2tPIlgwokJ9xntt9USl7JslNRdDEi+7epzeYTMaEH1Q607u2bDPISpWY9/C8pxoVnm4NAu8P+j2V6k+vgdTAMc1uG9uQxMLd21Y7cCQtFA=
Received: from SN4PR0201CA0050.namprd02.prod.outlook.com (2603:10b6:803:20::12) by CH2PR12MB4216.namprd12.prod.outlook.com (2603:10b6:610:a8::23) 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 17:01:59 +0000
Received: from BL2NAM02FT013.eop-nam02.prod.protection.outlook.com (2603:10b6:803:20:cafe::75) by SN4PR0201CA0050.outlook.office365.com (2603:10b6:803:20::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.15 via Frontend Transport; Mon, 16 Dec 2019 17:01:59 +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 BL2NAM02FT013.mail.protection.outlook.com (10.152.77.19) 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 17:01:58 +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 xBGH1vC1010029 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 12:01:58 -0500
To: xml2rfc@ietf.org
References: <5d192de5-c6ca-aa1f-b7e0-0500704e491a@htt-consult.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c5d985f6-b011-8605-db7d-14f3be88d689@alum.mit.edu>
Date: Mon, 16 Dec 2019 12:01:57 -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: <5d192de5-c6ca-aa1f-b7e0-0500704e491a@htt-consult.com>
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)(136003)(346002)(396003)(376002)(39860400002)(199004)(189003)(6916009)(70206006)(70586007)(956004)(31696002)(5660300002)(86362001)(76130400001)(36906005)(336012)(356004)(246002)(186003)(75432002)(53546011)(31686004)(7596002)(26005)(786003)(316002)(2616005)(26826003)(2906002)(4744005)(8936002)(8676002)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:CH2PR12MB4216; 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: 5c600f88-d914-47f7-646e-08d78249a9a9
X-MS-TrafficTypeDiagnostic: CH2PR12MB4216:
X-Microsoft-Antispam-PRVS: <CH2PR12MB4216C6A98155B1E83BE34C7EF9510@CH2PR12MB4216.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:7219;
X-Forefront-PRVS: 02530BD3AA
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: ZoDmXhVC3WobH/43fcyNtxdeQJuLHd9B+b542m4FTb6pjcijxIj3b7AaZ+eHITeT1S2FnuM9kO9qi6tpj2DnVHMG9zaFZiE0Eil5vUsyTI471hn3n3gAjJ4pI9EcSrWF16Il4T233UV3WXfsUZg+l/gJqtovUVOqG7v6xDrkI3hYG2xDNS+vFOOLkkShDaQK9MCKZUUovZRO1/DgE6gYFP+sr0cTdD4OcCcJmWuxNdklPVbvVM3gfUstoJ3DmWA2zT5ScFoLZ54Q/Q9NhyCVaPLMwSpG1SWVBi8PqiiL3zph5NjuwrXBFJdgFJNPjiaJpu8rdt+67B/WO7Q/iU3Z/ifhiY82GlXXznOPjlr/giq7W7qhIVb3OoOA0aN3dlyGYB5R/Nyj96xN6CmGWUa6M2qGz3njCZNray8t8g1sELWVkSHVI46DHhaNhOgXxN8s
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Dec 2019 17:01:58.6308 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 5c600f88-d914-47f7-646e-08d78249a9a9
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: CH2PR12MB4216
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/1lDcHG1snWzwpzcFYPfRQM99e9I>
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:02:03 -0000

On 12/16/19 11:47 AM, Robert Moskowitz wrote:
> I see examples of section=5 for RFCs, but for IDs, the section number 
> will tend to be version specific.
> 
> Is there a way to reference the anchor label for the desired section?
> 
> I am missing it in the FAQs.

How do you imagine that working? When following the reference while 
reading, this will be looking at the html or txt version of the 
document. Does the html version use the same anchors as the xml version 
does? And in case of txt, the reader can't see the anchors.

	What did you have in mind?
	Paul

v2.23.0 | Report a Bug | By Email