By Topic

Java and the PAS process

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)

Anyone who thinks standards just happen and the job of creating standards is easy, fun, and a chance to travel to fun places should have had the chance to help standardize Java. The Sun Microsystems director of standards, was given the “opportunity” of responding to the market's (users, providers, partners, competitors) request to make Java a standard. Everyone wanted it, and Java was already well documented, well known, and being tested and deployed all over the world. The first task was to determine which Standards Developing Organization (SDO) to use and which path or standardization process to follow as the specification moves from a Sun contribution to a final international standard. After much discussion inside and outside the company, we decided to go with the ISO/IEC JTC1 PAS procedure. Here, he explains the Publicly Available Specification (PAS) process and, so that this is not just an academic discussion, uses Java as the example of how the process worked and didn't work. The Java experience also serves to demonstrate that developing standards isn't simple; rather it's a complex discipline that seems (at times) to become everyone's favorite target

Published in:

Micro, IEEE  (Volume:18 ,  Issue: 1 )