JSR 271, Mobile information Device profile 3 start!

JS Jsrs:java specification REQUESTSJSR 271:mobile Information Device profile 3
This JSR would specify the 3rd generation Mobile Information Deviceprofile, expanding upon the functionality in all areas a S-asimproving interoperability across devices.
Status:in Progress Stage Start Finish Expert Group formation Mar, "JSR Review ballot View results-Mar, JCP version in Use:2.6java Specification participation agreement version I N Use:2.0please Direct comments on this JSR to:jsr-271-comments@jcp.org specification Leadjim Van Peursem Motorola E Xpert Groupmotorolai would like to join this Expert groupexpert Group Private Page JSR Community Update page
Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information



Section 1. Identification

Submitting Member:motorola

Name of contact Person:dr. James E. Van Peursem

E-Mail address:jim.van.peursem@motorola.com

Telephone Number: +1 847 523 1051

Fax Number: +1 847 523 2854

Specification Lead:dr James E. Van Peursem

E-Mail address:jim.van.peursem@motorola.com

Telephone Number: +1 847 523 1051

Fax Number: +1 847 523 2854

Initial Expert Group Membership:

Initial EG Membership:

* Aplix * Cingular * Ericsson Mobile platforms (EMP) * Esmertec * IBM * Intel * Nokia * Orange France * Philips * RIM * Si Emens * Sony-ericsson Mobile * Sun Microsystems, Inc. * T-mobile * Vodafone

Supporting this JSR:

* Aplix * Cingular * Ericsson Mobile platforms (EMP) * Esmertec * IBM * Intel * Orange France * Philips * RIM * Siemens * Sony-ericsson Mobile * Sun Microsystems, INC * T-mobile * Vodafone

Section 2:request


2.1 Please describe the proposed specification:
This JSR would build upon the success of MIDP2 by enhancing the profiles with the following additions/changes:


* Enable and specify proper behavior for MIDlets on each of the CLDC, CDC, and OSGi, for Example:o Enable multiple concurrent MIDlets in one VM o specify proper firewalling, runtime behaviors, and lifecycle management ISS UEs for MIDlets o enable background MIDlets (e.g. ui-less) o enable auto-launched? MIDlets (e.g. started at platform boot time) o Enable Inter-midlet Communications * Enable shared libraries for MIDlets * Tighten spec. Areas to improve cross-device interoperability * Increase functionality in all areas. E.G.O improve UI expressability and extensibility o Better support for devices with larger displays O-Enable MIDlets to Dr AW to secondary display (s) o Enable richer and higher performance games o Secure RMS stores o removable/remote RMS stores o IPv6 o multiple network interfaces per device* Specify standard ways for doing MIDlet provisioning through Othermeans (E . G. OMA (SyncML) dm/ds, Bluetooth, removable media, mms,jsr-232, etc.) * Extensive device Capabilities QUery * Localization & Internationalization (if appropriate, integrating/augmenting JSR-238 as needed)
A Key design goal of MIDP3 is backward compatibility with MIDP2 content.
2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)
MIDP on Mobile handsets
2.3 The Executive committees would like to ensure JSR submittersthink about you their proposed technology relates to all O f the Javaplatform editions. Please provide to the which platformeditions are being targeted by this JSR, and how this JSR hasconsidered the Relationship with the other platform editions.
The target platform is the "MID profile" in J2ME.
2.4 Should This JSR is voted on by both Executive committees?
No
2.5 What need of the Java community would be addressed by the proposed specification?
This JSR would specify the 3rd generation Mobile Information Deviceprofile, expanding upon the functionality in all areas a S-asimproving interoperability across devices.
2.6 Why isn ' t this need met by existing specifications?
N/A
2.7 Give a short description of the underlying technology or technologies:
CLDC, CDC, OSGi, and MIDP 2.0
2.8 Is there a proposed package name for the API specification? (i.e, javapi.something, org.something, etc.)
javax.microedition.*
2.9 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you kno W of?
No
2.10 Are there any security issues that cannot is addressed by the current security model?
No
2.11 Are there any internationalization or localization issues?
No
2.12 Are there any existing specifications that might is renderedobsolete, deprecated, or in need of revision as a of this work?
Yes. JSR-118 MIDP 2.0
2.13 Please describe the anticipated schedule for the development of Thisspecification.
The targeted schedule for the ' JSR is as follows:-Expert Group formation:march-2005-early Draft review:september 2005 -Public review:january 2006-proposed Final draft:march 2006-final Approval Ballot:may 2006
2.14 Please describe the anticipated working model for the Expert Group working on developing thisspecification.
The Expert Group would conduct its work into a similar fashion to THEMIDP 2 Expert group. This is, the primary means of communication willbe via email list (s) and Web site (s). In addition, Periodicface-to-face meetings is held approximately every 6-8 weeks, andphone conferences as needed for Special issues that need to be resolvedbetween meetings. Decisions is made by technical consensus.
2.15 It is important to the success of the community and each jsrthat the work of the Expert Group being handled in a manner Which providesthe community and the public with the insight into the work the Expertgroup are doing, and the decisions that the Expert Group has made. Theexecutive committees would like to ensure Spec. Leads understand thevalue of this transparency and ask all JSR hav e an operating Planin place for how their JSR would address the involvement of thecommunity and the public. Please provide your and refer tothe Spec leads Guide for a more detailed description and a set ofexample questio NS you could wish to answer in your.
Transparency Plan:a) All members of the expert Group would be allowed to subscribe to andparticipate into discussions on the Email list (s) as they choose. Theface-to-face meetings'll be open to all active participants with alimit of one representative Keep the meetingspace to a reasonable size (i.e. approx 30-35 people). Any free Seatswill is made available to observers in some kind of simple lottery-typesystem, similar to how MIDP2 is Orga NIZED.B) The specification lead would, on a quarterly basis, provide a BRIEFJSR status to the JCP PMO, for publication to T He Java community. Thiswill include the current schedule for the JSR and notes on any majorevents that have occurred in the previous quarter.
2.16 Describe how the RI and TCK'll de delivered, i.e. Aspart of a profile or Platform edition, or stand-alone, O R both. Includeversion information for the "profile" or platform in your answer.
An independent RI and TCK'll be produced as a part of this JSR with each being licensed separately.
2.17 Please state the rationale if previous versions are Availablestand-alone and your are now proposing into 2.13 to only de Liver RI Andtck As part of a profile or Platform edition (for a. Sections 1.1.5 and1.1.6 of the JCP 2 document).
N/A
2.18 Please provide a description of the business terms to Thespecification, RI and TCK that'll apply when this JSR is Final.
These are terms only represent the initial commercial terms to is usedand remain to the subject of final execution legal ments Coveringthe subject matter hereof to is determined by Motorola in its solediscretion.

We'll license to all interested parties.

Independent implementations would be ALLOWED-TCK and RI would be licensed separately.

For TCK we do to charge a single one-time fee for access and anannual maintenance fee for a term of four. The actual size of thelicense fees is based on the associated development, with atarget of the cost recovery. Since MIDP are much larger and Complexthan most other JSRs, we anticipate the fees of $100,000 of USD forone-time fee and $50,000 for annual maintenance fee.

TCK would include both binary environment and source code of the test suite.

Maintenance fee covers limited basic support, level TCK appealsprocess, bugs fixes when available and updates, which are due to changesin the specification. Major new releases May is subject to additionalsingle one time fee.

For RI in source code form we'll charge a per unit license fee. Maintenance releases'll cover bug fixes, updates and new releasesnecessary due to spec changes, and when made generally Available Byspecification lead.

Section 3:contributions


3.1 Please list any existing documents, specifications, orimplementations that describe the technology. Please include links tothe documents if they are publicly available.
JSR-118 MIDP 2.0
3.2 Explanation of how this items might is used as a starting point for the work.
This specification would serve as the basis for beginning the Work,which would be extended, enhanced, and clarified. Note This backwardcompatibility with specified MIDP 2.0 behaviors'll be of the paramountimportance wherever possible.

Section 4:additional information (Optional)


4.1 This section contains any additional information which the submitting member is wishes to include in the JSR.