We use <a href="http://www.google.com/url?sa=t&amp;rct=j&amp;q=rfc%20required%20recommended%20optional&amp;source=web&amp;cd=1&amp;ved=0CBoQFjAA&amp;url=http%3A%2F%2Fwww.ietf.org%2Frfc%2Frfc2119.txt&amp;ei=he27TuXGFeXo2gXgh_2cBw&amp;usg=AFQjCNFOxXVqXaO3EKLRE2wUoMIxuM4HVg">the terminology from RFC 2119</a>, in order to ensure consistency; so: &quot;required&quot;, &quot;recommended&quot;, or &quot;optional&quot;.<div>
<br></div><div>I suppose we could replace &quot;required not&quot; with &quot;must not&quot;?</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">&lt;<a href="mailto:angelo.bertolli@gmail.com">angelo.bertolli@gmail.com</a>&gt;</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>
&gt; Please do apologize my English, but as a foreign language &#39;REQUIRED<br>
&gt; NOT to&#39; written this way looks exactly like &quot;NOT REQUIRED to&#39;&quot; (with<br>
&gt; this exact casing).<br>
&gt;<br>
&gt; Could be my bad, but these are guidelines and the cleaner, the better.<br>
&gt;<br>
&gt; Mario Peshev<br>
&gt; Training and Consulting Services @ DevriX<br>
&gt; <a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br>
&gt; <a href="http://devrix.com" target="_blank">http://devrix.com</a><br>
&gt; <a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Thu, Nov 10, 2011 at 5:17 PM, Chip Bennett &lt;<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>&gt; wrote:<br>
&gt;&gt; Good morning, Theme developers and reviewers!<br>
&gt;&gt; Now is the time to begin discussing and finalizing the changes to the Theme<br>
&gt;&gt; Review Guidelines pursuant to the release of WordPress 3.3. Please read and<br>
&gt;&gt; discuss, here:<br>
&gt;&gt; <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>

&gt;&gt; Note that, until WordPress 3.3 is released, these proposed revisions are a<br>
&gt;&gt; work-in-progress. Consider the above link as a &quot;Request For Comment&quot;; if you<br>
&gt;&gt; have anything to add, or disagree with anything proposed, please comment<br>
&gt;&gt; accordingly. We post these, because we value your input and feedback as<br>
&gt;&gt; Theme developers.<br>
&gt;&gt; Thanks!<br>
&gt;&gt; Chip<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; theme-reviewers mailing list<br>
&gt;&gt; <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
&gt;&gt; <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt; _______________________________________________<br>
&gt; theme-reviewers mailing list<br>
&gt; <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
&gt; <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>