I've commented on the document that there does not appear to be anything in the proposal that is not supported by the EFSP.
This seems like a good opportunity to point the entire specification committee to some work that I've been doing to prepare a draft of the EFSP 1.3.
One of the themes is to remove elements of the process that prescribe the nature of specifications. The foundational process is not, IMHO, the place to make specific requirements regarding how optional elements must be defined and implemented, or even have any notion of optional elements. Individual specifications themselves--or the specification committee--can opt make this requirement, but should not inherit it as an absolute requirement by default (i.e., if the Jakarta EE specification committee feels strongly that some aspect of the nature of how specifications themselves are written and implemented, they can include it in the JESP).
I opened
issue 42 to track this specific change (
issue 22 requests clarification of "optional", my hope is to remove the concept instead).
I've created a
board to manage all of the issues that I'm tracking for this iteration.
The diff of my work-in-progress is
here. Bear in mind that I am actively working on this, so the work-in-progress will change.
There's a couple of big things on the list that may be of interest to the Jakarta EE specification committee:
Please do add your comments on these and any other issue. Please feel free to open additional issues.
I need one volunteer to represent the interests of the Jakarta EE specification committee on a committee to revise the EFSP. At this time, I'm anticipating that we'll do most of the work via the repository and have possibly one or two short meetings to discuss issues. I'll leave it to the specification committee to decide how to select the representative.
Thanks,
Wayne