You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The grammar describes the <name> child element as optional, but xml2rfc requires it
Allowing nesting implies that there now can be deeper hierarchies; this needs to be discussed and potentially disallowed in prose
The <back> element still allows multiple <references> child elements; either the grammar should be restricted or this should be mentioned in prose (this might also require changes in the Style Guide); in particular, a v2 processor will handle two <references> entries in <back> differently than xml2rfv in v3 mode (and that's really confusing)
...as done for #49:
Proposal: back out the change; it's not needed and was indeed discussed before and rejected. The problem discussed in https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-00#section-3.1.6 could be fixed simply by moving the associated text from the HTML spec to the vocabulary spec.
Potential extension:
The text was updated successfully, but these errors were encountered: