| Re: [ee4j-pmc] Specification project scope statements |
> From: Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
> For the specification project:
>
> Jakarta Batch provides the specification document along with the API
> and TCK for describing a means for scheduling, orchestrating, and
> managing batch processes in Jakarta EE applications.
OK, thanks for the feedback. It looks like I misunderstood and we're looking for simpler scope statements.
So I would now write that more like:
"Jakarta Batch provides the specification document along with the API and TCK for describing a means for executing and managing batch processes in Jakarta EE applications."
(I'm purposely avoiding using the word "scheduling" since JSR-352 specifically excluded that from our domain).
In trying to work this out, I'd had the thought to move some of the wording you thought fit better into "Description" into "Scope", to make it say more than basically "continue JSR 352".
But if we're going for a simpler scope that's fine. I haven't participated in enough of the conversations to have a strong opinion here.
And maybe even something like the scope statement in https://projects.eclipse.org/proposals/eclipse-project-jms is OK.
All that says is: "Eclipse Proeject for JMS provides the API and TCK for Java™ Message Service (JMS) API, starting from the specification defined by JSR-343."