Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Use of CDI acronym

I'm not aware of any issues with regards to Red Hat or IBM trademarks, acronym or otherwise, that would affect Bean Validation, CDI, or Batch.  Those projects are being provisioned now with those names and acronyms.

On the Oracle acronyms, that situation has greatly improved and there are usages of say "EJB" and "JMS" that are ok.

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


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com


On Jul 12, 2019, at 11:47 AM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi,

I was wondering about that too. For the moment I kept CDI in the texts I'm changing according to the guidelines, but would be happy to change it along as well.

Kind regards,
Arjan Tijms


On Fri, Jul 12, 2019 at 8:30 PM Guillermo González de Agüero <z06.guillermo@xxxxxxxxx> wrote:
Hi,

We know we can't use Oracle acronyms but I wonder, is that the same for Red Hat and IBM led specs? Specifically, being able to use CDI instead of "Jakarta Contexts and Dependency Injection" everywhere would be very helpful.


Regards,

Guillermo González de Agüero
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc


Back to the top