Re: [xml2rfc] rfc2629-xhtml.ent warning

Robert Moskowitz <rgm@htt-consult.com> Tue, 16 May 2023 14:05 UTC

Return-Path: <rgm@htt-consult.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 6A66DC151B14; Tue, 16 May 2023 07:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 6DyTGYE0Ayl6; Tue, 16 May 2023 07:05:10 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85B73C1519BD; Tue, 16 May 2023 07:05:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 631C26258A; Tue, 16 May 2023 10:04:47 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id RgYRRCXY1TKS; Tue, 16 May 2023 10:04:44 -0400 (EDT)
Received: from [192.168.160.29] (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id DD04862574; Tue, 16 May 2023 10:04:43 -0400 (EDT)
Message-ID: <ff083624-b9f3-f125-5f65-08625cf11f72@htt-consult.com>
Date: Tue, 16 May 2023 10:05:05 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
Content-Language: en-US
To: Jay Daley <exec-director@ietf.org>
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <b09e9607-966a-6250-db4b-5d541b1e690d@htt-consult.com> <EA51BFDA-0A1C-49DA-8301-FDF9BD805D2E@ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
In-Reply-To: <EA51BFDA-0A1C-49DA-8301-FDF9BD805D2E@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/Mlvij5D9sJXQCyEqi1KNmJcx7iY>
Subject: Re: [xml2rfc] rfc2629-xhtml.ent warning
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, 16 May 2023 14:05:11 -0000


On 5/16/23 09:19, Jay Daley wrote:
>> On 16 May 2023, at 14:12, Robert Moskowitz <rgm@htt-consult.com> wrote:
>>
>> It has been a few weeks since my last run of xml2rfc, and that was on what I had installed on my old Fedora 35 notebook, now on my updated Fedora 38 system...
>>
>> So this morning I got (4 times):
>>
>> Warning: /home/rgm/data/htt/Projects/Critical/drafts/rfc2629-xhtml.ent is no longer needed as the special processing of non-ASCII characters has been superseded by direct support for non-ASCII characters in RFCXML.
>>
>>
>> The only use of rfc2629 in my xml is:
>>
>> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
>> <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
>>
>> So obviously there has been a change that I did not catch.  No comments from the rfc editor on working with my drafts a couple months back for rfcs 9373 & 9374 that had these lines.
>>
>> So what is the current for !DOCTYPE and xml-stylesheet?
> A DOCTYPE is not recommended because the grammar is specified in Compact RelaxNG not any other schema format.   The recommended method to associate the schema with the XML is
>
> 	<?xml-model href="rfc7991bis.rnc"?>
>
> Note, this will require you to have rfc7991bis.rnc in your build path.

I deleted those 2 lines and the build went well.  Don't know for how 
many years I have had them in.  Perhaps when I upgraded all my drafts to v3?

>
> This is fully explained in the authors documentation here:
>
> 	https://authors.ietf.org/en/templates-and-schemas
>
> That same page also links to the "official" templates that can be used as starting points.

I probably could have gone back to starting point with this new draft.

>
> Finally, the authors documentation also lists various XML editors and how the interact with the schema
>
> 	https://authors.ietf.org/en/drafting-in-xml
>
> Jay
>
>> thanks
>>
>>
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc