Mike,
in fact you told me in person at ECE 2017 that you do NOT want specifications to be developed first, and then added ontop of the products, but that you want the specifications to describe the EXISTING features of the existing products. I can't help it if you didn't want to say or imply that, but it was what I (and others in the room) understood. This might be a misunderstanding, so let's restart from scratch:
So a specification project MAY invent new features in the specifiation FIRST, before ANY product actually implements this? Good for us! :-)
-Markus
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Dienstag, 11. September 2018 16:22
To: jakarta.ee-community@xxxxxxxxxxx
Subject: Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central
On 2018-09-09 7:18 AM, Markus KARG wrote:
Unfortunately this is not the EFs official policy. According to EF president Mike Milinkovic, all EE4J API projects shall NOT force features from vendors, but instead shall only wrap existing features under a common hood. What I did is adding feature to API AND to Jersey parallel, and encouraged other vendors to follow.
Markus,
I don't recall ever making the statement above. It's possible that there's been a misunderstanding.
I do expect innovation to happen in the specifications once we get the process going. There will have to be some give-and-take between the aspirations of the community and the vendors who have to bear the cost of implementing them. But I see that as a normal part of any specification process that desires to deliver new innovations.
