| Re: [jakarta.ee-community] Specification acronyms |
Markus,
We are working on that finalizing that list...
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
jakarta.ee-community-bounces@xxxxxxxxxxx wrote on 05/30/2019 10:40:40 AM:
> From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
> To: "'Jakarta EE community discussions'" <jakarta.ee-community@xxxxxxxxxxx>
> Date: 05/30/2019 10:41 AM
> Subject: [EXTERNAL] Re: [jakarta.ee-community] Specification acronyms
> Sent by: jakarta.ee-community-bounces@xxxxxxxxxxx
>
> It would be great if Oracle or the EF could post a list of those
> trademarks. So everybody would know them.
>
> From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-
> community-bounces@xxxxxxxxxxx] On Behalf Of Kevin Sutter
> Sent: Donnerstag, 30. Mai 2019 16:02
> To: Jakarta EE community discussions
> Subject: Re: [jakarta.ee-community] Specification acronyms
>
> That is not a "full stop", Richard. The acronyms will not be used
> in the Specification Project names and descriptions. But, beyond
> that, they can continue to be used in documentation, package names,
> class names, etc. Both by Eclipse and vendors.
>
> (There may be a few exceptions to this rule, like JDBC. But, almost
> of the other acronyms are not TM'd.)
>
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Java EE architect
> e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
> phone: tl-553-3620 (office), 507-253-3620 (office)
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
>
> jakarta.ee-community-bounces@xxxxxxxxxxx wrote on 05/30/2019 08:14:50 AM:
>
> > From: Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx>
> > To: Jakarta EE community discussions <jakarta.ee-community@xxxxxxxxxxx>
> > Date: 05/30/2019 08:20 AM
> > Subject: [EXTERNAL] Re: [jakarta.ee-community] Specification acronyms
> > Sent by: jakarta.ee-community-bounces@xxxxxxxxxxx
> >
> > Eclipse and the vendors cannot use the acronyms we are all familiar
> > with. Full stop. That is a condition of the transfer of IP to Eclipse.
> >
> > My suggestion, as a community, is when writing about a topic the
> > first mention is always Jakarta XXX. For example, "Jakarta
> > Messaging" and subsequent mentions use just "Messaging" its longer
> > than JMS by a few characters but actually is simpler to verbalize.
> > Another example is EJB, instead, you start any written statement
> > with "Jakarta Enterprise Beans" and subsequently use Enterprise
> > Beans. After some time the community will invent its own short
> > forms again but following this convention will get us started, avoid
> > confusion, and IP issues.
> >
> > On Sun, May 26, 2019 at 5:01 AM Gergely Molnár <gergelymolnarpro@xxxxxxxxx
> > > wrote:
> > Sorry for send again, Jakarta is already Enterprise so it can be JB
> > as Jakarta Bean.
>
> > Best regards/Üdvözlettel:
> > Gergely Molnár
> >
> > Gergely Molnár <gergelymolnarpro@xxxxxxxxx> ezt írta (időpont: 2019.
> > máj. 26., V 11:58):
> > PS.: At the release note, it can be the full name, e.g.: Java EE 8
> > feature list, they wrote Enterprise JavaBean and not EJB.
>
> > Best regards/Üdvözlettel:
> > Gergely Molnár
> >
> > Gergely Molnár <gergelymolnarpro@xxxxxxxxx> ezt írta (időpont: 2019.
> > máj. 26., V 11:11):
> > Or just explain at every documentation the J from the abbreviation
> > is Jakarta, because domain of all is jakarta.* If you use Enterprise Java
> > Bean then you use javax.* or if you would like to use Enterprise Jakarta
> > Bean then you should use jakarta.* EJB is not a trade mark, it is?
> >
> > Best regards / Üdvözlettel,
> > Gergely Molnár
> >
> > Guillermo González de Agüero <z06.guillermo@xxxxxxxxx> ezt írta
> > (időpont: 2019. máj. 26., V, 11:04):
> > If we start renaming acronyms on packages we'll also need to rename
> > some classes: https://docs.oracle.com/javaee/7/api/javax/jms/
> > JMSConnectionFactory.html
> >
> > Also, EJB won't probably recieve many updates from now on. There's
> > little to gain from changes on those packages.
> >
> > I'd rather go the easy path, simply replacing javax.* with jakarta.*
> >
> > El sáb., 25 may. 2019 22:49, Werner Keil <werner.keil@xxxxxxxxx> escribió:
> > In some cases, every spec (except potentially some that are not
> > touched for the time being) must change the "javax" part to
> > "jakarta" and in a few the "filling" packages like "ws" or
> > "enterprise" are also subject to change.
> >
> > Where the longer name was already in the package now like "servlet"
> > or "persistence", there is no real need to change those, in other
> > cases like "javax.jms" it should change to something like
> > "jakarta.messaging", too.
> >
> > Not sure about EJB again, that is a bit of a special case,as the
> > mail hinted, it's possible the "ejb" package name stays with the
> > slight weirdness of a project whose acronym would rather be "JEB"
> > than "EJB", for others like "JMS" I know from the project team that
> > a change to "jakarta.message" or "jakarta.messaging" is preferred
> > over "jakarta.jms". This may be done on a case by case basis as well.
> >
> > Werner
> >
> > On Sat, May 25, 2019 at 9:47 PM Guillermo González de Agüero <
> > z06.guillermo@xxxxxxxxx> wrote:
> > Don't think so: https://www.eclipse.org/lists/jakartaee-platform-
> > dev/msg00331.html
> >
> > On Sat, May 25, 2019 at 9:36 PM Gergely Molnár <gergelymolnarpro@xxxxxxxxx
> > > wrote:
> > The naming problem also affect the package name, doesn't it? If it
> > affect, what happening with compability?
> >
> > Best regards / Üdvözlettel,
> > Gergely Molnár
> >
> > Werner Keil <werner.keil@xxxxxxxxx> ezt írta (időpont: 2019. máj.
> > 25., Szo, 21:10):
> > Please don't forget, EE4J is nothing but the administrative umbrella
> > at Eclipse Foundation: https://projects.eclipse.org/projects/ee4j
> > Projects like Eclipse Mosquitto, SmartHome, Hono or Vorto also don't
> > constantly get a tease about being called iMosquitto, iSmartHome,
> > etc. or IoTMosquitto,... so better accept it and don't bother
> > talking about it here all the time.
> >
> > Regards,
> > Werner
> >
>
> >
> > On Sat, May 25, 2019 at 8:58 PM Gergely Molnár <gergelymolnarpro@xxxxxxxxx
> > > wrote:
> > Hi all,
> >
> > Just a hint: EEJB Eclipse Enterprise Jakarta Bean. It as good as EE4J.
>
> > Best regards/Üdvözlettel:
> > Gergely Molnár
> >
>
> > Werner Keil <werner.keil@xxxxxxxxx> ezt írta (időpont: 2019. máj.
> > 25., Szo 20:47):
> > Christian/all,
> >
> > I have a little bit of insight from the spec committee and although
> > I just have one Individual voice and vote on behalf of the
> > community, I was also the longest serving Individual both in the
> > Java EE EG (since Java EE 6) and JCP EC, part of its duties are now
> > with the spec committee.
> >
> > We still see a lot of people asking for "J2EE" experience after all
> > those years, it won't die completely even as we approach 2020.
> > We should try to use the project and spec names where possible. Some
> > like "Jakarta Messaging" still being nicknamed "JMS" probably won't
> > be a big tragedy because if you abbreviate it, you still end up with
> > "JMS". "Jakarta Persistence" also would not be damaged if some still
> > called the API part "JPA", while especially in this case, the Java
> > package already contains the name.
> > Others like the current "EJB" might be harder because the proposed
> > name would twist it to "JEB" (not that anybody wants to advertise
> > politicians here?;-)
> > Some specs like CDI always had a terribly long name. There was a
> > suggestion to cut it down to "Jakarta Contexts" but not only would
> > abbreviating that make little sense, it would also diminish the
> > value and scope of CDI by dropping the whole "Dependency Injection"
> > part, while @Inject is what many associate with it although it's
> > only part of another smaller spec embedded underneath.
> >
> > JAX-RS was always a wrong and ill-fated acronym, the "X" if any
> > could be related to "javax", in reality it was mostly a quick and
> > dirty transfer of the "JAX-WS" (for XML and SOAP) into RESTful Web
> > Services, therefore IMO here it is a house cleaning and nobody
> > should use JAX-RS any more after the Jakarta EE name changes.
> >
> > Werner
> >
> > On Sat, May 25, 2019 at 5:13 PM Christian Kaltepoth <christian@xxxxxxxxxxxx
> > > wrote:
> > Hi all,
> >
> > I'm not sure where the best place to ask this question is, so I'm
> > cross posting this to the community, PMC and WG lists.
> >
> > I would like to kindly ask for some clarification about how to deal
> > with the popular Java EE specification acronyms like JPA, JAX-RS,
> > EJB, etc in the future. A few people mentioned that Jakarta EE must
> > not use these acronyms anymore, but AFAIK there wasn't any official
> > statement about that.
> > Mike mentioned in his blog post that some acronyms like EJB, JPA or
> > JAX-RS need to change
> > Ivar wrote that it would be up to the spec committee to define
> > guidelines or restrictions regarding the use of acronyms.
> > Bill noted that details about this issue are wrapped up in the
> > negotiations between Oracle and the EF
> > Could anyone please provide some insights? Especially regarding
> > these questions:
> > Can Jakarta EE continue to use the old acronyms like EJB, JAX-RS and
> > so on? If no, which ones are forbidden? I guess the ones containing
> > a "J" which stands for "Java"?
> > If we are not allowed to keep the old acronyms, should each project
> > find a new acronym or should we prevent any kind of acronym like suggested
> > by Ivar? Has there been any discussions about this so far?
> > Thanks a lot!
> >
> > Christian
> >
> > --
> > Christian Kaltepoth
> > Blog: http://blog.kaltepoth.de/
> > Twitter: http://twitter.com/chkal
> > GitHub: https://github.com/chkal
> >
> > _______________________________________________
> > 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
> > _______________________________________________
> > 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
> > _______________________________________________
> > 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
> >
> > --
> > Richard Monson-Haefel
> > https://twitter.com/rmonson
> > https://www.tomitribe.com/_______________________________________________
> > jakarta.ee-community mailing list
> > jakarta.ee-community@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or
> > unsubscribe from this list, visit
> > https://urldefense.proofpoint.com/v2/url?
> >
> u=https-3A__www.eclipse.org_mailman_listinfo_jakarta.ee-2Dcommunity&d=DwICAg&c=jf_iaSHvJObTbx-
> >
> siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=UixNmBoXgLAj96anJWbtKpyBuM0E9QITeqvl_hvnWng&s=Cw3iO4K0dWnVLa7JUS7z9iWu46GpmNiX-
> > gK-9f2ifmo&e=_______________________________________________
> jakarta.ee-community mailing list
> jakarta.ee-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://urldefense.proofpoint.com/v2/url?
> u=https-3A__www.eclipse.org_mailman_listinfo_jakarta.ee-2Dcommunity&d=DwICAg&c=jf_iaSHvJObTbx-
> siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=caTodp32_U2IxOKHskvRrkTABjPHuIWycKFO8hQRkB4&s=37-2WorWLS8j9UXLSExxN-
> HNsNlkCR-cn8SVDqVtIZA&e=
_______________________________________________
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