Also, if the topic hasn’t come up already (I’m not on the lists where it would have been discussed), some consideration should be given to whether the all optional features ought to be disallowed, or if it
only the introduction of new optional features should be disallowed (grandfathering in option features that were already there). It seems like we should be aiming for the latter approach. In that case, proposed wording could be something like:
An individual specification can have optional features, however when a component specification is included in the Platform and Web Profile, and Core Profile all features are required
except for features that were already in the Platform and optional prior to Jakarta EE 10. This requirement is noted in the Platform specification.
From:
jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Date: Wednesday, March 8, 2023 at 8:30 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>, JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Cc: Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>, jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Resolution on optional features
Scott, Just removing “otherwise it is not required” would make it clear that optional features are not allowed in the platform and profiles. Either of the following
would accomplish that: An individual specification can have optional features,
|
This Message Is From an External Sender
|
|
This message came from outside your organization.
|
|
|
Scott,
Just removing “otherwise it is not required” would make it clear that optional features are
not allowed in the platform and profiles.
Either of the following would accomplish that:
An individual specification can have optional features, however when a component specification is included in the Platform and Web Profile, and Core Profile all features are required.
This requirement is noted in the Platform specification.
An individual specification can have optional features, however when a component specification is included in the Platform and Web Profile, and Core Profile all optional features
must be explicitly declared as required. This requirement is noted in the Platform specification.
From:
jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Scott Stark <starksm64@xxxxxxxxx>
Date: Wednesday, March 8, 2023 at 8:20 AM
To: JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Cc: Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>, jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Resolution on optional features
What would you propose as the clearer alternative wording? On Mar 8, 2023 at 8: 12: 18 AM, Nathan Rauh <nathan. rauh@ us. ibm. com> wrote: Scott, Your description
of the resolution was that it disallows optional features from the platform and
|
This Message Is From an External Sender
|
|
This message came from outside your organization.
|
|
|
What would you propose as the clearer alternative wording?
Scott,
Your description of the resolution was that it
disallows optional features from the platform and profiles. However, from reading the statement itself, one would logically conclude the exact opposite, because the language “otherwise
it is not required” tells us of the existence of an alternative to explicitly declaring the feature required. The language of “must” on its own would be a requirement. The language of “must” coupled with “otherwise”
means a choice between two alternatives, each with their own corresponding requirement (required feature vs optional feature).
Please look into correcting the language of this resolution. There have already been multiple times during development of Jakarta EE 11 specs where
I have witnessed other specification participants wanting to make various component spec features optional, and each time I’ve had to step in and point out that the Jakarta EE platform does not allow new optional features to be introduced. If the text of
this resolution is left as is, it will no longer be possible to argue against those attempts anymore and we will start to see more optional features being added because those same features will come back up for discussion again and we will no longer have grounds
to argue against optionality.
Last month (February 8th, 2023) the Specification Committee passed the following resolution to disallow optional features in the platform and profiles: An individual specification can have optional features, however
when a component specification
|
This Message Is From an External Sender
|
|
This message came from outside your organization.
|
|
|
Last month (February 8th, 2023)
the Specification Committee passed the following resolution to disallow optional features in the platform and profiles:
An individual specification can have optional features, however when a component specification is included in the
Platform and Web Profile, and Core Profile an optional feature must be explicitly declared as required, otherwise it is not required. This requirement is noted in the Platform specification.
Kenji Kazumura - Fujitsu [+1]
Tom Watson - IBM - Emily Jiang [+1]
Ed Bratt - Oracle - Dmitry Kornilov [+1]
Andrew Pielage - Payara - Petr Aubrecht [+1]
David Blevins - Tomitribe - Jean-Louis Monteiro, Cesar Hernandez [absent]
Ivar Grimstad - PMC Representative [+1]
Marcelo Ancelmo - Participant Member -
Abraham Marin-Perez [0]
Werner Keil - Committer Member [absent]
Scott Stark - Red Hat - Scott Marlow Enterprise Member [+1]
Zhai Luchao - Shandong Cvicse Middleware Co. - Enterprise Member [+1]
