Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Guidelines for the use of existing Oracle/JCP Acronyms

I think everybody should dedide for himself and we as a group should simply wait what the community does. Now that there is a general guideline there is no need for us to continue this discussion, as it would not lead to any effective change.

-Markus

 

Von: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] Im Auftrag von Reza Rahman
Gesendet: Mittwoch, 3. Juli 2019 00:35
An: Jakarta EE community discussions
Betreff: Re: [jakarta.ee-community] Guidelines for the use of existing Oracle/JCP Acronyms

 

Personally I believe it is time to step away from these acronyms anyway. In my experience, it has been an endless source of adoption issues, especially in the eyes of newcomers. Jakarta Messaging is a lot more self-explanatory than continuously needing to explain what "JMS" stands for.

 

Reza Rahman
Principal Program Manager
Java on Azure

Please note that views here are my own as an individual community member and do not represent the views of my employer.

 

On 7/1/2019 11:52 AM, will.lyons@xxxxxxxxxx wrote:

Emmanuel -

The guidance says that for names of Jakarta EE projects, specifications, test suites, and other related materials, the full project name/title and any scope statement should not incorporate an identified acronym.  So the name "Jakarta Message Service Specification" is OK, and I expect that is the name that will be used for this spec.

We're assuming that within documents, and in repo names, URLs, package names, the default preference will be to re-use an existing acronym.  For example, we're assuming the default preference would be to use the acronym "JMS" for Jakarta Message Service within the body of spec docs, and in repo names, URLs and package names.   The details are spelled out in the guideline document, but the guidelines are intended to enable that usage if it is clear where the technology is originating from (Oracle/JCP or Eclipse/Jakarta EE).  

Will

On 7/1/19 11:39 AM, Emmanuel Bernard wrote:

Is there any recommended acronym generator algorithm ? e.g. Jakarta Messaging Service Specification -> XxXX

 

On Sun, Jun 30, 2019 at 7:18 PM <will.lyons@xxxxxxxxxx> wrote:

Hello -

The Jakarta EE Working Group Steering Committee has unanimously approved
the following "Guidelines for the use of existing Oracle/JCP Acronyms"
posted at:

https://jakarta.ee/legal/acronym_guidelines/

As stated in the document, the goal of these guidelines is to avoid
confusion and ensure that the developer community can easily identify
whether a Jakarta EE project, specification, test suite, or other
related item originates from Oracle/JCP or from the Eclipse/Jakarta EE
process.  The guidelines apply to use of Oracle/JCP acronyms in names of
Jakarta EE projects, specifications, test suites, and other related
materials, such as project repositories, URLs, and package names.  We
will use these guidelines in creation of Jakarta EE 8 artifacts and in
subsequent versions of Jakarta EE.

Thanks

Will

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community




_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community




_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community

 

-- 
Reza Rahman
Principal Program Manager
Java on Azure
 
Please note that views here are my own as an individual community member and do not represent the views of my employer.

Back to the top