IETF Logo Mail Archive

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

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 18 December 2019 19: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 1C80D120B87 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 11:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.95
X-Spam-Level:
X-Spam-Status: No, score=-4.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, 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 VXiiabH0uYCQ for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 11:22:20 -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 8E3E0120B81 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 18 Dec 2019 11:22:20 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C4050F4071C; Wed, 18 Dec 2019 11:21:59 -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 ACE5EF4071C for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 11:21:58 -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 9OVV-Cvjcz6M for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 11:21:57 -0800 (PST)
Received: from mail-oi1-f180.google.com (mail-oi1-f180.google.com [209.85.167.180]) by rfc-editor.org (Postfix) with ESMTPS id 11A73F4071B for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 11:21:57 -0800 (PST)
Received: by mail-oi1-f180.google.com with SMTP id b8so1712437oiy.5 for <rfc-interest@rfc-editor.org>; Wed, 18 Dec 2019 11:22:15 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iLUbiqE6FUQ9LhjhdQW4UJCC2LWzLa7+/FRg8OOXDXg=; b=J0OK9A/BcXPFvzsUonSZmEJUc3YplV9r+ITYusjRxodPEw4UsRqyxJAAQ3sHXdAxvZ WjjsnszpbG/Bhxd93hXH94kI2ErBHxehFwNwSQRGVihha0E4XJvxjMh706dAGW3xY7Y5 ZSbGPV0lQ0GgMsSQYnOtD03E31HyHvQ+hRsZsYD51eDA+smrzSpt686cPcVxwx3Wdj6p lEGZzb95c9SGoXxnkDHQZAZ2Ngek2ooG5o0uGdcmS8r8p3BA0b2s2bVkAuXxPjzvEj1m 4taQecQzNYwLM8wa9brA7ISi1zTtL2QM9z1r2S9cu7Q4ghPsNHP11G61qb/Hl2OzZX9c uKfg==
X-Gm-Message-State: APjAAAXp9tabrp2eDupiWPKkqfGQu8nEDWFefW2Ozm3RPM3Pg+SpN4+4 hVcJOBq9CWNkA5rnqrLIcG+E2RX5b6dhCAGtFmI=
X-Google-Smtp-Source: APXvYqxZ57ZlF1UzyqbWFNDVCLE0sklPujeqSRXkXbnABzEtZSXAbbSzRk7hA9WakM9UgH405JkwwmtpZwYRpnSqlSI=
X-Received: by 2002:a05:6808:3a9:: with SMTP id n9mr1212241oie.31.1576696934962; Wed, 18 Dec 2019 11:22:14 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <3a685a70-b0d0-5d72-64eb-7d900d4587ab@gmx.de>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 18 Dec 2019 14:22:03 -0500
Message-ID: <CAMm+LwineZzC+CkF93nBFY0=4uTLXZTCcNAnitE4N4QvRG+YWw@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
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: RFC Interest <rfc-interest@rfc-editor.org>, Pete Resnick <resnick@episteme.net>
Content-Type: multipart/mixed; boundary="===============0461370046137305107=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

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

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.

It would be nice if you could add my <norm> and <info> elements or add an
attribute to xref to capture this info so that I can round trip source docs
between the Word, Markdown and XML representations without loss of
information.


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.

_______________________________________________
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