General questions | Membership questions | JSR and Expert Group questions | Spec Lead process questions | Login questions | Web Site questions | Glossary
The JCP 2 Process Document defines many terms and acronyms that are used throughout the JCP website. This page collects all the definitions in one place for easy reference. The definitions are arranged alphabetically.
A | B | C | D | E | F | I | J | M | O | P | Q | R | S | T | U | W
Active: a JSR Status label indicating a specification development project which is moving quickly through the stages of the JCP but has not yet produced a Final Release.
Appeal Ballot: The EC ballot to override a first-level decision on a TCK test challenge.
Associate Member: An individual who wishes to participate independently in the activities of the JCP without requiring an employer's permission.
Associate Membership Agreement: The membership agreement signed by Associate Members.
Associate Seat: An Executive Committee seat filled by the election process described in section 3.7.6 of the JCP 2.10 document.
Ballot: See Appeal Ballot, Final Approval Ballot, Final Approval Reconsideration Ballot, JSR Ap-proval Ballot, JSR Reconsideration Ballot, JSR Renewal Ballot, JSR Renewal Reconsideration Ballot, JSR Withdrawal Ballot, Maintenance Review Ballot, Maintenance Renewal Ballot, Maintenance Release Withdrawal Ballot, Public Review Ballot, Public Draft Specification Recon-sideration Ballot, Transfer Ballot. Unless otherwise noted in this document all Ballots last for 14 days.
Change Log: An area accessible from the Spec Page that lists all changes made to the Specification after Final Release. There are three sections: PROPOSED (changes not yet made to the Specification), ACCEPTED (changes made), and DEFERRED (change items to be considered in a new JSR).
Community Review: A 30 to 90 day period when Members review and comment on the draft Specification. Used in JCP 2.5 and earlier versions.
Continued Availability: Describes a set of rules for standalone JSRs (Java APIs not part of a Java platform) that become part of a Java platform (such as J2EE platform or the J2SE platform) later on as the result of a future JSR for that API.
Contributor Agreement: A legal agreement defining the terms, particularly those concerning the grant of intellectual property rights, under which contributions are made to a project.
Contributor: A JCP Member who is not a member of an Expert Group but who at the Spec Lead's discretion is formally recognized as having contributed to the JSR.
Dormant: A JSR Status label indicating that no work is underway on the specification development project, either because there is no Lead or because the Executive Committee voted to remove it from the list of active JSRs after a long period of inactivity.
Dormant Specification (Dormant): A Specification that does not have an identified Maintenance or Specification Lead, or which has been Inactive for a very extended period. All Specifications become Dormant at the end of their life cycle, but a JSR may become Dormant sooner through long inactivity and a ballot from the Executive Committee.
Draft Specification Approval Ballot: The EC ballot to determine if a Community Review draft should proceed to Public Review. Used in JCP 2.5 and earlier versions.
Draft Specification Reconsideration Ballot: The EC ballot that followed Community Review in JCP 2.5 and earlier versions, held to determine if a revised draft should proceed to Public Review.
Early Draft Review: A 30 to 90 day review period when a draft of the Specification is made available to the public for review and comment.
Elected Seat: An EC seat filled by the election process described in section 3.7.6.
Employer Contribution Agreement: An agreement that must be signed by the employer of an individual Full Member in which the employer makes certain IP commitments with respect to the employee's participation in the JCP.
Errata Maintenance Release: An update to a Final Release specification consisting only of corrections and clarifications. Introduced in JCP 2.11, an Errata Maintenance Release is published as soon as the corrections are ready; it does not require a Maintenance Review.
Executive Committee (EC): The Members who guide the evolution of the Java technologies. The EC represents a cross-section of both major stakeholders and other Members of the Java Community. EC Members must be elected or ratified by votes of the JCP Members in order to serve on the EC. The EC Policies and Procedures are in the EC Standing Rules. Note that, before JCP 2.9, "Executive Committee" could refer to either or both of two separate Committees which guided the evolution of the Java platforms: the SE/EE Executive Committee (for JSRs relating to Standard Edition or Enterprise Edition) and the ME Executive Committee (for JSRs relating to Micro Edition). To read more, visit the Executive Committee page.
Executive Committee for ME: The 16-seat committee of ratified and elected Members which reviewed Java ME-related JSRs from May 2000 - November 2012. With JCP 2.9, the ME EC merged with the SE/EE EC to form a single Executive Committee which reviews all JSRs operating under JCP 2.5 and above.
Executive Committee for SE/EE: The 16-seat committee of ratified and elected Members which reviewed Java SE and Java EE-related JSRs from May 2000 - November 2012. With JCP 2.9, the SE/EE EC merged with the ME EC to form a single Executive Committee which reviews all JSRs operating under JCP 2.5 and above.
Expert: A term from JCP 2.9 and earlier that referred to a Member representative who had expert knowledge and was an active practitioner in the technology covered by the JSR.
Expert Group: The group of JCP Members who develop or make significant revisions to a Specification.
Final: A JSR Status label indicating that a specification development project has produced its Final Release, the Specification can be implemented, the Reference Implementation and Technology Compatibility Kit are available, and the Expert Group has disbanded.
Final Approval Ballot: The EC ballot to approve the Final Draft along with its associated RI and TCK.
Final Approval Reconsideration Ballot: The EC ballot to reconsider an initial rejection of a Final Draft, RI, and TCK.
Final Draft: The final draft of the Specification that will be put forward for EC approval.
Final Release: The final stage in the JSR development process when the Specification, RI, and TCK have been completed and can be licensed by implementers.
First-Level TCK Appeals Process: The process defined by the Spec Lead that allows implementors of the Specification to appeal one or more tests defined by the Specification's TCK.
Full Member: A corporation, organization, or individual who has signed the JSPA in order to obtain full membership rights within the JCP.
IEPA1: The IEPA that covered an individual's participation on the Expert Group of a JSR started before October 29, 2002. IEPAs are no longer used, having been replaced by Individual Memberships.
IEPA2: The revised IEPA that covered an individual's participation on the Expert Group of a JSR started between October 29, 2002 and March 9, 2004. IEPAs are no longer used, having been replaced by Individual Memberships.
Inactive: a JSR status label applied to a JSR which has not reached Final Release nor has posted a milestone for 12 months or more.
Individual Expert Participation Agreement (IEPA): An agreement between Sun Microsystems and an individual that allowed that individual to serve on an Expert Group at the invitation of the Specification Lead. There was no fee associated with the IEPA and it was valid until the Expert Group disbanded. The IEPA allowed individual technical experts who did not represent companies or organizations to participate on an Expert Group without becoming a JCP Member. IEPAs are no longer used; the IEPA has since been replaced with the Individual Membership.
Individual Member: a person who has signed the Java Specification Participation Agreement and become a JCP Member as an individual, rather than as a representative of any organization.
Issue: an explicit reference to an item defined in an Issue Tracker.
Issue List: A list of Issues generated from an Issue Tracker, identifying the disposition of each.
Issue Tracker: A mechanism to allow issues (problems, tasks, comments, or requests for change) to be recorded and tracked by priority, status, owner, or other criteria. The Issue Tracker should permit issues to be identified by states such as open, resolved, and closed and should support the assignment of resolution types such as deferred (postponed to a follow-on release,) fixed (implemented,) challenged (no satisfactory resolution,) and rejected (deemed inappropriate or out of scope.)
Item Exception Ballot: The EC ballot to determine whether or not to include specific change items in a Minor Revision. Used in JCP 2.7 and earlier versions.
Iterative JSR: A JSR that intends to deliver multiple releases with multiple JSRs of a technology on a time-based cadence.
J2ME Building Block (Building Block): A subset of one or more APIs defined in the J2SE or J2EE Platform Edition Specifications. The J2ME Platform Edition Specification is a collection of Building Blocks. J2ME Profile Specifications can build up desired functionality by combining new API sets with existing Building Blocks.
Java Community Process (JCP): The formal process described in this document for developing or revising Java technology Specifications.
Java Community Process Member (Member): A company, organization, or individual that has signed a Membership Agreement and is abiding by its terms.
Java Specification (Specification): A written specification for some aspect of the Java technology. This includes the language, virtual machine, Platform Editions, Profiles, and application programming interfaces.
Java Specification Request (JSR): The document submitted to the PMO by one or more Members to propose the development of a new Specification or a significant revision to an existing Specification.
Java Specification Participation Agreement (JSPA): A one-year renewable agreement between Oracle America and a company, organization or individual that allows the latter entities to participate in the Java Community Process as a Full Member.
JCP Specification Page (Spec Page): Each Specification approved for development or revision will have a dedicated public web page established on the JCP Web Site to contain a history of the passage of the Specification through the JCP, including a record of the decisions, actions, and votes taken by the EC with respect to the draft Specification.
JCP Web Site: The web site where the public can stay informed about JCP activities, download draft and final Specifications, and follow the progress of Specifications through the JCP.
JSPA 1: A Java Specification Participation Agreement covering Membership in the JCP and participation in JSRs started before October 29, 2002.
JSPA 2: the output of JSR 99: the revised version of the Java Specification Participation Agreement that covers Full Membership in the JCP and participation in JSRs started after October 29, 2002.
JSR Approval Ballot: A two-week EC ballot to determine if the initial JSR submission should be approved.
JSR Page: The web page on the JCP Web site where the JSR's history is recorded and where other relevant information about the JSR is published.
JSR Reconsideration Ballot: The EC ballot to determine if a revision of an initial JSR submission should be approved.
JSR Renewal Ballot: An EC ballot to confirm that a JSR should continue in its work.
JSR Renewal Reconsideration Ballot: An EC ballot to determine if a revised JSR should continue its work.
JSR Review: A two- to four-week period (the length to be set at the discretion of the submitter) during which the public can review and comment on a proposed new JSR before the JSR Approval Ballot.
JSR Status: a label applied to a JSR to indicate the status of a given specification development project. JSR Status labels include: Active, Final, Maintenance, Inactive, Withdrawn, Rejected, and Dormant. They are explained in the table below:
JSR Withdrawal Ballot: An EC ballot to confirm that a completed JSR that appears to have been abandoned should be withdrawn.
Licensor Name Space: The public class or interface declarations whose names begin with "java", "javax", "com.sun" (or "com.Your name" if You are the Specification Lead) or their equivalents in any subsequent naming convention adopted by Oracle.
Maintenance Lead (ML): The Member Representative or individual JCP Member responsible for maintaining the Specification.
Maintenance Release (MREL): The final stage in the JSR maintenance process when the Specification, RI, and TCK have been updated and can be licensed by implementers.
Maintenance Review: A period 14 or 30 days prior to finalization of a Maintenance Release when Members and the public consider and comment on the change the Maintenance Lead proposes to include in the release, as identified in the associated Issue List.
Maintenance Review Ballot: An EC ballot to determine whether the changes and time line proposed by a Maintenance Lead are appropriate for a Maintenance Release.
Maintenance Renewal Ballot: a ballot during which EC members vote on whether to permit a Maintenance Lead to extend the deadline for delivery of materials for Maintenance Release, or whether the previous Maintenance Review should be rescinded and the ML be required to start the process again.
Maintenance Release Withdrawal Ballot: An EC ballot to confirm that a completed Maintenance Release that appears to have been abandoned should be withdrawn.
Member: See Associate Member, Full Member, Java Community Process Member, Member Representative, Partner Member.
Member Representative: An individual who is an employee of or who has a contractual relationship with a Full Member and who is authorized by that Member to represent its interests within the JCP.
Membership Agreement: See Associate Membership Agreement, JSPA, Partner Membership Agreement.
Milestone: Any posting of a JSR that corresponds to one of the milestones detailed in the Java Community Process document. For example, "Community Review," "Early Draft Review," "Proposed Final Draft," "Final Release" and "Public Review" are all milestones.
Minor Revision: Minor changes made to a final Specification by the Maintenance Lead as part of the Maintenance process.
Observer: An individual who is not a member of the JCP but who takes advantage of the JCP's transparency mechanisms to observe and/or comment on Expert Group activities.
Partner Member: A non-profit organization that is unwilling or unable (since it is not a legal entity) to sign the JSPA but which nevertheless wishes to promote and to participate in the activities of the JCP.
Partner Membership Agreement: The membership agreement signed by non-profit organizations that are not legal entities, and therefore ineligible to sign the JSPA.
Platform Edition Specification (Platform Edition): A Specification that defines a baseline API set that provides a foundation upon which applications, other APIs, and Profiles can be built. There are currently three Platform Edition Specifications: Java SE, Java EE, and Java ME.
Profile Specification (Profile): A Specification that references one of the Platform Edition Specifications and zero or more other JCP Specifications (that are not already a part of a Platform Edition Specification). APIs from the referenced Platform Edition must be included according to the referencing rules set out in that Platform Edition Specification. Other referenced specifications must be referenced in their entirety.
Program Management Office (PMO): The group within Oracle that is responsible for administering the JCP and chairing the EC.
Proposed Final Draft: The version of the draft Specification that will be used as the basis for the RI and TCK.
Public Draft Specification Reconsideration Ballot: The EC ballot to determine if a revised draft should proceed after Public Review.
Public Review: A 30 to 90 day period when the public can review and comment on the draft Specification.
Public Review Ballot: The EC ballot to determine if a draft should proceed after Public Review. Used in JCP versions 2.0 through 2.10.
Public Review Final Approval Ballot: The EC ballot to determine if a draft should proceed to Final Release after Public Review. Introduced in JCP 2.11.
Qualified Individual: An individual not acting for or on behalf of a legally organized entity that uses the TCK for the purpose of developing and distributing a compatible implementations of a Spec, and that has established to the satisfaction of the Spec Lead, in its reasonable discretion, that such individual is ready to begin testing its credible implementation of the Spec in question.
Qualified Not-for-Profit: A legally organized not-for-profit entity (such as, but not limited to, a "501[c]" corporation) that is not effectively controlled by a commercial interest and that uses the TCK for the purpose of developing and distributing a compatible implementation of a Spec.
Ratified Seat: An EC seat filled by the ratification process described in section 3.7.5 of the JCP 2.10 document.
Reference Implementation (RI): The prototype or "proof of concept" implementation of a Specification.
Rejected: a JSR Status label indicating that the specification development project or proposal was not approved by Executive Committee ballot.
Release: A Final Release or a Maintenance Release.
Specification: See Java Specification.
Specification Lead (Spec Lead): The Member Representative or individual JCP Member who leads an Expert Group and who is responsible for its deliverables as defined in this Process Document.
Technology Compatibility Kit (TCK): The suite of tests, tools, and documentation that is used to determine if an implementation of a JSR complies with that Specification.
Transfer Ballot: The EC ballot to approve transfer of ownership of a Specification, RI, and TCK from one JCP Member to another. (Transfer of ownership does not mean transfer of IP rights, only the right to start again. The new Spec Lead can, however, negotiate a transfer of IP with the old Spec Lead.)
Umbrella Java Specification Request (UJSR): A JSR that defines or revises a Platform Edition or Profile Specification. A UJSR proceeds through the JCP like any other JSR.
Withdrawn: A JSR Status label applied to a specification development project that started in the JCP and was later removed from the list of active projects because no JCP Member was willing to continue in the leadership role.