2.1 Please describe the proposed Specification:

Personal Basis Profile provides a J2ME application environment for network-connected devices supporting a basic level of graphical presentation. Version 1.0 of Personal Basis Profile (JSR-129) served as the conceptual "basis" of Personal Profile 1.0: it is a subset of and upward-compatible to the more complete functionality of Personal Profile. Additionally, Personal Basis Profile 1.0 was derived from the J2SE 1.3.1 API specification. Applications written to the java.* APIs in this specification would therefore run on J2SE 1.3.1.

This JSR proposes to update the Personal Basis Profile specification to reflect the J2SE 1.4 APIs. The result, Personal Basis Profile version 1.1, will be backward-compatible to its 1.0 counterpart.

Note that while new APIs may be adopted from J2SE 1.4, no new, non-J2SE APIs are planned for definition in this JSR.

(* Estimated. Includes all of Foundation Profile 1.1. Application and localization memory requirements are additional. Version 1.1 of this profile includes an estimated 256 KB -- 512 KB ROM increase over the actual version 1.0 footprint. This estimated ROM increase is due to footprint increases expected in Foundation Profile 1.1 and additional graphics functionality in Personal Basis Profile.)

2.4 Why isn't this need met by existing specifications?

Personal Basis Profile 1.0 was derived from the J2SE 1.3.1 API specification. Since that time, J2SE 1.4 has provided a number of feature improvements and specification fixes. Personal Basis Profile 1.1 will be derived from J2SE 1.4 and will thus reflect the most up-to-date API versions.

In addition, future CDC optional packages are likely to be derived from J2SE 1.4, and it is important for the platform receiving these optional packages (in this case, Personal Basis Profile) to match the API version of the optional package for the sake of application compatibility and developer familiarity.

For example, the Advanced Graphics and UI (AGUI) Optional Package for J2ME (JSR-209) is based on J2SE 1.4 APIs, and will require an underlying AWT infrastructure that is also based on the 1.4 design. Personal Basis Profile 1.1 will provide the necessary support for JSR-209. Note, however, that this support is not expected to result in significant footprint increases or APIs that are unusable in the absence of JSR-209.

Finally, the Personal Basis Profile 1.0 graphics facilities lacked certain J2SE features which would be generally useful for consumer devices using AWT: J2SE 1.4 focus management and wide line drawing. The expert group for version 1.1 of this Profile will consider extending its graphics facilities to include these features and whether such support should be integrated into the platform or be made available through an optional package.

2.5 Please give a short description of the underlying technology or technologies:

Personal Basis Profile provides core graphics, UI, and application model facilities on top of the J2ME Foundation Profile. The graphics and UI facilities are well-known and derived from J2SE --- namely, the Abstract Windowing Toolkit (AWT) and portions of Java 2D. This Profile also provides the Xlet application model, which is unique to J2ME

.
Personal Profile is distinguished from Personal Basis Profile in that it provides the API facilities necessary for the execution of common Java web applets. Such applets make use of the applet application model and circa JDK 1.1 AWT heavyweight widget APIs. Both of these features are omitted from Personal Basis Profile; instead, it contains the AWT component framework APIs necessary for the support of lightweight widget toolkits such as Swing.

Both Personal Profile and Personal Basis Profile are built upon the J2ME Foundation Profile (JSR-46), which provides the core language, I/O and networking facilities for the platform..

Both Personal Profile and Personal Basis Profile are built upon the J2ME Foundation Profile (JSR-46), which provides the core language, I/O and networking facilities for the platform.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

None known.

2.8 Are there any security issues that cannot be addressed by the current security model?

None known.

2.9 Are there any internationalization or localization issues?

The J2ME Foundation Profile (on which this Profile depends) provides the necessary infrastructure for localization.

The AGUI Optional Package (JSR-209) proposes to include the J2SE Input Method Framework to assist the internationalization of Personal Basis Profile implementations.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

The specification for Personal Basis Profile 1.0 will be superceded by this specification.

Personal Profile is closely related to Personal Basis Profile. Work on this JSR will proceed in conjunction with work on a Personal Profile 1.1 JSR.

It is expected that the J2ME Foundation Profile (JSR-46) will require an update to match the J2SE 1.4 APIs in support of this work.

2.11 Please describe the anticipated schedule for the development of this
specification.

Community Review Draft: July 2003
Public Review Draft: August 2003
Completion: October 2003

2.12 Please describe the anticipated working model for the Expert Group working on developing this
specification.

E-mail, teleconference, and face-to-face discussions as needed and as appropriate, in coordination with the work of the JSR-209 expert group and the expert groups for the J2ME Foundation Profile and Connected Device Configuration.

Since this JSR is closely related to the one for Personal Profile 1.1, it is expected that the two expert groups will be identical in composition and will work on the two specifications concurrently.

2.13 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.

The RI and TCK will be delivered as part of this profile work.

2.14 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).

2.15 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.

The TCK and RI will be available for license separately:

* TCK:

o Annual license access fee providing access to the TCK code updates and upgrades, and basic support.
o Per unit royalty fee which will be dependent on volume.

* RI:

o Annual license access fee allowing commercial use of the RI code, as well as providing access to updates and upgrades.
o Per unit royalty fee which will be dependent on volume.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.