On Mon, Jul 4, 2011 at 17:59, Misty Stanley-Jones <span dir="ltr">&lt;<a href="mailto:misty@redhat.com">misty@redhat.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

For the Enterprise docs, we do not shorten the name. We use &quot;Enterprise Application Platform&quot; in all cases. I have seen a directive to use &quot;JBoss Enterprise Application Platform, provided by Red Hat&quot; at the first instance, and shorten that to &quot;JBoss Enterprise Application Platform.&quot; However, that has not caught on. Specifically, we do not ever shorten it to EAP, even though it would probably make our lives easier if we could.<br>

</blockquote><div><br></div><div>I&#39;d argue that it&#39;s important to include the acronym, not just for convenience but for clarity. The reason is, we toss around the acronym like an old glove on the website and in interviews, blog entries, and other media channels. If we never put the two together in the documentation, then it&#39;s really odd and confusing when it comes up.</div>

<div><br></div><div>Why not do it like all other acronyms are introduced.</div><div><br></div><div>JBoss Application Server (AS)</div><div><br></div><div>and</div><div><br></div><div>JBoss Enterprise Application Platform (EAP)</div>

<div><br></div><div>-Dan</div><div><br></div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>

<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>