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 #311
JAX-RS: The Java^TM API for RESTful Web Services
Final Approval Ballot
Ballot duration: 2008-09-09 to: 2008-09-22

These are the final results of the Final Approval Ballot for JSR #311. The Executive Committee for SE/EE has approved this ballot.

Votes

SE/EE

Apache Software Foundation

Eclipse Foundation, Inc

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Lea, Doug

Nortel

Oracle

Red Hat

SAP SE

SAS Institute Inc.

Suleiman, Hani

Sun Microsystems, Inc.

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2008-09-10 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-15 Suleiman, Hani voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-16 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-19 Red Hat voted Yes with the following comment:
The spec lead of the EE6 specification has confirmed that the EE6 TCK would contain no "field of use restrictions", as originally raised by Apache with regard to another JSR (i.e. the SE TCK licensing). That is a good thing.

However, in the absence of an explicit JSPA rule that would forbid such field-of-use restrictions, we will remain worried that a similar issue might resurface anytime, for any JSR.

Consequently, in the future, for any submitted JSR (by SUNW or not), we will specifically expect the spec lead to provide clear information on that aspect and take the answer in account when casting our vote.
------------------------------------------------------------------------------
On 2008-09-19 Nortel voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-19 Lea, Doug voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-19 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-22 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-22 SAS Institute Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-22 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.

------------------------------------------------------------------------------
On 2008-09-22 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-22 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 (often confidential) license to obtain access to the TCK test suite must not be used to restrict what kind of devices or products implementations may be used with unless those restrictions appear in the spec itself.  The TCK is intended to ensure compatibility, not to provide the Spec Lead with a means to prevent implementations that faithfully implement the spec. The Apache Foundation claims they have been unable to obtain a TCK License that does not add  new restrictions on implementations for SE 5 or SE 6, despite the JCP requirement to provide TCK Licenses at no cost to not-for profits.

The public JSR 311 page says "The TCK license does not limit how a compatible implementation of the specification can be used or distributed, e.g., by limiting the hardware devices or operating environments that can be supported."   Since JSR 311 is part of Java EE (as well being standalone), and the EE spec requires SE, I assume this means that the Spec Lead (who is Spec Lead for SE, EE and JSR 311) offers both an EE TCK License and an SE TCK License for use together where there are no field of use restrictions in either license.

------------------------------------------------------------------------------
On 2008-09-22 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2008-09-22 Eclipse Foundation, Inc voted Yes with the following comment:
As the spec lead has explicitly committed that there are no field of use restrictions for this JSR, Eclipse votes yes.
------------------------------------------------------------------------------