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 #184
Mobile 3D Graphics API for J2ME^TM
JSR Review Ballot
Ballot duration: 2002-04-23 to: 2002-05-06

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

Votes

BEA Systems

Cisco Systems

Ericsson Inc.

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 International (Europe) GmbH

Sun Microsystems, Inc.

Texas Instruments Inc.

Zucotto Wireless

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

On 2002-04-26 Philips Electronics UK Ltd voted No with the following comment:
The vote against this is for the following reasons;

1) A set of optional packages for various features used by games applications will cause significant market fragmentation and developer confusion as different manufacturers made different decisions about which of those optional packages to include.

2) I have colleagues who have spent years working on non-games applications for 3D graphics in consumer products. Lots of nice & attractive demos were produced by nothing actually made it into a product. I simply do not see non-games applications for 3D being realistic. Even if there was a small chance of this, I believe the 3D API needs to have an optimised fit with
its largest initial user. I strongly believe this is best done within the JSR-178 EG as a second optional package there and not as a separate JSR.
If it has to be a separate JSR then it must have the same spec lead & EG.

3) JSR-178 has a clear commitment to work with JSR-134 "to facilitate migration from one platform to the other". JSR-184 explictly rejects this "we hope to keep this JSR small, focussed, and independent of the feature set implemented in JSR-134."
------------------------------------------------------------------------------
On 2002-04-25 Matsushita Electric Industrial Co., Ltd. voted Abstain with the following comment:
Matsushita abstains from voting this JSR with the following comments:
 JSR178 also defines the 3D APIs for J2ME.
 If JSR178 overlaps with JSR185, it will cause the fragmentation of the 
 3D APIs for J2ME.
 We believe the JSR should be revised to clarify the relation with JSR178.
------------------------------------------------------------------------------
On 2002-04-25 Nokia Corporation voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-04-23 Motorola voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-05-06 BEA Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-05-06 IBM voted Yes with the following comment:
We support optional, general purpose, APIs, like 3D Graphics, to be developed as separate JSRs; rather than as additions to existing profiles.  This allows for an evolution where Profiles serve as umbrella platforms and APIs are components that can be added to a profile in a modular fashion.
------------------------------------------------------------------------------
On 2002-05-06 Zucotto Wireless voted Yes with the following comment:
We support JSR-184 and agree with the need to implement 3D graphics outside of the gaming context for applications such as screen savers, transitions, animated characters, UI, etc. but acknowledge that in the near term, gaming may be the most significant driver. 

As such, we strongly recommend JSR-184 adopt a similar Spec Reviewer (as is being done in JSR-178) category that will allow all interested 3D engine, gaming engine and gaming application developer experts contribute to the API. 

We also have the following additional comments that MUST be followed to ensure success:

· JSR-184 MUST ensure its expert group contains a representative sampling of experts from JSR-178 core expert group
· JSR-184 MUST add at least one other 3D engine company to the Expert Group
· JSR-184 MUST add at least one other 3D engine company / content provider from Asia to the Expert Group

· Suggest that light sources, transparency, high level mesh support and synchronization with audio be addressed in JSR-184 in addition to the features mentioned
· Game specific features such as collision detection be defined by JSR-178
· A high level of abstraction be maintained to allow for flexibility in underlying implementation
------------------------------------------------------------------------------
On 2002-05-06 Texas Instruments Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-05-06 Research In Motion, LTD (RIM) voted Abstain with the following comment:
The timing of the vote to coincide with the last day of voting for JSR 178 makes it difficult to vote properly in that JSR 184 would make a good companion to JSR 178.
------------------------------------------------------------------------------
On 2002-05-05 Ericsson Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-05-03 Insignia Solutions voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-05-03 Sun Microsystems, Inc. voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-05-02 Cisco Systems voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-05-01 Siemens AG voted Yes with no comment.
------------------------------------------------------------------------------
On 2002-04-29 PalmSource, Inc. voted Yes with the following comment:
Overall, in favor of it.  But this JSR MUST work very closely with JSR 178 to ensure reuse of the 3D modeling APIs in both packages.  We see 184 (or at least the base 3D modeling engine) as a reusable part for JSR 178.  One potential structuring is to have the reusable 3D modeling APIs in a javax.microedition.3d package, and then have specific add-on APIs in subpackages, such as javax.microedition.3d.ui.  Then the 3d package can be reused in JSR 178.  REUSE is key to this JSR and JSR 178's further success.
------------------------------------------------------------------------------