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

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
>   