IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Tue, 27 June 2023 14:47 UTC

Return-Path: <randy@psg.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 26AC8C1519AD for <xml2rfc@ietfa.amsl.com>; Tue, 27 Jun 2023 07:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 r2TL99fKy60x for <xml2rfc@ietfa.amsl.com>; Tue, 27 Jun 2023 07:47:05 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A982FC151551 for <xml2rfc@ietf.org>; Tue, 27 Jun 2023 07:47:05 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.93) (envelope-from <randy@psg.com>) id 1qE9yA-000fXm-Ad; Tue, 27 Jun 2023 14:47:02 +0000
Date: Tue, 27 Jun 2023 07:47:01 -0700
Message-ID: <m2jzvpt122.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: xml2rfc@ietf.org
In-Reply-To: <938b00d1-5fb7-3e75-a682-1c4799acde02@gmx.de>
References: <m25y7auglb.wl-randy@psg.com> <B71CAF97-2924-47FF-B28C-61E9C1B93CB1@tzi.org> <m21qhyueoj.wl-randy@psg.com> <2612E60E-6B70-44DE-A87A-5ADB7F21F923@tzi.org> <40975c07-be1c-124b-f9fa-6d8a979157b5@nostrum.com> <m2v8f9ua1d.wl-randy@psg.com> <938b00d1-5fb7-3e75-a682-1c4799acde02@gmx.de>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/rzWgoL5lN3umv-2GYr4khDpmF9U>
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: Tue, 27 Jun 2023 14:47:06 -0000

>> i need to build when there is no net connectivity.  this is why i
>> have rsunc repos.
> 
> That is supposed to be possible with xi:include and relative
> references.

recipe for idiots, please.

and no, jay, i do not think it is reasonable to ask a routing,
security, ... person to deep dive xml rfcs in order to use the
principal tool set.

randy

v2.23.0 | Report a Bug | By Email