IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Tue, 27 June 2023 10:44 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 491CFC1575D0 for <xml2rfc@ietfa.amsl.com>; Tue, 27 Jun 2023 03:44:14 -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 x5tdpRsQ9AqP for <xml2rfc@ietfa.amsl.com>; Tue, 27 Jun 2023 03:44:10 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 5FF78C1522CD for <xml2rfc@ietf.org>; Tue, 27 Jun 2023 03:44:08 -0700 (PDT)
Received: from client-0227.vpn.uni-bremen.de (client-0227.vpn.uni-bremen.de [134.102.107.227]) (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 4Qr1Y11ZC3zDCfD; Tue, 27 Jun 2023 12:44:05 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAD2=Z85FjsO3cNCGpFX2oTRhfvafgLGb4ZATzMNPt4VTsGQtpw@mail.gmail.com>
Date: Tue, 27 Jun 2023 12:44:04 +0200
Cc: XML2RFC Interest Group <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 709555444.7595659-04770908e45a6e6f32f005b3ee03f9a3
Content-Transfer-Encoding: quoted-printable
Message-Id: <036A7C36-3100-4175-8A90-6F35C1E8C0C5@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> <BEAEBC3E-CEAE-494B-9551-E5D178E86FC3@tzi.org> <CAD2=Z85FjsO3cNCGpFX2oTRhfvafgLGb4ZATzMNPt4VTsGQtpw@mail.gmail.com>
To: Kesara Rathnayake <kesara@staff.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/eazCO_yUgMm3Qe4Jd7XNU6fiVmc>
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 10:44:14 -0000

Hi Kesara,

On 2023-06-27, at 07:27, Kesara Rathnayake <kesara@staff.ietf.org> wrote:
> 
> XInclude / PI include retrievals happen in a very early stage in xml2rfc.
> At that stage warning silence process is not initiated so you cannot
> silence that warning.

Ah, interesting.
(I checked that the command line argument --silence also doesn’t have an effect on this.)

> This is probably a bug.

Now
https://github.com/ietf-tools/xml2rfc/issues/1012

Thank you!

Grüße, Carsten

v2.23.0 | Report a Bug | By Email