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

JSR214

StageJSR Review Ballot

Ballot durationApr 15, 2003 to Apr 28, 2003

Votes

ME

BEA Systems

IBM

Insignia Solutions

Matsushita Electric Industrial Co., Ltd.

Motorola

Nokia Corporation

PalmSource, Inc.

Philips Electronics UK Ltd

Research In Motion, LTD (RIM)

Siemens AG

Sony Ericsson Mobile Communications AB

Sony International (Europe) GmbH

Sun Microsystems, Inc.

Symbian Ltd

Texas Instruments Inc.

Zucotto Wireless

Vote Log

ME

On 2003-04-23 Sun Microsystems, Inc. voted No with the following comment:
Sun thinks that approving this JSR as submitted will not set the project up to be successful. The JSR does not motivate a Java Community need to dynamically manipulate ebXML CCP/A documents on small devices. Sun itself does not see such a need, and has not heard one expressed by the Java Community. 

Should such a need be identified, a basic prerequisite for scoping such an activity would be to reference, leverage and compliment the work of the JSR-157 expert group.
------------------------------------------------------------------------------
On 2003-04-24 Research In Motion, LTD (RIM) voted Abstain with the following comment:
JSR 172 seems to be a related ME JSR so the fact that it wasn't mentioned means the technical scope of this JSR may overlap with other JSRs. A check into EE JSRs should also be done to ensure an existing JSR isn't available to be adapted for ME. The lack of supporters and jcp members ready to sign up for the EG looks troubling also.  Supporters lend credibility to the perception that the Java community "needs" this domain standardized.

------------------------------------------------------------------------------
On 2003-04-25 Motorola voted No with the following comment:
We believe that the technology area discussed by this JSR proposal is too immature to support its codification in a JSR. We encourage Iopsis to stay involved in the Java Community Process and when this need matures, build a base of industry support and resubmit their proposal as either part of another JSR or as a stand alone JSR.
------------------------------------------------------------------------------
On 2003-04-25 Nokia Corporation voted No with the following comment:
We do not see any important use cases for this, and not in a mobile device.
There are so many things unclear in the area of what this JSR suggests that we do not believe it become succesful.
JSR 157 (ebXML CPP/A APIs for Java), for example, has not made much progress since Nov 2001.
Ideally that JSR should first put something into community review at least,
before a decision on whether a J2ME-specific subset is  needed or not? 
We just do not see this important currently.
Iopsis might wish to come back to the issue when the area has been matured.
------------------------------------------------------------------------------
On 2003-04-25 PalmSource, Inc. voted No with the following comment:
We do not see such a serious need being addressed here, and wonder about this JSRs viability.
------------------------------------------------------------------------------
On 2003-04-27 Matsushita Electric Industrial Co., Ltd. voted Abstain with no comment.
------------------------------------------------------------------------------
On 2003-04-28 Insignia Solutions voted No with the following comment:
Sames issues as 213.
------------------------------------------------------------------------------
On 2003-04-28 Sony Ericsson Mobile Communications AB voted No with the following comment:
We do not see the need for this now. 
------------------------------------------------------------------------------
On 2003-04-28 Symbian Ltd voted No with the following comment:
We would like to see clearer demand and use cases for ebXML CPPA document handling on CLDC/mobile devices
------------------------------------------------------------------------------
On 2003-04-28 Philips Electronics UK Ltd voted No with the following comment:
This proposal needs a lot more discussion among the interested parties than seems to have happened. That should happen before any re-submission.
------------------------------------------------------------------------------
On 2003-04-28 IBM voted No with the following comment:
ebXML CPP/A APIs are already being defined by JSR-157, which ideally would address the needs of all platforms.  Given that JSR-157 has made little progress since Nov 2001 and the current lack of demand for this functionality in J2ME, this JSR needs to wait until these conditions change.  
------------------------------------------------------------------------------
On 2003-04-28 Texas Instruments Inc. voted No with the following comment:
It is not clear to us that a standalone J2ME JSR for the proposed activity is needed.
------------------------------------------------------------------------------
On 2003-04-28 Siemens AG voted No with the following comment:
ebXML is already wide-spread, but taking into account the upcoming web service paradigm, it is not clear, whether ebXML will stay as it is.
For us it is unclear what the use cases for ebXML CPPA on CLDC devices are and how the APIs of JSR 157 are taken into account.
------------------------------------------------------------------------------
On 2003-04-29 BEA Systems voted No with the following comment:
This proposal is premature, and insufficiently motivated for J2ME devices.
------------------------------------------------------------------------------