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 #304
Mobile Telephony API version 2
JSR Review Ballot
Ballot duration: 2006-07-18 to: 2006-07-31

These are the final results of the JSR Review Ballot for JSR #304. The Executive Committee for ME has approved this ballot.

Votes

Ericsson AB

IBM

Intel Corp.

Matsushita Electric Industrial Co., Ltd.

Motorola

Nokia Corporation

NTT DoCoMo, Inc.

Orange France SA

Philips Electronics UK Ltd

Research In Motion, LTD (RIM)

Samsung Electronics Corporation

Siemens AG

Sony Ericsson Mobile Communications AB

Sun Microsystems, Inc.

Symbian Ltd

Vodafone Group Services Limited

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

On 2006-07-19 Orange France SA voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-19 Research In Motion, LTD (RIM) voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-19 Motorola voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-21 Vodafone Group Services Limited voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-23 Siemens AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-23 Samsung Electronics Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-24 Nokia Corporation voted Yes with the following comment:
This JSR proposes media control related functionality related to telephony sessions. We think that any media related functionality must reuse the existing Java ME APIs for media functions as defined in JSR 135 Mobile Media API and JSR 234 Advanced Multimedia Supplements in order to have well coordinated management of the media resources in the device. Therefore, this JSR must design its API in a way that it reuses and integrates with JSRs 135 and 234.
Secondly, the JSR text refers to a 'a strong relationship to the Network Mobility and Mobile Data JSR' but such a JSR does not exist so far. We request clarification to the EC regarding the reference to such a JSR.
------------------------------------------------------------------------------
On 2006-07-24 Sony Ericsson Mobile Communications AB voted Yes with the following comment:
Sony Ericsson fully agrees with the comments from Nokia about the need for aligning multimedia support with the existing multimedia JSRs (JSR-135 &JSR-234).
------------------------------------------------------------------------------
On 2006-07-26 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-30 Philips Electronics UK Ltd voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-31 Intel Corp. voted Yes with the following comment:
Intel concurs with the comments by Nokia.
------------------------------------------------------------------------------
On 2006-07-31 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2006-07-31 IBM voted Abstain with the following comment:
IBM supports the notion that certain new mobile telephony features should have a consistent interface in the Java language.  However, IBM has  concerns about how this proposal will address that need.    We note that predecessor JSR253 has just been approved (March 06) via the JCP and has seen limited implementation.  We'd prefer to see any imagined function for a successor (in any form) stem from feedback as customer requirements from experience with multiple implementations.  We see significant potential overlap with JSR281, still in its infancy.   We'd like to see that the Expert Group will assure that relevant industry specifications are taken into account in the definition of this JSR.  We also note that the predecessor JSR253 is not a constituent component in JSR248/249 Mobile Services Architecture which itself seems to have significant industry interest.  We would like to see Expert Group membership that assures these overlaps can be resolved in a manner that is consistent and simple for industry adoption, prior to this coming to a community vote.  Ideally, we would like to see this JSR reformulated to assure this same consistent and simple industry adoption at its outset. 

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.
------------------------------------------------------------------------------