IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Mon, 26 June 2023 20:55 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 C0B17C15171E for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 13:55:11 -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 PFMq5sMw2za7 for <xml2rfc@ietfa.amsl.com>; Mon, 26 Jun 2023 13:55:11 -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 46B23C1516E9 for <xml2rfc@ietf.org>; Mon, 26 Jun 2023 13:55:11 -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 1qDtEr-000cPO-2K; Mon, 26 Jun 2023 20:55:09 +0000
Date: Mon, 26 Jun 2023 13:55:08 -0700
Message-ID: <m21qhyueoj.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: XML2RFC Interest Group <xml2rfc@ietf.org>
In-Reply-To: <B71CAF97-2924-47FF-B28C-61E9C1B93CB1@tzi.org>
References: <m25y7auglb.wl-randy@psg.com> <B71CAF97-2924-47FF-B28C-61E9C1B93CB1@tzi.org>
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="ISO-8859-7"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/xIkmd7jVMo2V33c56oq9K0AxWKA>
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:55:11 -0000

>> 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.

bummer that

> 3.17.4 newly informs you that the PIs you are using have been
> deprecated a long time ago in RFCXMLv3.

i have a local rsunk repo and am doing

    <references title="Normative References">
      <?rfc include="reference.RFC.2119.xml"?>
      <?rfc include="reference.RFC.2622.xml"?>
      <?rfc include="reference.RFC.2725.xml"?>

what should i be doing if i want to go to xml heaven?

randy

v2.23.0 | Report a Bug | By Email