There is no legal issue with refering to "JAX-RS" at all, as it is not an Oracle trademark, and I do have explicit written permission by Oracle to continue using this acronym. If there are other restrictions, then these are completely controlled by some EF-internal committee (not us, not Oracle), so you should ask *those* people that control *those* documents you like to actually change. We here at JAX-RS can just guess, as we have no control on the files you like to change. The JAX-RS tutorial is not an official document of *us*. -Markus Von: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] Im Auftrag von Christian Kaltepoth
Gesendet: Sonntag, 15. September 2019 11:46
An: jaxrs developer discussions
Betreff: Re: [jaxrs-dev] Use of "Jakarta REST" on Jakarta EE tutorial My understanding of the guidelines is that it is fine to use JAX-RS *if* the document clarifies if you are referring to JCP JAX-RS or Jakarta JAX-RS. From https://jakarta.ee/legal/acronym_guidelines/ I understand the original acronyms can't be used in official Jakarta EE material. You can informally refer to Jakarta RESTful Web Services as "JAX-RS" but can't use that therm in official documents (like the tutorial) if it's not referring to the JCP JAX-RS. AFAIK, the main reason the tutorial is not already published in jakarta.ee is because it needed to remove all the Java EE and references. If that's the case, JAX-RS couldn't be used and so Jakarta REST (if approved as an acceptable name by the comitters) or Jakarta RESTful Web Services would be the options. I'm adding Bill Shannon to the conversation to let him clarify it. Guillermo González de Agüero So let's stay with JAX-RS. ;-) -Markus I would prefer to have a short name for the spec hat is used in a consistent way. Mixing Jakarta REST and JAX-RS all the time is very confusing. As mentioned before, I would prefer to keep the JAX-RS short name. But that's just my opinion. As a JAX-RS Committer I think you are free to decide that. But you should talk with those that defined overall Jakarta tutorial, maybe they want special wording. -Markus I'm working on migrating the Java EE tutorial to Jakarta EE terms. In the absence of a new acronym or short name, that means replacing 140 JAX-RS mentions with "Jakarta RESTful Web Services". I wonder, would it be acceptable to informally use "Jakarta REST" on those places where JAX-RS was used? This would be consistent with uses of "Faces pages" for JSF or "enterprise beans" for EJB. As opposed to the spec, the tutorial is a non normative document. The only reason I'm asking this is to reduce verbosity. Guillermo González de Agüero _______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
-- _______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
-- |
