Skip to content
New issue

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

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

Already on GitHub? # to your account

style guide: no requirements in "Examples" sections #4382

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ralfhandl
Copy link
Contributor

@ralfhandl ralfhandl commented Feb 25, 2025

Follow-up to #4339 (comment).

PR #4339 added text to an "Examples" section that used requirements language with "MUST" and "MAY". In this case the text was just copied verbatim from "non-example" sections of the spec, and no new requirements were added.

Better style is to

  • not to add requirements in a section called "Examples" or similar because readers may be confused whether these are really normative requirements or just explanations to the examples
  • not to use requirements language in explanations to examples

Tick one of the following options:

  • schema changes are included in this pull request
  • schema changes are needed for this pull request but not done yet
  • no schema changes are needed for this pull request

@ralfhandl ralfhandl added the editorial Wording and stylistic issues label Feb 25, 2025
@ralfhandl ralfhandl requested review from a team as code owners February 25, 2025 09:10
style-guide.md Outdated
@@ -21,6 +21,7 @@ The following additional rules should be followed but currently are not enforced
9. Use [Oxford commas](https://en.wikipedia.org/wiki/Serial_comma), avoid [Shatner commas](https://www.latimes.com/archives/blogs/jacket-copy/story/2011-06-30/goodbye-oxford-comma-hello-shatner-comma).
10. Use `<span id="thing"></span>` for link anchors. The `<a name="thing"></a>` format has been deprecated.
11. Headings use [title case](https://en.wikipedia.org/wiki/Title_case) and are followed by a blank line.
12. Do not add requirements in "Examples" sections, and avoid [RFC2119 key words (MUST, MAY, ...)](https://datatracker.ietf.org/doc/html/rfc2119) in these sections.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are requirements here? Is that the same thing as using a MUST/MAY keyword. Would it be accurate to say that this sort of content needs to be in a different section?

@lornajane
Copy link
Contributor

I tried to follow the thread of the other pull request, some comments, and what caused this change, but I'm not really clear, sorry. Could you add a note to the pull request description about what problem this solves or what we need to do or not do? I think it would help to inform the reviewer (me!)

@ralfhandl ralfhandl requested review from lornajane and a team February 28, 2025 08:23
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
editorial Wording and stylistic issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants