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

Robert Moskowitz <rgm@htt-consult.com> Mon, 16 December 2019 18:59 UTC

Return-Path: <rgm@htt-consult.com>
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 B09AB1208E4 for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 10:59:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 8GPDC_FGrkgf for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 10:59:53 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 578891208D8 for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 10:59:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 5E2C06212F; Mon, 16 Dec 2019 13:59:49 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mYxbW+s7wDF8; Mon, 16 Dec 2019 13:59:43 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id A86916212E; Mon, 16 Dec 2019 13:59:42 -0500 (EST)
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, 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>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <9d152437-c022-1b6d-e2e6-5c7143153e0a@htt-consult.com>
Date: Mon, 16 Dec 2019 13:59:37 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <f0253702-7b84-9dc1-08c8-87c8d97f3086@alum.mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/OPZZoeGhshRrqItYi9yCYlPdMsw>
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:59:55 -0000


On 12/16/19 1:26 PM, 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.

I disagree.  that is often EXACTLY what you want.  I don't control 
draft-x, but I need to reference a specific section in my draft-y. The 
author(s) of draft-x have sent me the anchor they will maintain for the 
section I am concerned with.  I will always want my draft-y to point to 
the current section in the current draft.

They could have published 5 min before me, and I will want my section 
reference to match.

Been there.  Done that.