-
Notifications
You must be signed in to change notification settings - Fork 123
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
Update BCP 14 language to comply with RFC 8174 #706
base: master
Are you sure you want to change the base?
Conversation
I have no idea if this is an editor, council, or board concern. Thoughts? |
I like the idea, but I am a bit worried as this is essentially a non-backwards compatible change: All non-capitalized RFC 2119 keywords in previous XEP texts (if there are any) will lose their semantic. I wonder if we should introduce a appendix-conformance-v2 and just change the template to use this instead, so that previous XEPs are not affected by the change. |
I really doubt it matters; we can clean it up later if we notice any. As far as I'm aware all recent XEPs are using caps. |
I'm not sure why this would be a good thing - 2119 doesn't require the words to be in caps, why would we benefit from doing so? |
I'd say for the same reason RFC 8174 was written. |
Yep, being stupid, ta. I'd have thought Council would be a sensible venue for discussion. I'd have thought we'd need to bump the versions of all the affected XEPs, too, as this affects the reading of them, and probably grepping through to check that we don't have any non-upper-case uses that this would affect. |
Okay, editors. Since council accepted this, do you have opinions on how we merge this?
Opinions? |
Just merge it. It won't change anything in practice and it's not a change to the actual XEPs themselves, just a change to some metadata associated with all XEPs (more or less). |
If revision blocks can be added by script, that is best - our policy is that all XEP changes should have a new revision block, and this is a non-editorial change to many XEPs so would certainly be better with one. |
I disagree; this isn't a change to the normative XEP text, and is just clarifying the situation as it stands today, its completely editorial. Please just merge this and let's be done with it already. |
66ddb17
to
a5ec195
Compare
Rebased. Ping seeking a decision on my last comment. Thanks! |
Ping again. This was approved quite a while ago. |
a5ec195
to
e6004a9
Compare
Clarify that normative RFC 2119 language MUST be in all caps.