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

Improve references classification and uses of MUST and SHOULD #11

Merged
merged 4 commits into from
Feb 23, 2024

Conversation

jiceatscion
Copy link
Contributor

There's still some more MUST required IMHO.

Copy link
Member

@nicorusti nicorusti left a comment

Choose a reason for hiding this comment

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

Hi JC, IN see that you left several should etc in lowercase. Was this intentional, based on rfc8174?

I agree with you that some more work on these terms might be needed, I openet #12 to track this, as I'll merge this one to submit a new version to datatracker

@nicorusti nicorusti merged commit 9ff5f72 into main Feb 23, 2024
2 checks passed
@jiceatscion
Copy link
Contributor Author

As far as I remember, I went through every instance of must may should and their negatives. The should that I left in lowercase were likely intentional: layman use of the word for phrasing as opposed to normative, or sufficiently optional to not deserve an uppercase "should". But my opinion is just that, of course.

@nicorusti nicorusti deleted the Normative_refs_terms branch May 17, 2024 09:40
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

Successfully merging this pull request may close these issues.

2 participants