We use <a href="http://www.google.com/url?sa=t&rct=j&q=rfc%20required%20recommended%20optional&source=web&cd=1&ved=0CBoQFjAA&url=http%3A%2F%2Fwww.ietf.org%2Frfc%2Frfc2119.txt&ei=he27TuXGFeXo2gXgh_2cBw&usg=AFQjCNFOxXVqXaO3EKLRE2wUoMIxuM4HVg">the terminology from RFC 2119</a>, in order to ensure consistency; so: "required", "recommended", or "optional".<div>
<br></div><div>I suppose we could replace "required not" with "must not"?</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, Nov 10, 2011 at 9:26 AM, Angelo Bertolli <span dir="ltr"><<a href="mailto:angelo.bertolli@gmail.com">angelo.bertolli@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Maybe the word FORBIDDEN could be used instead if it makes it clearer.<br>
<div class="HOEnZb"><div class="h5"><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 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>> wrote:<br>
>> Good morning, Theme developers and reviewers!<br>
>> Now is the time to begin discussing and finalizing the changes to the Theme<br>
>> Review Guidelines pursuant to the release of WordPress 3.3. Please read and<br>
>> discuss, here:<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 are a<br>
>> work-in-progress. Consider the above link as a "Request For Comment"; if you<br>
>> have anything to add, or disagree with anything proposed, please comment<br>
>> accordingly. We post these, because we value your input and feedback 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>
</div></div></blockquote></div><br></div>