IETF Logo Mail Archive

Re: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]

"Pete Resnick" <resnick@episteme.net> Wed, 18 December 2019 20:22 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB9661208C4 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 12:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.951
X-Spam-Level:
X-Spam-Status: No, score=-4.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 68BuPOk-Fpr9 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 12:22:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 482FF120A28 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 18 Dec 2019 12:22:48 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 23B35F4071D; Wed, 18 Dec 2019 12:22:29 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 25259F4071D for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 12:22:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2B-1zv2luP7 for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 12:22:26 -0800 (PST)
Received: from episteme.net (episteme.net [216.169.5.102]) by rfc-editor.org (Postfix) with ESMTPS id AC5ADF406D8 for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 12:22:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 6AB9997FFD69; Wed, 18 Dec 2019 14:22:43 -0600 (CST)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gxkqo848tr-B; Wed, 18 Dec 2019 14:22:41 -0600 (CST)
Received: from [172.16.1.18] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 691C697FFD56; Wed, 18 Dec 2019 14:22:41 -0600 (CST)
From: Pete Resnick <resnick@episteme.net>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 18 Dec 2019 14:22:40 -0600
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <12C0558E-2C76-4631-9165-07F71BC1B9D6@episteme.net>
In-Reply-To: <CAMm+LwineZzC+CkF93nBFY0=4uTLXZTCcNAnitE4N4QvRG+YWw@mail.gmail.com>
References: <0e6427dd-df73-4946-a688-e02e9d68ae65@joelhalpern.com> <64ec190d-62fe-bcf1-ffd6-012d0da403f3@gmx.de> <8A76E9C0-921E-42CF-8EDD-6F95A91C06F4@amsl.com> <84D67BB2-D6A0-4CE6-827F-ABD130E7B512@episteme.net> <4a1d77bf-e2ed-af69-d0fb-7626c2c53b76@gmx.de> <93AC374E-D9F9-4261-94EA-25C6EFF11A78@episteme.net> <3a685a70-b0d0-5d72-64eb-7d900d4587ab@gmx.de> <CAMm+LwineZzC+CkF93nBFY0=4uTLXZTCcNAnitE4N4QvRG+YWw@mail.gmail.com>
MIME-Version: 1.0
Subject: Re: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: Julian Reschke <julian.reschke@gmx.de>, RFC Interest <rfc-interest@rfc-editor.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 18 Dec 2019, at 13:22, Phillip Hallam-Baker wrote:

> I would have a real problem with the bibxml containing <xi:include/>. 
> It
> would break my systems when running in offline mode.

Like I said, I am ambivalent about the specific implementation, just 
that it would be nice for the files to exist. That said:

> I use tags of the form <norm target="RFC822"> to specify links to 
> RFCs.
> These cause the processor to attempt to resolve the reference against 
> a
> local cache followed by an external network request if it fails.
>
> If you put <xi:include/> in the bibxml files they are now tied to the
> network reference and I have to do a lot of work to undo that so I can
> cache them correctly.

You could also resolve the includes when you build your cache.

> The subtler issue this brings up is that RFC822 is a fixed reference 
> that
> will never change meaning while BCP14 is not. It can and does change 
> over
> time.

Which says that you're going to have to refresh your cache for BCP and 
STD regularly to make sure you've got the latest contents.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email