Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema Issue, RFC 7991, In Section 2.42, <references> #49

Closed
levkowetz opened this issue Oct 8, 2018 · 3 comments
Closed

Schema Issue, RFC 7991, In Section 2.42, <references> #49

levkowetz opened this issue Oct 8, 2018 · 3 comments

Comments

@levkowetz
Copy link
Contributor

In Section 2.42, <references>

The v3 schema cannot properly model multiple reference subsections
contained within one numbered section. The v2 formatter handled this by
silently inserting an enclosing section, but with the introduction of
the preptool, which in theory should produce a master file from which
various formatters would produce equivalent results, this becomes
troublesome, as the automatic insertion of a container section is
specified for the html formatter, in section 9.8. of RFC 7992, but not
for the text formatter. It would be much better to make the prepped xml
explicitly show exactly what should be rendered, and not rely on
formatters silently insert elements.

Proposal: Update the schema to make it possible for <references>
to contain <references>, and have the prepped xml
explicitly show both the encapsulating section and the
subsections.

Implementation: Implemented as proposed in the current version of
xml2rfc.

@paulehoffman
Copy link
Contributor

Consensus was to implement.

@reschke
Copy link
Contributor

reschke commented Mar 8, 2019

How deep can <references> be nested?

@paulehoffman
Copy link
Contributor

Closed with PR #70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants