I don't understand that new versions of the JAX-RS specification shall be done, but at the same time it would violate Oracle's naming rights if we call that new specification still "JAX-RS"…?! That means, we have to rename the specification's name? BTW, a quick search in the WIPO Global Trademark Database did not bear any registration of the term "JAX-RS", neither by Oracle nor by others.
-Markus
From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Donnerstag, 23. November 2017 18:25
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] EE4J Project Proposals
On 2017-11-23 11:58 AM, Markus KARG wrote:
What is "the corresponding spec project"? For JAX-RS for example, Jersey is "just" the RI, and it is just the *current* RI.
Exactly right.
In the JCP we could decide to have future release of JAX-RS with different RIs.
It is the intent of Oracle, IBM, Red Hat, and other participants that future versions of the JAX-RS specs will be done using a new spec process hosted at the Eclipse Foundation.
So does that mean that from now on the JCP must stick with Eclipse-provided *current* RIs forever?
Um. no. That would be dumb. And under the new spec process provisions will be made to allow new RIs to appear, as well as ensuring the creation of independent implementations.
Actually I do not understand why the API project is not simply named "JAX-RS API", the TCK project "JAX-RS TCK" and the RI simply "Jersey"?
Because those project names would violate Oracle's trademark rights in the "JAX-RS" name.
