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 #263
Fault Management API
Final Approval Ballot
Ballot duration: 2007-08-14 to: 2007-08-27

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

Votes

SE/EE

Apache Software Foundation

BEA Systems

Borland Software Corporation

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-08-17 Nortel voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-20 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-20 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-20 Borland Software Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-21 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-08-21 Suleiman, Hani voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-21 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-22 BEA Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-23 IBM voted Yes with the following comment:
Our experience in implementing  the Fault API has shown that  it provides only basic capabilities and not rich enough to meet real life reqiurements. So in almost all cases we land up extending it and being one off from standards spec. We recommend that the Fault API should expose more service interfaces and the data structure to pass information back and forth needs to be enriched to accomodate real-life requirements.

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-08-24 SAS Institute Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-26 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2007-08-27 Intel Corp. voted Yes with the following comment:
We commend the Spec Leads for providing to the EC the text for all the required licenses for implementing this JSR's spec.  All too often the EC is given only vague, partial information and have no idea if the terms permit open implementation. We  encourage other Spec Leads to provide full text of at least one alternative for the JCP required licenses.
------------------------------------------------------------------------------
On 2007-08-27 Apache Software Foundation voted Yes with the following comment:
Thanks for the Field-Of-Use-Free TCK binary license, and kudos for the open source TCK.
------------------------------------------------------------------------------
On 2007-08-27 Fujitsu Limited voted Yes with no comment.
------------------------------------------------------------------------------