Re: [xml2rfc] Why development version dislikes <!ENTITY RFC2119 PUBLIC ...

Elwyn Davies <elwynd@dial.pipex.com> Tue, 26 July 2011 18:28 UTC

Return-Path: <elwynd@dial.pipex.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 A03BB21F888A for <xml2rfc@ietfa.amsl.com>; Tue, 26 Jul 2011 11:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NaUoH41WA9Ub for <xml2rfc@ietfa.amsl.com>; Tue, 26 Jul 2011 11:28:01 -0700 (PDT)
Received: from b.painless.aaisp.net.uk (b.painless.aaisp.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id ACA6721F873D for <xml2rfc@ietf.org>; Tue, 26 Jul 2011 11:28:00 -0700 (PDT)
Received: from dhcp-172d.meeting.ietf.org ([130.129.23.45]) by b.painless.aaisp.net.uk with esmtpa (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1QlmMI-0003L1-Gq; Tue, 26 Jul 2011 19:27:59 +0100
Message-ID: <4E2F072B.5030709@dial.pipex.com>
Date: Tue, 26 Jul 2011 19:27:55 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
References: <4E2DE139.5040205@gmail.com> <4E2DE7C0.5080108@gmx.de> <4E2E02A1.7060305@gmail.com> <4E2E10DA.7060608@gmail.com> <4E2E28FB.3070608@gmail.com> <4E2E3F32.3050509@it.aoyama.ac.jp> <4E2E4475.4070208@gmail.com> <4E2EDC1C.7000501@dial.pipex.com> <4E2F0102.6000802@gmx.de>
In-Reply-To: <4E2F0102.6000802@gmx.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: xml2rfc <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] Why development version dislikes <!ENTITY RFC2119 PUBLIC ...
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: elwynd@dial.pipex.com
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 26 Jul 2011 18:28:01 -0000

Julian Reschke wrote:
> On 2011-07-26 17:24, Elwyn Davies wrote:
>> Hi.
>>
>> Should have said draft is
>> http://tools.ietf.org/id/draft-irtf-routing-reqs-11.xml
>>
>> I just tried out an old draft that I know contains some unusual 
>> features.
>>
>> Unfortunately it didn't get as far as checking on these.
>>
>> I get a lot of error messages related to entity references:
>> My imported references are in the form
>>
>> *<!ENTITY* RFC3471 SYSTEM
>> "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3471.xml"*>
>>
>> The error messages are of the form:
>> *ERROR: Unable to validate the XML document: INPUT
>> Line 1406: IDREF attribute target references an unknown ID "RFC3471"
>>
>> The problem is doubtless that there are a number of different forms for
>> these ENTITY definitions!
>>
>> Regards,
>> Elwyn
>
> That may be an actual bug; my validators do not see any (serious) 
> problems with that source file.
>
> Best regards, Julian
:-)
Well it certainly used to go through earlier versions of xml2rfc! And 
the RFC Editor was happy with it!

The main reason for trying that draft was that it uses a numbered list 
that spans many sections which is a relatively unusual feature.

I know there is already a set of drafts/rfcs as test docs... Do we have 
a document that provides an (arcane) test of as many features as we 
think of?

Maybe the project plan includes a set of automated regression tests of 
this kind - if not I think that would be a useful idea.  Perhaps I ought 
to expand my  example file that I did when I did the xml2rfc tutorial.  
Would that be helpful or has it been done already?

Regards,
Elwyn