Background

On December 8, 1998, Sun Microsystems, Inc., introduced the Java Community Process for the development and revision of Java technology specifications. This formal process was designed to be fast, flexible, and adaptable to a wide variety of working styles present in the community today. Each use of the process will be audited by the independent auditing firm of PriceWaterhouseCoopers. A draft version of the process was circulated to licensees and others for their review and comment on October 8, 1998. Their feedback was gathered by PriceWaterhouseCoopers and played an important role in shaping the form and content of the process.

Read the press announcement made at the Java Business Expo Conference.

Java Community Process Goals

• Enable the broader Java Community to participate in the proposal, selection, and development of Java APIs by establishing a means for both licensees and non-licensees to participate.

• Enable members of the Java Community to propose and carry-out new API development efforts without the need for Sun engineers to be actively involved.

• Ensure that the process is faithfully followed by all participants each time it is used by requiring auditing at key milestones.

• Ensure that each specification is backed by both a reference implementation and the associated suite of conformance tests.

• Help foster a good liaison between the Java community and other bodies such as consortia, standards bodies, academic research groups, and non-profit organizations.

These new procedures are designed to allow for wider participation in the early stages of specification development and to provide an extra level of assurance to the international Java Community that all steps of the process have been properly carried out by all parties involved and that a given specification can be implemented and tested for conformance.

See Also Community Process Formal Rules New Specification Proposals Open Calls for Experts