Again, see this link:<div><a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a></div><div><br></div><div>For simplicity and clarity, the only levels of criticality that we use are:</div><div>
<br></div><div>Required</div><div>Recommended </div><div>Optional</div><div><br></div><div>(We sometimes may refer to "Critical", but that refers to thinks like security exploits, that generally don't appear in the Guidelines.)</div>
<div><br></div><div>Per this standard:</div><div><br></div><div>Required = Must = Shall (and "Required not" = "Must not" = "Shall Not")</div><div>Recommended = Should (and "Recommended not" = "Should not")</div>
<div>Optional = May</div><div><br></div><div>Any further stratification of criticality would only make the Guidelines more confusing, and therefore more difficult to which to conform.</div><div><br></div><div>Chip</div><div>
<br><div class="gmail_quote">On Thu, Nov 10, 2011 at 9:44 AM, Mario Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net">mario@peshev.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
In my understanding there is a level of imperativeness between<br>
different statements, like:<br>
<br>
<br>
must<br>
have to<br>
be required to<br>
need to<br>
should<br>
could<br>
recommended<br>
might<br>
may<br>
nice to<br>
<br>
In a desc order, something like this. And the first two on the top are<br>
a bit harsh in my opinion.<br>
<br>
Of course, it's just a single opinion shared. I do browse a lot and<br>
have to write tons of documentations and support tickets on a daily<br>
basis and being very careful using different statements.<br>
<div class="im HOEnZb"><br>
Mario Peshev<br>
Training and Consulting Services @ DevriX<br>
<a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br>
<a href="http://devrix.com" target="_blank">http://devrix.com</a><br>
<a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br>
<br>
<br>
<br>
<br>
</div><div class="HOEnZb"><div class="h5">On Thu, Nov 10, 2011 at 5:34 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> But that's the point: it *is* an imperative. That's the difference between<br>
> being REQUIRED to do/not to do something, versus something being RECOMMENDED<br>
> to do/not to do, or OPTIONAL.<br>
> For example: use of fopen() type functions: the requirement is imperative.<br>
> They MUST NOT be used.<br>
> Chip<br>
><br>
> On Thu, Nov 10, 2011 at 9:31 AM, Mario Peshev <<a href="mailto:mario@peshev.net">mario@peshev.net</a>> wrote:<br>
>><br>
>> I would not like 'must not' as too imperative - 'should not' or<br>
>> 'required to' + some other verb indicating negative sound better in my<br>
>> language at least.<br>
>><br>
>> Best regards,<br>
>><br>
>> Mario Peshev<br>
>> Training and Consulting Services @ DevriX<br>
>> <a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br>
>> <a href="http://devrix.com" target="_blank">http://devrix.com</a><br>
>> <a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br>
>><br>
>><br>
>><br>
>><br>
>> On Thu, Nov 10, 2011 at 5:29 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
>> wrote:<br>
>> > We use the terminology from RFC 2119, in order to ensure consistency;<br>
>> > so:<br>
>> > "required", "recommended", or "optional".<br>
>> > I suppose we could replace "required not" with "must not"?<br>
>> > Chip<br>
>> ><br>
>> > On Thu, Nov 10, 2011 at 9:26 AM, Angelo Bertolli<br>
>> > <<a href="mailto:angelo.bertolli@gmail.com">angelo.bertolli@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Maybe the word FORBIDDEN could be used instead if it makes it clearer.<br>
>> >><br>
>> >> On 11/10/2011 10:24 AM, Mario Peshev wrote:<br>
>> >> > Please do apologize my English, but as a foreign language 'REQUIRED<br>
>> >> > NOT to' written this way looks exactly like "NOT REQUIRED to'" (with<br>
>> >> > this exact casing).<br>
>> >> ><br>
>> >> > Could be my bad, but these are guidelines and the cleaner, the<br>
>> >> > better.<br>
>> >> ><br>
>> >> > Mario Peshev<br>
>> >> > Training and Consulting Services @ DevriX<br>
>> >> > <a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br>
>> >> > <a href="http://devrix.com" target="_blank">http://devrix.com</a><br>
>> >> > <a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>> >> > On Thu, Nov 10, 2011 at 5:17 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>><br>
>> >> > wrote:<br>
>> >> >> Good morning, Theme developers and reviewers!<br>
>> >> >> Now is the time to begin discussing and finalizing the changes to<br>
>> >> >> the<br>
>> >> >> Theme<br>
>> >> >> Review Guidelines pursuant to the release of WordPress 3.3. Please<br>
>> >> >> read<br>
>> >> >> and<br>
>> >> >> discuss, here:<br>
>> >> >><br>
>> >> >><br>
>> >> >> <a href="http://make.wordpress.org/themes/2011/11/10/wordpress-3-3-proposed-guidelines-revisions/" target="_blank">http://make.wordpress.org/themes/2011/11/10/wordpress-3-3-proposed-guidelines-revisions/</a><br>
>> >> >> Note that, until WordPress 3.3 is released, these proposed revisions<br>
>> >> >> are a<br>
>> >> >> work-in-progress. Consider the above link as a "Request For<br>
>> >> >> Comment";<br>
>> >> >> if you<br>
>> >> >> have anything to add, or disagree with anything proposed, please<br>
>> >> >> comment<br>
>> >> >> accordingly. We post these, because we value your input and feedback<br>
>> >> >> as<br>
>> >> >> Theme developers.<br>
>> >> >> Thanks!<br>
>> >> >> Chip<br>
>> >> >> _______________________________________________<br>
>> >> >> theme-reviewers mailing list<br>
>> >> >> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
>> >> >> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
>> >> >><br>
>> >> >><br>
>> >> > _______________________________________________<br>
>> >> > theme-reviewers mailing list<br>
>> >> > <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
>> >> > <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
>> >> _______________________________________________<br>
>> >> theme-reviewers mailing list<br>
>> >> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
>> >> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > theme-reviewers mailing list<br>
>> > <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
>> > <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
>> ><br>
>> ><br>
>> _______________________________________________<br>
>> theme-reviewers mailing list<br>
>> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
>> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>