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

Elwyn Davies <elwynd@dial.pipex.com> Tue, 26 July 2011 17:14 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 976A021F8B30 for <xml2rfc@ietfa.amsl.com>; Tue, 26 Jul 2011 10:14:20 -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=[AWL=0.000, 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 u0B7nLMuyHO9 for <xml2rfc@ietfa.amsl.com>; Tue, 26 Jul 2011 10:14:20 -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 7492821F8A57 for <xml2rfc@ietf.org>; Tue, 26 Jul 2011 10:14:19 -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 1QllCy-0001TK-VA; Tue, 26 Jul 2011 18:14:17 +0100
Message-ID: <4E2EF5E7.8010502@dial.pipex.com>
Date: Tue, 26 Jul 2011 18:14:15 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20081209)
MIME-Version: 1.0
To: Brian Rosen <br@brianrosen.net>
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> <379B976F-2426-4472-AFA5-9B4BEF4E17CB@brianrosen.net>
In-Reply-To: <379B976F-2426-4472-AFA5-9B4BEF4E17CB@brianrosen.net>
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
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 17:14:20 -0000

Yes. I checked that..

/E
Brian Rosen wrote:
> Are your ENTITYs in DOCTYPE:
> <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
>
> <!ENTITY RFC2119 PUBLIC ''
>  'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
>
> ]>
>
> That is what Brian Carpenter found was needed.
>
> Brian
>
> On Jul 26, 2011, at 11:24 AM, 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
>>
>>
>>
>>
>> Brian E Carpenter wrote:
>>     
>>> On 2011-07-26 16:14, Martin J. Dürst wrote:
>>>  
>>>       
>>>> Hello Brian,
>>>>
>>>> On 2011/07/26 11:39, Brian E Carpenter wrote:
>>>>    
>>>>         
>>>>> It appears that the new code requires ENTITY definitions
>>>>> to be embedded within the DOCTYPE declaration. This has never been
>>>>> the case before. Thus:
>>>>>
>>>>> <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
>>>>>
>>>>> <!ENTITY RFC2119 PUBLIC ''
>>>>>   'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
>>>>>
>>>>> ]>
>>>>>
>>>>> I suspect a lot of existing source files would be invalidated by this
>>>>> requirement.
>>>>>      
>>>>>           
>>>> Sorry, but that would actually be a good thing.     
>>>>         
>>> Yes, if it is carefully announced and introduced at a specific date.
>>> I have no trouble with fixing my source files, but I need to be told.
>>> (The diagnostic was quite helpful in that it pointed to exactly
>>> the line that was causing the problem, but I could only isolate the
>>> problem by a line-by-line comparison with Elwyn's future-proof
>>> tutorial example. That's not satisfactory for the entire user
>>> population.)
>>>
>>>    Brian
>>>
>>>
>>>  
>>>       
>>>> Free-standing ENTITY
>>>> declarations are not allowed by XML. Please see:
>>>>
>>>> http://www.w3.org/TR/REC-xml/#NT-doctypedecl
>>>> http://www.w3.org/TR/REC-xml/#NT-EntityDecl
>>>>
>>>> This slipped through the cracks up to now because the Tcl implementation
>>>> was very ad-hoc. The new implementation uses a parser library, I guess
>>>> (would be crazy if it didn't).
>>>>
>>>> Of all things, we don't want to give the impression that the IETF is
>>>> calling something XML that isn't.
>>>>
>>>> Regards,    Martin.
>>>>
>>>>    
>>>>         
>>> _______________________________________________
>>> xml2rfc mailing list
>>> xml2rfc@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>>  
>>>       
>> _______________________________________________
>> xml2rfc mailing list
>> xml2rfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc
>>     
>
>