IETF Logo Mail Archive

Re: [xml2rfc] XInclude should be used instead of PI include

Robert Sparks <rjsparks@nostrum.com> Mon, 26 June 2023 23:17 UTC

Return-Path: <rjsparks@nostrum.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 E4680C151540 for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 16:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.076
X-Spam-Level:
X-Spam-Status: No, score=-7.076 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJyPd9IYfpQJ for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 16:17:34 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0AA9C14F75F for <xml2rfc@ietf.org>; Mon, 26 Jun 2023 16:17:33 -0700 (PDT)
Received: from smtpclient.apple (mobile-166-173-58-67.mycingular.net [166.173.58.67]) (authenticated bits=0) by nostrum.com (8.17.2/8.17.1) with ESMTPSA id 35QNHUxK020507 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 26 Jun 2023 18:17:32 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1687821452; bh=IEildPsbF5sPviR/7Xs/kENVNpgQnZhqisbUkGZuLZs=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=kztvyksR7LpDPL6pfDn0igC4Tg7wGfbLTCVaFWgWS9hsmf+CKyDsg+vSAlLV+8Oqw Oqs1bG8dmigImLPE8rjj2xi74ZWQ+UWmicFmBSNLPZsZlv/e6XsbR30VWMVWaIf3TK VbeS3VNx6UTzayiWAgm+mnJWVYCSDtKcG/Qdy5iA=
X-Authentication-Warning: raven.nostrum.com: Host mobile-166-173-58-67.mycingular.net [166.173.58.67] claimed to be smtpclient.apple
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Robert Sparks <rjsparks@nostrum.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 26 Jun 2023 18:17:15 -0500
Message-Id: <1C2D7469-A3FE-4029-9F5F-649E2AC3B390@nostrum.com>
References: <m2v8f9ua1d.wl-randy@psg.com>
Cc: xml2rfc@ietf.org
In-Reply-To: <m2v8f9ua1d.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: iPhone Mail (20F75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/-8-l7yM9uklW1bt4aOH7vGM_-5E>
Subject: Re: [xml2rfc] XInclude should be used instead of PI include
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <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, 26 Jun 2023 23:17:38 -0000


Sent from my iPhone

> On Jun 26, 2023, at 5:35 PM, Randy Bush <randy@psg.com> wrote:
> 
> 
>> 
>>>> i have a local rsunk repo and am doing
>>>> 
>>>>    <references title="Normative References">
>>>>      <?rfc include="reference.RFC.2119.xml"?>
>> 
>> That would look like <xi:include
>> href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
>> 
>> All of Carsten's observation about this hardcoding an external
>> reference and that the URLs have been changing a _lot_ recently are
>> correct, as you can see from the before-preptool source for one of the
>> most recently published RFCs:
>> 
>> rjsparks@undex feat-rfc % curl --no-progress-meter
>> https://www.rfc-editor.org/prerelease/rfc9425.notprepped.xml | grep
>> 8174
>>     <xref target="RFC8174"/> when, and only when, they appear in all
>> capitals,
>> <xi:include
>> href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
>> 
>> (The RPC is shifting to using bib.ietf.org to which xml2rfc.ietf.org
>> redirects).
>> 
>> For Internet-Drafts, you'll need to use an href that looks like
>> 
>> https://bib.ietf.org/public/rfc/bibxml-ids/reference.I-D.ietf-rtgwg-segment-routing-ti-lfa.xml
>> 
>> That is, using xi:include comes with the extra burden of knowing the
>> names of the bibxml datasets.
>> 
>> There are conversations ongoing about how to avoid these
>> author-unfriendly aspects.
> 
> i demand a refund!!!!
> 
> i need to build when there is no net connectivity.  this is why i have
> rsunc repos.

I hear you
> 
> randy

v2.23.0 | Report a Bug | By Email