Re: [xml2rfc] Why development version dislikes <!ENTITY RFC2119 PU BLIC ...
elwynd@dial.pipex.com Wed, 27 July 2011 04:21 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 15B6E11E80BB for <xml2rfc@ietfa.amsl.com>; Tue, 26 Jul 2011 21:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 wEdl8gUkQ0Ie for <xml2rfc@ietfa.amsl.com>; Tue, 26 Jul 2011 21:21:26 -0700 (PDT)
Received: from auth.a.painless.aaisp.net.uk (auth.a.painless.aaisp.net.uk [IPv6:2001:8b0:0:30:230:48ff:fe72:d05c]) by ietfa.amsl.com (Postfix) with ESMTP id D3FCA11E8079 for <xml2rfc@ietf.org>; Tue, 26 Jul 2011 21:21:18 -0700 (PDT)
Received: from qubcpq14-1176054427.sdsl.bell.ca ([70.25.42.155] helo=[192.168.2.111]) by a.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1QlvcO-0007bp-5G; Wed, 27 Jul 2011 05:21:12 +0100
From: elwynd@dial.pipex.com
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Date: Wed, 27 Jul 2011 00:20:28 -0400
Message-ID: <jFfK26qsLg1C.vl2Vfyvw@smtp.aaisp.net.uk>
X-Mailer: EPOC Email Version 2.10
MIME-Version: 1.0
Content-Language: i-default
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: xml2rfc <xml2rfc@ietf.org>
Subject: Re: [xml2rfc] Why development version dislikes <!ENTITY RFC2119 PU BLIC ...
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: Wed, 27 Jul 2011 04:21:27 -0000
- original message - Subject: Re: [xml2rfc] Why development version dislikes <!ENTITY RFC2119 PUBLIC ... From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp> Date: 27/07/2011 2:23 am Hello Elwyn, On 2011/07/27 3:27, Elwyn Davies wrote: > 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'm a bit confused here. I have looked at this, and it only contains <!DOCTYPE rfc SYSTEM "rfc2629.dtd">, no ENTITY declarations. Can you check again? Regards, Martin. Hi, Marti. I just reloaded it and it does indeed show 3 x PUBLIC and 10 x SYSTEM entities. They are in the page sourc/e if displayed directly with Firefox or if saving link. regards, Elwyn. >>> 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 > _______________________________________________ > xml2rfc mailing list > xml2rfc@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc >