[rfc-i] [IAB] draft-hoffman-rfcexamples-04, "3. Example of a v3 Document"
Joe Hildebrand (jhildebr)
jhildebr at cisco.com
Tue Mar 1 10:12:34 PST 2016
Just expand all of the entity refs, and put the expansions in the v3. This has to be done before any of the other translations, in case included entities generate old-style XML.
This is the only way to not lose information, and to make sure that all of the included bits have been translated. If the document is too large at that point, the author can go back in and create x:includes as desired.
On 2/28/16, 11:19 PM, "IAB on behalf of Julian Reschke" <iab-bounces at iab.org on behalf of julian.reschke at gmx.de> wrote:
>On 2016-02-29 04:55, HANSEN, TONY L wrote:
>> 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
>> 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.
>Well, there are other cases that need to be considered. What would you map
><!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
> <!-- re-declare " " as code point 160 (non-breaking space) -->
> <!-- you may need this for UAs that do not read external DTDs -->
> <!ENTITY nbsp
> " ">
>In general, how does the conversion treat Internal Entities defined in
>the document to-be-converted? And how does it treat those defined by
>rfc2629.dtd (and included files)?
>Best regards, Julian
More information about the rfc-interest