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

BCP 14 boilerplate detection #43

Open
martinthomson opened this issue Oct 29, 2024 · 0 comments
Open

BCP 14 boilerplate detection #43

martinthomson opened this issue Oct 29, 2024 · 0 comments

Comments

@martinthomson
Copy link

The following warning:

 6  Warning
 └- Code - MISSING_NOTRECOMMENDED_IN_BOILERPLATE
 └- Desc - The keyword NOT RECOMMENDED appears but not included in the RFC2119 boilerplate.
 └- Ref  - https://www.rfc-editor.org/rfc/rfc7322.html#section-4.8.2

...is the only one related to BCP 14. The XML I have looks like so:

      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP¤14 <xref target="BCP14"/> when, and only when, they
appear in all capitals, as shown here.</t>

(This is the new form that kramdown-rfc produces from {::boilerplate bcp14-tagged-bcp}, which uses a BCP reference rather than the two RFC references that used to be used. I can't see how that leads to this specific problem though.)

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

No branches or pull requests

1 participant