Ability to validate RFCXML v3

[ajeanmahoney]

No description provided.

[JayDaley]

It would be useful to determine if this is
(a) continuous background validation; or
(b) user initiated validation
(c) both
I use tools that follow (c) and mainly rely on (a) but occasionally have to use (b)

[JayDaley]

It would also be useful to determine what grammar to use for the validation:
(a) Automatically using whatever is specified in an <?xml-model ...>
(b) A specific grammar file pointed to by the user, possibly also overriding any <?xml-model ...>. This could tie in with (b) from the comment above with two manual validation options

• Validate now
• Validate using ...

[ajeanmahoney]

The basics: validate RFCXML v3 upon opening a file and upon saving. Continuous validation would be great

[ajeanmahoney]

DraftForge highlights the generic xinclude mechanism as a schema error:

element "xi:include" not allowed anywhere; expected the element end-tag 
or element "reference", "referencegroup" or "references"xml(unknown_element)

However, the RPC uses xincludes for RFC and I-D references. This should not be flagged as an error:

<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8017.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-rats-reference-interaction-models.xml"/>