IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Tue, 27 June 2023 05:05 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 16D21C1524AA for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 22:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.888
X-Spam-Level:
X-Spam-Status: No, score=-6.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01] 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 adpO9BwVA_nc for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 22:04:59 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (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 15007C151527 for <xml2rfc@ietf.org>; Mon, 26 Jun 2023 22:04:57 -0700 (PDT)
Received: from smtpclient.apple (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Qqt1h02YbzDCdM; Tue, 27 Jun 2023 07:04:55 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAD2=Z84T0ALPnF_abws8zixooaVsY8XJeipYS6nvmWWwry9pLw@mail.gmail.com>
Date: Tue, 27 Jun 2023 07:04:45 +0200
Cc: Robert Sparks <rjsparks@nostrum.com>, XML2RFC Interest Group <xml2rfc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEAEBC3E-CEAE-494B-9551-E5D178E86FC3@tzi.org>
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> <CAD2=Z86QZ1qMK1=8L2Vo7c=0N0LCPOOdh5QT_OMudAKQNu6FJQ@mail.gmail.com> <2966D571-310C-463F-8C22-B95F28490A6F@tzi.org> <CAD2=Z84T0ALPnF_abws8zixooaVsY8XJeipYS6nvmWWwry9pLw@mail.gmail.com>
To: Kesara Rathnayake <kesara@staff.ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/pvMPcWDGOVmK05u4R3gmArhVXFI>
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 05:05:05 -0000

On 27. Jun 2023, at 06:54, Kesara Rathnayake <kesara@staff.ietf.org> wrote:
> 
> I'm under the impression that we need to move away from using PIs.

PIs are great for doing things that are instructions on the processing.
(They are not so great for the actual content of the document.)
Compare pragmas in programming languages.

There used to be a feature that could be invoked like this:

<?v3xml2rfc silence="XInclude should be used instead of PI include" ?>

I can’t get this to work though with 3.17.4.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email