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 #321
Trusted Computing API for Java^TM
JSR Review Ballot
Ballot duration: 2007-11-27 to: 2007-12-10

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

Votes

SE/EE

Apache Software Foundation

BEA Systems

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 2007-12-04 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-06 SAP SE voted Yes with the following comment:
Our "YES" vote is contingent upon excluding this JSR from Java SE because the proposed GPL v2 license terms for RI and TCK will allow only limited commerical use. According to the Java SE Spec Lead, there are currently no plans to include this JSR into Java SE. 

------------------------------------------------------------------------------
On 2007-12-06 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-07 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 2007-12-07 Intel Corp. voted Yes with the following comment:
No Field Of Use issues with this JSR and the RI and TCK liceneses are publicly viewable.

The Spec Lead and Expert Group should work with TCG (Trusted Computing Group) where the TSS spec comes from that this builds upon.  TCG is still working in this area so this JSR must be consistent with it and with future directions.  An alternative would have been to do the Java API in TCG where the expertise in this area is.  With 2 prototypes but the creators of only one of them working on this proposed JSR in JCP, we don't know if doing this at TCG would have allowed participation of both.  The JSR requires expertise outside of Java so we hope those experts are consulted for input if they cannot participate in JCP.  It is imperative to coordinate closely with TCG.  
------------------------------------------------------------------------------
On 2007-12-08 Suleiman, Hani voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-10 SAS Institute Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-10 Lea, Doug voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-10 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 2007-12-10 Google Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-10 BEA Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-10 Nortel voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-10 Apache Software Foundation voted Yes with the following comment:
The ASF commends the spec lead for choosing an open source license for the RI and the TCK.
------------------------------------------------------------------------------
On 2007-12-10 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-12-10 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------