Why Jave~TM was-not-standardized twice

摘要

This paper examines two attempts by Sun Microsystems to standardize its Java~TM Technology (a proprietary de facto standard). Sun approached ISO/IEC JTC1 and later the ECMA consortium, but it withdrew both times. In this paper, I analyse Sun's actions. A conceptual framework is applied that distinguishes two levels of coordination in standardization: 'technology-oriented compatibility control' and 'orchestration of market orientation'. Sun's actions addressed both levels. It initially used standardization to focus attention on Java~TM and increase confidence in an open, stable Jana specification process. But it turned to proprietary 'compatibility control' in reaction to standard politics and developments in the market.