Patrick Curran

Sun Microsystems, Inc.

 

Apache Software Foundation		Apple Computer, Inc.		BEA Systems
Borland		Caldera Systems		Cisco Systems
Compaq Computer Corporation		Ericsson		Fujitsu Limited
Hewlett-Packard		IBM		Insignia Solutions
Lea, Doug		Matsushita Electric Industrial Co., Ltd.		Motorola
Nokia Corporation		Nokia Networks		Oracle
PalmSource, Inc.		Philips Electronics UK Ltd		Progress Software
Research In Motion, LTD (RIM)		Siemens AG		Sony
Sun Microsystems, Inc.		Texas Instruments Inc.		Zucotto Wireless

Expert Group Private Page

JSR Community Update Page

 

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Original Summary: This JSR aims to define a new version of the Java Community Process. Its overriding goal is to ensure that the Process document is in sync with the new version of the JSPA under development by JSR 99.

Section 1. Identification

Submitting Member: Sun Microsystems, Inc

Name of Contact Person: Onno Kluyt

E-Mail Address: onno.kluyt@sun.com

Telephone Number: +1 650 352 4752

Fax Number: +1 408 276 7129

Specification Lead: Onno Kluyt

E-Mail Address: onno.kluyt@sun.com

Telephone Number: +1 650 352 4752

Fax Number: +1 408 276 7129

Initial Expert Group Membership:

The Expert Group will consist of the Members of the two JCP Executive Committees, see http://jcp.org/participation/committee/.

Supporting this JSR:

The Members of the two JCP Executive Committees http://jcp.org/participation/committee/ are supporting this JSR submission.

Section 2: Request

2.1 Please describe the proposed Specification:

This JSR aims to define a new version of the Java Community Process. Its overriding goal is to ensure that the Process document is in sync with a new version of the JSPA under development by JSR 99. The key process changes driven by the work of JSR 99 are:
- Visibility for the EC into a Spec Lead's decision whether or not to make the output of a JSR available for independent implementation. This visibility requirement may take the form of inclusion of business terms in the JSR submission, a special vote by the EC following a JSR's
approval, or other subject to the deliberations of this JSR's Expert Group.
- Indication under what JSPA version a JSR is executing.
- Any required Process changes because of the Special Patent Considerations in JSR 99.

It is required that this JSR's schedule follows that of JSR 99 for the successful migration of the Community's membership to the JSPA defined by JSR 99. The Process revision proposed by this JSR cannot go into effect without the availability of the JSPA being defined by JSR 99.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

Not applicable.

2.3 What need of the Java community will be addressed by the proposed specification?

JSR 99 is developing a new version of the JSPA (Java Specification Participation Agreement). The JSPA sets forth the basic legal structure for the Java Community Process. Certain aspects of that new JSPA (such as Independent Implementations and patent provisions) require changes to the Process in order to be effective. In order to keep the basic legal structure in sync with the Process description it is necessary to perform this JSR.

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

See 2.1 and 2.3.

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

Not applicable.

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

Not applicable.

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

Not applicable.

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

Not applicable.

2.9 Are there any internationalization or localization issues?

It is the goal of this JSR not to introduce any aspects in the JCP Program that would hinder the current successful international participation in the process.

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 output of this JSR will become the active working model of the Community, replacing the current rules of JCP 2.1.

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

Community Review: April 2002
Public Review: June 2002
Proposed Final Draft: July 2002
Final Approval: July 2002

Note that from the completion of Community Review onwards it is the goal of this JSR's Spec Lead to have the schedule be the same as JSR 99's schedule. It is especially important that both JSRs complete at the same time.

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

The two Exectuive Committees together form the Expert Group with the JCP PMO as the Spec Lead. It is expected that the current working group for JSR 99 - the so-called Ad Hoc committee - will perform the majority of the work effort for this JSR. The Ad Hoc committee will report to the ECs during the regular EC meetings. The Ad Hoc committee has frequent conference calls as well as exchange and discussion via email.

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.

JCP 2.1 document: http://jcp.org/procedures/jcp2/
The current JSPA: http://jcp.org/participation/membership/
JSR 99: http://jcp.org/jsr/detail/99.jsp.

3.2 Explanation of how these items might be used as a starting point for the work.

JCP 2.1 and the current JSPA define the starting points. JSR 99 provides the requirements for this JSR.

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.

This JSR will not produce a RI and TCK. See Appendix B of the JCP 2.1 document.