[jboss-as7-dev] Documentation - Naming conventions

[Misty Stanley-Jones]

----- Original Message -----
> From: "Dan Allen" <dan.j.allen at gmail.com>
> To: "Misty Stanley-Jones" <misty at redhat.com>
> Cc: "Pete Muir" <pmuir at redhat.com>, "JBoss AS7 Development" <jboss-as7-dev at lists.jboss.org>
> Sent: Wednesday, July 6, 2011 3:12:15 PM
> Subject: Re: [jboss-as7-dev] Documentation - Naming conventions
> On Mon, Jul 4, 2011 at 17:59, Misty Stanley-Jones < misty at redhat.com >
> wrote:
> 
> 
> 
> For the Enterprise docs, we do not shorten the name. We use
> "Enterprise Application Platform" in all cases. I have seen a
> directive to use "JBoss Enterprise Application Platform, provided by
> Red Hat" at the first instance, and shorten that to "JBoss Enterprise
> Application Platform." 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.
> 
> 
> 
> I'd argue that it'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's really odd and confusing when it comes up.
> 
> 
> Why not do it like all other acronyms are introduced.
> 
> 
> JBoss Application Server (AS)
> 
> 
> and
> 
> 
> JBoss Enterprise Application Platform (EAP)
> 

This was a decision made by people outside of docs. It has to do with branding and trademarking, I believe.

> 
> -Dan
> 
> --
> 
> Dan Allen Principal Software Engineer, Red Hat | Author of Seam in
> Action
> Registered Linux User #231597
> 
> 
> http://www.google.com/profiles/dan.j.allen#about
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction

-- 


Misty Stanley-Jones, RHCE 
Content Author, ECS Brisbane 
☺: misty (Freenode IRC) ✉: misty at redhat.com ☏: +61 7 3514 8105 ☏: 88105