| Re: [jakarta.ee-spec.committee] compatibility and innovation agenda item |
|
On 2018-07-17 5:59 PM, Scott Stark
wrote:
How was this brought up in the context of the patent policy draft that Scott Peterson of Red Hat has contributed to? I know there has been a discussion of whether patent rights should be tied to the release of a specification or passing of the TCK, but I don't remember that being tied to a balance between innovation and compatibility? Scott, This was me paraphrasing to this group Scott P's words in an IP Advisory Committee call. But there does seem to be a misunderstanding. No one is saying that these two alternatives are an either/or. I.e. tying patent rights to TCK compliance does not kill innovation, nor does more open patent rights kill compatibility. They are slight nudges in different directions, not stark contrasts. To a large degree this is also a debate about whether we want
Jakarta EE to follow the status quo convention established by the
JCP, or do we want to follow what (as Scott Peterson says) current
best practices among specification organizations. I would also point out that Oracle has made it very clear that
the existing JCP approach of tying patent rights to TCK compliance
is a must for all of the Java EE 8 specifications being
contributed to Jakarta EE. Which I think is fair, given that it is
their IP they are contributing. So this debate is only about what
do we want to do for future, new, Jakarta EE specifications
outside of the javax namespace. |