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 #213
Micro WSCI Framework for J2ME.
JSR Review Ballot
Ballot duration: 2003-04-15 to: 2003-04-28

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

Votes

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

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

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 for the application of web service choreography technologies to 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, we think basic prerequisites for this JSR would be consideration of the work of BPEL4WS at OASIS, which we believe the industry is consolidating around, as well as the Java API work starting in the JCP under JSR-207. Finally, we think that work on XML processing proposed by this JSR unnecessarily duplicates work well under way in JSR-172.
------------------------------------------------------------------------------
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:
It is very difficult to understand the practical relevance of this JSR at the moment. 
We don't see any appealing use cases that suggest a meaningful "coordinator" role for a terminal in choreographed collaborations nor do we see that this kind of scenarious would come every day business any time soon. This is taking still time even for the the mainstream WS community, and many things need to be clarified before it happens.
The relationship to JSR172's JAXP work, or to JSR173 (Streaming API for XML) which is working on XML pull parsers has not been explained either.
And we'd like to see that not every JSR is involving in creating generic things such as XML parsing etc. 

------------------------------------------------------------------------------
On 2003-04-25 PalmSource, Inc. voted No with the following comment:
This is a JSR proposal based on standards, which is a good thing. However, we don't see a significant need being addressed here. If this passes, then this JSR must work in concert with the APIs defined in JSR 172 Web services to ensure compatibility and extensibility of those APIs.  A single stack of optional Web services packages in the J2ME space is desirable and in fact a necessity to reduce potential API fragmentation.
------------------------------------------------------------------------------
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:
The potential redundancies with 172 and the unclear position of endorsement leads Insignia to be believe that this JSR needs more work. 
------------------------------------------------------------------------------
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 Abstain with the following comment:
Mobile client devices will need the ability to discover, coordinate, and integrate multiple web services. We therefore believe this is important technology. 

However we are also concerned with the overlap with other JSRs
------------------------------------------------------------------------------
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:
The relationship of this proposal with JSR-172 and Oasis BPEL4WS is unclear.
------------------------------------------------------------------------------
On 2003-04-28 Texas Instruments Inc. voted No with the following comment:
We believe that JSRs addressing similar technologies should be coordinated. We encourage the submitters to contact the spec leads of the related ME web services JSRs and get agreement on how and when to proceed with this proposed activity.
------------------------------------------------------------------------------
On 2003-04-28 Siemens AG voted No with the following comment:
We believe that Web Service Choreography is certainly the future of Web Services. Currently,a lot of standardization organizations and companies make own proposals, but it is not really clear, what is really necessary for support of choreography on J2ME devices.
Also the relationship of this proposal with JSR-172 and Oasis BPEL4WS is unclear.
We think that JSRs addressing similar technologies should be coordinated.

------------------------------------------------------------------------------
On 2003-04-29 BEA Systems voted No with the following comment:
This proposal did not adequately address overlaps with other specifications in process.
------------------------------------------------------------------------------