Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] [jakartaee-spec-project-leads] [jakartaee-platform-dev] Resolution on optional features

Where I get confused is that the definition of optional is "not required.”

     adjective
            1. left to one's choice; not required or mandatory:
            2. leaving something to choice.

I’m not sure I’m understanding the distinction we intend.


-David

On Mar 10, 2023, at 8:15 AM, Scott Stark <starksm64@xxxxxxxxx> wrote:

Right, we are trying to clearly state there are no optional features in the platform or profiles.

The option feature section in the Core Profile is to eliminate any optional features from component specifications it includes. It simply calls out that they are not required.

On Mar 8, 2023 at 2:35:01 PM, David Blevins <david.blevins@xxxxxxxxx> wrote:
My understanding based solely on the new text is as you state — essentially optional features are ok.

We had very clear text that said no new optional features in any Platform or Profile from EE 10 and onward, but still added an optional features section to the new Core Profile.  I personally do not think there is any text that can be created that would in practice actually stop implementation choices like these from being added to specifications.

IMO options are fine as long as we make implementations clearly state in the Public TCK Results Summary page of their CCR what options they’ve implemented.

-- 
David Blevins


On Mar 8, 2023, at 6:12 AM, Nathan Rauh <nathan.rauh@xxxxxxxxxx> wrote:

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.
 
 

From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> on behalf of Scott Stark <starksm64@xxxxxxxxx>
Date: Tuesday, March 7, 2023 at 5:19 PM
To: Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>, JakartaEE Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>, jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [jakartaee-platform-dev] Resolution on optional features

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
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
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.
 
The ballot tally was:
 

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]



_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads

_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec


Back to the top