| [jakarta.ee-spec.committee] Concerns from today's meeting, input for tomorrow |
It was concerning to hear that there is a non-trivial Java trademark concern still in place looming over the Jakarta EE spec process. Hence my question about where the Java trademark issue is showing up. I'm still not really understanding how usage of java.* and javax.* in the legacy package namespaces has a significant trademark concern that has not already been addressed prior to Oracle even considering moving the enterprise Java specs over to Eclipse.
In reviewing the only trademark agreement that I or our legal team has seen, this has nothing to do with Java based trademarks. It is an agreement on use of the Jakarta EE Compatible branding.
We have commitments that have timeframes for withdrawal of support barring sufficient progress that are too close for comfort to not have an understanding of such a basic issue. We are certainly not willing to be involved in a spec process that continues to require any type of veto power in the hands of a single vendor.
In terms of approval of a specification process, we are only concerned with the spec process for Jakarta EE. If a general process can be bootstrapped as a by-product, that is fine, but we need to see the ability to move Java EE 8 into Jakarta EE 9 ASAP, including how one bootstraps the specification text and evolution of the legacy javax.* package APIs.