IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Mon, 26 June 2023 20:51 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 7D8DAC1516E9 for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 13:51:24 -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 Xjp0YSLEpt96 for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 13:51:21 -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 C0419C14F75F for <xml2rfc@ietf.org>; Mon, 26 Jun 2023 13:51:21 -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 4Qqg46747jzDCc3; Mon, 26 Jun 2023 22:51:18 +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: <m25y7auglb.wl-randy@psg.com>
Date: Mon, 26 Jun 2023 22:51:08 +0200
Cc: XML2RFC Interest Group <xml2rfc@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B71CAF97-2924-47FF-B28C-61E9C1B93CB1@tzi.org>
References: <m25y7auglb.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/orIgtiQ3W8hDaw6Wiih5IjJYO54>
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 20:51:24 -0000

On 26. Jun 2023, at 22:13, Randy Bush <randy@psg.com> wrote:
> 
> macosx ventura
> xml2rfc 3.17.4
> 
> i am suddenly getting a mass of
> 
> Warning: XInclude should be used instead of PI include for reference.RFC.4632.xml
> Warning: XInclude should be used instead of PI include for reference.RFC.5485.xml
> Warning: XInclude should be used instead of PI include for reference.RFC.7234.xml
> Warning: XInclude should be used instead of PI include for reference.RFC.7485.xml
> Warning: XInclude should be used instead of PI include for reference.RFC.7909.xml
> 
> clue bat please?

You can safely ignore this message.
(You won’t go to XML heaven, though.
3.17.4 newly informs you that the PIs you are using have been deprecated a long time ago in RFCXMLv3.
Which is not a problem, as the RFC editor will fix this in the course of their routine replacement of all the reference mechanics during draft ingestion.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email