[rfc-i] draft-hoffman-rfcexamples-04, "3. Example of a v3 Document"

HANSEN, TONY L tony at att.com
Sun Feb 28 19:55:16 PST 2016


On 2/27/16, 5:20 PM, "rfc-interest on behalf of Julian Reschke" <rfc-interest-bounces at rfc-editor.org on behalf of julian.reschke at gmx.de> wrote:


>On 2016-02-27 21:47, Paul Hoffman wrote:
>> On 27 Feb 2016, at 11:37, Julian Reschke wrote:
>>
>>> <http://greenbytes.de/tech/webdav/draft-hoffman-rfcexamples-04.html#rfc.section.3>:
>>>
>>>
>>>> The following is a v3 document that has all the elements that are
>>>> needed for typical Internet-Drafts. It was converted from the example
>>>> in Section 2.
>>>>
>>>> <?xml version='1.0' encoding='US-ASCII'?>
>>>> <!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
>>> > ...
>>>
>>> I think this shouldn't reference the RFC 2629 DTD...
>>
>> But should instead reference ... ?
>>
>> --Paul Hoffman
>
>
>Nothing. There is no DTD for V3.


I've looked at convertv2v3. The reference exists in the original v2 doc and is just preserved. That is, this is the entry in the v2 doc:

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
   <!ENTITY RFC2119 SYSTEM
     "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
   ]>

All of the ENTITY references are pulled out and changed to x:includes. Then the remaining DOCTYPE was then just left alone, with no special checks as to what DTD was being referenced.

I guess I can add some code to check for this special case and remove the DTD entirely if it's an rfc2629.dtd reference.

	Tony


More information about the rfc-interest mailing list