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

JSR287

StageJSR Review Ballot

Ballot durationDec 6, 2005 to Dec 19, 2005

Votes

ME

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

Vote Log

ME

On 2005-12-19 Intel Corp. voted Yes with the following comment:
In general, we concur with the idea expressed in other comments that standardization of a Java API should only follow (at the least) considerable progress on any underlying standards that it references.  However, it would seem that there is a balance to be struck between ensuring a certain degree of doneness in the underlying standard, and the advantage of having a standard Java API available soon after an underlying data format or protocol standard is available, and so the right timing is probably specific to each situation.

We have not had time to fully investigate the current status of the OMA work item referenced in this JSR, but we believe it appropriate to let the Spec Lead and EG start their work with the expectation that they will "do the right thing" with respect to the timing of the OMA work and this Java specification.

Given that concerns have been raised, we encourage the Spec Lead to educate the EC about the status of the OMA work, and the Spec Lead?s expectations and intentions with respect to the timing of the OMA standard and this Java API.

------------------------------------------------------------------------------
On 2005-12-19 Sun Microsystems, Inc. voted Yes with the following comment:
Sun is a supporter of an updated version of JSR 226 to reflect the new W3C SVG Tiny version 1.2 with the following caveats:
A new immediate mode API should not be included in this JSR since it  fully overlaps with existing APIs already in development JSR 209 for the CDC platform and should be included in the MIDP3 specification for the CLDC platform.  Inclusion in this JSR will cause further confusion for developers.
Only the SVG DOM APIs should be subsetted for this JSR.  Subsetting the SVG language is beyond the scope of a JSR and should be handled in the W3C SVG Working Group.
Defining a scene update API is within the scope of this JSR, but defining scene update syntax should be done within the W3C.
JSR 287 should be designed like JSR 226 so that it is compatible with all Java profiles
------------------------------------------------------------------------------
On 2005-12-19 Research In Motion, LTD (RIM) voted Abstain with the following comment:
RIM recognizes the comment by Orange as important for the Spec Lead to consider carefully. (e.g. coordinating and striking balance with efforts on similar topics at other standards organizations, resolving any potential overlap issues with other JSRs, with openess in mind)
------------------------------------------------------------------------------
On 2005-12-19 Matsushita Electric Industrial Co., Ltd. voted Abstain with no comment.
------------------------------------------------------------------------------
On 2005-12-19 Siemens AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-09 Nokia Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-12 Orange France SA voted No with the following comment:
Orange agrees a new version of SVG API is required in order to reflect evolution of W3C SVG from version 1.1 to version 1.2; from this perspective JSR 287 proposal fulfills an important Java ME community need and is supported by Orange. Nevertheless, OMA-3GPP Rich Media is not sufficiently dependent of the SVG standard to be included in the same JSR, as stated in JSR 287 proposal text, even as a separate optional package. Additionally OMA-3GPP Rich Media may not be mature enough to be targeted in JSR 287 schedule. Consequently, Orange does not support JSR 287 proposal text and suggests reconsidering the proposal without the references to Rich Media.
------------------------------------------------------------------------------
On 2005-12-15 Symbian Ltd voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-16 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-16 Sony Ericsson Mobile Communications AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-16 IBM voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-19 NTT DoCoMo, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-19 Vodafone Group Services Limited voted Yes with the following comment:
The job in OMA should be finished before the schedule of 287 to coordinate both groups
------------------------------------------------------------------------------
On 2005-12-19 Motorola voted Yes with no comment.
------------------------------------------------------------------------------
On 2005-12-19 Philips Electronics UK Ltd voted Abstain with the following comment:
Orange's comment would seem to have some merit.
------------------------------------------------------------------------------
On 2005-12-19 Samsung Electronics Corporation voted Abstain with the following comment:
Samsung also think Orange's comment seem to have some merit.
------------------------------------------------------------------------------