The jetty project is looking at the naming consequences of the transition with regards to implementation names (eg module names and classnames). Let's consider the websocket API. It will soon be the case that a container may wish to offer it's webapps the choice of using the javax.* version of the API or the jakarta.* version.
Would be be allowable (with regards to trademarks) to have the various modules, classes and options for those to use javax and jakarta in their names. For example the user could choose between enabling modules websocket-javax and websocket-jakarta, which internally might enable classes like org.eclipse.jetty.websocket.javax.* and org.eclipse.jetty.websocket.jakarta.*, which are configured with parameters etc. that also might include javax and jakarta?
Or is that going to run foul of one or more trademarks? Are there fair use provisions that allows us the use these trademarks in the names of things that work with the APIs of those trademarks?
If so, are there similar issues with the use of ee ? Ie could the modules be called websocket-ee8 and websocket-ee9, which internally refer to classes like org.eclipse.jetty.websocket.ee8.* and org.eclipse.jetty.websocket.ee9.* etc. ? Is this usage still OK if it is within an non certified container that does not implement the full ee stack? Is ee subject to trademarks?
Is this something the Eclipse Foundation can get legal advice on? Or is the answer known already?
regards
--
