Open paulehoffman opened 5 months ago
To help clarify:
Are you looking at idnits3 or idnits2? (You must be looking at idnits3 if it's inspecting the xml)?
idnits3 expects v3, not the hybrid v2/v3 that kramdown-rfc currently produces. kramdown-rfc would need to be run through --v2v3 before it would make sense to feed it to idnits3.
v3, definitely. (Sorry for not being specific; I'm looking at v3 now.)
I will change to using --v2v3, but think the report might still stand: processing instructions are generic to all XML, not just what is produced by kramdown.
Post-processing with xml2rfc --v2v3 still produces XML with the same processing instructions.
Perhaps we warn that PIs are present but otherwise ignore them?
That is OK, or not even "warn" that they are present because they will be harmless to xlm2rfc. (That's assuming that xml2rfc ignores them when creating publication versions.)
The current version of kramdown-rfc adds procoessing instructions similar to the following to the XML output:
idnits currently flags these with
INVALID_ABSTRACT_SECTION_CHILD
andINVALID_INTRODUCTION_SECTION_CHILD
.