There isn't a way - since <?rfc include="..."?> is only a processing
instruction (not a real XML include construct), the file without
preprocessing *is* technically invalid. However, xxe will still work
fine, and xml2rfc will still work fine, so as long as these are the
only errors you don't have to worry about them.
Bill
If your only goal is to be compatible with XXE and xml2rfc, then <rfc
include> directives are fine. If you need to have valid XML for a
different editor, or other tools, then you might want valid XML.
An alternative that works in XXE and xml2rfc and is also technically
valid XML is to use ENTITY statements rather than <rfc include>
directives. This approach requires specifying what should be included
later in the document at places marked by &rfc3411; style markers.
See http://tools.ietf.org/tools/templates/mib-doc-template-xml.txt for
an example of this approach.
The <rfc include> directive approach may feel more natural for a
programmer that uses includes in their programming source files. The
ENTITY approach requires thinking of the problem slightly differently.
David Harrington
dbharr...@comcast.net
iet...@comcast.net
dharr...@huawei.com
> I am guessing that the problem is that both of these sections only use
> <?rfc include="..." ?> directives. However, I am not clear how to fix
> this.
From the sound of it, that is exactly correct.
Yes, you can fix this. You do so by using the other form of include.
That, however, forces you to use xml2rfc exclusively when attached to
the network, as it goes to central locations to find the files. I use
the <?rfc form and keep a local cache of the reference files so that
I can use it at my leisure.
- Philip