Re: [jakartaee-platform-dev] Resolution on optional features

[Nathan Rauh <nathan.rauh@xxxxxxxxxx>]

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]