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 #211
Content Handler API
JSR Review Ballot
Ballot duration: 2003-03-18 to: 2003-03-31

These are the final results of the JSR Review Ballot for JSR #211. The Executive Committee for ME has 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-03-31 IBM voted Abstain with the following comment:
As proposed, this JSR addresses this functionality for J2ME platforms CLDC 1.0/MIDP 2.0 and CDC/Foundation/Personal Profile.  As with all JSRs, we encourage the expert group to consider how this functionality applies across other Java platforms, as applicable.  Other platforms include J2SE, J2EE, MIDP 1.0, CLDC 1.1, and Personal Basis Profile.  All JSRs should strive for platform consistency, in support of an end-to-end programming model.
------------------------------------------------------------------------------
On 2003-03-20 PalmSource, Inc. voted Yes with the following comment:
The only comment I have is regarding the JSR's target of MIDP 2.0.  Is there any reason that MIDP 1.0 cannot be the lowest common denominator if there are no MIDP 2.0 API dependencies?  In general, all optional packages should target the widest possible base code set and MIDP 1.0 would allow that.  I realize in 6-9 months that MIDP 2.0 will hopefully be the "norm" but one can be assured that MIDP 1.0 will not be completely gone from the market.  I believe you should start with MIDP 1.0 as a base and try for that, and then go to MIDP 2.0 if technical reasons require it.  I would classify MIDP 1.0 as a goal and not a requirement.
------------------------------------------------------------------------------
On 2003-03-21 Research In Motion, LTD (RIM) voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-21 Motorola voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-25 Insignia Solutions voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-25 Symbian Ltd voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-27 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-28 Philips Electronics UK Ltd voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-30 Matsushita Electric Industrial Co., Ltd. voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-31 Nokia Corporation voted Yes with the following comment:
As one of its tasks EG should clarify the relation of this JSR to the existing content handler JSRs, especially JSR-135, and see how they cooperate and fit together.
------------------------------------------------------------------------------
On 2003-03-31 Siemens AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-31 Texas Instruments Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2003-03-31 BEA Systems voted Yes with no comment.
------------------------------------------------------------------------------