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

Carsten Bormann <cabo@tzi.org> Tue, 17 December 2019 06:17 UTC

Return-Path: <cabo@tzi.org>
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 F20EF1200C7 for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 22:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ilmich7uymOo for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 22:17:21 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7598120059 for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 22:17:21 -0800 (PST)
Received: from client-0179.vpn.uni-bremen.de (client-0179.vpn.uni-bremen.de [134.102.107.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 47cSbg5r0Dz169T; Tue, 17 Dec 2019 07:17:19 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <cacf403c-fee9-f2b8-b404-837138e2f51c@gmx.de>
Date: Tue, 17 Dec 2019 07:17:19 +0100
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, xml2rfc@ietf.org
X-Mao-Original-Outgoing-Id: 598256237.184912-1b9caf2147a91cbfba3b3dd07ac52412
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5191240-8706-4AF6-9B77-AA18C81E9DB0@tzi.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> <380c21e0-ab94-2b28-b944-3bf5e63f0feb@alum.mit.edu> <cacf403c-fee9-f2b8-b404-837138e2f51c@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/7J8FBXAAEUuC0oUEwp22XdL9ZC0>
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: Tue, 17 Dec 2019 06:17:24 -0000

On Dec 17, 2019, at 06:58, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> IDs and RFCs, once published, are immutable.
> 
> A *published* draft usually should not reference parts of editor's copy
> of another draft.
> 
> What *does* work (and that's what I was referring to) is having
> auto-computed references between drafts that are published in sync, such
> as currently the three http-core specs.

As usual, there is confusion between the authoring language and the publishing language.

The desired feature here is to have references to other documents in the authoring language that update automatically.  

The time of commit is the time of publishing.  In the publishing language, there must not be references to information that changes, such as an unnumbered reference to an I-D.  Converting to plain text previously made sure that the commitment process happens.  Now, the conversion from the authoring language to the publishing language needs to be done by separate tool, which we tend to call “prep tool”.

Julian, you are familiar with doing this between drafts published at the same time, but synchronized publishing is not at all a prerequisite to references (bibxml, section numbers/names) that auto-update.

Grüße, Carsten