| All,
As I understand it, we have opponents to using “Jakarta REST” and opponents to using “JAX-RS” (myself included). Thus, the options are to use the full name and/or contextual references such as “this API”. I suggest we do that and move forward.
— Santiago
That's not quite right. As described in the guidelines you
reference, you can include a disclaimer so that you can use "JAX-RS"
to refer to "Jakarta RESTful Web Services" in this document.
Still, the recommendation from the PMC was to choose simple names
for the specifications and to use those simple names instead of
acronyms going forward, possibly dropping the "Jakarta" if the
context is clear. This avoids any of the confusion related to the
acronyms. While "Jakarta REST" was a suggested simple name for this
specification, the team chose to use "Jakarta RESTful Web Services".
This spec may be the only one that is clinging to the old acronym.
You can decide whether the tutorial reads better with the disclaimer
and the old acronym, or with the new spec name.
Note that the tutorial already published at https://eclipse-ee4j.github.io/jakartaee-tutorial/,
and is automatically updated as the tutorial source is updated.
It's not linked into the jakarta.ee web site, but it probably should
be.
Guillermo González de Agüero wrote on
9/15/19 2:35 AM:
Hi,
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.
Regards,
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@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jaxrs-dev
|
