The Java Community Process(SM) Program - JSRs: Java Specification Requests

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy

JSR #303
Bean Validation
Public Review Ballot
Ballot duration: 2009-02-03 to: 2009-02-09

These are the final results of the Public Review Ballot for JSR #303. The Executive Committee for SE/EE has approved this ballot.

Votes

SE/EE

Apache Software Foundation

Eclipse Foundation, Inc

Ericsson AB

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Keil, Werner

Lea, Doug

Nortel

Oracle

Red Hat

SAP SE

Sun Microsystems, Inc.

VMware

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2009-02-09 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-09 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-09 Lea, Doug voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-09 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-09 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-03 Apache Software Foundation voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-03 Eclipse Foundation, Inc voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-04 Red Hat voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-04 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-05 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-05 Intel Corp. voted Yes with the following comment:
This is a general comment we make in each ballot  By the agreement that forms the JCP, other than reciprocity rules for licensing and three compatibility conditions (including passing the TCK test suite) "the Spec Lead agrees not to impose any contractual condition or covenant that would limit or restrict the right of any licensee to create or distribute such Independent Implementations." The Apache Foundation claims in an open letter that they have been unable to obtain a TCK License that does not restrict compatible implementations of the SE Platform (additional restrictions that are not in the  specification itself). 

The JSR page says the TCK for the standalone version of the spec will be open source (so no field of use problems.  However, when included in a platform spec, the platform spec must not directly or indirectly (through other specs it requires like SE) limit how compatible implementations can be used (other than what is in the spec of course).
------------------------------------------------------------------------------
On 2009-02-06 Keil, Werner voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-08 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2009-02-09 IBM voted Yes with the following comment:
IBM's vote is based on the technical merits of this JSR and is not a vote on the licensing terms.  IBM supports licensing models that create an open and level playing field by allowing third parties to create independent implementations of Java Specifications and that do not allow individuals or companies to exercise unnecessary control for proprietary advantage.  We support open source as a licensing model for contributions in the JCP, and would hope others will support this direction. This comment is not necessarily directed at the current business or license terms for this JSR, however, it is a statement of IBM's preferred licensing model.

------------------------------------------------------------------------------