JCP Members should use this form to submit a new Java Specification Request. The JSR is posted to the JCP website when the JSR Review begins. 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. Note that the JSR Approval Ballot always starts on a Tuesday, so the JSR Review may be extended slightly beyond the 2 or 4 weeks you specify in order to end the day before the ballot begins.

When filling out the form, please include HTML tags if you wish a certain formatting or to include links.

* indicate required fields

Title: *
Please provide the name of the JSR.
See Oracle Legal Notices for guidelines for naming your JSR proposal. For information about the JSR Naming Program, please send inquiries to pmo@jcp.org.

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

Duration: *
Please indicate the desired length of the JSR Review:
2 weeks
4 weeks

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

2.19 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications. *

2.20 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker? *

2.21 Please provide the location of the publicly accessible document archive you have created for the Expert Group: *

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.