JCP Members may submit a Java Specification Request using this form. To get on the JSR Approval Ballot, submitted JSRs must be received on or before the Wednesday prior to the following Tuesday's ballot. The JSR is posted to the JCP website when the JSR Approval Ballot begins. Note that Executive Committee members submitting new JSRs should have their EC representatives send a message to spec-submit@jcp.org in parallel, confirming that the EC Member company is aware of and approves the submission.

* indicate required fields

Title: *
Please provide the name of the JSR.
See Sun Trademark and Logo Policies for guidelines for naming your JSR proposal. For information about the JSR Naming Program, please send inquiries to JSRNaming@sun.com.

Summary: *
Please provide a description of the JSR in 30 words or less.

Section 1: Identification

Initial Group Membership:
(Please provide company or organization names. Note that expert group members must have signed the JSPA.)

Supporting this JSR: *

Section 2: Request

2.1 Please describe the proposed Specification: *

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

2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.*

2.4 Should this JSR be voted on by both Executive Committees? *

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

2.6 Why isn't this need met by existing specifications? *

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

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

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

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

2.11 Are there any internationalization or localization issues? *

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

2.13 Please describe the anticipated schedule for the development of this specification: *

2.14 Please describe the anticipated working model for the Expert Group working on developing this specification.: *

2.15 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate.: *

2.16 Please describe how the RI and TCK will be 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.: *

2.17 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.16 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.18 Please provide the full text of the licenses that will apply to your Final Release Specification, Reference Implementation and Technology Compatibility Kit, or provide links to the same.: *

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. *

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

Section 4: Additional Information

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